Raspberry Pi OS 12 (Bookworm) released

[TheOldPresbyope]

Dunno.

I'm looking for clues online but haven't turned up anything useful yet. I may be forced to ask <gasp> on the RPi forum.

ETA - so I noticed an issue on the RPi github repo which induced me to try installing the kernel headers. Turns out that was unnecessary but look at the response. (This on a Pi400 with full desktop but that shouldn't matter)

Code:

kreed@pi400:/lib/modules/6.1.0-rpi4-rpi-v8/kernel $ sudo apt install linux-headers-rpi-v8
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-headers-rpi-v8 is already the newest version (1:6.1.54-1+rpt2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This suggests 6.1.54-1+rpt2 is the answer you're looking for.

Regards,
Kent

[bitlab]

Also for bookworm pi-gen is used for creating the image, so no changes in workflow required for building the moode image.

[Tim Curtis]

@TheOldPresbyope Anything > 6.1.35 will include the Allo fixes :-)
@bitlab thats fantastic !

I see that Wayland is being used instead of X11 for Pi4/5 which is cool but the LocalUI stuff in moOde uses X11 and xset commands :-0

Prolly one of several "opportunities" in Bookworm ;-)

[TheOldPresbyope]

Ah, something I didn't notice yesterday.

In Bullseye and earlier, the boot partition is mounted thusly

Code:

pi@moode: $ lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0     179:0    0 14.8G  0 disk
├─mmcblk0p1 179:1    0  256M  0 part /boot
└─mmcblk0p2 179:2    0 14.6G  0 part /

In Bookworm, it's pushed down a level

Code:

kreed@pi400: $ lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mmcblk0     179:0    0 29.7G  0 disk
├─mmcblk0p1 179:1    0  512M  0 part /boot/firmware
└─mmcblk0p2 179:2    0 29.2G  0 part /

Bookworm, the gift that keeps on giving.

Regards,
Kent

[tomaxsas]

Yeah upgrading to new version is always fun experience. And besides that, Rpi 3 still uses X11 on Bookworm

ALso uname -a gives proper version in comment section

[Tim Curtis]

Couple things I noticed yesterday regarding HDMI ports (Pi-4 / 64bit Bookworm Lite)

1. No tvservice binary

Code:

pi@dev64-bk:~ $ which tvservice
pi@dev64-bk:~ $

2. HDMI device names different from Bullseye

Code:

pi@dev64-bk:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

3. HDMI devices show no mixer controls

Code:

pi@dev64-bk:~ $ amixer -c1
pi@dev64-bk:~ $
pi@dev64-bk:~ $ amixer -c2
pi@dev64-bk:~ $

[Tim Curtis]

Another oddness is the corrupted /home/pi/.asoundrc file after opening raspy-config and just looking at the Audio options :-0

You can track the Git issue here https://github.com/RPi-Distro/raspi-config/issues/223

Code:

pi@dev64-bk:~ $ sudo raspi-config

pi@dev64-bk:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
ALSA lib conf.c:2007:(_snd_config_load_with_include) _toplevel_:18:1:Unexpected char
ALSA lib conf.c:4096:(config_file_open) /home/pi/.asoundrc may be old or corrupted: consider to remove or fix it
ALSA lib conf.c:4018:(snd_config_hooks_call) function snd_config_hook_load returned error: Invalid argument
ALSA lib conf.c:4625:(snd_config_update_r) hooks failed, removing configuration
aplay: device_list:283: control open (0): Invalid argument
ALSA lib conf.c:2007:(_snd_config_load_with_include) _toplevel_:18:1:Unexpected char
ALSA lib conf.c:4096:(config_file_open) /home/pi/.asoundrc may be old or corrupted: consider to remove or fix it
ALSA lib conf.c:4018:(snd_config_hooks_call) function snd_config_hook_load returned error: Invalid argument
ALSA lib conf.c:4625:(snd_config_update_r) hooks failed, removing configuration
aplay: device_list:283: control open (1): Invalid argument
ALSA lib conf.c:2007:(_snd_config_load_with_include) _toplevel_:18:1:Unexpected char
ALSA lib conf.c:4096:(config_file_open) /home/pi/.asoundrc may be old or corrupted: consider to remove or fix it
ALSA lib conf.c:4018:(snd_config_hooks_call) function snd_config_hook_load returned error: Invalid argument
ALSA lib conf.c:4625:(snd_config_update_r) hooks failed, removing configuration
aplay: device_list:283: control open (2): Invalid argument

