"Mikkel L. Ellertson" <mikkel@xxxxxxxxxxxxxxxx> wrote:
If you are running the 2.6.19 kernel, instead of loading the
mmc_block and sdhci modules, try loading the tifm_sd module. If you
get a message like "kernel: tifm_7xx1: sd card detected in socket 1"
in your logs when you insert a card, then running "modprobe
I had not used my SD slot for a while, and when I tried it with the
2.6.19 kernel, the way I used to access it no longer worked. I am
not sure what version of the kernel changed things. When I first got
it working, I had this in my /etc/rc.d/rc.local:
# Setup the 5 in 1 card reader for SD cards.
#
setpci -s 04:06.2 4c.b=02
# Load the SD and MMC modules again.
modprobe sdhci || exit 1
modprobe mmc_block || exit 1
In order to get it to automount, I had to change a selinux mode.
semanage fcontext -a -t removable_device_t /dev/mmcblk.*
It doesn't look like it is needed any more...
lsmod says that tifm_7xx1 and tifm_core load automatically but I don't
see the device. If I "modprobe tifm_sd", I get the "card failed to
respond for a long period of time" message below. Removing the SD card
or putting it back in gets me the kobject_add message and call trace
(below):
tifm_7xx1: sd card detected in socket 3
tifm_7xx1: sd card detected in socket 3
tifm_sd: card failed to respond for a long period of time<6>tifm_7xx1:
sd card detected in socket 3
kobject_add failed for tifm_sd0:3 with -EEXIST, don't try to register
things with the same name in the same directory.
Call Trace:
[<ffffffff8026999a>] show_trace+0x34/0x47
[<ffffffff802699bf>] dump_stack+0x12/0x17
[<ffffffff80343e1a>] kobject_add+0x174/0x19f
[<ffffffff803acf0e>] device_add+0xaf/0x520
[<ffffffff8812789e>] :tifm_7xx1:tifm_7xx1_insert_media+0x247/0x2fd
[<ffffffff8024b96b>] run_workqueue+0xb2/0x109
[<ffffffff8024844c>] worker_thread+0xec/0x11e
[<ffffffff802324b7>] kthread+0xd0/0x100
[<ffffffff8025ced8>] child_rip+0xa/0x12
At least the system is now detecting the SD card and attempting to do
something with it. SELinux is in permissive mode so it shouldn't be
interfering with the activity.
For all I know the only problem is just that card doesn't automount but
would be accessible if I looked in the right place (e.g., dev/sd?) and
manually mounted it.
Cheers,
Dave
--
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce
