Best 3.9 Kernel for Raring

[Rich Oliver]

If I want to use a 3.9 Kernel should I use a Saucy Kernel or try and install from a standard Kernel?

[SteveRiley]

If you're asking about the available mainline kernel builds, the 29 April build of 3.9 will be the only one specifically labeled "raring." The "saucy" builds will be more current, and will run on Raring just fine. Mainlines are always built on the latest LTS just before the named release. The named release indicates which configuration was used for the build. (source)

[Rich Oliver]

Ah Thanks that's good to know. I shall probably try 3.10 as soon as its out. I actually didn't spot the 29th April Ring tail build.

[starbuck]

Hi Steve,

would these three packages be enough to completely update current 3.8 raring kernel to saucy 3.9.3:

http://kernel.ubuntu.com/~kernel-ppa...91535_i386.deb
http://kernel.ubuntu.com/~kernel-ppa...191535_all.deb
http://kernel.ubuntu.com/~kernel-ppa...91535_i386.deb

Is there anything to consider when using a saucy kernel in raring, or is it supposed to work just fine, also with future packages in raring?
What packages relate to the kernel packages, and could potentially be at odds with a saucy kernel in raring (like packages that will be adapted for saucy (kernel), and that not update to that 3.9.3 in raring)?

[SteveRiley]

Typically, distributions take the kernel source code, add in a few of their own patches, and then compile the code using customized configurations. (Mostly, configuration files enable or disable specific -- often obscure -- capabilities). The default kernels provided by Ubuntu follow this route.

Ubuntu also offers another option: unpatched kernels, but still compiled with Ubuntu's configuration files. These are called mainline builds and are available for download.

The "-series" suffix indicates the release whose configuration files were used during compilation. The kernels are compiled using the toolchain from the LTS closest to the named series. Thus, 3.9.3-saucy was compiled with the Precise toolchain using the Saucy configuration. In practice, you can use a newer series on an older release, so long as you stay relatively close. I just installed the 3.9.3-saucy kernel on my Raring laptop last night, and it's working fine. You could probably use this same kernel on Quantal and even Precise, but I wouldn't try it on anything earlier than that.

[PJJ]

. . . In practice, you can use a newer series on an older release, so long as you stay relatively close. I just installed the 3.9.3-saucy kernel on my Raring laptop last night, and it's working fine. You could probably use this same kernel on Quantal and even Precise, but I wouldn't try it on anything earlier than that.

In installed 'saucy' as an update to 12.10 by first going to 13.04 and then version updating to 3.9.3.

As of now everything is working so smoothly that I am (again) tempted to use 'saucy' more often as working installation - till the next user induced issues and problems.

[SteveRiley]

In installed 'saucy' as an update to 12.10 by first going to 13.04 and then version updating to 3.9.3.

Installing a Saucy-series kernel doesn't mean you've updated your entire Kubuntu release to Saucy. I think you already know this, but just wanted to be sure.

FWIW, I have almost never used the default kernels that come with any particular release. Kernel development happens much faster than Ubuntu's six-month cycle, and I think it's important to keep on top of that. I've been running the latest version of mainline kernels for quite some time. I generally avoid the "rc" builds and wait until a kernel version is finished. Then I install that, and regularly update it whenever a new one appears.

[Guest]

If I can join to this post - I would like to ask if any of you do not have any problem to get proprietary driver ( nvidia / fglrx ) properly "depmoded" into mainline kernel within installation process ? I do have that problem - so it is always going to work only with mesa drivers but I cannot figure out how to make it work with proprietary drivers. Any suggestions or experience how to get mainline kernel work with proprietary driver (even compile it from source code) ?
thanks.

[Rog131]

...any problem to get proprietary driver ( nvidia / fglrx ) properly "depmoded" into mainline kernel within installation process ? ...

Could you tell how you are installing the proprietary driver ?
Are you wrapping the driver to the debian package ?
Do you have the dkms installed ?

The dkms:

:~$ apt-cache show dkms
Description: Dynamic Kernel Module Support Framework
DKMS is a framework designed to allow individual kernel modules to be upgraded
without changing the whole kernel. It is also very easy to rebuild modules as
you upgrade kernels.
Homepage: http://linux.dell.com/dkms

At here, fglrx:

Log of sudo apt-get install linux-image-3.9.0-030900-generic linux-headers-3.9.0-030900-generic
Wed May 1 17:33:57 2013

Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
linux-headers-3.9.0-030900
Suggested packages:
fdutils linux-doc-3.9.0 linux-source-3.9.0 linux-tools
The following NEW packages will be installed:
linux-headers-3.9.0-030900 linux-headers-3.9.0-030900-generic
linux-image-3.9.0-030900-generic
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
....
run-parts: executing /etc/kernel/postinst.d/dkms 3.9.0-030900-generic /boot/vmlinuz-3.9.0-030900-generic
...
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.9.0-030900-generic /boot/vmlinuz-3.9.0-030900-generic
...

The dkms is taking care of the kernel modules = > no problems at here.

[SteveRiley]

The nVidia blob from Xorg-Edgers installs without a hitch on my T520.

[Guest]

Could you tell how you are installing the proprietary driver ?
Are you wrapping the driver to the debian package ?
Do you have the dkms installed ?

The dkms:


At here, fglrx:



The dkms is taking care of the kernel modules = > no problems at here.

-well, I should post here more information. I have dkms installed and all necessary stuff. I do not use deb packages.
For fglrx installation I am using my own installation script which works properly with any official ubuntu kernel except mainline kernels.

-The problem /for all mainline/ kernels is following:
DKMS make.log for fglrx-updates-9.012 for kernel 3.10.0-999-generic (x86_64)
Thu May 23 10:02:18 BST 2013
/usr/sbin/dkms: line 73: cd: /var/lib/dkms/fglrx/9.012/build: No such file or directory
AMD kernel module generator version 2.1
kernel includes at /lib/modules/3.10.0-999-generic/build/include not found or incomplete
file: /lib/modules/3.10.0-999-generic/build/include/linux/version.h

-even if I create this file and calculate the version number /-> in .../version.h/ I still get problem to finalize to proper installation -> always leads to that fglrx is not "taking part" in any way.

[Rog131]

fglrx

Same kind of: https://bugs.launchpad.net/ubuntu/+s...s/+bug/1182069
- It is with the Saucy
- It has the same problem: '/usr/sbin/dkms: line 73: cd: /var/lib/dkms/fglrx/9.012/build: No such file or directory''


At here:

- AMD Catalyst 13.4/ Kernel 3.9.0 was installing without problems.
- The 3.10 have problems:

Traceback (most recent call last):
File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.10.0-999-generic (x86_64)
Consult /var/lib/dkms/fglrx/12.104/build/make.log for more information...

Ubuntu+1 link of the 3.10: http://ubuntuforums.org/showthread.php?t=2147104