You are not logged in.

Dear visitor, welcome to If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.


Friday, February 27th 2004, 12:40pm

Upgrade Suse 9.0 to kernel 2.6.2

Has anyone here accomplished to upgrade Suse 9.0 to kernel 2.6.x ? I would like to try but I don't even know where to start.
The Best Games are for Download @ GCCLINUX


Tuesday, March 2nd 2004, 1:34am

yes.. BUT

update mkinitrd, modutils and install udev. (modutils works fine with 2.6.1 and 2.6.2 kraxel builds.. read the last lines before doing anything)

then install kernel-source and kernel-default.
also dont forget the "#generate-modprobe.conf | tee /etc/modprobe.conf"

BUT: make a backup of your modprobe.conf before (generate-modprobe.conf is a bit buggy). Copy the contents of your "lsmod" before rebooting so you will know what modules to load in case your NIC, soundcard, modem wont start up. If they are not loaded, add "/usr/sbin/modprobe <modulename>" to your boot.local at "/etc/init.d/".

CAUTION: I advise to stay away from the 2.6.3-7 kraxel build. It breaks a lot of stuff. Forget about nvidia drivers, or radeon, etc.. It will also break XFree86 stuff (video libs mostly). Also you need to remove modutils and use module-init-tools. So stay with 2.6.2-6-default for now. :wink:


Tuesday, March 2nd 2004, 7:44am

Thank you for your post, although I am still unsure where to start. Would it be too much to ask if you could write me a step by step procedure in how to upgrade.

Many Thanks
The Best Games are for Download @ GCCLINUX


Wednesday, March 3rd 2004, 3:18am



The procedure is for Suse 9.0 i386 only. This have worked for me but i cannot garantee it will work for you. Proceed with caution and make sure you copy this post for offline reading if something unexpected happens (print it if you can). In case of a major screwup, make sure you have your Suse 9.0 CDs/DVDs at hand for system rescue. Also, this procedure is NOT recomended for the weak of heart or linux newbies (in that case, you should wait for Suse 10 or whatever its going to be called). For further assistance, you should have basic knowlodge in understanding kernel messages.
Don't be afraid because of the lenght of this "simple guide". Im only trying to make it a very clear procedure. :wink:

[list]Packages Needed (RPMs)[/list:u][/list][list]
(update) kernel: *

(install) udev:…-018-3.i586.rpm **

(update) mkinitrd:….0-130.i586.rpm

(update) modutils:….25-78.i586.rpm ***

(update) lvm2:….07-40.i586.rpm ****

(install) device-mapper:….07-15.i586.rpm *****


The packages listed above are for reference. Get them from your closest Suse mirror and keep in mind the versions may change at any time without notice, rendering the above links useless. Now on to the caveats:

* This procedure is aimed at upgrading to the 2.6.2 kernel . The RPMs for 2.6.3 currently breaks some drivers, notably proprietary Video drivers. I also believe XFree86 needs some tweaks in order to work properly with this kernel. If you really need 2.6.3, proceed with manual compilation. Tutorials avaiable at Also keep in mind these are experimental builds and older versions are NOT kept online, so make sure you have local backups of older kernels provided by that ftp address. A mirror for the 2.6.2 kernel package is avaiable in the Installing/Updating section.

** udev is required for the 2.6 series linux kernel. Its an implementation of devfs for user space. Devices are listed in /sys .

*** modutils from Suse 9.0 is able to work with 2.4 as well as 2.6 kernels. If you plan to keep both 2.4 and 2.6 kernels, you must have this package. If you plan to keep only the 2.6 kernel, you will be better off with module-init-tools for long term compatibility (…pre9-2.i586.rpm). module-init-tools is a substitute for modutils.

**** If you are currently using LVM on 2.4 , you must upgrade to lvm2 for 2.6.x or you risk not being able to boot later. If you do not use LVM, you may safely ignore this upgrade, but it wont hurt to do it anyway.

***** lvm2 depends on it.


The procedure here listed must be executed as root. But before doing anything, lets get into some backup steps.

[code:1]# md /root/backup 'or mkdir, lets create a backup folder
# cp /etc/modprobe.conf /root/backup/ 'very important as this file will be overwritten later
# lsmod > /root/backup/mymodules.txt 'writes the output of lsmod &#40;list loaded modules&#41; to mymodules.txt[/code:1]


For NVIDIA closed source driver users:
If you are using the NVidia video drivers, make sure you uninstall them or disable it. You will need the new drivers with support for the 2.6 kernel. If you do not wish to use the 5336 version (latest as of 02-03-2004) you can patch your old ones as instructed in .

In order to uninstall the drivers, you must find where your NVIDIA-Linux-x86-1.0-????-pkg?.run file is. It is usually at /usr/share/doc/nvidia/. But keep in mind this procedure is done on Runlevel 3 instead of 5. To go to runlevel 3, save all your work and logout from your kde/gnome session if necessary, hit CTRL+ALT+F3 , login as root and ...

