Official moOde 7.3.0 support thread

[quattr0]

Greetings,

I'm trying out the new-to-me Khadas Tone Board. Was surprised that Moode 7.3.0 nicely recognizes under MPD setup after I switched from HAT to USB. Nice touch!!!

I could play songs from NAS fine. However, when playing through Roon, I receive this error in syslog. Any idea?

Sep 2 16:34:16 moode kernel: [ 2168.689990] bcm2835-i2s fe203000.i2s: I2S SYNC error!

[TheOldPresbyope]

Greetings,

I'm trying out the new-to-me Khadas Tone Board.  Was surprised that Moode 7.3.0 nicely recognizes under MPD setup after I switched from HAT to USB. Nice touch!!!

I could play songs from NAS fine.  However, when playing through Roon, I receive this error in syslog.  Any idea?

Sep  2 16:34:16 moode kernel: [ 2168.689990] bcm2835-i2s fe203000.i2s: I2S SYNC error!

Roon and moOde are two different animals.

The implication of your question is that you have installed Roon Bridge on the host which is running moOde. I've never used Roon but it's my understanding that Roon (or Roon Remote) has to ask Roon Bridge to discover the audio devices available on the host. Since you changed audio devices you'll have to go through that discovery process again, n'cest pas?

Regards,
Kent

[quattr0]

Greetings,

I'm trying out the new-to-me Khadas Tone Board.  Was surprised that Moode 7.3.0 nicely recognizes under MPD setup after I switched from HAT to USB. Nice touch!!!

I could play songs from NAS fine.  However, when playing through Roon, I receive this error in syslog.  Any idea?

Sep  2 16:34:16 moode kernel: [ 2168.689990] bcm2835-i2s fe203000.i2s: I2S SYNC error!

Roon and moOde are two different animals.

The implication of your question is that you have installed Roon Bridge on the host which is running moOde. I've never used Roon but it's my understanding that Roon (or Roon Remote) has to ask Roon Bridge to discover the audio devices available on the host. Since you changed audio devices you'll have to go through that discovery process again, n'cest pas?

Regards,
Kent

Merci, Kent! Turns out that error is harmless according to Google.  And I didn't know Roon wanted me to select a different audio device which clearly labeled Khadas...lol instead of the existing Moode+HAT audio device that i've been using.  My bad!

[eraser1320]

I would look in your Router WLAN logs to see if there are any messages indicating why it might be rejecting the association.

Nothing is being rejected every and never has. I see in my logs during the initial wifi configuration from AP mode on the first boot, it associates just fine and wifi works normally. However after rebooting again, moOde switches into AP mode, no more association attempts to my router. Then if I plug in ethernet, moOde switches out of AP mode and associates wifi just fine. As soon as I unplug the ethernet, it switches back into AP mode. There are never any association rejection in my router logs, only successful ones.

Hello,
sometimes the simplest thing is not considered: eg. the toaster does not work: has the power been connected?
So I hope I'm not offended to ask if the option:

Menu
Configure
System
System Modifications
Wait for eth0 address

is it set to "OFF" 
Sorry for the banality and greetings,
Francesco

Totally I appreciate the back to basics advice . But I already tried that, both before and after the re-install. What about access to a dev build of 7.4.0? I don't think I have any options left .

[fdealexa]

I would look in your Router WLAN logs to see if there are any messages indicating why it might be rejecting the association.

Nothing is being rejected every and never has. I see in my logs during the initial wifi configuration from AP mode on the first boot, it associates just fine and wifi works normally. However after rebooting again, moOde switches into AP mode, no more association attempts to my router. Then if I plug in ethernet, moOde switches out of AP mode and associates wifi just fine. As soon as I unplug the ethernet, it switches back into AP mode. There are never any association rejection in my router logs, only successful ones.

Hello,
sometimes the simplest thing is not considered: eg. the toaster does not work: has the power been connected?
So I hope I'm not offended to ask if the option:

Menu
Configure
System
System Modifications
Wait for eth0 address

is it set to "OFF" 
Sorry for the banality and greetings,
Francesco

Totally I appreciate the back to basics advice . But I already tried that, both before and after the re-install. What about access to a dev build of 7.4.0? I don't think I have any options left .

Hello,
my feeling is that something is wrong with the DHCP process (assigning the default GW and DNS): why don't you try static addressing? The only advice is to be careful of the duplicate address: I can suggest using those assigned by DHCP and be sure that no one else tries to get an address in the meantime you are in test.
If successful, you can work on the DHCP server reservation later to avoid duplicating IP addresses.
Sorry for my english and best regards,
Francesco

[eraser1320]

I would look in your Router WLAN logs to see if there are any messages indicating why it might be rejecting the association.

Nothing is being rejected every and never has. I see in my logs during the initial wifi configuration from AP mode on the first boot, it associates just fine and wifi works normally. However after rebooting again, moOde switches into AP mode, no more association attempts to my router. Then if I plug in ethernet, moOde switches out of AP mode and associates wifi just fine. As soon as I unplug the ethernet, it switches back into AP mode. There are never any association rejection in my router logs, only successful ones.

Hello,
sometimes the simplest thing is not considered: eg. the toaster does not work: has the power been connected?
So I hope I'm not offended to ask if the option:

Menu
Configure
System
System Modifications
Wait for eth0 address

is it set to "OFF" 
Sorry for the banality and greetings,
Francesco

Totally I appreciate the back to basics advice . But I already tried that, both before and after the re-install. What about access to a dev build of 7.4.0? I don't think I have any options left .

Hello,
my feeling is that something is wrong with the DHCP process (assigning the default GW and DNS): why don't you try static addressing? The only advice is to be careful of the duplicate address: I can suggest using those assigned by DHCP and be sure that no one else tries to get an address in the meantime you are in test.
If successful, you can work on the DHCP server reservation later to avoid duplicating IP addresses.
Sorry for my english and best regards,
Francesco

Thanks for the suggestion, already tried static as well.

[the_bertrum]

Nothing is being rejected every and never has. I see in my logs during the initial wifi configuration from AP mode on the first boot, it associates just fine and wifi works normally. However after rebooting again, moOde switches into AP mode, no more association attempts to my router. Then if I plug in ethernet, moOde switches out of AP mode and associates wifi just fine. As soon as I unplug the ethernet, it switches back into AP mode. There are never any association rejection in my router logs, only successful ones.

Hello,
sometimes the simplest thing is not considered: eg. the toaster does not work: has the power been connected?
So I hope I'm not offended to ask if the option:

Menu
Configure
System
System Modifications
Wait for eth0 address

is it set to "OFF" 
Sorry for the banality and greetings,
Francesco

Totally I appreciate the back to basics advice . But I already tried that, both before and after the re-install. What about access to a dev build of 7.4.0? I don't think I have any options left .

Hello,
my feeling is that something is wrong with the DHCP process (assigning the default GW and DNS): why don't you try static addressing? The only advice is to be careful of the duplicate address: I can suggest using those assigned by DHCP and be sure that no one else tries to get an address in the meantime you are in test.
If successful, you can work on the DHCP server reservation later to avoid duplicating IP addresses.
Sorry for my english and best regards,
Francesco

Thanks for the suggestion, already tried static as well.

This doesn't sound like a software issue.  Either there is a configuration problem on the network, or a hardware fault on a network device.  Try putting stock RaspiOS on your device and see if the wifi works then.  If you see a similar issue, I'd begin to suspect the wifi module on the Pi is dodgy.

[TheOldPresbyope]

So I did a full reinstall with a fresh 7.3.0 image.

After going through the initial setup by connecting to the moode AP, entering in my wifi info and rebooting, it it connected to my wifi network and I was able to start the rest of my configuration. No ethernet plugged in the entire setup process.

It's a pity you didn't try rebooting several times with this initial configuration to see if it connected in WiFi client mode each time. Whether your start over with a plain RaspiOS install or with a new 7.3.0 install, be sure next time to reboot several times in your testing.

However, after doing more setup that required another reboot, the second reboot after the fresh install, I'm back to the exact same behavior as my other posts. It goes into AP mode, unless I have an ethernet cable plugged in. :-(

So what "more setup" did you do? Be specific to be terrific.

None of my multiple (re)installations of multiple releases of moOde on an RPi4B has failed during testing the way yours is. I won't have access to any other RPi models for several weeks yet but IIRC no installations failed on RPi3A and RPi3B+ models as well. Somewhere in one of the boxes currently in storage there's even an RPi3B v1.2 which I haven't used in a while.

Until we understand what's going on with your 7.3.0 player there's no point in jumping into test releases.

Regards,
Kent

[eraser1320]

So I did a full reinstall with a fresh 7.3.0 image.

After going through the initial setup by connecting to the moode AP, entering in my wifi info and rebooting, it it connected to my wifi network and I was able to start the rest of my configuration. No ethernet plugged in the entire setup process.

It's a pity you didn't try rebooting several times with this initial configuration to see if it connected in WiFi client mode each time. Whether your start over with a plain RaspiOS install or with a new 7.3.0 install, be sure next time to reboot several times in your testing.

However, after doing more setup that required another reboot, the second reboot after the fresh install, I'm back to the exact same behavior as my other posts. It goes into AP mode, unless I have an ethernet cable plugged in. :-(

So what "more setup" did you do? Be specific to be terrific.

None of my multiple (re)installations of multiple releases of moOde on an RPi4B has failed during testing the way yours is. I won't have access to any other RPi models for several weeks yet but IIRC no installations failed on RPi3A and RPi3B+ models as well. Somewhere in one of the boxes currently in storage there's even an RPi3B v1.2 which I haven't used in a while.

Until we understand what's going on with your 7.3.0 player there's no point in jumping into test releases.

Regards,
Kent

The only additional setup I did was choose my DAC. I was about to chock it up to some hardware failure, but installed Volumio in the exactly same way. Connect while in AP mode, setup wifi and reboot. It's still connected to wifi normally, DAC is setup and everything is working. I'm kind of hoping it is hardware failure and it doesn't come back up after a reboot or two, because I honestly like moOde much better.

[uteroid]

Noticed an issue playing DFF files. These are albums that I converted from SACD-ISO using iso2dsd converter. Whenever I try to play one of those I get the following error. These files worked fine before updating to 7.3.0. I tried re-installing with clean image same thing.

MPD error
Failed to open "ALSA Default" (alsa); Error opening ALSA device "_audioout"; snd_pcm_hw_params() failed: Invalid argument


I'm using Allo Digione with Coaxial connection.