Lenovo 100S-14IBR MicroSD 不显示

Lenovo 100S-14IBR MicroSD 不显示

编辑 08-07-17 我会尝试重新表述这个问题。设备如何出现在“实时会话”中并在正常启动期间完全消失?

有点沮丧。16.04LTS 安装基本无缝,唯一不能用的就是 MicroSD 读卡器。

读取器出现在 lspci 中(00:12.0 SD 主机控制器:Intel Corporation Device 2296(rev 35))

00:00.0 Host bridge: Intel Corporation Device 2280 (rev 35)
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 35)
00:0b.0 Signal processing controller: Intel Corporation Device 22dc (rev 35)
00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 35)
00:13.0 SATA controller: Intel Corporation Device 22a3 (rev 35)
00:14.0 USB controller: Intel Corporation Device 22b5 (rev 35)
00:1a.0 Encryption controller: Intel Corporation Device 2298 (rev 35)
00:1b.0 Audio device: Intel Corporation Device 2284 (rev 35)
00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 35)
00:1c.2 PCI bridge: Intel Corporation Device 22cc (rev 35)
00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 35)
00:1f.3 SMBus: Intel Corporation Device 2292 (rev 35)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)

如果通过 USB 读卡器连接,则会显示三种不同格式的卡,即 exFat、NTFS 和 ext3/ext4。

内部读卡器中的卡在 Windows 10(exFat)中可以工作。

现在令人沮丧的是,内部读卡器中的卡显示使用 Ubuntu 实时 USB(mmcblk2)!

    ubuntu@ubuntu:~$ lsblk
NAME                MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb         179:24   0     4M  0 disk 
mmcblk0boot0        179:8    0     4M  1 disk 
loop0                 7:0    0   1.4G  1 loop /rofs
sda                   8:0    1   7.5G  0 disk 
└─sda1                8:1    1   7.5G  0 part /cdrom
mmcblk2             179:32   0 118.4G  0 disk 
└─mmcblk2p1         179:33   0 118.4G  0 part /media/ubuntu/Storage
mmcblk0boot1        179:16   0     4M  1 disk 
mmcblk0             179:0    0  29.1G  0 disk 
├─mmcblk0p2         179:2    0   488M  0 part /media/ubuntu/c4d4b98b-eb5d-4ac5-b
├─mmcblk0p3         179:3    0  28.1G  0 part 
│ ├─ubuntu--vg-swap_1
│ │                 253:1    0   1.9G  0 lvm  
│ └─ubuntu--vg-root 253:0    0  26.3G  0 lvm  
└─mmcblk0p1         179:1    0   512M  0 part

但是在正常启动的情况下,插入卡不会产生任何反应,没有 dmesg,没有 mount,没有 lsblk,没有 nuttin。

另一个有趣的项目是,在“磁盘”中,机器内置的 32GIG eMMC 显示为 SD 卡。Ubuntu 可能无法同时处理两个 SD 控制器吗?

感谢您的知识、经验和帮助。

编辑 07-28-17 lspci -nnk | grep -A3 'SD 主机控制器' 的输出

00:12.0 SD Host controller [0805]: Intel Corporation Device [8086:2296] (rev 35)
            Subsystem: Lenovo Device [17aa:3905]
        Kernel modules: sdhci_pci
00:13.0 SATA controller [0106]: Intel Corporation Device [8086:22a3] (rev 35)

sudo dmesg | tail -n 100 的输出(在多次配对鼠标、移除 microSD、等待、安装 microSD、等待失败后)

