Comment 176 for bug 53923

Revision history for this message
Mackenzie Morgan (maco.m) wrote : Re: [Bug 53923] TIFM bug affecting also 2.6.22

Just for the heck of it, have you tried checking with an Edgy Live CD that the card reader itself isn't broken? The fact that dmesg isn't seeing anything happening there at all is a bit weird.

> I tried a fresh gutsy cd, everything works on my tablet pc (even the pen
> of course), but MMC cardreader. I repeat, this cardreader, with this
> card I am using now, worked without any manual intervention in edgy.
> Here in feisty and gutsy, the tifm_* modules won't do anything useful.
> Removing those modules, then inserting SDHCI, won't do anything either
> (where not doing anything means no messages in system logs in both
> cases). If I remove every related module, then do the setpci hack, then
> install only sdhci, I get this in the logs
>
> Jun 20 13:27:36 ubuntu kernel: [ 510.404000] sdhci: Secure Digital
> Host Controller Interface driver
> Jun 20 13:27:36 ubuntu kernel: [ 510.404000] sdhci: Copyright(c)
> Pierre Ossman
> Jun 20 13:27:36 ubuntu kernel: [ 510.404000] sdhci: SDHCI controller
> found at 0000:03:0b.3 [104c:803c] (rev 0)
> Jun 20 13:27:36 ubuntu kernel: [ 510.404000] ACPI: PCI Interrupt
> 0000:03:0b.3[D] -> GSI 23 (level, low) -> IRQ 19
> Jun 20 13:27:36 ubuntu kernel: [ 510.404000] mmc0: SDHCI at
> 0x58006800 irq 19 DMA
>
> but nothing will happen when inserting the card (again, no messages in
> the log).
>
> Please someone tell me how to provide more information, I am afraid that
> my case can be different from others and I would like to file a proper
> report *before* gutsy, since I reported a dupe of this *before feisty*
> (when I was wasting my time testing the beta), then had it fixed, then
> it broke again *after feisty* i.e. in the stable version. I believe in
> contributing to the community and reporting problems, but I am getting
> a
> little fed up with this particular bug.
>
> --
> tifm: Texas Instruments Card reader not working
>
> You received this bug notification because you are a direct subscriber
> of the bug.