Ok a reboot fixed it. Any fix coming sometime soon?
I dunno. I’m preparing another update (probably this weekend) with an updated kernel, but I’m definitely not sure if this fixes the issue. I see reports from others that are months old. So…
Hi,
I’ve pushed out another beta release (2024.03.93) which fixes the ‘last’ Pi 5 issues and brings an updated kernel.
This latter is related to one thing remaining in this release: a sporadic ‘black screen’. It is unclear to me when it happens or what triggers it, but it is kernel related. Let’s see what this update brings.
Have a great weekend!
Regards, Harry
5 Likes
The most recent Beta is refusing to complete installation. Looks like it’s stuck at “Wrapping up”. This is a Pi4 with no display.
Have you tried going back to the webpage your self?
All three units updated and working fine here.
Two RPi4s are on RoPieee 2024.03.93 (1540) [beta]. Kernel version: 6.6.25-SPCKFSH-v8+
One RPi3B is on RoPieee 2024.03.93 (1539) [beta]. Kernel version: 6.6.25-SPCKFSH-v7+
Unit 1
- Hardware: Raspberry Pi 4 Model B Rev 1.5
- Network: ethernet
- Audio: USB Inmotion Air
- Display: No
- Remote: No
Unit 2
- Hardware: Raspberry Pi 4 Model B Rev 1.5
- Network: ethernet
- Audio: USB to Schiit Fulla/UE boom 2
- Display: No
- Remote: No
Unit 3
- Hardware: Raspberry Pi 3 Model B Rev 1.2
- Network: ethernet
- Audio: digi+ pro hat optical and coax to KEF LS50W and Schiit Yggdrasil
- Display: Yes
- Remote: OSMC
1 Like
Yes. I have two other Pis on main release and they show up. The Beta Pi doesn’t show up. Is it possible the WiFi got broken by the update?
No it shouldn’t. But have tried accessing it in a new browser window/tab?
It’s not listed on my router anymore so it’s no longer on the network. This is odd because I’ve never had an update issue in about six years with Ropieee. I’ve also updated this Beta just fine every time until now.
Is it acting like an AP?
This should be visible because there should be an wifi network named ‘RoPieee-xxxxx’
Okay, I’m not sure what you’re asking me but I did a hard reboot (pulled the power) on the Pi, it rebooted, found the network and now appears to be working with the current Beta. I’m not sure what was going on, but as soon as I saw it was back on the network I opened the browser page and it had Ropieee logo in gray and said it was finishing up. Now it works fine. Hard to tell without a display but it appears it got hung up on one of the reboots. Do you want feedback now that it’s back on line?
Yes, please.
Harry, one interesting aspect from the latest update is that the two beta units (when accessing the web gui to perform the update) had pre-filled new values for the host name and time zone. As an experiment I agreed to configure… the host name was reset to ropieee after the update. Easy to set the values again, but not the normal update behaviour.
Screen shot is from a production RoPieee which seems to have the same issue in my environment. Host name is the MAC value from the Advanced screen of course and the time zone the first option in the drop down.
Sorry for the delay. I got to listening to music and forgot to send this on. Here’s the feedback.
5f622707ed3dc120
1 Like
Hi Nathan,
This beta has indeed had some changes to the web ui.
The previous stable version had an issue, hence you saw some fields filled with the ‘ZgotmplZ’ value.
But to get things clear:
The image is from a stable production version, right? It shows that the hostname is not properly set. Correct?
So what exactly happened? You say that the hostname was reset to ropieee after you hit configure, but was the
for hostname also ‘ropieee’?
Thanks
Yes, correct, the image is from a stable unit. The two beta unit looked the same, but I didn’t save the screenshot for some reason.
At present, all 5 stable units show the initial System tab has having the same new values and needing to be “configured”.
On the beta units, I hit “configure”, rebooted, and then hit “update”. The overall sequence is something like:
Original values
- Hostname: CavePi
- Timezone: America/Vancouver
Sequence
- Go to web gui after announcement of new beta version.
- Initial load of web gui (eg I dismiss the first splash screen that shows once)
- System tab is filled with new values. Option is “Configure”, not “Update”
- Hostname: ZgotmplZ
- Timezone: Africa/Abidjan
- Hit “Configure” and reboot.
- Hit “Update”. I did not notice whether the hostname changed or not, or what the value was.
- Update process completes
- Hostname: ropieee
- Timezone: Africa/Abidjan
So, can we conclude that, already in the previous beta build:
Although your hostname was ‘CavePi’ and the timezone ‘America/Vancouver’, it was wrongly displayed?
You corrected that in the interface, ran ‘configure’, reboot and then updated the unit.
Went back to the interface, which properly showed the settings.
Something like this?
No, I corrected after the update. I wanted to see exactly what would happen.
For the 5 stable units that currently display the “wrong” values, should I correct now?
Well, I’m not entirely sure, but I suspect there’s a bug in the current stable version that causes this. The beta fixes that, but the ‘wrong’ values mean actually ‘emtpy’ values.
RoPieee 2024.03.93 (1540)
Hardware: Raspberry Pi 4 Model B Rev 1.4; 16GB disk
Network: wired ethernet
Audio: USB DAC — Roon
Audio: USB DAC — Squeezelite
Display: no
Remote: Flirc
1 Like