USB Digital Camera under RedHat 8
 

HELP!

I've got a problem. how do I mount the specific usb device (my digital camera ist a konica KD-400Z?

here's some of my dmesg (in red my digital cam):

PCI: 00:10.3 PCI cache line size corrected to 64.
ehci-hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 6 ports detected
usb-uhci.c: $Revision: 1.275 $ time 15:16:26 Jul 15 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 3 for device 00:10.0
IRQ routing conflict for 00:10.0, have irq 7, want irq 3
IRQ routing conflict for 00:10.1, have irq 7, want irq 3
IRQ routing conflict for 00:10.2, have irq 7, want irq 3
IRQ routing conflict for 00:10.3, have irq 7, want irq 3
usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 7
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 3 for device 00:10.1
IRQ routing conflict for 00:10.0, have irq 7, want irq 3
IRQ routing conflict for 00:10.1, have irq 7, want irq 3
IRQ routing conflict for 00:10.2, have irq 7, want irq 3
IRQ routing conflict for 00:10.3, have irq 7, want irq 3
usb-uhci.c: USB UHCI at I/O 0xa400, IRQ 7
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 3 for device 00:10.2
IRQ routing conflict for 00:10.0, have irq 7, want irq 3
IRQ routing conflict for 00:10.1, have irq 7, want irq 3
IRQ routing conflict for 00:10.2, have irq 7, want irq 3
IRQ routing conflict for 00:10.3, have irq 7, want irq 3
usb-uhci.c: USB UHCI at I/O 0xa000, IRQ 7
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,5), internal journal
Adding Swap: 1044184k swap-space (priority -1)
hub.c: new USB device 00:10.1-1, assigned address 2
input0: USB HID v1.10 Mouse [Logitech USB Receiver] on usb3:2.0
hub.c: new USB device 00:10.1-2, assigned address 3
usb.c: USB device 3 (vend/prod 0x4e6/0x6) is not claimed by any active driver.
hub.c: new USB device 00:10.0-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x4c8/0x726) is not claimed by any active driver.
hub.c: new USB device 00:10.0-2, assigned address 3
input1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb2:3.0
input2: USB HID v1.10 Pointer [Logitech Logitech USB Keyboard] on usb2:3.1
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
usb-uhci.c: interrupt, status 3, frame# 156
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Konica Model: KD-400Z Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
ohci1394: $Rev: 693 $ Ben Collins <bcollins@debian.org>
PCI: Found IRQ 10 for device 00:07.0
PCI: Sharing IRQ 10 with 00:08.0
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[ed800000-ed8007ff] Max Packet=[2048]
ieee1394: SelfID completion called outside of bus reset!
PCI: Found IRQ 3 for device 00:0f.2
ohci1394_1: OHCI-1394 1.1 (PCI): IRQ=[3] MMIO=[eb800000-eb8007ff] Max Packet=[2048]
ieee1394: SelfID completion called outside of bus reset!
ieee1394: Host added: Node[00:1023] GUID[00e0180000098892] [Linux OHCI-1394]
usb-uhci.c: ENXIO 84000380, flags 0, urb df38c5c0, burb df38c6c0
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -6
usb-uhci.c: ENXIO 84000380, flags 0, urb df38c5c0, burb df38c6c0
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 84000380, flags 0, urb df38c6c0, burb df38c5c0
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -6
usb-uhci.c: ENXIO 84000380, flags 0, urb df38c6c0, burb df38c5c0
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 84000380, flags 0, urb df38c6c0, burb df38c5c0
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 18 ret -6a

anyone here who has a clou? would appreciate it, thanks.

greets BlinkEye

more infos
 

here's my cat /proc/scsi/scsi

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: eUSB Model: MultiMediaCard Rev:
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Konica Model: KD-400Z Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: CyberDrv Model: CW099D CD-R/RW Rev: 100M
Type: CD-ROMa

BUT if I mount /dev/scsi1 /mnt/camera I get an ERROR:

mount: Gerätedatei /dev/scsi1 doesn't exist.

What's up???

this is some of my /proc/bus/usb/devices

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=04c8 ProdID=0726 Rev= 1.00
S: Manufacturer=KONICA CORPORATION
S: Product=KD-400Z
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

Did you create a directory/folder called /mnt/camera and give it the correct permissions?

'scsi1' is the SCSI channel that your camera is connected to, not the device. The device is likely to be something like 'sda1', 'sdb1' or something like that, depending on your setup. You need to mount the device, not the channel. So, you would be looking to:

mount -t vfat /dev/sda1 /mnt/camera

You use 'vfat' if your camera uses Windows-type formatting, or you could use 'auto' and let the kernel decide what to do, depending on what it finds. As I said before, 'sda1' might need to be something different, depending on your setup, including other hardware - especially SCSI - installed on your system. You need to have created '/mnt/camera' (you could use any name here you like) beforehand and given it correct permissions, or else only root will be able to access the camera.

With your camera plugged in, you should have a listing under /dev for sda, sdb, sda1 and sdb1. Given that your camera is on scsi channel 1, it should show up as scsi device sdb, and it should point to scsi/host1/bus0/target0/lun0/disk and its filesystem - sdb1 - should show up as scsi/host1/bus0/target0/lun0/part1. Whatever, look for the device letter that shows up as host1 and ends with 'disk' and 'part1'. By that reasoning, you would be using 'sdb1' in the above mount command.

This is how I got my camera working:

http://www.linuxquestions.org/questi...threadid=74030

You might find the procedure useful in working out how to go about it.

yeah, I did create /mnt/camera folder and gave it the right permission.

THANKS SO FAR.

as the problem seems to be is to find out on which device my camera is plugged in. I'm currently working on the suggestion of geoff_f , but I don't get wiser with the /dev folder, I don't see which device is the one for my camera.

geoff_f
 

to geoff_f :

woah, you made one hell of a great thread about cameras that will save me a lot of trouble and time (www.linuxquestions.org/questions/showthread.php?s=&threadid=74030) . thanks a lot.

still, I tried to mount several scsi devices - and get every time the message :
"mount: /dev/sda1 ist kein gültiges blockorientiertes Gerät" (sorry, can't translate that properly :) )

I have two DVD/CDRW drives (the CDRW drive is attached to scd0 and and the DVD drive to hdd (had to change that in order to use xine)

I'm no linguist, but this is probably:

mount: /dev/sda1 is not a valid block device

And, sorry, I can't help you there either, as this 'not a valid block device' message has stumped me in other threads. The only thing that may be a factor is kernel version. I'm using 2.4.21-0.13mdk, which is something like a pre-release of 2.4.21. Maybe a kernel upgrade could help. It would be good if someone could shed some light on this 'not a valid block device' problem that a lot of people are having with their digital cameras.

<edit> added 'valid' to error message.

jep, would be grateful. mayhap I try a kernel upgrade - nevertheless

somebody must know the answer of
besides, you're apparently a linguist.

I believe that this is a generic mount error message that can result from a number of situations, so it's not very helpful in diagnosing a specific problem.

I'm not sure how to determine the SCSI device from the information in /proc/scsi/scsi -- but did you try mounting it as 'sdb1' instead? (or 'sdc1', etc...)

:cool:

yeah I tried. same error message over and over. but thanks for the hint

Why not use a recent release of GTKam/GPhoto2 to access your camera? I think that'll mount it for you too, because I remember it put a link to browse the files on my desktop when using KDE. :)

yeah, I tried allready. the problem is, that my camera isn't supported by gPhoto (neither with the recent version). so I need additional help...

how about just using a cf card reader? I just bought one yesterday and it works like a charm.

Which kernel are you using? I have a similar problem and I saw a post which said that newer kernels (2.4.20 I think) will have increased usb digital camera support.

Have you tried your manufacturer's website for drivers/assistance?