[    4.778998] SSE version of gcm_enc/dec engaged.
[    4.788256] sdhci-pci 0000:00:12.0: SDHCI controller found [8086:2296] (rev 35)
[    4.790639] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (5986:0670)
[    4.795643] uvcvideo 1-5:1.0: Entity type for entity Realtek Extended Controls Unit was not initialized!
[    4.795648] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
[    4.795650] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
[    4.795653] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!
[    4.795781] input: Lenovo EasyCamera as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8
[    4.803139] sdhci-pci 0000:00:12.0: SDHCI controller found [8086:2296] (rev 35)
[    4.803672] usbcore: registered new interface driver uvcvideo
[    4.803673] USB Video Class driver (1.1.1)
[    4.809029] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[    4.811105] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    4.811380] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    4.905521] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[    5.013428] kvm: disabled by bios
[    5.043525] kvm: disabled by bios
[    5.053791] sdhci-pci 0000:00:12.0: SDHCI controller found [8086:2296] (rev 35)
[    5.061115] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    5.076271] intel_rapl: Found RAPL domain package
[    5.076274] intel_rapl: Found RAPL domain core
[    5.143921] Adding 1939452k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 across:1939452k SSFS
[    5.419978] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[    5.657025] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    5.727622] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VC: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    5.727626] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    5.727628] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[    5.727630] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    5.727631] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    5.727634] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
[    5.727636] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
[    5.757341] sdhci-pci 0000:00:12.0: SDHCI controller found [8086:2296] (rev 35)
[    5.771677] sdhci-pci 0000:00:12.0: SDHCI controller found [8086:2296] (rev 35)
[    5.776412] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[    5.776574] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[    5.776688] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[    6.345200] audit: type=1400 audit(1501191741.892:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=743 comm="apparmor_parser"
[    6.345205] audit: type=1400 audit(1501191741.892:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=743 comm="apparmor_parser"
[    6.345206] audit: type=1400 audit(1501191741.892:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=743 comm="apparmor_parser"
[    6.345208] audit: type=1400 audit(1501191741.892:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=743 comm="apparmor_parser"
[    6.350204] audit: type=1400 audit(1501191741.900:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=742 comm="apparmor_parser"
[    6.350208] audit: type=1400 audit(1501191741.900:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=742 comm="apparmor_parser"
[    6.364939] audit: type=1400 audit(1501191741.912:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="webbrowser-app" pid=746 comm="apparmor_parser"
[    6.364944] audit: type=1400 audit(1501191741.912:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="webbrowser-app//oxide_helper" pid=746 comm="apparmor_parser"
[    6.374553] audit: type=1400 audit(1501191741.924:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=747 comm="apparmor_parser"
[    6.532130] random: crng init done
[    6.597005] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.597008] Bluetooth: BNEP filters: protocol multicast
[    6.597014] Bluetooth: BNEP socket layer initialized
[    7.252743] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    7.254898] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    7.255160] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    7.460021] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    7.460283] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    7.475244] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    7.596501] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   11.200899] wlp2s0: authenticate with 94:62:69:72:0b:30
[   11.219809] wlp2s0: send auth to 94:62:69:72:0b:30 (try 1/3)
[   11.221810] wlp2s0: authenticated
[   11.225750] wlp2s0: associate with 94:62:69:72:0b:30 (try 1/3)
[   11.229095] wlp2s0: RX AssocResp from 94:62:69:72:0b:30 (capab=0x411 status=0 aid=5)
[   11.230489] wlp2s0: associated
[   11.230563] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[   12.093603] Bluetooth: RFCOMM TTY layer initialized
[   12.093613] Bluetooth: RFCOMM socket layer initialized
[   12.093625] Bluetooth: RFCOMM ver 1.11
[   13.614497] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:8988:cb48:de88:ca3b DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=879629 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[   13.614539] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:8988:cb48:de88:ca3b DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=400712 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
[   13.624827] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:8988:cb48:de88:ca3b DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=879629 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[   13.624866] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:8988:cb48:de88:ca3b DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=400712 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
[   16.160523] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
[   25.685607] [UFW BLOCK] IN=wlp2s0 OUT= MAC=f0:42:1c:22:12:35:f0:03:8c:70:f8:38:08:00 SRC=192.168.1.238 DST=192.168.1.152 LEN=90 TOS=0x00 PREC=0x00 TTL=128 ID=15532 PROTO=UDP SPT=137 DPT=59424 LEN=70 
[   37.668157] [UFW BLOCK] IN=wlp2s0 OUT= MAC=f0:42:1c:22:12:35:f0:03:8c:70:f8:38:08:00 SRC=192.168.1.238 DST=192.168.1.152 LEN=90 TOS=0x00 PREC=0x00 TTL=128 ID=15596 PROTO=UDP SPT=137 DPT=46566 LEN=70 
[  109.854895] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  362.065084] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  488.016211] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  613.968221] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  740.228629] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  992.131545] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1118.081673] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1244.031997] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1369.984811] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1496.241182] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1622.193221] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1625.691928] perf: interrupt took too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 1748.148543] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 1850.528040] perf: interrupt took too long (3183 > 3143), lowering kernel.perf_event_max_sample_rate to 62750
[ 1873.479766] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2000.047480] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2125.997322] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2251.949080] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2377.591276] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2504.159824] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2756.060381] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 2882.013894] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 3007.964148] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 3260.172188] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 3386.123487] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[ 3435.812400] perf: interrupt took too long (4008 > 3978), lowering kernel.perf_event_max_sample_rate to 49750
[ 3638.026795] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:94:62:69:72:0b:30:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 

