I’ve a pretty old but very usable computer with the following configuration:
AMD 64 Processor
1024 megabytes memory
2 120 gigabyte harddisc
Asus K8V Deluxe with onboard sound and ethernet controller
NVidia FX5200 video using generic (Open Source) ‘nv’ driver
The plain vanilla install brought me kernel 18.104.22.168 without hiccups. Two week ago I got confronted with the kernel update to kernel 22.214.171.124 also without a hitch.
Now I’m confronted with the update to 126.96.36.199 and also without any problems.
Do you also have luck or are there some hiccups to be ironed out.
–In order to beat Microsoft the OpenSource community must stand strong…
I performed the update on my test PC, and old athlon-1100 with basic nvidia (I use the openGL drivers), no wireless (only wired), no virtual box, basic sound hardware (VIA8233 with ALC650D) and a Phillips web cam.
As always, before the kernel update, I backed up my /boot/grub/menu.lst file, after the kernel update, BEFORE rebooting, I checked the updated /boot/grub/menu.lst file (updated by the kernel install) against the backup file that I created. The new updated file looked great. So I rebooted, with no problem.
Graphics, audio, wired internet, and webcam worked with no problem.
For those curious as to what the update brings from 188.8.131.52 to 184.108.40.206:
and when going from 220.127.116.11 to 18.104.22.168
wOOt This is very interesting for the more technically skilled Linux users, since the kernel is the most important part of Linux. I hope that for less technically skilled Linux fans the release-notes will also come in a more friendly way like ‘Crash problem hardware <vendor> <type> corrected.’ without all the C stuff, so that everyone can know why the updates are means for.
Performed the update today, and all went well.
Of course I had to reorganize everything in the boot loader, renaming and all, but besides that, it went very smoothly. Changing the Boot loader options isn’t really a big deal for me, even when there are updates often because I only have OpenSUSE 11.0, Windows XP Pro SP3, and Failsafe, so I just have to rename them and organize them into the order I want. So, all-in-all, it was very easy to install and update the kernel.
I’m sure if you surf hard enough, you can find all sorts of interesting links …
If moderators are allowed to have fun :rolleyes: then to wet your appetite here are some links, with the first for each kernel being a summary, and the second a free-for all discussion:
22.214.171.124 Linux 126.96.36.199 [LWN.net] and discussion: Stable kernel 188.8.131.52 [LWN.net]
184.108.40.206 Linux 220.127.116.11 [LWN.net] and discussion: Stable kernel 18.104.22.168 [LWN.net]
22.214.171.124 Linux 126.96.36.199 [LWN.net] and discussion: Stable kernel 188.8.131.52 [LWN.net]
184.108.40.206 Linux 220.127.116.11 [LWN.net] and discussion: I didn’t see a discussion page
18.104.22.168 Linux 22.214.171.124 [LWN.net] and discussion: Stable kernel 126.96.36.199 released [LWN.net]
188.8.131.52 Linux 184.108.40.206 [LWN.net] and discussion: Stable kernel 220.127.116.11 [LWN.net] and also “Stable” kernel 18.104.22.168 [LWN.net]](http://lwn.net/Articles/285782/)
To my surprise i’ve haven’t had a hiccup with the kernel update which is really nice cause in 10.3 every kernel update i had a hiccup cause when i installed OS i would remove my sata drive which has windows on it then just add it to grub after install and every kernel update would break and would have manually fix it but OS 11 not one problem
Another “after the fact” way to see what changes have been done to the kernel, simply open an xterm/konsole and type:
rpm -q --changelog <your-kernel>
For example, I type on my PC
rpm -q --changelog kernel-pae > kernel-changelog.txt
and with my favourite text editor open up the file “kernel-changelog.txt” and peruse the changes.
Surely, I’ll give this command a try. This is what I’ve searched for.
I’ve issued the following command ‘rpm -q --changelog kernel-default-22.214.171.124-0.1 >results.txt’ and I’ve read the generated text file easily in a text-editor. What a whopping changelog! But wait, the first issue is dated at 3 july 2006.