From: patrick.mourlhon@wanadoo.fr
To: linux-kernel@vger.kernel.org
Subject: Re: ATAPI CDRW which doesn't work
Date: Sun, 4 Feb 2001 07:37:47 +0100 [thread overview]
Message-ID: <20010204073747.C529@MourOnLine.dnsalias.org> (raw)
You were my best hope, cause i did something similar for
a Hp 720c on parallel port, and it worked. I did excatly
what you've just said.
But the whole thing still doesn't work properly.
I finally could mount the device, then read the first root directory.
But couldn't get more... always got what you see at the end of the
error message.. I/O error, which resulted in no files appearing from
a 'ls' command.
I've got those kind of message now :
Feb 4 07:18:35 Line kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 00 00 2e 00 00 01 00
Feb 4 07:18:35 Line kernel: SCSI host 0 abort (pid 0) timed out - resetting
Feb 4 07:18:35 Line kernel: SCSI bus is being reset for host 0 channel 0.
Feb 4 07:18:35 Line kernel: hdb: ATAPI reset complete
Feb 4 07:18:35 Line kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 00 00 2e 00 00 01 00
Feb 4 07:18:35 Line kernel: SCSI host 0 abort (pid 0) timed out - resetting
Feb 4 07:18:35 Line kernel: SCSI bus is being reset for host 0 channel 0.
Feb 4 07:18:37 Line kernel: hdb: irq timeout: status=0xd0 { Busy }
Feb 4 07:18:41 Line kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Request Sense 00 00 00 40 00
Feb 4 07:18:41 Line kernel: Info fld=0x0, Current sd0b:00: sense key Medium Error
Feb 4 07:18:41 Line kernel: I/O error: dev 0b:00, sector 184
Feb 4 07:20:09 Line kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 00 00 2e 00 00 01 00
Feb 4 07:20:09 Line kernel: hdb: irq timeout: status=0xd0 { Busy }
Feb 4 07:20:09 Line kernel: hdb: ATAPI reset complete
Feb 4 07:20:09 Line kernel: hdb: irq timeout: status=0xd0 { Busy }
Feb 4 07:20:09 Line kernel: hdb: ATAPI reset complete
Feb 4 07:20:10 Line kernel: hdb: irq timeout: status=0xd0 { Busy }
Feb 4 07:20:10 Line kernel: scsi0 channel 0 : resetting for second half of retries.
Feb 4 07:20:10 Line kernel: SCSI bus is being reset for host 0 channel 0.
Feb 4 07:20:10 Line kernel: hdb: status timeout: status=0xd0 { Busy }
Feb 4 07:20:10 Line kernel: hdb: drive not ready for command
Feb 4 07:20:21 Line kernel: hdb: ATAPI reset complete
Feb 4 07:20:22 Line kernel: Device 0b:00 not ready.
Feb 4 07:20:22 Line kernel: I/O error: dev 0b:00, sector 184
On Sun, 04 Feb 2001, Marko Kreen wrote:
> On Sat, Feb 03, 2001 at 11:05:44PM +0100, patrick.mourlhon@wanadoo.fr wrote:
> > Hi,
> >
> > I've never could make this CDRW ATAPI to work, if someone could
> > provide me any clue about the baby. I just said that people on the
> > kernel mailing list may care of its but. It looks like the baby didn't
> > even noticed. ;-)
>
> Compile in options 'SCSI generic', 'SCSI cdrom and 'SCSI
> emulation support' then add 'hdb=scsi' to kernel parameters.
>
> Now you can use it as SCSI cdrom, and cd-writers recognize it
> too. Eg. for cdrecord you should probably put 'dev=0,0,0' to
> command line (I assume you have no other SCSI controller).
>
>
> --
> marko
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-04 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 6:37 patrick.mourlhon [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-04 6:38 ATAPI CDRW which doesn't work patrick.mourlhon
2001-02-03 22:05 patrick.mourlhon
2001-02-04 1:06 ` Marko Kreen
2001-02-04 10:16 ` Joachim 'roh' Steiger
2001-02-04 15:15 ` Marko Kreen
[not found] ` <20010204073352.A529@MourOnLine.dnsalias.org>
[not found] ` <20010204172220.B19909@l-t.ee>
2001-02-04 16:58 ` patrick.mourlhon
2001-02-05 1:09 ` Jens Axboe
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=20010204073747.C529@MourOnLine.dnsalias.org \
--to=patrick.mourlhon@wanadoo.fr \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.