Jump to content

Photo

[SOLVED] Alcor Micro Corp. 8-in-1 Media Card Reader not showing in File Manager


  • Please log in to reply
13 replies to this topic

#1 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 27 March 2012 - 03:43 AM

I'm running a live session of 1.4, at first my wireless mouse and kb would not work from the USB port on this reader, but after it recognized in another port I plugged it back and it works now. But when I put a SD card in it doesn't recognize a drive in File Manager. Not sure if this is a compatibility issue or if I just need to go hunt down a driver somewhere? In case it helps or is relevant:

uname -a
Linux bodhi 3.2.0-19-generic #30 SMP Tue Mar 20 09:35:59 CDT 2012 i686 GNU/Linux

lsusb
Bus 005 Device 004: ID 046d:c52b Logitech, Inc.
Bus 005 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 15d9:0a4c Dexon
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0781:5567 SanDisk Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsmod
Module Size Used by
joydev 17313 0
dm_crypt 22384 0
snd_via82xx 24658 1
gameport 15027 1 snd_via82xx
snd_via82xx_modem 18262 0
ppdev 12900 0
snd_ac97_codec 105572 2 snd_via82xx,snd_via82xx_modem
hid_logitech_dj 18032 0
ac97_bus 12642 1 snd_ac97_codec
parport_pc 32006 1
shpchp 32285 0
snd_mpu401_uart 13865 1 snd_via82xx
lp 13349 0
parport 36664 3 ppdev,parport_pc,lp
snd_rawmidi 25371 1 snd_mpu401_uart
snd_pcm 76379 3 snd_via82xx,snd_via82xx_modem,snd_ac97_codec
i2c_viapro 12969 0
snd_seq_device 14130 1 snd_rawmidi
snd_timer 24609 1 snd_pcm
snd 61792 10 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_mpu401_uart,snd_rawmidi,snd_pcm,snd_seq_device,snd_timer
mac_hid 13037 0
soundcore 14556 1 snd
snd_page_alloc 14036 3 snd_via82xx,snd_via82xx_modem,snd_pcm
squashfs 35941 1
aufs 158929 91
nls_iso8859_1 12617 1
nls_cp437 12751 1
vfat 17266 1
fat 55347 1 vfat
radeon 744224 2
usbhid 45614 1 hid_logitech_dj
ttm 64800 1 radeon
drm_kms_helper 36749 1 radeon
hid 81147 2 hid_logitech_dj,usbhid
drm 197087 4 radeon,ttm,drm_kms_helper
sata_via 13461 0
via_rhine 27226 0
i2c_algo_bit 13152 1 radeon
pata_via 13382 3
usb_storage 39284 1



A big thank you to everyone who contributes to Bodhi Linux


#2 Jeff

Jeff

    Lead Developer

  • Developer
  • 12416 posts
  • LocationBloomington, IL

Posted 27 March 2012 - 04:07 AM

Can you also post the output of:

lspci

ls /dev/sd*

ls /dev/mmc*

Thanks,
~Jeff

#3 STRUPPI

STRUPPI

    Member

  • Members
  • 738 posts

Posted 27 March 2012 - 03:04 PM

Hi satcheatananda,
you are 100% shure that the electricle contact in time of SD-Card plug in is OK?

If I plug in my SD card not 100% correct [softly], the green PC-LED 'SD-Card is pluged in' worked, but my file manager do not see this SD card [and Place module see this SD card not too]
Unpluged the SD card and again 'stronger/harder pluged in' and my SD card is in place module and in the same time open my file manager as SD-Card contents.

your lsusb let see, that Linux [Bodhi] is knowing about your Card reader, normal, all is OK:
Bus 005 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader

That's my lsusb:
struppi@PREDATOR:~$ lsusb
Bus 002 Device 003: ID 056a:0065 Wacom Co., Ltd 
Bus 002 Device 002: ID 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 SmartCard Reader
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device
Bus 001 Device 002: ID eb1a:51b2 eMPIA Technology, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
struppi@PREDATOR:~$ 
'Bus 001 Device 005: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device' is my SD-Card Reader.

#4 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 28 March 2012 - 02:44 AM

Hi Struppi,

Plugging it in softly does not seem to make a difference. I did find a thread on the #! forum but have not had time to try it.

Here you go Jeff, thanks:

lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:0a.0 Communication controller: Agere Systems V.92 56K WinModem (rev 03)
00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80)
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

ls /dev/sd*
/dev/sda /dev/sda2 /dev/sda6 /dev/sdb1 /dev/sdd /dev/sdf
/dev/sda1 /dev/sda5 /dev/sdb /dev/sdc /dev/sde

ls /dev/mmc*
ls: cannot access /dev/mmc*: No such file or directory

#5 STRUPPI

STRUPPI

    Member

  • Members
  • 738 posts

Posted 28 March 2012 - 05:37 AM

struppi@PREDATOR:~$ ls /dev/sd*
/dev/sda   /dev/sda4  /dev/sda8  /dev/sdb6  /dev/sdc3  /dev/sdf
/dev/sda1  /dev/sda5  /dev/sdb   /dev/sdc   /dev/sdd   /dev/sdg
/dev/sda2  /dev/sda6  /dev/sdb1  /dev/sdc1  /dev/sdd1  /dev/sdh
/dev/sda3  /dev/sda7  /dev/sdb5  /dev/sdc2  /dev/sde
struppi@PREDATOR:~$ 
struppi@PREDATOR:~$ sudo blkid
[sudo] password for struppi: 
/dev/sda1: LABEL="System_Reserved" UUID="E2B492BCB4929321" TYPE="ntfs" 
/dev/sda2: LABEL="Boot_C" UUID="18BCF418BCF3EE5E" TYPE="ntfs" 
/dev/sda3: LABEL="Bodhi_PAE" UUID="2334be8f-d04f-435c-b90b-4f91f459306c" TYPE="reiserfs" 
/dev/sda5: LABEL="SOS_Bodhi" UUID="40b1d6c9-4e28-413b-9a8f-08fbf0e0bb6a" TYPE="ext4" 
/dev/sda6: LABEL="NEW" UUID="54a7902e-ac85-4682-af00-3590cdc40c66" TYPE="xfs" 
/dev/sda7: LABEL="TEST" UUID="0b453018-98da-4688-bcad-0e40b47b70ed" TYPE="reiserfs" 
/dev/sda8: LABEL="swap" UUID="2291b13a-d171-482f-9709-4c59935c1e57" TYPE="swap" 
/dev/sdb5: LABEL="DATA_D" UUID="42AC1500AC14EFE1" TYPE="ntfs" 
/dev/sdb6: LABEL="mozilla" UUID="21BF902D4D9EA32E" TYPE="ntfs" 
/dev/sdc1: LABEL="Save_E" UUID="041CE03C1CE02A7E" TYPE="ntfs" 
/dev/sdc2: LABEL="datas" UUID="91dd1302-a432-4838-81c3-06035ddb1bc3" TYPE="reiserfs" 
/dev/sdc3: LABEL="acronis_back" UUID="41e63957-2193-412e-9a29-fff28a054a9c" TYPE="xfs" 
/dev/sdd1: LABEL="Backup_F" UUID="82881FDF881FD091" TYPE="ntfs" 
/dev/sdg1: LABEL="MULTIBOOT" UUID="59CD-454B" TYPE="vfat" 
struppi@PREDATOR:~$ 
sdg1 is my SD-Card [pluged in]

Can not function:
struppi@PREDATOR:~$ ls /dev/mmc*
ls: cannot access /dev/mmc*: No such file or directory
struppi@PREDATOR:~$
In /dev is no mmc presend....

Please satcheatananda,
make a
sudo blkid
with a inpluged SD-Card and post the result here.

#6 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 29 March 2012 - 03:56 AM

Okay this is with the 1.3 live CD, don't have my USB drive with 1.4 with me:



bodhi@bodhi:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="40" UUID="580CC9110CC8EAD8" TYPE="ntfs"
/dev/sda5: UUID="5ffbc604-3cca-4f61-a295-93f886fa7983" TYPE="ext4"
/dev/sda6: UUID="0b334f80-188e-4c6d-9e81-593f347e8127" TYPE="swap"


