TB2932 shows up as CARDREADER and not a storage device
Bug #1911003 reported by
Sheila Miguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Support Library |
Expired
|
Undecided
|
Unassigned |
Bug Description
We have a report from someone that the TB2932 device shows up as a cardreader and not a storage device.
It's from the submission for this hardware:
https:/
I've checked the submission json and it shows up as CARDREADER. I don't know if that's legit what the machine reports to you or if something weird is going on.
I'm attaching the submission.
To post a comment you must log in.
The following section of `udevadmin info -e` gave indeed a CARDREADER:
P: /devices/ pci0000: 00/0000: 00:1a.0 /devices/ pci0000: 00/0000: 00:1a.0 ID=103C: 8723 NAME=0000: 00:1a.0 pci:v00008086d0 00002C4sv000010 3Csd00008723bc0 8sc05i01 D=46201815 CLASS_FROM_ DATABASE= Generic system peripheral SUBCLASS_ FROM_DATABASE= SD Host controller FROM_DATABASE= Intel Corporation
L: 0
E: DEVPATH=
E: SUBSYSTEM=pci
E: DRIVER=sdhci-pci
E: PCI_CLASS=80501
E: PCI_ID=8086:02C4
E: PCI_SUBSYS_
E: PCI_SLOT_
E: MODALIAS=
E: USEC_INITIALIZE
E: ID_PCI_
E: ID_PCI_
E: ID_VENDOR_
P: /devices/ pci0000: 00/0000: 00:1a.0/ mmc_host/ mmc0 /devices/ pci0000: 00/0000: 00:1a.0/ mmc_host/ mmc0
L: 0
E: DEVPATH=
E: SUBSYSTEM=mmc_host
P: /devices/ pci0000: 00/0000: 00:1a.0/ mmc_host/ mmc0/mmc0: 0001 /devices/ pci0000: 00/0000: 00:1a.0/ mmc_host/ mmc0/mmc0: 0001
L: 0
E: DEVPATH=
E: SUBSYSTEM=mmc
E: DRIVER=mmcblk
E: MMC_TYPE=MMC
E: MMC_NAME=TB2932
E: MODALIAS=mmc:block
P: /devices/ pci0000: 00/0000: 00:1a.0/ mmc_host/ mmc0/mmc0: 0001/block/ mmcblk0 id/mmc- TB2932_ 0x25f82c28 /devices/ pci0000: 00/0000: 00:1a.0/ mmc_host/ mmc0/mmc0: 0001/block/ mmcblk0 /dev/mmcblk0 D=1956737 0x25f82c28 TABLE_UUID= 88975763 TABLE_TYPE= dos MEDIA_FLASH_ SD=1 /dev/disk/ by-id/mmc- TB2932_ 0x25f82c28
N: mmcblk0
L: 0
S: disk/by-
E: DEVPATH=
E: SUBSYSTEM=block
E: DEVNAME=
E: DEVTYPE=disk
E: MAJOR=179
E: MINOR=0
E: USEC_INITIALIZE
E: ID_NAME=TB2932
E: ID_SERIAL=
E: ID_PART_
E: ID_PART_
E: ID_DRIVE_FLASH_SD=1
E: ID_DRIVE_
E: DEVLINKS=
E: TAGS=:systemd:
The lsblk output:
KNAME="mmcblk0" TYPE="disk" MOUNTPOINT="" mmcblk0boot0" TYPE="disk" MOUNTPOINT="" mmcblk0boot1" TYPE="disk" MOUNTPOINT="" "/boot/ efi"
KNAME="mmcblk0p1" TYPE="part" MOUNTPOINT=""
KNAME="
KNAME="
KNAME="nvme0n1" TYPE="disk" MOUNTPOINT=""
KNAME="nvme0n1p1" TYPE="part" MOUNTPOINT=
KNAME="nvme0n1p2" TYPE="part" MOUNTPOINT=""
KNAME="nvme0n1p3" TYPE="part" MOUNTPOINT="/"
KNAME="nvme1n1" TYPE="disk" MOUNTPOINT=""
KNAME="nvme1n1p1" TYPE="part" MOUNTPOINT=""
Note that the main NVME is well reported as a DISK device.
I have no idea what this MMC device really is? a cache of some sort?
Model: INTEL HBRPEKNX0202AH (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 EFI boot, esp
2 538MB 5038MB 4500MB fat32 Recovery Partition msftdata
3 5038MB 512GB 507GB ext4
Model: MMC TB2932 (sd/mmc)
Disk /dev/mmcblk0: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 31.4GB 31.4GB primary
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot0: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Model: INTEL HBRPEKNX0202AHO (nvme)
Disk /dev/nvme1n1: 29.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 29.3GB 29.3GB primary
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table...