Ubuntu
linux-source-2.6.22 package

  1. Bug #137686
  2. Comment #19

Comment 19 for bug 137686

Revision history for this message
Krzysztof Wyszyński (goomior) wrote : Re: [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs

After some hours of testing, I think tah the problem is related to udev. When I start one terminal I type:

sudo udevmonitor

and in the second one:

sudo modprobe mmc_block
sudo modprobe mmc_core
sudo rmmod sdhci

then udevmonitor says:

UDEV [1193066226.837458] remove /class/mmc_host/mmc0 (mmc_host)
UDEV [1193066226.837487] remove /bus/pci/drivers/sdhci (drivers)
UDEV [1193066226.837500] remove /module/sdhci (module)

Next I try to:

sudo modprobe sdhci

and udevmonitor says:

UDEV [1193066281.343161] add /module/sdhci (module)
UDEV [1193066281.343189] add /bus/pci/drivers/sdhci (drivers)
UDEV [1193066281.343201] add /class/mmc_host/mmc0 (mmc_host)

Nothing special. Now let's try to restart udev typing:

sudo /etc/init.d/udev restart

Udevmonitor produces a lot of output about reenabling some devices. Again, nothing special. Now let's try to remove sdhci:

sudo rmmod sdhci

and insert it again:

sudo modprobe sdhci

And after some sdhci insertions/removals, suprisingly, udevmonitor says:

UEVENT[1193067609.739142] add /module/sdhci (module)
UDEV [1193067609.740053] add /module/sdhci (module)
UEVENT[1193067609.741298] add /bus/pci/drivers/sdhci (drivers)
UDEV [1193067609.742317] add /bus/pci/drivers/sdhci (drivers)
UEVENT[1193067609.743938] add /class/mmc_host/mmc0 (mmc_host)
UDEV [1193067609.746477] add /class/mmc_host/mmc0 (mmc_host)
UEVENT[1193067609.841820] add /class/mmc_host/mmc0/mmc0:1234 (mmc)
UEVENT[1193067609.844307] add /block/mmcblk0 (block)
UEVENT[1193067609.844330] add /block/mmcblk0/mmcblk0p1 (block)
UDEV [1193067609.853536] add /class/mmc_host/mmc0/mmc0:1234 (mmc)
UDEV [1193067609.943687] add /block/mmcblk0 (block)
UDEV [1193067610.006325] add /block/mmcblk0/mmcblk0p1 (block)

Voilà. The SD card is detected and Nautilus asks for importing photos. Unfortunately, this process in unrepeatable :( Even the number of lines generated by udevmonitor when inserting/removing sdhci is not the same. After several (hundreds) of sdhci insertions/removals you may be able to get your card recognized. Maybe this comment doesn't solve the problem but now, at least, I have some algorithm to get my card recognized. It may take a long time, but finally it works.