USB Mass Storage in 2.4.0

I know there has been some talk arround this topic on this list so If I missed the answer I apologize, i just joined the list today. I read through the archive and all I could find relative to mass storage is the scsi dependancy, which I am aware of. Here is my situation.

I have a Fujufilm FX-1400 digital camera that uses the USB Mass Storage driver. I know it works because I had it working in 2.4.0-test12, and in 2.4.0 however I had a major system failure and lost my new kernel. This time arround I can not get USB Mass Storage to work. I have tried various combinations of the scsi and usb options. I thought maybe I needed SCSI Disk support as well but it didnt seem to matter. I have tried with scsi and usb mass storage as modules and as part of the kernel, still no luck. Here is what happens when I connect the camera :

Jan 10 18:49:05 t20 kernel: hub.c: USB new device connect on bus1/1, 
assigned device number 3
Jan 10 18:49:05 t20 kernel: Product: USB Mass Storage
Jan 10 18:49:05 t20 kernel: SerialNumber: Y-170^^^^^000810X0000003005237
Jan 10 18:49:06 t20 kernel: scsi0 : SCSI emulation for USB Mass Storage 
devices
Jan 10 18:49:06 t20 kernel:   Vendor:  `.À ÀòÏ  Model: \206   Ø\177.À¡# 
À ÝòÏ  Rev: ÿÿÿÿ
Jan 10 18:49:06 t20 kernel:   Type:   Scanner                            

ANSI SCSI revision: 02

Now this used to detect a scsi disk and all I had to do was mount it. I am sure there must be other conflicting config options but I just dont know what it could be. Any help would be greatly appreciated.

Robert.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

Matthew here is the info you requested, thanks for your help.

Hrm... from these logs, everything looks okay, except for the fact that the device refuses to return any INQUIRY data.

Can you reproduce the conditions under which it was working and send logs from that? Or at least remember what the /proc/scsi/scsi info looked like?

Matt

Quoted 3 lines · Robert J. Bell

Matthew here is the info you requested, thanks for your help.

Unfortunately I lost everything on my system (the one that worked) and I don't believe I ever looked in /proc/scsi/scsi because It was working and I didn't feel the need to go poking around. I had this problem initially the first time I compiled 2.4.0 but I went back and added SCSI Generic "on" and that seemed to fix it. I am just confused why it thinks this is a scanner. IS there any way to force it to detect it as a scsi disk?

I must have recompiled this kernel 50 times trying to recreate the the scenario where this worked. I can send you my .config if you think that will help.

Robert

Quoted 13 lines · Matthew Dharm

Hrm... from these logs, everything looks okay, except for the fact that the device refuses to return any INQUIRY data.

Can you reproduce the conditions under which it was working and send logs from that? Or at least remember what the /proc/scsi/scsi info looked like?

Matt

Quoted 3 lines · Robert J. Bell

Matthew here is the info you requested, thanks for your help.

Do you have an OHCI controller or an UHCI controller? I noticed that you're using the "alternate" UHCI driver... can you try this with the standard UHCI driver?

Matt

Quoted 25 lines · Robert J. Bell

Unfortunately I lost everything on my system (the one that worked) and I don't believe I ever looked in /proc/scsi/scsi because It was working and I didn't feel the need to go poking around. I had this problem initially the first time I compiled 2.4.0 but I went back and added SCSI Generic "on" and that seemed to fix it. I am just confused why it thinks this is a scanner. IS there any way to force it to detect it as a scsi disk?

I must have recompiled this kernel 50 times trying to recreate the the scenario where this worked. I can send you my .config if you think that will help.

Robert

Quoted 13 lines · Matthew Dharm

Hrm... from these logs, everything looks okay, except for the fact that the device refuses to return any INQUIRY data.

Can you reproduce the conditions under which it was working and send logs from that? Or at least remember what the /proc/scsi/scsi info looked like?

Matt

Quoted 3 lines · Robert J. Bell

Matthew here is the info you requested, thanks for your help.

I have a Fujufilm FX-1400 digital camera that uses the USB Mass Storage driver. I know it works because I had it working in 2.4.0-test12, and in 2.4.0 however I had a major system failure and lost my new kernel.