I found a LinuxQuestions thread on the same reader: http://www.linuxques...-card-}-756634/

Will try booting with card in here and try blkid again. BTW FWIW I will update the hardware wiki with the details once I get this working.

#7 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 29 March 2012 - 04:28 AM

:unsure: Umm.. So it turns out I was putting a SDHC card in a SD only reader. It wouldn't complete POSTing and would hang when I plugged it in under Windows, but sure enough it reads the 1gb card fine in Bodhi - user error!

#8 STRUPPI

STRUPPI

    Member

  • Members
  • 738 posts

Posted 29 March 2012 - 02:29 PM

Hi satcheatananda,
I do not understand this [understand to less english, sorry]:

Umm.. So it turns out I was putting a SDHC card in a SD only reader. It wouldn't complete POSTing and would hang when I plugged it in under Windows, but sure enough it reads the 1gb card fine in Bodhi - user error!


SDHC is a SD-Card from the HC-Class [Speed for write/read]
A SDHC in a "only-read-SD-Card-Device"-slot is like a CD in a only read CD-device....function normal as reader and is no problem.

Your 'Alcor Micro Corp. 8-in-1 Media Card Reader' is knowing and function in Bodhi [I think so].
If your last post with inpluged SDHC [your blkid -posting], I think your SDHC is wrong formated.

For the quick test you need a
lsusb
Is there written your '8-in-1 Media Card Reader' and blkid let you not see a inpluged SDHC [SD-Card] is the SD-Card-Format [file system] wrong or damage or unknow.
Test with Bodhi 1.3 Live and SD-Card:

Without SD-Card:
bodhi@bodhi:~$ sudo blkid
/dev/loop0: TYPE="squashfs" 
/dev/sda1: LABEL="System_Reserved" UUID="E2B492BCB4929321" TYPE="ntfs" 
/dev/sda2: LABEL="Boot_C" UUID="18BCF418BCF3EE5E" TYPE="ntfs" 
/dev/sda3: LABEL="Bodhi_PAE" UUID="2334be8f-d04f-435c-b90b-4f91f459306c" TYPE="reiserfs" 
/dev/sda5: LABEL="SOS_Bodhi" UUID="40b1d6c9-4e28-413b-9a8f-08fbf0e0bb6a" TYPE="ext4" 
/dev/sda6: LABEL="NEW" UUID="54a7902e-ac85-4682-af00-3590cdc40c66" TYPE="xfs" 
/dev/sda7: LABEL="TEST" UUID="0b453018-98da-4688-bcad-0e40b47b70ed" TYPE="reiserfs" 
/dev/sda8: LABEL="swap" UUID="2291b13a-d171-482f-9709-4c59935c1e57" TYPE="swap" 
/dev/sdb5: LABEL="DATA_D" UUID="42AC1500AC14EFE1" TYPE="ntfs" 
/dev/sdb6: LABEL="mozilla" UUID="21BF902D4D9EA32E" TYPE="ntfs" 
/dev/sdc1: LABEL="Save_E" UUID="041CE03C1CE02A7E" TYPE="ntfs" 
/dev/sdc2: LABEL="datas" UUID="91dd1302-a432-4838-81c3-06035ddb1bc3" TYPE="reiserfs" 
/dev/sdc3: LABEL="acronis_back" UUID="41e63957-2193-412e-9a29-fff28a054a9c" TYPE="xfs" 
/dev/sdd1: LABEL="Backup_F" UUID="82881FDF881FD091" TYPE="ntfs" 
/dev/sdi1: LABEL="MULTISYSTEM" UUID="2D3D-0290" TYPE="vfat" 
bodhi@bodhi:~$ 

