LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices



Reply
 
Search this Thread
Old 09-20-2009, 07:11 PM   #1
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Rep: Reputation: 33
can't get 8-1 card reader to work {ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card }


Hello,
i have Acer AST160 with the 2.6.18-164.el5 #1 SMP stock kernel, running CentOs 5.2.
Acer comes with FC51GM motherboard and 5-1 ( or 7-1?) card reader. I never tried to get it to work under linux, but i do recall that it worked under windows back 3 years ago.
For the purpose of this execrsise i'm trying to access the Cannon SD Memory Card SDC-16M.
This is what i see in the messages:

Code:
Sep 19 19:07:45 server kernel: Initializing USB Mass Storage driver...
Sep 19 19:07:45 server kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Sep 19 19:07:45 server kernel: usbcore: registered new driver usb-storage
Sep 19 19:07:45 server kernel: USB Mass Storage support registered.
Sep 19 19:07:45 server kernel:   Vendor: Generic   Model: USB SD Reader     Rev: 1.00
Sep 19 19:07:45 server kernel:   Type:   Direct-Access                      ANSI SCSI revision: 00
Sep 19 19:07:45 server kernel: sd 4:0:0:0: Attached scsi removable disk sdb
Sep 19 19:07:45 server kernel:   Vendor: Generic   Model: USB CF Reader     Rev: 1.01
Sep 19 19:07:45 server kernel:   Type:   Direct-Access                      ANSI SCSI revision: 00
Sep 19 19:07:45 server kernel: sd 4:0:0:1: Attached scsi removable disk sdc
Sep 19 19:07:45 server kernel:   Vendor: Generic   Model: USB SM Reader     Rev: 1.02
Sep 19 19:07:45 server kernel:   Type:   Direct-Access                      ANSI SCSI revision: 00
Sep 19 19:07:45 server kernel: sd 4:0:0:2: Attached scsi removable disk sdd
Sep 19 19:07:45 server kernel:   Vendor: Generic   Model: USB MS Reader     Rev: 1.03
Sep 19 19:07:45 server kernel:   Type:   Direct-Access                      ANSI SCSI revision: 00
Sep 19 19:07:45 server kernel: sd 4:0:0:3: Attached scsi removable disk sde
Sep 19 19:07:45 server kernel: device-mapper: uevent: version 1.0.3
fdisk -l doesn't reveal any devices from the above.

cat /proc/scsi/usb-storage/4
Code:
cat /proc/scsi/usb-storage/4
   Host scsi4: usb-storage
       Vendor:
      Product: USB Reader
Serial Number: 2004888
     Protocol: Transparent SCSI
    Transport: Bulk
       Quirks:
cat /proc/scsi/sg/device_strs
Code:
ATA             ST3160812AS             3.AA
Generic         USB SD Reader           1.00
Generic         USB CF Reader           1.01
Generic         USB SM Reader           1.02
Generic         USB MS Reader           1.03
so it seems that the system recognizes the device - the reader.
if i plug any ( and i have a few ) of cards - no messages are generated in the /var/log and i can't mount any of the sd* devices. I do have one HD that is mapped to sda and it works just fine. I also have the USB KVM that gets recognized and also works fine.
Please advise.
Thank you

Last edited by DBabo; 09-23-2009 at 01:11 PM. Reason: wrong harware
 
Old 09-21-2009, 06:56 PM   #2
Lee_Ball
Member
 
Registered: Jul 2005
Location: Manchester (UK)
Distribution: Fedora CentOS
Posts: 132

Rep: Reputation: 18
What happens if you unplug the card reader, insert a card then plug it back in?
 
Old 09-21-2009, 10:12 PM   #3
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by Lee_Ball View Post
What happens if you unplug the card reader, insert a card then plug it back in?
i'm afraid i can't do that - it's "built-in", Here is the link to a pic.
 
Old 09-22-2009, 04:13 AM   #4
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Depending on how old your system is try running:

Code:
/sbin/rescan-scsi-bus -l
sometime at startup.
 
Old 09-22-2009, 02:16 PM   #5
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by H_TeXMeX_H View Post
Depending on how old your system is try running:

Code:
/sbin/rescan-scsi-bus -l
sometime at startup.
box is 2005 (2004?) the centos is latest and greatest.
 
Old 09-22-2009, 10:06 PM   #6
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by H_TeXMeX_H View Post
Depending on how old your system is try running:

Code:
/sbin/rescan-scsi-bus -l
sometime at startup.
all right got to this issue tonight.
here is the output of the execution of the script as root:

Code:
./rescan-scsi-bus.sh-1.29 -l
./rescan-scsi-bus.sh-1.29: line 476: [: 474:: integer expression expected
Host adapter 0 (sata_nv) found.
Host adapter 1 (sata_nv) found.
Host adapter 2 (sata_nv) found.
Host adapter 3 (sata_nv) found.
Host adapter 4 (usb-storage) found.
Scanning SCSI subsystem for new devices
Scanning host 0 channels 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, LUNs  0 1 2 3 4 5 6 7
Scanning host 1 channels 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, LUNs  0 1 2 3 4 5 6 7
Scanning host 2 channels 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, LUNs  0 1 2 3 4 5 6 7
Scanning host 3 channels 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, LUNs  0 1 2 3 4 5 6 7
Scanning for device 3 0 0 0 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 00
      Vendor: ATA      Model: ST3160812AS      Rev: 3.AA
      Type:   Direct-Access                    ANSI SCSI revision: 05
Scanning host 4 channels 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, LUNs  0 1 2 3 4 5 6 7
Scanning for device 4 0 0 0 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 00
      Vendor: Generic  Model: USB SD Reader    Rev: 1.00
      Type:   Direct-Access                    ANSI SCSI revision: 02
Scanning for device 4 0 0 1 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 01
      Vendor: Generic  Model: USB CF Reader    Rev: 1.01
      Type:   Direct-Access                    ANSI SCSI revision: 02
Scanning for device 4 0 0 2 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 02
      Vendor: Generic  Model: USB SM Reader    Rev: 1.02
      Type:   Direct-Access                    ANSI SCSI revision: 02
Scanning for device 4 0 0 3 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 03
      Vendor: Generic  Model: USB MS Reader    Rev: 1.03
      Type:   Direct-Access                    ANSI SCSI revision: 02
0 new device(s) found.
0 device(s) removed.
 
Old 09-23-2009, 03:44 AM   #7
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
So then it still doesn't work after running it ?
 
Old 09-23-2009, 09:57 AM   #8
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by H_TeXMeX_H View Post
So then it still doesn't work after running it ?
nope
 
Old 09-23-2009, 10:12 AM   #9
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Looks like a standard issue USB card reader, connected to a USB pin-header on the motherboard. Actually looks almost identical to my own card-reader, which I pilfered out of an HP Pavilion box.

This can be verified by typing:

shell# lsusb # Please show us this output, if it is indeed shown there.

and assuming it shows up in the list generated by the above command, please repeat the command, like so:

shell# lsusb -v # Please post this output too.

The kernel already sees the device as the usual SCSI disks, just like mine does, so before further experimentation (which we'll get to) does your card reader have a little green light on it (or whatever color) which lights up when you insert a card?
If it DOES have a light, and the light DOES light up with a card inserted, then put a card in it, and try ALL the following commands (make sure the folder "/mount/point" exists and is empty, before proceeding):

Commands:
shell# mount /dev/sdb1 -t vfat /mount/point -o ro
shell# mount /dev/sdc1 -t vfat /mount/point -o ro
shell# mount /dev/sdd1 -t vfat /mount/point -o ro
shell# mount /dev/sde1 -t vfat /mount/point -o ro

If mount does not return a single word, after doing one of the above commands, then try just a plain "mount" command, with no arguments, and examine the output. Is your device mounted?
If on the other hand, the mount attempts above DO PRODUCE output, like errors of some sort, please post for us the errors.

Meanwhile, I believe I posted a thread around here somewhere, about my own card reader, and I will go and try to locate that thread for you; I think I showed some UDEV rules I had made so that my card-reader clots would always appear in teh same place every time, so I didn't need to frig around like this

I'll find it and post a link for you -- cross your fingers

EDIT: in a console, as root, while you are plugging in and removing the card(s), please have the following command running (you should have one of these commands on your system):
shell# udevadm monitor --kernel # for new udev versions
shell# /sbin/udevmonitor # for older udev's

If you see console output when inserting/removing devices, please show us the output.

Sasha

Last edited by GrapefruiTgirl; 09-23-2009 at 10:18 AM.
 
Old 09-23-2009, 10:28 AM   #10
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Update:

Here's the contents of my udev rules file for the USB card reader:

shell# cat 11-usb-storage.rules

Code:
# the HP 4-slot 15-in-1 card reader I have now installed in my machine.
SUBSYSTEMS=="scsi",ATTRS{vendor}=="Generic ",ATTRS{model}=="USB SD Reader   ",ATTRS{rev}=="1.00",NAME{all_partitions}="card-reader-SD",GROUP="plugdev"
SUBSYSTEMS=="scsi",ATTRS{vendor}=="Generic ",ATTRS{model}=="USB CF Reader   ",ATTRS{rev}=="1.01",NAME{all_partitions}="card-reader-CF",GROUP="plugdev"
SUBSYSTEMS=="scsi",ATTRS{vendor}=="Generic ",ATTRS{model}=="USB SM Reader   ",ATTRS{rev}=="1.02",NAME{all_partitions}="card-reader-SM",GROUP="plugdev"
SUBSYSTEMS=="scsi",ATTRS{vendor}=="Generic ",ATTRS{model}=="USB MS Reader   ",ATTRS{rev}=="1.03",NAME{all_partitions}="card-reader-MS",GROUP="plugdev"
If you need some help making udev rules for your device, if these rules do not work for you, please post back and I'll try to help you. For the record, here's the procedure I followed in making my rules:

# commands for identifying the attribs/strings of devices, use the following procedure:
# (from http://shallowsky.com/blog/tags/udev/)
# 1) Find out the corresponding /block device name for it, like this:
# sh# udevinfo -q path -n /dev/sdd
# In my case, the SD reader was /block/sdd. Now pass that into udevinfo -a, like so:
# sh# udevinfo -a -p /block/sdd
# and look for a few items that you can use to identify that slot uniquely.
# for me, I used the MODEL attribute, and the REV attribute, to identify the gadgets.

NOTE: the above instructions are for an older udev, and there MIGHT be newer commands in place of the ones mentioned here. if that's the case, I'll work on it with you afterwards and try to update the commands..

Sasha
 
Old 09-23-2009, 01:03 PM   #11
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Original Poster
Rep: Reputation: 33
that's a great resource!
Thank you for taking your time and providing all this information.
Let me answer your questions as they arrived:
Code:
lsusb
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 035: ID 10d5:55a2 Uni Class Technology Co., Ltd 2Port KVMSwitcher
Bus 002 Device 034: ID 045e:008a Microsoft Corp. Wireless Keyboard and Mouse
Bus 002 Device 033: ID 058f:9254 Alcor Micro Corp. Hub
Bus 002 Device 001: ID 0000:0000
Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
and:
Code:
lsusb -v

Bus 001 Device 001: ID 0000:0000
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x0000
  idProduct          0x0000
  bcdDevice            2.06
  iManufacturer           3 Linux 2.6.18-164.el5 ehci_hcd
  iProduct                2 EHCI Host Controller
  iSerial                 1 0000:00:0b.1
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0002  1x 2 bytes
        bInterval              12
Hub Descriptor:
  bLength              11
  bDescriptorType      41
  nNbrPorts             8
  wHubCharacteristic 0x000a
    No power switching (usb 1.0)
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood       10 * 2 milli seconds
  bHubContrCurrent      0 milli Ampere
  DeviceRemovable    0xc0 0xe6
  PortPwrCtrlMask    0xf7  0xb7
 Hub Port Status:
   Port 1: 0000.0000
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
   Port 4: 0000.0100 power
   Port 5: 0000.0000
   Port 6: 0000.0100 power
   Port 7: 0000.0100 power
   Port 8: 0000.0100 power

Bus 002 Device 035: ID 10d5:55a2 Uni Class Technology Co., Ltd 2Port KVMSwitcher
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x10d5 Uni Class Technology Co., Ltd
  idProduct          0x55a2 2Port KVMSwitcher
  bcdDevice            1.00
  iManufacturer           1 No brand
  iProduct                2 2Port KVMSwicther
  iSerial                 3 0�
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           59
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 HID Mouse
    bmAttributes         0x80
    MaxPower               96mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              7 Mouse
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      65
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              16
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              6 Mouse
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      24
          Report Descriptor: (length is 24)
            Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
                            (null)
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Collection, data= [ 0x01 ] 1
                            Application
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Local ): Usage Minimum, data= [ 0x00 ] 0
                            (null)
            Item(Local ): Usage Maximum, data= [ 0xff 0x00 ] 255
                            (null)
            Item(Global): Report Count, data= [ 0x08 ] 8
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Main  ): Output, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Main  ): End Collection, data=none
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              16

