|
Bugzilla – Full Text Bug Listing |
| Summary: | bootloader mangles kernel paths ... | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Michael Meeks <mmeeks> |
| Component: | YaST2 | Assignee: | Jozef Uhliarik <juhliarik> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast log | ||
using yast2-qt under Gnome FWIW: rpm -q --changelog yast2-qt | head * Wed Feb 27 2008 sh@suse.de - Removed obsolete Unicode fonts (now in separate pkg gnu-unifonts) - V 2.16.31 Created attachment 199987 [details]
yast log
Hi Michael, I tried reproduce your problem with bootloader becasue I don't find any "interesting" log message from bootloader in yast logs. Result is: if user don't fill in kernel image and initrd bootloader mangels menu.lst. (comboboxes for kernel image and initrd are empty and user continue via OK button) I am not sure if bootloader is responsible for missing information about kernel image and initrd. It is just my opinion. Yes I know that bootloader have to check if user get relevant data during editing. Could you confirm my opinion about missing kernel image and initrd? (You probably forgot edit 2 comboboxes kernel image and initr) When you say 'combo boxes' do you mean edit fields ? I certainly did not omit to fill them. Having said that, and having updated to the latest factory, the problem appears to have gone away. |
If I run yast2, try to edit my "SLED10" section, and change the kernel path I have two problems: a) when you use the 'browse' button to select a file - the path of the kernel / image doesn't get inserted into the entry to the left of the button [ which I assume is to be expected ], so: b) when manually entering a string eg. /sled10/boot/vmlinuz in the entry *appears* to be fine, writes the config file & exits - but then when you cat /boot/grub/menu.lst you see it has corrupted it: sudo cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Mon Mar 10 16:49:36 GMT 2008 default 0 timeout 8 ##YaST - generic_mbr ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title Pae -- openSUSE 11.0 - 2.6.24.1-6 root (hd0,1) kernel /boot/vmlinuz-2.6.24.1-6-pae root=/dev/disk/by-id/scsi-SATA_ST9200420ASG_5SH043SM-part2 vga=0x317 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd-2.6.24.1-6-pae ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 - 2.6.22.13-0.3 (/dev/sda1)### title openSUSE 10.3 - 2.6.22.13-0.3 (/dev/sda1) rootnoverify (hd0,1) chainloader (hd0,0)+1 title SLED10 kernel (hd0,1) root=/dev/disk/by-id/scsi-SATA_ST9200420ASG_5SH043SM-part5 vga=0x317 resume=/dev/sda3 splash=silent showopts HTH.