cabled Posted December 28, 2018 Share Posted December 28, 2018 (edited) Having read through the thread, it seems I may have fallen prey to the issues with new eMMCs...? There was a recent hardware BOM change and the new part is https://www.samsung.com/semiconductor/estorage/emmc/KLM8G1GETF-B041/. This is not getting detected. Spoiler Quote Output is as follows: U-Boot 2016.09-armbian-fel-mass-storage-dirty (Sep 28 2016 - 12:21:11 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 1 GiB Using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 (FEL boot) ## Executing script at 43100000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2229486 Bytes = 2.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 1024MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2004620! ion_reserve_common: ion reserve: [0x50000000, 0x60000000]! Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... Starting g_mass_storage scripthttps://github.com/zador-blood-stained/fel-mass-storage No SD/eMMC device found done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check file system ... fsck from util-linux 2.25.2 Checking all file systems. done. Usage: mount [-r] [-w] [-o options] [-t type] [-f] [-i] [-n] device directory done. Target filesystem doesn't have requested /sbin/init. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: No such file or directory done. Could not copy file: No such file or directory No init found. Try passing init= bootarg. Rebooting automatically due to panic= boot argument Am I understanding the issue correctly? And if so, this means the kernel and uInit will have to be re-done? If its at all material, the previous part was Hynix H26M31003GMR which was being shown as an SD card... Edited December 28, 2018 by Tido added spoiler Link to comment Share on other sites More sharing options...
Igor Posted December 28, 2018 Share Posted December 28, 2018 29 minutes ago, cabled said: And if so, this means the kernel and uInit will have to be re-done? More likely u-boot needs to have support for this chip. Link to comment Share on other sites More sharing options...
cabled Posted December 28, 2018 Share Posted December 28, 2018 Ok. Pardon the confusion, limited familiarity with this area. Does this just mean that I should attempt to recompile uboot per http://linux-sunxi.org/Mainline_U-Boot#Configure_U-Boot and the issue might resolve? Link to comment Share on other sites More sharing options...
zador.blood.stained Posted December 28, 2018 Author Share Posted December 28, 2018 This does not depend on u-boot (and it doesn't have much checks for eMMC revisions anyway). Most likely this could be solved by patching the CSD check: https://github.com/zador-blood-stained/fel-mass-storage/issues/5 Link to comment Share on other sites More sharing options...
cabled Posted December 28, 2018 Share Posted December 28, 2018 yes, I read that thread from your git but am not 100% clear. This means I clone the git and cross compile the kernel, then make that adjustment and retrieve the resultant uImage? And that goes in place of zImage in the current tool package? Assuming that I understand this correctly and this allows me to get the MMC on USB to clone my old image, does it also mean that the image should be fine at that point? Link to comment Share on other sites More sharing options...
zador.blood.stained Posted December 28, 2018 Author Share Posted December 28, 2018 2 hours ago, cabled said: This means I clone the git and cross compile the kernel, then make that adjustment and retrieve the resultant uImage? As I wrote in the issue, you need zImage and matching uInitrd with a custom premount script from the repository. There are no guides on how exactly to create them. The only thing that makes it easier is that mentioned eMMC CSD revision patch is already included in the Armbian patchset, but this assumes that CSD revision 8 is the problem which is impossible to confirm without kernel logs. Link to comment Share on other sites More sharing options...
MarshallMCH Posted January 21, 2019 Share Posted January 21, 2019 Any update on this issue? I have a OPI PC Plus and cannot get the EMMC to be recognized:( Link to comment Share on other sites More sharing options...
Recommended Posts