fedora hangs just before entering runlevel 5 (fresh install)
I have a P4 3.06 Ghz Hyperthreading, in an Asus P4G8X Deluxe with 1GB RAM. With WinXP installed
Before installing Fedora I ran Knopixx 3.3 to see if everything was detected fine and it was. So I used Partition Magic to get enough free space for Fedora
I had to install in text mode because the graphics card is not detected (Asus GeForce4 Ti4200 8x).
Before starting configuration I got a message saying that partitions where not aligned correctly (probably due to a partitioning tool which got bad numbers for the geometry of the disk), saying that I could ignore it, but with the possibility of having problems with the boot loader. I ignored it and continued.
After installing, during boot the system hangs just before entering runlevel 5. I thought it hanged due to firewire (it was the las thing getting loaded), but putting nofirewire as a kernel option didn't resolve it. It hanged this time just after "enabling swap space".
I booted with the installation CD in rescue mode to see if the problem was a bad swap partition, executed swapon -a and there was no problem at all.
Later, inside Windows XP, i started this linux installation inside Vmware and noticed that the next fase after firewire was "entering run level 5". So I assume the problem is here somewhere.
I updated the BIOS to the most recent one and the problem persists.
Can the problem be due to the "bad aligned partition"? In one hand it appears to be so, because runlevel 5 may be executed outside the /boot partition (confirm if I'm wrong as this was a "shot in the dark"), on the other hand the warning said the problem would be in the boot loader and not in the system boot.
As Vmware emulates a machine with a certain hardware, I see to chances. Or there is some hardware (outside vmware) that is confusing the system before entering runlvel 5, or, as Linux inside Vmware uses the partitions handed by Vmware, he is not a victim of the "bad aligning".
But it's strange if it is a hardware problem, as Knopixx detected everything fine.
While inside Vmware, I managed to install the latest testing kernel RPM from Fedora update, and the problem persists.
Thanks for any info provided!