[Bug 2053052] [NEW] Device type not shown for eMMC

Heinrich Schuchardt 2053052 at bugs.launchpad.net
Tue Feb 13 17:25:30 UTC 2024


Public bug reported:

When installing via Subiquity to eMMC the drive is only shown as "local
disk".

It would be helpful for the user to understand what type of device it
is, e.g. by adding the device name: "local disk mmcblk0".

block/probe-data.json has this information:

{
    "blockdev": {
        "/dev/mmcblk0": {
            "CURRENT_TAGS": ":systemd:",
            "DEVLINKS": "/dev/disk/by-path/platform-16010000.mmc /dev/disk/by-id/mmc-SOD16G_0xe5ce1136 /dev/disk/by-diskseq/10",
            "DEVNAME": "/dev/mmcblk0",
            "DEVPATH": "/devices/platform/soc/16010000.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0",
            "DEVTYPE": "disk",
            "DISKSEQ": "10",
            "ID_DRIVE_FLASH_MMC": "1",
            "ID_DRIVE_MEDIA_FLASH_MMC": "1",
            "ID_NAME": "SOD16G",
            "ID_PATH": "platform-16010000.mmc",
            "ID_PATH_TAG": "platform-16010000_mmc",
            "ID_SERIAL": "0xe5ce1136",
            "MAJOR": "179",
            "MINOR": "8",
            "MMC_TYPE": "MMC",
            "SUBSYSTEM": "block",
            "TAGS": ":systemd:",
            "USEC_INITIALIZED": "10087412",


So how about "MMC 0 device SOD16G"?

Best regards

Heinrich

** Affects: subiquity (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2053052

Title:
  Device type not shown for eMMC

Status in subiquity package in Ubuntu:
  New

Bug description:
  When installing via Subiquity to eMMC the drive is only shown as
  "local disk".

  It would be helpful for the user to understand what type of device it
  is, e.g. by adding the device name: "local disk mmcblk0".

  block/probe-data.json has this information:

  {
      "blockdev": {
          "/dev/mmcblk0": {
              "CURRENT_TAGS": ":systemd:",
              "DEVLINKS": "/dev/disk/by-path/platform-16010000.mmc /dev/disk/by-id/mmc-SOD16G_0xe5ce1136 /dev/disk/by-diskseq/10",
              "DEVNAME": "/dev/mmcblk0",
              "DEVPATH": "/devices/platform/soc/16010000.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0",
              "DEVTYPE": "disk",
              "DISKSEQ": "10",
              "ID_DRIVE_FLASH_MMC": "1",
              "ID_DRIVE_MEDIA_FLASH_MMC": "1",
              "ID_NAME": "SOD16G",
              "ID_PATH": "platform-16010000.mmc",
              "ID_PATH_TAG": "platform-16010000_mmc",
              "ID_SERIAL": "0xe5ce1136",
              "MAJOR": "179",
              "MINOR": "8",
              "MMC_TYPE": "MMC",
              "SUBSYSTEM": "block",
              "TAGS": ":systemd:",
              "USEC_INITIALIZED": "10087412",

  
  So how about "MMC 0 device SOD16G"?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2053052/+subscriptions




More information about the foundations-bugs mailing list