From: Micha Feigin <michf@post.tau.ac.il>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc3 lost cdrom
Date: Sun, 3 Oct 2004 04:43:35 +0200 [thread overview]
Message-ID: <20041003024335.GA4070@luna.mooo.com> (raw)
In-Reply-To: <1096766301.1375.9.camel@krustophenia.net>
On Sat, Oct 02, 2004 at 09:18:21PM -0400, Lee Revell wrote:
> On Sat, 2004-10-02 at 22:10, Micha Feigin wrote:
> > I seem to have lost cdrom support through scsi emulation, any ideas?
> > (its a burner, and drive detection with xcdroast in ide mode is
> > terrible, takes minutes).
>
> Sounds like an xcdroast bug. If they finally dropped the scsi emulation
> it would be a welcome change. It does not make sense to have to use
> some fake SCSI bus to burn CDs on an IDE system.
Not sure if its a bug or a feature ;-) but it does give the message
that its going to take a long time and if I want to make it shorter I
should use scsi emulation and not ide. I don't understand enough about
these to know where the problem lies I'm afraid.
Anyway I got the output of dmesg and was hoping it could shed some more
light on the problem. Seems like a problem with isofs from that:
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 5
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
attempt to access beyond end of device
sr0: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
attempt to access beyond end of device
sr0: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
attempt to access beyond end of device
sr0: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
attempt to access beyond end of device
sr0: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
end_request: I/O error, dev sr0, sector 64
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
end_request: I/O error, dev sr0, sector 64
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
>
> Lee
>
>
> +++++++++++++++++++++++++++++++++++++++++++
> This Mail Was Scanned By Mail-seCure System
> at the Tel-Aviv University CC.
>
next prev parent reply other threads:[~2004-10-03 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 2:10 2.6.9-rc3 lost cdrom Micha Feigin
2004-10-03 1:18 ` Lee Revell
2004-10-03 2:43 ` Micha Feigin [this message]
2004-10-04 6:19 ` Jens Axboe
2004-10-05 23:28 ` Micha Feigin
2004-10-05 23:37 ` Micha Feigin
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=20041003024335.GA4070@luna.mooo.com \
--to=michf@post.tau.ac.il \
--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.