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