Raspberry Pi troubleshooting and configuration instructions for complete f'ing morons

Yo dudes,

I was trying to update my Mercury V2 with the latest Volumio config that allows Qobus connect. Mike from Pi2AES was VERY kind to make an update config for the V2.

After downloaded the config and flashed it onto my SD card with Etcher.

When I put the card in and turned on the V2 I am not seeing it on the network any more

I looked for a local Volumio wifi hotspot as if it was the first setup and no luck...

Any advice or point me in the right direction?

Trying to revive the Mercury V2 so I can enjoy some music

 

Always, always, always make sure you check the box for validation after flashing with Etcher. Many times I have to wipe the SD card of all the partitions, write one big exFat, and then flash again. Sometimes flashing over top of an already written two and working SD throws it off somehow and fails. It happens to me a bunch. It is nice to have a Linux box to do all the partioning.

 

what I posted for this was a complete image that is designed to overwrite everything on the card. I use either BALENA or the raspberry pie official flashing tool. Both of those seem to do OK with an already programmed card. I've not used etcher so I'm not sure how it works

 

Thank you guys! I checked and I did use BalenaEtcher.

I will give it a flash again tomorrow when I have some time to troubleshoot.

 

Check with volumio to make sure you don’t need to use the official raspberry pi installer as afaik balena doesn’t let you set environment info they now want (like wifi details and ssh credentials).

 

BalenaEtcher is simply the updated name for the software formerly known as Etcher. It's not a separate or different tool. If anyone here is still using Etcher, then you are using old software that was not updated since 2023. I guess I still just refer to it as its old name.

Normally I do not have issues, but sometimes I do. That is why I like to run the verify tool after flashing. Never had one not work after verifying.

 

appreciate everyone’s help and tips!

I reflash the SD card today and I was able to get everything working!

I did have to ‘add new device’ in the Volumio app. Then connect to my network again. Then all good!

 

Has anyone tried the latest version of MoOde on an RPI? I flashed it according to the website's new instructions which have new flashing procedures you have to do with the official Raspberry Pi flashing software, and got the .local site to load on my computer, and entered my wifi and password into the mode setings at .local but it won't show up using wifi, it only shows up when connected to ethernet directly.

I don't understand why Holo managed to make a rock solid streaming software while they are not even a software company and meanwhile Volumio, RopieeXL, MoOde are exclusiveliy RPI software companies and their software is buggy beyond belief. the RED has never, not once stopped working on me in like 8 months. Every Pi2AES or RPI I have stops working very frequently no matter whichof those 3 I use. I just don't quite get it.

 

I haven't updated to the latest, but I've been solid on 2 pi2aes on pi4s for a year now probably with no issues. I've been meaning to update but it requires a fresh flash since they changed over to bookworm or new kernel or whatever I think it is ?

 

hmm... I've run multiple Rpi based streamers for years at this point (albeit, all as roon endpoints using Ropiee)... they never give me a hiccup, they just run.

 

For a couple of reasons. First off, Tim (moOde), is a one man show. He does what he can, and he has a few volunteers helping him compile tant test. Most of the stuff on there is compiled from off the shelf free stuff with free licenses. Although he did design the look and feel of the UI. Red OS on the other hand was compiled by staff engineers and also very light. Compared to other OS's like moOde, Volumio, Gentooplayer, etc. it is very light. Ropiee is the only other one that is almost as light.

You should just configure your Wifi settings before you flash. Follow my instructions.

 

@rhythmdevils which model of RPi? I am a moOde contributor and it’s been very reliable for me. Although as of late the venerable RPi2 has WiFi Linux driver weirdness.

 

It's an RPI 4. Brand new. I'll try @Azimuth 's tutorial, i went back to Ropiee and it's at least being seen through Wifi now.

I'm having another issue though. I'm trying to play from a plain RPI 4 USB out to an Intona 3 Isolator, and UPNP is giving me all kinds of issues. The JDS Synapse worked fine but the RPI software or something seems to be having a hard time with the Intona. Like it can't see it or it draws too much power (though I tried plugging it in via the micro usb port and it didn't help).

Sometimes it will play a song and then stop and not finish the album. But usually in BubbleUPNP the dot representing the current time in the track and the time both just start blinking and it stays at zero and won't play.

But a lot of people must play RPI's USB out to Intona isolators. I've got the settings in Ropiee like this.

Any ideas?

 

With what are you powering the RPi? You want to ensure it’s got at least as much power as the official one.

You can check whether the USB bus is undervolting by entering “sudo dmesg” in the terminal.

 

I'm using this power supply made for the RPI

So that should be right.

I'm doing a pretty unusual thing here.

i'm basicalliy making a desktop DAC using iBasso dongles. It might seem silly, but i started adding components to the DC-07 Pro to boost it's performance ans was really surprised at the results and have just kept going. Honestly, it's comparable to a high end DAC once you add a good power supply and clean USB. I hope to post about it soon.

So i've got an RPI with Roipiee XL right now
feeding the Intona USB 3 superspeed isolator
with the CB19 cable splitting power and data signal, and the data cable going to the Intona
And the powwer ccable being fed by a Sigma 11 LPS

So maybe the RPI is having troube with the dongles somehow, I'm not sure how audio works out of the RPI, if it needs to "communicate" wtth the device and maybe that's the issue

i know, it seems crazy, but you should hear the results. Raises a lot of questions and eyebrows for me (like maybe 5 eyebrows)

 

Reminds me of the time i added an Sbooster psu to an Apogee Groove and really liked the results.