Sd Card Slot not working

Hey guys, so I'll be straight up and admit that I don't think this issue is related to Garuda although it does happen on Gauda. The reason for this is that it behaves the same on Windows too. Essentially, I have an Asus Vivobook s510ua. It has a port for an sd card which I put a micro sd card into. Micro sd card goes into the sd card adapter which goes into the slot in the laptop. However, when slotting it in, even with different sd cards and different sd card adapters, it isn't detected at all on my laptop. So I was hoping someone might have an idea if the port is dead or a way to troubleshoot this possibly? Thanks

System:
  Kernel: 5.18.0-3-bore arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-bore
    root=UUID=95b636ca-42a5-47b4-9b7a-038581af6cdf rw [email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=41193397-191d-45b5-8c2b-405cf71e73b2 loglevel=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
    wm: kwin_wayland vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: X510UA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X510UA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X510UA.312 date: 04/29/2020
Battery:
  ID-1: BAT0 charge: 21.1 Wh (71.0%) condition: 29.7/42.1 Wh (70.6%)
    volts: 11.5 min: 11.5 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: discharging cycles: 481
CPU:
  Info: model: Intel Core i7-7500U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check family: 6 model-id: 0x8E (142)
    stepping: 9 microcode: 0xF0
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 509 high: 514 min/max: 400/3500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 503 2: 507 3: 514 4: 513
    bogomips: 23220
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5916
    class-ID: 0300
  Device-2: IMC Networks VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:2 chip-ID: 13d3:5a07 class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa gpu: i915 display-ID: 0
  Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.1.0
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
    chip-ID: 8086:9d71 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.0-3-bore running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-8:3 chip-ID: 8087:0a2b class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 931.52 GiB used: 184.28 GiB (19.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO M.2 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 448.4 GiB size: 448.4 GiB (100.00%)
    used: 86.09 GiB (19.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 32.1 MiB (10.7%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 448.4 GiB size: 448.4 GiB (100.00%)
    used: 86.09 GiB (19.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 448.4 GiB size: 448.4 GiB (100.00%)
    used: 86.09 GiB (19.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 448.4 GiB size: 448.4 GiB (100.00%)
    used: 86.09 GiB (19.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.52 GiB used: 2 MiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.06 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 57.0 C pch: 37.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 2500
Info:
  Processes: 253 Uptime: 13m wakeups: 1 Memory: 15.52 GiB
  used: 3.27 GiB (21.1%) Init: systemd v: 251 tool: systemctl Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1564 lib: 374 Shell: fish
  v: 3.4.1 running-in: yakuake inxi: 3.3.16
Garuda (2.6.3-2):
  System install date:     2022-05-27
  Last full system update: 2022-05-31
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:            systemd-sysctl.service

M$ and Garuda, hardware fault, or clean the slot :wink:

Did you search in Internet?

Remember, we are not the personal search engine for Garuda users here.

2 Likes

Yeah I know I'm not that much of a noob haha. I did Google around as much as I could and looked through my bios but nothing there. I understand it's likely a hardware problem with the port due to testing multiple adapters and SD cards. Thought I'd just ask on the off chance someone knows some magical spell or something to fix it

I'm not really sure your model has the same card reader, anyway, just an idea:
https://wiki.archlinux.org/title/ASUS_A55VJ#Card_reader

2 Likes

You can use lsusb or lspci to show the device - depending on how it's connected internally. Find it in the list, then search for the device's ID.

1 Like

Nevermind I fixed it haha. I'd already tried cleaning it with no luck. However, I found some weird little bristle brush and a long piece of bendy plastic and I just shoved it in there and jiggled it around and shook the laptop and prayed and it worked :sweat_smile:

3 Likes

Sorry for wasting your guy's time. I really thought it was something in the BIOS potentially as I'd really tried cleaning vigorously already. Maybe I just got some random luck this time. This has been bothering me for literal months like I'm so pissed it was this easy to fix

No worries, it's a learning experience! Don't forget to mark your solution so the thread closes and is found by any others searching for a similar issue.

2 Likes

Yeah done thanks haha. People here know by now that I tend to work out my problem after posting an issue here. It's weird though like nothing I tried before worked and then suddenly I made a post here and it starts working. Damn technology. Anyway cheers :sweat_smile:

4 Likes

It typically is. Fastboot or its ilk can be set to skip hardware checks at boot, and so sometimes Windows will willy-nilly decide your hardware is not what it is and change that in the BIOS. It happened to me with the BT adaptor on this 2019 9th Gen desktop rig.

So you were correct in first thinking about the BIOS, in my humble opinion, but now that we know about your atrocious housekeeping, we'll bear that in mind in future.
:stuck_out_tongue_winking_eye:

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.