This is the only bug I could find that I thought might be related to my
issue. I was going to try blacklisting the ata drivers as suggested
above, but I'm not sure how to include all the necessary ones to get the
old IDE driver (for now). I started having problems with 2.6.20-12,
though -11 works fine. Like other symptoms reported here, it's
detecting my devices as SCSI sda devices rather than the usual hda
stuff, and I'm not sure whether this is an issue or by design, but -12
and -13 won't boot.
I managed to get a dmesg with -12 as /boot (hda1, though it saw it as
sda1) managed to mount properly. I was getting warnings with -13, but I
don't care, there's nothing valuable on this machine :). Cheers.
-Scott
** Attachment added: "3 dmesg from 2.6.20-{13,12,11} (in that order)"
http://librarian.launchpad.net/6991211/tmp.txt
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