[code:1]# init 3 'you will see the output of some services being terminated. so your X session will be terminated. You cannot play with video drivers while X11 is running. If you dont receive a prompt, you can press ENTER and that should do the trick.
# cd /usr/share/doc/nvidia
# sh NVIDIA-Linux-x86-1.0-????-pkg?.run --uninstall
# sax2 -m 0=nv 'here you will set your video driver to the default open source nv driver. This one works with kernel 2.6 with no problems so the next time you boot on 2.6, you should be able to use KDE/Gnome right away. Save your settings and exit.
# init 5 'optional.. but good to do so you know the NV driver is working as expected. The lack of the nvidia logo shows you're not using it anymore. At this point, you're thrown back at F7. CTRL+ALT+F3 to go back to your prompt in case something goes wrong. Do a init 3 again, check if you didnt miss anything. Rinse, repeat.[/code:1]
But if you want to do it the dirty way, use your preferred text editor to edit /etc/X11/XF86Config . Find the line Load "glx" and comment this line by adding a # in front of it. Now find the Section "Device" section, where you see Driver "nvidia" change to Driver "nv" . Save the file.

Now hit CTRL+ALT+BACKSPACE to restart XFree86. The Nvidia logo should not appear here either.

The next time you run NVIDIA-Linux-x86-1.0-5336-pkg?.run to install the 2.6 kernel compatible drivers (of course, after booted on 2.6), it will remove the old drivers automatically.
It can be downloaded from…

Now considering you downloaded the packages from the top of this post, except the kernel, lets move on to some rpm voodoo magic.

Download the 2.6.2 kernel and sources at:….6.2-6.i586.rpm….6.2-6.i586.rpm

So, lets see what packages you have already and wich versions (as root):
[code:1] # rpm -qa | egrep 'mkinit|udev|modut|module-i|lvm|device' [/code:1]

You should now see mkinitrd, modutils and possibly lvm. Update these packages if required with:
# rpm -vh -U modutils-2.4.25-78.i586.rpm
Watch for dependencies. Im writing this from the top of my head. If i remember correctly, with lvm2 you should need to include both lvm2 and device-mapper packages on the same "rpm -vh -U" string.
If you are an user of apt4rpm, better. Just do it with no fear :wink: .
As far as i can tell, theres no particular order for the rpm voodoo.

And now,
[code:1]# rpm -vh -U kernel-default-2.6.2-6.i586.rpm kernel-source-2.6.2-6.i586.rpm[/code:1]

Watch for the output. It should change your grub settings automatically.

[list]Booting with 2.6[/list:u][/list][list]
Now that you have everything in place and no errors ocurred, you should be safe to reboot.
At this time, choose the normal boot but keep in mind that some improvements like ACPI may be buggy for some systems. If you experience unusual hd resets in loop, try the ide=nodma string in grub. If its a total screwup, use the Failsafe option on grub. If everything fails, time for some system rescue (hence the note at the top about having the cds at hand).

Dont mind the Failed notices when your services are being started. This is normal and your services are actually started.
Now with a successful boot, you should check if all the kernel modules are loaded. Do a lsmod and compare with the output of the old one you have on your backup folder now (mymodules.txt). Most of the time sound modules are not loaded, so you have to do something like:
[code:1]# modprobe snd-emu10k1 'this is for SoundBlaster Live! cards[/code:1]
Thats why you need the module names. lsmod again, compare. Rinse, repeat.

The generate-modprobe.conf tool might help fixing it for good. For that, do:
[code:1]# generate-modprobe.conf | tee /etc/modprobe.conf[/code:1]
But this tool can be quite buggy sometimes, hence the note about backup of your old modprobe.conf . To test, reboot.
If its not working for you and you dont want to do a modprobe by hand every time you reboot, add lines to your /etc/boot.local file as:
/sbin/modprobe snd-emu10k1
/sbin/modprobe snd_ens1370[/code:1]

The first thing you will notice when starting up KDE is the lack of sound. This is also normal. Go to KAmix and you will see the sound is muted. If this wont work for you, go to your KDE Control Panel and in the sound settings, change from Autodetect to ALSA.


For NVIDIA closed source driver users:
Now you are ready for the new NVIDIA video drivers.
[code:1]# init 3
# sh 'follow all the steps
# sax2 -m 0=nvidia 'dont bother about setting 3d acceleration. it will work anyway
# init 5[/code:1]

I think thats all for now. If i forgot something, shout. Any input apreciated. :D

Good luck and may the force be with you.[/list][/list][/list]


Wednesday, March 3rd 2004, 7:23am

netods what can I say apart from a very big thank you, I like your point of disclaim and all the other points. I can tell you that I would never hold any one responsible if soothing went wrong specially if someone like you is simple trying to help. Anyway I have a test system where I do all my messing around with and I will be upgrading that system first a couple of times before I tough my main system.
Once again thank you very much for your instructions regardless if I have problems or not.

Kind Regards :D
The Best Games are for Download @ GCCLINUX


Wednesday, March 3rd 2004, 9:48am

No problemo...

No problemo. Glad its useful to someone :D .
The disclaim part is mostly a big red sign to warn you that you are about to mess with the heart of your system. And also Novell Suse Inc. will simply refuse to offer you support once you changed the kernel :wink: .
Needing help, im always at #suse in .