I've rebuilt the Elrepo Kernel-ml package (with thanks to Alan Bartlett) and applied the ClearOS patches, so that users can experiment with a more 'bleeding edge' kernel. This is useful for situations where the current ClearOS 6.x 2.6.32 kernel is too 'old' and doesn't support your hardware, or you want to take advantage of some later kernel features
Only install this on test systems! you have been warned, you get to keep the pieces if it breaks ;-) These kernels install alongside your existing kernels, so if it doesn't boot correctly, you can choose your old kernel from the boot menu and carry on
See the following link for a list of interesting kernel-3.7 features
http://www.phoronix.com/scan.php?page=news_item&px=MTIxNjA
To instal (64bit systems only):-
Check the boot config is OK in /etc/grub.conf, change default if required
Reboot and cross everything! monitor output in 'dmesg' after boot
Known issues:-
- there appear to be a lot of SELinux policy warnings
- multiwan support is unknown
Only install this on test systems! you have been warned, you get to keep the pieces if it breaks ;-) These kernels install alongside your existing kernels, so if it doesn't boot correctly, you can choose your old kernel from the boot menu and carry on
See the following link for a list of interesting kernel-3.7 features
http://www.phoronix.com/scan.php?page=news_item&px=MTIxNjA
To instal (64bit systems only):-
wget ftp://timburgess.net/repo/clearos/6/testing/x86_64/kernel-ml-3.7.9-1.clearos.x86_64.rpm
rpm -ivh kernel-ml-3.7.9-1.clearos.x86_64.rpm
Check the boot config is OK in /etc/grub.conf, change default if required
Reboot and cross everything! monitor output in 'dmesg' after boot
Known issues:-
- there appear to be a lot of SELinux policy warnings
- multiwan support is unknown
Share this post:
Responses (18)
-
Accepted Answer
Hi Tim
I installed the 3.13 Kernel succesfully ( i assume as there where no errors) rebooted but the Wifi adapter still has no option to configure as part of the gateway.
I checked uname -r and in the dashboard and the system is still reporting a Kernel version of 2.6.32-431.23.3.v6.x86_64
have i missed something?
Edit: Seems i didnt change the default selection in the grub.conf. -
Accepted Answer
-
Accepted Answer
OK - the kernel is a straight rebuild from Elrepo, perhaps there is a config difference, or more likely a module version difference. The tun.ko module is built and provided in this kernel. There is some major differences between the 2.6.32 and 3.13.x series so it will be difficult to try and compare...as I said I don't use ibVPN but if I get time I'll have a go
[root@leonardo ~]# modinfo tun
filename: /lib/modules/3.13.2-1.clearos.x86_64/kernel/drivers/net/tun.ko
alias: devname:net/tun
alias: char-major-10-200
license: GPL
author: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
description: Universal TUN/TAP device driver
srcversion: 5C9BC6FCBD9D92B2626F89E
depends:
intree: Y
vermagic: 3.13.2-1.clearos.x86_64 SMP mod_unload modversions
You can check yours is loaded by ibVPN by running 'lsmod | grep tun'...also check the dmesg output -
Accepted Answer
Hello Tim,
No, with the standard kernel, everything works fine.
I've been debugging a lot with Darryl Sokoloski (dev of ibVPN app in CLearOS) as we thought at first that the problem was coming from the app.
But in fact it's this kernel that causes trouble. And I need this kernel to have my wifi working.
Maybe you can contact Darryl to identify what is mis-working with your kernel ?
Darryl told me that the only kernel module that he uses is tun.ko. Do you have included it ? -
Accepted Answer
-
Accepted Answer
Hello Tim.
I encounter an issue with this kernel and ibVPN.
The vpn starts fine but it doesn't work fine.
When I try to load a page it takes several minutes to load (4/5 minutes) and sometimes it will never load.
In fact, after some debugging with Darryl Sokoloski, some packets are lost and restransmitted but the answer never comes back.
Do you have any idea to fix that ? -
Accepted Answer
Tim you've just saved my life.
I've been struggling with wifi for ... well, 1 year and 9 months
I abandoned the fight a long time ago and put my ClearOS box in a closet. And today, I was wondering if something has evolved with ClearOS. I reinstalled v6.5 but no changes for me. The kernel is still <= 2.63.35 so I can't compile the drivers.
And by a curious concincidence :P , I read this topic (I was searching if a higher kernel was available).
And the magic was here.
Everything works fine the first time. :woohoo:
Great job, Tim.
Bye
Orvis -
Accepted Answer
I'm also using VirtualBox on Win7 x64. I guess you mean virtual hardware? My virtual NICS (LAN and WAN) are both Intel Pro1000/MT Desktop in NAT configuration so the LAN uses 10.0.2.0/24 addresses (but has nothing connected. I connect via 127.0.0.1 via my PC) which get port forwarded through. The WAN interface uses 10.0.3.0/24. The interface itself normally gets 10.0.3.15 and the gateway is 10.0.3.2.
Syswatch form 2.6.32:
and 3.13.2:Thu Apr 17 14:21:08 2014 info: system - syswatch started
Thu Apr 17 14:21:08 2014 info: config - IP referrer tool is not installed
Thu Apr 17 14:21:08 2014 info: config - debug level - 0
Thu Apr 17 14:21:08 2014 info: config - retries - 5
Thu Apr 17 14:21:08 2014 info: config - heartbeat - 10
Thu Apr 17 14:21:08 2014 info: config - interval - 60 seconds
Thu Apr 17 14:21:08 2014 info: config - offline interval - 10 seconds
Thu Apr 17 14:21:08 2014 info: config - referrer IP detection - disabled
Thu Apr 17 14:21:08 2014 info: config - ping server auto-detect - enabled
Thu Apr 17 14:21:08 2014 info: config - try pinging gateway - yes
Thu Apr 17 14:21:08 2014 info: config - number of external networks - 1
Thu Apr 17 14:21:08 2014 info: config - monitoring external network - eth1
Thu Apr 17 14:21:08 2014 info: info - loading network configuration
Thu Apr 17 14:21:08 2014 info: info - network configuration for eth1 - config: ifcfg-eth1
Thu Apr 17 14:21:08 2014 info: info - network configuration for eth1 - onboot: enabled
Thu Apr 17 14:21:08 2014 info: info - network configuration for eth1 - type: dhcp
Thu Apr 17 14:21:08 2014 info: info - network configuration for eth1 - wifi: disabled
Thu Apr 17 14:21:08 2014 info: eth1 - network - IP address - 10.0.3.15
Thu Apr 17 14:21:08 2014 info: eth1 - network - gateway - 10.0.3.2
Thu Apr 17 14:21:08 2014 info: eth1 - network - type - private IP range
Thu Apr 17 14:21:08 2014 info: system - changing active WAN list - eth1 (was startup)
Thu Apr 17 14:21:08 2014 info: system - current WANs in use - eth1
Thu Apr 17 14:21:08 2014 info: system - restarting firewall
Thu Apr 17 14:21:09 2014 info: system - updating intrusion prevention whitelist
Thu Apr 17 14:21:09 2014 info: system - adding ping server 69.90.141.72
Thu Apr 17 14:21:09 2014 info: system - adding ping server 10.0.3.2
Thu Apr 17 14:21:09 2014 info: system - adding DNS server 172.17.2.1
Thu Apr 17 14:21:09 2014 info: system - reloading intrusion prevention systemThu Apr 17 09:44:35 2014 info: system - syswatch started
Thu Apr 17 09:44:35 2014 info: config - IP referrer tool is not installed
Thu Apr 17 09:44:35 2014 info: config - debug level - 0
Thu Apr 17 09:44:35 2014 info: config - retries - 5
Thu Apr 17 09:44:35 2014 info: config - heartbeat - 10
Thu Apr 17 09:44:35 2014 info: config - interval - 60 seconds
Thu Apr 17 09:44:35 2014 info: config - offline interval - 10 seconds
Thu Apr 17 09:44:35 2014 info: config - referrer IP detection - disabled
Thu Apr 17 09:44:35 2014 info: config - ping server auto-detect - enabled
Thu Apr 17 09:44:35 2014 info: config - try pinging gateway - yes
Thu Apr 17 09:44:35 2014 info: config - number of external networks - 1
Thu Apr 17 09:44:35 2014 info: config - monitoring external network - eth1
Thu Apr 17 09:44:35 2014 info: info - loading network configuration
Thu Apr 17 09:44:35 2014 info: info - network configuration for eth1 - config: ifcfg-eth1
Thu Apr 17 09:44:35 2014 info: info - network configuration for eth1 - onboot: enabled
Thu Apr 17 09:44:35 2014 info: info - network configuration for eth1 - type: dhcp
Thu Apr 17 09:44:35 2014 info: info - network configuration for eth1 - wifi: disabled
Thu Apr 17 09:44:35 2014 info: eth1 - network - IP address - 10.0.3.15
Thu Apr 17 09:44:35 2014 info: eth1 - network - gateway - unknown
Thu Apr 17 09:44:35 2014 info: eth1 - network - type - private IP range
Thu Apr 17 09:44:35 2014 warn: eth1 - no default gateway found
Thu Apr 17 09:44:35 2014 info: eth1 - ping check - no gateway found
Thu Apr 17 09:44:35 2014 info: eth1 - restarting DHCP connection
I've just tried changing it to a Static IP and it does not help. It does not like the gateway it finds with the 2.6.32 kernel. -
Accepted Answer
-
Accepted Answer
There is something more seriously wrong. It looks like my VM WAN, which is DHCP, is not picking up a gateway IP with the new kernel. Syswatch then continually restarts the interface. Reverting to the stock kernel is fine.
..... my production box has DHCP on its WAN so I may have to hold off on this update. Pity as it makes a lot of nice noises about power management. -
Accepted Answer
-
Accepted Answer
Ok I'll try and replicate it here, you only need kernel-devel for compiling modules (I've never had to update kernel-headers for kmod modules) and unlikely you'll need either for libreswan as its not kernel dependant
Kernel-headers are backwards compatible and do not have to match the latest kernel, in fact software built against the newer version may not work on older kernels
https://www.kernel.org/doc/Documentation/make/headers_install.txt -
Accepted Answer
I assumed I would need to recompile Libreswan and maybe the kmod packages so I would need the headers, but I can't see how to install them. I can't upgrade the headers (see above -ivh and -Uvh which give the same error) and I can't uninstall the old kernel-headers because of a fist full of dependencies, unless I remove the old package with a --nodeps which I am a bit cautions of doing.
I did try installing the kernel and rebooting and that was fine but I still could not remove the old kernel-headers.
I suppose I could take a snapshot of the VM so I could roll back, but I'd be reluctant to go down this route on my live system. Could there be an issue with the -ml in the package name with packages like glibc-headers not seing this as a valid package to satisfy its dependencies? -
Accepted Answer
-
Accepted Answer
I thought I'd try this one but I'm struggling with the headers:
I can't remove kernel-headers-2.6.32-431.3.1.v6.x86_64 because of a dependency with glibc-headers and glibc-devel and thus to lots of perl stuff.[root@ClearOS6_3 src]# rpm -ivh kernel-ml-headers-3.13.2-1.clearos.x86_64.rpm
error: Failed dependencies:
kernel-headers < 3.13.2-1.clearos conflicts with kernel-ml-headers-3.13.2-1.clearos.x86_64
[root@ClearOS6_3 src]# rpm -Uvh kernel-ml-headers-3.13.2-1.clearos.x86_64.rpm
error: Failed dependencies:
kernel-headers < 3.13.2-1.clearos conflicts with kernel-ml-headers-3.13.2-1.clearos.x86_64
P.s. It is on my test VM so it is not at all critical -
Accepted Answer
Just built kernel-ml-3.13.2 with the ClearOS patches and it's running on my live system without problems
http://www.phoronix.com/scan.php?page=news_item&px=MTUxNTk
wget ftp://timburgess.net/repo/clearos/6/testing/x86_64/kernel-ml-3.13.2-1.clearos.x86_64.rpm
rpm -ivh kernel-ml-3.13.2-1.clearos.x86_64.rpm
kernel-ml-devel and kernel-ml headers are also available if required for building your own modules
ftp://timburgess.net/repo/clearos/6/testing/x86_64/kernel-ml-devel-3.13.2-1.clearos.x86_64.rpm
ftp://timburgess.net/repo/clearos/6/testing/x86_64/kernel-ml-headers-3.13.2-1.clearos.x86_64.rpm
FYI some features in later 3.x kernels...
- BTRFS support
- SMB2 CIFS support
- nftables (iptables successor)
- Better hardware and wireless support
- Power management for Radeon cards
- ARM support (investigating this one!) for kernels 3.7+
- Filesystem improvements
- Timerless multitasking (and power savings)
Enjoy all feedback welcome!
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »