Description of problem: When trying to install Mageia Cauldron on my new hybrid laptop Asus T100 [1], I found that its eMMC drive is not recognize by drakxtools as a block device (not seen in diskdrake, in the installer, ...). The basic patch in attachment is inspired by getVirtIO(), and allow to see the eMMC in diskdrake. It probably could be enhanced to get more information from the device (vendor, model, ...). [1] http://www.asus.com/Notebooks_Ultrabooks/ASUS_Transformer_Book_T100/#specifications Reproducible: Steps to Reproduce:
Created attachment 4540 [details] tree /sys/bus/mmc/devices/mmc[01]* on Asus T100
Created attachment 4541 [details] basic patch
Thanks! Were you able to do an install with that? You can patch the installer at runtime (see https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks#Customisation_of_the_install_by_patching_it) Or else, does diskdrake see your disks with that patch, once booted on Mageia?
Keywords: (none) => PATCH
(In reply to Thierry Vignaud from comment #3) > Thanks! > > Were you able to do an install with that? not for now > You can patch the installer at runtime (see > https://wiki.mageia.org/en/Drakx- > installer_tips_and_tricks#Customisation_of_the_install_by_patching_it) > Or else, does diskdrake see your disks with that patch, once booted on > Mageia? In live mode with the patched detect_devices.pm, diskdrake correctly see the eMMC like any other disk.
Created attachment 4542 [details] recognize mmcblk partitions You probably need something like this
(In reply to Thierry Vignaud from comment #5) > Created attachment 4542 [details] > recognize mmcblk partitions > > You probably need something like this Should it replace my patch? or in complement? With your patch alone, diskdrake doesn't recognize mmcblk partitions. With my patch I made a live install. When I tried a net install, I found that the module sdhci-acpi (used for the intel 33BB controller) is not available in installer, so that the emmc doesn't work at install time. Could it be added?
In complement. sdhci-acpi was just added to drakx-installer-images. Now you should be able to perform an install with both patches. If it's work then we'll commit those patches.
Any luck?
With sdhci-acpi, the eMMC is now correctly detected in the installer. Sadly it says that some partitions are corrupted. I don't know why, gparted and diskdrake see them correctly. But I suspect either some hardware failures on the eMMC, or a buggy UEFI firmware or a kernel bug, ... because after the live install, the installed system has always a corrupted rpm db (I tried many installs). I give up with linux on this hardware for the time being; I don't have enough time currently to diagnose in depth, try new kernels, ... Sorry Thanks for your help.
I think I'll commit the patches anyway since disks were detected.
Can you attach your /root/drakx/report.bug.xz in order to see if there's anything interesting? Also ccing Thomas (maybe he knows if there're issues with emmc?)
Keywords: (none) => NEEDINFOCC: (none) => tmb
I'm not sure if I should create a new bug report with my issue. I'll extend this one unless you tell me otherwise. I just have installed M.4 on an Intel NUC machine (DE3815TYKHE) which has a basic eMMC device built in. The install medium was a current Mageia-4.1-dual-DVD.iso from USB. Installation went fine, eMMC was recognized. However, booting after the completed installation failed. It turned out that the boot installer did forget to include the sdhci drivers in the initrd. I edited the initrd image on a different M.4 system and added the missing driver modules from the identical kernel. Then I installed the new initrd via the rescue system. Afterwards, I could boot normally from the eMMC. BTW, thanks for your hard work!
CC: (none) => digidietze
Thanks for debugging this! I think it would better if you should open a new bug report against the dracut package and make it depends on this one.
Resolution: (none) => FIXEDStatus: NEW => RESOLVEDCC: (none) => mageia
Blocks: (none) => 13814
Done. Thanks!