Bugzilla – Bug 146459
Bootmanager detection detects "resume" incorrectly
Last modified: 2007-05-10 12:21:43 UTC
When I´ve other versions of linux on my system the installer detects those and adds entries to the list in the "bootmanager" page. The "resume" field is detected incorrect, it always points to the partition the new system is installed to, even for the other systems (where it should point to their root filesystem).
We'll need the usual: yast logs and grub-config. Thanks.
I attached the logs. I asked the bootloader config to auto-detect my configuration, and this time there was another output which was also wrong. But the log files apply to it. I´ve /dev/sda3 (SuSE 10.0) and /dev/sda4 (SuSE 10.1). Both use /dev/sda9 for swap. The entry for /dev/sda3 (10.0) had a "resume" entry "/dev/sda9", but the one for /dev/sda4 (10.1) had no "resume" entry at all. Another thing which is wrong here is that name of the the entry for the "old" SuSE linux was correct: "SuSE Linux 10.0 (/dev/sda3), but the second field showed "/dev/sda4,root=/dev/sda3". But this is only a visual problem (the first entry is wrong) in the listview since it writes "(hd0,2)/boot/vmlinuz" into the grub files which refers correct to /dev/sda3
Created attachment 65753 [details] YaST2 logs
Created attachment 65754 [details] menu.lst
So, it looks like a YaST issue.
I just tested this with beta3 and the resume tag was now detected correct. The only thing which is still wrong is the description in the list (second field still shows "/dev/sda4")
This is still there in beta6 (the wrong description), but it´s just a visual glitch.
Or it seems that there´s the visual glitch and no resume parameter is written at all for the 10.1 version.
Fixed in openSUSE 10.3