From: Rick Richardson <rickr@mn.rr.com>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@suse.de>
Subject: Re: vmware 2.0.3, kernel 2.4.0 and a cdrom
Date: Sat, 24 Feb 2001 18:42:56 -0600 [thread overview]
Message-ID: <20010224184255.A4372@mn.rr.com> (raw)
On Sun, Jan 14 2001, Martin Maciaszek wrote:
> Since I installed Kernel 2.4.0 VMware is no longer able to
> recognize my cdrom drive. VMware shows a dialog box on power up
> with following content:
> [...]
> CDROM: '/dev/scd0' exists, but does not appear tobe a CDROM device.
On Mon Jan 15 2001, Jens Axboe wrote:
> Could you try with this patch, so maybe we can get some hints as to what
> is going on?
I didn't see any reply to the request to see the debug output from
the patch. So here is the output when it is applied to kernel 2.4.2:
Feb 24 18:36:11 ipcroe kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
Feb 24 18:36:11 ipcroe kernel: sr0: scsi-1 drive
Feb 24 18:36:19 ipcroe kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
Feb 24 18:36:19 ipcroe kernel: Mode Sense (10) 00 0e 00 00 00 00 00 18 00
Feb 24 18:36:19 ipcroe kernel: [valid=0] Info fld=0x0, Current sr00:00: sense key Illegal Request
Feb 24 18:36:19 ipcroe kernel: Additional sense indicates Invalid command operation code
-Rick
--
Rick Richardson rickr@mn.rr.com http://home.mn.rr.com/richardsons/
Twins Cities traffic animations are at http://members.nbci.com/tctraffic/
Important data should not be entrusted to Fisher, as it may eat it and make
loud belching noises. -- RH 7.1 beta release notes.
next reply other threads:[~2001-02-25 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 0:42 Rick Richardson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-06 1:22 vmware 2.0.3, kernel 2.4.0 and a cdrom Gregory T. Norris
2001-02-06 1:27 ` Jens Axboe
2001-02-06 1:29 ` Jens Axboe
2001-01-14 19:49 Martin Maciaszek
2001-01-14 20:29 ` Martin Tessun
2001-01-15 21:15 ` 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=20010224184255.A4372@mn.rr.com \
--to=rickr@mn.rr.com \
--cc=axboe@suse.de \
--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 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).