With SD-Card pluged in:
bodhi@bodhi:~$ sudo blkid
/dev/loop0: TYPE="squashfs" 
/dev/sda1: LABEL="System_Reserved" UUID="E2B492BCB4929321" TYPE="ntfs" 
/dev/sda2: LABEL="Boot_C" UUID="18BCF418BCF3EE5E" TYPE="ntfs" 
/dev/sda3: LABEL="Bodhi_PAE" UUID="2334be8f-d04f-435c-b90b-4f91f459306c" TYPE="reiserfs" 
/dev/sda5: LABEL="SOS_Bodhi" UUID="40b1d6c9-4e28-413b-9a8f-08fbf0e0bb6a" TYPE="ext4" 
/dev/sda6: LABEL="NEW" UUID="54a7902e-ac85-4682-af00-3590cdc40c66" TYPE="xfs" 
/dev/sda7: LABEL="TEST" UUID="0b453018-98da-4688-bcad-0e40b47b70ed" TYPE="reiserfs" 
/dev/sda8: LABEL="swap" UUID="2291b13a-d171-482f-9709-4c59935c1e57" TYPE="swap" 
/dev/sdb5: LABEL="DATA_D" UUID="42AC1500AC14EFE1" TYPE="ntfs" 
/dev/sdb6: LABEL="mozilla" UUID="21BF902D4D9EA32E" TYPE="ntfs" 
/dev/sdc1: LABEL="Save_E" UUID="041CE03C1CE02A7E" TYPE="ntfs" 
/dev/sdc2: LABEL="datas" UUID="91dd1302-a432-4838-81c3-06035ddb1bc3" TYPE="reiserfs" 
/dev/sdc3: LABEL="acronis_back" UUID="41e63957-2193-412e-9a29-fff28a054a9c" TYPE="xfs" 
/dev/sdd1: LABEL="Backup_F" UUID="82881FDF881FD091" TYPE="ntfs" 
/dev/sdi1: LABEL="MULTISYSTEM" UUID="2D3D-0290" TYPE="vfat" 
/dev/sdg1: LABEL="MULTIBOOT" UUID="59CD-454B" TYPE="vfat" 
bodhi@bodhi:~$ 
sdg1 is my SD-Card

Next check can you make with the GParted-Live-CD.

There are very much possebilities in Linux to check, is your SD-Card wrong formated.
Most is this a result of formating under MS-Windows, but not general.
struppi@PREDATOR:~$ sudo fdisk -l /dev/sdg

Disk /dev/sdg: 1019 MB, 1019215872 bytes
32 heads, 61 sectors/track, 1019 cylinders
Units = cylinders of 1952 * 512 = 999424 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ee176

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1   *           1        1019      994513+  83  Linux
struppi@PREDATOR:~$ 

struppi@PREDATOR:~$ sudo fdisk -l /dev/sdg1

Disk /dev/sdg1: 1018 MB, 1018381824 bytes
32 heads, 61 sectors/track, 1018 cylinders
Units = cylinders of 1952 * 512 = 999424 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

     Device Boot      Start         End      Blocks   Id  System
struppi@PREDATOR:~$ 
It is again the same SD-Card and you see, declaration is as Linux-System [but is vfat] and can boot.
struppi@PREDATOR:~$ sudo blkid /dev/sdg1
/dev/sdg1: LABEL="MULTIBOOT" UUID="59CD-454B" TYPE="vfat" 
struppi@PREDATOR:~$ 

Have you more SD-Cards as this one testet in this Card-Reader?

#9 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 30 March 2012 - 01:02 AM

SDHC is a SD-Card from the HC-Class [Speed for write/read]


Actually, doesn't the HC stand for high capacity rather than speed? 4gb and over? From what I've read some older readers cannot read SDHC, some can with a firmware upgrade, but not all? The card reads fine in another machine as it is formatted now btw.

I can try to find the Alcor model number and reference it on their site, I suppose there is a chance there is a firmware upgrade to make it read SDHC. Unfortunately there does not seem to be any specific reference on HP's site.

#10 STRUPPI

STRUPPI

    Member

  • Members
  • 738 posts

Posted 30 March 2012 - 10:59 AM

Actually, doesn't the HC stand for high capacity rather than speed? 4gb and over?

Yep, right !
http://www.wisegeek....-sdhc-cards.htm

In the Net are much written, that in Ubuntu 10.04 with the 'Alcor Micro Corp. 8-in-1 Media Card Reader' have much big problems to read/found SDHC-Cards.

