Sony memory reader in CB-712/4 does not work

[mirekm]

(original report was that SD/MMC didn't work, but SD works now according to Matt LaPaglia. He posted lspci and dmesg output on a fresh bug he opened specifically about the Sony memory stick part: bug 200668, which is marked as a dup of this one. Perhaps that should be the other way around, or this should be closed since it was originally about the SD reader, which is now fixed? I would have just commented normally, but it probably helps if this is the _first_ thing someone sees when looking at this bug... Sorry for the bug noise, everyone.

This bug is specifically about readers that are part of the ENE Technology cardbus controller with PCI ID 1524:1412. Don't post about totally different SD/MMC hardware on this bug; open a new one. See also bug 303844 about the SD reader in PCI ID 1524:1411, which has a similar name but doesn't work at all with Linux.)

My computer - acer 2492NWLMi
kernel 2.6.20-13-generic
lspci:
06:04.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
06:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
06:04.2 Generic system peripheral [0805]: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01)
06:04.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc: (rev 01)
06:04.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller (rev 01)

ProblemType: Bug
Architecture: i386
Date: Sun Apr 1 07:10:28 2007
DistroRelease: Ubuntu 7.04
Uname: Linux mm4 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

[Justin Sunseri (jmsunseri)]

This bug appeared on my computer as well after the most recent kernel upgrade. I also noticed that now when the SD card is plugged into the camera and connected to the USB port it no longer establishes a connection with the camera. This also used to work before the most recent kernel change.

[Justin Sunseri (jmsunseri)]

This bug is still present in 2.6.20-14-generic and is a regression. This card reader has worked for over a year and worked out of the box in edgy. What ever information is needed to resolve this problem please let me know as soon as possible this is a very important piece of hardware for me.

[ 497.928000] mmcblk0: mmc0:b368 SD 249856KiB
[ 497.928000] mmcblk0: p1

This is the output from dmesg when i insert the card. It appears as though it detects that the card has been inserted but g-v-m does not mount the drive, even though it is set to do so, and it does not appear in nautilus as a file system and no directory is created for it in /media/

[Justin Sunseri (jmsunseri)]

When i boot back into 2.6.20-12 the card reader works as expected.

[Justin Sunseri (jmsunseri)]

sorry i have not figured out how to attach 2 files for the same bug comment.

[Dagfinn Ilmari Mannsåker (ilmari)]

The problem is that HAL can't find the parent device from the DEVPATH passed from the udev event. Here's the hald --debug output when plugging and unplugging the card on -14. There was an MMC/SD merge in -13, which I suspect is the culprit.

[Dagfinn Ilmari Mannsåker (ilmari)]

For completeness, here's the 'udevmonitor --udev --environment' output as well.

[Dagfinn Ilmari Mannsåker (ilmari)]

I can confirm it working on 2.6.20-12-generic, here's the udevmonitor output. Note the device-based DEVPATH, as opposed to the class-based one on 2.6.20-14-generic

[Justin Sunseri (jmsunseri)]

It's a one line change that should be in before feisty's release.

[JonniePee (policke8872)]

I too have this problem, the card reader worked fine under Edgy, but when I upgraded to Feisty it stopped working. I am working on a Sager Hel80 Notebook with a 4-1 Internal Reader. Feisty

06:04.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
        Subsystem: COMPAL Electronics Inc Unknown device 0020
        Flags: bus master, medium devsel, latency 168, IRQ 16
        Memory at d2000000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=06, secondary=07, subordinate=0a, sec-latency=176
        Memory window 0: 88000000-8bfff000 (prefetchable)
        Memory window 1: 90000000-93fff000
        I/O window 0: 00004000-000040ff
        I/O window 1: 00004400-000044ff
        16-bit legacy interface ports at 0001

06:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
        Subsystem: COMPAL Electronics Inc Unknown device 0020
        Flags: medium devsel, IRQ 11
        Memory at d2001800 (32-bit, non-prefetchable) [disabled] [size=128]
        Capabilities: [80] Power Management version 2