两项操作均在“正常”启动期间执行(使用 eMMC)

以及 sudo dmesg | tail -n 10 的输出(启动到 USB 并插入 microSD 后)(仅显示它何时正常工作 - 而不是在正常启动到 eMMC 期间)

[  128.747616] wlp2s0: authenticate with 94:62:69:72:0b:30
[  128.755528] wlp2s0: send auth to 94:62:69:72:0b:30 (try 1/3)
[  128.757792] wlp2s0: authenticated
[  128.762276] wlp2s0: associate with 94:62:69:72:0b:30 (try 1/3)
[  128.765765] wlp2s0: RX AssocResp from 94:62:69:72:0b:30 (capab=0x411 status=0 aid=5)
[  128.766919] wlp2s0: associated
[  128.766986] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  298.515241] mmc2: new ultra high speed SDR104 SDXC card at address 59b4
[  298.521173] mmcblk2: mmc2:59b4       118 GiB 
[  298.538077]  mmcblk2: p1

编辑 08-08-17

检测到卡时实时会话期间 sudo lspci -v 的输出(仅显示 SD 控制器部分)

00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 35) (prog-if 01)
Subsystem: Lenovo Device 3905
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at 91315000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Kernel driver in use: sdhci-pci
Kernel modules: sdhci_pci

以及从 SATA 正常启动时 sudo lspci -v 的输出(仅显示 SD 控制器部分)

00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 35) (prog-if 01)
Subsystem: Lenovo Device 3905
Flags: fast devsel, IRQ 18
Memory at 91315000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Kernel modules: sdhci_pci

不同之处在于设置的标志。有效的实时会话启动设置了“总线主控”和“延迟 0”标志。关于如何在正常启动期间设置这些标志,您有什么想法吗?

编辑 08-09-17 也许会发生一个顿悟的时刻

在正常启动时看不到 microSD 卡

dana@Astrolaptop3:~$ sudo modinfo sdhci_pci
filename:       /lib/modules/4.10.0-30-generic/kernel/drivers/mmc/host/sdhci-pci.ko

并从实时会话启动中看到 microSD 卡

ubuntu@ubuntu:~$ sudo modinfo sdhci_pci
filename:       /lib/modules/4.8.0-36-generic/kernel/drivers/mmc/host/sdhci-pci.ko

因此,有效的驱动程序是 4.8.0-36 内核的一部分,无效的驱动程序是 4.10.0-30 内核的一部分。我该如何使用有效的旧驱动程序?我不一定想恢复整个内核,只想恢复驱动程序。

编辑 08-10-17

Ubuntu 错误 1710023,“4.10.0-30-generic...sdhci_pci 驱动程序无法检测到 microSDXC,而 4.8.0-36-generic 可与相同硬件配合使用”已添加 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1710023

如果这影响到您,请登录启动板并单击“这个错误是否影响到您?”

答案1

恢复到内核 4.8.17-040817-generic 可修复此问题。现在一切正常。

4.8 已设置“总线主控”和“延迟 0”标志,但我不知道如何以其他方式设置它们。已尝试 4.10.x 和 4.12.x - 均已损坏。

这不是一个好答案,但这是一个答案。下一个问题是 4.10.xxx 为何损坏?

编辑 08-12-17

有点意料之中——将内核恢复到 4.8 会破坏系统。我放弃了。Ubuntu 中又一个不起作用的东西。但至少我更多地练习了擦除驱动器并重新开始。

答案2

我在使用我自己的 4.14.69 内核版本的 Intel NUC5CPYH 上使用相同的 SD 主机控制器 (8086:2296) 时遇到了同样的问题。显然,在该内核中(也可能在您的 Ubuntu 4.10.x 内核中?),尽管 sdhci-pci 似乎在工作,但除非先加载相关的 pinctrl 驱动程序(在我的情况下是 pinctrl-cherryview),否则 MMC 无法初始化。

此错误报告

相关内容