DragonFly bugs List (threaded) for 2007-06
Re: [issue566] NATA a nonstarter with ATI SB600 on MSI K9AGM-FID
:Joe "Floid" Kanowitz <email@example.com> added the comment:
:Two new 'developments:'
:-Finally gave in/gave up and ordered some PATA-to-SATA bridges last week, so
:I'll be able to test the theory that this is only a problem with the legacy PATA
:controller when they arrive.
PATA to SATA bridge? You mean something that plugs into a PATA header
and provides a SATA port? That can't be right... do people actually
make those? I'd be amazed if that sort of thing worked reliably.
Or did you mean you ordered SATA controllers that plug into e.g. PCI
slots and provide SATA ports?
:-Just tried the new -PREVIEW with the big NATA update, and things haven't
:improved much if at all for this configuration. I can "sort of" boot (if I can
:avoid fsck, e.g. single-user), the disk comes up in UDMA33, ICRC errors galore,
:I couldn't convince natacontrol to raise it *above* UDMA33, but trying to choose
:BIOSDMA took it all the way back to PIO4, which seems to be stable enough for me
:to build a kernel with the old driver like I should've done before I embarked on
:Pretty sure the channels still aren't showing an IRQ assigned, also pretty sure
:the (cosmetic) sb600.diff ID patch in the bugtracker didn't make it into the tree.
NATA doesn't report irq assignments, I haven't looked into why not.
Please post the 'atapci', 'ata', 'acd', and 'ad' lines in the boot.
e.g. you should see something like this:
atapci0: <nVidia nForce3 Pro UDMA133 controller> port ...
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
acd0: CDRW <CD-W54E/1.1B> at ata1-master PIO4
atapci1: <nVidia nForce3 Pro SATA150 controller> port ...0.0 on pci0
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
ad6: 194481MB <Maxtor 6L200M0 BACE1G20> at ata3-master SATA150