06:04.2 Generic system peripheral [0805]: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01) (prog-if 01)
        Subsystem: COMPAL Electronics Inc Unknown device 0020
        Flags: bus master, medium devsel, latency 64, IRQ 17
        Memory at d2001c00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

06:04.4 FLASH memory: ENE Technology Inc Unknown device 0551 (rev 01)
        Subsystem: COMPAL Electronics Inc Unknown device 0020
        Flags: medium devsel, IRQ 255
        Memory at d2001000 (32-bit, non-prefetchable) [disabled] [size=256]
        Capabilities: [80] Power Management version 2

Sorry I am new to linux and ubuntu.

[Ben Collins (ben-collins)]

Available in 2.6.20-15.25

[Brian Rogers (brian-rogers)]

On 2.6.20-13-generic, SD cards did not automount.
Now with 2.6.20-15.25, the device does not even appear in /dev and I get the following in dmesg:

mmcblk: probe of mmc0:d5d9 failed with error -28

[Brian Rogers (brian-rogers)]

Update: 2.6.20-15.27 has resolved the issue. My SD slot works again, and SD cards are automounted.

[Jan Kaláb (pitel)]

Fresh Feisty install, 2.6.20-15-generic, and card reader doesn't work.

[rogue780 (shawn-shawn-haggard)]

Just to add to this--I'm having the same issue with a fresh feisty install. Although in edgy it worked fine.

[Justin Sunseri (jmsunseri)]

I think you guys must be having a different issue than the one i reported.

On 5/10/07, rogue780 <email address hidden> wrote:
>
> Just to add to this--I'm having the same issue with a fresh feisty
> install. Although in edgy it worked fine.
>
> --
> MMC/SD memory card reader does not work
> https://bugs.launchpad.net/bugs/99648
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sincerely

Justin Sunseri

[Michael Stein (der-stein)]

On kernel 2.6.20-15.27 the problem still exists at me.

Michael

[Matt LaPaglia (mlapaglia)]

This is still happening in Hardy:

06:04.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
 Subsystem: COMPAL Electronics Inc Unknown device 0020
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 168, Cache Line Size: 128 bytes
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at d2000000 (32-bit, non-prefetchable) [size=4K]
 Bus: primary=06, secondary=07, subordinate=0a, sec-latency=176
 Memory window 0: d4000000-d7fff000 (prefetchable)
 Memory window 1: d8000000-dbfff000
 I/O window 0: 00004400-000044ff
 I/O window 1: 00004800-000048ff
 BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
 16-bit legacy interface ports at 0001

06:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
 Subsystem: COMPAL Electronics Inc Unknown device 0020
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Interrupt: pin B routed to IRQ 17
 Region 0: Memory at d2001800 (32-bit, non-prefetchable) [disabled] [size=128]
 Capabilities: <access denied>

06:04.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01) (prog-if 01)
 Subsystem: COMPAL Electronics Inc Unknown device 0020
 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Interrupt: pin B routed to IRQ 17
 Region 0: Memory at d2001c00 (32-bit, non-prefetchable) [size=256]
 Capabilities: <access denied>

06:04.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller (rev 01)
 Subsystem: COMPAL Electronics Inc Unknown device 0020
 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Interrupt: pin B routed to IRQ 17
 Region 0: Memory at d2001900 (32-bit, non-prefetchable) [size=256]
 Capabilities: <access denied>

Only SD cards work now, not Sony-styled memory sticks.

[Matt LaPaglia (mlapaglia)]

I added my previous bug as a dup, 2.6.24 to the affected list, and confirmed it (the dup was already marked as confirmed, but delayed until Ibex.

[Leann Ogasawara (leannogasawara)]

Removing linux-source-2.6.24 task since beginning with Hardy, kernel bugs should be reported against the "linux" package which this already is. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Matt LaPaglia (mlapaglia)]

