Seemed OK here, without a bit more information, a "did not boot"
is almost useless. For example,
what is on emmc (and, by implication uboot)? me, mrfixit
Did you try a vt (virtual terminal,,ctl-alt-F3)?
The red light seems to signify sleep, I don't know how well it will do
--edit--
And... not so well, maybe because of oldish kernel,, 15% in 6 hours
Something is not right in uboot, 2.7 is actually OK, works
In short,, blanked 1st 16M on emmc, restored mbr (emmc)
So, a "safe" way to test uboots, with blank SPI and blank emmc,, will use SD uboot
Both q4os and armbian (debian) behaved the same, green led, blank screen
After. a bit varied viz red led, but MUCH better than ones that "locked" pbp
(no leds, other than chrg, no response to pwr button, appeared dead)
If I didn't know "extra long press" ,, I would be cursing
I did learn that a good SD had to be in or it would not work
Just to be clear, q4os uboot did NOT lock pbp
lockers:
fedoraproject:fedora:32
ubuntu 20.04 LTS (Focal Fossa)
kali 2020.3
is almost useless. For example,
what is on emmc (and, by implication uboot)? me, mrfixit
Did you try a vt (virtual terminal,,ctl-alt-F3)?
The red light seems to signify sleep, I don't know how well it will do
--edit--
And... not so well, maybe because of oldish kernel,, 15% in 6 hours
Something is not right in uboot, 2.7 is actually OK, works
In short,, blanked 1st 16M on emmc, restored mbr (emmc)
So, a "safe" way to test uboots, with blank SPI and blank emmc,, will use SD uboot
Both q4os and armbian (debian) behaved the same, green led, blank screen
After. a bit varied viz red led, but MUCH better than ones that "locked" pbp
(no leds, other than chrg, no response to pwr button, appeared dead)
If I didn't know "extra long press" ,, I would be cursing
I did learn that a good SD had to be in or it would not work
Just to be clear, q4os uboot did NOT lock pbp
lockers:
fedoraproject:fedora:32
ubuntu 20.04 LTS (Focal Fossa)
kali 2020.3
