public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
* Re: Still Having Fun with SCSI Emulation.
@  Martin G. McCormick
   ` Janina Sajka
  0 siblings, 1 reply; 10+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: blinux-list

	I have one last question before I dive back in to this
this weekend.

	If the SCSI support is compiled in rather than modules,
does that change the need for the lilo.conf directive that
Janina is referring to?

	There is nothing at all regarding SCSI in my lilo.conf.

	My understanding of modules versus compiled is that it is
all supposed to function the same when up and running.  The only
difference is that your kernel grows or shrinks by loading and
unloading portions of code as needed rather than just having them
sitting there unused part of the time.

Martin

Janina Sajka writes:
>I have it as modules, and I have had no dificulty with it since at least 
>2.2.12. I have it on my IBM Thinkpad T20, where I have a swappable ide 
>burner.




^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: Still Having Fun with SCSI Emulation.
@  Martin McCormick
  0 siblings, 0 replies; 10+ messages in thread
From: Martin McCormick @  UTC (permalink / raw)
  To: blinux-list

	I want to thank everyone on this list who has suggested
things for me to try to get my CD burner working under Linux.
The magic turned out to be in the device name.  Someone from this
list who I have thanked profusely, suggested for me to try the
raw SCSI designator as reported by  cdrecord -scanbus.  I did and
voila, it works.

	It certainly pays to be persistent.  I have been beating
on this problem since December 26 and lightly studying the issue
since long before.

	Again thanks to several of you and I hope I can repay in
kind soon.

	The only piece of advice I can give sounds kind of corny,
but it is to not give up.  This really has nothing to do with the
purpose of this list as the access to all the software is perfect
standard UNIX input and output so your talking or Braille
interfaces will, of course, tell you how things are going.

	The only thing more impressive than the open-source
software is the generosity of UNIX users in helping others.  If
one is trying to help him or herself, I have found that many UNIX
users are more than glad to lend a hand.

Martin McCormick




^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: Still Having Fun with SCSI Emulation.
@  Martin G. McCormick
   ` Willem van der Walt<vdwaltw@health.gov.za>
  0 siblings, 1 reply; 10+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: blinux-list

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3560 bytes --]

	I made a lot of progress and what I found may help some
people so here it is as briefly as I can make it.

	First, I will sound like a politician here and say that
everybody was right to some extent on configuring SCSI emulation
in the kernel.  My big mistake was in compiling in SCSI disk
support.  This killed the CDROM SCSI emulation.  When I took out
the SCSI disk support, the SCSI channel appeared.

	I still had terrible problems with cdda2wav and
cdparanoia and they both did the same thing.

	Both tried to work using /dev/scd0 as the scsi device,
but the system groaned and sputtered and the audio was full of a
wraspy sound which was basically a break in the sound about 75
times per second.  This is the sector rate, but you shouldn't
hear it.  I ran cdparanoia for 20 or 30 minutes once and it
didn't even rip one song completely.

	Since I now had SCSI emulation, I decided to install the
Plextor CDRW drive.  I guess the other drive is simply not
capable of CDDA playback because the system now can download an
entire CD in 7 minutes flawlessly with perfect audio just like it
is supposed to.

	Both cdda2wav and cdparanoia now seem to work perfectly
but I seem to still be snatching defeat from the jaws of victory.

	It was time to burn a CDRW disk with a file system so I
put in a brand new CDRW which was included with the drive as a
sample.
I got mkisofs to produce a mountable image so the last step was
to feed that to cdrecord.  I used the following command.

mkisofs -l -R -q /home/martin |cdrecord -dev=/dev/scd0:0,0 -dummy -

	I held my breath and got the following error which was
the first error I had seen using the new drive:

cdrecord: Cannot do inquiry for CD/DVD-Recorder.
cdrecord: Success. test unit ready: scsi sendcmd: fatal error
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
scsidev: '/dev/scd0:0,0'
devname: '/dev/scd0'
scsibus: 0 target: 0 lun: 0
Using libscg version 'schily-0.1'
CDB:  00 00 00 00 00 00
cmd finished after 0.000s timeout 40s

	The order of the output lines from cdrecord is a little
different than they normally display, but I captured standard
error and standard output and they don't arrive at the same time.
If I use cdparanoia and test the drive, I get good output

cdparanoia III release 9.7 (December 13, 1999)
(C) 1999 Monty <monty@xiph.org> and Xiphophorus

Checking /dev/sg0 for cdrom...
	Testing /dev/sg0 for cooked ioctl() interface
		/dev/sg0 is not a cooked ioctl CDROM.
	Testing /dev/sg0 for SCSI interface
		generic device: /dev/sg0
		ioctl device: /dev/scd0
		CDROM sensed: PLEXTOR CD-R   PX-W1210A 1.08 

Checking for SCSI emulation and transport revision...
	Drive is ATAPI (using SCSI host adaptor emulation)

Checking for MMC style command set...
	Drive is MMC style
004: Unable to read table of contents header

Unable to open disc.  Is there an audio CD in the drive?

	That last part about the audio CD is due to there being
the new CDRW which had not yet been recorded yet.  If I put an
audio CD in, it reads the table of contents just fine.

	Has anybody any ideas as to what this last nasty problem
is?

	By the way, if you compile the SCSI emulation support in
to the kernel, the append statements in lilo.conf don't seem to
do anything.  That probably is necessary to make the module load,
but I tried it with and without and nothing changed.

	Thanks to Janina and all for your good suggestions.  You
have kept me beating my head on this brick wall until I have made
a dent at least.  I'm still not all the way through, yet.
Martin McCormick




^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: Still Having Fun with SCSI Emulation.
@  Martin G. McCormick
  0 siblings, 0 replies; 10+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: blinux-list

	Many thanks for the example.  I'll adapt it to my
situation and seeif that helps.

Martin




^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: Still Having Fun with SCSI Emulation.
@  Martin G. McCormick
   ` Janina Sajka
  0 siblings, 1 reply; 10+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: blinux-list

Janina Sajka writes:
>Do you reference ide-scsi in your lilo.conf?

	No, and if I was a gambler, I would bet that there in
lies the problem.

> I have it as:
>
>append = "hdc=ide-scsi hde=ide-scsi"

	I remember reading that directive in the HOWTO or
somewhere that dealt with this topic and I was kind of confused at
the time or maybe half asleep and thought that this was something
taken care of in the kernel configuration.

	Do you have the SCSI emulation and driver set up as
loadable modules or did you just reply  y  to having that module
become an integral part of the kernel?  That is how I have done
the SCSI configuration because it is something that will more
than likely get used all the time.  Except for the increase in
kernel size, it is probably more efficient to have things like
that compiled in.

	As I said, this may be the missing link that explains why
nothing seems to tie the SCSI support to what is actually
there.

	Again thanks for the reminder.  I certainly hope that
that is what's missing.  This system just isn't that unusual.

Martin




^ permalink raw reply	[flat|nested] 10+ messages in thread
* Still Having Fun with SCSI Emulation.
@  Martin G. McCormick
   ` Janina Sajka
  0 siblings, 1 reply; 10+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: blinux-list

[-- 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.




^ permalink raw reply	[flat|nested] 10+ messages in thread
end of thread, other threads:[~ UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 Still Having Fun with SCSI Emulation Martin G. McCormick
 ` Janina Sajka
  -- strict thread matches above, loose matches on Subject: below --
 Martin McCormick
 Martin G. McCormick
 ` Willem van der Walt<vdwaltw@health.gov.za>
 Martin G. McCormick
 Martin G. McCormick
 ` Janina Sajka
 Martin G. McCormick
 ` Janina Sajka

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).