http://qa.mandrakesoft.com/show_bug.cgi?id=6188
Product: drakxtools
Component: drakboot
Summary: DrakBoot messes up lilo.conf -> Booting Impossible
Product: drakxtools
Version: 9.2-17mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: drakboot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Installed Mandrake 9.2 final, worked all fine. Default kernel chosen by
Mandrake is 2.4.22-10mdkenterprise.
However, I realised that for some reason, only 896M RAM were detected/used,
although I have 1GB. Hence I used the DrakBoot LILO configuration tool to
change it to 1024M.
This did not work for some reason and the computer did not boot, so I booted
with parameter mem=896M and wanted to change it back in DrakBoot, so that there
is no value in the field "enter precise RAM if necessary".
Now, the problem: When I rebooted again, the computer stopped booting with
"Uncompressing Linux... Ok, booting the kernel".
After some looking around, I found the problem: DrakBoot had messed up my lilo.conf
It added as boot parameter all the usual stuff, but then also "mem= mem=896",
which is of course nonsense and the kernel could not handle that.
After changing this to "mem=896M", and reinstalling the boot loader via the
rescue disk, I could boot again.
See below my lilo.conf as it is now. Note the changed (by me) and working
parameter in the linux-enterpris section, whereas in all other sections it still
has the messed up parameters as filled in by DrakBoot.
This has to be fixed, DrakBoot should really not create invalid lilo.conf entries.
The other stupid thing is that the advanced setings in DrakBoot are always
applied to all sections - so in my case none of the kernels could boot anymore.
I think after changing LILO, DrakBoot should provide another menu entry with the
previous settings, as a fallback when booting is not possible. Alternatively,
one should be able to apply the settings seperately for each individual kernel
image.
Also apologies - as I am using the stable version, I should go to MandrakeExpert
to report this bug, but I couldn't find a Bugzilla there. And as 9.2 is only a
week old, this bug is probably still present in the current cooker.
Here my lilo.conf:
boot=/dev/hde
map=/boot/map
vga=794
default="linux-enterpris"
keytable=/boot/de-latin1.klt
prompt
nowarn
timeout=50
message=/boot/message
menu-scheme=wb:bw:wb:bw
disk=/dev/hde bios=0x80
image=/boot/vmlinuz
label="linux"
root=/dev/hde9
initrd=/boot/initrd.img
append="noapic devfs=mount hda=ide-scsi acpi=ht resume=/dev/hde7 splash=silent
mem= mem=896"
vga=788
read-only
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hde9
initrd=/boot/initrd.img
append="noapic devfs=mount hda=ide-scsi acpi=ht resume=/dev/hde7 mem= mem=896"
read-only
image=/boot/vmlinuz-enterprise
label="linux-enterpris"
root=/dev/hde9
initrd=/boot/initrd-enterprise.img
append="noapic devfs=mount hda=ide-scsi acpi=ht resume=/dev/hde7 splash=silent
mem=896M"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hde9
initrd=/boot/initrd.img
append="failsafe noapic devfs=nomount hda=ide-scsi acpi=ht resume=/dev/hde7
mem= mem=896"
read-only
other=/dev/hde1
label="windows"
table=/dev/hde
other=/dev/hdf1
label="windows2"
table=/dev/hdf
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80
other=/dev/fd0
label="floppy"
unsafe
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
