Debian Bullseye for OpenFrame

[Man in a van]

@roobarb!

Just for info (you must have eaten ebnough chocolate by now, surely )

I have just tried the latest image

/debian/latest_510/bul-ext2-1028-43-bullseye-5.10.177op. 06-Apr-2023 04:54 186M

and get the following output on the Joggler screen



hashtags were checked after download
no rush

keep safe

ronnie

[proddick]

I am rebuilding a Joggler and used 5.10.176 from 23 March 2023 and that booted fine.

However, audio is bad (stutters) with the BBC Sounds plug-in, but works fine for Global, Spotify, my ripped music, etc. BBC Sounds also works fine on the SB Radio, so issue is specific to the Joggler.

Anyone got any suggestions? I believe the stream needs transcoding from the 48Khz sampling rate and I have checked that LAME is installed and the settings confirm all OK.

[fanshawe]

I am rebuilding a Joggler and used 5.10.176 from 23 March 2023 and that booted fine.

However, audio is bad (stutters) with the BBC Sounds plug-in, but works fine for Global, Spotify, my ripped music, etc. BBC Sounds also works fine on the SB Radio, so issue is specific to the Joggler.

Anyone got any suggestions? I believe the stream needs transcoding from the 48Khz sampling rate and I have checked that LAME is installed and the settings confirm all OK.

Hi - I had this exact issue and the solution for me was to set the transcoding for the joggler (see this post: viewtopic.php?p=33365#p33365). A couple of caveats though:

• I am not on the most recent Joggler build (one from the end of last year) so can't vouch for that

• I am only the Joggler's internal speaker; if you're using using something other than that you may want to increase the bit rate of the transcoding if you can hear a benefit to it

[proddick]

Hi - I had this exact issue and the solution for me was to set the transcoding for the joggler (see this post: viewtopic.php?p=33365#p33365). A couple of caveats though:

• I am not on the most recent Joggler build (one from the end of last year) so can't vouch for that

• I am only the Joggler's internal speaker; if you're using using something other than that you may want to increase the bit rate of the transcoding if you can hear a benefit to it

Thanks for the reply. I am testing with the internal speaker and found my issue this afternoon. The lame.exe file was being blocked from execution by Windows and once I fixed that all is fine. I haven't set any rate limiting and 320Kb/s is working fine from Radio 3

[proddick]

I am trying to install an "out-of-kernel" driver for the Realtek 8811CU so I can use a better, low cost USB WIFI. The instructions to install the drivers are at https://github.com/morrownr/8821cu-20210916 but I am a Linux numpty and have struggled at the first step and am hoping someone can help!

The command below fails because it can't find the headers - "Unable to locate package - linux-headers-5.10.176op". Is it possible to solve this?

Code: Select all

sudo apt install -y linux-headers-$(uname -r) build-essential bc dkms git libelf-dev rfkill iw

[proddick]

I am trying to install an "out-of-kernel" driver for the Realtek 8811CU so I can use a better, low cost USB WIFI. The instructions to install the drivers are at https://github.com/morrownr/8821cu-20210916 but I am a Linux numpty and have struggled at the first step and am hoping someone can help!

The command below fails because it can't find the headers - "Unable to locate package - linux-headers-5.10.176op". Is it possible to solve this?

Code: Select all

sudo apt install -y linux-headers-$(uname -r) build-essential bc dkms git libelf-dev rfkill iw

I found the headers at https://birdslikewires.net/download/ope ... .10.176op/ and installed them using dpkg so got past the first hurdle. Now the driver build is failing and looking at the make error I think it may be due to the Joggler being a 32 bit platform. Any thoughts?

[roobarb!]

Apologies to any folks who had issues with the last 5.10.180 build of Debian - there was a repo outage at the time the build ran which broke it.

I've removed the dodgy build and linked back to the .179 release. The .180 version should be reprocessed overnight.

BTW, I've abandoned Twitter these days, but I'm here on Mastodon if anybody needs to give me a nudge.

[pete]

Thank you Andy!!

[proddick]

I have one Joggler running 5.10.179 connected on Ethernet and (for reliability) trying to connect a second one on Ethernet too. However, the second one appears to get the same IP address from DHCP. I seem to recall an issue with non unique MAC addresses a long time ago - can anybody advise?

Looking at the Joggler the MAC addresses are as below and look odd?

ethernet - 02:0e:8e:24:d1:da
wifi - 00:0e:8e:24:d1:da

[proddick]

I have one Joggler running 5.10.179 connected on Ethernet and (for reliability) trying to connect a second one on Ethernet too. However, the second one appears to get the same IP address from DHCP. I seem to recall an issue with non unique MAC addresses a long time ago - can anybody advise?

Looking at the Joggler the MAC addresses are as below and look odd?

ethernet - 02:0e:8e:24:d1:da
wifi - 00:0e:8e:24:d1:da

I found the back story here that there is no MAC address for onboard Ethernet so an address is spoofed from the WIFI one. I still am having some issues that two Ethernet Jogglers are getting the same IP address which is weird. I may try a USB Ethernet to see if that is a workaround.

[proddick]

My journey to 5.10 really isn't going well

My latest issue is that when I try and use my USB DAC/Amp with 5.10.179 it crashes the Squeeeplayer app. Any suggestions as to what I can check - I think the unit is still alive and can probably look at logs, etc?

[proddick]

I have one Joggler running 5.10.179 connected on Ethernet and (for reliability) trying to connect a second one on Ethernet too. However, the second one appears to get the same IP address from DHCP. I seem to recall an issue with non unique MAC addresses a long time ago - can anybody advise?

Looking at the Joggler the MAC addresses are as below and look odd?

ethernet - 02:0e:8e:24:d1:da
wifi - 00:0e:8e:24:d1:da

I found the back story here that there is no MAC address for onboard Ethernet so an address is spoofed from the WIFI one. I still am having some issues that two Ethernet Jogglers are getting the same IP address which is weird. I may try a USB Ethernet to see if that is a workaround.

It appears that the network.yaml was updated with the same MAC address (02-0e-8e-24-d1-da) for the Ethernet port on both my Joggler, which is odd. Is this a bug in the current build? As a workaround I generated a random MAC and changed it in the file.

[hawsey]

I have one Joggler running 5.10.179 connected on Ethernet and (for reliability) trying to connect a second one on Ethernet too. However, the second one appears to get the same IP address from DHCP. I seem to recall an issue with non unique MAC addresses a long time ago - can anybody advise?

Looking at the Joggler the MAC addresses are as below and look odd?

ethernet - 02:0e:8e:24:d1:da
wifi - 00:0e:8e:24:d1:da

I found the back story here that there is no MAC address for onboard Ethernet so an address is spoofed from the WIFI one. I still am having some issues that two Ethernet Jogglers are getting the same IP address which is weird. I may try a USB Ethernet to see if that is a workaround.

It appears that the network.yaml was updated with the same MAC address (02-0e-8e-24-d1-da) for the Ethernet port on both my Joggler, which is odd. Is this a bug in the current build? As a workaround I generated a random MAC and changed it in the file.

@proddick does this help ? viewtopic.php?f=4&t=2301&start=20

Sent from my 2107113SG using Tapatalk