Bus 002 Device 034: ID 045e:008a Microsoft Corp. Wireless Keyboard and Mouse
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x045e Microsoft Corp.
  idProduct          0x008a Wireless Keyboard and Mouse
  bcdDevice           73.73
  iManufacturer           1 Microsoft
  iProduct                2 Microsoft Wireless Optical Desktop� 1.00
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           59
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      60
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     481
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0007  1x 7 bytes
        bInterval              10

Bus 002 Device 033: ID 058f:9254 Alcor Micro Corp. Hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0         8
  idVendor           0x058f Alcor Micro Corp.
  idProduct          0x9254 Hub
  bcdDevice            3.12
  iManufacturer           1 ALCOR
  iProduct                2 Generic USB Hub
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval             255
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             4
  wHubCharacteristic 0x0009
    Per-port power switching
    Per-port overcurrent protection
  bPwrOn2PwrGood       22 * 2 milli seconds
  bHubContrCurrent    100 milli Ampere
  DeviceRemovable    0xc0
  PortPwrCtrlMask    0xe6
 Hub Port Status:
   Port 1: 0000.0100 power
   Port 2: 0000.0303 lowspeed power enable connect
   Port 3: 0000.0303 lowspeed power enable connect
   Port 4: 0000.0100 power

Bus 002 Device 001: ID 0000:0000
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  idVendor           0x0000
  idProduct          0x0000
  bcdDevice            2.06
  iManufacturer           3 Linux 2.6.18-164.el5 ohci_hcd
  iProduct                2 OHCI Host Controller
  iSerial                 1 0000:00:0b.0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0002  1x 2 bytes
        bInterval             255
