It's worth pointing out that I also tried the above installations with the all_generic_ide=1 option set. Unfortunately, this didn't make any difference. Adding the noapic and nolapic options made no effect beyond making the keyboard response very slow.
The following line in dmesg arouses my suspicion: ata1.00: configured for UDMA/133 Is it possible that the motherboard is treating the HDD like a PATA drive internally even though its connected via SATA? I read something about the newer libata being very picky about timings to PATA drives, and I wonder if this drive being connected via a SATA cable but treated differently might cause issues. That's a bit cheap if VIA didn't even include a proper SATA controller on their motherboard! The hard drive has native command queueing. I was hoping I could set a jumper on the drive or similar to turn off that feature, but there aren't any such jumpers. Could NCQ be causing any problems here? In the meantime, I'm going to give up on the SATA for now and just connect a PATA drive to get this working. -- SATA HDD on VIA Epia EX crashes and lockups https://bugs.launchpad.net/bugs/238368 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
