New ropieee build on rpi4 rebooting over and over again

Audio Gear Talk RoPieee
1

Hi @spockfish

I haven’t been using my pi2AES as a Ropieee for a while (I misguidedly had it on Volumio because I’d bought some Wyse thin clients and wanted consistency). Unfortunately when u tried to run a fresh install it gets to config and boots but then it reboots over and over again.

Not sure if I’ve done something wrong - I’ve tried reflashing a couple times.

Here’s feedback - I managed to get it in the middle of a reboot cycle by very quick timing!

ce5f4e931bd72265

Thanks Harry!

2

2 things:

You have enabled auto reboot.

On top of that something is wrong with the internet connection, it comes alive with a rather large delay.

When that happens the unit thinks it’s time to auto reboot, and there you go.

Boot the unit up and try to disable auto reboot. After that we can figure out why the internet connection comes up so slowly.

Thanks

3

Well thank you!

Ok, reflashed, turned off auto reboot, and didn’t configure any services (other than Roon bridge). It is true that it is slow to get an Internet connection, and doesn’t seem to be getting ntp sync. Not sure if that’s true for the volumio I had running on the same hardware.

Now I can’t get Roon to see the device - Not sure if that’s related. I tried reinserting the Volumio SD card and all is working there.

Updated feedback: 299272ecd56cb990

Thank you Harry as always!

John

4

I know what’s going on on your unit. I’ll prepare a beta build to address it. I’ll keep you posted.

5

Well that is mighty kind, thank you Harry!

Is there a layman’s version of what’s going on? Hardware out of date? Some weird thing about RPi4+Pi2AES?

Best,
John

6

Yeah, there is. An issue introduced by me :wink:

In the previous release I re-enabled ipv6. You have a router that supports that, so your RoPieee unit gets both an ipv4 and ipv6 address. Nerd stuff :wink: However… with your unit the ipv6 configuration is finished a little bit earlier than the ipv4. And RoPieee’s ‘wait for a working internet connection’ was/is not as robust with ipv6 as with ipv4. Hence, your unit thinks it has a connection (but hasn’t yet), continues, but is then also not capable of fetching the Roon stuff (which it fetches the first time after an installation).

So what’s next? Change to the ‘beta’ update channel on the ‘advanced’ tab. Configure, reboot and let your unit ‘sit’ for a few hours. After a few hours you will see a notification stating that an update is available. Install as usual, and your unit will be up and running again (including the Roon stuff, it will repair this automatically).

Thanks

1 Like