From Bugzilla Helper: User-Agent: Mozilla/4.77 [de] (X11; U; Linux 2.2.19bb01-ide+raid+ipsec i686) Description of problem: My notebook locks hard when booting the kernel. Last message is: RAMDISK: Compressed image found at block 0 How reproducible: Always Steps to Reproduce: 1. Install ROSWELL on a ACER Travelmate 522TXV 2. After installation, the system locks hard on every boot 3. Additional info: My notebook is a ACER Travelmate 522TXV, PIII 600, 192 MB memory, ATI RAGE mobility
I also experienced this same problem, however, I'm running ROSWELL on a Dell OptiPlex GX1 desktop computer. To resolve the problem, I had to boot from the boot/rescue floppy and remove the initrd line from /etc/lilo.conf and run /sbin/lilo. Once I stopped trying to load the initrd, my machine booted with no problem.
Seems to be really INITRD related. When I start my system from the lilo prompt with "linux noinitrd" everything is fine. I commented out the initrd line from lilo.conf, reinstalled lilo and now my system boots without a problem.
ok so both of you are using lilo not grub ? also, could you paste the "e820 info" (eg the memory map in the beginning of "dmesg", the lines with "BIOS-e820:" in them)
Yes, I4m using lilo and not grub. Here comes the e820 info you requested: BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000000bff0000 (usable) BIOS-e820: 000000000bff0000 - 000000000bff8000 (ACPI data) BIOS-e820: 000000000bff8000 - 000000000c000000 (ACPI NVS) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
We (Red Hat) should try to fix this for the next release.
I'm using lilo and here's the info asked for (this is without loading initrd): BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000008000000 (usable) BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) Hope this helps.
I am seeing the same thing. I am using a Dell Optiplex GX150, celeron 600. It's worth noting that this only happened after running an upgrade from 7.1 to roswell, with ext3 migration. I also ran a full install on this very same machine, and did not experience this problem. Both times I chose lilo. In the broken (upgrade) case, disabling the ramdisk (with "lilo: linux noinitrd" at boot time) allowed the machine to boot. Here's the boot info requested earlier: BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000007e07000 (usable) BIOS-e820: 0000000007e07000 - 0000000007e26000 (ACPI data) BIOS-e820: 0000000007e26000 - 0000000008000000 (reserved) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) Thanks, Josh
Just a quick update: I did a clean install of ROSWELL last Friday due to some performance problems that seemed to stem from doing an "upgrade". When I rebooted my machine, I encountered the same problem with it just hanging. When I selected linux with the 'noinitrd' option, it loaded fine. Perhaps it's not just with the upgrade from 7.1 to ROSWELL.
Same problem, different solution: I had this happen multiple times on two different Thinkpad T22 machines. Commenting out linear in lilo.conf and rerunning lilo fixed it.
Does this happen with the final 7.2 release?
If I remember correctly, once I installed the final 7.2 release, I didn't encounter this problem anymore.
Great, thanks.