Internal mmc disk in Minix Neo Z83-4 with custom kernel
by shpenat from LinuxQuestions.org on (#6CFD9)
Hi
I have Minix Neo Z83-4 fanless box. I managed to install Fedora 38 on it, which works quite fine. Now, I am trying to build a custom system on it based on Linux from scratch (LFS) book. I have build several custom linux boxes in the past, so I know a little bit about building software and kernel configuration. However, this time I got stuck and I need an ideas about what did I misss.
The issue is with my custom build kernel, which should be tuned directly to the hardware and not utilize the initramfs. However with mu costom kernel I get:
Code:VFS: Cannot open root device "PARTUUID=..." or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:The list of recognized partitions is empty. So I know I have misconfigured my kernel and it does not recognize the disk.
Since the Fedora 38 is able to recognize the disk, the issue is not in missing support in linux, but rather custom kernel misconfiguration. From the Fedra 38 I have gathered the following info:
Quote:
Quote:
Quote:
Code:#lsmod
sdhci_acpi 32768 0
sdhci 94208 1 sdhci_acpi
mmc_block 61440 5
mmc_core 258048 5 sdhci,mmc_block,btsdio,brcmfmac,sdhci_acpiFrom the data I gathered I know I need to allow
Code:CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_ACPI=y
CONFIG_MMC=y
CONFIG_MMC_BLOCK=y
CONFIG_MMC_COREAparently that is not enough and the MMC card is still not recognized. Any suggestions about what to allow in kernel configuration is welcome.
Thanks for any reply.
I have Minix Neo Z83-4 fanless box. I managed to install Fedora 38 on it, which works quite fine. Now, I am trying to build a custom system on it based on Linux from scratch (LFS) book. I have build several custom linux boxes in the past, so I know a little bit about building software and kernel configuration. However, this time I got stuck and I need an ideas about what did I misss.
The issue is with my custom build kernel, which should be tuned directly to the hardware and not utilize the initramfs. However with mu costom kernel I get:
Code:VFS: Cannot open root device "PARTUUID=..." or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:The list of recognized partitions is empty. So I know I have misconfigured my kernel and it does not recognize the disk.
Since the Fedora 38 is able to recognize the disk, the issue is not in missing support in linux, but rather custom kernel misconfiguration. From the Fedra 38 I have gathered the following info:
Quote:
| # hwls *-mmc0 description: MMC Host physical id: 1 logical name: mmc0 *-mmc1 description: MMC Host physical id: 2 logical name: mmc1 *-device description: SD/MMC Device product: BJNB4R vendor: Unknown (21) physical id: 1 bus info: mmc@1:0001 date: 03/2017 serial: 3639276639 capabilities: mmc |
| # lspci 00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36) 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 36) 00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36) 00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36) 00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 36) 00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) |
Quote:
| #dmesg 6.286462] sdhci: Secure Digital Host Controller Interface driver [ 6.286473] sdhci: Copyright(c) Pierre Ossman [ 6.313787] mmc0: SDHCI controller on ACPI [80860F14:02] using ADMA [ 6.316176] mmc2: SDHCI controller on ACPI [80860F14:01] using ADMA [ 6.319759] mmc1: SDHCI controller on ACPI [80860F14:00] using ADMA [ 6.377314] r8169 0000:01:00.0: enabling device (0000 -> 0003) [ 6.401365] r8169 0000:01:00.0 eth0: RTL8168g/8111g, a0:1e:0b:09:df:81, XID 4c0, IRQ 162 [ 6.401384] r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] [ 6.413260] mmc1: new HS200 MMC card at address 0001 [ 6.493101] mmc2: new ultra high speed SDR104 SDIO card at address 0001 [ 6.522752] mmcblk1: mmc1:0001 BJNB4R 29.1 GiB [ 6.532460] r8169 0000:01:00.0 enp1s0: renamed from eth0 [ 6.539603] mmcblk1: p1 p2 p3 p4 [ 6.540630] mmcblk1boot0: mmc1:0001 BJNB4R 4.00 MiB [ 6.542121] mmcblk1boot1: mmc1:0001 BJNB4R 4.00 MiB [ 6.543551] mmcblk1rpmb: mmc1:0001 BJNB4R 4.00 MiB, chardev (237:0) |
sdhci_acpi 32768 0
sdhci 94208 1 sdhci_acpi
mmc_block 61440 5
mmc_core 258048 5 sdhci,mmc_block,btsdio,brcmfmac,sdhci_acpiFrom the data I gathered I know I need to allow
Code:CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_ACPI=y
CONFIG_MMC=y
CONFIG_MMC_BLOCK=y
CONFIG_MMC_COREAparently that is not enough and the MMC card is still not recognized. Any suggestions about what to allow in kernel configuration is welcome.
Thanks for any reply.