So who here is running the "testing" 2.6.32 kernel? How's it going?

[muungwana]

anybody know if btrfs is enabled by default? ...the next generation file system that does what ZFS from sun does is still in development and not suitable for long term file storage but i find the snapshot abilities to be very handy for short term file management

[ElCuervo]

I installed it yesterday. So far, NFS and SSH don't work for me with the new kernel. Of course, I'll keep fixing it until I break it completely - then I'll boot into the older kernel!

[Old-Polack]

Neither of the testing kernels will build the dkms-nvidia173 driver. Trying with the same driver from nVidia d/l the installer complains /lib/modules/2.6.31.9-pclos3/source/include/linux/version.h missing, or /lib/modules/2.6.32.2-pclos5/source/include/linux/version.h missing.

This is with the full kernel sources installed, rather than the kernel-devel packages. The newer nVidia drivers build, but won't work properly with a GeForce 6800 GT card; gets a decent desktop, but locks up the various video players. This is common to all kernels when this driver is used.

Needs a way to get the nvidia 173.xx driver to build on either of these kernels before they can be used with this graphics card.

Back to the 2.6.27.31.tex5 for now.

Don't know anything about dkms so I'm just guessing here but maybe the following assumption makes sense: the Nvidia 190 dkms compiles and works fine because it has been set up to use the new gcc which is also used for the new kernels. The 173 Nvidia dkms was set up with the old gcc and hence only works with the older kernels up to 2.6.27 which were compiled with the old gcc. So to have the 173 Nvidia dkms working with the newer kernels maybe the dkms needs to be reworked to use the newer gcc or it may work if "export IGNORE_CC_MISMATCH=1" is set before compiling the dkms?? Just a thought...

This was brought up in another thread, but dkms seems to already be set that way by default. I've had the same modules compiled with gcc 4.1, 4.3, and 4.4 without any error messages and the modules all seem to function as they should. The installation I'm currently using with the 2.6.27.31.tex5 kernel has the nvidia d/l driver now installed. It's installer mentioned the compiler mismatch, and asked if I wanted to discontinue the installation. I answered no, and the build went on successfully. It builds with this kernel because the /lib/modules/2.6.27.31.tex5/source/include/linux/version.h file it seeks, is in fact present.

I see the problem totally as the build stopping because a required file (version.h) is missing from the sources. It may not be needed by the kernel build process anymore, may be renamed, (in which case a link with the version.h name would be sufficient) or may be an optional file, for the kernel build process to use only if some specific feature is desired, but the nvidia driver build process does require it, and it's not there. Either the file needs to be provided, or the requirement for it deleted from the driver code. As the driver code is closed source, changing it seems unlikely, while providing a proper version.h file in the kernel sources should be relatively simple.

[pinoc]

Hi Old-Polack,

I have installed 2.6.32 and the corresponding -devel package and the file /lib/modules/2.6.32.2-pclos5/source/include/linux/version.h does exist and has the following content:

Code: [Select]

#define LINUX_VERSION_CODE 132640
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

Strange that you don't seem to have this file, maybe you can just create it with the above content and then test if the 173 dkms compiles? I think you mentioned you installed the full sources, maybe there is a problem with that and you can try installing the devel-package instead?
best,
-pinoc

[Old-Polack]

Hi Old-Polack,

I have installed 2.6.32 and the corresponding -devel package and the file /lib/modules/2.6.32.2-pclos5/source/include/linux/version.h does exist and has the following content:

Code: [Select]

#define LINUX_VERSION_CODE 132640
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

Strange that you don't seem to have this file, maybe you can just create it with the above content and then test if the 173 dkms compiles? I think you mentioned you installed the full sources, maybe there is a problem with that and you can try installing the devel-package instead?
best,
-pinoc

Funny you should mention.

I took a version.h file from the 2.6.27.31.tex5 sources, compared it with the version.h file from a 2.6.26 kernel, and noticed the only difference seemed to be the last digit of the first line, which incremented by one. Assuming one increment per version, I extrapolated the version.h files for the 2.6.31 and 2.6.32 kernels to be;

