+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: General Discussion on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=112)
+--- Thread: 3 days in, slow/stuck or no boot. (/showthread.php?tid=19324)
RE: 3 days in, slow/stuck or no boot. - lgmpbp2 - 07-26-2024
Thanks. Will give it a go.
Re @tophneal comment- it doesn't look similar but thank you.
RE: 3 days in, slow/stuck or no boot. - lgmpbp2 - 07-26-2024
"Bad CRC using default environment"
this means something is corrupt in hard drive?
RE: 3 days in, slow/stuck or no boot. - wdt - 07-26-2024
No hard drive, only flash
Unless you flashed SPI, a 16M chip,,, & it is likely you did not,
the controlling uboot (+idbloader) is on emmc
If that message is early in boot it is likely a uboot message
complaining that there is no custom configuration (of uboot)
and can be ignored ..
I seem to recall that complaint, but how and when are you seeing it?
what does lsblk say? Does it show all the storage devices? and their partitions?
You could fsck the partitions shown and see if there are any errors
RE: 3 days in, slow/stuck or no boot. - KC9UDX - 07-27-2024
It's normal early in booting. U-Boot is saying it can't boot from SPI ROM, because you haven't formatted it (and don't need to).
RE: 3 days in, slow/stuck or no boot. - lgmpbp2 - 07-27-2024
Thank you
RE: 3 days in, slow/stuck or no boot. - Generaltuxenburg - 07-28-2024
(06-30-2024, 10:04 AM)lgmpbp2 Wrote: Very glad to receive Pinebook Pro last Thursday June 27th.
Quite cautious with it- no new OS installs as am new to Pine products and fairly new to Linux.Sunday, June 30, Pinebook pro boots to Manjaro images. After a few hard reboots, Manjaro image, again. Press escape.
Received the message below. Hard re boot again to black screen and no Manjaro image. Unsure how to proceed. Please advise? Apologies if this was discussed previously
Honestly unless you love Manjaro I would just install Armbian it’s far superior at least in my experience.
RE: 3 days in, slow/stuck or no boot. - lgmpbp2 - 08-04-2024
Thanks to everyone for advice & suggestions. Attempted Armbian. Unsure if it is truly installed on eMMc
Can't seem to upload screenshots
Will get back to you.
RE: 3 days in, slow/stuck or no boot. - lgmpbp2 - 08-30-2024
Update: 1.cannot use SD cards, now, but USB stick of pmOS works;
2. re flashed Tow-Boot to SPI;
3. Got Pine64 emmc adapter & another emmc module;
4. Flashed pmOS to emmc module, put it in PBP, but receive message something like; "emmc didn't respond to voltage select -110;
5. Flashed Armbian to another emmc module and put in PBP but received the same message.
Currently, have pmOS KDE Plasma on USB 2 on PBP.
Conclude from the messages about voltage select- 110 that the timing is off, or the emmc isn't positioned properly, or the u-boot is an issue? This is from scanning similar issues on the internet. Please know I really like PinebookPro, am not a techie but have watched tutorials to understand as much as possible, and I suppose I believe in the community or concept of PBP. Thus, am not criticising, but hoping to understand and find a solution Because I would like to get the PBP up and working from emmc. Thank you.
RE: 3 days in, slow/stuck or no boot. - KC9UDX - 08-31-2024
Just from my experience; others may disagree: I would zero out the SPI ROM until you get everything working. Put U-Boot or Tow-Boot on the eMMC and boot from that.
RE: 3 days in, slow/stuck or no boot. - wdt - 09-01-2024
Since most emmc are soldered down the specs are little known
There are specs for speed, HS200 and HS400, I do know that
a 120 GB emmc I have only works in 1 of the 3 adapters I have
Anyway I assume that the original emmc works, so why not
fsck it when booted in pmOS?
This was the original error IIUR, this can be done from the emergency
shell that shows in your screen shot as well
OR install armbian on it, again when booted pmOS.
OR install when plugged into pc?
If you are a windows refuge, there is a version of etcher for win
(etcher is fairly safe in that it is hard to write to wrong device, it can be done, but not easily)