Raspbian 12 Bookworm and 11 Bullseye for Libre Computer Boards

Start
, ,
146

Okay. I just used the menu editor to change ‘Preferences–>Raspberry Pi Configuration’ to ‘sudo raspi-config’ and checked ‘Launch in terminal’ It’s a decent workaround that is still accessible from the GUI.

Thanks.

147

I had to modify /etc/network/interfaces and add the following line for my wifi dongle to work:

auto lo
iface lo inet loopback
iface eth0 inet manual

auto wlan0
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
1 Like
148

you saved me, thanks!

149

For those looking for a headless setup: ignore the Raspberry Pi Imager configuration GUI, it is completely ignored. The Raspberry Pi Imager only does two things:

  1. Creates a file called firstrun.sh that will configure the device on the first boot (and then delete firstrun.sh)
  2. Adds systemd.run=/boot/firstrun.sh to the cmdline.txt file

The problem is that firstrun.sh is never executed because cmdline.txt is completely ignored, see here for confirmation: Raspbian 12 Bookworm and 11 Bullseye for Libre Computer Boards - #78 by librecomputer

You can use Raspberry Pi Imager to perform this setup through the GUI on first boot

@librecomputer could you remove this recommendation from the post or provide a workaround to make sure that firstrun.sh is executed?

1 Like
150

We can include this in the July release. Thanks for bringing this up.

151

Hi,

do you have an ETA of the July release? I’m kinda waiting for this - for multiple reasons.
And because I have 5 S905 boards with emmc I’d like to do this in one step.

Cheers

152

I just noticed the July releases were posted yesterday. I’m surprised there was no announcement.?
https://distro.libre.computer/ci/raspbian/11/

153

We push the beta release to the server already. It’s 99% there and way better than the previous images in every conceivable way. However there’s still some finishing touches like the first-run.sh mentioned that we need to integrate.

154

We have added firstrun.sh functionality in the first partition (mounted as /boot/efi) to our Raspbian 11 images. Raspbian 10 does not seem to have this functionality so we did not add it to Raspbian 10. This will be released as part of the image update cycle in a few days.

155

Cool!
Out of curiosity, what method did you use to trigger it? I believe that on an RPi, they insert a line in cmdline.txt that calls firstrun.sh (and I believe it deletes this line upon successful completion). But, I’m assuming that you still aren’t doing anything with the cmdline.txt file, right?

156

We just added a systemd service wanted by multi-user.target after local-fs.target. We ripped out all of the hacky stuff Raspberry Pi’s bash scripts do since we have better facilities for those anyway.

157

2023-05-03-raspbian-bullseye-arm64+aml-s905x-cc.img.xz
error during boot. lite version works fine but desktop version does not work. during the boot, a mounting error is mentioned and the full system will never boot or install.
i tried dd and rpi-imager.

158

Probably an error with your flash tool or MicroSD card. What is the exact error?

We have no problems booting that image.

159

Le Potato has a very long bootup (at least for me) where it will take ~5min before anything shows up on the HDMI display. As long as all three (blue green red) LEDs are lit it should eventually display something. It seems more picky about uSD cards than an RPi, where even cheap throwaway cards work in a RPi don’t work on Le Potato. Use a SanDisk or Samsung uSD card for best results.

160

This should not be the case. It should show video within 3 seconds of power on. What is the make and model of your display?

161

I’ve tried with tons of displays.
Seiki 39" 4k
Uperfect mini (1080p)
some no-name RPi touchscreen display (1024x600)
Samsung 4k TV
Element 4k TV
Spectre 4k monitor
and too many more

The time from plugin to display is always super long.

162

On a different note, replacing ‘bullseye’ with ‘bookworm’ in all the apt sources and doing a full dist-upgrade to try to upgrade to debian 12 base makes the GUI horrible after reboot - it seems to replace all the rpi desktop with something that seems to be debian but not really.

Is there any way to get the rpi desktop back, or should I just reflash back to debian11 base?

163

You are doing something wrong then. Those displays should be supported. We have Debian 12. Why are you upgrading Raspbian which is based on Debian 11?

164

Does Libre have a recommended upgrade procedure for its boards for when new images are published? Is the procedure the same whether it is a point release vs. a full version upgrade?

For example, if I have a Le Potato running the 2022-09-22 release of Raspbian Bullseye, what is the procedure for upgrading to the 2023-05-03 Bullseye release?

Is this the same procedure you would recommend for going from Buster to Bullseye (or Bullseye to Bookworm, once that is released)?

I am assuming that simply running apt upgrade is not going to take care of upgrading the bootloader and microboot? So, at some point, I am going to need to do something more if I want to take advantage of all the latest fixes and features, right?

165

To break it down:

  1. Bootloader

This is too dangerous for us to update without bricking existing setups. We leave this up to the user to do via libretech-flash-tool with the force parameter.

  1. Linux

This is automatically updated.

  1. Userspace

Userspace utilities are automatically updated. Sometimes we make changes to the base configuration like adding default packages, etc. These are not automatic but not consequential to your image if you don’t use them.