Hi. There is a new kernelupdate on YOU. I'm in doubt if it will do wrong to my running kernel: uname -a Linux lajka3 2.6.11.4-21.8-default #1 Tue Jul 19 12:42:37 UTC 2005 i686 athlon i386 GNU/Linux Please have a look at: http://www.urbakken.dk/kernelupdate.png. Erik Jakobsen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-09-03 at 09:37 +0200, Erik Jakobsen wrote:
There is a new kernelupdate on YOU. I'm in doubt if it will do wrong to my running kernel:
kernel-default-2.6.11.4-21.9.i586.rpm (suse 9.3) )broke sound here: nimrodel:~ # rcalsasound start Starting sound driver: intel8x0FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.11.4-21.9-default/kernel/sound/pci/snd-intel8x0.ko): Unknown symbol in module, or unknown parameter (see dmesg) tailf /var/log/kernel: Sep 3 14:39:54 nimrodel kernel: snd_intel8x0: Unknown parameter `joystick' Sep 3 14:39:54 nimrodel kernel: load_module: err 0xfffffffe (dont worry) Despite that "dont worry" sound doesn't work :-/ /etc/modprobe.d/sound: options snd-intel8x0 enable=1 index=0 joystick=0 (had joystick=1, changed to 0, no efect). nimrodel:~ # uname -a Linux nimrodel 2.6.11.4-21.9-default #1 Fri Aug 19 11:58:59 UTC 2005 i686 i686 i386 GNU/Linux nimrodel:~ # cat /proc/version Linux version 2.6.11.4-21.9-default (geeko@buildhost) (gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)) #1 Fri Aug 19 11:58:59 UTC 2005 sound modules are default suse version plus YOU updates only. I will have to revert to kernel-default-2.6.11.4-21.8.i586.rpm :-( - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDGaKRtTMYHG2NR9URAtq3AJwLCdioKRdP71t/pvecg3hPYmFiZQCfSpft iQTi8XbWViKZiajOmJq7QDw= =S+Ii -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-09-03 at 15:17 +0200, I wrote:
kernel-default-2.6.11.4-21.9.i586.rpm (suse 9.3) )broke sound here:
Forget it, it was my fault. It is not broken. It was not a missing symbol, but an unknown parameter, that chose to be unknown after this updated. Solved. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDGk6PtTMYHG2NR9URAsKIAJ0X+1Q0idDTQOLaCDFpyf1/iqcLowCcCg50 1Rrwlg2gKux3G4xhf4tDzOU= =F33v -----END PGP SIGNATURE-----
On Saturday 03 September 2005 2:37 am, Erik Jakobsen wrote:
Hi.
There is a new kernelupdate on YOU. I'm in doubt if it will do wrong to my running kernel:
uname -a Linux lajka3 2.6.11.4-21.8-default #1 Tue Jul 19 12:42:37 UTC 2005 i686 athlon i386 GNU/Linux
Please have a look at:
http://www.urbakken.dk/kernelupdate.png.
Erik Jakobsen
Join the both the SUSE Security (suse-security@suse.com) and the SUSE Security Announce list (suse-security-announce@suse.com). You'll get more details about the updates so you can read through what the changes are. And if you wait a few hours or days you may see if any problems get reported about the newer kernels. Don't forget to reboot after a kernel update.!.! What is your concern anyway? You MUST specify what your concern is so that someone may be able to address it. My crystal ball is still in the repair shop, just never seems to work like I expect it to. Your running kernel is running. Updating will replace it so that WHEN you reboot you'll be running on the newer kernel. Until you reboot nothing will happen to your current kernel. The newer kernel can't do anything until you actually boot to it. You may always rename or copy your running kernel (currently booted) to something/somewhere else as a fall-back if the new kernel doesn't perform correctly for you, create another grub/lilo entry for it, etc. Stan
Stan Glasoe wrote:
On Saturday 03 September 2005 2:37 am, Erik Jakobsen wrote:
Hi.
There is a new kernelupdate on YOU. I'm in doubt if it will do wrong to my running kernel:
uname -a Linux lajka3 2.6.11.4-21.8-default #1 Tue Jul 19 12:42:37 UTC 2005 i686 athlon i386 GNU/Linux
Please have a look at:
http://www.urbakken.dk/kernelupdate.png.
Erik Jakobsen
Join the both the SUSE Security (suse-security@suse.com) and the SUSE Security Announce list (suse-security-announce@suse.com). You'll get more details about the updates so you can read through what the changes are. And if you wait a few hours or days you may see if any problems get reported about the newer kernels. Don't forget to reboot after a kernel update.!.!
Ok Stan.
What is your concern anyway? You MUST specify what your concern is so that someone may be able to address it. My crystal ball is still in the repair shop, just never seems to work like I expect it to.
A bit rude I think you are here. I just wanted to know what could happen if I choosed to update. Nothing especially mystery about that, and hope your crystal ball will be back soon again. For my asking it wasn't necessary.
Your running kernel is running. Updating will replace it so that WHEN you reboot you'll be running on the newer kernel. Until you reboot nothing will happen to your current kernel. The newer kernel can't do anything until you actually boot to it. You may always rename or copy your running kernel (currently booted) to something/somewhere else as a fall-back if the new kernel doesn't perform correctly for you, create another grub/lilo entry for it, etc.
I use grub
Stan
Erik
Stan Glasoe wrote:
Your running kernel is running. Updating will replace it so that WHEN you reboot you'll be running on the newer kernel. Until you reboot nothing will happen to your current kernel. The newer kernel can't do anything until you actually boot to it. Of course, if you try to load a module after updating the kernel, but before rebooting, all bets *may* be off :-)
participants (4)
-
Carlos E. R. -
Darryl Gregorash -
Erik Jakobsen -
Stan Glasoe