LinuxQuestions.org - Camera won't mount

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Camera won't mount (https://www.linuxquestions.org/questions/linux-hardware-18/camera-wont-mount-249065/)

Camera won't mount

I'm having problems mounting my digital camera. It's a Sanyo Xacti VPC-S3 and I'm running Slackware 9.1. USB support is compiled into the kernel and my USB joypad works fine.

lsmod says (uninteresting modules not listed):

Code:

ide-scsi              10224  0 

scsi_mod              57172  1  [ide-scsi]

When I switch the camera on and tell it to connect to the pc dmesg says

Code:

hub.c: new USB device 00:11.2-1, assigned address 3

usb.c: USB device 3 (vend/prod 0x474/0x222) is not claimed by any active driver.

And then the camera just sits there saying "connecting card reader" until I load the module usb-storage. When I do, the screen on the camera goes black and that's exactly what happens when Windows detects the camera, so I guess it's a good thing.

dmesg now gives me

Code:

Initializing USB Mass Storage driver...

usb.c: registered new driver usb-storage

scsi1 : SCSI emulation for USB Mass Storage devices

  Vendor: SANYO    Model: S3                Rev: 1.00

  Type:  Direct-Access                      ANSI SCSI revision: 02

WARNING: USB Mass Storage data integrity not assured

USB Mass Storage device found at 3

USB Mass Storage support registered.

Now, a new directory called usb-storage-0 pops up in /proc/scsi. It contains a file "1":

Code:

  Host scsi1: usb-storage

      Vendor: SANYO

      Product: SANYO DIGITAL CAMERA

Serial Number: 000078357296

    Protocol: Transparent SCSI

    Transport: Bulk

        GUID: 047402220000000078357296

    Attached: Yes

By now I'm thinking I should be able to mount the camera just by typing mount /dev/sdxy /mnt/camera but I just get "mount: /dev/sda1 is not a valid block device" (and it's the same for all sda sdb etc).
Turning the camera off and on again it says "connecting card reader" for ever and ever.

What am I missing here?

Try

Code:

echo 'scsi add-single-device 0 0 0 0' > /proc/scsi/scsi

Quote:

Originally posted by ToniT
Try

Code:

echo 'scsi add-single-device 0 0 0 0' > /proc/scsi/scsi

Thanks, but it doesn't seem to make any difference. :(
What should be happening?

That should refresh the scsi driver to scan for new devices.

Is the usb-device seen when you cat the /proc/scsi/scsi?
If yes, what does the /proc/partitions look like, does it get into there?

Do you have other scsi devices? If no, can you access /dev/sda now?
(eg. "cat /dev/sda | hexdump -C")

Ah, one more thing. Do you have sd_mod loaded (a support for scsi disks)?

When attached what does

Code:

fdisk -l

say.

Quote:

Originally posted by ToniT
That should refresh the scsi driver to scan for new devices.

Is the usb-device seen when you cat the /proc/scsi/scsi?
If yes, what does the /proc/partitions look like, does it get into there?

Do you have other scsi devices? If no, can you access /dev/sda now?
(eg. "cat /dev/sda | hexdump -C")

Yeah, it's in /proc/scsi/scsi:

Code:

root@brinstar:/proc/scsi# cat scsi

Attached devices: 

Host: scsi1 Channel: 00 Id: 00 Lun: 00

  Vendor: SANYO    Model: S3              Rev: 1.00

  Type:  Direct-Access                    ANSI SCSI revision: 02

/proc/partitions has nothing on it though. It's got my IDE partitions and nothing more.
I have no other scsi devices unless you count the joypad, but that goes into /dev/input/js0.

Quote:

Originally posted by Brian1
When attached what does fdisk -l say.

It's a lot like /proc/partitions (which turns out to be its source of information!).

Quote:

Originally posted by ToniT
Ah, one more thing. Do you have sd_mod loaded (a support for scsi disks)?

Now we're getting somewhere! I don't! :o
Turns out I haven't even compiled it as a module. I'll get right to it.

Bloody hell, it works! And it works wonderfully! :D
ToniT, I'm in your debt. Thank you! And thank you Brian1 as well!