Soo.. it turned out to be a really dumb error.. unstable power.
I found in the output of 'dmesg' a line saying 'Under-voltage detected! (0x00050005)'.
Just used a different USB cable and now it worked!
It's almost embarrasing, but as I had been trying two different supplies (one labeled with up to 8A) with a short USB cable, and power via the i2s rail as well I hadn't thought about that. So powering via the Mamboberry might was unstable and the cable was not good enough.
I don't understand why Volumio had been working and why configuring the wifi triggered that kind of problem. And why the output of the command 'moodeutl -l' stops after the System section (ok, next part is the network part, but I would have thought that reporting still would continue even if something went wrong - or showing some error).
But it seems save to say, if you are running in curious problems you should connect via ssh, execute 'dmesg' and have a look for an error regarding voltage..
Thanks for trying to help me out!
I'm happy now
I found in the output of 'dmesg' a line saying 'Under-voltage detected! (0x00050005)'.
Just used a different USB cable and now it worked!
It's almost embarrasing, but as I had been trying two different supplies (one labeled with up to 8A) with a short USB cable, and power via the i2s rail as well I hadn't thought about that. So powering via the Mamboberry might was unstable and the cable was not good enough.
I don't understand why Volumio had been working and why configuring the wifi triggered that kind of problem. And why the output of the command 'moodeutl -l' stops after the System section (ok, next part is the network part, but I would have thought that reporting still would continue even if something went wrong - or showing some error).
But it seems save to say, if you are running in curious problems you should connect via ssh, execute 'dmesg' and have a look for an error regarding voltage..
Thanks for trying to help me out!
I'm happy now
