From: "Martin G. McCormick" <martin@dc.cis.okstate.edu>
To: blinux-list@redhat.com
Subject: Still Having Fun with SCSI Emulation.
Date: Thu, 10 Jan 2002 11:23:57 -0600 [thread overview]
Message-ID: <200201101723.g0AHNvg60743@dc.cis.okstate.edu> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]
I built my kernel which is 2.217 and selected SCSI
support. I also selected SCSI emulation as there is no SCSI
hardware. There is an ATAPI CDROM and the new Plextor CDRW drive
will simply plug in to a remaining IDE slot on one of the
controllers which are in the system.
Because of that, I also selected SCSI CDROM support
and the generic support. The only thing I didn't select was any
hardware SCSI controllers, hard disk support or tape support.
My /dev directory shows SG devices as in /dev/sg1, etc.
When I boot, the dmesg output says the following
regarding SCSI devices:
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
scsi : 1 host.
scsi : detected total.
I am not sure if there should be something in the last
line that says
scsi : detected total.
Then, I try something from root like
cdrecord -scanbus
I get
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
Well, I was root when I did that and that was cdrecord
-scanbus.
If I try a lucky guess like cdda2wav -D/dev/sg1, I get
the following error:
cdda2wav: Bad file descriptor. Cannot open SCSI driver.
open(/dev/sg1) in file interface.c, line 474
Use the script scan_scsi.linux to find out more.
Probably you did not define your SCSI device.
You can scan the SCSI bus(es) with 'cdrecord -scanbus'.
Set the CDDA_DEVICE environment variable or use the -D option.
You can also define the default device in the Makefile.
The debug option for cdrecord told me that the device
spec points to a null pointer which means that it is not set yet
and explains why nothing else works. I could certainly set the
device name if I knew one that works.
By the way, I am using a 2.217 kernel because the 2.4x
kernels seem to not respond to aumix settings. I think I'll mess
with one problem at a time. I did compile a 2.410 kernel and had
exactly the same SCSI weirdness.
I think I maybe have missed a step or are
misunderstanding instructions in the documentation. Right now,
nothing quite adds up.
next reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin G. McCormick [this message]
` Janina Sajka
Martin G. McCormick
` Janina Sajka
Martin G. McCormick
` Janina Sajka
Martin G. McCormick
Martin G. McCormick
` Willem van der Walt<vdwaltw@health.gov.za>
Martin McCormick
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=200201101723.g0AHNvg60743@dc.cis.okstate.edu \
--to=martin@dc.cis.okstate.edu \
--cc=blinux-list@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).