[SOLVED, sort of] sd card in 4 slot card reader not mounting in current

justwantin · 06-28-2012, 07:32 AM

I have a no name 4 slot cardreader that has never given me a problem in 13.37 but it is not working in current. External usb drives and usb sticks are recognised and mounted but this thing is not. From dmesg I'm inclined to think that the system is not probing all 4 slots even though this is enabled in the kernel.

Code:

[  281.996620] usb 2-1.8: new high-speed USB device number 3 using ehci_hcd
[  282.086848] usb 2-1.8: New USB device found, idVendor=0bda, idProduct=0158
[  282.086851] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  282.086852] usb 2-1.8: Product: USB2.0-CRW
[  282.086853] usb 2-1.8: Manufacturer: Generic
[  282.086854] usb 2-1.8: SerialNumber: 20060413092100000
[  282.115147] usbcore: registered new interface driver uas
[  282.116916] usb_storage: exports duplicate symbol fill_inquiry_response (owned by kernel)
[  282.126934] usb_storage: exports duplicate symbol fill_inquiry_response (owned by kernel)

There is nothing wrong with the device as I can plug it in loaded with an sd card on this same machine running porteus and have the sd card mounted

Code:

[ 49.303243] usb 2-1.7: new high-speed USB device number 4 using ehci_hcd
[   49.407173] scsi9 : usb-storage 2-1.7:1.0
[   50.420672] scsi 9:0:0:0: Direct-Access     Generic- Multi-Card       1.00 PQ: 0 ANSI: 0 CCS
[   50.421073] sd 9:0:0:0: Attached scsi generic sg4 type 0
[   51.041151] sd 9:0:0:0: [sdd] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
[   51.042468] sd 9:0:0:0: [sdd] Write Protect is off
[   51.042474] sd 9:0:0:0: [sdd] Mode Sense: 03 00 00 00
[   51.043420] sd 9:0:0:0: [sdd] No Caching mode page present
[   51.043421] sd 9:0:0:0: [sdd] Assuming drive cache: write through
[   51.048822] sd 9:0:0:0: [sdd] No Caching mode page present
[   51.048830] sd 9:0:0:0: [sdd] Assuming drive cache: write through
[   51.054676]  sdd: sdd1 sdd2 sdd3
[   51.057171] sd 9:0:0:0: [sdd] No Caching mode page present
[   51.057173] sd 9:0:0:0: [sdd] Assuming drive cache: write through
[   51.057175] sd 9:0:0:0: [sdd] Attached SCSI removable disk
[   51.473092] EXT4-fs (sdd3): mounted filesystem with ordered data mode. Opts: (null)
[   52.668268] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)

I have tried a workaround

Code:

echo 8 > /sys/module/scsi_mod/parameters/max_luns

as per this page http://en.gentoo-wiki.com/wiki/SD_and_MMC_card_readers but the problem persists. I've checked the kernel config and the kernel is configured to scan all slots (luns), i.e. (CONFIG_SCSI_MULTI_LUN). Perhaps someone can give me a heads up.

vdemuth · 06-28-2012, 01:07 PM

I suspect you are running the huge kernel. If so, try creating an initrd and boot using that. Should be (hopefully) the answer.

justwantin · 06-28-2012, 03:07 PM

I'm using hugesmp which is what I used in 13.37 and I could mount a multicard reader in 13.37. What would I be putting in the intrid?

vdemuth · 06-28-2012, 11:56 PM

Run the following command (as root) then copy and paste its output to a console window (also as root).

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

Run LILO and reboot.

justwantin · 06-29-2012, 04:25 PM

OK, I'm not quite following you. This has composed a mkintrid command

Code:

mkinitrd -c -k 3.2.21-smp -f ext4 -r /dev/sdb1 -m jbd2:mbcache:ext4 -u -o /boot/initrd.gz

That if run will put an initrd.gz in boot and if I add initrd = /boot/initrd.gz to my lilo stanza for this system and the run lilo I will boot with those modules loaded.

So all I have to do now is figure out what modules are not loading when I insert my multicard reader and add them to the mkintrd command?

vdemuth · 06-30-2012, 12:40 AM

Thats pretty much it. make sure that you are booting the generic kernel with an initrd, and the rest should just happen. No extra modules needed. So your lilo.conf file should look similar to this one of mine:

Quote:

# Slackware 13.37 Linux bootable partition config begins

image = /boot/vmlinuz-generic-3.2.13
initrd = /boot/initrd.gz
root = /dev/sdb1
label = Stock-Slack
append = "resume=/dev/sdb2 quiet"
read-only
# Linux bootable partition config ends

justwantin · 06-30-2012, 10:13 PM

vdemuth,

Thanks for you assistance with this. However, I hosed my system and did a complete reinstall with current rsync'd yesterday. The multi card reader is now being recognised properly.

I can't say for sure what exactly made the difference. I used a different RW dvd (with less scratches) for the install, did not install any of kde, uninstalled slack xfce packages and then used upgradepkg --reinstall --install-new to install the xfce packages from salix plus the rest of /full from the salix install cd. Allot of work but I've been struggling to get a workable system up and running since I had to rebuild this box. After update-pciids I can get slack-current working with my nvidia card (I can't on salix) but I don't want the kde bloat and xfce on slack without additional aps is rather spare. If that sounds like a strange setup I have been using Porteus with a couple quick and dirty hacks as a hdd install to access in the interim.

NyteOwl · 07-01-2012, 12:53 PM

Salix isn't Slackware so if you've been mixing and matching pieces, I would expect the periodic glitch.

justwantin · 07-01-2012, 02:36 PM

Can't be much worse than I've been having. This new mobo is a real dog, I've upgraded bios firmware which helped somewhat but I can't get anything better than vesa 800X600 with salix. I can get the nvidia driver installed and good display with slack-current but I am not interested in everything but the kitchen sink kde that comes with slack. The salix xfce environment is well integrated with additional aps and suits me fine so I put that on top of a slack system. I've got invoices to write and its the end of the financial year so I have book keeping to do. I need to have this machine up and running.