You are not logged in.
I've been unable to get my SD card slot to read a card after ejected the card and inserting a new (or same, doesn't matter) card. I don't see any sort of output in dmesg or /var/log/everything.log indicating any sort of failure or error.....it just seems like it doesn't detect the card and/or card slot anymore.
sudo fdisk -l yields nothing beyond my sda.
Here are relevant portions of /var/log/everything.log and dmesg, as well as lscpi's output.
http://pastebin.com/pastebin.php?dl=f2f2ef6af
dmesg
scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0
sd 4:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
sd 4:0:0:0: [sdb] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] Attached SCSI removable disk
/var/log/everything.log
http://pastebin.com/f6c917cea
Jan 24 13:33:04 l33tpc kernel: scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Jan 24 13:33:04 l33tpc kernel: usb-storage: device scan complete
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB)
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] Write Protect is off
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jan 24 13:33:04 l33tpc kernel: sdb: sdb1
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jan 24 13:33:04 l33tpc kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
This data was obtained by having an 8GB SDHC card (unlocked) inserting before powering the laptop.
I have laptop-mode-tools installed with some of the options enabled, and if needed I can report that info from /etc/laptop-mode/conf.d/
Now I'm going to reboot and further troubleshoot by comparing the logs without a card inserted, then insert a card and see if it works. IIRC it will not if not inserted at boot.
EDIT:
One more thing, here is my daemon list from rc.conf. I have no extra kernel modules loaded manually either.
DAEMONS=(syslog-ng netfs crond hal laptop-mode alsa samba wicd)
Last edited by DarksideEE7 (2010-01-27 16:44:15)
Offline
Open a root terminal and type "tail -f /var/log/messages.log". Now insert and then remove the card. What messages do you see? If you get this equivalent message:
Jan 24 13:33:04 l33tpc kernel: sdb: sdb1
then your card and its partition are being detected and you just need to open up your file manager to access the card. If you don't get that show us what messages you actually get in the terminal.
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline
Open a root terminal and type "tail -f /var/log/messages.log". Now insert and then remove the card. What messages do you see? If you get this equivalent message:
Jan 24 13:33:04 l33tpc kernel: sdb: sdb1then your card and its partition are being detected and you just need to open up your file manager to access the card. If you don't get that show us what messages you actually get in the terminal.
That's how I obtained the above logs.......by tailing messages.log (well actually everything.log). I do this as root as well. When I unplug it and plug it in I get nothing.
I just rebooted with the card ejected at boot, then inserted the card. I saw nothing with fdisk -l, so I checked everthing.log and saw nothing.
I then did:
sudo tail -f /var/log/messages.log (as well as everything.log)
and re-inserted.........nothing.
USB drives work completely fine too, and my USB to SD adapter works fine with the SD cards. It's just a bit annoying to have to resort to this when I have an SD card reader, which is preferred due to it's low profile.
Thanks for the input, and if anyone else has any ideas I'm open to suggestion. If any further info is needed I can certainly supply it.
Offline
I can't believe it but this issue is still existant in my system. I'm unable to use the SD card slot if I eject the card. I'm only able to mount the card (or mount and browse it via hal in Dolphin file manager) if I have the card in at boot.
Does anyone have any ideas on what I can do? This is quite frustrating. I've basically been forced to use a USB>>SD card adapter if I want to use someone elses SD card. I would greatly appreciate any help.
I just tested it and did:
sudo tail -f /var/log/messages.log
as well as looked at dmesg's output and it shows absolutley nothing after this message (showing that it has been ejected):
Apr 27 04:15:42 l33tpc hald: unmounted /dev/sdb1 from '/media/disk-1' on behalf of uid 0
Offline
I'm still unable to read SD cards when ejected then re-inserted. If anyone has any suggestions as to what to do I would greatly appreciate it.
I tailed /var/log/messages.log (also everything.log), ejected the disk, then inserted it and I see nothing. I also check dmesg and nothing new pops up during the eject/insert process.
Just to reiterate, I can read the disk if it's inserted at boot, but after that if I eject and insert it I can't read it in Dolphin, and I don't see the partitions listed in:
sudo fdisk -l
Here is the output of lsusb after ejecting reinserting:
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04f2:b036 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Last edited by DarksideEE7 (2010-06-25 21:41:18)
Offline
On my asus eee pc, you have to set the option
"installation of os" to finished <-- Well it's an option along these lines.
Then the card reader starts to behave. Has your bios got a similar option?
Last edited by gazj (2010-06-25 22:14:09)
Offline
On my asus eee pc, you have to set the option
"installation of os" to finished <-- Well it's an option along these lines.
Then the card reader starts to behave. Has your bios got a similar option?
I'm not sure let me reboot and check.....
Offline
Nope, no such option in my BIOS
EDIT:
I tried booting with the SD card out of the reader and inserting afterward, and it wasn't detected this way. Nothing showed in messages.log or dmesg.
It looks like the only way it works is when udev is started at boot, but after that no dice. This is really frustrating......
Last edited by DarksideEE7 (2010-06-26 00:55:27)
Offline