Hub Descriptor:
  bLength              11
  bDescriptorType      41
  nNbrPorts             8
  wHubCharacteristic 0x0002
    No power switching (usb 1.0)
    Ganged overcurrent protection
  bPwrOn2PwrGood        1 * 2 milli seconds
  bHubContrCurrent      0 milli Ampere
  DeviceRemovable    0xc0 0xe6
  PortPwrCtrlMask    0xf7  0xb7
 Hub Port Status:
   Port 1: 0000.0103 power enable connect
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
   Port 4: 0000.0100 power
   Port 5: 0000.0103 power enable connect
   Port 6: 0000.0100 power
   Port 7: 0000.0100 power
   Port 8: 0000.0100 power

Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x058f Alcor Micro Corp.
  idProduct          0x9360 8-in-1 Media Card Reader
  bcdDevice            1.00
  iManufacturer           1
  iProduct                2 USB Reader
  iSerial                 3 2004888
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
aha! I have "8in1" . good to know

Quote:
before further experimentation (which we'll get to) does your card reader have a little green light on it (or whatever color) which lights up when you insert a card?
YES.

Quote:
... If it DOES have a light, and the light DOES light up with a card inserted, then put a card in it, and try ALL the following commands (make sure the folder "/mount/point" exists and is empty, before proceeding):

Commands:
shell# mount /dev/sdb1 -t vfat /mount/point -o ro
shell# mount /dev/sdc1 -t vfat /mount/point -o ro
shell# mount /dev/sdd1 -t vfat /mount/point -o ro
shell# mount /dev/sde1 -t vfat /mount/point -o ro

If mount does not return a single word, after doing one of the above commands, then try just a plain "mount" command, with no arguments, and examine the output. Is your device mounted?
If on the other hand, the mount attempts above DO PRODUCE output, like errors of some sort, please post for us the errors.
and the output is:
Code:
mount -v /dev/sdb1 -t vfat /media/ssmd/
mount: special device /dev/sdb1 does not exist
[root@server ~]# mount -v /dev/sdb -t vfat /media/ssmd/
mount: /dev/sdb is not a valid block device
[root@server ~]# mount -v /dev/sdc1 -t vfat /media/ssmd/
mount: special device /dev/sdc1 does not exist
[root@server ~]# mount -v /dev/sdc -t vfat /media/ssmd/
mount: No medium found
[root@server ~]# mount -v /dev/sdd1 -t vfat /media/ssmd/
mount: special device /dev/sdd1 does not exist
[root@server ~]# mount -v /dev/sdd -t vfat /media/ssmd/
mount: No medium found
[root@server ~]# mount -v /dev/sde1 -t vfat /media/ssmd/
mount: special device /dev/sde1 does not exist
[root@server ~]# mount -v /dev/sde -t vfat /media/ssmd/
mount: No medium found
seems that sdb has smth in it. :
Code:
mount -v /dev/sdb  /media/ssmd/
mount: you didn't specify a filesystem type for /dev/sdb
       I will try all types mentioned in /etc/filesystems or /proc/filesystems
Trying hfsplus
mount: /dev/sdb is not a valid block device
mount doesn't reveal anything new.
udevmonitor doesn't produce any output upon insertion or removal of the card.
it seems that udevd is up:
Code:
root       519     1  0 Sep20 ?        00:00:00 /sbin/udevd -d
it is my {mis?}understanding that udev sybsystem is not getting any events from the card, so i don't need look into rules just yet? Please let me know.
Andrew

Last edited by DBabo; 09-23-2009 at 01:12 PM.
 
Old 09-23-2009, 01:36 PM   #12
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
You'll be happy to know, your card reader has the same manufacturer as mine -- Alcor Micro Corp. Mine works great, so there's a good chance yours will too, eventually.

Looks like the slot you're using is /dev/sdb.

Now, you can't mount "sdb" -- it has to be sdb1 or sdb2 or whatever; probably, if there's only one partition on the card, it will be /dev/sdb1.

What you see here:

Quote:
[root@server ~]# mount -v /dev/sdb -t vfat /media/ssmd/
mount: /dev/sdb is not a valid block device
..is a good sign that that slot is the one with the card in it, trying to be read. But you need to tell it what partition to mount, hence the 1 as in /dev/sdb1

Now, the file-system type: If you don't have an fstab entry for the card slot, you need to specify a file system type on the command line. Here's my fstab file for my card reader; note that I use "auto" for the filesystem type, which you CANNOT do on command line):
Code:
/dev/card-reader-SD1	/media/CardReader/SD	auto		defaults,users,noauto,ro		0 0
/dev/card-reader-CF1	/media/CardReader/CF	auto		defaults,users,noauto,ro		0 0
/dev/card-reader-SM1	/media/CardReader/SM	auto		defaults,users,noauto,ro		0 0
/dev/card-reader-MS1	/media/CardReader/MS	auto		defaults,users,noauto,ro		0 0
So, you see how I have named my slots? These names are/were created using the UDEV rules I showed you above.

