(05-05-2021, 10:33 AM)CharlesBunders Wrote: (05-05-2021, 09:59 AM)wdt Wrote: >It prompted to use library's in different locations and make changes.
I'm guessing you mean different repositories?????
If so, this means no network
Check,,,ip a
Then,,,, nmtui
I really hosed my sd card boot a week ago, had to go thru this and more
Usually pacman -Syu is the main recovery method
Not different repositories. Image attached.
nmtui worked great. I could activate the network connectivity and ran pacman -Syu. I chose Y for all the suggestions and once complete it still boots and just has a cursor flashing in the upper left. Never gets in to Manjaro.
those are repositories that the packages had been moved to. (iirc) Manjaro began some reorganizing aarch64 packages to match that of their x86 repos during last year. you should approve those in your update. You're not getting updates to KDE by denying them.
05-09-2021, 05:09 PM
(This post was last modified: 05-09-2021, 05:26 PM by CharlesBunders.)
Thank you for the replies. They were all helpful, especially the suggestion to use " nmtui". With that I could get the network working from the state the machine was in. With that working I tried running a straight update and that didn't help. I used etcher to create a Debian image on an sd card. Inserting that and rebooting worked and the machine runs nicely from that image. However, in trying to get that image burnt on to the storage of the Pinebook Pro it didn't seem to work.
I did a:
$ xzcat imagename.img.xz | sudo dd of=/dev/mmcblk2 bs=1M status=progress conv=fsync
This appeared to run and work but shutting down, removing the sd card and restarting the machine it still launched Manjaro.
What I am doing wrong here, do I need to flash something to /dev/mmcblk1 too?
Code: Filesystem Size Used Avail Use% Mounted on
/dev/root 59G 6.0G 50G 11% /
devtmpfs 1.9G 1.9G 0 100% /dev
tmpfs 1.9G 35M 1.9G 2% /dev/shm
tmpfs 1.9G 14M 1.9G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/mmcblk0p1 63M 25M 39M 39% /boot
tmpfs 388M 4.0K 388M 1% /run/user/109
tmpfs 388M 28K 388M 1% /run/user/1000
/dev/mmcblk1p2 58G 6.7G 48G 13% /media/rock/ROOT_MNJRO
/dev/mmcblk1p1 214M 58M 156M 27% /media/rock/BOOT_MNJRO
Got it figured out. Using examples from this video:
https://youtu.be/mTyBI2PO4I0
Using the command:
$ lsblk
I could see I needed to unmount a few things, then I had to target mmcblk1 not mmcblk2. Debian installed on the emmc and works great.
Thanks.
(05-06-2021, 02:50 PM)James Good Wrote: This might only be slightly related to the topic of this thread. On June 11, 2020, DHL finally delivered the PBP that I had ordered in late October or early November of 2019. Initial power-on was uneventful and the passwords were set as suggested. The PBP was not used, but was fully charged, for about a week then restarted. This second start resulted in the PBP starting another system update or upgrade to the operating system. The battery was full, so there was no real problem. An hour or two later after the update or upgrade finished, the PBP restarted. No problem. However, the password I had set the week before was not recognized and there was no clear way to reset either the root or user password. After several months of trying to turn the PBP back on and start learning how it does (and should) work, near total frustration set in and I attempted to load another version of Linux on it more in the effort to have a laptop that could be used than anything. Multiple attempts by me with several different distros of Linux later the PBP still would not boot. I asked a friend that has programming experience if he would like to try and he did. After almost two weeks, he gave it back to me and said that he was not able to get any OS to load or boot to the internal drive (eMMC) and said that he was at a loss on how to proceed now. He did say that he was able to look at what is on the internal drive and found fragments of TWO different operating systems. Neither he nor I know how to proceed from here. The desired goal would be to be able to have Manjaro loaded and operational on the PBP, but if that is not possible then a recent version of a Debian release could work. But it almost looks like the laptop might need to be looked at in a shop that has the equipment necessary to completely erase then restore the internal drive to a 'factory new' condition. I live in the USA and would prefer to send the laptop to a repair shop in the USA rather than have to send it to another country.
Please advise on what steps should be attempted next.
Thank you,
James Good
1. Download the Manjaro-ARM-kde-plasma-pbpro-20.04-emmc-installer-20.04.img.xz from this link: https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/20.04/
2. DD to microSD card (8GB or larger)
3. plug into your PinePook Pro microSD slot and power up
4. Follow on screen instruction and reflash the Pinebook Pro eMMC
5. Your Pinebook Pro back to factory reset condition
(05-19-2021, 02:28 AM)tllim Wrote: (05-06-2021, 02:50 PM)James Good Wrote: This might only be slightly related to the topic of this thread. On June 11, 2020, DHL finally delivered the PBP that I had ordered in late October or early November of 2019. Initial power-on was uneventful and the passwords were set as suggested. The PBP was not used, but was fully charged, for about a week then restarted. This second start resulted in the PBP starting another system update or upgrade to the operating system. The battery was full, so there was no real problem. An hour or two later after the update or upgrade finished, the PBP restarted. No problem. However, the password I had set the week before was not recognized and there was no clear way to reset either the root or user password. After several months of trying to turn the PBP back on and start learning how it does (and should) work, near total frustration set in and I attempted to load another version of Linux on it more in the effort to have a laptop that could be used than anything. Multiple attempts by me with several different distros of Linux later the PBP still would not boot. I asked a friend that has programming experience if he would like to try and he did. After almost two weeks, he gave it back to me and said that he was not able to get any OS to load or boot to the internal drive (eMMC) and said that he was at a loss on how to proceed now. He did say that he was able to look at what is on the internal drive and found fragments of TWO different operating systems. Neither he nor I know how to proceed from here. The desired goal would be to be able to have Manjaro loaded and operational on the PBP, but if that is not possible then a recent version of a Debian release could work. But it almost looks like the laptop might need to be looked at in a shop that has the equipment necessary to completely erase then restore the internal drive to a 'factory new' condition. I live in the USA and would prefer to send the laptop to a repair shop in the USA rather than have to send it to another country.
Please advise on what steps should be attempted next.
Thank you,
James Good
1. Download the Manjaro-ARM-kde-plasma-pbpro-20.04-emmc-installer-20.04.img.xz from this link: https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/20.04/
2. DD to microSD card (8GB or larger)
3. plug into your PinePook Pro microSD slot and power up
4. Follow on screen instruction and reflash the Pinebook Pro eMMC
5. Your Pinebook Pro back to factory reset condition Thank you for this information and the directions. I have completed the flash to the micro USB card and will complete the instructions in the morning (my local time).
|
