Continuation of rpi effort and how to test
So, I have done the "heavy lifting" so far, but there are still some work needed. Like getting wifi and bluetooth to work (I suspect just adding firmware will help, see example for pine: https://gitlab.com/ubports/core/rootfs-builder-debos/blob/master/pine64-common.yaml#L15). On the graphical side of things, there is still a host of bugs using the wayland session, but this will be worked on in parallel with pinephone and librem5, so this is not a raspberry specific issue. In short, when it gets fixed on pine it gets fixed on rpi too
The build "scripts" can be found here: https://gitlab.com/ubports/core/rootfs-builder-debos/blob/master/raspberrypi.yaml please send pr's here to improve the images.
Images will be built daily by the ci, they can be found here: https://ci.ubports.com/job/rootfs/job/rootfs-rpi/. flashing is really easy using etcher (https://www.balena.io/etcher/) to flash the sdcard.
This has been tested on rpi3, but should work on anything newer then 3 (as it needs arm64)
Some bugs that i saw:
- Won't start without keyboard or mouse connected
- Once unity8 has started, you need to reconnect the mouse/keyboard to make it work
- Performance using the opensource mesa drivers is still not "great"
- Needs swap
- A host of wayland session bugs
Also will leave this here: https://github.com/anholt/mesa/wiki/VC4-Performance-Tricks might be an idea to look into. (that's the mesa driver)
You're an absolute wizard, @mariogrip - thank you so much for doing this. I've already downloaded the image and will try it out tomorrow.
No. Bespoke ARM images can only be installed to their target devices. Similarly to phone images.
@jezek We have images here that are designed for the pinebook https://ci.ubports.com/job/rootfs/job/rootfs-pinebook/ but please note that these are really early images, so they are not stable at all, and there is some bugs
This post is deleted!
Good to see great progress.
Using the latest image the Pi4 boots and runs well although a graphics issue means that you can't read anything opened in a window.
Scaling is now sorted on the monitor and when using the 7 inch touch screen.
The graphics issue does not affect the Pi3 but it is (understandably) frustratingly slow.
The touch screen worked on the first image but not on the most recent one. UPDATE It woked after a reboot but as the left and right edges are slightly offscreen it restricts its usefuleness.
UT on the Raspberry Pi feels much closer now to something that will work. Thanks to those who understand all this far more than me for putting the work in.
Trying v66 on RPI4B 4GB flashed on SDCard with dd command :
- Connected to 1920x1080 screen through HDMI0 => ok
- Need to disconnect/reconnect radio interface for keyboard/mouse
- Overscan is always activated : ~48 pixels/lines black borders
- First and second boot : horizontal view, initial parameters, keyboard layout ok
- Third boot login : rotated, after login : switched to horizontal by itself
- Third boot : wrong keyboard layout (uk instead of previous fr selected)
- Ethernet connected but not seen, WiFi activated, Bluetooth not found
- After third boot, shutdown makes a restart, not a shutdown
- Next time, the shutdown was complete
Main problem :
- The window manager displays the frames and menus correctly
- The application show a correct initial display for one second
- Then, the inner part of the window becomes garbage
- It reminds me something like incoherent window size and viewport size
Calc just started (correct)
Calc after one or two seconds (garbage)
Multiple apps : all garbage, menu and notification : all clean
To remove overscan, uncomment this line
If your mouse lags, try to add this :
at the end of the line in /firmware/cmdline.txt
Another tip : print screen key works
Easy to access to the snapshots by reading the SDCard on my desktop
Will use it next time instead of the ugly pictures above ... Here is a reduced to 720p example :
Maintaining the Super (Windows or Apple) Key displays the available shortcuts. They work AFAIK.
Unfortunately, I was looking for CTRL-ALT-F1 and CTRL-ALT-F7 shortcuts but they don't seem to exist, do they ?
As said above ethernet is not seen (in the notification area) however ethernet is working !
So, one more tip if you want : ssh works too
On your desktop/laptop, use the following command in the /firmware folder of the SDCard
After booting, you can login from your desktop/laptop with
ssh phablet@[local-IP] password: phablet
Have a nice evening
@Pulsar33 the CTRL-ALT-F1 and CTRL-ALT-F7 I confirm they don't work
Is there some progress about graphical problem for Pi4 ?
Hum, seems to regress.
Tried the #77 and I've a black screen after the boot listing and reboot.
However ssh works but don't know what to do with it.
@Mark The work on preparing UT apps for other arm64 platforms gives us something to work with now. The UT Tweak Tool seems to work reasonably as does TELEports and File Manager. I can get sound output from the terminal but not through the apps. Mouse behaviour is a little odd and seems to deteriorate - most of my experience is on the Touchscreen which seems more stable and easier to use. Adding Swap has been helpful, particularly when having multiple open tabs on the Morph Browser. If someone can get to the bottom of the (compositor?) issue with the Pi4 the resource related issues should be much reduced, particulatly with the 2 and 4 GB versions.
Would the approach taken here (with Gentoo running arm64 including camera, sound and display) work for us or is it too far from the way UT works? https://github.com/sakaki-/gentoo-on-rpi-64bit