Internal microsd card reader does not work in Ubuntu 17.10

Bug #1730152 reported by funicorn
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Ubuntu 17.10 x86_64 of Wayland-Session is running on a HP Envy 13-ad1xx notbook with a internal microsd card reader. The system gives no response when inserting different micro sd cards, which work fine on Windows 10. I report this bug in hope that the upstream may notice and make some change on the suited driver or kernel module. I would provide more information under further direction.

According to `lspci` output, the model name is 'Alcor Micro Device 6625'.

`udevadm monitor --env` gives no related events when inserting or pulling out the microsd card, in which only thermal_zone changes are recorded. No related events are recoded in /var/log/kern.log either.

With sd card being inserted, `sudo fdisk -l` and `sudo blkid` gives no related information. The outputs are all about partitions on the local disk. No sdhc or mmc device is found in /dev/ either.

The only implication now is the system notice the existence of the card reader, in terms of `lspci` outputs, the '01:00.0 Unassigned class [ff00]: Alcor Micro Device 6625', even when a sd card is inserted:

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: limorg 1514 F...m pulseaudio
 /dev/snd/controlC0: limorg 1514 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 10:29:26 2017
HibernationDevice: RESUME=UUID=8f370e7c-280d-4864-b687-a2c81ce87247
InstallationDate: Installed on 2017-10-22 (13 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 0bda:5620 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Laptop 13-ad1xx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=67e321d1-4810-4157-8c29-09aaaac51ea7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-29 (6 days ago)
dmi.bios.date: 07/26/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83A8
dmi.board.vendor: HP
dmi.board.version: KBC Version 39.32
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/26/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A8:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY Laptop 13-ad1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

Revision history for this message
funicorn (funicorn) wrote :
funicorn (funicorn)
description: updated
tags: added: kernel-module
removed: kernal-module
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: artful
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 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'.

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/v4.14-rc8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
funicorn (funicorn) wrote :

The bug exists in ubuntu 16.04. It still exists in the mainstream kernel v4.14-rc6. I haven't tested in kernel v4.14-rc8.

Revision history for this message
funicorn (funicorn) wrote :

OK. I have tested it in the newest mainstream kernel v4.14-rc8. There is nothing changed.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Unless someone writes driver for the card reader, it's not going to work.

Changed in linux (Ubuntu):
importance: Medium → Wishlist
Revision history for this message
Bao Pham (baothaipham2017) wrote :

Please someone write the driver for this card reader.

Revision history for this message
sfc (sfc-0) wrote :

You could try this driver: https://github.com/josch09/ampe_stor. From the code, it seems supporting AU6601, AU6621, and AU6625, but it's not working on my envy 13 ad110tu (AU6625). It can detect the card, and get the capacity, but then many errors will occur and finally the reader dies. Maybe it will work on your device.

Revision history for this message
sfc (sfc-0) wrote :
Revision history for this message
funicorn (funicorn) wrote :

@sfc Could you explain a little more how exactly to use the dkms.conf file? Should I put the file in the same ampe_stor directory?

Revision history for this message
sfc (sfc-0) wrote :

@funicorn Yes. Put that dkms.conf in the same ampe_stor directory and use "dkms add" to add it. Please refer to https://help.ubuntu.com/community/DKMS and https://github.com/dell/dkms for detailed instructions.

Revision history for this message
funicorn (funicorn) wrote :

@sfc I installed the driver and had it loaded, however the card reader remains unassigned after reboot. Maybe I should wait for some kernel update fixing this issue. Thanks a lot for help.

Revision history for this message
Neculai Dan Ciprian (enkumber) wrote :

Still no way to fix this?

Revision history for this message
Alexey (alexey-muranov) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.