** Description changed:

  My Toshiba A70 laptop's SD card reader with PCI ID 1524:0550  (part of
  an ENE CB-710/2/4 Cardbus Controller) doesn't work with Linux.  I
  haven't tried Ubuntu pre-gutsy, but it hasn't worked with Gutsy, Hardy,
  or Intrepid.  I've never seen it work under Linux, so AFAIK this isn't a
  regression.  This hardware is a few years old...
  
  There are various bug reports on very similar hardware, but most
  reporters haven't been careful to report PCI IDs, or even choose non-
  generic titles, so the SD card reader bugs are a mess.  I'm opening a
  new one that's just about this specific hardware, instead of trying to
  revive one of the old bugs.
  
+  Note that this not the same as bug 99648.  Please look at both and
+ decide if your bug is exactly either of those.  If not, open a new bug.
+ (see
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/303844/comments/12)
+ 
+ (update: incorporating some of the stuff figured out in the first few 
comments)
+  This bug is about the SD reader, while bug 99648 is about the Sony Memory 
Stick reader not working in a very similar piece of hardware.  This bug is 
about hardware with 4 PCI subdevices (02:04.0 - 02:04.3), not 5 (.0 - .4).  The 
hardware in bug 99648 also has a 1524::0551 PCI device, while the hardware in 
this bug doesn't.  Although it's not clear which of these differences 
distinguishes between the hardware that Linux's driver handles and the hardware 
that doesn't work.  The problem seems to be lack of documentation from the 
manufacturer, as usual.
+  So it's possible you might have this bug even though you have a 1524::0551 
PCI device, or if you have 5 PCI subdevices.  Please check extra carefully 
before adding comments here, since all this similar hardware is confusing 
enough already.  If your hardware does have a 1524::0551 device, and the SD 
reader doesn't work, and it never worked (so it's not a regression, which would 
require a new bug report), then please say so when you post, so we'll know you 
read this and we'll be more likely to believe you.  Even then, unless someone 
does some reverse engineering, this hardware will probably never be supported 
without information from the manufacturer.  All we could do with corrections to 
which hardware is affected is give a more accurate assessment of when you are 
stuck with incompatible hardware, and when you should keep trying to get the 
drivers working.
+ (end update)
  
  OS:
  Linux whale 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 
GNU/Linux
  Ubuntu 2.6.27-10.20-generic
  
  lspci -vvnn:
  02:04.0 CardBus bridge [0607]: ENE Technology Inc CB-710/2/4 Cardbus 
Controller [1524:1411]
          Subsystem: Toshiba America Info Systems Device [1179:ff01]
  02:04.1 FLASH memory [0501]: ENE Technology Inc ENE PCI Memory Stick Card 
Reader Controller [1524:0530]
  ...
  02:04.2 SD Host controller [0805]: ENE Technology Inc ENE PCI Secure Digital 
Card Reader Controller [1524:0550] (prog-if 01)
          Subsystem: Toshiba America Info Systems Device [1179:ff01]
          Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
          Interrupt: pin B routed to IRQ 17
          Region 0: Memory at d0215000 (32-bit, non-prefetchable) [size=256]
          Capabilities: [80] Power Management version 2
                  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold-)
                  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
          Kernel modules: sdhci-pci
  02:04.3 FLASH memory [0501]: ENE Technology Inc FLASH memory: ENE Technology 
Inc: [1524:0520]
  ...
  
   shdci-pci loads ok,
  [458502.494499] sdhci: Secure Digital Host Controller Interface driver
  [458502.494511] sdhci: Copyright(c) Pierre Ossman
  [458502.503353] sdhci-pci 0000:02:04.2: SDHCI controller found [1524:0550] 
(rev 0)
  [458502.503386] sdhci-pci 0000:02:04.2: PCI INT B -> GSI 17 (level, low) -> 
IRQ 17
  [458502.507085] mmc0: SDHCI controller on PCI [0000:02:04.2] using PIO
  (see attached dmesg output for the full thing.  I can attach a full lspci 
-vvnn if anyone wants.)
  
   The hardware works with these cards under another OS, so it's the
  hardware is physically ok.  (It is old, though.  Even WinXP doesn't work
  with 2GB SD cards, only 1GB.  2GB isn't even SDHC, which of course
  doesn't work either.)
  
   When I insert an MMC or SD card, the light on the card reader flashes for a 
second, then goes out.  Nothing is reported in the kernel log, and no /dev/mmc* 
appears. Inserting a card increases the IRQ count for mmc0 by 2, removing a 
card generates 1 interrupt.
   17:      22500   IO-APIC-fasteoi   ATI IXP Modem, ATI IXP, mmc0
  Other than that, a whole lot of nothing happens.  Unloading and reloading the 
module repeatedly hasn't helped, so it's not an intermittent problem.
  
   This is _not_ the same hardware that Leu has on bug 31440.  I think I
  have the same hardware as the original submitter (who left -nn out of
  his lspci args, so I'm not sure), but since that bug has been closed
  (wontfix) based on Leu's hardware, it would probably be confusing to
  reopen it.
  
-  It's also not the same hardware as bug 99648, since mine only has 4
- subdevices (.0 - .3), not 5 (.0 - .4).  And the PCI device name is
- different, although that might just be an older PCI name database...
- 
   Someone thinks this hardware has never worked under Linux:
  "The 1524:0550 is a dead Dodo. I've never seen any reports of it working at 
all." from http://osdir.com/ml/linux.drivers.sdhci.devel/2007-09/msg00026.html
  
   But someone else does seem to have had success (with different hardware.  CB 
controller = 1524:1412, which has different subdevices).
  http://marc.info/?l=linux-kernel&m=116758515323702&w=2
+ (yup, turns out this is a different piece of hardware, and doesn't help for 
this bug.)

-- 
ENE CB-710/2/4 sdhci [PCI 1524:0550] doesn't work
https://bugs.launchpad.net/bugs/303844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to