Hi,

This is 100% reproducible. I'm using a Shuttle SG33G5 and Q9300 (45nm).

If I press a key during the GRUB countdown and choose Linux (Linux is the default), the boot hangs after the line "Booting the kernel." and before "Redhat nash..." is displayed.

So I went into GRUB and removed the "quiet" kernel option to see why/where it's failing. Then when typing up this in another PC, I noticed that Fedora 9 actually booted but with single core support.

I see this in dmesg:
CPU 1 irqstacks, hard=c07ba000 soft=c079a000
Not responding.
Inquiring remote APIC #1...
... APIC #1 ID: failed
... APIC #1 VERSION: failed
... APIC #1 SPIV: failed
CPU #1 not responding - cannot use it.
Booting processor 1/2 ip 4000
Not responding.
Inquiring remote APIC #2...
... APIC #2 ID: failed
... APIC #2 VERSION: failed
... APIC #2 SPIV: failed
CPU #2 not responding - cannot use it.
Booting processor 1/3 ip 4000
Not responding.
Inquiring remote APIC #3...
... APIC #3 ID: failed
... APIC #3 VERSION: failed
... APIC #3 SPIV: failed
CPU #3 not responding - cannot use it.
Total of 1 processors activated (5015.39 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Brought up 1 CPUs

Please help. How do I fix this? It's kinda pointless having a boot option if I can't use it.

Thanks,
Sarav

1) so you have not advised what happens if you do not arrow down at the grub menu???

2) IMHO this has nothing to do with grub but with your kernel selection and distro selection relative to your hardware.

3) does this hardware work with any distro including live cd that you know of?

4) until you get a better answer...if you have not run a good all round live cd such as knoppix...upload your /var/log/syslog to a on line site such as www.ripway.com so we can study your chipsets pls.

it is possible your kernel is hanging because it does not have the correct drivers or....needs a boot parameter aka cheat code...aka boot prompt to stop some driver loading etc