Running cdrecord -scanbus as root (cdrecord version 1.10, redhat 7.2,
kernel 2.4.9-31) & having a problem with it.  The program simply displays
the following text & then sits there for hours on end:

Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J?rg Schilling

Nothing else happens.  I've even gone so far as to fire it up before I go
to bed & then come back in the morning & it's still sitting there like that.

Process doesn't seem to be out of hand, no performance hit on my machine.  
However, I'm unable to kill the process.  'kill -9 pid' won't phase it.  
The process keeps running & running & running until I finally reboot the
box.

I'm trying to get a USB cd drive to work, & all the docs keep coming back
to cdrecord -scanbus, so that's why I'm trying to run it.

Any idea what this would be indicative of, & how to make it work properly?

Thanks!

On Sat, 30 Mar 2002 09:44:34 -0500, $uRoot staggered into the Black Sun
and said:

Problem with the USB modules somewhere, it sounds like.  You didn't post
enough information for anyone to just hand you a fix, though, so please
post the following items:

0. The output of "dmesg | tail -15" as executed right after executing
   "cdrecord -scanbus"
1. The output of "lsmod"
2. The make and model of the USB CD-RW you're trying to use

If you are using the "uhci" module for USB chipset support, use the
"usb-uhci" module instead.  

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com     /  "He is a rhythmic movement of the
-----------------------------/    penguins, is Tux." --MegaHAL

Dances With Crows hollered:

Thanks for the reply.

It's a LaCie USB CD-RW (aka Mitsumi 4804TE).  I had posted something a few
days ago regarding some initial questions I had...  Had included quite a
bit of info in that post, here it is if it's of any additional help:

http://groups.google.com/groups?selm=3C9FE818.1040705%40thinktankdeco...

Since posting that, I've since updated my kernel from 2.4.7-10 to 2.4.9-31.

Basically, this is just an IDE burner in an external case with a USB
interface.  I've thought about taking the drive out of the external case &
putting it inside the machine on the IDE bus.  Would that be a step in the
right direction???

Here's the other info you asked about.

dmesg | tail -15

ISO 9660 Extensions: RRIP_1991A
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=905, generation=2
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=911, generation=2
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=915, generation=2
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0,  type -1
resize_dma_pool: unknown device type -1
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=905, generation=3
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=911, generation=3
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=915, generation=3

lsmod

Module                  Size  Used by    Not tainted
sg                     28932   1  (autoclean)
ide-cd                 27072   2  (autoclean)
cdrom                  28672   0  (autoclean) [ide-cd]
emu10k1                49764   1  (autoclean)
soundcore               4452   4  (autoclean) [emu10k1]
nls_iso8859-1           2816   4  (autoclean)
smbfs                  37024   3  (autoclean)
parport_pc             14916   1  (autoclean)
lp                      6336   0  (autoclean)
parport                25568   1  (autoclean) [parport_pc lp]
autofs                 11620   0  (autoclean) (unused)
ne                      7488   1
8390                    6752   0  [ne]
usb-storage            55788   1
scsi_mod               98840   2  [sg usb-storage]
usb-uhci               21732   0  (unused)
usbcore                51936   1  [usb-storage usb-uhci]
ext3                   62624   2
jbd                    41156   2  [ext3]

Now, from looking at dmesg, I'm assuming the sg0 is the usb device??  I had
been trying to mount it as scd(0-7)...  trying to mount it now as

mount -t iso9660 /dev/sg0 /mnt/cdrom2
/dev/sg0 is not a block device

So, that's where I'm at.  Still wondering if it would be easier just to
throw the burner inside the machine???

On Sat, 30 Mar 2002 15:11:35 -0500, $uRoot staggered into the Black Sun
and said:

Don't know whether that'd work or not.  Might be something to try, but
some of those external cases are a pain to open up.

[snip weird Samba errors--you may wish to look at those later, though]

That looks odd.  Scanning the code in drivers/scsi/scsi_dma.c , you
should only get that error if the SCSI subsystem can't recognize what
type of device it is.  This is possible if the usb-storage module
doesn't recognize the device correctly, or if the proper #defines
haven't been set when the usb-storage module was compiled.  grepping
through drivers/usb/storage/* shows that at least one type of Mitsumi
USB CD-RW is in the "unusual_devs.h" file.

I would suggest upgrading the kernel, probably not from Redhat's site,
but from the official kernel source tree.

Using usb-uhci, that's good.  Odd that sr_mod isn't loaded, or does
Redhat build that directly into their stock kernels?  Might want to try
modprobing sr_mod anyway.

Most SCSI and pretend-SCSI devices have two identities, the "block
device" that you normally use, and the "generic device" you can use to
get more control over the hardware.  SCSI CD-RWs use both the block
device, /dev/scd[0-9] , and the generic device, /dev/sg[0-9] .  You read
from and mount the block device, while you use the generic device to
write.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com     /  "He is a rhythmic movement of the
-----------------------------/    penguins, is Tux." --MegaHAL