You are not logged in.
Solution
Clean up the dust inside the card slot.
Problem Description
Realtek Card Reader could be detected by linux (Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)) and load the kernel rtsx_pci but cannot detect sdcard.
Context
I have used SDcard as an installation medium for installing Arch. After installation, I am using Arch with my SDcard inserted. But today, as I was going to change it to a SDcard with larger memory, I just found that my new SDcard cannot be detected. As I tested my previous old SDcard, it cannot be detected anymore as well.
At first, I thought it was an driver problem. Then I tested the sdcard on my Windows 11 with DELL official drivers. but it also cannot work on Windows 11. And I also found that my bootable SDcard also cannot be detected by UEFI anymore, and I have guaranteed that my "boot from sdcard" and "enable sdcard" in UEFI options are enabled.
Log
There is nothing shown in `dmesg` as I insert/umount the sdcard.
There is nothing about my sdcard shown in `lsblk`.
# lspci -k
...
72:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)
Subsystem: Dell Device 0afc
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci$ neofetch
-` zayn7lie@zayn7lie-acl
.o+` ---------------------
`ooo/ OS: Arch Linux x86_64
`+oooo: Host: XPS 13 9310
`+oooooo: Kernel: 6.11.9-arch1-1
-+oooooo+: Uptime: 13 mins
`/:-:++oooo+: Packages: 753 (pacman)
`/++++/+++++++: Shell: bash 5.2.37
`/++++++++++++++: Resolution: 1920x1200
`/+++ooooooooooooo/` DE: Hyprland
./ooosssso++osssssso+` Theme: Adwaita-dark [GTK3]
.oossssso-````/ossssss+` Icons: Adwaita [GTK3]
-osssssso. :ssssssso. Terminal: kitty
:osssssss/ osssso+++. CPU: 11th Gen Intel i7-1195G7 (8) @ 5.000GHz
/ossssssss/ +ssssooo/- GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics]
`/ossssso+/:- -:/+osssso+- Memory: 1882MiB / 15705MiB
`+sso+:-` `.-/+oso:
`++:. `-/+/
.` `/ Last edited by zayn7lie (2024-11-24 03:06:41)
Offline
Then I tested the sdcard on my Windows 11 with DELL official drivers. but it also cannot work on Windows 11. And I also found that my bootable SDcard also cannot be detected by UEFI anymore
This is all on the same machine?
And you cannot read any SD card in that reader on any OS (maybe also test some life distro) or the UEFI?
Ie. is there any reason to assume that the reader hardware still functions?
Do the cards look ok? Or are there deep scratches on the contacts (the golden strips)?
Do you have windows fast-start (still, windows sometime reactivates it with updateds) disabled?
Have you tried to reset the UEFI?
For clarification
I have used SDcard as an installation medium for installing Arch.
does that mean you installed arch onto an SD card and ran it from there??
Offline
1. This is all on the same machine?
2. And you cannot read any SD card in that reader on any OS (maybe also test some life distro) or the UEFI?
3. Ie. is there any reason to assume that the reader hardware still functions?
4. Do the cards look ok? Or are there deep scratches on the contacts (the golden strips)?
5. Do you have windows fast-start (still, windows sometime reactivates it with updateds) disabled?
6. Have you tried to reset the UEFI?
7. does that mean you installed arch onto an SD card and ran it from there??
1. Yes.
2. Yes.
3. I am not sure since the kernel and hardware are still properly shown in UEFI, Arch, and Windows 11
4. Yes, I have tried my newly bought card and my previous card. And the problem occurs just after I pick out my previous card.
5. No, they are both started in GRUB.
6. No. But I have updated my UEFI to the newest version through DELL official.
7. No. I just use SD as an installation medium to install arch (I burn iso file into a partition in my old SD, and for the rest partition I use them as storage memory).
Just a note. For how I know UEFI cannot see my sdcard, my machine (Dell xps13 9310) allows me to boot from a sdcard from UEFI, and I prevously use it for installing Arch. But now the sdcard boot option in UEFI is missing after the last umount. But the UEFI self-test did not show any error with the hardware.
Last edited by zayn7lie (2024-11-22 14:55:45)
Offline
1. This is all on the same machine?
5. No, they are both started in GRUB.
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
If that alone doesn't help, reset the UEFI.
Just that the device nvrm registers doesn't mean that the drive can properly operate, eg. if you took a screwdriver and scratched the slot a lot, the device would still properly register, but it couldn't contact any cards you insert.
Offline
1. This is all on the same machine?
5. No, they are both started in GRUB.3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.If that alone doesn't help, reset the UEFI.
Just that the device nvrm registers doesn't mean that the drive can properly operate, eg. if you took a screwdriver and scratched the slot a lot, the device would still properly register, but it couldn't contact any cards you insert.
I have tried the both ways, `> powercfg /H off` then reboot windows then linux twice, and reset UEFI, but SDcards are still cannot be detected.
Is there anyway to find out whether it is a hardware problem or a driver problem?
And just for notification, before I took out my old SDcard, everything ran flawlessly. The problem occurs only just after I took out my old SDcard from the reader.
Last edited by zayn7lie (2024-11-23 02:42:03)
Offline
It's not a "driver" problem if multiple operating systems and the UEFI are affected (drivers being OS specific hardware interfaces) - it would rather be the hardware or some firmware (incl. the UEFI)
I assume that both SD cards work fine in a different reader?
Did you try the reader from a life distro like https://grml.org/ ?
Does the windows driver indicate any kind of problems with the device?
Does "dmesg -W" generate *any* response when slotting a card?
Does it help to add "rtsx_pci.msi_en=N" to the https://wiki.archlinux.org/title/Kernel_parameters ?
The fact that this broke with physical interaction and that the SD card had apparently been in that location for a very long timer permananetly makes me worry that this is some physical problem.
(Though I will say that you'd probably see residuals of any kind of corrosion on the contacts of the old card)
Do the cards completely slide in and sit firmly in the slot?
The other big thing is that the fast-boot situation might have left the reader in an undefined state it cannot recover from.
Do you have system journals from when it still worked?
sudo journalctl -b -8 | curl -F 'file=@-' 0x0.st for 8 boots ago?
And then please also post a journal from a current (broken) boot.
Offline
I find out the reason, after disassembling my laptop to check the hardware, I found there is dust inside my reader slot...
After cleaning up the dust, the problem was solved.
It's not a "driver" problem if multiple operating systems and the UEFI are affected (drivers being OS specific hardware interfaces) - it would rather be the hardware or some firmware (incl. the UEFI)
I assume that both SD cards work fine in a different reader? - Yes. I just have bought a independent card reader and it works.
Did you try the reader from a life distro like https://grml.org/? - No. I think the main problem might be the hardware or some firmware problem as you said.
Does the windows driver indicate any kind of problems with the device? - No. No error is shown in the testing from UEFI and windows.
Does "dmesg -W" generate *any* response when slotting a card? - No.
Does it help to add "rtsx_pci.msi_en=N" to the https://wiki.archlinux.org/title/Kernel_parameters? - No.
Last edited by zayn7lie (2024-11-24 03:08:58)
Offline