SD card reader Ricoh e822 not working

dmesg|grep -i sdhci
[ 1.195136] sdhci: Secure Digital Host Controller Interface driver
[ 1.195140] sdhci: Copyright(c) Pierre Ossman
[ 1.490151] sdhci-pci 0000:03:00.0: SDHCI controller found [1180:e822] (rev 0)
[ 1.490191] sdhci-pci 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1.490247] sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
[ 1.490257] sdhci-pci 0000:03:00.0: setting latency timer to 64
[ 1.490349] mmc0: SDHCI controller on PCI [0000:03:00.0] using DMA
[ 1.490365] sdhci-pci 0000:03:00.4: SDHCI controller found [1180:e822] (rev 0)
[ 1.490389] sdhci-pci 0000:03:00.4: PCI INT C -> GSI 16 (level, low) -> IRQ 16
[ 1.490412] sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
[ 1.490421] sdhci-pci 0000:03:00.4: setting latency timer to 64
[ 1.490503] mmc1: SDHCI controller on PCI [0000:03:00.4] using DMA
[ 2433.716435] sdhci-pci 0000:03:00.0: PCI INT A disabled
[ 2433.716885] sdhci-pci 0000:03:00.4: PCI INT C disabled
[ 2435.931779] sdhci-pci 0000:03:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[ 2435.931812] sdhci-pci 0000:03:00.0: restoring config space at offset 0x4 (was 0x0, writing 0xd6500a00)
[ 2435.931826] sdhci-pci 0000:03:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
[ 2435.932113] sdhci-pci 0000:03:00.4: restoring config space at offset 0xf (was 0x300, writing 0x30b)
[ 2435.932146] sdhci-pci 0000:03:00.4: restoring config space at offset 0x4 (was 0x0, writing 0xd6500800)
[ 2435.932155] sdhci-pci 0000:03:00.4: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)
[ 2435.932166] sdhci-pci 0000:03:00.4: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
[ 2435.962460] sdhci-pci 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 2435.962464] sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
[ 2435.962504] sdhci-pci 0000:03:00.0: setting latency timer to 64
[ 2435.963600] sdhci-pci 0000:03:00.4: PCI INT C -> GSI 16 (level, low) -> IRQ 16
[ 2435.963604] sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
[ 2435.963613] sdhci-pci 0000:03:00.4: setting latency timer to 64

You can try the sm_ftl or ssfdc modules

sudo rmmod sdhci-pci
sudo modprobe MODULENAME
(do some testing -- did it work? no?)
sudo rmmod MODULENAME
sudo modprobe OTHERMODULENAME

So you suggest to remove the sdhci-pci module and than probe for "MODULENAME". But there is nothing to probe when I remove it, right? Do I have to download sm_ftl and ssfdc first or are they already somewhere on my system.

Sorry if this appears to be a stupid question but its my first time fooling around with modules.
Help will be appreciated.

Ah! now I understand what you mean. I tryed the modules you suggested. When I use sdhci-pci the LED blinks. It doesn't do anything with the other modules. Still don't see it in nautilus when I insert the card. Thank you very much for your knowledge!

So how do I browse it?

I also tried this:

bas@Bla:~/Downloads/sdricoh_cs-0.1.4$ make
make -C /lib/modules/2.6.35-24-generic/build SUBDIRS=/home/bas/Downloads/sdricoh_cs-0.1.4 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.35-24-generic'
  CC [M] /home/bas/Downloads/sdricoh_cs-0.1.4/sdricoh_cs.o
/home/bas/Downloads/sdricoh_cs-0.1.4/sdricoh_cs.c: In function ‘sdricoh_pcmcia_suspend’:
/home/bas/Downloads/sdricoh_cs-0.1.4/sdricoh_cs.c:535: error: too many arguments to function ‘mmc_suspend_host’
make[2]: *** [/home/bas/Downloads/sdricoh_cs-0.1.4/sdricoh_cs.o] Error 1
make[1]: *** [_module_/home/bas/Downloads/sdricoh_cs-0.1.4] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.35-24-generic'
make: *** [default] Error 2

I would not use sdricoh_cs ; if you look at their homepage, it says that their code has already been incorporated into the kernel, so if it is going to magically work, it will. Yes, sm

