On Mon, 2003-02-17 at 13:27, mike wrote:
> Hey guys, thanks for the feedback.
> 
> I've already tried using /dev/sda1 but I get an error that says
> '/dev/sda1 is not a valid block device'
> 
> Using 'dmesg | tail' I got the follwing.
> 
> [root@localhost root]# dmesg | tail
> usbdevfs: process 2496 (lsusb) did not claim interface 0 before use
> NTFS: Unicode name contains a character that cannot be converted to
> chosen character set. Remount with utf8 encoding and this should work.
> usbdevfs: process 3461 (lsusb) did not claim interface 0 before use
> usbdevfs: process 3463 (lsusb) did not claim interface 0 before use
> usb-uhci.c: interrupt, status 2, frame# 1965
> ohci1394: pci_module_init failed
> usb.c: USB disconnect on device 2
> hub.c: USB new device connect on bus3/1, assigned device number 4
> WARNING: USB Mass Storage data integrity not assured
> USB Mass Storage device found at 4

Looks like the kernel can't properly detect what the device is.  It
could be either a slight incompatibility between linux and the usb hub
(built-in) or an incompatibility with the device.  From the log, it
looks like linux just can't talk to the device.  You'll want to do some
more searching on google to get more information on your camera and
linux.

Personally, I prefer a usb memory reader.  I use compact flash right now
and I find it's much more convenient to pull the cartridge and pop it in
my reader and mount that as a drive.

When things go right, you should see a message in the log about /dev/sd
something (a,b,c etc).  Then you know the device is properly captured.  

Michael.

> 
> *It looks like the device was detected at '4' but I don't know what that
> means, or what I should enter into the fstab file...
> 
> 
> 
> 
> 
> 
> _______________________________________________
> newbies mailing list
> [EMAIL PROTECTED]
> http://phantom.byu.edu/cgi-bin/mailman/listinfo/newbies

_______________________________________________
newbies mailing list
[EMAIL PROTECTED]
http://phantom.byu.edu/cgi-bin/mailman/listinfo/newbies

Reply via email to