Discussion:
Potential bug report for Realtek MicroSD Card Reader
Add Reply
Brandan Ballantyne
14 days ago
Reply
Permalink
Hey Team!

I'm new to Debian and running the latest Debian 12.10 with updates. I'm
having an issue with my MicroSD card reader and I'm not sure how to proceed.


My hardware is identified in lspci as

0000:31:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
RTS525A PCI Express Card Reader (rev 01)


Running 'sudo dmesg | grep mmc' shows

[    2.139647] mmc0: cannot verify signal voltage switch
[    2.254430] mmc0: non-supported SD ext reg layout
[    2.254434] mmc0: new ultra high speed SDR104 SDXC card at address 0001
[    2.281281] mmcblk0: mmc0:0001 GG8Y7 955 GiB
[    2.282177]  mmcblk0: p1
[    2.880894] Modules linked in: mmc_block hid_sensor_hub usbhid
hid_multitouch i915(+) nvme nvme_core t10_pi drm_buddy i2c_algo_bit
crc64_rocksoft crc64 drm_display_helper crc_t10dif spi_pxa2xx_platform
cec crct10dif_generic dw_dmac hid_generic rc_core dw_dmac_core xhci_pci
xhci_hcd ttm crct10dif_pclmul rtsx_pci_sdmmc crct10dif_common
drm_kms_helper mmc_core intel_lpss_pci usbcore i2c_hid_acpi crc32_pclmul
i2c_i801 thunderbolt drm intel_lpss i2c_hid video rtsx_pci crc32c_intel
i2c_smbus idma64 vmd hid usb_common battery wmi button
[   10.276708] mmc0: cannot verify signal voltage switch


Running 'dpkg -l | grep linux-image' shows

ii  linux-image-6.1.0-32-amd64 6.1.129-1                           
amd64        Linux 6.1 for 64-bit PCs (signed)
ii  linux-image-6.1.0-33-amd64 6.1.133-1                           
amd64        Linux 6.1 for 64-bit PCs (signed)
ii  linux-image-amd64 6.1.133-1                            amd64       
Linux for 64-bit PCs (meta-package)


This issue is apparently not new:
https://forums.linuxmint.com/viewtopic.php?t=343567. Here, word on the
street is that the issue was apparently fixed in some fabled upstream
update in the kernel, but it still appears to be a persistent issue on
my hardware on kernel 6.1.0-33-amd64.


I can confirm the SD Card is working on Windows 11 so I don't believe
this is a bad device.


I'd appreciate any advice handling this or assistance in filing the
appropriate report with the appropriate team.

Thanks and best,

-Brandan Ballantyne
Marco Moock
14 days ago
Reply
Permalink
Post by Brandan Ballantyne
I'd appreciate any advice handling this or assistance in filing the
appropriate report with the appropriate team.
Try a current kernel first.
Enable backports in sources.list, then run

sudo apt install -t bookworm-backports linux-image-amd64
--
kind regards
Marco

Send spam to ***@stinkedores.dorfdsl.de
Timothy M Butterworth
14 days ago
Reply
Permalink
Post by Marco Moock
Post by Brandan Ballantyne
I'd appreciate any advice handling this or assistance in filing the
appropriate report with the appropriate team.
Try a current kernel first.
Enable backports in sources.list, then run
sudo apt install -t bookworm-backports linux-image-amd64
Installing a unsupported backports kernel will not actually fix the
problem. It is better to file a bug against the stable kernel and let the
developers determine if they need to backport a fix.
Post by Marco Moock
--
kind regards
Marco
--
⢀⣎⠟⠻⢶⣊⠀
⣟⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
Max Nikulin
13 days ago
Reply
Permalink
Post by Marco Moock
sudo apt install -t bookworm-backports linux-image-amd64
Installing a unsupported backports kernel will not actually fix the
problem. It is better to file a bug against the stable kernel and let
the developers determine if they need to backport a fix.
Installing backports kernel or trying weekly testing live .iso image may
give an important data point whether there is a driver version that
works for the specific card reader (and the specific memory card).
Anssi Saari
14 days ago
Reply
Permalink
Post by Brandan Ballantyne
Hey Team!
This is a list for Debian users.
Post by Brandan Ballantyne
I'm new to Debian and running the latest Debian 12.10 with
updates. I'm having an issue with my MicroSD card reader and I'm not
sure how to proceed.
Looks like you didn't actually specify what the problem is? Your linked
web forum message had an actual error message in the log which you don't
seem to have.
Loading...