It seems Gavin Atkinson wrote:
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
With the new ATA code, the boot now hangs. I now get on a verbose bootup:
ata1-master: FAILURE - ATAPI_IDENTIFY status=1ERROR error=0
Okies, what if you make that CDROM a slave ?
I am rather naive on the topic but don't many drives have a single
drive jumper
which works better than a master with no slave at times?
On Wednesday, August 13, 2003, at 5:43 AM, Gavin Atkinson wrote:
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
ata1: spurious
On Fri, 8 Aug 2003, Soeren Schmidt wrote:
ftp://ftp.deepcore.dk/pub/ATAng
Before these rather radical changes to the ATA driver hits the
tree, here is the opportunity to test them out, give usefull
feedback and for the depending subsytems to adjust to the new
ways of things (burncd atapicam
On Fri, Aug 08, 2003 at 09:55:11PM +0200, Soeren Schmidt wrote:
The first preview release of ATAng is now available on:
ftp://ftp.deepcore.dk/pub/ATAng
I cvsup'd to HEAD and applied the conf-patch and put in your
new ATA source, but when I recompiled my kernel and rebooted, the
server
It seems Jason Dambrosio wrote:
On Fri, Aug 08, 2003 at 09:55:11PM +0200, Soeren Schmidt wrote:
The first preview release of ATAng is now available on:
ftp://ftp.deepcore.dk/pub/ATAng
I cvsup'd to HEAD and applied the conf-patch and put in your
new ATA source, but when I
Hi,
I've just compiled ATAng into my kernel, and I'm currently running it -
but I had to rip out my CD-ROM to make it work. I wasn't able to grab
the exact wording of the error, but it was something along the lines of
a failure to identify ata1-slave - which I suppose is my CD-ROM player.
It then
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
With the new ATA code, the boot now hangs. I now get on a verbose bootup:
ata1-master: FAILURE - ATAPI_IDENTIFY status=1ERROR error=0
Okies, what if you make that CDROM a slave ?
That seems to work fine:
ata1:
It seems Gavin Atkinson wrote:
I'm using ATAng-20030809-1.tgz on top-of-tree current on hardware detected
with the old ATA code as:
atapci0: Intel ICH5 UDMA100 controller port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7
at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
ata1: spurious interrupt - status=0x7f error=0x7f reason=0x7f
ad0: 19881MB Maxtor 6E020L0 [40395/16/63] at ata0-master UDMA100
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
With the new ATA code, the boot now hangs. I now get on a verbose bootup:
ata1-master: FAILURE - ATAPI_IDENTIFY status=1ERROR error=0
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
ata1: spurious interrupt - status=0x7f error=0x7f reason=0x7f
ad0: 19881MB Maxtor 6E020L0 [40395/16/63] at ata0-master UDMA100
acd0: CDROM SAMSUNG CD-ROM SC-152A at ata1-slave PIO4
OK, your CDROM doesn't like to be
It seems Gavin Atkinson wrote:
On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
ata1: spurious interrupt - status=0x7f error=0x7f reason=0x7f
ad0: 19881MB Maxtor 6E020L0 [40395/16/63] at ata0-master UDMA100
acd0: CDROM SAMSUNG CD-ROM SC-152A at ata1-slave PIO4
12 matches
Mail list logo
