STATUS: FAILED BUILD: 2.1: 296dfbc9b3a3c0ed64b8e748c2868928b9c2aa8b ENVIRONMENT: genericx86 - on MMAX32bit STEPS TO REPRODUCE: 1. Plugin usb which contains live image burned 2. Configure device BIOS to firstly boot from USB if necessary 3. Boot the device and select option "Install" from boot menu 4. Proceed through default install process 5. Remove USB, and reboot into new installed system. EXPECTED OUTCOME: 1. User can choose install system from usb stick onto harddisk from boot menu or command line option 2. Installed system can boot up ACTUAL OUTCOME: The following message is displayed when installing: "usb 1-2: reset high-speed USB device number 3 using xhci_hcd" After a while, the next message is displayed: Like the installation was complete and remove the media and press ENTER, Then I boot the burned image, and I got a Kernel panic - not syncing: Invalid configuration from end user prevents continuing. Link to AB: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1/machines/genericx86/core-image-sato-sdk-genericx86.hddimg NOTE: If you download the image and burn directly in a USB it will be burned and booted succesfully, issue comes once you try to install from that burned memory to another one.
Additional Information: Rep 100%. ioremap error for 0x78da4000-0x78da5000, requested 0x2, got 0x0 dmi: Firware registration Failed. VFS: Unable to mount fs on unknown-block(0,0) User configuration error - no valid root filesystem found Kernel panic - not syncing: Invalid configuration from end user prevents continuing CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.3-yocto-standard #1
Correspond to this test execution: https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5683 Test Case: 196.
I have no minnow H/W, sending to Saul.
What kind of media are you installing onto and how is that media attached to the minnowboard?
(In reply to comment #4) > What kind of media are you installing onto and how is that media attached to > the minnowboard? Hi Saul, The origin media is a SanDisk USB - 8GB - sdcz45-008g. The destiny media is also a USB: I tried with two ADATA UV128/16GB - USB 3.0 The other one is Kingston 16GB. I know the best option is to have an external HDD to perform this, however this is what I have until now to do this. The weird situation here is that this method worked in past executions.
Retested on poky : 6c1c01392d91f512e2949ad1d57a75a8077478ba 2.1_M4.rc2. Failed
Reopened as failed in latest execution 2.1_M4.rc2
I don't have a working MinnowMax right now. If Francisco or any one can upload full dmesg, we can have a deeper look. I suspect it cannot find rootfs successfully.
Created attachment 3151 [details] Install log
Created attachment 3152 [details] Boot after install log
It looks like we need the "rootwait" kernel command line option to boot from USB. I can't see any offending changes in init-install-efi.sh so I'm thinking there was either an APPEND change somewhere or a kernel change.
Cannot reproduce on intel-core2-32, below the image used: http://yocto-ab-master.ostc.intel.com/pub/releases/yocto-meta-intel-5.0-krogoth-2.1.rc3/machines/intel-core2-32/core-image-sato-intel-core2-32.hddimg
I fixed this in meta-intel by adding "rootwait" to APPEND, but I'm keeping this open because it still needs to be fixed properly in oe-core via updating the install-efi.sh script. Right now the script only adds rootwait for SD cards, but it needs to add it for USB media as well.
This bug will need backport for YP 2.1.1
Created attachment 3249 [details] boot fail
This was found on 2.2 M1, commit poky : 6f0c5537e02c59e1c8f3b08f598dc049ff8ee098 STATUS: FAILED genericx86 - on MMAX32bit EXPECTED:Installed system can boot up installing from USB live image to external USB-sata drive the image: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2_M1.rc2/genericx86/core-image-sato-sdk-genericx86.hddimg RESULT: Installation process is correct until reboot, panic message is displayed, see attached file. An external sata drive via USB is used for installation. Boot is correct when rootwait is added to kernel edit options. note:installation and booting procces is already working in 2.2 for NUC.
The problem is not present on Meta intel 2.2 M2 commit poky : a3cad8f0e0db9b2ad62ce0f2f1b0234cb9192f56 STATUS: PASS Meta-intel 2.2 M2 - on MMAX32bit AND NUC64 EXPECTED:Installed system can boot up installing from USB live image to external USB-sata drive in minnow Max32 and internal memory in NUC. RESULT: Installation process is correct.
I have a proper fix coming to oe-core for this, rather than just a hack in meta-intel.
Fixed as of df6694b7c852c9ac627135d4158b306d90b7273f/ See: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=df6694b7c852c9ac627135d4158b306d90b7273f