+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Pinebook Pro Hardware and Accessories (https://forum.pine64.org/forumdisplay.php?fid=116)
+--- Thread: Pinebook Pro Boot Issues - Booting needs multiple attempts (/showthread.php?tid=11581)
Pages:
1
2
RE: Pinebook Pro Boot Issues - Booting needs multiple attempts - wdt - 10-03-2020
Well, there are at least 4 (slightly) different debian images, this is aarch64 kernel and armhf userland,,
so somewhat unique,, obviously quite good for 32 bit arm apps
I actually have that on my emmc, for reasons, but that is NOT what I recommended to you
I said "rescue SD",, on 8-16G SD, not necessarily highest quality SD,,, do update it (mrfixit_update.sh,when booted from SD)
Then, it is very easy to put that uboot on emmc
In short, using dd,, save emmc mbr,, maybe save 1st 16M,, dd 1st 16m SD->emmc,, restore mbr
This takes literally 5 minutes (or less), also, an OK rescue SD, and good for 32 bit arm apps
The uboot (trust) is good for sleep BTW, it is a bsp uboot, the distro, not at all
Oh, I realized that i didn't say, yes that is the right image
Do you need me to explain the dd commands to you?
RE: Pinebook Pro Boot Issues - Booting needs multiple attempts - mtndew - 10-04-2020
(10-03-2020, 10:11 PM)wdt Wrote: Well, there are at least 4 (slightly) different debian images, this is aarch64 kernel and armhf userland,,
so somewhat unique,, obviously quite good for 32 bit arm apps
I actually have that on my emmc, for reasons, but that is NOT what I recommended to you
I said "rescue SD",, on 8-16G SD, not necessarily highest quality SD,,, do update it (mrfixit_update.sh,when booted from SD)
Then, it is very easy to put that uboot on emmc
In short, using dd,, save emmc mbr,, maybe save 1st 16M,, dd 1st 16m SD->emmc,, restore mbr
This takes literally 5 minutes (or less), also, an OK rescue SD, and good for 32 bit arm apps
The uboot (trust) is good for sleep BTW, it is a bsp uboot, the distro, not at all
Oh, I realized that i didn't say, yes that is the right image
Do you need me to explain the dd commands to you?
I can run dd, that's my preferred method for "burning" disk images.
Can you explain the difference from the boot image on the mrfixit disk image and the uboot-pinebookpro-bsp I installed earlier? How can it fix the garbled screen after soft reboot issue and the bsp image cannot? As far as linux experience, I'm fairly intermediate and I haven't had to deal with booting issues yet. I run Manjaro KDE and Arch on my x86 based desktop and laptop and booting has always just "worked". Would you happen to know if the Manjaro folks plan to create a boot image that fixes the soft reboot issue? Maybe I should report this issue on the Manjaro forum as well?
Thanks for all your help btw!
RE: Pinebook Pro Boot Issues - Booting needs multiple attempts - eKeith - 10-04-2020
(10-03-2020, 10:11 PM)wdt Wrote: ...
Do you need me to explain the dd commands to you?
Would you please? This would help teach. Thanks.
Sent from my PH-1 using Tapatalk
RE: Pinebook Pro Boot Issues - Booting needs multiple attempts - wdt - 10-04-2020
> on my x86 based desktop and laptop and booting has always just "worked".
bios firmware has been around 40 years now, even now as the "csm" module in UEFI firmware
U-boot has existed ~20 years, but it is a lot more work supporting dozens of devices and several architectures
Both mrfixit and manjaro's bsp uboot are patched rockchip bsp uboot, slightly different patches?
Right now, my emmc uboot area is blank, using manjaro 19.10 uboot on SD, unaltered
all I can say is sleep is OK, suggests that it is bsp (19.10)
While I have used "strings" to "dig thru" various uboots, it's hard to get an idea of version numbers,
About dd, a little background first
default bs is 512 bytes, 1 sector,,, DON'T use this when writing more than a very few megs
(quite slow, 1/4 speed or slower, a little hard on nand). I try to use bs=1M, don't have to think much
& when writing an image, don't have to use count=, it will stop at end of if= (input file)
Because different distros have different mmcblkX number, you have to check,, X HAS to be right
lsblk,,, boot0,boot1 always on emmc,,, / will be what you booted from
When I use /dev/SD & /dev/emmc replace with right /dev/mmcblkX
All of uboot is in 1st 16M ,, none of this is mounted
The mbr is 1st sector, or if gpt partitioned first 34 sectors (gpt is not very common, only Ayufan?)
run gdisk /dev/emmc to check,, then q (quit)
If you copy 1st 16M the mbr will almost certainly be wrong, so save original, restore at very end
cd ; mkdir uboot-sav ; cd uboot-sav (shell interprets ";" as <enter>,, a blank directory to work in)
become root/use sudo
dd if=/dev/emmc of=emmc.mbr count=1 (save emmc mbr, 512B)
??? save original emmc uboot???
dd if=/dev/emmc of=1st-16.distro.orig bs=1M count=16
dd if=/dev/SD of=/dev/emmc bs=1M count=16 (to blank,, use if=/dev/zero)
dd if=emmc.mbr of=/dev/emmc (since emmc.mbr is only 512 bytes no need for count or bs)
You will notice, no need for seek or skip or complicated calculations, hardly could be simpler
Just be SURE that X,,mmcblkX is right
BTW, seek is for output, skip for input,,,, man dd (and konqueror is best man pg viewer,, #dd)
One last thought,writing images,, do use xzcat OR zcat (for gz files)... so... xzcat xz-image |dd (no if=)
dd is smart enough to NOT need dd if=- ,,, "-" equals standard input
Also xzcat won't erase original once file is extracted