Distribution: Opensuse 10.3 Beta 1 Hardware Environment: Laptop Asus G1S "08:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 08:01.1 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 08:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 12) 08:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 08:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)" It reads sd cards but not mmc or it does not support 4gb mmc cards
What kernel are you running? Support for large MMC cards was added rather recently. I'm quite impressed you've been able to find one.
Sorry, I see that we have a bugzilla field for that these days. :) This is most likely a hardware issue. It might be tweakable from software, but I'll need to dig through some specs first. Have you tried any other MMC cards?
sorry but i do not have other mmc. Just this 4gb. It's not a hardware issue because it works on other OS. I also have 2 sds, a 512 and 1gb. The 1gb card is or isn't detected, it works randomly. the 512 works just fine
I'm afraid no progress has been made on this. A relevant bit in the settings for the controller has been identified, but we have not found any way of modifying it (it is read from a EEPROM in your laptop). Philip Langdale also has this controller and has been digging into the issue. I haven't seen any progress from him yet though. Since it works in Windows, there should be a way of modifying the relevant bits. Could you see if you can find a tool that dumps the entire PCI config space for the Ricoh devices? (The equivalent of lspci -xxx in Linux)
Dell came through with the details on how to do this. You have to poke registers on the firewire function of the device. On my laptop it is device 03:01.0 but it might be different on yours. /sbin/setpci -s ‘03:01.0′ 0xCA=0×57 (Write Enable) /sbin/setpci -s ‘03:01.0′ 0xCB=0×02 (MMC Disable) /sbin/setpci -s ‘03:01.0′ 0xCA=0×00 (Write Disable) More details on my blog: http://intr.overt.org/blog/?p=59
Tester hasn't come back with a reply for several months, and the fix has been known to solve the issue on other machines. Closing bug.