It seems Alex wrote:
Mike, I couldn't find your fix in the commit logs - perhaps someone else
committed it? Do you have the revision number? The problem still
persists:
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ad0: 6194MB TOSHIBA MK6409MAV
Mike Smith wrote:
JFWIW, this sounds like something that I "fixed" in the old wd driver,
where a device 'echoed' on the bus after it was deselected. Increasing
the timeout between deselecting the device and trying to talk again to
the bus was, AFAIR, the workaround then.
Mike, I couldn't
JFWIW, this sounds like something that I "fixed" in the old wd driver,
where a device 'echoed' on the bus after it was deselected. Increasing
the timeout between deselecting the device and trying to talk again to
the bus was, AFAIR, the workaround then.
It seems Alex wrote:
OK -
At 22:01 01/25/2000 +0100, you wrote:
It seems Tom Embt wrote:
Don't mean to butt in here, I haven't really been following the thread -
but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x)
on secondary master of the PIIX4 on my BP6. By going into the BIOS (the
section of
Soren Schmidt wrote:
It seems Alex wrote:
You need to update..
OK - I've just updated. Here goes again:
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using
UDMA33
acd0: CDROM
It seems Alex wrote:
OK - here's the part relevant to ata:
ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device
1.1 on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0
ata0: mask=03 status0=50 status1=00
ata0: mask=03 status0=50 status1=00
ata0: devices = 0x1
I have the same problem:
[anders@enterprise:anders] $ dmesg | grep ata
ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1
on pci0
ata0 at 0x01f0 irq 14 on ata-pci0
ata-isa0: already registered as ata0
ata0-slave: ata_command: timeout waiting for intr
ata0-slave: identify
It seems Anders Andersson wrote:
I have the same problem:
[anders@enterprise:anders] $ dmesg | grep ata
ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1
on pci0
ata0 at 0x01f0 irq 14 on ata-pci0
ata-isa0: already registered as ata0
ata0-slave: ata_command: timeout
On Tue, Jan 25, 2000 at 09:40:11AM +0100, Anders Andersson wrote:
I have the same problem:
[anders@enterprise:anders] $ dmesg | grep ata
ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1
on pci0
ata0 at 0x01f0 irq 14 on ata-pci0
ata-isa0: already registered as ata0
At 09:47 01/25/2000 +0100, Soren Schmidt wrote:
It seems Anders Andersson wrote:
I have the same problem:
[anders@enterprise:anders] $ dmesg | grep ata
ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1
on pci0
ata0 at 0x01f0 irq 14 on ata-pci0
ata-isa0: already
It seems Tom Embt wrote:
Don't mean to butt in here, I haven't really been following the thread -
but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x)
on secondary master of the PIIX4 on my BP6. By going into the BIOS (the
section of it where you would set CHS numbers,
It seems Alex wrote:
Speaking of identify failed, I get the following:
ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device
1.1 on pci0
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
...
ata1-slave: ata_command: timeout waiting for intr
Soren Schmidt wrote:
It seems Alex wrote:
Speaking of identify failed, I get the following:
ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device
1.1 on pci0
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
...
ata1-slave: ata_command:
Last weekend i tried patches from Soren Schmidt to reactivate my old
cdrom which went away after the ata-update around the 18. January. This
patches completely broke ata support for me (that means the kernel did
not boot anymore). Of course i reported this one or two days later.
Now an
It seems F. Heinrichmeyer wrote:
Last weekend i tried patches from Soren Schmidt to reactivate my old
cdrom which went away after the ata-update around the 18. January. This
patches completely broke ata support for me (that means the kernel did
not boot anymore). Of course i reported this
It seems Alex wrote:
You need to update..
OK - I've just updated. Here goes again:
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using
UDMA33
acd0: CDROM UJDA150 at ata1-master using PIO4
Hi
At Sun, 23 Jan 2000 18:51:25 +0100 (CET),
Soren Schmidt [EMAIL PROTECTED] wrote:
I updated to today's -current from -stable.
My ATAPI CD-ROM drive doesn't probed,
and is seemed to be halted.
(The tray is locked, won't open, and the LED keeps being on.)
This is fixed in the next
It seems Motomichi Matsuzaki wrote:
Thank you for fixing, but still not probed.
What can I do for your work?
ata-pci0: Intel PIIX4 ATA-33 controller port 0xf000-0xf00f at device 7.1 on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000
ata0: mask=03 status0=50 status1=00
ata0:
At Tue, 25 Jan 2000 08:29:32 +0100 (CET),
Soren Schmidt [EMAIL PROTECTED] wrote:
Thank you for fixing, but still not probed.
ata-pci0: Intel PIIX4 ATA-33 controller port 0xf000-0xf00f at device 7.1 on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000
ata0: mask=03 status0=50
Hi.
I updated to today's -current from -stable.
My ATAPI CD-ROM drive doesn't probed,
and is seemed to be halted.
(The tray is locked, won't open, and the LED keeps being on.)
Mother board: ABIT BH6
CD-ROM drive: ATAPI [CDU77E-NE] on primary-master
other ATAs: none
It worked fine on -stable.
It seems Motomichi Matsuzaki wrote:
Hi.
I updated to today's -current from -stable.
My ATAPI CD-ROM drive doesn't probed,
and is seemed to be halted.
(The tray is locked, won't open, and the LED keeps being on.)
Mother board: ABIT BH6
CD-ROM drive: ATAPI [CDU77E-NE] on primary-master
21 matches
Mail list logo
