Grub freezes before `Uncompressing kernel'
 

Grub freezes after displaying `boot' but before `Uncompressing kernel'.



I installed Ubuntu 6.0.2 on a Athlon (now Sempron) 2000+ with 512Mb of RAM and four hard drives (15Gb, 20Gb, 1.2Gb, 1.2Gb). It worked fine, and my partition setup was as follows:

However, my dad soon wanted his computer back, so I had to move my hard drives up to my system, which has the following specs: Pentium 133, 128Mb RAM, 5 PCI/ISA ports (5 of each),
and a fairly old BIOS, which doesn't support drives over 8.5Gb. However, since my /boot partition is in the first 100Mb of the first drive, it shouldn't matter too much.

My heating system is fine; I put brand new quality thermal paste on the CPU and added a 120mm fan. I also ran memtest86 for 10 hours, and my memory is fine.

When booting up I get the following output:
At that point it freezes, with no hard drive activity whatsoever. I've left it for about 30 minutes, and no change.

I tried removing `quiet' and `splash' from the kernel line, as well as adding `acpi=off pci=noacpi, noapic, nopcm, pcm=off' and various combinations of those options. No change.


I've spent several hours searching for a solution, but I can't seem to figure it out. I also had this problem with Fedora Core 5. It worked fine on my laptop, a Pentium II 366Mhz with 256Mb of RAM. However, that system had one 4.5Gb HD and that was it.

Try adding the option to the kernel boot line:

edd=skipmbr

If that doesn't work, try:

edd=off

Some old BIOS may not like the new way of finding the master boot record.

Nope, that didn't work.

At another forum (where I am one of the two knowledgeable tech guys, leaving exactly one person to help me), I was given the following advice:
Stop mixing RAID and non-RAID.
Use a HD size that the BIOS supports
Check all of your hardware.


Well, after replacing the motherboard, CPU, and PSU, and running memtest86 for 10 hours, I loaded a copy of FC5 onto a 4.5Gb disk and tried it. No dice. I also removed all my non-parity RAM, and that didn't help at all.

This seems very strange to me, as I've heard of people getting Linux to work on a P133. I've no idea what I'm doing wrong.


Windows 95/98 and DOS both run fine on this system, and XP Home did boot (although it barely ran). Also, I can boot into one diskette Linux, BootE. However, various other diskette Linuxes give me stuff like "Failed to load initial console." Grr.


Since the OP, one of my /home drives failed (thank God for RAID), and a Celeron motherboard I was testing flaked out, along with a spare PSU. Shouldn't have split molex connectors with electrical tape. None of that's relevant, but it's a testament to the bad luck I've been having.

Try a live CD like Knoppix, and see if that will boot. Then, check how the machine is seeing the partitions with fdisk -l

I am a newbie.. and my dual boot with fedora core 7 and windows xp was giving me this same problem. It would boot into windows xp fine but as soon as i chose to boot fedora 7 it would freeze on me. How can i add the "edd=skipmbr" line so i don't have to type that in everytime i want to load fedora?

thanks,
Mike

You can add the value to the kernel lines in /etc/grub.conf. Once you add it, any new kernels added by maintenance will automatically get the option, so you only have to do it once.

ok so i'm a real noob and wanted windows xp to be the primary boot so i reinstalled fedora because i accidentally did the text mode install and wanted the graphical and made windows the main boot and now when it comes to grub loader i select fedora add the edd=skipmbr and its still freezing. neither the edd=skipmbr or edd=off worked this time :/ u guys have any ideas?? its a dell xps 1710 laptop with a sata hard drive oh i also just tried removing quiet from the editor thing and it gets to net: registered protocol family 2 and just sits there and freezes.

Freeze uncompressing Kernel
 

At least in Fedora this is a known bug for certain dual core configs (mostly related to Dell machines)
Passing maxcpus=1 in kernel line worked around this for me, then upgrade to Kernel 2.6.22 allowed me to use dual core again fixing the problem.

See bug 241249 un redhat bugzilla (sorry not to post the full url, but since this is my first post, LinuxQuestions wants me to introduce myself and I have no time to do so now)

Hope this helps.

I don't know what made me do this but after reading that last post i went into the bios and turned off a few features of the dual core processor and its working fine. Windows xp boots and so does fedora :) Thanks for all your help everyone!