This is still an issue in the latest intrepid beta.

the sony memory sticks are not recognized, nothing appears in dmesg.

[Leann Ogasawara (leannogasawara)]

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. However, this will remain open against the actively developed kernel. Thanks.

[Peter Cordes (peter-cordes)]

This seems similar to bug 62995, which is closed, so I'll repost here some info I posted there about ENE chipsets.

I found this mailing list post saying that the 1524:0550 device ID has never worked, but 1524:0551 does work these days:
http://osdir.com/ml/linux.drivers.sdhci.devel/2007-09/msg00026.html

But someone seems to have had success in 2006 with a 1524:0550 card reader:
http://marc.info/?l=linux-kernel&m=116758515323702&w=2

 My Toshiba A70, which has never had its SD slot working under Linux has (lspci w/ and without -n):
02:04.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller
02:04.0 0607: 1524:1411

02:04.1 ...

02:04.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (prog-if 01)
02:04.2 0805: 1524:0550 (prog-if 01)

[ 35.794406] sdhci-pci 0000:02:04.2: SDHCI controller found [1524:0550] (rev 0)
[ 35.794465] sdhci-pci 0000:02:04.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 35.794606] mmc0: SDHCI controller on PCI [0000:02:04.2] using PIO

 Nothing happens at all when I insert an SD or MMC card (Hardy and Intrepid, and I think I've had Gutsy on it, but not older than that.)

[Peter Cordes (peter-cordes)]

can someone update the bug title to say what hardware it's about?

 There are a lot of "mmc doesn't work" bugs, and I'm trying to sort them out so I can tell if my problem on the tosh A70 is already known. And to help people find the right bug to post more info on. A lot of times people post with info on some totally different SD/MMC hardware on a bug about one kind of hardware, because the bug title was totally generic.

[Justin Sunseri (jmsunseri)]

Why did you all of a sudden change the summary of the bug? This affects me
and it has nothing to do with a sony card reader.

Sincerely

Justin Sunseri
Please don't print this e-mail unless you really need to.

On Mon, Dec 1, 2008 at 2:43 PM, Peter Cordes <email address hidden> wrote:

> ** Summary changed:
>
> - MMC/SD memory card reader does not work
> + Sony memory reader in CB-712/4 does not work
>
> ** Description changed:
>
> + (original report was that SD/MMC didn't work, but SD works now according
> + to Matt LaPaglia.
> +
> + This bug is specifically about readers that are part of the ENE
> + Technology cardbus controller with PCI ID 1524:1412. Don't post about
> + totally different SD/MMC hardware on this bug; open a new one. See also
> + bug 303844 about the SD reader in PCI ID 1524:1411, which has a similar
> + name but doesn't work at all with Linux.)
> +
> My computer - acer 2492NWLMi
> kernel 2.6.20-13-generic
> lspci:
> 06:04.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller
> (rev 10)
> 06:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader
> Controller (rev 01)
> 06:04.2 Generic system peripheral [0805]: ENE Technology Inc ENE PCI
> Secure Digital Card Reader Controller (rev 01)
> 06:04.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc:
> (rev 01)
> 06:04.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller
> (rev 01)
>
> ProblemType: Bug
> Architecture: i386
> Date: Sun Apr 1 07:10:28 2007
> DistroRelease: Ubuntu 7.04
> Uname: Linux mm4 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007
> i686 GNU/Linux
>
> ** Tags added: sd
>
> --
> Sony memory reader in CB-712/4 does not work
> https://bugs.launchpad.net/bugs/99648
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Peter Cordes (peter-cordes)]

> Why did you all of a sudden change the summary of the bug?

 I'm trying to sort out the SD card reader bugs so there is one open bug for each specific piece of hardware that doesn't work. I thought this bug looked like it should be about this hardware, not yours, since you jumped in later and realized that you were reporting something different from the others.

 I guess you assumed that this bug was now about your problem, which is fair enough given the several replies on that topic. So maybe I was a little cavalier in taking over this bug to make it into the originally reported issue. However, something has to change, since this bug # can't be about two separate bugs... Bugs have to be very specific so they can eventually get closed when fixed, instead of morphing into the next problem. I was trying to figure out my own hardware, and eventually reported bug 303844.

> This affects me and it has nothing to do with a sony card reader.

 You have a Ricoh R5C822, which is not the same hardware as the original reporter, or Matt LaPaglia. Are the problems you're reporting more like bug 247819?

 I tagged some other bugs with "sd":
 https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=sd
but there are probably others about SD card readers that aren't tagged. Hmm, maybe I shouldn't have picked a tag that also stands for scsi-disk. Ubuntu maintainers, please advise... I can go retag bugs with sdhci or something. (although some hw uses tifm...)

 So sorry for the inconvenience, but could you open a new bug report for your bug? You can link to this bug for reference, but it would be good to include a current lspci -vvnn, dmesg, and kernel version in the new bug. Or if you find another bug that looks like what's affecting you, see if it needs more info or something.

 thanks.

[Justin Sunseri (jmsunseri)]

Never mind I'm just going to unsubscribe from this bug.

Sincerely

Justin Sunseri
Please don't print this e-mail unless you really need to.

[David Stansby (dstansby-deactivatedaccount)]

May I ask why there is still a 7.04 milestone here, as 7.04 has been unsupported for the best part of half a year now.

[quezak (quezak)]

I Have the same bug I think... SD cards work, Memory Sticks don't (I don't have a MMC to check).

