Re: problem mounting digital card reader

From: tony (tony_at_home.com)
Date: 04/05/04


Date: Mon, 05 Apr 2004 12:30:42 +1000

Dances With Crows wrote:
> On Sat, 03 Apr 2004 11:23:10 +1000, tony staggered into the Black Sun
> and said:
>
>>I have a lexar digital card reader to view pictures from my digital
>>camera. My problem is that I can't mount the reader on my Redhat 8
>
> [snip]
>
>>Keyboard, mouse and infra-red reader all of which were detected by
>>Redhat and are working correctly.
>
>
> Sounds like your base USB support is loaded and it's working properly
> (assuming the mouse and keyboard are USB; you didn't specify that.)
>
> If all the right modules are loaded, plug in the card reader and do
> "dmesg | tail -30". Look at the output; if you see lines like "device
> FOO:BAR is not claimed by any active driver", then the first thing to do
> is to upgrade your kernel from a REdhat-approved RPM or from a tarball
> from kernel.org. Redhat 8 used an old kernel, and it's possible that
> your card reader isn't on the supported USB device list in that old
> kernel.
>
Thanks for your help. Not being too clever with Linux I've been feeling
my way in the dark mostly with this. I guess I have been spoilt a bit
with the plug and its ready to use style of windows. I imagined it would
be like the CD player on Red Hat, where you insert the disc and when the
icon appears you click the icon to read the contents

I found the following after running the dmesg, so it looks as though
everthing is being 'found' by the OS. I assume the mass storage device
found is the card? so do I still have to mount this to read the pictures
on it? If So which block device do you use to mount this card? I've
tried /dev/sda1
I've got kernel 2.4.18-14 if thats any help

hub.c: USB new device connect on bus1/2, assigned device number 6
usb.c: USB device 6 (vend/prod 0x5dc/0xb002) is not claimed by any
active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
usb-uhci.c: interrupt, status 2, frame# 2022
usb_control/bulk_msg: timeout
scsi1 : SCSI emulation for USB Mass Storage devices
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 6
USB Mass Storage support registered.
usbdevfs: USBDEVFS_CONTROL failed dev 6 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 6 rqt 128 rq 6 len 18 ret -84
usb.c: USB disconnect on device 6
hub.c: USB new device connect on bus1/2, assigned device number 7
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 7



Relevant Pages

  • Re: USB flash drive not automounting or mounting
    ... Let me try to mount it: ... SCSI device sdb: 487424 512-byte hdwr sectors ... USB Mass Storage device found at 31 ...
    (Debian-User)
  • Re: Mounting an iPod via USB
    ... > Initializing USB Mass Storage driver... ... WARNING: USB Mass Storage data integrity not assured ... USB Mass Storage device found at 2 ... usb.c: USB disconnect on device 00:10.4-1 address 2 ...
    (Debian-User)
  • USB flash drive not automounting or mounting
    ... Let me try to mount it: ... SCSI device sdb: 487424 512-byte hdwr sectors ... USB Mass Storage device found at 31 ...
    (Debian-User)
  • Re: Is extra USB event possible in FreeBSD 8?
    ... I want to identify the device created for an USB Mass Storage device with its vendor and product identification numbers. ... Currently USB subsystem in FreeBSD 8 does not send all these crucial information in one event to make such a match possible. ...
    (freebsd-current)
  • Re: A8N-E, 3gig memory, and usb?
    ... my 2 1 gig sticks to get RMAed. ... reader from the standard Windows "USB Mass Storage Device" to "Genesys Mass ... and change the driver back to the standard "USB Mass Storage ...
    (alt.comp.periphs.mainboard.asus)