[opensuse] Kernel update for 10.3
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system. Currently have bug number 331662 open but there has not been any activity on it. I am currently forced to boot to the repair part of the DVD (which fails) and then select boot installed system in order for the system to come up. Since the boot kernel I am currently using actually loads from the DVD how can I proceed with this update? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/11/2007 03:34 AM, Kenneth Schneider wrote:
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system. Currently have bug number 331662 open but there has not been any activity on it. I am currently forced to boot to the repair part of the DVD (which fails) and then select boot installed system in order for the system to come up. Since the boot kernel I am currently using actually loads from the DVD how can I proceed with this update?
Though the install GUI has been a great way to install and setup, when it breaks, you can always fall back to the CLI for more fine control and better feedback from the commands. Since it sounds like you have a boot problem, what is the problem and get that fixed so you can update your kernel with confidence. Did grub get installed? Where? Is this an upgrade or new install (drive devices changed)? Though I think booting the installed system would boot the system kernel (what does uname -a tell you), meaning you can update it OK, it would be best to get it all working properly. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sri, 2007-10-10 at 15:34 -0400, Kenneth Schneider wrote:
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system.
That concerns me either. I didn't know that SUSE updates kernel packages rather then install new packages and keeps the old ones on the system. Is it possible to roll back the old one, or something, in case we really end up with a non booting system? Fortunately, I didn't end up with a non booting system today, and nVidia drivers works either, but you never know when that might happen. Cheers! -- Igor Jagec
On Oct 11 2007 09:46, Igor Jagec wrote:
On Sri, 2007-10-10 at 15:34 -0400, Kenneth Schneider wrote:
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system.
That concerns me either. I didn't know that SUSE updates kernel packages rather then install new packages and keeps the old ones on the system.
Is it possible to roll back the old one, or something, in case we really end up with a non booting system?
It is as simple as using rpm -i over rpm -U. I do that manually since package managers generally use -U.
Fortunately, I didn't end up with a non booting system today, and nVidia drivers works either, but you never know when that might happen. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Igor Jagec wrote:
On Sri, 2007-10-10 at 15:34 -0400, Kenneth Schneider wrote:
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system.
That concerns me either. I didn't know that SUSE updates kernel packages rather then install new packages and keeps the old ones on the system.
Is it possible to roll back the old one, or something, in case we really end up with a non booting system?
Fortunately, I didn't end up with a non booting system today, and nVidia drivers works either, but you never know when that might happen.
Cheers!
You will be happy to hear of two improvements with the new kernel: 1) It works! a) drivers that had stopped working for disk controllers now compile and can load b) it properly 'mkinitrd' to incorporate user supplied module into boot image c) it did not corrupt the MBR when installed as an update like .31 did for me d) the HDA sound support works - I can change volume without loss of sound 2) It leaves a copy of the previous kernel in place. a) it properly modifies GRUB adding itself and leaving prior boot kernel pointer b) it was compatible with a MD raid installation Finally, I can stop looking for an apparantly non-existant copy of version -25 which was the last version that worked with my scsi hardware raid controller. The sound still works and all issues I had previously with the kernel are gone. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-10-11 at 04:22 -0400, Richard Creighton wrote:
Igor Jagec wrote:
On Sri, 2007-10-10 at 15:34 -0400, Kenneth Schneider wrote:
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system.
That concerns me either. I didn't know that SUSE updates kernel packages rather then install new packages and keeps the old ones on the system.
Is it possible to roll back the old one, or something, in case we really end up with a non booting system?
Fortunately, I didn't end up with a non booting system today, and nVidia drivers works either, but you never know when that might happen.
Cheers!
You will be happy to hear of two improvements with the new kernel:
1) It works! a) drivers that had stopped working for disk controllers now compile and can load b) it properly 'mkinitrd' to incorporate user supplied module into boot image c) it did not corrupt the MBR when installed as an update like .31 did for me d) the HDA sound support works - I can change volume without loss of sound
2) It leaves a copy of the previous kernel in place.
You might want to re-check this. I just upgraded to the new kernel and it deleted the old one. The link to the "old kernel" actually points to the new one. The new one just uses the full name instead of the link. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kenneth Schneider wrote:
On Thu, 2007-10-11 at 04:22 -0400, Richard Creighton wrote:
Igor Jagec wrote:
On Sri, 2007-10-10 at 15:34 -0400, Kenneth Schneider wrote:
Noticed kernel update for 10.3 386 system and I am concerned that I will end up with a NON-booting system.
That concerns me either. I didn't know that SUSE updates kernel packages rather then install new packages and keeps the old ones on the system.
Is it possible to roll back the old one, or something, in case we really end up with a non booting system?
Fortunately, I didn't end up with a non booting system today, and nVidia drivers works either, but you never know when that might happen.
Cheers!
You will be happy to hear of two improvements with the new kernel:
1) It works! a) drivers that had stopped working for disk controllers now compile and can load b) it properly 'mkinitrd' to incorporate user supplied module into boot image c) it did not corrupt the MBR when installed as an update like .31 did for me d) the HDA sound support works - I can change volume without loss of sound
2) It leaves a copy of the previous kernel in place.
You might want to re-check this. I just upgraded to the new kernel and it deleted the old one. The link to the "old kernel" actually points to the new one. The new one just uses the full name instead of the link.
That is very strange...I have both the new kernel and the old .31 kernel in /boot and my /grub menu.1st had 4 entries, 2 of which pointed to the new kernel and 2 pointed to the old .31 kernel. I am not aware that I did anything special. OK, strike number 2 above unless you get some voodoo witchcraft luck working. At least the controller driver, and I discovered, VMWare love the new kernel, as does my MB which had been resisting all efforts to be tamed. Every kernel so far had something that broke something until now. I'll try and see if I accidentally did something to keep my old kernel, but I rebooted with .31 before I answered this to ensure it still was really there, and it did and just to be sure, I am back on the new kernel. Even the /lib entries for the .31 kernel are intact....go figure. Maybe one of the openSuSE kernel guys will pipe in and tell us if this was a fluke or was by design. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-10-11 at 16:35 -0400, Richard Creighton wrote:
Kenneth Schneider wrote:
You might want to re-check this. I just upgraded to the new kernel and it deleted the old one. The link to the "old kernel" actually points to the new one. The new one just uses the full name instead of the link.
That is very strange...I have both the new kernel and the old .31 kernel in /boot and my /grub menu.1st had 4 entries, 2 of which pointed to the new kernel and 2 pointed to the old .31 kernel. I am not aware that I did anything special. OK, strike number 2 above unless you get some voodoo witchcraft luck working. At least the controller driver, and I discovered, VMWare love the new kernel, as does my MB which had been resisting all efforts to be tamed. Every kernel so far had something that broke something until now. I'll try and see if I accidentally did something to keep my old kernel, but I rebooted with .31 before I answered this to ensure it still was really there, and it did and just to be sure, I am back on the new kernel. Even the /lib entries for the .31 kernel are intact....go figure. Maybe one of the openSuSE kernel guys will pipe in and tell us if this was a fluke or was by design.
I don't doubt you at all, it could be something I did. This is the contents of /boot: -rw-r--r-- 1 root root 842872 2007-10-08 07:46 System.map-2.6.22.9-0.4-default -rw------- 1 root root 512 2007-10-06 18:13 backup_mbr lrwxrwxrwx 1 root root 1 2007-10-06 16:33 boot -> . -rw-r--r-- 1 root root 80417 2007-10-08 07:50 config-2.6.22.9-0.4-default drwxr-xr-x 2 root root 1024 2007-10-11 10:04 grub lrwxrwxrwx 1 root root 27 2007-10-11 10:04 initrd -> initrd-2.6.22.9-0.4-default -rw-r--r-- 1 root root 4315748 2007-10-11 10:04 initrd-2.6.22.9-0.4-default drwx------ 2 root root 12288 2007-10-06 16:19 lost+found -rw-r--r-- 1 root root 389120 2007-10-10 23:58 message -rw-r--r-- 1 root root 138182 2007-10-08 08:29 symsets-2.6.22.9-0.4-bigsmp.tar.gz -rw-r--r-- 1 root root 100801 2007-10-08 08:16 symsets-2.6.22.9-0.4-debug.tar.gz -rw-r--r-- 1 root root 138222 2007-10-08 07:52 symsets-2.6.22.9-0.4-default.tar.gz -rw-r--r-- 1 root root 136527 2007-10-08 08:23 symsets-2.6.22.9-0.4-xen.tar.gz -rw-r--r-- 1 root root 136574 2007-10-08 08:25 symsets-2.6.22.9-0.4-xenpae.tar.gz -rw-r--r-- 1 root root 400506 2007-10-08 07:52 symtypes-2.6.22.9-0.4-default.gz -rw-r--r-- 1 root root 116261 2007-10-08 07:51 symvers-2.6.22.9-0.4-default.gz -rwxr-xr-x 1 root root 2147342 2007-10-08 07:50 vmlinux-2.6.22.9-0.4-default.gz lrwxrwxrwx 1 root root 28 2007-10-11 10:04 vmlinuz -> vmlinuz-2.6.22.9-0.4-default -rw-r--r-- 1 root root 1593788 2007-10-08 07:46 vmlinuz-2.6.22.9-0.4-default You can see that the only kernel I have is 2.6.22.9-0.4 and my menu.lst file contains: # Modified by YaST2. Last modification on Thu Oct 11 10:04:43 EDT 2007 default 0 timeout 8 gfxmenu (hd0,0)/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 - 2.6.22.9-0.4 root (hd0,0) kernel /vmlinuz-2.6.22.9-0.4-default root=/dev/disk/by-id/cciss-3600508b100104b44414f365744360006-part3 vga=0x31a resume=/dev/mapper/lsi_jhicccaiaa_part2 splash=silent showopts initrd /initrd-2.6.22.9-0.4-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 - 2.6.22.9-0.4 root (hd0,0) kernel /vmlinuz-2.6.22.9-0.4-default root=/dev/disk/by-id/cciss-3600508b100104b44414f365744360006-part3 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /initrd-2.6.22.9-0.4-default ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd0,0) kernel /vmlinuz root=/dev/disk/by-id/cciss-3600508b100104b44414f365744360006-part3 vga=0x31a resume=/dev/mapper/lsi_jhicccaiaa_part2 splash=silent showopts initrd /initrd ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd0,0) kernel /vmlinuz root=/dev/disk/by-id/cciss-3600508b100104b44414f365744360006-part3 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /initrd The entry for openSUSE 10.3 (the old one) points to the vmlinuz entry which is nothing more a link to vmlinuz-2.6.22.9-0.4-default. Go figure. I could go and install the original kernel along side the latest and have both, but since I'm not having problems with the latest I'll let it go for now. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Čet, 2007-10-11 at 17:08 -0400, Kenneth Schneider wrote:
I don't doubt you at all, it could be something I did.
Yep, 'zypper update' ;) I think we should file that to Novell's Bugzilla.
You can see that the only kernel I have is 2.6.22.9-0.4
Same here: # ll /boot total 9688 -rw------- 1 root root 512 2007-10-05 14:47 backup_mbr lrwxrwxrwx 1 root root 1 2007-10-05 14:28 boot -> . -rw-r--r-- 1 root root 80417 2007-10-08 13:50 config-2.6.22.9-0.4-default drwxr-xr-x 2 root root 1024 2007-10-11 08:52 grub lrwxrwxrwx 1 root root 27 2007-10-11 08:52 initrd -> initrd-2.6.22.9-0.4-default -rw-r--r-- 1 root root 4140213 2007-10-11 08:52 initrd-2.6.22.9-0.4-default drwx------ 2 root root 12288 2007-10-05 14:22 lost+found -rw-r--r-- 1 root root 391168 2007-10-05 14:47 message -rw-r--r-- 1 root root 138222 2007-10-08 13:52 symsets-2.6.22.9-0.4-default.tar.gz -rw-r--r-- 1 root root 400506 2007-10-08 13:52 symtypes-2.6.22.9-0.4-default.gz -rw-r--r-- 1 root root 116261 2007-10-08 13:51 symvers-2.6.22.9-0.4-default.gz -rw-r--r-- 1 root root 842872 2007-10-08 13:46 System.map-2.6.22.9-0.4-default -rwxr-xr-x 1 root root 2147342 2007-10-08 13:50 vmlinux-2.6.22.9-0.4-default.gz lrwxrwxrwx 1 root root 28 2007-10-11 08:52 vmlinuz -> vmlinuz-2.6.22.9-0.4-default -rw-r--r-- 1 root root 1593788 2007-10-08 13:46 vmlinuz-2.6.22.9-0.4-default Cheers! -- Igor Jagec
On Čet, 2007-10-11 at 16:35 -0400, Richard Creighton wrote:
You might want to re-check this. I just upgraded to the new kernel and it deleted the old one. The link to the "old kernel" actually points to the new one. The new one just uses the full name instead of the
Kenneth Schneider wrote: link. That is very strange...I have both the new kernel and the old .31 kernel in /boot and my /grub menu.1st had 4 entries, 2 of which pointed to the new kernel and 2 pointed to the old .31 kernel. I am not aware that I did anything special.
I don't know what actually caused different behavior for us, but I just did the 'zypper update' in command line. It should do the same job as Update applets. Or it shouldn't? I don't know, maybe I should file it to Novell's bugzilla. Cheers! -- Igor Jagec
Kenneth Schneider wrote:
<snip>
You might want to re-check this. I just upgraded to the new kernel and it deleted the old one. The link to the "old kernel" actually points to the new one. The new one just uses the full name instead of the link.
I figured out what happened ... and you are correct. I had installed a copy of .25 from command line earlier so I had 2 kernels when the update came in, .25 and .31. The update erased .25 but left .31 then menu.1st was updated to reflect the contents of /boot correctly. Interesting bug that I will exploit to ensure I always have a backup kernel to go to when updates come in. I'm going to try and repeat the experiment. The trick apparantly is to NOT let Yast do the rpm install of one of the kernel rpms so the erasure doesn't occur, then you have 2 kernels in /boot. Dunno why they don't do it that way by design? Thanks for pointing out the error, indirectly the bug and an idea for a useful exploit that may come in handy next time we get a kernel with an oops built in as an update. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 11 October 2007 07:01:08 pm Richard Creighton wrote:
Thanks for pointing out the error, indirectly the bug and an idea for a useful exploit that may come in handy next time we get a kernel with an oops built in as an update.
I would not rely on bug. It will be corrected as soon as someone report it. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Thursday 11 October 2007 07:01:08 pm Richard Creighton wrote:
Thanks for pointing out the error, indirectly the bug and an idea for a useful exploit that may come in handy next time we get a kernel with an oops built in as an update.
I would not rely on bug. It will be corrected as soon as someone report it.
Oh, I've learned not to count on anything, but I will keep an old kernel around as a 'sacrificial lamb' so when I see a kernel update available, I can offer it to the Yast T-Rex monster instead of the current, functioning, kernel. If T-Rex eats both, well, I'm no worse off than now and if it eats the sacrificial lamb instead of the good kernel, I will have a backup for a while longer. Hopefully it will become a 'feature' rather than a bug. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Pet, 2007-10-12 at 02:38 -0500, Rajko M. wrote:
On Thursday 11 October 2007 07:01:08 pm Richard Creighton wrote:
Thanks for pointing out the error, indirectly the bug and an idea for a useful exploit that may come in handy next time we get a kernel with an oops built in as an update. I would not rely on bug. It will be corrected as soon as someone report it.
I have just asked on Factory mailing list if that really is a bug. If so, I'm gonna report it, if someone else doesn't :) Cheers! -- Igor Jagec
On Pet, 2007-10-12 at 02:38 -0500, Rajko M. wrote:
On Thursday 11 October 2007 07:01:08 pm Richard Creighton wrote:
Thanks for pointing out the error, indirectly the bug and an idea for a useful exploit that may come in handy next time we get a kernel with an oops built in as an update. I would not rely on bug. It will be corrected as soon as someone report it.
...and I was told on Factory mailing list that is a bug, but not the Zypper or Kernel bug, but the bootloader handling bug. Anyway, I've just report it to Novell's Bugzilla (#333392). Cheers! -- Igor Jagec
On Friday 12 October 2007 08:22:57 am Igor Jagec wrote:
333392
Resolved, duplicate of: https://bugzilla.novell.com/show_bug.cgi?id=332933 -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- "Richard Creighton"
participants (7)
-
Igor Jagec -
Jan Engelhardt -
Joe Morris (NTM) -
Kenneth Schneider -
L. Mark Stone -
Rajko M. -
Richard Creighton