Once you modprobe the modules, you can check the end of the kernels message buffer, using the command "dmesg" (this will print a lot, so you might want to use "dmesg | tail -n 200 " to only keep the last 200 lines.

If sdhci-pci causes the led to blink, then your device might (might, not is) be working. You may still need to mount the device onto your filesystem using the mount command.

Check the output of the kernel message buffer (as above), and have a look to see if there are any
new /dev/sd* entries. You may need to cycle the card for the module to work. Not sure -- I don't have a ricoh card reader.

Looks good I think. It the amount of mem on the card. But, what now? How do I browse it?

[ 1627.965572] mmc1: SDHCI controller on PCI [0000:03:00.4] using DMA
[ 1635.560140] mmc1: new high speed SDHC card at address b368
[ 1635.592164] mmcblk0: mmc1:b368 SDC 59.5 GiB
[ 1635.592263] mmcblk0: p1
[ 1803.721529] CE: hpet increased min_delta_ns to 11250 nsec
[ 2300.900409] mmc1: card b368 removed
[ 2304.551246] mmc1: new high speed SDHC card at address b368
[ 2304.551501] mmcblk0: mmc1:b368 SDC 59.5 GiB
[ 2304.551692] mmcblk0: p1
[ 3392.300416] mmc1: card b368 removed
[ 3993.349525] mmc1: new high speed SDHC card at address b368
[ 3993.349760] mmcblk0: mmc1:b368 SDC 59.5 GiB
[ 3993.349927] mmcblk0: p1

bas@vaio:/dev$ ls /sd*
ls: cannot access /sd*: No such file or directory

When I ls the dev dir while putting the card in and out 2 entries appear:

mmcblk0
mmcblk0p1

Could it be black listed or somethin?

sudo mount /dev/mmcblk0 /mnt
[sudo] password for bas:
mount: you must specify the filesystem type

sudo mount /dev/mmcblk0 /mnt -t vfat

[ 4920.590045] mmcblk0: mmc1:b368 SDC 59.5 GiB
[ 4920.590215] mmcblk0: p1
[ 5752.890647] FAT: bogus number of reserved sectors
[ 5752.890654] VFS: Can't find a valid FAT filesystem on dev mmcblk0.

I installed this or exFAT support:
https://launchpad.net/~relan/+archive/exfat/+files/fuse-exfat_0.9.3-1_amd64.deb

No it says this:
bas@vaio:/dev$ sudo mount.exfat-fuse /dev/mmcblk0 /mnt
FUSE exfat 0.9.3
ERROR: exFAT file system is not found.

Now what? Does anyone still have any ideas? Im out of options... Thanks for the help.

It sounds like your reader is working, but you might want to use gparted to reformat the card to a readable filesystem -- where did you get the card from? How was it formatted? mmc/sd cards (mmc is a subset of sd, without the "secure" memory sectors AFAIK), should pretty much be seen as raw storage until you format it.

If there is no data on the card, I would just reformat it.

Its's brand new "Transcend 64 GB SDXC Memory Card".
I got it out of the packaging and put it straight into a brand new "Toshiba Camileo sx500" camcorder. Recorded some video's @ 1080i (60 fps).
Took it out and put it in the card reader. I would like to get the recordings of.

If I reformat it. Is it possible the camcorder doesn't understand the filesystem anymore? I also read somewhere if you change the filesystem, the lifetime of the SD card is reduced but im not shure if thats true...

Exfat is not supported without the kernel module you were trying to compile earlier, and even with that it is experimental. Exfat is relatively new. Mac OS only suported it two months ago.

Try formatting the device back to fat32, then re-record with your camcorder -- it could be that your camcorder can read/write fat, but can also do exfat. Of course you will lose the data in your current recording.

You might want to know, there is a PPA for the exfat FUSE driver.

https://launchpad.net/~relan/+archive/exfat

This will let you simply add exfat support using your package manager; however this is experimental code, so if your data gets wiped on that filesystem, so be it.

Thanks a lot for your help mycae
Already tried your link but it didnt work

I was able to plug in the camera and use MTP to transer in R/W.
Thanks for the help. Hopefully some one reverse engeneers M$ exfat in the futere so its compatible with ubuntu gparted and fdisk

regards
B