@Pudge do you use the SD card directly or through a USB adapter? I had the impression that through the USB adapter it’s faster, though the adapter gets really hot
if go down that road … better use
atm i use on Rpi5 ( have used on PBP ) still 128 GB SanDisk Extreme Pro microSDXC most reliable i use on PBP (internal slot or a SABRENT M.2 NVMe 500GB internal connected) if more it become " flakey" like Mr Pudge say
Edit… sad all speeds limited ( still no bad )
2 Likes
I use the uSD card directly into the uSD slot on the PineBook Pro.
So far I haven’t installed to an eMMC module. I will still keep the 64 GB eMMC with Manjaro on it for reference. Eventually I will be running the PBP from a spare 64 GB eMMC I bought with the device.
Pudge
EDIT:
The PineBook Pro is kind of useless for me because all my mp3, images, videos, and anything even slightly important are on my RPi 4b LAN sever. PineBook Pro doesn’t have a Ethernet connector and I refuse to enable WiFi on the RPi 4b server.
To remedy this, I have this unit on the way (should be delivered today) and will see how it works.
Gives me Ethernet support when at home, and 3 extra USB 3 ports.
1 Like
i use sshfs from rpi4 or n2 for that … you point that to me 
yes need adapter for Ethernet
1 Like
Once I get the adapter, the majority of personal files, mp3, images, and videos do not have to reside on the PineBook Pro. With that load gone, 64 GB to 129 GB storage device is more than enough.
The way I have it set up, when I bootup the PineBook Pro, the LAN server is mounted via sshfs to a directory off my home directory on my desktops.
cat AutoMountServer
#!/bin/bash
sshfs pshare@enosServer:/server /home/$USER/enosServer
exit
Pudge
1 Like
near same . i no auto mount ( i have zero auto mount for less point of fail ) i old + i like decide when thing mount only when i need . 125GB enough for sure
EDit… simple alias for few , they mount ( 99% of time in terminal any way , so easy )
1 Like
I was always wondering why there is so much talk about the sd cartds to use… some weeks ago i stumble over armbian webside they have a good information about this.
1 Like
1 Like
Hi guys,
Rock 5B owner here, I’ve tried all three methods of installation, so far none have been successful. On two of the methods the plasma desktop shows up but the installer won’t launch. For that matter nothing launches. The other method just gives a blank screen with a mouse arrow. Following the install as it went along, nothing indicated a problem.
Any ideas? Thanks!
Thanks for reporting back, it is appreciated.
Later this evening, I should have time to do some test installs on Radxa Rock 5B and see if I can duplicate these problems.
Catch ya later
Pudge
you have any read through about lifespan of sd cards?
Which kernels are used in the PBP image? Back in the day, Nadia used to compile her own images. Then, the guy that took over moved back to using Manjaro’s images.
I haven’t read about it, but over the last 4 years I have lived it.
Pudge
1 Like
I compile the kernel myself using this PKGBUILD
In the spirit of full disclosure, that PKGBUILD is based on Manjaro’s PKGBUILD with some modifications with the patches, and “config” is modified to enable btrfs amongst other things.
Pudge
2 Likes
On this unit, Radxa ROCK 5B with a RK3588 SOC and Mali G610 graphics I made three test installs
These images were designed for the RK3588 (Not RK3588S) with Mali G610 graphics. Any variation in SOC or graphics will probably not run on these images:
rootfs-radxa-5b-20231208
ddimg-radxa-5b-20231208
I did three test installs, using the three methods of installation, and all worked as expected.
Method 1 - Samsung Pro Plus 128 GB uSD - KDE Plasma - x11 - on btrfs
Method 2 - SanDisk 32 GB uSD - i3wm - x11 - ext4
Method 3 - Samsung EVO select 128 GB uSD - Cinnamon 6.0 - Wayland - ext4
I have a Samsung SSD 970 EVO Plus 250GB NVME that I use for image development.
I plugged in the uSD cards with the NVME still connected, and it booted from the uSD when present, and booted from the NVME when the uSD was not present. Have not tried eMMC or USB SSD yet.
At this point, I don’t have any guesses without more information.
Pudge
EDIT:
I re-read your post, and it kind of sounds like video problems.
1 Like
Ah, I am using a 4k monitor, I’ll try a 1080 monitor. Yeah I think I had this issue with some other installs. Once installed, 4k resolution worked just fine. Also, I’ll verify if display port alt-mode works and report back. Thanks
1 Like
Yes, this is the unit I have. I’ve gone back and tried all three methods with a 1080p monitor. Booting from an Amazon Basics 64gb micro sd card.
Methods 2 & 3 same result as before. The installer would not launch from the plasma desktop.
Method 1, booting from the sd card went into emergency mode and I was able to log into root and run a journactl:
systemd[1]: Failed to mount /boot
systemd-modules-load; Failed to find module ‘crypto_user’
systemd-modules-load; Failed to find module ‘pkcs8_key_parser’
My unit is set up like yours and using Arch and Ubuntu installs behaves the same way.
I really want to try EoS Cinnamon 6.0 with wayland. Hope we can solve this.
Thanks…
You have me stumped. There are only a few things I can think of.
-
the Radxa ROCK 5B is very sensitive about power modules. If I remember correctly from another Topic that you had the Official Radxa ROCK 5B 30 Watt power supply ?
-
Try another micro SD card. I have been tinkering with ARM devices for about 4 years now and have tried a lot of different uSD brands. Now I only use Samsung or SanDisk uSD. Look for the ratings of a U with a 3 inside it and A2 V30. See Post # 11 of this Topic.
-
Did you flash the SPI chip that is physically on the Radxa 5B board. I had to temporally install Debian to flash the SPI chip. I don’t think this is the problem here, but who knows. I used the simple method. Legaleese - Flash the SPI chip at your own risk.
https://wiki.radxa.com/Rock5/install/spi
Pudge
1 Like
I did three test installs today.
Method 1 failed, the AS card written in the live EOSx86 environment wouldn’t boot properly, it would take me to an error message where my option was to press control + D do go to root access or something. I can look into it more and get some logs if it’s of interest.
Method 2 worked, it resulted in a Gnome install in ext4, of course, and method 3 worked, and resulted in a btrfs working gnome system, but:
- tap to click wasn’t’ enabled, in the SD install environment or in the resulting system.
- Ethernet isn’t recognized, and Wi-fi isn’t recognized upon first boot, only after powering off and rebooting. Now that I think about it, maybe the problem was that the first boot was after restart and not after powering off, the PbP is finicky about that for things like bluetooth and wifi, right, mr, @Shjim?
No Ethernet or Wifi:
Wifi, but no Ethernet:
A working btrfs system!
Maybe the Ethernet thing is related to the Kernel? In my eMMC the kernel (arch using manjaro kernel) is 6.2.x, I think.
@Pudge, thanks for making this possible, and do let me know if you think I can help further.
1 Like