Code: [Select]

#define LINUX_VERSION_CODE 132639                                           <-- 2.6.31
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))


#define LINUX_VERSION_CODE 132640                                            <-- 2.6.32
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

modified the file, for each kernel, as shown, and saved it in the appropriate place in each respective /usr/src/ directory.

I tried building the nvidia driver with that home made version.h for the 2.6.31.9-pclos3 kernel, and got a totally different error about still not being able to determine the version. This was before my first post in this thread, so then suspected I had gotten the extrapolation wrong, or missed something else, possibly to do with the second line in version.h. From your reply, it would now seem this is not so.

I haven't yet tried with the 2.6.32.2-pclos5 but I suspect now, there is still yet another unspecified file missing. I will try again with the 2.6.32.2-pclos5 kernel, and check the error message more carefully if it too fails. Should that be the case, then I'll uninstall the full sources, install the -devel package, and try yet again, to see if that works.

I find this a bit strange, as this is the first time I've found the full source installation to not include all that is included in the -devel package, plus all the extras.

[Old-Polack]

Progress Report:

Booted to run level 3 with the 2.6.32.2-pclos5 kernel. Dkms again failed to build the nvidia 173.xx driver. Tried the nVidia d/l installer with version.h in place in full sources, and got;

ERROR:Unable to determine the version of the kernel sources located in '/lib/modules/2.6.32.2-pclos5/source'. Please make sure you have installed the kernel source for your kernel and that they are properly configured: on Red Hat Linux systems for example, be sure you have 'kernel-source' or 'kernel-devel' RPM installed. If you know the correct kernel source files are installed, you may specify the kernel source with the '--kernel-source-path' command line option.

Retried the command with --kernel-source-path /usr/src/linux parameter, after making sure the link pointed to the correct sources directory. Got the same above error.

Uninstalled the kernel source, and installed the kernel-devel package. Dkms still fails to build the 173.xx package with this kernel,... but the nVidia d/l package now builds... and I am currently still running with the 2.6.32.2-pclos5 kernel and that driver installed.

So far the one item that seems not quite up to snuff is glxgears, which gives 3000+ fps with the 2.6.27.31.tex5 kernel, but with this kernel;

[root@fatman ~]# glxgears
5774 frames in 5.0 seconds = 1154.772 FPS
6354 frames in 5.0 seconds = 1270.696 FPS
6611 frames in 5.0 seconds = 1321.870 FPS
6921 frames in 5.0 seconds = 1384.167 FPS
7127 frames in 5.0 seconds = 1425.357 FPS
6899 frames in 5.0 seconds = 1379.329 FPS
6892 frames in 5.0 seconds = 1378.122 FPS

Other than that everything seems to be working so far.

Edit:

After playing about a bit getting VBox setup for this kernel, and testing my video players and such, re ran glxgears;

[root@fatman ~]# glxgears
20916 frames in 5.0 seconds = 4183.042 FPS
21411 frames in 5.0 seconds = 4282.139 FPS
21527 frames in 5.0 seconds = 4305.304 FPS
21336 frames in 5.0 seconds = 4267.135 FPS
20982 frames in 5.0 seconds = 4196.236 FPS
21573 frames in 5.0 seconds = 4314.500 FPS
21408 frames in 5.0 seconds = 4281.247 FPS
21415 frames in 5.0 seconds = 4282.621 FPS
21541 frames in 5.0 seconds = 4308.126 FPS

Now that's looking more like what I expected.  

[MBantz]

I'm having somewhat the same issues with 2.6.32.2 kernel but with the Nvidia 190 driver,

when building the dkms, it asked for the kernel .config file, it was not present, so I took it from the nosrc.rpm, needed to install glibc-headers and kernel-devel to be able to compile successfully, by hand that is using:

dkms build -m nvidia-current -v 190.53-1pclos2010 --kernelsourcedir=/usr/src/linux-2.6.32.2-pclos5/

