My Digitalcamera images?

[White]

I know that in Linux it is a folder where the images from a digitalcamera, that is connected to the computer, is, and I wonder what that folder is named at where it is? I have Knoppix 4.0.2 and my digitalcamera is named Kodak Easyshare CD43.The system finds the camera, Ive looked in Control Center and found it.
So, where are my images?

[sakiZ]

Cameras connect to a computer in a couple of different ways.

Either as a camera device using a special protocol or as a little USB drive. Some cameras have a switch to use either method.

I believe Kodak uses the USB drive method. A lot of cameras do.

Plug in your camera to a USB port. Turn it on. Open a console and type lsusb.

See if it shows up. You can make a mount point for it and access the camera as a drive.


sakiZ

[A. Jorge Garcia]

OK, I ran lsusb and got:

Bus 001 Device 001: ID 0000:0000

now what? How do I get my digital pictures off my Kodak Easy Share Camera on my knoppix-installered PC?

TIA,
AJG

[sakiZ]

Hmm. The camera name should show up as part of the device.

1: type modprobe usb-storage to make sure the mass storage module is loaded
Note any messages.

2.. Ok, type "dmesg"

and see if there are messages that say something like usb-storage device found and what the device is ie: /dev/sda1 or something similar

3. go to the directory /mnt and create this: /mnt/Camera

If dmesg for your device showed up as sda1 then

su to root and "mount /dev/sda1 /mnt/Camera (make sure the camera is on and connected)

substitute the device description as needed.

See if all that works.

sakiZ

[A. Jorge Garcia]

Thanx for your help!

OK, I did as you suggested and got:


dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usbcore: registered new driver usb-storage
usb 1-1: new full speed USB device using uhci_hcd and address 2

and


