Debian Bullseye for OpenFrame

[alexis92]

________________________________________________________________

Debian Bullseye for OpenFrame (Kernel 5.10)
Operating System Patches / Kernel Patches / Build Log
________________________________________________________________


We have once again outlived another long-term-support operating system!

This time we're going completely modern; Debian Bullseye with the officially supported 5.10 kernel branch - with working audio switching!

One really nice thing is that we're now in line with the latest Raspberry Pi operating system, meaning a lot of their documentation should be now be applicable to the OpenFrame. Hardware variations dependent of course, but still handy given their huge user base of tinkerers.

Before anybody asks, no, our old nemeses of Imagination Technologies and Intel still prevent anybody from having OpenGL support on the GMA500 Poulsbo chipset. However, we are using the kernel driver with... well, whatever updates it has seen in recent years.

The automated build system lives on (in fact it's just been completely refreshed) so you should always be able to visit the link up above and get the very latest kernel with a fully patched operating system. Build logs are here in case you want to check the latest version came together without errors.

As with the previous image this is command line only out of the box, created to be as 'vanilla' as possible. This means you can use instructions available for any Debian Bullseye system to install whichever GUI environment you might like. Or none at all.


Highlights

• Single image for any OpenFrame.
• Built for size; about 430 MB space used initially.
• Fully working audio and video with kernel drivers.
• Simple before-boot wireless network configuration.

Installation and Setup

So I'm not editing in multiple places, please check the instructions on birdslikewires.net.


Issues

- Right now I have not tested the of-install scripts, so these are likely to be a disaster.
Rather than hold up the release for a few convenience scripts, I'll get around to these when I can.™

- SqueezePlay is in dire need of a revamp.
I've not been using it recently, though I am keen to update it... check my trade marked comment above.

- Website instructions are a bit outdated.

I hope this update finds you all well and you can make good use of it!

The link doesn't seem to be working for me, just wanted to ask if it is something on my end?

[Paul Webster]

At the moment ...
of@openframe:~$ sudo of-update
Server error by openbeak.net (500).
Update aborted.

I tried to install Squeezeplay using of-install and it failed.
I traced the problem to the useradd command that has -s bash instead of -s /bin/bash
Made that change locally and reran of-install and it worked.

Went off the suggest that fix over in repository and found that it was already in there at least 2 years ago.
So I think that, at least until of-update is working again ... the scripts in the downloadable image need updating.

[Man in a van]

I have tried using "of-expand"

It sort of works

After the reboot one has to wait for a long time as the screen reports blocks being added until finished.

I know roobarb! has mentioned the "of" commands are one his list of thinks to fix.

ronnie

[roobarb!]

the scripts in the downloadable image need updating.

They do indeed. I'm impressed you got SqueezePlay to install, amazed in fact!

I have tried using "of-expand"

It sort of works

That one should be working fine. I use that on every test build. It does take a while after rebooting to complete the resize, just the nature of the task, but the system is completely usable while it does so.

[Paul Webster]

One big difference for me compared to the previous build that I had installed ... is that the WiFi has remained up the whole time.
With the previous one, on the same Joggler in the same location and same access points, I found that the WiFi was dropping out after a few hours.
With this one I have had SSH session open for 2 days with no drops.

[roobarb!]

With this one I have had SSH session open for 2 days with no drops.

That's good news, I assume you're using the original RT2770 (iirc) adapter?

[Paul Webster]

I see RT2860 mentioned in dmesg.

However, SSH session did drop after another day or two but, unlike with the previous OS version, the WiFi connection on the Joggler reestablished itself so I could SSH in again.

[ethirolle]

Hey folks! First post here... and of course, I'm hoping someone can help me solve a little problem

I got Debian Bullseye for OpenFrame installed, created a "squeezeplay" user, and ran "sudo of-install squeezeplay"... and even installed Enhanced Digital Output (EDO). And it works! UI and touch screen are functioning, and I can play music via the USB out into a DAC, and on to my recover. Woo-hoo!!

BUT... I can't turn off or reboot this Joggler from the options (Reboot and Shutdown) under the "Quit" menu in the Jive UI. When I try, it hangs for about 10 seconds, and then goes back to the main menu.

And if I make a change (like change the Digital Out) that forces a reboot, the UI just hangs on the "Rebooting" screen.

I've tried adding the squeezeplay user to the sudo group, then editing sudoers file to add this:

Code: Select all

# Allow squeezeplay to run commands in /opt/squeezeplay/bin/openframe_power.sh, with no need for password
squeezeplay ALL = NOPASSWD: /bin/systemctl reboot -i, /bin/systemctl poweroff -i, /bin/killall jive

And I think I tried a couple other things that I have now forgotten... but no luck.

Any idea how I can resolve this? I'd like to be able to shut down the Joggler without needing to SSH into it (and I hate just pulling the plug without sending the OS the proper shutdown command),

Thanks!!

---

Addendum: I figured out which log file to tail: /var/log/daemon.log. When I click the "Shutdown" menu option, I see this in that log:

Code: Select all

Jul 22 02:33:54 openframe startx[659]: Failed to set wall message, ignoring: Interactive authentication required.
Jul 22 02:33:54 openframe startx[659]: Failed to power off system via logind: Interactive authentication required.
Jul 22 02:33:54 openframe startx[659]: Failed to start poweroff.target: Interactive authentication required.
Jul 22 02:33:54 openframe startx[659]: See system logs and 'systemctl status poweroff.target' for details.

Following the suggestion in that last log line yields:

Code: Select all

# systemctl status poweroff.target
● poweroff.target - Power-Off
     Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:systemd.special(7)

but I'm still not sure how to bypass the need for these interactive authentications...

Thanks!

---

OK, a bit more work and I think I got this figured out. Solution was in two parts:

(1) re-order the lines in /etc/sudoers so that the configuration for the user squeezeplay comes AFTER the config for the sudo group (per https://askubuntu.com/a/340669). In that way, the user config overrides the group config:

Code: Select all

# Allow members of group sudo to execute any command
%sudo	ALL=(ALL:ALL) ALL

# Allow squeezeplay to run commands in /opt/squeezeplay/bin/openframe_power.sh, with no need for password
squeezeplay ALL = NOPASSWD: /bin/systemctl reboot,  /bin/systemctl reboot --no-wall -i, /bin/systemctl reboot -i, /bin/systemctl poweroff -i, /bin/killall jive

(2) edit "/opt/squeezeplay/bin/openframe_power.sh" to add "sudo " before each command, like

Code: Select all

sudo systemctl reboot -i

[proddick]

I am setting up another Joggler and downloaded the 4 Aug 2022 build 135 and it didn't boot. I noticed that it is a LOT smaller than previous ones so perhaps the build failed? I downloaded the 30 July 2022 build 134 and that one booted fine.

[roobarb!]

I am setting up another Joggler and downloaded the 4 Aug 2022 build 135 and it didn't boot. I noticed that it is a LOT smaller than previous ones so perhaps the build failed? I downloaded the 30 July 2022 build 134 and that one booted fine.

Thanks for the heads-up, looks like some 404 error on the Debian apt servers killed this build. It limped along and generated an image, but yeah, it's broken.

I'll clear it out and let it run again overnight.

[roobarb!]

I'll clear it out and let it run again overnight.

The .135 image looks fine this time!