kernel panic -=- won't boot--Fixed

[liquidzoo]

label="263-13"

root=/dev/hdg1

initrd=/boot/initrd-2.6.3-13mdk.img

append="devfs=mount acpi=ht resume=/dev/hdg11 splash=silent"

vga=788

read-only

 

Why do you have resume=/dev/hdg11 here instead of /dev/hde11?

 

Also, did you re-run lilo after you made these changes? Just type lilo and hit enter.

 

Also, why are you wanting to suspend anyway? This option has never worked correctly for me in Mandrake.

 

Did you run the swapon command I gave you?

[rockybalboa]

Ouch you caught me.

I meant for the resume line to read hde11. Although it doesn't give me any error on boot, despite the fact that it's clearly wrong. I can't figure out how I should be getting the error involving hdg5.

I am not trying to suspend. If you are refferring to the resume lines, they were there when I first opened lilo.conf. Haven't tried hardware suspend mode and don't intend to. Or does the suspend have to do with the fact that it's a journaling file system? Additionally, I get the resume errors listed earlier when ever I try to boot the -13 kernel. What would happen if I edited out the resume part of the lines?

Yes, I ran the swapon command. It gave no output so it either didn't work or it worked without a problem.

I'll go back and edit the errant lines. I doubt it will change my problem, but that's a highly uneducated guess.

[liquidzoo]

Editing out (or removing completely) those lines will definitely solve your resume problem.

 

If the swapon command didn't error, it worked.

 

Just for reference, here's my lilo.conf file

 

# File generated by DrakX/drakboot
# WARNING: do not forget to run lilo after modifying this file

boot=/dev/hda
map=/boot/map
vga=794
default="linux"
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
       label="linux"
       root=/dev/hda1
       initrd=/boot/initrd.img
       append="devfs=mount splash=silent"
       vga=788
       read-only
image=/boot/vmlinuz
       label="linux-nonfb"
       root=/dev/hda1
       initrd=/boot/initrd.img
       append="devfs=mount"
       read-only
image=/boot/vmlinuz-rc3.1mdk
       label="262-0rc31"
       root=/dev/hda1
       initrd=/boot/initrd-rc3.1mdk.img
       append="devfs=mount splash=silent"
       read-only
image=/boot/vmlinuz
       label="failsafe"
       root=/dev/hda1
       initrd=/boot/initrd.img
       append="failsafe devfs=nomount"
       read-only
other=/dev/fd0
       label="floppy"
       unsafe

image=/boot/vmlinuz-2.6.2-3mdk-i686-up-4GB
       label=262i686up4G-3
       root=/dev/hda1
       read-only
       optional
       vga=794
       append=" devfs=mount splash=silent"
       initrd=/boot/initrd-2.6.2-3mdk-i686-up-4GB.img

image=/boot/vmlinuz-2.6.3-7mdk-i686-up-4GB
       label=263i686up4G-7
       root=/dev/hda1
       read-only
       optional
       vga=794
       append=" devfs=mount splash=silent"
       initrd=/boot/initrd-2.6.3-7mdk-i686-up-4GB.img

image=/boot/vmlinuz-2.6.6-2mdk-i686-up-4GB
       label=266i686up4G-2
       root=/dev/hda1
       read-only
       optional
       vga=794
       append=" devfs=mount splash=silent"
       initrd=/boot/initrd-2.6.6-2mdk-i686-up-4GB.img

 

Is this a laptop or a desktop? If it's a desktop, you don't need the resume= part for sure. Delete it, re-run lilo, and reboot. Everything should be fine.

[rockybalboa]

Another mess solved!

Deleting the resume entries did the trick.

Everything seems to be working ok.

The first couple of boots went really slow.

What does this message mean

drakboot[4355]: check_geometry_using_the_partition_table failed for (hde1, 14346044): 892,254,62 vs 1023,2,62 with geometry 155061/16/63

It's from the bootlog. While trying to pinpoint the reason for the slow boot (and curiosity's sake) I found it. My greatest concern is that after all this partition juggling there might be something screwed up that will sneak up later. I particularly don't like the idea that it's talking about the boot sector.

Thanks again for the help!

DW