prosum
2005-01-22, 06:46 AM CST
Today I installed FC3 on my new WD Raptor 37GB 10k rpm SATA disk. It was recongnized properly, partitioned and installed to without any problems at all. But it simply won't boot.
After loading what should be the apropriate SATA kernel modules, and recognizing the controller, the boot process stops at the following line:
ata: dev 0 ATA, max UDMA/133, 72303840 sectors: lba 48No kernel panic, no error, no nothing. It just stops.
Now, the disk is alive and well, so why does this happen? I've searched around a bit and I can't find anyone mentioning the same problem. I'm beginning to suspect that the kernel isn't happy with my chipset. But my motherboard, an FIC KT600Pro, should be using a standard VIA chipset.
I have an FC2 installation on another disk (with a custom config 2.6.9 kernel), and it behaves simmilarly as long as the SATA disk is in my machine.
So what can I do? Not having linux is out of the question, so I'm contemplating buying a new motherboard, or maybe a stand-alone SATA controller. But it would be nice if there were a solution that didn't involve buying new hardware..
After loading what should be the apropriate SATA kernel modules, and recognizing the controller, the boot process stops at the following line:
ata: dev 0 ATA, max UDMA/133, 72303840 sectors: lba 48No kernel panic, no error, no nothing. It just stops.
Now, the disk is alive and well, so why does this happen? I've searched around a bit and I can't find anyone mentioning the same problem. I'm beginning to suspect that the kernel isn't happy with my chipset. But my motherboard, an FIC KT600Pro, should be using a standard VIA chipset.
I have an FC2 installation on another disk (with a custom config 2.6.9 kernel), and it behaves simmilarly as long as the SATA disk is in my machine.
So what can I do? Not having linux is out of the question, so I'm contemplating buying a new motherboard, or maybe a stand-alone SATA controller. But it would be nice if there were a solution that didn't involve buying new hardware..