Please test this Reader for me with a simple 1GB SD-Card and post the result here.

Long time ago was needet to install the PC/SC too [pcscd & libccid & pcsc-tools & libpcsc-perl].
I have this installed for my extra home banking Card Reader, so I do not know, is that the differents between us.
Or is this a faulty of the Alcor Card-Reader...?

#11 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 31 March 2012 - 02:01 AM

Hi Struppi, (this is/was Sat - I changed name per forum user requests) here are the results for the 1G card. This card shows in File Manager too:

bodhi@bodhi:~$ ls /dev/sd*
/dev/sda /dev/sda2 /dev/sda6 /dev/sdb1 /dev/sdc1 /dev/sde
/dev/sda1 /dev/sda5 /dev/sdb /dev/sdc /dev/sdd /dev/sdf


bodhi@bodhi:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="40" UUID="580CC9110CC8EAD8" TYPE="ntfs"
/dev/sda5: UUID="5ffbc604-3cca-4f61-a295-93f886fa7983" TYPE="ext4"
/dev/sda6: UUID="0b334f80-188e-4c6d-9e81-593f347e8127" TYPE="swap"
/dev/sdb1: LABEL="MYLINUXLIVE" UUID="9E4D-533C" TYPE="vfat"
/dev/sdc1: SEC_TYPE="msdos" UUID="194B-50C2" TYPE="vfat"



bodhi@bodhi:~$ sudo fdisk -l /dev/sdc

Disk /dev/sdc: 1019 MB, 1019215872 bytes
14 heads, 45 sectors/track, 3159 cylinders
Units = cylinders of 630 * 512 = 322560 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 1 3160 995203+ 6 FAT16


bodhi@bodhi:~$ sudo fdisk -l /dev/sdc1

Disk /dev/sdc1: 1019 MB, 1019088384 bytes
32 heads, 61 sectors/track, 1019 cylinders
Units = cylinders of 1952 * 512 = 999424 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System


Again all of the above is with the 1G card. After reinserting the 8G I get nothing with:

bodhi@bodhi:~$ sudo fdisk -l /dev/sdc


The system hangs for a while and returns to the prompt with no info.

EDIT: I have to add that I tried a 2G card successfully as well, and both the 1G and 2G are FAT16. I don't know if that is also the case with my 8G card or if it is FAT32, but I know it did work in another system.

#12 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 31 March 2012 - 02:06 AM

Hi satcheatananda,
I do not understand this [understand to less english, sorry]:



Umm.. So it turns out I was putting a SDHC card in a SD only reader. It wouldn't complete POSTing and would hang when I plugged it in under Windows, but sure enough it reads the 1gb card fine in Bodhi - user error!


Hi, it looks like you edited this post after I replied to it before. What I mean is I believe it is an old reader that will not read higher capacity cards. I have read in different places that some cards will simply not work with the newer SDHC cards and even a firmware upgrade will not make it work (although for some a firmware upgrade will work) so I think it is one of these older models. None of the info I've been able to find for this model says anything about SDHC.

#13 STRUPPI

STRUPPI

    Member

  • Members
  • 738 posts

Posted 31 March 2012 - 12:21 PM

Yep agreeabledisplayname,
this is possible [I think this too] so the test with this Card-Reader and a standard SD-Card, much less as 4 GB, aprox 1GB or 512 MB].
I have this Card Reader too, but can not found this Part....I do not remember, where I have stored this... my moment used PC have a includet Card-Reader....so a externel Card Reader is/was not needet.

#14 agreeabledisplayname

agreeabledisplayname

    Member

  • Members
  • 42 posts

Posted 31 March 2012 - 05:29 PM

I should have thought of this before, but I used Bodhi specifically to test the 8G card in the other system that worked before, sure enough it works with no problem. I don't know if the formatting issue would be an OS level thing but if so it seems clear Bodhi has no problem with the formatting. Although it was interesting that fdisk reported that the system is "W95 FAT32" - I don't know if that is different from a generic FAT32?

Anyway I would try formatting it again but since the card is not even recognized in the system with the Alcor reader I can't format it there.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users