My lspci -vvnn in attachement.

[csantiago (santiago-carlos)]

It is stated that bug #99648 is related to device PCI 1524:1412 and bug #303844 is related to PCI 1524:0550.

As you can see from file in attachment, my card reader has the following devices (and subdevices):
1524:1412
1524:0530
1524:0550
1524:0520
1524:0551

Has my hardware has both devices, I filed the 'lspci -vvnn' listing to both bugs.

I am using using Ubuntu 9.04 after a fresh install. And this is NOT a regression fail. It never worked.

If it maters, my linux kernel is (uname -r):
2.6.30-020630rc4-generic

@Quezak,

I dont know what kind of SD cards you are using. I am trying to use one just like the one at http://picnicb.ciao.com/de/143018331.jpg with no luck. Card and reader works OK on windows.

What is the size of the SD cards you are using?

[Jeremy Foshee (jeremyfoshee)]

Unassigned from Ben Collins.

-JFo

[raulegastelo2 (raulegastelo2)]

I am running Ubuntu 9.10 Karmic Koala on a Toshiba Satellite and I can not get my ENE Card Reader working. Any help would be appreiciated. I am 100% new to this OS so simple step by step would be great. Thanks.

[xproflmfao (baileyhkg-deactivatedaccount)]

I am running Ubuntu 10.04 Lucid Lynx on a PCG-7141L with a "MagicGate" Memory Stick Slot. My official 128MB Sony stick is not running on Ubuntu. When I stick it in, the light indicator on my Sony doesn't flash nor does the drive ever show up in the OS. I have been using Ubuntu for nearly a year, but I am not a computer geek. After googling around the internet, I've learned that some sort of Ricoh software is required. However, when I put in the lspci command in the terminal, the Ricoh driver is shown and it even mentions Memory Stick/Memory Stick Pro! I'm going to attach the following picture to clear things up a bit. Any help would be appreciated.

[Jeremy Foshee (jeremyfoshee)]

resetting to fix released. If you feel you are affected by a similar issue, please file new individual bugs containing your apport collected information. This closure is due in very large part to the original report being made in 2007 and our desire to have one bug for one issue. It is not likely that the issue reported here so long ago is still in effect.

Thanks!

~JFo