On Wed, Apr 20, 2005 at 11:49:24AM -0400, [EMAIL PROTECTED] wrote: > The ATA driver issued a 'read sectors' command and did not receive a > 'done' interrupt within 30 seconds. > I would guess either the interrupt is not going where we think it is > (the drive is not 'busy' any more according to the status) or the chip > used in the controller needs special code. > > Can you get the output of the /bin/pci command? > > --jim
Hello, I found out that there is no problem if there is no disk attached to the controler. However, the corresponding line from /bin/pci is: 0.10.0: 01.80.00 1103/004 10 0:0000ec01 16 1:0000e801 16 2:0000e401 16 3:0000e001 16 4:0000dc01 256 Another question: Is there some device/command that shows the vendor/device IDs or similar? It'd be a pleasure to grep for "Adaptec" or "controller" or alike, and get "0.10.0" back ;) .. I actually booted netbsd2, and hope that it is right; I can't get the /bin/pci-output to my unix-machine atm, some newbie problems, so I handpasted the above. > > On Wed Apr 20 10:27:38 EDT 2005, [EMAIL PROTECTED] wrote: > > > > > > Hello everybody, > > > > I'm installing Plan9 on my AMD at the moment, and booting it gives me: > > lba 0 -> 0, count 1 -> 1 (1) > > 0x00 0x00 0x00 0x00 0x00 0xE0 0x58 > > command 20 > > data 80e82c98 limit 80e82e98 dlen 512 status 0 errror 0 > > > > several times. It slows the booting process down, of couse ;). It happens > > after > > the "Install or Boot it"-menue, and before it asks me what mouse, and so on > > I > > use. > > > > I recall that these Problems started when I added my beloved Adaptec ATA > > Raid > > 1200 PCI controller to the system. > > > > Anybody a rough idea where that comes from in particular? Any fix? >
