ZimaOS v1.7.0 (kernel 6.18.9) cannot see the 512GB UFS disk on a Beelink ME
Pro 304 (Intel Core 3-304, Wildcat Lake), which is the device's intended OS disk.
Root cause: the kernel is built with # CONFIG_SCSI_UFSHCD is not set. The PCI
device is present — 00:17.0 Universal Flash Storage controller [8086:4d47] —
but no driver binds to it, so no block device appears (lsblk shows only the SATA
disks). No dm-verity involved; rootfs is plain squashfs.
Note: this exact device ID (0x4D47) is ALREADY in the upstream ufshcd-pci table
(drivers/ufs/host/ufshcd-pci.c), so no new code is needed — only enabling the
config in the x86_64 kernel build:
CONFIG_SCSI_UFS=y
CONFIG_SCSI_UFSHCD=y (or =m)
CONFIG_SCSI_UFSHCD_PCI=y (or =m)
Impact: the Beelink ME series (very popular OS-agnostic NAS) uses UFS as its OS
disk; without this, ZimaOS can't be installed there natively. Enabling these
flags would make the whole ME line first-class ZimaOS targets.
ZimaOS v1.7.0 (kernel 6.18.9) cannot see the 512GB UFS disk on a Beelink ME
Pro 304 (Intel Core 3-304, Wildcat Lake), which is the device's intended OS disk.
Root cause: the kernel is built with
# CONFIG_SCSI_UFSHCD is not set. The PCIdevice is present —
00:17.0 Universal Flash Storage controller [8086:4d47]—but no driver binds to it, so no block device appears (lsblk shows only the SATA
disks). No dm-verity involved; rootfs is plain squashfs.
Note: this exact device ID (0x4D47) is ALREADY in the upstream ufshcd-pci table
(drivers/ufs/host/ufshcd-pci.c), so no new code is needed — only enabling the
config in the x86_64 kernel build:
CONFIG_SCSI_UFS=y
CONFIG_SCSI_UFSHCD=y (or =m)
CONFIG_SCSI_UFSHCD_PCI=y (or =m)
Impact: the Beelink ME series (very popular OS-agnostic NAS) uses UFS as its OS
disk; without this, ZimaOS can't be installed there natively. Enabling these
flags would make the whole ME line first-class ZimaOS targets.