Created attachment 3969 [details] tiny_bootlog serial STATUS: IDLE BUILD: 2.4 M3: rc1-5f6945f5031e1a4ca116cc1eccf4c2f9dc228547 ENVIRONMENT: intel-corei7-64 on Minnowboard Max STEPS TO REPRODUCE: 1- Clone Poky 2- Clone meta-intel layer 3- source environment 4- bitbake-layers add-layer “../meta-intel” 5- Add below to the local.conf DISTRO="poky-tiny" MACHINE ="intel-corei7-64" 6- $bitbake core-image-tiny-initramfs 7- When image was built correctly: a.WIC image should be created under tmp/deploy/images/intel-cori7-64 b.Burn WIC image to USB an boot it to Minnow 64 8- Connect Minnowmax board via serial. EXPECTED OUTCOME: Verify Poky tiny image can be created and can boot ACTUAL OUTCOME: Poky tiny Image ask for Password, even with EXTRA_IMAGE_FEATURES ?= "debug-tweaks" in local.conf. This can be verified only via serial. Attached boot file from serial.
(In reply to comment #0) > Created attachment 3969 [details] > tiny_bootlog serial > > STATUS: IDLE > BUILD: 2.4 M3: rc1-5f6945f5031e1a4ca116cc1eccf4c2f9dc228547 > ENVIRONMENT: intel-corei7-64 on Minnowboard Max > STEPS TO REPRODUCE: > 1- Clone Poky > 2- Clone meta-intel layer > 3- source environment > 4- bitbake-layers add-layer “../meta-intel” > 5- Add below to the local.conf > DISTRO="poky-tiny" > MACHINE ="intel-corei7-64" > 6- $bitbake core-image-tiny-initramfs > 7- When image was built correctly: > a.WIC image should be created under tmp/deploy/images/intel-cori7-64 > b.Burn WIC image to USB an boot it to Minnow 64 > 8- Connect Minnowmax board via serial. > EXPECTED OUTCOME: > > Verify Poky tiny image can be created and can boot > > ACTUAL OUTCOME: > > Poky tiny Image ask for Password, even with EXTRA_IMAGE_FEATURES ?= > "debug-tweaks" in local.conf. > This can be verified only via serial. > Attached boot file from serial. Juan, I believe the bug summary is not fully correct: the image does boot but password is not blank, right? So the problem is the blanking, not the booting process.
Ok, I've said this several times: The core-image-tiny-initramfs image DOES NOT NEED A PASSWORD, it DOES NOT HAVE INIT, It simply drops to shell. If, for any reason you are getting a login prompt, then something within the image building process went wrong, my guess is that your build directory is dirty. There is no reason at all to add EXTRA_IMAGE_FEATURES ?= "debug-tweaks".
> Juan, I believe the bug summary is not fully correct: the image does boot > but password is not blank, right? So the problem is the blanking, not the > booting process. You're right Leo, thing is, that HDMI video stop the boot process, so I think it didn't boot at all, so I did connect the minnowmax via serial and realized that it ask for password, anyway I changed the summary, thanks.
Juan, Please use the following command to create the wic image manually and make sure that you are indeed testing a tiny build: $ wic create systemd-bootdisk-tiny64 -e core-image-tiny-initramfs in case you are testing for intel-core2-32 , please change systemd-bootdisk-tiny64 to systemd-bootdisk-tiny32
(In reply to comment #4) > Juan, > > Please use the following command to create the wic image manually and make > sure that you are indeed testing a tiny build: > > $ wic create systemd-bootdisk-tiny64 -e core-image-tiny-initramfs > > in case you are testing for intel-core2-32 , please change > systemd-bootdisk-tiny64 to systemd-bootdisk-tiny32 It worked, I was able to create tiny image and boot ok, Im adding this steps to test case, we can close this bug.
Verified.