SD card not detected on 4.8.4 (Slate AX / GL-AXT1800) - same issue as 4.8.2/4.8.3 thread

Hi,

I'm experiencing the same micro SD card detection issue reported in the 4.8.2/4.8.3 threads, but on firmware 4.8.4.

Symptoms:

  • No /dev/mmcblk0 device appears in /proc/partitions after inserting the card
  • No kernel messages logged on hot insertion (dmesg stays empty)
  • Tested with two different SD cards (different brands/capacities): same result with both, ruling out a card-specific issue
  • Card-detect GPIO works correctly (Got CD GPIO appears in dmesg after driver rebind)
  • SDHCI controller initializes fine (mmc0: SDHCI controller on 7804000.sdhci_sd using ADMA 64-bit)
  • Manual driver rebind produces: mmc0: error -110 whilst initialising SD card

What I checked:

root@GL-AXT1800:~# dmesg
[  632.067569] sdhci_msm 7804000.sdhci_sd: Got CD GPIO
[  632.067642] sdhci_msm 7804000.sdhci_sd: allocated mmc-pwrseq
[  632.071297] sdhci_msm 7804000.sdhci_sd: sdhci_msm_get_ice_device_vops: ICE device is not enabled
[  632.221872] mmc0: SDHCI controller on 7804000.sdhci_sd [7804000.sdhci_sd] using ADMA 64-bit
[  632.243032] mmc0: error -110 whilst initialising SD card
  • Card-detect GPIO and controller probe both work (/sys/class/mmc_host/mmc0/ present, readlink -f shows 7804000.sdhci_sd, driver sdhci_msm)
  • Manual unbind/bind of the driver reproduces the same -110 timeout every time
  • USB storage works perfectly fine on the same unit — this appears isolated to the SD card path

Confirmed workaround: Downgrading to 4.6.11 would likely resolve this based on other reports in the 4.8.2/4.8.3 thread, but I wanted to flag that this regression is still present in 4.8.4, so it hasn't been fixed yet in the stable branch.

SD cards tested:

  • Amazon Basics SD 512Gb
  • 4Gb SD Card (cannot remember the brand right now)

Happy to provide GoodCloud remote access if that helps investigate further, as offered in the other thread.

Thanks!

Hi,

Thank you for your report.

Yes, if possible, please follow the guide below and share your device with us via GoodCloud so that we can check it remotely:

Kindly send us the MAC address and the router password via private message so that we can access the device.

We will then ask our R&D team to investigate the issue remotely and see whether a fix can be implemented.