Now, depending on how shiny-new your distro is, HAL might be playing a role in this entire situation. I'm not sure, and my HAL skills are pretty much non-existent at this time, so if HAL is involved, I won't be able to help there. Let's hope for now there's no HAL stuff going on..

If you have "/sbin/udevmonitor", then you will also have the other udev* commands.
It appears, now that I have checked the man page for that version of udev, that "udevmonitor" is not exactly the right command I should have told you to use. It IS the right command to watch your udev RULES in action, to make sure your rules are being used at the right time, and that they are doing what you expect; but there's another udev* command which watches for the kernel events, and I can't recall what it was

To locate all the udev files and binaries you have, type this, from a console:

sh-4.0# find / -name udev* -type f

If you don't see any udev commands that look useful, or if you want to try something else that might work just great, try this:

Verify the name of your kernel.log file in /var/log and type the following into a console, as root, and THEN plug the card in and out:

shell# tail -f /var/log/kernel.log

And you should now see stuff on the screen

At this point, especially if you see stuff on kernel.log when you put the card in/out, I recomend you make some udev rules as I did.

If someone else has better advice, or feels that udev rules will not help on that distro for whatever reason, I'm open to suggestions; however I believe pretty certainly that if you make the right rules, to name your devices as I did, and have udev create all the special devices sda1, sda2, sda3, etc., that your card reader will work.

