[opensuse] Kernel Update questions
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and being that this is only the second time that I have updated my Kernel on my system I don't know what is normal. I have openSUSE 10.2 on my system and the first time I updated my Kernel everything was straight forward and I had no questions. This time how ever grub no longer lists openSUSE 10.2 as a boot option, this time it lists this: openSUSE 10.2 (XEN) Windows Kernel-2.6.18.8-0.1-xen Kernel-2.6.18.8-0.1-default My fist question is: Should it be listing my Kernel instead of listing openSUSE, and if so then why didn't it do it on the last Kernel update? My second question is: Why is it still listing the old openSUSE 10.2 xen while there is a Kernel option for xen? I think you for your time, and I hope that some one knows what I am talking about and is able to give me some answers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 08 March 2007 19:58, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and being that this is only the second time that I have updated my Kernel on my system I don't know what is normal. I have openSUSE 10.2 on my system and the first time I updated my Kernel everything was straight forward and I had no questions. This time how ever grub no longer lists openSUSE 10.2 as a boot option, this time it lists this: openSUSE 10.2 (XEN) Windows Kernel-2.6.18.8-0.1-xen Kernel-2.6.18.8-0.1-default
My fist question is: Should it be listing my Kernel instead of listing openSUSE, and if so then why didn't it do it on the last Kernel update?
My second question is: Why is it still listing the old openSUSE 10.2 xen while there is a Kernel option for xen?
I think you for your time, and I hope that some one knows what I am talking about and is able to give me some answers.
Hi Adam, I guess, old entries are just fallback option for users that need to update ATI or nVidia video drivers. Otherwise they will have system without graphic environment and no option to ask somebody, what to do. -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Mar 08, 2007 at 08:58:14PM -0500, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and being that this is only the second time that I have updated my Kernel on my system I don't know what is normal. I have openSUSE 10.2 on my system and the first time I updated my Kernel everything was straight forward and I had no questions. This time how ever grub no longer lists openSUSE 10.2 as a boot option, this time it lists this: openSUSE 10.2 (XEN) Windows Kernel-2.6.18.8-0.1-xen Kernel-2.6.18.8-0.1-default
My fist question is: Should it be listing my Kernel instead of listing openSUSE, and if so then why didn't it do it on the last Kernel update?
My second question is: Why is it still listing the old openSUSE 10.2 xen while there is a Kernel option for xen?
I think you for your time, and I hope that some one knows what I am talking about and is able to give me some answers.
What kernel did you install before? 2.6.18.8-0.1-default is the correct one if you are not using XEN. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-03-09 at 07:45 +0100, Marcus Meissner wrote:
2.6.18.8-0.1-default is the correct one if you are not using XEN.
Shouldn't it be plain "linux", with "vmlinuz" being a symlink to the new kernel? I understood that was the way it going to be from now on. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF8pjKtTMYHG2NR9URAt8vAJ92tGsEuf23QoEv87U60gGUjFbWdwCeNKtc 702JxahZ5wwHj066erYo0h0= =J6ux -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 09 Mar 2007, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and being that this is only the second time that I have updated my Kernel on my system I don't know what is normal. I have openSUSE 10.2 on my system and the first time I updated my Kernel everything was straight forward and I had no questions. This time how ever grub no longer lists openSUSE 10.2 as a boot option, this time it lists this: openSUSE 10.2 (XEN) Windows Kernel-2.6.18.8-0.1-xen Kernel-2.6.18.8-0.1-default
My fist question is: Should it be listing my Kernel instead of listing openSUSE, and if so then why didn't it do it on the last Kernel update?
My second question is: Why is it still listing the old openSUSE 10.2 xen while there is a Kernel option for xen?
I think you for your time, and I hope that some one knows what I am talking about and is able to give me some answers.
Mine has done the same. It now shows openSuse 10.1 on the first line and the the Kernel version on the second - the kernal patch has really messed up Grub as I have to select the second line for it to work. And why has the screen reverted to 10.1 when it was a clean install of 10.2 on my machine. Someone somewhere is not testing their patches very well. Hopefully another patch will be coming our way to fix this little problem. regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 March 2007 06:29, ianseeks wrote:
On Friday 09 Mar 2007, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and
Mine has done the same. It now shows openSuse 10.1 on the first line and the the Kernel version on the second - the kernal patch has really messed up Grub as I have to select the second line for it to work. And why has the screen reverted to 10.1 when it was a clean install of 10.2 on my machine. Someone somewhere is not testing their patches very well. Hopefully another patch will be coming our way to fix this little problem.
More or less the same situation here. My first line "OpenSuse 10.2 has been removed and a last entrance and default a line which starts with Kernel etc. is added. The Failsafe possibility has been removed. The new entrance does not have the line ###Don't change this comment..... And as leftover from this kernel update I find four .gz files in /boot The last kernel is nowhere to be found in /boot and if something breaks after the kernel updatetheir is no alternative boot. -- +=========================================+ | Powered by openSUSE 10.2 (i586) Kernel: 2.6.18.8-0.1-default | KDE: 3.5.5 "release 45.2" | 12:44pm up 14:56, 2 users, load average: 1.78, 0.88, 0.75 | +=========================================+ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Mar 10, 2007 at 12:59:59PM +0700, Constant Brouerius van Nidek wrote:
On Saturday 10 March 2007 06:29, ianseeks wrote:
On Friday 09 Mar 2007, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and
Mine has done the same. It now shows openSuse 10.1 on the first line and the the Kernel version on the second - the kernal patch has really messed up Grub as I have to select the second line for it to work. And why has the screen reverted to 10.1 when it was a clean install of 10.2 on my machine. Someone somewhere is not testing their patches very well. Hopefully another patch will be coming our way to fix this little problem.
More or less the same situation here. My first line "OpenSuse 10.2 has been removed and a last entrance and default a line which starts with Kernel etc. is added. The Failsafe possibility has been removed. The new entrance does not have the line ###Don't change this comment..... And as leftover from this kernel update I find four .gz files in /boot The last kernel is nowhere to be found in /boot and if something breaks after the kernel updatetheir is no alternative boot.
The bug is number 252911. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 March 2007 06:46, Marcus Meissner wrote:
On Sat, Mar 10, 2007 at 12:59:59PM +0700, Constant Brouerius van Nidek wrote:
On Saturday 10 March 2007 06:29, ianseeks wrote:
On Friday 09 Mar 2007, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update,
The bug is number 252911.
Ciao, Marcus
Thanks to this bug I have a completely broken system, with no working options in menu.lst I can only get into the system by booting off the install disk. The menu.lst that was written out after the update is basically blank, with entries that have no information (no kernel, root, etc.). This persists even if I go to yast-bootloader and ask it to propose a new configuration. I tried falling back to the install kernel, but have the same problem with a broken menu.lst. Does anyone know what package is used to compose and write out the menu.lst file? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Mar 11, 2007 at 02:04:13PM -0400, Mike wrote:
On Saturday 10 March 2007 06:46, Marcus Meissner wrote:
On Sat, Mar 10, 2007 at 12:59:59PM +0700, Constant Brouerius van Nidek wrote:
On Saturday 10 March 2007 06:29, ianseeks wrote:
On Friday 09 Mar 2007, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update,
The bug is number 252911.
Ciao, Marcus
Thanks to this bug I have a completely broken system, with no working options in menu.lst I can only get into the system by booting off the install disk.
The menu.lst that was written out after the update is basically blank, with entries that have no information (no kernel, root, etc.). This persists even if I go to yast-bootloader and ask it to propose a new configuration.
This is something we have not yet seen this bug do. Are /boot/vmlinuz and /boot/initrd still there?
I tried falling back to the install kernel, but have the same problem with a broken menu.lst. Does anyone know what package is used to compose and write out the menu.lst file?
perl-Bootloader CIao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/11/2007 04:19 PM somebody named Marcus Meissner wrote:
On Sun, Mar 11, 2007 at 02:04:13PM -0400, Mike wrote:
On Saturday 10 March 2007 06:46, Marcus Meissner wrote:
....
The menu.lst that was written out after the update is basically blank, with entries that have no information (no kernel, root, etc.). This persists even if I go to yast-bootloader and ask it to propose a new configuration.
This is something we have not yet seen this bug do.
Are /boot/vmlinuz and /boot/initrd still there?
I tried falling back to the install kernel, but have the same problem with a broken menu.lst. Does anyone know what package is used to compose and write out the menu.lst file?
perl-Bootloader
This would seem to be a good argument for the kernel upgrade to create sufficient backups so that the previous kernel could be used. Better yet would be to put the previous kernel into the grub/lilo menu as a second boot option. -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 11 March 2007 16:19, Marcus Meissner wrote:
On Sun, Mar 11, 2007 at 02:04:13PM -0400, Mike wrote:
The menu.lst that was written out after the update is basically blank, with entries that have no information (no kernel, root, etc.). This persists even if I go to yast-bootloader and ask it to propose a new configuration.
This is something we have not yet seen this bug do.
Are /boot/vmlinuz and /boot/initrd still there?
After looking over other forums and people dealing with the bug, I believe my particular scenario is because my x86_64 system is using a disk array. I currently have it booting with this manually edited menu.lst: title openSUSE 10.2 kernel (hd0,4)/vmlinuz-2.6.18.8-0.1-default root=/dev/mapper/isw_ddfafhegd_ARRAY_part7 initrd (hd0,4)/initrd-2.6.18.8-0.1-default If I just take the "propose new configuration" result I get the following: ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader (hd0,1)+1 ###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.2 ###Don't change this comment - YaST2 identifier: Original name: 2.6.18.8-0.1-default### title 2.6.18.8-0.1-default initrd (hd0,4)/initrd-2.6.18.8-0.1-default Which doesn't work at all. One thing that is interesting is that the boot loader gui comes up with a number of options in the gui that do not get written to menu.lst. Now my next problem is that cpu frequency scaling has stopped working since the kernel update. I don't know if there was supposed to be some kernel param set that I have lost because of the bug, or if the new kernel doesn't work right on my core 2 duo. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Mar 11, 2007 at 05:35:28PM -0400, Mike wrote:
On Sunday 11 March 2007 16:19, Marcus Meissner wrote:
On Sun, Mar 11, 2007 at 02:04:13PM -0400, Mike wrote:
The menu.lst that was written out after the update is basically blank, with entries that have no information (no kernel, root, etc.). This persists even if I go to yast-bootloader and ask it to propose a new configuration.
This is something we have not yet seen this bug do.
Are /boot/vmlinuz and /boot/initrd still there?
After looking over other forums and people dealing with the bug, I believe my particular scenario is because my x86_64 system is using a disk array. I currently have it booting with this manually edited menu.lst:
title openSUSE 10.2 kernel (hd0,4)/vmlinuz-2.6.18.8-0.1-default root=/dev/mapper/isw_ddfafhegd_ARRAY_part7 initrd (hd0,4)/initrd-2.6.18.8-0.1-default
Was this actually two lines? or just one, wrapped by your mailer? Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 09 Mar 2007, Adam Jimerson wrote:
I have a couple of questions about the Kernel 2.6.18.8-0.1 update, and being that this is only the second time that I have updated my Kernel on my system I don't know what is normal. I have openSUSE 10.2 on my system and the first time I updated my Kernel everything was straight forward and I had no questions. This time how ever grub no longer lists openSUSE 10.2 as a boot option, this time it lists this: openSUSE 10.2 (XEN) Windows Kernel-2.6.18.8-0.1-xen Kernel-2.6.18.8-0.1-default
My fist question is: Should it be listing my Kernel instead of listing openSUSE, and if so then why didn't it do it on the last Kernel update?
My second question is: Why is it still listing the old openSUSE 10.2 xen while there is a Kernel option for xen?
Mine did the same. It listed Kernel-2.6.18.8-0.1-default. OK I guess, I could change it in Yast >bootloader, which I did, but now I have no Failsafe. Guess I could reconstruct that in menu1st, but that is not
On Friday 09 March 2007 18:29, ianseeks wrote: the point. Hope somebody takes a look at this. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Adam Jimerson -
Bob S -
Carlos E. R. -
Constant Brouerius van Nidek -
ianseeks -
ken -
Marcus Meissner -
Mike -
Rajko M.