The Beta Channel: what's cooking? Now at 4.019 (2021/11/13)

There is no difference between XL and ‘regular’, except additional sevices.

So here’s the simple rule for making the choice:

“Are you doing Roon only? Choose Regular”

So, with this beta the wireless stuff has been significantly written. First question: can you select the wifi dongle in the ‘Interface’ drop down?

Cool, I’ll keep the XL version then so I have Apple Play.

Yes, I can select the device under the drop down and select it and set up wifi. But only after the Pi’s are booted I can insert the dongle. If I boot or reboot with the TP-Link dongles inserted, I can’t access the Pi anymore through the web interface (.local), or any other way.

Both models will show as TP-Link.

You should, if you keep the cable connected.

So if you configure the dongle, keep it inserted AND the cable as well.

In that scenario you should be able to reach the unit (ethernet) and you can send me feedback.

I meant any other way but Ethernet, lol. I’ll get back to you. Ethernet is far away from the audio…

I think I have to bring the USB DAC with me… My Pi 3B+ wouldn’t come up online through the .local URL after I had setup the TP-Link as the wifi interface… Not sure if I messed up the network settings, it won’t work anymore. I had to use a backup SD card to get it back working.

I’ll investigate more this week…

@spockfish I’m on beta and get this. I wanted to post before unplugging and restarting.

Logs have been sent to RoPieee HQ with unique identifier be8b647c7218bcf1

Just reboot

I did, thanks.

2.637 (2020/11/08)

With the latest Pi 4 revision the way the USB controller firmware is flashed, has changed.
So this build is about fixing that.

I’m thinking about doing this firmware step automatically during installation, but that’s for later.

update 2.637 working on both Pi4 B rev 1.2 an rev 1.4. On the rev 1.4 it doesn’t show the USB FW Version under the information tab

Can you send feedback?

Logs have been sent to RoPieee HQ with unique identifier 0ea1287fcf1a2fd2

Ok, it seems your unit gives a faulty CPU revision code, hence it’s not detected as a Pi 4.
That’s why it’s not showing the firmware field.

Have you overclocked stuff or something like that or is this board very new?

it’s running stock with a HifiBerry Digi+ Pro HAT. I bought this Pi about one month ago from PiHut so might be ‘very new’.

Hmmm. weird. It’s CPU indicator is not known in Raspberry Pi’s database.
I’ll keep a close look, but only add it when it pops up in the Pi database.

2.638 (2020/11/09)

  • another kernel update
  • rewritten service discovery part in the web interface (again. sigh.) This is largely initiated from the idea that you can trigger updates on remote units from the ‘devices’ tab.

I’m still not entirely satisfied with the new kernel. If that’s settled we can release.

2 Likes

Cool…can you kick them all off in one go?

No not right now. This is just prepatory stuff to be able to such a thing in the future.

3 Likes

Am I the only one where RPi3 with DigiOne Signature HAT is not booting with the current beta firmwares (e.g. todays 2.641 [beta])?
Tried it last weekend and today again and RPi hangs on reboot. On stable firmware all is working.

2.643 (2020/11/17)

Another round of kernel updates and some finetuning on the web ui.
Hopefully this is it. If everything runs fine for the coming days we’re getting very close to a release.

1 Like