Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#73231 - [efivar] Installer doesn't detect the internal eMMC drive

Attached to Project: Arch Linux
Opened by trapanator (trapanator) - Sunday, 02 January 2022, 15:16 GMT
Last edited by David Runge (dvzrv) - Tuesday, 04 January 2022, 18:57 GMT
Task Type Bug Report
Category Kernel
Status Assigned
Assigned To David Runge (dvzrv)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

I have a baytrail device (Minix Z64).
I can boot it with Archlinux installer (adding `acpi=off` on the grub menu to be able to boot it).
But when I am in the shell, I cannot see the internal eMMC drive.
I tried to load these kernel modules (with modprobe):

* mmc_block
* sdhci
* sdhci_acpi

Still I cannot see the internal eMMC. Maybe I forgot other module?

Additional info:
* Installer, december version

This task depends upon

Comment by trapanator (trapanator) - Monday, 03 January 2022, 13:53 GMT
Using Fedora 35 and Ubuntu 20.04 media installers, they can see internal eMMC drive.

I think that there's something missing...
Comment by AK (Andreaskem) - Monday, 03 January 2022, 14:50 GMT
What exactly do you mean by "see"? Where do you expect it? Is it not listed by lsblk? Is it missing in /dev?
Comment by trapanator (trapanator) - Monday, 03 January 2022, 14:51 GMT
yes, it is not listed by lsblk and neither there is /dev/mmc*
Comment by trapanator (trapanator) - Monday, 03 January 2022, 14:59 GMT
I'm attaching dmesg and lsblk outputs
Comment by Morten Linderud (Foxboron) - Monday, 03 January 2022, 15:09 GMT
Probably missing this backport from efivar. It was pointed out in #archlinux-releng a day or two ago.

https://github.com/rhboot/efivar/commit/f0d3ed17ef3b2bbdfdff4dde12ec0a82d1ccdd33
Comment by AK (Andreaskem) - Monday, 03 January 2022, 15:12 GMT
edit: (the previous comment seems to offer a likely explanation)

ACPI is used to discover and configure hardware components. I would not be surprised if setting acpi=off is the reason for your issue. Is there some other option you could try to get the system to boot?
Comment by trapanator (trapanator) - Monday, 03 January 2022, 15:13 GMT
I have to turn off the acpi because I cannot see anything on the screen.

Are there another alternatives?
Comment by trapanator (trapanator) - Monday, 03 January 2022, 15:14 GMT
Note that the system is an Intel Atom Baytrail Z3735F
Comment by AK (Andreaskem) - Monday, 03 January 2022, 15:24 GMT
To rule out acpi=off as the culprit, you might get lucky with the options described here (although the commit mentioned above seems more likely to be required)

https://wiki.ubuntu.com/DebuggingACPI#Debugging_procedure

If "acpi=off" allows the system to boot, try to isolate the ACPI issue with the following boot parameters
Try booting with "acpi=ht"
This disables all of ACPI except just enough to enable Hyper Threading. If acpi=off works and acpi=ht fails, then the issue is in the ACPI table parsing code itself, or perhaps the SMP code.
Try booting with "pci=noacpi"
This disables ACPI for IRQ routing and PCI scanning.
Try booting with "acpi=noirq"
This disables ACPI for IRQ routing.
Try booting with "pnpacpi=off"
This disables the ACPI component of the Linux Plug and Play code.
Try booting with "noapic"
Disables the IO-APIC for IRQ routing or PCI scanning.
Try booting with "nolapic"
Disables the local APIC.
Comment by trapanator (trapanator) - Monday, 03 January 2022, 15:55 GMT
Bingo! The 'nolapic' did the trick.
But lsblk doesn't show the eMMC device;
But (again) lsmod now lists "mmc_block", "sdhci" and "sdhci_acpi" (before it didn't with acpi=off!)

And now? I should wait for the patch?
Comment by David Runge (dvzrv) - Tuesday, 04 January 2022, 19:16 GMT
@trapanator: Thanks for the report.

I am currently evaluating what can be done here, as there has not been a release for efivar since 2018 and upstream does not respond (https://github.com/rhboot/efivar/issues/137). Backporting seems a bit risky as there are three years of commits and the commit in question does not apply cleanly. Another (also potentlially risky) option would be to bump to some commit in the list of recent commits.

My assumption is, that other downstream distributions use some specific commit or heavily patch the sources to make this work.
Comment by trapanator (trapanator) - Tuesday, 04 January 2022, 19:28 GMT
Should I test with an older ISO version?
Comment by BTD Master (btdmaster) - Saturday, 15 January 2022, 20:46 GMT Comment by trapanator (trapanator) - Sunday, 16 January 2022, 08:12 GMT
Great! Waiting for next version of installer. Or can I grab a testing iso, now?

Loading...