11-11-2023, 06:17 PM
(This post was last modified: 11-11-2023, 07:23 PM by TheOldPresbyope.
Edit Reason: addendum; typos
)
More on Bookworm/Wayland/localUI
Good news: the same uSD card with Bookworm and wayfire on it boots on my Pi5B, Pi4B, and Pi3B+ and runs either Chromium or Firefox using Wayland protocol rather than X11.
There's obviously some cache-building going on when wayfire and a browser are first invoked. Here's just the chromium-browser results but there are similar differences for firefox (and as reported before, always longer times than for chromium-browser)
Pi5B - wayfire/chromium-browser 1st run: 24s to moodeaudio homepage
wayfire/chromium-browser 2nd run: 4s
Pi4B - wayfire/chromium-browser 1st run: 26s
wayfire/chromium-browser 2nd run: 9s
Pi3B+ - wayfire/chromium-browser 1st run: 40s
wayfire/chromium-browser 2nd run: 12s
If I reboot, then this process starts over.
Note that the transition from terminal screen to full screen moodeaudio homepage is rather busy visually: first, a period of dark screen with cursor outline in white; second, a period of white screen with cursor solid in black; then dark screen with rotating red circular line segments; finally, the browser window.
Second good news: the Pi5B and Pi4B were outputting to an HDMI LCD screen; the Pi3B+ was outputting to an official Raspberry Pi 7-in LCD touchscreen. I didn't notice any performance issue with the Pi3B+ relating to Wayland/wayfire. A USB mouse worked with either display; haven't tried touchscreen.
Addendum: Of course the touch function of the touchscreen display should just work...but it doesn't. I should have checked the repo for issues first: Touchscreen not working with latest Bookworm image.
So, ran rpi-update on my 10-10-2023 Bookworm Lite installation. The kernel was bumped from
to
and I can now use the touch function to make selections on the touchscreen display.
Regards,
Kent
Good news: the same uSD card with Bookworm and wayfire on it boots on my Pi5B, Pi4B, and Pi3B+ and runs either Chromium or Firefox using Wayland protocol rather than X11.
There's obviously some cache-building going on when wayfire and a browser are first invoked. Here's just the chromium-browser results but there are similar differences for firefox (and as reported before, always longer times than for chromium-browser)
Pi5B - wayfire/chromium-browser 1st run: 24s to moodeaudio homepage
wayfire/chromium-browser 2nd run: 4s
Pi4B - wayfire/chromium-browser 1st run: 26s
wayfire/chromium-browser 2nd run: 9s
Pi3B+ - wayfire/chromium-browser 1st run: 40s
wayfire/chromium-browser 2nd run: 12s
If I reboot, then this process starts over.
Note that the transition from terminal screen to full screen moodeaudio homepage is rather busy visually: first, a period of dark screen with cursor outline in white; second, a period of white screen with cursor solid in black; then dark screen with rotating red circular line segments; finally, the browser window.
Second good news: the Pi5B and Pi4B were outputting to an HDMI LCD screen; the Pi3B+ was outputting to an official Raspberry Pi 7-in LCD touchscreen. I didn't notice any performance issue with the Pi3B+ relating to Wayland/wayfire. A USB mouse worked with either display; haven't tried touchscreen.
Addendum: Of course the touch function of the touchscreen display should just work...but it doesn't. I should have checked the repo for issues first: Touchscreen not working with latest Bookworm image.
So, ran rpi-update on my 10-10-2023 Bookworm Lite installation. The kernel was bumped from
Code:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 6.1.0-rpi4-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (202
3-10-05) aarch64 GNU/Linuxto
Code:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 6.1.61-v8_16k+ #1696 SMP PREEMPT Thu Nov 2 16:49:24 GMT 2023
aarch64 GNU/Linuxand I can now use the touch function to make selections on the touchscreen display.
Regards,
Kent