# Note the card parameter is missing the card number

pi@dev64-bk:~ $ cat ./.asoundrc
pcm.!default {
  type asym
  playback.pcm {
    type plug
    slave.pcm "output"
  }
  capture.pcm {
    type plug
    slave.pcm "input"
  }
}

pcm.output {
  type hw
  card 
}

ctl.!default {
  type hw
  card 
}

Setting the Audio option to Headphones restores the config

Code:

pi@dev64-bk:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
 Subdevices: 8/8
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
 Subdevice #4: subdevice #4
 Subdevice #5: subdevice #5
 Subdevice #6: subdevice #6
 Subdevice #7: subdevice #7
card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
pi@dev64-bk:~ $

[TheOldPresbyope]

Been away since the weekend. Finally back poking around Bookworm.

Regarding WiFi, it actually still uses wpa_supplicant to establish the connection (authentication, handshaking, etc) but under the control of NetworkManager via DBus. 

In particular, the file /etc/wpa_supplicant/wpa_supplicant.conf isn't used. Instead, connection details are stored in /etc/NetworkManager/system-connections/<SSID>.nmconnection files.

On a headless bookworm system for which I preconfigured WiFi in the RPi Imager before flashing (my SSID is Krypton):

Code:

###like wpa_supplicant.conf before it, only root can read/write the connection file###

kreed@rpios1264:/etc/NetworkManager/system-connections $ ls -l
total 4
-rw------- 1 root root 326 Oct  9 23:57 Krypton.nmconnection

###the content is similar to the content of a wpa_supplicant.conf file but not the same###

kreed@rpios1264:/etc/NetworkManager/system-connections $ sudo more Krypton.nmconnection
[connection]
id=Krypton
uuid=b48f997d-3923-4eeb-9363-6db20e190763
type=wifi
interface-name=wlan0

[wifi]
mode=infrastructure
ssid=Krypton

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=<elided>

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]
(END)

I haven't quite worked out how this got configured when Bookworm booted. Apparently, the /boot/firstrun.sh script uses scripts in the rootfs which are OS-version-specific to deal with the setup but it still mentions /etc/wpa_supplicant/wpa_supplicant.conf. I'm sure it will turn out to be something obvious.

Regards,
Kent

[Tim Curtis]

Been away since the weekend. Finally back poking around Bookworm.

Regarding WiFi, it actually still uses wpa_supplicant to establish the connection (authentication, handshaking, etc) but under the control of NetworkManager via DBus. 

In particular, the file /etc/wpa_supplicant/wpa_supplicant.conf isn't used. Instead, connection details are stored in /etc/NetworkManager/system-connections/<SSID>.nmconnection files.

On a headless bookworm system for which I preconfigured WiFi in the RPi Imager before flashing (my SSID is Krypton):

Code:

###like wpa_supplicant.conf before it, only root can read/write the connection file###

kreed@rpios1264:/etc/NetworkManager/system-connections $ ls -l
total 4
-rw------- 1 root root 326 Oct  9 23:57 Krypton.nmconnection

###the content is similar to the content of a wpa_supplicant.conf file but not the same###

kreed@rpios1264:/etc/NetworkManager/system-connections $ sudo more Krypton.nmconnection
[connection]
id=Krypton
uuid=b48f997d-3923-4eeb-9363-6db20e190763
type=wifi
interface-name=wlan0

[wifi]
mode=infrastructure
ssid=Krypton

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=<elided>

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]
(END)

I haven't quite worked out how this got configured when Bookworm booted. Apparently, the /boot/firstrun.sh script uses scripts in the rootfs which are OS-version-specific to deal with the setup but it still mentions /etc/wpa_supplicant/wpa_supplicant.conf. I'm sure it will turn out to be something obvious.

Regards,
Kent

Hopefully it's a clean switchover to the new config and not some sort of either/or/depending. That would be messy :-0

[Tim Curtis]

Bookworm development host is up and running :-)