In the 173.xx case the -v parameter is different (look in /var/lib/dkms/nvidia* folder for the exact name/version)

When the compilation above is done, there will be a dkms build logfile in /var/lib/dkms/nvidia*/version*/build - this is interesting to know what it says,

EDIT: forgot to mention that the compile went fine, but fail starting X - it says 'invalid module format' - so I changed nvidia to nv in Xorg.conf and use this for now (i.e. the driver is not used)

cheers,
MBantz

[menotu]

I had the same issue as some others - eg, 2.6.32.2 installed just fine but when rebooting it dropped me at the command line and "startx" wouldn't run.

My fix was to re-boot using 2.6.27.31 (which I had kept on the system) I then opened Synaptic and this time re-installed the following:

1: kernel 2.6.32.2
2: nvidia_190.53 driver
3: virtualbox 3.1.2

Rebooted and everything went as smooth as clockwork

[Bald Brick]

As a result of installing 2.6.32.2 I've seen one major change: no more lockups!

Ever since installing KDE4 I've been plagued by the screen freezing relatively frequently. Not anymore!

The system also seems snappier, but that may of course depend on how I use it. On the negative side an open window showing a directory isn't always updated automatically when something is written to that directory. This happened a lot some years ago, but not lately. That it started again when I installed the the new kernel may of course be coincidence.

My video driver is Nvidia 190.42 from Synaptic and the video card is a G96 (GeForce GT 120).

[muungwana]

On the negative side an open window showing a directory isn't always updated automatically when something is written to that directory. This happened a lot some years ago, but not lately. That it started again when I installed the the new kernel may of course be coincidence.

This problem shows up when using kernel version 2.6.31 and up and is already fixed in trunk. KDE SC 4.4 will not have this bug

[kjpetrie]

I've just downloaded it to test in my test partition to see how badly it runs on this hardware.

With the i810 and greater driver the system would reboot in response to any attempt to start X. Also the boot messages were unreadable (as previously mentioned) in a normal boot, though not on non-fb boot.

With the XORg|intel driver I get a desktop, but no compositing of course. I have just discovered my modprobe.conf is:

Code: [Select]


00000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000'
        }
        control.18 {
                comment.access 'read write'
                comment.type BOOLEAN
                comment.cou
and my modprobe.preload is:

Code: [Select]


IS_LAPTOP=false
KERNEL=2.6
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

I'm now going to rboot to see what happens.

[T6]

"21541 frames in 5.0 seconds = 4308.126 FPS

Now that's looking more like what I expected."




2905 frames in 5.0 seconds = 580.972 FPS


 

[kjpetrie]

On this hardware [82945G/GZ Integrated Graphics Controller (rev 02)] neither the .31 nor the .32 kernel will run X with the Intel-supplied 810 and greater driver (from the repo). I have to revert to the generic Intel driver to get a desktop. I then have no 3d, so it's not a forward step yet.

Possibly it is the result of the empty modprobe.conf and modprobe.preload files, or possibly the newer kernels just don't like Intel hardware.

I tried playing with the options in xorg.conf, but the most I could get with the Vendor's driver was a desktop that stopped loading (played the beginning of the start sound then froze - the generic xorg intel gives a white flash at this point) about half way through, and no virtual terminals to switch into either.

With the generic driver gears runs at just 270 FPS. (.31 kernel.)

[7272andy]

I've been running the .32 kernel with an Intel 9343GM using the "Intel 810 and later driver" as supplied from the repo. for the last few weeks.

As a rule things are a lot snappier in general use though my glxgears have dropped to similar levels to T6. Seen no other on screen problems (verbose boot shows all the lines).

Andy

[kjpetrie]

After re-installing the video driver I could sometimes get to a desktop and even run compositing at 280 FPS. However, XAA rendering (X triggers instant reboot if this is selected) was not available and EXA runs slower on this GPU.

It isn't reliable though. Even booting isn't reliable and sometimes fails, unable to find the filesystem.