I'll check in later on to see what's up

EDIT: you might also try "msdos" as a file-system type, if you're using command line, but IIRC, I used "vfat".

Best of success,
Sasha

Last edited by GrapefruiTgirl; 09-23-2009 at 01:50 PM. Reason: added EDIT at bottom.
 
Old 09-23-2009, 03:58 PM   #13
DBabo
Member
 
Registered: Feb 2003
Distribution: Scientific Linux 6, Fedora
Posts: 393

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by GrapefruiTgirl View Post
You'll be happy to know, your card reader has the same manufacturer as mine -- Alcor Micro Corp. Mine works great, so there's a good chance yours will too, eventually.
xe-xe-xe . I was looking around by "Alcor" and came across your post where you described your experience with it

Quote:
Originally Posted by GrapefruiTgirl View Post
Looks like the slot you're using is /dev/sdb.
well, yeah. but it also seems that regardless if the card is in or out.


Quote:
Originally Posted by GrapefruiTgirl View Post
Now, you can't mount "sdb" -- it has to be sdb1 or sdb2 or whatever; probably, if there's only one partition on the card, it will be /dev/sdb1.

What you see here:
...is a good sign that that slot is the one with the card in it, trying to be read. But you need to tell it what partition to mount, hence the 1 as in /dev/sdb1
if you read carefully my post - i tried all combinations - /sdb and /sdb1. only sdb produced some meaningful information.


I followed H_TeXMeX_H suggestion and reooted the system with card inserted.
system found the card and i was able to mount it:
Code:
fdisk -l:
Disk /dev/sdb: 14 MB, 14909440 bytes
2 heads, 32 sectors/track, 455 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         455       14531+   1  FAT12
and mount was obvious.

Sum up:
1. the good - card reader is working and card is working as well.
2. card can't be recognized on hotplug.

let me read on udev and i'll update the thread.

Thank you Sasha.
 
Old 09-23-2009, 04:06 PM   #14
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Cool! Nice going;

Memories are coming back to me........ Slowly.. I'm not 100% sure, but I suspect you can make it auto-mount, if that's what you'd like. I prefer not auto-mounting much of anything, myself, so I stick my card(s) in and then run a mount command or use my file browser (except if I boot up with a card in, it will automount because of my fstab file) but you can put auto-mounting stuff into the udev rules too, assuming that udev is indeed playing a role here, which almost certainly it is.

After supper, I'll try to help a bit more with the udev stuff, after seeing where you're at by that time.

Good stuff

PS - you may have already fixed it, but you had a messed up [quote] tag in your last post (Fixed)

Sasha
 
Old 09-24-2009, 09:45 AM   #15
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
It indeed sounds like a udev rules issue ... except I'm not good at writing those properly, maybe GrapefruiTgirl can help you.
 
  


Reply

Tags
acer, centos, ehcihcd, udev


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to Get Card Reader to Work In Ubuntu 7.10 taurusx5 Linux - Software 1 03-13-2008 09:40 AM
How to Get Card Reader to Work In Ubuntu 7.10 taurusx5 Linux - Software 1 03-12-2008 12:12 AM
Getting SD card reader to work ratsm Linux - Hardware 1 10-31-2006 07:46 PM
card reader wont work rahilrai Linux - Newbie 1 03-13-2006 08:56 AM
card reader doesn't work jerryluis Mandriva 0 06-22-2004 03:46 PM


All times are GMT -5. The time now is 04:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration