warning warning , new os images today Oct 11

[sdetweil]

see this story about the changes, live on pi4 and 5
https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/

there are impacts on desktop, video , audio, networking

so expect impacts

[karsten13]

@sdetweil

Thanks!

Major change is the move from X11 to Wayland.

Legacy images are now bullseye, buster is not available anymore.

[BKeyport]

@sdetweil so, does bookworm work at all for MM?

[sdetweil]

@BKeyport yes, without problem, the base works. my updated scripts, in testit branch

I have another test to do, 32 bit on pi4.

32 & 64 on pi3,& pi0w2 are ok
32 & 64 bit on pi4 are ok

| pi0w works ok, had a script bug…

[sdetweil]

@karsten13 but audio system changed too.

[karsten13]

@sdetweil

yes … but the biggest impact for me is wayland because my docker images don’t run on the new Bookworm release. I need to take a closer look, but it’s too late now …

[sdetweil]

@karsten13

interesting…

the install of the 32 bit system on the PI4, results in a hybrid
(pi3 is ok)

64 bit kernel (aarch64) and 32 bit user space (armhf)
| edit, also tested 32 bit bullseye on pi4, installer worked as expected, MM running fine, started by pm2 (also mixed env, uanme is aarch64, but runtime is 32 bit

[sdetweil]

@karsten13 the buster image is still in the archives

warning

I am incorrect…

they removed that image… only the bullseye image remains

but nodejs for armv6l is discontinued after v11… so MM will no longer install or update or run on Pi0W after the 2.24 release AS LONG as you do NOT flash the OS image again… (which would wipe node 16) as node 16 is not available for armv6l devices anymore

warning

[bugsounet]

@sdetweil said in warning warning , new os images today Oct 11:

@karsten13

interesting…

the install of the 32 bit system on the PI4, results in a hybrid
(pi3 is ok)

64 bit kernel (aarch64) and 32 bit user space (armhf)

This was already the case with Bulleyes since May or June 2023.
To have a 32bit kernel just add this in /boot/config.txt :
arm_64bit=0

Result is:

it’s armv7l and not aarch64 ;)

The main problem with aarch64 is some app with compile for x64 using but we can execute it because like you says: it’s an 32bits system
Again… like we know using x64 raspbian OS (full) with a pi it’s not really stable and can make some trouble
So I’m agree with you: it’s complex for manage any update

[bhepler]

The install script worked okay on Armbian 23.8.1 (Bookworm). PM2 install worked great. Screensaver disable didn’t work the first time but after a manual configuration to auto-boot into the user and then a couple of boots it seems to be doing well.