How To Update rAudio-1 #479
Replies: 6 comments 15 replies
-
|
I'm updating my installation applying 'pacman -Syu' almost daily. No problems so far. |
Beta Was this translation helpful? Give feedback.
-
|
I ran the pacman update and ended up with one problem. The Radio Paradise radio links don't work. The radio links included with the distro are the only radio links I have. Everything else seems to be OK. There was a question about installing Jack2 that I relied yes to. Don't know if that has anything to do with the problem. |
Beta Was this translation helpful? Give feedback.
-
|
I setup a log file for mpd and the telling portion of the error was: Turns out my system date was about 10 days behind. I installed the ntp package and ran ntpdate. Started working just fine. Now I'll need to figure out my approach to maintaining system time. |
Beta Was this translation helpful? Give feedback.
-
|
@teslasparks301 This bug does not appear to affect everyone, and might be because systemd does not see the network. Just out of interest, are you using Ethernet or wifi? |
Beta Was this translation helpful? Give feedback.
-
|
I have never heard of systemd-timesyncd. I checked them both and both were already enabled though timesync looks like it hung on Aug 8 which is the date my system time was showing before resetting it. networkd just brings up the network which, of course, is needed to connect to a time server. It's really just a supporting service to set time while timesyncd does the actual work. I'm not sure why systemd needs to set time. There already were tools for that. It's really turned into Frankenstein's monster. I started linux with kernel 1.1.13. It's hard to keep up with the changes after learning how to manage the system. And don't even get me started on the revamp of resolv.conf. I installed fake-hwclock and ntp, changed /etc/ntp.conf to use my regional ntp pool, and enabled the two of services. I think I'll be disabling systemd-timesyncd. I have probably ensured future headaches for myself when I do a reinstall or update. hahaha BTW, my network connection is wifi. Since rAudio runs headless, I would have noticed not being able to connect to snapcast, ssh, or the web interface. We've really drifted off-topic but I enjoy the conversation. :) |
Beta Was this translation helpful? Give feedback.
-
|
@teslasparks301 As @klassikmann does not have the problem, I suspect it is just wifi users who are affected. That would explain why the time was correct immediately after my fresh install made with a wire connection, but drifted once I went back to wifi. Unfortunately, there is no good way to poll users about their setups. I would not mind at all if @rern incorporated this option in the OS. Your report has linked both of my current bug reports, one for wrong time and the other the Radio Paradise problem. It did not occur to me that the time being out of sync would affect the updates. |
Beta Was this translation helpful? Give feedback.
-
|
I haven't dug very deep into Paradise problem but from what I can tell curl would not handshake with the security certificate because the system time and actual time differential was too great. So I don't think there is an actual problem with Paradise but just system time. I ran a pacman -Syu and rebooted the box. When I ssh connected to the rpi again I systime was about 2 minutes slow. 3-5 minutes later it was within a couple of milliseconds. To summarize, I have ntpd, fake-hwclock, and systemd-timesyncd.service all working and so far seems to be OK. At no time did I use anything but wifi. |
Beta Was this translation helpful? Give feedback.
-
|
From what I read, the time and date problem was caused by a systemd update. Hopefully it will be fixed by another update. So far, I find that entering |
Beta Was this translation helpful? Give feedback.
-
|
After a quick look at systemd-timesyncd.service, systemd-networkd.service, and a couple of other service files plus the man page timesyncd my guess is that timesyncd is trying to run before networkd is done setting up your wifi. I found no dependencies between the 2. CAUTION!! Rant Ahead! Just because I didn't see them doesn't mean there not there. systemd is a huge steaming pile of Borg-ish code with it's little fingers invading so much of the administrative code for no good reason that I can understand. fake-hwclock, ntpdate, and ntpd were already well established and can do a better job. The timesyncd man page hints at that. But that's just me. In the interest of brevity, I won't tell you how I really feel. ;) Rant Off! The short story is try making sure wifi is established before timesyncd runs and see if that works. I would add a dependency to systemd.timesyncd.service. That's essentially what you are doing with the restarts. And/Or, just for fun, try a static address instead of DHCP on your wifi. The interface up time will be faster using a static address. |
Beta Was this translation helpful? Give feedback.
-
|
@teslasparks301 It looks to me as if the files in /etc/systemd/network/ tell systemd-networkd what interfaces are valid, and the wifi one is missing. Just having one file with Name=* in it is probably all that is needed, but someone decided to complicate things and forgot to include wifi interfaces. Try my possible fix in #472 and see if it works for you too. It would be good to have confirmation or otherwise, and there doesn't seem to be many of us using wifi. |
Beta Was this translation helpful? Give feedback.
-
|
I shutdown my box and let it sit for about an hour. When I booted my system time was about 1 hour slow. That was to be expected since it was set via fake-hwclock. In about 5 min ntpd had me within several milliseconds of true time. I checked the status of timesyncd and found it still wasn't running. I applied the fix suggested in #472 and redid the shutdown, wait, and boot. Time was within several milliseconds as soon as it booted because timesyncd (which could be done by ntpdate) was running. The fix worked for timesyncd. I decided to disable timesyncd and go with fake-hwclock and ntpd. I don't know if that will cause a problem after a prolonged shutdown, say a few weeks or more, but that's the route I'm going for now. There is more than one way to do it (TIMTOWTDI - the motto of Perl - pronounced 'Tim toady'). |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Trying to update ArchLinux on my RP3, but it does not seem to work: RP3DAC:~ # sudo pacman -Syu Am I doing something wrong? BN PS: Same in RP4 rAudio e6 |
Beta Was this translation helpful? Give feedback.
-
|
Ok, that is very good news. So the new image supports both RP3 and RP4? |
Beta Was this translation helpful? Give feedback.
-
Yes. |
Beta Was this translation helpful? Give feedback.
-
|
To properly format as code or file content:
Please edit your post. |
Beta Was this translation helpful? Give feedback.
-
|
Done. The '#' invoked some unexpected control codes, sorry. |
Beta Was this translation helpful? Give feedback.
-
|
I have now updated rAudio ArchLinux without problems. BN |
Beta Was this translation helpful? Give feedback.
-
Is it safe to run 'pacman -Syu'? Or should all updates be done strictly through the Add-Ons page of the web gui?
Beta Was this translation helpful? Give feedback.
All reactions