From: Jim Duda <jim@duda.tzo.com>
To: linux-ide@vger.kernel.org
Subject: Re: 2.6.31-rc1 with ide-tape / STT2000A
Date: Mon, 10 Aug 2009 20:40:10 -0400 [thread overview]
Message-ID: <h5qelb$6it$1@ger.gmane.org> (raw)
In-Reply-To: <20090809175840.0705f2d0@lxorguk.ukuu.org.uk>
On 08/09/2009 12:58 PM, Alan Cox wrote:
On 08/10/2009 01:23 PM, Alan Cox wrote:
>> hdc: HL-DT-ST GCE-8160B, ATAPI CD/DVD-ROM drive
>> hdd: Seagate STT20000A, ATAPI TAPE drive
>> ide-cd: hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache
>> libata version 3.00 loaded.
>> ata_piix 0000:00:1f.2: version 2.13
>> ata_piix 0000:00:1f.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18
>> ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
>> ata_piix 0000:00:1f.2: setting latency timer to 64
>>
>
> You have both sets of drivers loaded at once. That won't do what you
> want. You need to build without the old IDE layer.
>
>
Aha!
Removing the older IDE drivers completely restored the use of the st driver.
I'm attempting a backup using libata and st now.
Maybe I don't need ide-tape afterall.
Thanks!
Jim
libata version 3.00 loaded.
ata_piix 0000:00:1f.1: version 2.13
ata_piix 0000:00:1f.1: enabling device (0005 -> 0007)
ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ata_piix 0000:00:1f.1: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
ata_piix 0000:00:1f.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xefe0 ctl 0xefac bmdma 0xef60 irq 18
ata4: SATA max UDMA/133 cmd 0xefa0 ctl 0xefa8 bmdma 0xef68 irq 18
ata2.00: ATAPI: HL-DT-ST GCE-8160B, 1.02, max MWDMA2
ata2.01: ATAPI: Seagate STT20000A, 8A51, max MWDMA2
ata2.01: device is on DMA blacklist, disabling DMA
>
> Alan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-08-11 0:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 20:30 2.6.31-rc1 with ide-tape / STT2000A Jim Duda
2009-08-08 20:59 ` Robert Hancock
2009-08-08 21:44 ` Jim Duda
2009-08-09 16:58 ` Alan Cox
2009-08-09 19:47 ` Jim Duda
2009-08-09 20:21 ` Alan Cox
2009-08-09 20:25 ` Jim Duda
2009-08-09 20:58 ` Alan Cox
2009-08-09 22:27 ` Bartlomiej Zolnierkiewicz
2009-08-10 17:21 ` Alan Cox
2009-08-10 19:48 ` Bartlomiej Zolnierkiewicz
2009-08-10 21:20 ` Alan Cox
2009-08-10 21:42 ` Bartlomiej Zolnierkiewicz
2009-08-11 0:40 ` Jim Duda [this message]
2009-08-09 7:28 ` Borislav Petkov
2009-08-09 22:51 ` Jim Duda
2009-08-09 23:32 ` Jim Duda
2009-08-10 0:01 ` Jim Duda
2009-08-10 2:28 ` Jim Duda
2009-08-10 22:10 ` Jim Duda
2009-08-10 22:36 ` Alan Cox
2009-08-10 23:07 ` Jim Duda
2009-08-10 23:21 ` Jim Paris
2009-08-10 23:34 ` Jim Duda
2009-08-11 9:37 ` Alan Cox
2009-08-11 4:33 ` Borislav Petkov
2009-08-11 11:25 ` Jim Duda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h5qelb$6it$1@ger.gmane.org' \
--to=jim@duda.tzo.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).