Any chance that your router has assigned a different IP address to the wireless connection?
Thanks for the suggestion but I have already checked te router and it looks like there is no connection being made
Hey @Newbiggen,
Your log shows classic Single Network Mode behavior - eth0 is UP with IP 192.168.1.116, while wlan0 is UP but not associated (ESSID:off/any, no IP). This is expected when ethernet takes priority.
There is no issue:
Volumio allows only ONE active network interface at a time. While eth0 is UP (even without cable physically connected), WiFi cannot connect to any access point - this is by design.
Since you already have WiFi configured:
- Shutdown Volumio completely (not just reboot)
- Unplug the ethernet cable
- Power on Volumio
With no ethernet connection at boot, wlan0 will be the active interface and will connect to your configured WiFi network.
Why this works:
Your log proves wlan0 is fully functional - it has valid MAC address (dc:a6:32:f2:72:89), proper IEEE 802.11 capabilities, and you confirmed it worked after fresh install. The problem is purely Single Network Mode state management blocking wlan0 while eth0 remains UP.
Kind Regards,
My web radios with pls urls. at least from SomaFM, are causing MPD to crash or die. I see log entries about restarting MPD, and sometimes that works. Other times, I need to manually restart the volumio service. A couple example urls:
https://somafm.com/thistle130.pls
Creating a web radio using the individual urls from the pls file works fine. These pls urls all worked in Volumio 3.
Version 4.071 on a Raspberry PI 4 with a USB hard disk attached.
Logs: http://logs.volumio.org/volumio/ZoTC0p0.html
Thank you for your reply, but there is still a problem!
I have tried again with a complete reinstall of v 4.071
Raspberry Pi 4 Model B
SD card - v 4.071
Onboard WiFi
This is the log after logging on for the first time via wireless
http://logs.volumio.org/volumio/sfJBSi5.html
I then shut down completely, then rebooted via ethernet
http://logs.volumio.org/volumio/Oo25bDY.html
Next I shut down completely again and tried to logon again with WiFi - Nothing !
I am, however able to logon still with a wired connection
It looks like the Single Network Mode management is failing to switch the WiFi back on when there is no ethernet present
I have just found that if I boot via ethernet then pull the plug on the ethernet volumio will switch back to wireless. When I put the ethernet plug back in it switches to a wired connection - allās well there then, but if I try now to reboot now it will ony work if I reconnect the ethernet
Have you any further ideas please?.
1 Like
Hi all,
Iām afraid I have to join as I have the same problem connecting to wifi.
Raspberry Pi 3b with v4.071.
As long as I use the wired connection everything runs as expected. As soon as I switch to wireless (shutdown - unplug - boot) nothing happens. No connection to my wifi and no hotspot.
Log: http://logs.volumio.org/volumio/H1j7leZ.html
Thx
petjek
Hi - try booting with wired connection, then unplug the ethernet connection without shutting down - I have found that at this point it will switch to wireless connection [you will probably have to remake the connection from your laptop/phone etc by logging in again to volumio.local or whatever]. You can now shut down. The next time you login it should work with the wireless connection.
This is is not an ideal situation but a workaround until it is sorted out ā¦
Hope this is of help
It did! Thank you for the quick response.
I pleased it work for you. Iām surprised that this issue hasnāt been raised by more users. Just be aware that if you login with a wired connection again you will have to adopt the same procedure if you want to use a wireless login next time
Just for what itās worth, this procedure doesnāt work for me when using a Raspberry Pi 3B+. I have had similar experiences with wifi, posted earlier in this thread.
@Newbiggen I did have exactly the same issue you describe (Raspberry Pi4 , volumio 4.071).
To solve that problem on my system I had to add vers=2.1,noserverino in the āOptionsā field.
Hardware: Fujitsu Futro S720 ThinClient AMD GX-217GA 1,65 GHz 8GB RAM, mSATA SSD 4GB
Wired LAN
Audio: Nvarcher SA9123L USB ā SPDIF and I2S 24BIT 192K
When do you think there will be a mainstream release? for the wifi dongle fix?
Unfortunately i have no information.
Album art differences between versions 3.874 and 4.071
I have my music stored on a NAS, and I have versions 3.874 and 4.071 running on devices pointing at the relevant NFS mount on that NAS.
āWeb album artā is turned off on both devices. On the device running v3.874, all the album art is fetched. On the device running v4.071, not all album art is fetched. On the NAS, permissions are the same for all folders and files in the music directory tree.
Iāve identified a few issues where the file tags werenāt āstrictā enough; remedying these and resetting the album art cache on the device running v4.071 successfully fetched the corresponding album art.
Doing a complete new install of v4.071 and re-scanning the NAS results in exactly the same album art not being fetched. This suggests thereās something awry with the way some files are tagged, which in turn suggests that the problem is at my end and not related to the Volumio software.
But ā¦ there are some albums where I cannot see whatās amiss with the file tags. I even tried ripping a couple of albums using a different ripper and checking the tags using a different tag editor.
Music on my NAS is stored thus: /mnt/share/nfs/music/{artist}/{album}. Every album folder contains an album art file named either cover.jpg or folder.jpg.
v4.071:
Raspberry Pi 4 Model B Rev 1.4
Revision: d03114
Log link: http://logs.volumio.org/volumio/4BEFouk.html
v3.874:
Raspberry Pi 3 Model B Plus Rev 1.3
Revision: a020d3
Log link:http://logs.volumio.org/volumio/lOin2kM.html
Just re-reading the Volumio4 announcementā¦ It took me a long time to migrate from V2 to V4, primarily a HDMI screen issue - fixed thanks to this post. I appreciate the reasons why such a major change couldnāt happen automatically. Are there instructions how the ālast 100ā tracks played, and āmy web radiosā, and other āfavoritesā can be migrated from V2 to V4? Actually too late for me, but such a post couldāve saved me some time, so maybe of use to others? The startup time running a RPi3B+ is agonisingly longer too, gone from 30ā¦45s to 175s - see 2018 post - is that expected? I could scrap the 3B+ & buy an RPi4B but the former already has a HAT attached, precluding a heatsink, and there could also be insufficient current issues if I moved to the latter. How memory dependent is the startup time - is the 2GB option going to reduce startup much over the 1GB options for the RPi4B? Too many questions sorry but thanks for any suggestions.
You definitely will also require a new power supply with at least 3A if you want to use a PI4
More than 2MB RAM wonāt help reducing the startup time
Best Regards
Hi,
Volumio V4 will take longer to boot on a Raspberry Pi 3. This is due to Bookworm, which introduces newer software and packages that add overhead on older hardware.
Without more details, itās hard to confirm whether your HAT is fully compatible with Bookworm. Could you share which HAT youāre using? (Whether itās on a Pi 3 or Pi 4 shouldnāt make much difference, though you may need a GPIO extender to raise the HAT above the fan.)
Hereās an overview of Raspberry Pi memory options:
The price difference between the Pi 4 1GB and 8GB models is typically around ā¬30ā50. Keep in mind that more memory wonāt reduce boot time, thatās better improved with a USB thumb drive or SSD. Extra memory will, however, make the Pi run faster overall.
Thanks Josh2000 & Wheaten for your generous replies. My own-built very specific player hardware precludes any change to the power supply (or Iām not prepared to make those changes because it also incorporates a 18650x2 battery UPS for clean shutdown). I will investigate the faster SD card & report my findings. The boot timing was using a SanDisk Ultra XDHC I A1. After reviewing a couple of Volumio posts on SD card timings, Iāll buy a Samsung 64GB EVO Plus 2 today. The HAT is the HifiBerry DAC Plus. Thanks once again.
I swapped from a SanDisk Ultra XDHC to a Samsung EVO Plus 2 SD card - it appears in reviews to be one of the fastest around - sadly no change at all to the time from boot to 1st item played via AutoStart, or maybe even a few seconds slower. Unexpected result?