Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In my case if I 1) plug in the USB-cardreader and afterwards 2) insert the sd-card, it looks exactly as in your case - the reader is recognized, but the card is invisible.
But:
If I 1)first insert the sd-card into the reader and 2) plug in the USE-cardreader, everything is recognized.
Distribution: Slackware 12.1, AND IM LOVIN EVERY MINUTE OF IT, JERRY! :D
Posts: 122
Rep:
I cant tell you exactly, because im not an expert, but I had this problem. I think its got something to do with the kernel and subsquently DBUS not being able to scan the individual LUNS on the reader. scan for luns is an option in the kernel. but, like I said, take this with a pinch of salt because Im not quite sure. hopefully someone more knowledgeable can step in and clear things up.
you could overkill the problem and unload then reload usb kernel modules, but its an absolute pain, better to try an updated kernel for your distro.
I had the same problem in Slackware 12, and then they fixed it in Slack 12.1
-> Device Driver
-> SCSI device support
-> Probe all LUNs on each SCSI device
Quote:
If you have a SCSI device that supports more than one LUN (Logical
Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
can say Y here to force the SCSI driver to probe for multiple LUNs.
A SCSI device with multiple LUNs acts logically like multiple SCSI
devices. The vast majority of SCSI devices have only one LUN, and
so most people can say N here. The max_luns boot/module parameter
allows to override this setting.
Ok, thanks for the suggestions. I will try the idea of plugging the reader after the card, but the thing is that this is a built in reader to the case up front. I am going to get inside and try the unplugging deal when I get the chance. Hopefully that will work.
The thing about the LUNS, I checked and that was already enabled on the running kernel, 2.6.26. If that was the reference, it's not the problem.
I myself didnt actually recompile a kernel and enable "Probe all LUNs on each SCSI device", so Im not sure that was it.
what actually happened was, I switched from Slack 11, which didnt have HAL, to Slack 12, which did have HAL installed. so on second thought, it could be HAL that was the reason the card reader then started to work properly, although it is possible that the "Probe all LUNs on each SCSI device" option was enabled in the newer Slack 12 release.
Ha! That's cool, bashyow! I now installed & started up hal ("/etc/init.d/hald start") and look at that - the card gets recognized as soon as I stick it into the cardreader - don't have to disconnect & reconnect the whole cardreader anymore.
Thanks!!!
I had a similar problem with a card reader that I've used with CF cards for years. It wouldn't take microSDHC or normal SD and neither would another card reader I tried. rc.hald didn't fix it (was already running, anyway) but compiling in LUNS fixed it with the second reader. The first reader gets hung up resetting the SD slot and finally disables read support after about 2 minutes, and if I unplug it during that time it will crash usb-storage with no way to recover other than a restart. I guess that reader predates microSDHC, or has a bad slot. The working reader is LENMAR AllIn1 and the failed reader is Belkin 15-in-1.
ta0kira
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.