Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Assume this is the relevant stuff from dmesg. Still not obvious what the driver is. Is it just something about usb - which I don't know anything about?? The camera plugs in via the usb connector.
sb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 16:52:03 May 16 2005
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:07.2
PCI: Sharing IRQ 11 with 00:03.0
PCI: Sharing IRQ 11 with 00:03.1
PCI: Sharing IRQ 11 with 00:10.0
usb-uhci.c: USB UHCI at I/O 0xdce0, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:07.2-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x54c/0x4e) is not claimed by any active driver.
sb.c: USB disconnect on device 00:07.2-1 address 2
hub.c: new USB device 00:07.2-1, assigned address 3
usb.c: USB device 3 (vend/prod 0x54c/0x4e) is not claimed by any active driver.
fdisk -l gives nothing either as user or root. Looked in the corresponding /proc thing and nothing apparently usefull.
The camera's plugged in via USB. Does that mean some sort of obvious device?
Most cameras have 2 modes - Disk or USB mode, and Camera or PTP mode. The first is the USB Mass Storage Device mode, which is generally what you need to mount a USB device (unless there's a specific driver for your particular device, like the Manager driver for iRiver devices).
In Camera or PTP mode the camera is expecting a specific, narrow range of communication events, and has limited ability to respond to those events. For example, the filename must be a certain string of characters, it must be in certain folders, etc. otherwise any illegal files will not be reported. This mode is designed to be simple and foolproof since it's only supposed to handle image and video files. gphoto is coded to work with this mode natively.
Anyway, the point is that you should check to see if your camera is in the wrong mode to be used as a mass storage device.