[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: SD card reader (Winbond)



David G. Miller wrote:
> "Mikkel L. Ellertson" <mikkel infinity-ltd com> 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
>>
> 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.
> 
For me, it auto-mounted as soon as I did the modprobe tifm_sd. But I
have the card labeled, so that may make a difference. I remember
some problems about USB drives not auto-mounted if they were not
labeled, so you may run into the same problems. In any case, the
device will be /dev/mmcblk.<something>, and not /dev/sd<something>.
The card is not treated as a SCSI drive, unlike the USB connected
ones. It may still be using the SCSI code - I have not looked into
it that deeply, but it is a multi-media card block device. (mmcblk)

>From the differences in responce, I suspect that we have different
setups. My laptop only has a single slot for memory cards, and does
not support the Smart Media or Compact Flash cards.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]