From: William Lee Irwin III <wli@holomorphy.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 2.5.56-mm1 fails to detect cd burner
Date: Tue, 18 Mar 2003 13:13:57 -0800 [thread overview]
Message-ID: <20030318211357.GA1232@holomorphy.com> (raw)
In-Reply-To: <3196100000.1047914843@aslan.scsiguy.com>
On Mon, Mar 10, 2003 at 10:36:27PM -0800, William Lee Irwin III wrote:
>> jejb referred me to you (gibbs) for this after guiding me through a
>> cable check.
On Mon, Mar 17, 2003 at 08:27:23AM -0700, Justin T. Gibbs wrote:
> Can you try the latest driver 6.2.30, from here:
> http://people.FreeBSD.org/~gibbs/linux/SRC/
> Just untar the 2.5.X tarball into your source tree and recompile.
> If you still are having problems with the driver at that point, I'll
> guide you through other steps to enable debugging and get additional
> information.
Okay, I've got 2.5.65-mm1 up and it's detected. It needs some runtime
testing I'll have to do in 12-36 hours, probably with virgin 2.5.65
plus your driver.
Thanks.
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.28
<Adaptec 3960D Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
anticipatory scheduling elevator
(scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 31, 16bit)
Vendor: WDIGTL Model: WDE18310 ULTRA2 Rev: 1.30
Type: Direct-Access ANSI SCSI revision: 02
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
anticipatory scheduling elevator
(scsi0:A:3): 20.000MB/s transfers (20.000MHz, offset 15)
Vendor: YAMAHA Model: CRW8424S Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
anticipatory scheduling elevator
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.28
<Adaptec 3960D Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
anticipatory scheduling elevator
(scsi1:A:6): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: IBM Model: DDYS-T36950N Rev: S93E
Type: Direct-Access ANSI SCSI revision: 03
scsi1:A:6:0: Tagged Queuing enabled. Depth 253
anticipatory scheduling elevator
st: Version 20021214, fixed bufsize 32768, wrt 30720, s/g segs 256
SCSI device sda: 35761710 512-byte hdwr sectors (18310 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 71687340 512-byte hdwr sectors (36704 MB)
SCSI device sdb: drive cache: write through
sdb: unknown partition table
Attached scsi disk sdb at scsi1, channel 0, id 6, lun 0
sr0: scsi3-mmc drive: 24x/16x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
-- wli
next prev parent reply other threads:[~2003-03-18 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 6:36 2.5.56-mm1 fails to detect cd burner William Lee Irwin III
2003-03-11 16:03 ` William Lee Irwin III
2003-03-17 15:27 ` Justin T. Gibbs
2003-03-18 21:13 ` William Lee Irwin III [this message]
2003-03-29 13:49 ` William Lee Irwin III
2003-03-30 21:24 ` William Lee Irwin III
2003-03-30 22:26 ` Justin T. Gibbs
2003-03-31 5:29 ` William Lee Irwin III
2003-03-31 5:50 ` Douglas Gilbert
2003-03-31 6:03 ` William Lee Irwin III
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=20030318211357.GA1232@holomorphy.com \
--to=wli@holomorphy.com \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@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