Solved: Volumio3 not obtaining IP address

Have been using Volumio for years on a Raspberry Pi 2b and decided to try it on a new RaspberryPi 4 64bit. Followed in installation instructions and once booted I can see the “Volumio” hotspot but when trying to connect to it, it is stuck while obtaining IP address.

Any idea how to solve this issue?

Welcome @galsegal, best advice is to follow the guide:

https://volumio.github.io/docs/User_Manual/Quick_Start_Guide.html

Sometimes a power off, power on helps if the hotspot is not working. The hotspot password is volumio2.

Good luck.
Simon

Thanks, tried it multiple times, same result…
Also tried with the ethernet cable attached. Hotspot was not created (expected) but the UI was not loaded after 10 minutes.

Weird. You can see the hotspot though? Maybe some bad sectors on your SD. Do you have an extra one you could try? Or lack of power, did you get a new power supply for your pi4?
Edit: just checking, you did unzip the image before flashing it?

Used a fresh 32Gb SD card.
When trying to flash the unzipped version (I am using Macbook Pro and Etcher Balena), Etcher is complaining about that the image might be corrupted. It works fine with the zipped version. After flashing this is what I see on the SD card:

ls -l /Volumes/boot/
total 103200
-rwxrwxrwx  1      25426 Dec 20 16:02 bcm2708-rpi-b-plus.dtb
-rwxrwxrwx  1      24774 Dec 20 16:02 bcm2708-rpi-b-rev1.dtb
-rwxrwxrwx  1      25163 Dec 20 16:02 bcm2708-rpi-b.dtb
-rwxrwxrwx  1      24896 Dec 20 16:02 bcm2708-rpi-cm.dtb
-rwxrwxrwx  1      26101 Dec 20 16:02 bcm2708-rpi-zero-w.dtb
-rwxrwxrwx  1      24908 Dec 20 16:02 bcm2708-rpi-zero.dtb
-rwxrwxrwx  1      26301 Dec 20 16:02 bcm2709-rpi-2-b.dtb
-rwxrwxrwx  1      26450 Dec 20 16:02 bcm2710-rpi-2-b.dtb
-rwxrwxrwx  1      28567 Dec 20 16:02 bcm2710-rpi-3-b-plus.dtb
-rwxrwxrwx  1      27948 Dec 20 16:02 bcm2710-rpi-3-b.dtb
-rwxrwxrwx  1      26257 Dec 20 16:02 bcm2710-rpi-cm3.dtb
-rwxrwxrwx  1      47484 Dec 20 16:02 bcm2711-rpi-4-b.dtb
-rwxrwxrwx  1      47657 Dec 20 16:02 bcm2711-rpi-400.dtb
-rwxrwxrwx  1      47593 Dec 20 16:02 bcm2711-rpi-cm4.dtb
-rwxrwxrwx  1      52456 Dec 20 16:02 bootcode.bin
-rwxrwxrwx  1        385 Dec 20 16:04 cmdline.txt
-rwxrwxrwx  1        189 Dec 20 16:04 config.txt
-rwxrwxrwx  1       7301 Dec 20 16:02 fixup.dat
-rwxrwxrwx  1       5429 Dec 20 16:02 fixup4.dat
-rwxrwxrwx  1       3176 Dec 20 16:02 fixup4cd.dat
-rwxrwxrwx  1       8440 Dec 20 16:02 fixup4db.dat
-rwxrwxrwx  1       8436 Dec 20 16:02 fixup4x.dat
-rwxrwxrwx  1       3176 Dec 20 16:02 fixup_cd.dat
-rwxrwxrwx  1      10288 Dec 20 16:02 fixup_db.dat
-rwxrwxrwx  1      10288 Dec 20 16:02 fixup_x.dat
-rwxrwxrwx  1    5456128 Dec 20 16:02 kernel.img
-rwxrwxrwx  1    5787640 Dec 20 16:02 kernel7.img
-rwxrwxrwx  1    6146456 Dec 20 16:02 kernel7l.img
drwxrwxrwx  1      18432 Dec 20 16:02 overlays
-rwxrwxrwx  1          0 Dec 20 16:04 resize-volumio-datapart
-rwxrwxrwx  1    2940128 Dec 20 16:02 start.elf
-rwxrwxrwx  1    2215776 Dec 20 16:02 start4.elf
-rwxrwxrwx  1     791356 Dec 20 16:02 start4cd.elf
-rwxrwxrwx  1    3716808 Dec 20 16:02 start4db.elf
-rwxrwxrwx  1    2975368 Dec 20 16:02 start4x.elf
-rwxrwxrwx  1     791356 Dec 20 16:02 start_cd.elf
-rwxrwxrwx  1    4788712 Dec 20 16:02 start_db.elf
-rwxrwxrwx  1    3698952 Dec 20 16:02 start_x.elf
-rwxrwxrwx  1   12890158 Dec 20 16:08 volumio.initrd
-rwxrwxrwx  1      38405 Dec 20 15:57 volumio.png

There have been several reports of problems involving Pi images and Etcher. Please try Raspberry Pi Imager. https://www.raspberrypi.com/software/

Thanks you so much @SimonE, Works like a charm!
I wasn’t aware of this issue. I used RaspberryPi Imager, flash the latest volumio version 3.179. After a few minutes the hotspot was available, and once I connected to it, I received the IP address quickly and could run the initial wizard.

Thanks for bringing back music to my life :wink:

Yeah I think @volumio should stop advertise Etcher in their instructions as it causes for a lot of issues lately.
They should opt for either Raspberry Pi Imager or Win32DiskImager
image

Couldn’t agree more. I am using Volumio for years (since v1) and used Etcher as suggested many times.
This is the first time I encounter this problem.
@volumio using Etcher might cause a bad and frustrating onboarding experience.
I also started to think about buying a device for streaming, and that experience prevented me from choosing Primo.