dmesg | grep USB
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:1f.2: Intel Corporation 82801BA/BAM USB (Hub #1)
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Initializing USB Mass Storage driver...
USB Mass Storage support registered.
usb 1-1: new full speed USB device using uhci_hcd and address 2

and


dmesg | grep hub
usbcore: registered new driver hub
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected

I don't see any mount points.... Now what?

BTW, usbview sees the camera!

TIA,
AJG

[sakiZ]

The mount point is what you CREATE. If you haven't created it, it's not there.

The mount point I gave you is /mnt/Camera

I guess I wasn't clear about that.

You could name it anything you like acutally.

Just use your file browser to go to the /mnt directory and create a folder called Camera so that you have

/mnt/Camera

I'm assuming your device is sda1 so go ahead and use that.

SakiZ

[A. Jorge Garcia]

What I meant by mount point was the correct dev. You say you assume its /dev/sda1, how can you assume that? I thought you wanted the dmesg info to figure that out. Anyway, I tried /dev/sda1 and got an invalid block device error.

Thanx for your help,
AJG

[angor]

Try opening a console *before* you plug the camera in, then run
<code>
less +F /var/log/messages
</code>
Now plug in the camera, already switched on.

(You might need to be root; syslogd needs to be running for this to work)

Hopefully you'll see some activity in the console window:
Mar 14 09:46:00 tunix kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Mar 14 09:46:00 tunix kernel: usb-storage: device found at 3
Mar 14 09:46:00 tunix kernel: usb-storage: waiting for device to settle before scanning
Mar 14 09:46:00 tunix kernel: usbcore: registered new driver usb-storage
Mar 14 09:46:00 tunix kernel: USB Mass Storage support registered.
Mar 14 09:46:05 tunix kernel: Vendor: USB Model: Flash Disk Rev: 2040
...
Mar 14 09:46:05 tunix kernel: sda: sda1
Mar 14 09:46:05 tunix kernel: sd 0:0:0:0: Attached scsi removable disk sda
Mar 14 09:46:05 tunix kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Mar 14 09:46:05 tunix kernel: usb-storage: device scan complete

In this case the device to mount is "/dev/sda1" (like suggested by sakiZ); since
sda1 didn't work for you, hopefully something else shows up.

[A. Jorge Garcia]

OK, I entered
less +F /var/log/mesages and then turned on the camera. Does it take a long time to recognize the /dev? All I get is
Mar 14 17:39:33 Collosus kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2
Mar 14 17:39:35 Collosus usb.agent[6617]: libgphoto2: loaded successfully

What gives?

BTW,
cat /proc/bus/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.12 uhci_hcd
S: Product=Intel Corporation 82801BA/BAM USB (Hub #1)
S: SerialNumber=0000:00:1f.2
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=040a ProdID=0578 Rev= 1.00
S: Manufacturer=Eastman Kodak Company
S: Product=KODAK EasyShare CX7300 Digital Camera
S: SerialNumber=CX730X1192236
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=85(I) Atr=03(Int.) MxPS= 64 Ivl=16ms

and
dmesg | grep sd returns nothing!

and
dmesg | grep uh
uhci_hcd 0000:00:1f.2: Intel Corporation 82801BA/BAM USB (Hub #1)
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 10, io base 0x0000ef80
usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: new full speed USB device using uhci_hcd and address 3
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: new full speed USB device using uhci_hcd and address 5

and
dmesg | grep oh
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)

TIA,
AJG

[sakiZ]

You say that dmesg | grep sd returns no info?

Hmmm.

With you camera plugged in an turned on open a console and type:

cat /proc/scsi/scsi

If scsi support is enabled your camera should show up.

This is how mine looks:

Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: Fujifilm Model: FinePix 1400Zoom Rev: 1000
Type: Direct-Access ANSI SCSI revision: 02

Check it out. Let us know.

sakiZ

[A. Jorge Garcia]

cat /proc/scsi/scsi says:


Attached devices:
and nothing more!

Neither can I get gphoto2 or gtkam to detect any camera....

HELP!!!

Frustrated,
AJG

[sakiZ]

That command should show you all your scsi drives/devices not just your camera.

Do your CDRom Drives show up?

Something is way off here.

sakiZ

[nad]

" I: If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none) "

Hmmm ...

And nothing in /proc/scsi/scsi .

I've been following this thread and it seems more and more likely a firmware/bios/hardware issue.

If all the BIOS USB settings are enabled, I suggest that you check the cabliing to the on board USB header. I've seen systems shipped with the data wires interchanged to cross between two case connectors. What happens is that the initial exchange of information is passed over the voltage wires, so the system knows that something has connected and what it is, but the data lines never complete negotiation.

But it is still curious that your hubs have not been registered. I would doublecheck the bios settings first.

Have you ever used these USB ports before and found then working?

[A. Jorge Garcia]

OK, you're going to want to move all the sensitive and impressionable types out of the room for a second as I have to use some fowl language.

Ready? Here goes nothing! My response:

Well, there's the rub. I have used this camera/cable/port combo in (watch out, here it comes) WinDoze (sorry) without a hitch. There, I said it. Are you happy you made me admit to using the unNamableOS (sorry)? However, this is the only thing I need WIMxP (again, sorry) for, so I'd rather not have to use it at all....

BTW, I hope I have nothing to worry about regarding the profanity above. I'm sure the words in bold will be editted out by the censors (but, of course, you can't see those words, so you don't know what I'm talking about)!

TIA,
AJG

[sakiZ]

Well, no I'm not happy you have to go back to using an aging (over 5 years old) proprietary, virus magnet.

But you gotta do what you gotta do.

Good luck.

sakiZ

[nad]

For our information, what make and model of computer is this, and any other particulars you know or care to mention.

The output of the command: lspci -vvv would be appreciated.

I'm sorry that we could not help you, but, some of these problems are intractable in this proprietary world.

[A. Jorge Garcia]

Thanx for all your help! Don't sweat it if you can't figure out my problem. Its really the Mrs that uses this box and camera combo in WimpDoze. I use my Dell GX270 PIV cluster at school. Anyway, I've gotten SO MUCH out of using KNOPPIX and you guys have HELPED ME SO MUCH over the years, that this is just one minor blip on the radar screen as far as I'm concerned! I'm such a KNOPPIX maven now that if I can't get the camera to work with KNOPPIX, I just won't use it, that's all.... I just won't touch WimpDoze anymore. Any time I do, its such a headache!

OK, I have KNOPPIX 4.0.2CD installed to hda2 (dual boot as the better half must use WIMxP). The box is a Dell Dimension 4100 PIII 866Mhz with 128MB RAM and 20GB hdd and an 8x cdr drive. Could this be like a winModem problem? In other words, my USB hardware is designed to work only with WimpDoze?


lspci -vvv > temp.txt returns:

0000:00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [88] #09 [f104]
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4

0000:00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fc900000-fe9fffff
Prefetchable memory behind bridge: f0600000-f46fffff
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fea00000-feafffff
Prefetchable memory behind bridge: f4700000-f47fffff
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-

0000:00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0

0000:00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02) (prog-if 80 [Master])
Subsystem: Intel Corp.: Unknown device 4541
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 4: I/O ports at ffa0 [size=16]

0000:00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corp.: Unknown device 4541
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin D routed to IRQ 10
Region 4: I/O ports at ef80 [size=32]

0000:00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02)
Subsystem: Intel Corp.: Unknown device 4541
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 9
Region 4: I/O ports at efa0 [size=16]

0000:01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) (prog-if 00 [VGA])
Subsystem: nVidia Corporation: Unknown device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at f2000000 (32-bit, prefetchable) [size=32M]
Expansion ROM at fe9f0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4

0000:02:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2500ns min, 2500ns max), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 3
Region 0: I/O ports at dc00 [size=128]
Region 1: Memory at feaffc00 (32-bit, non-prefetchable) [size=128]
Expansion ROM at feac0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-

0000:02:0c.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 09)
Subsystem: Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort+ <MAbort+ >SERR- <PERR-
Latency: 64 (3000ns min, 32000ns max)
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at df00 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

HTH,
AJG

[nad]

Your computer uses dell specific oem devices. This information should be forwarded to www.linux-usb.org that the device information may be included in future driver releases. The line below from your output is typical of this (Unknown device) and there are several.

0000:00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corp.: Unknown device 4541