Skip to content

Conversation

@nathan-contino
Copy link
Contributor

No description provided.

@nathan-contino nathan-contino merged commit 4553dc7 into develop Oct 28, 2024
1 check passed
@nathan-contino nathan-contino deleted the pi-os-update-october-2024 branch October 28, 2024 12:36
For information about supported modes and the `mode` syntax, see the https://github.com/WayfireWM/wayfire-wiki/blob/master/Configuration.md#output-configuration[Wayfire documentation].

Add the same configuration block to `/usr/share/greeter.ini` to configure the login screen resolution.
To set a custom resolution, use our Screen Configuration tool, `raindrop`. If your Raspberry Pi OS installation doesn't already include `raindrop` (for instance, if you're still using the previous Screen Configuration tool, `arandr`), you can download `raindrop` from `apt` or the Recommended Software GUI.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that raindrop is in the Recommended Software GUI ?

Switch between the X11 and Wayland backends, and choose a window manager. Since Raspberry Pi OS _Bookworm_, all Raspberry Pi models run Wayland using labwc by default.

NOTE: To use Wayland on Raspberry Pi models prior to Raspberry Pi 4, you must also add `wayland=on` to `/boot/firmware/cmdline.txt`.
NOTE: To use Wayland on Raspberry Pi models prior to Raspberry Pi 4 running a version of Raspberry Pi OS earlier than _Bookworm_, add `wayland=on` to `/boot/firmware/cmdline.txt`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't right. It's "older releases of Bookworm" where you'd have needed to add this wayland=on, not versions before Bookworm. Might be best to just delete this NOTE entirely?

Switch between the X11 and Wayland backends. Raspberry Pi 4 and later use Wayland by default; other models of Raspberry Pi use X11 by default.
Switch between the X11 and Wayland backends, and choose a window manager. Since Raspberry Pi OS _Bookworm_, all Raspberry Pi models run Wayland using the labwc window manager by default.

NOTE: To use Wayland on Raspberry Pi models prior to Raspberry Pi 4 running a version of Raspberry Pi OS earlier than _Bookworm_, add `wayland=on` to `/boot/firmware/cmdline.txt`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above. Also, I never actually edited /boot/firmware/cmdline.txt myself (when I was testing labwc on older Pis) - I just used raspi-config and let that make any necessary changes for me 🙂


[source,console]
----
$ sudo raspi-config nonint do_wayland <W1/W2>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess there might be a W3 here too?

NOTE: To use Wayland on Raspberry Pi models prior to Raspberry Pi 4, you must also add `wayland=on` to `/boot/firmware/cmdline.txt`.
* `W1`: use the Openbox window manager with X11 backend
* `W2`: use the wayfire window manager with Wayland backend
* `W3`: use the labwc window manager with Wayland backend
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably mention that labwc is now the recommended option, and we don't expect to be making updates to X11 or wayfire in future?

@lurch
Copy link
Contributor

lurch commented Oct 28, 2024

The changes made here now seem to suggest that Bookworm has always supported wayland on labwc on models older than Pi 4, which isn't actually the case; and might be confusing for people still running older versions of Bookworm which they haven't updated yet? (e.g. if they're using a Pi in a project which isn't connected to the internet) 🤷‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants