Realtek Barossa PCI Express SD card reader no longer working, rts_pstor module missing

[Carlos Montalvo]

The card reader is recognized (eg. via lspci), but the system doesn't detect nor mount any SD card.

It was working fine with the previous Quantal kernel, using the rts_pstor module. I remember reading about this module having been removed from upstream kernel source since version 3.8.0.

I have tried loading the following modules manually with modprobe, but none of them seem to work: rtsx_pci_sdmmc, rts5139, rtsx_pci

Another thing I've tried is to compile the rts_pstor module from a source tarball downloaded from Realtek's website. However, the module fails to compile, I believe it's because the source hasn't been updated since 2012 and so assumes an older kernel version. I have included the original tarball from Realtek as an attachment.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-26-generic 3.8.0-26.38
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: carlos 2078 F.... pulseaudio
Date: Tue Jul 16 21:25:11 2013
EcryptfsInUse: Yes
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=99bdf4ab-cb9c-4a96-8cda-97ea34e9572b
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2012-10-31 (258 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MachineType: Hewlett-Packard Compaq Mini CQ10-400
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=0788b9a6-56d9-4652-beb6-772a9688f512 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-26-generic N/A
 linux-backports-modules-3.8.0-26-generic N/A
 linux-firmware 1.106
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 21:25:25.642: The udisks-daemon is running (name-owner :1.26).
UpgradeStatus: Upgraded to raring on 2013-04-25 (82 days ago)
dmi.bios.date: 08/17/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 148A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 79.49
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd08/17/2010:svnHewlett-Packard:pnCompaqMiniCQ10-400:pvr049E100000202400110300000:rvnHewlett-Packard:rn148A:rvr79.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: Compaq Mini CQ10-400
dmi.product.version: 049E100000202400110300000
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

[Carlos Montalvo (cmontalvo-sv)]

As suggested, I installed the upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy

The system is still unable to mount SD cards, so I can confirm that the bug is also present in the new kernel.

[Carlos Montalvo (cmontalvo-sv)]

I tested Xubuntu 13.10 (Saucy Salamander) and the bug is still present.

The affected computer is a Compaq Mini CQ10-400.

[Carlos Montalvo (cmontalvo-sv)]

I installed the BIOS F.15 update (I had to reinstall the factory-default Windows 7, install the update, and then reinstall Xubuntu due to partitioning issues).

The problem still seems to be present.

Output of dmidecode added as attachment.

[penalvch (penalvch)]

Carlos Montalvo, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty/ and advise to the results?

[Carlos Montalvo (cmontalvo-sv)]

It seems that the bug is fixed in the 3.14-rc4 kernel. Thanks Christopher and Joseph!

[penalvch (penalvch)]

Carlos Motalvo, could you please test for this in Trusty via http://cdimage.ubuntu.com/daily-live/current/ and advise if this is reproducible?

[Carlos Montalvo (cmontalvo-sv)]

I booted the Trusty live image from the address above using an USB key (no installation to hard disk) and none of the SD cards I tried were recognized. Running dmesg didn't even show anything related to inserting/removing the cards.

[penalvch (penalvch)]

Triaged as fix in upstream, but reproducible in Trusty.

[ducke (ducke86)]

Hello,
Firstly I would like to apologize for my English, I go through google translation.
I'm a little French and a beginner in Ubuntu, which is not going to make things easy for you :)

It happens to me the same problèmeque Carlos Montalvo, my sd card reader does not work on Mint 16 Cinnamon.
I tried on a live usb xubuntu 14.04 but the problem is the same.

 Manufacturer: Hewlett-Packard
 Product Name: Compaq Mini CQ10-400
 Version: 04A0100000002400110300000
 Serial Number: CNC02359B8
 UUID: 0FBA8E21-6673-6FA8-8904-0021CC486AD6
 Wake-up Type: Power Switch
 SKU Number: WR26

here is the command lsusb

Bus 001 Device 002: ID 04f2:b1eb Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[ducke (ducke86)]

sorry I can not find how to edit my first post.

Here is the return of the order lspci

[code]00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 04)
01:00.1 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Barossa PCI Express Card Reader (rev 01)
02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe

if someone want to help me to solve the problem is it would be nice.

thank you in advance

[penalvch (penalvch)]

ducke, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

Carlos Montalvo, the next step is to fully reverse commit bisect in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[Carlos Montalvo (cmontalvo-sv)]

Sorry for taking so long to answer, I didn't get the last comment by e-mail.

I'm following the instructions right now and will post the results as soon as possible.

[Geoff (geoffch)]

I found this discussed over at https://bugzilla.redhat.com/show_bug.cgi?id=727990 (comments #12 and #13):

#12: "The rts_pstor driver has been removed from staging in kernel 3.8 and another driver (rtsx_pci) is able to handle this hardware. I've tested it with the recent kernel-3.8.1-201.fc18.x86_64 and it works."

#13: "Excellent find. I believe the driver is actually called rtsx_pci_ms (the rtsx_pci driver is something it depends on.) This is available in all current kernels."

These "rtsx" modules exist in Ubuntu. However, the Barossa card never associates with them, so the problem remains.

P.S.: I have a HP dv4-2164us netbook with this card, and this issue is one reason why I haven't upgraded from 12.04.

[penalvch (penalvch)]

Geoff, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs