Upcoming moOde 9.0.0 (Bookworm)

[Tim Curtis]

Revert to the integrated adapter
Reboot
Plug in the USB adapter
Post the output from the command below

Code:

ifconfig

[nosferatu_cat]

Revert to the integrated adapter
Reboot
Plug in the USB adapter
Post the output from the command below

Code:

ifconfig

Code:

admin@MoodeBoss:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
       ether dc:a6:32:12:c6:0b  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
       inet 127.0.0.1  netmask 255.0.0.0
       inet6 ::1  prefixlen 128  scopeid 0x10<host>
       loop  txqueuelen 1000  (Local Loopback)
       RX packets 302  bytes 34787 (33.9 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 302  bytes 34787 (33.9 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 192.168.1.8  netmask 255.255.255.0  broadcast 192.168.1.255
       inet6 fe80::ed5b:91cc:e96f:f44c  prefixlen 64  scopeid 0x20<link>
       ether dc:a6:32:12:c6:0d  txqueuelen 1000  (Ethernet)
       RX packets 590  bytes 123422 (120.5 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 575  bytes 397002 (387.6 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 2312
       ether 74:da:38:a9:37:5f  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions

[Tim Curtis]

Revert to the integrated adapter
Reboot
Plug in the USB adapter
Post the output from the command below

Code:

ifconfig

Code:

admin@MoodeBoss:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
       ether dc:a6:32:12:c6:0b  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
       inet 127.0.0.1  netmask 255.0.0.0
       inet6 ::1  prefixlen 128  scopeid 0x10<host>
       loop  txqueuelen 1000  (Local Loopback)
       RX packets 302  bytes 34787 (33.9 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 302  bytes 34787 (33.9 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 192.168.1.8  netmask 255.255.255.0  broadcast 192.168.1.255
       inet6 fe80::ed5b:91cc:e96f:f44c  prefixlen 64  scopeid 0x20<link>
       ether dc:a6:32:12:c6:0d  txqueuelen 1000  (Ethernet)
       RX packets 590  bytes 123422 (120.5 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 575  bytes 397002 (387.6 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 2312
       ether 74:da:38:a9:37:5f  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions

That shows that the adapter was successfully recognized.

Wait until ~pre5 is posted and then retest with integrated WiFi turned off and USB adapter plugged in.

[nosferatu_cat]

Revert to the integrated adapter
Reboot
Plug in the USB adapter
Post the output from the command below

Code:

ifconfig

Code:

admin@MoodeBoss:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
       ether dc:a6:32:12:c6:0b  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
       inet 127.0.0.1  netmask 255.0.0.0
       inet6 ::1  prefixlen 128  scopeid 0x10<host>
       loop  txqueuelen 1000  (Local Loopback)
       RX packets 302  bytes 34787 (33.9 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 302  bytes 34787 (33.9 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 192.168.1.8  netmask 255.255.255.0  broadcast 192.168.1.255
       inet6 fe80::ed5b:91cc:e96f:f44c  prefixlen 64  scopeid 0x20<link>
       ether dc:a6:32:12:c6:0d  txqueuelen 1000  (Ethernet)
       RX packets 590  bytes 123422 (120.5 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 575  bytes 397002 (387.6 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 2312
       ether 74:da:38:a9:37:5f  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions

That shows that the adapter was successfully recognized.

Wait until ~pre5 is posted and then retest with integrated WiFi turned off and USB adapter plugged in.

Thanks.

[romain]

Hello,
I have moodeaudio ~pre4 installed on my pi 5. Each time I reboot output device reverts to PI HDMI 1 instead of keeping my SMSL SU-9 PRO USB DAC selection.

[Tim Curtis]

Hello,
I have moodeaudio ~pre4 installed on my pi 5. Each time I reboot output device reverts to PI HDMI 1 instead of keeping my SMSL SU-9 PRO USB DAC selection.

Is the DAC on when the Pi is started?

[romain]

Hello,
I have moodeaudio ~pre4 installed on my pi 5. Each time I reboot output device reverts to PI HDMI 1 instead of keeping my SMSL SU-9 PRO USB DAC selection.

Is the DAC on when the Pi is started?

Yes Tim

Code:

aplay -l

returns

Code:

**** Liste des périphériques matériels PLAYBACK ****
carte 0 : AUDIO [SMSL USB AUDIO], périphérique 0 : USB Audio [USB Audio]
  Sous-périphériques : 0/1
  Sous-périphérique #0 : subdevice #0
carte 1 : vc4hdmi0 [vc4-hdmi-0], périphérique 0 : MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Sous-périphériques : 1/1
  Sous-périphérique #0 : subdevice #0
carte 2 : vc4hdmi1 [vc4-hdmi-1], périphérique 0 : MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Sous-périphériques : 1/1
  Sous-périphérique #0 : subdevice #0

[nosferatu_cat]

Hello,
I have moodeaudio ~pre4 installed on my pi 5. Each time I reboot output device reverts to PI HDMI 1 instead of keeping my SMSL SU-9 PRO USB DAC selection.

I used aplay-l to get a list of audio devices.  I created a copy of /etc/alsa.conf using nano and used the card number of the device I wanted.  

Code:

admin@MoodeBoss:/etc $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 2: Boss2 [Allo Boss2], device 0: fe203000.i2s-allo-cs43130 allo-cs43130-0 [fe203000.i2s-allo-cs43130 allo-cs43130-0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

admin@MoodeBoss:/etc $ sudo nano /etc/alsa.conf

defaults.pcm.card [your card number]
defaults.ctl.card [your card number]

[romain]

I tried your tip but it didn't work in my case.
Thanks

[TheOldPresbyope]

@Tim Curtis 

Hadn't done anything with ~pre4 for several weeks but now that I'm back from the west coast I thought I'd catch up. Couldn't wait for ~pre5 so gulped the repo as of two nights ago.

1. nice to see that the Xserver/local display now starts on my Pi3B+ (well, it did after I realized I had to update several config files which I realized were out of scope for gulp deploy).

2. Because of our recent exchanges with @downriver_bob regarding discovery of multiroom receivers, I thought I'd play (for the first time ever) with moOde's multiroom feature.

In a mix of 8.3.9 and 9~pre4 players, it seems that my 9~pre4 players can discover 8.3.9 and 9~pre4 receivers but 8.3.9 players can only discover 8.3.9 receivers. Should I expect this? 

I wrote a quick shell script which combines the actions you outlined to downriver_bob and ran it on all players. I get the same results everywhere. Examples (no apology for output format!)

Code:

# on a 9~pre4 player
pi@m9pre4a:~ $ ./findrx.sh
10.0.0.19 rx,Disabled,0dB,0,1,sunroom
10.0.0.121 rx,Off,0,0,1,m839test
10.0.0.186 rx,Disabled,0,0,1,m9pre4a
10.0.0.198 rx,On,0dB,0,1,m9pre4b
10.0.0.205 rx,On,0dB,0,1,m839
# Discover reports:  Found: m839test, m9pre4b, m839

#on a 8.3.9 player
pi@sunroom:~ $ ./findrx.sh
10.0.0.19 rx,Disabled,0dB,0,1,sunroom
10.0.0.121 rx,Off,0,0,1,m839test
10.0.0.186 rx,Disabled,0,0,1,m9pre4a
10.0.0.198 rx,On,0dB,0,1,m9pre4b
10.0.0.205 rx,On,0dB,0,1,m839
# Discover reports:  Found: m839test, m839

where sunroom, m839, and m839test are all, no surprise, 8.3.9 players. m9pre4a is ~pre4 with latest repo gulped; m9pre4b is pure ~pre4.

Hope I'm making some sense here.

Regards,
Kent

ETA the script is simply a hack based on your previous post

Code:

$ cat findrx.sh
#!/bin/sh
nmap -Pn -p6600 --open 10.0.0.0/24 -oG /tmp/findrx.scan >/dev/null
cat /tmp/findrx.scan | grep "6600/open" | cut -f 1 | cut -d " " -f 2 > /tmp/findrx.ips
for ip in `cat /tmp/findrx.ips`; do
      echo -n "$ip "
      curl $ip/command/?cmd=trx-control.php%20-rx
      echo
done