This question has been asked (by someone else) in another thread in the context of Slackware. In that thread the issue remains unresolved and seeing as how I'm using SuSE 9.1, I thought it best to restate it here.

My USB digital camera (Finepix 3800) works great on my 2.4 kernel (Mandrake 9.2) machine but not on my new 2.6 kernel SuSE 9.1 machine (AMD 64). I also have a laptop (32 bit centrino) which I believe used to detect the camera with Mandrake 9.1 but does not under the new SuSE install (I think this may be important because it may rule out the removal of a module which was not "64 bit clean"?)

A tail of /var/log/messages gives:

May 16 23:52:19 sauron kernel: usb 3-1: new full speed USB device using address 7
May 16 23:52:19 sauron kernel: usb 3-1: Product: USB Mass Storage
May 16 23:52:19 sauron kernel: usb 3-1: SerialNumber: Y-406^^^^^021119XFPX0004023756
May 16 23:52:19 sauron /etc/hotplug/usb.agent[3159]: need a device for this command
May 16 23:52:19 sauron kernel: scsi10 : SCSI emulation for USB Mass Storage devices
May 16 23:52:20 sauron kernel: USB Mass Storage device found at 7

What am I missing?

thanks!

By the looks of it, the device is being detected. You should simply be able to mount the device.

mount /dev/scsi10 /mnt/<whatever>

I agree that it SHOULD be this simple, but it's not. I believe that the output posted in my first message is indicating that no device (member of the /dev directory) has been assigned to the camera.

My /dev does not contain scsi listings and as I understand it scsi devices are assigned to sda, sdb and so forth.

I also have a Memorex Thumbdrive which works just fine. Below is the output and I have also independently verified that this device is in fact /dev/sdb1.

May 18 00:14:17 sauron /etc/hotplug/block.agent[7374]: try 1 while waiting for /block/sdb's bus_id 4:0:0:0
May 18 00:14:17 sauron kernel: sdb: sdb1
May 18 00:14:17 sauron kernel: Attached scsi removable disk sdb at scsi4, channel 0, id 0, lun 0
May 18 00:14:17 sauron kernel: USB Mass Storage device found at 2
May 18 00:14:17 sauron kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
May 18 00:14:17 sauron kernel: Attached scsi generic sg1 at scsi4, channel 0, id 0, lun 0, type 0
May 18 00:14:18 sauron /etc/hotplug/block.agent[7396]: new block device /block/sdb/sdb1
May 18 00:14:18 sauron /etc/hotplug/block.agent[7374]: waiting for /var/lock/block.agent.lock, process 7396 holds it
May 18 00:14:26 sauron /etc/hotplug/block.agent[7396]: mount by-path/usb-storage-D3A1606F3FCF5579:0:0:0p1
May 18 00:14:26 sauron /etc/hotplug/block.agent[7374]: new block device /block/sdb

Further assistance would be greatly appreciated.

In my continuing search I stumbled across this thread:
http://www.linuxquestions.org/questi...hreadid=138791

and I honestly can't tell if they are in fact the same problem.

Well, I read through the post that you linked to, and by the look of things he was having the same problem you are.

I would suggest compiling another kernel but with that patch, and see if it works for you.

Yeah I probably should give the patch a try... and although my tag says "newbie", I'm not a stranger to compiling a kernel. But the whole idea of shelling out $90 for SuSE 9.1 was to avoid exactly these issues for supported hardware (and this camera worked great in 2.4). I'm actually most concerned that if I do compile my own kernel, the automatic online updates (YOU) will no longer want to touch my kernel thereby excluding me from nifty updates for years to come.

I can wait for the camera to be supported (again) in future kernels, but it looks like they have not addressed this problem which has been present since 2.6.0.

Thanks for your help Dawizman.