Key words: Asrock (ASUS actually) and no FDC found.
This has been observed before on semi-recent ASUS mainboards.
It's caused by some boot loaders that use an incorrect "out"
instruction intended to reset the FDC. That "out" instruction
was acceptable for ancient FDCs, but it locks up the FDCs in
newer super-I/O chips found in some ASUS mainboards. The correct
approach is to issue a BIOS call instead, or use a real driver
that knows how to identify and drive newer FDCs.
This bug existed in the kernel's boot loader up until 2.4.13 or
so when I fixed it to eliminate the FDC lock up problem on my
ASUS P4T-E. Lilo and syslinux-2.02 don't have the bug. I have
seen GRUB lock up the FDC, however, which is yet another reason
why I don't use that POS.
What boot loader are you using? If the bug goes away with another
boot loader, then file a bug report with your vendor.
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/