Michael Leone on Tue, 12 Dec 2000 13:37:41 -0500


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] USB sony spressa CDR


> > "Since the mass storage driver presents the USB device as a SCSI device,
> > you need to turn on SCSI support, which is under SCSI support in the
> > configuration script. You should also turn on subordinate options as
> > appropriate to your mass storage device - usually one or more of SCSI
disk
> > support, SCSI tape support, SCSI CD-ROM (this would be you) support and
> > SCSI generic support"
>
> I did this when I compiled the kernel.  Should they be set up as modules
> instead of specifying Y for yes?

I compile mine directly into the kernel; some people prefer modules, to keep
the size of the kernel down.

>
> In demesg this is what is says about scsi:
> scsi : 0 hosts.
> scsi : detected total.

Well, that part is right, since you don't have any REAL scsi adapters.

>
> USB stuff is loaded last
>
> Here's what I get in messages.log:
>
> kernel: usb.c: registered new driver usbdevfs
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb.c: registered new driver hub
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb-uhci.c: $Revision: 1.237 $
time
> 10:54:52 Dec 12 2000
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb-uhci.c: High bandwidth mode
> enabled
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb-uhci.c: USB UHCI at I/O
0x3400,
> IRQ 11
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb-uhci.c: Detected 2 ports
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb.c: new USB bus registered,
> assigned bus number 1
> Dec 12 12:10:33 Jwelsh_Notebook kernel: usb.c: USB new device connect,
> assigned device number 1
> Dec 12 12:10:33 Jwelsh_Notebook kernel: hub.c: USB hub found
> Dec 12 12:10:33 Jwelsh_Notebook kernel: hub.c: 2 ports detected
> Dec 12 12:10:33 Jwelsh_Notebook usb: Loading USB interface succeeded
> Dec 12 12:10:33 Jwelsh_Notebook usb: Mount USB filesystem succeeded
> Dec 12 12:10:34 Jwelsh_Notebook kernel: usb.c: USB new device connect,
> assigned device number 2
> Dec 12 12:10:34 Jwelsh_Notebook kernel: usb.c: USB device 2 (prod/vend
> 0x4e6/0x101) is not claimed by any active driver.

This may be a problem. According to the web page, Vendor 0x4e6 is

04e6  Shuttle Technology Inc.

and device 0x101 is

 0101  E-USB ATA Bridge

which is something funky and specific to your laptop, since I don't see this
on mine. At a guess, I'd say this is the hardware that acts as a bridge
between your USB bus and your ATA (or IDE) bus. And Linux doesn't know what
to make of it.

> Dec 12 12:10:35 Jwelsh_Notebook kernel: usb.c: registered new driver
> usb-storage
> Dec 12 12:10:35 Jwelsh_Notebook kernel: USB Mass Storage support
registered.
> Dec 12 12:10:35 Jwelsh_Notebook usb: Loading USB storage succeeded

This means (I think) that you choose "USB mass storage support" when
compiling the kernel.

> >
> Tried both options, no joy
>
> One thing concerns me, is that I don't see any actual device ID's for the
cd
> burner/reader.  I would guess there should be...right?

Try 'cat /proc/bus/usb/devices' - does it show up there?

(BTW, realize that I'm just about as much of a total newbie at the
USB-on-Linux stuff as you are, but we'll see what we can come up with :-)

My log: (I have 2 USB ports on motherboard; I have an external 4 port hub
(as expansion)); into this, I have plugged in

a MS SideWinder joystick
an Epson Perfection 636U scanner
an Epson Photo Stylus 870 printer.

I compiled in support for HID (Human Interface Device [necessary for
joysticks and such]), USB printer, USB scanner, and Wacom
(I added in Wacom support - that's a drawing tablet - because I wanna buy
one in future)

Dec 12 01:04:53 dude kernel: usb.c: registered new driver hid
Dec 12 01:04:53 dude kernel: usb.c: registered new driver usblp
Dec 12 01:04:53 dude kernel: usb.c: registered new driver usbscanner
Dec 12 01:04:53 dude kernel: scanner.c: USB Scanner support registered.
Dec 12 01:04:53 dude kernel: usb.c: registered new driver usbdevfs
Dec 12 01:04:53 dude kernel: usb.c: registered new driver hub
Dec 12 01:04:53 dude kernel: usb-uhci.c: $Revision: 1.237 $ time 18:39:07
Dec 1
Dec 12 01:04:53 dude kernel: usb-uhci.c: High bandwidth mode enabled
Dec 12 01:04:53 dude kernel: usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 5
Dec 12 01:04:53 dude kernel: usb-uhci.c: Detected 2 ports
Dec 12 01:04:53 dude kernel: usb.c: new USB bus registered, assigned bus
number 1
Dec 12 01:04:53 dude kernel: usb.c: USB new device connect, assigned device
number 1
Dec 12 01:04:53 dude kernel: Product: USB UHCI Root Hub
Dec 12 01:04:53 dude kernel: SerialNumber: d400
Dec 12 01:04:53 dude kernel: hub.c: USB hub found
Dec 12 01:04:53 dude kernel: hub.c: 2 ports detected
Dec 12 01:04:53 dude kernel: usb.c: registered new driver wacom

Then later I see

Dec 12 01:04:53 dude kernel: usb.c: USB new device connect, assigned device
number 2
Dec 12 01:04:53 dude kernel: hub.c: USB hub found
Dec 12 01:04:53 dude kernel: hub.c: 4 ports detected
Dec 12 01:04:53 dude kernel: usb.c: USB new device connect, assigned device
number 3
Dec 12 01:04:53 dude kernel: Manufacturer: Microsoft
Dec 12 01:04:53 dude kernel: Product: Microsoft SideWinder Precision Pro
(USB)
Dec 12 01:04:53 dude kernel: usb-uhci.c: interrupt, status 3, frame# 1822
Dec 12 01:04:53 dude kernel: js0: Joystick device for input0
Dec 12 01:04:53 dude kernel: input0: USB HID v1.00 Joystick [Microsoft
Microsoft SideWinder Precision Pro (USB)] on usb1:3.0
Dec 12 01:04:53 dude kernel: Adding Swap: 465844k swap-space (priority -1)
Dec 12 01:04:53 dude kernel: usb.c: USB new device connect, assigned device
number 4
Dec 12 01:04:53 dude kernel: Manufacturer: EPSON
Dec 12 01:04:53 dude kernel: Product: USB Printer
Dec 12 01:04:53 dude kernel: SerialNumber: W03160002151022560
Dec 12 01:04:53 dude kernel: printer.c: usblp0: USB Bidirectional printer
dev 4 if 0 alt 0
Dec 12 01:04:53 dude kernel: usb.c: USB new device connect, assigned device
number 5
Dec 12 01:04:53 dude kernel: Manufacturer: EPSON
Dec 12 01:04:53 dude kernel: Product: Perfection636

But I don't have this "bridge" device you have. Think that's your problem;
once you can get that device recognized, it may read any actual external USB
devices you have THRU it. Then - hopefully - you should be OK.




______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug