Official moOde 6.7.1 support thread

[Kikaha]

Very odd.

This log entry indicates there is no HDMI port, only Headphone
20201216 160740 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty

This log entry indicates the HDMI port is on
20201216 160743 worker: HDMI port on

If Linux is able to recognize and configure HDMI port(s) it will show up in the device list printed by the command below.

Code:

aplay -l

Maybe something that was added to config.txt is causing an issue?

Even more odd:

Code:

cat  /proc/asound/cards
0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                     bcm2835 Headphones

Looks like that there is no HDMI port at all. Just doing apt update and upgrade and will reboot afterwards - I will report then.

Do not think that the additional lines in config.txt cause issues - at least the cec inactivation worked as intended. Perhaps some sort of kernel regression?

Hm. Looks like I bricked my raspi. Apt update and apt ugrade finished, but no boot... I will set up the entire system again.

[TheOldPresbyope]

2) Raspi 3B with 7" official display connected via HDMI to Marantz AVR --> same install --> sound only via headphone jack, no sound via HDMI

Possibly an unexpected conflict somewhere because of the local display?

I just looked at my only Official Display-equipped moOde player. It's running the testing version of moOde r7.0.0 but it has the same behavior as reported by the OP. Here's snippets of moodeutl -l and aplay -l outputs

Code:

20201216 121755 worker: -- Device
20201216 121755 worker: ALSA cards: (0:Headphones | 1:empty | 2:empty | 3:empty
20201216 121755 worker: Configured: (0:Pi Headphone jack | mixer:(Headphone) | alsavol:0)
20201216 121755 worker: ALSA mixer actual (Headphone)
20201216 121756 worker: ALSA Headphone volume set to (0%)
20201216 121756 worker: -- System
20201216 121757 worker: Host     (moodeld)
20201216 121757 worker: moOde    (7.0.0 2020-12-15)
20201216 121757 worker: RaspiOS  (10.6)
20201216 121757 worker: Kernel   (5.4.77-v7+ #1371)
20201216 121757 worker: Platform (Pi-3B+ 1GB v1.3)
20201216 121757 worker: ARM arch (armv7l, 32-bit kernel)
20201216 121757 worker: MPD ver  (0.22.3_p0x3)
20201216 121757 worker: CPU gov  (ondemand)
20201216 121757 worker: USB boot enabled
20201216 121757 worker: File system expanded
20201216 121757 worker: HDMI port on

and

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 8/8
...

Confirming, the Pi HDMI does not appear in the Output Device pulldown list in MPD Config.

Turning off the HDMI port, rebooting, turning the HDMI port back on, and rebooting did not change the situation.

OTOH, I'm running moOde r6.7.1 on another Pi-3B+ with an actual HDMI device attached (a 3.5in LCD display). Same snippets:

Code:

20201214 112406 worker: Device raw: (0:b1|1:Headphones|2:empty|3:empty
20201214 112406 worker: Device i2s: (none)
20201214 112406 worker: Device mpd: (1:Pi Headphone jack)
20201214 112406 worker: Device ses: (1|Pi Headphone jack|Headphone|0%)
20201214 112406 worker: ALSA Headphone volume set to (0%)
20201214 112406 worker: -- System
20201214 112408 worker: Host     (moode671)
20201214 112408 worker: moOde    (6.7.1 2020-07-22)
20201214 112408 worker: RaspiOS  (10.6)
20201214 112408 worker: Kernel   (5.4.79-v7+ #1373)
20201214 112408 worker: Platform (Pi-3B+ 1GB v1.3)
20201214 112408 worker: ARM arch (armv7l, 32-bit kernel)
20201214 112408 worker: MPD ver  (0.21.24)
20201214 112408 worker: CPU gov  (ondemand)
20201214 112408 worker: USB boot enabled
20201214 112408 worker: File system expanded
20201214 112409 worker: HDMI port on

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
 Subdevices: 4/4
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
 Subdevices: 3/4
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3

and of course the PI HDMI output device shows up in MPD Config.

I see only one difference in the /boot/config.txt files.

- hdmi_group=0 in the player not offering the Pi HDMI device
- hdmi_group=1 in the player which does

However, on yet another RPi3A+ player running the testing version of moode-r7.0.0 with no local display, the Pi HDMI output device is offered in MPD Config. In its /boot/config.txt file, hdmi_group=0 so this seems a red herring, which by all rights it should be.

Regards,
Kent

[Kikaha]

I guess I have it. Seems to be an issue with the power. Since the Official 7" Display is mounted to the Raspi, I have two USB plugs for power. It is recommended to use the display`s power plug and I obviously used the other one directly on the Raspi. With the said strange effects. When using the recommended power plug the system will not boot at all: The wellknown "colorful" screen appears. Seenms that the new SSD draws too much current in combination with the touch display.

Will try again with powered USB hub or stronger power adapter. Both I currently do not have at hand, but will come back later.

Kent: Perhaps it is worthwhile to check which power plugs you use on your raspis w/o Official 7" Display...

Thanks for your thoughts and ideas - eventually these pushed me in the right direction 

[TheOldPresbyope]

@Kikaha 

Ah, additional components. In addition to the SSD perhaps the HDMI connection is drawing current too but I have no knowledge of the electronic circuitry involved in an HDMI connection.

Certainly adequate power is needed but in my case I have a 3A supply feeding both the RPi and the Official Display through their individual power inputs using a USB power-splitter cable. I see no problems that I can associate with poor power. For example, the display shows the traditional 4 strawberry icons, one for each CPI, and no lightning bolt icon warning of an undervoltage condition. There are no power-associated warnings in the dmesg output.

I don't think we've ruled out the possibility that there is an unresolved configuration issue here.

...und Schöne Feiertage!

Regards,
Kent

[Tim Curtis]

I got same results with my Pi-Touch rig on 671 and upcoming 700. It looks like the attached Pi Touch results in the HDMI port being disabled. It might be different on a Pi-4 that has 2 HDMI ports ?

[Kikaha]

@Kikaha 

Ah, additional components. In addition to the SSD perhaps the HDMI connection is drawing current too but I have no knowledge of the electronic circuitry involved in an HDMI connection.

Certainly adequate power is needed but in my case I have a 3A supply feeding both the RPi and the Official Display through their individual power inputs using a USB power-splitter cable. I see no problems that I can associate with poor power. For example, the display shows the traditional 4 strawberry icons, one for each CPI, and no lightning bolt icon warning of an undervoltage condition. There are no power-associated warnings in the dmesg output.

I don't think we've ruled out the possibility that there is an unresolved configuration issue here.

...und Schöne Feiertage!

Regards,
Kent

OK... 3A should be well enough. But OTOH: When I connected the Pi via the Pi power input, I got the same as you: 4 strawberries, no lightning - but additionally this strange effect pretending that there were no HDMI out. I don`t know for hard the specs of my current power adapter, but anyway: I remounted the old system (moode 4.2 on an old SSD in an SSD-USB adapter called Icy Box) with SD card only with /boot partition inserted and this config runs flawlessly for more than 2 years now and of course right now again. Very odd.

Also Schöne Feiertage for you (and everyone here) and: Bleibt gesund - Covid19 is a killer.

[Macdelf]

I just noticed something. I use mp4tag to organize my library and track ordering is off when i use a single number for the tag (e.g. 12 as opposed to 12/19 for a 19 track album). Tracks seem to order as 1,10,11,12...19,2,3,4,5,6,7,8,9. Should I be using the total track count in the tag with the /? 
Thanks for any help.

[TheOldPresbyope]

I just noticed something. I use mp4tag to organize my library and track ordering is off when i use a single number for the tag (e.g. 12 as opposed to 12/19 for a 19 track album). Tracks seem to order as 1,10,11,12...19,2,3,4,5,6,7,8,9. Should I be using the total track count in the tag with the /? 
Thanks for any help.

This is classic situation with string comparisons. The solution is to number tracks 01, 02, ..., 99 if one knows there will never be more that 99 tracks.

Regards,
Kent

[Macdelf]

TTheOldPresbyope

I just noticed something. I use mp4tag to organize my library and track ordering is off when i use a single number for the tag (e.g. 12 as opposed to 12/19 for a 19 track album). Tracks seem to order as 1,10,11,12...19,2,3,4,5,6,7,8,9. Should I be using the total track count in the tag with the /? 
Thanks for any help.

This is classic situation with string comparisons. The solution is to number tracks 01, 02, ..., 99 if one knows there will never be more that 99 tracks.

Regards,
Kent

That worked. Funny I never noticed. Classical recordings had their movements out of order. 
Thank You and Merry Christmas
I am looking forward to 7.0!

[Kikaha]

I got same results with my Pi-Touch rig on 671 and upcoming 700. It looks like the attached Pi Touch results in the HDMI port being disabled. It might be different on a Pi-4 that has 2 HDMI ports ?

Hi,

I can now confirm that the HDMI port does not show up when Pi-Touch is attached. These are the outputs after first boot of the fresh install of 6.7.1 (fresh dowload, MD checked and ok, unzipped and flashed to the external SSD), undervolting issue now solved by usage of 2 power adapters (each 2.5 A, one for the power input of the Pi and the other one for the touch) simultaneously:

Code:

pi@moode:~ $ dmesg
...
...
[   14.288298] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[   14.298169] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   14.320662] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[   14.351465] bcm2835_audio bcm2835_audio: card created with 8 channels
[   14.352677] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[   14.373482] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[   14.374288] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[   14.374924] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[   14.375424] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[   14.375466] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[   14.375500] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[   14.375519] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[   14.375536] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[   14.376077] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[   14.403272] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[   14.493758] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[   14.493932] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[   14.515363] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[   14.515424] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[   14.529728] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[   14.529780] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[   14.675996] input: raspberrypi-ts as /devices/platform/soc/soc:firmware/soc:firmware:touchscreen/input/input0
[   14.710264] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   14.888583] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   14.905839] usbcore: registered new interface driver uas
[   14.946962] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   14.967828] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   14.968164] usbcore: registered new interface driver brcmfmac
[   14.988371] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
[   15.022496] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   15.219632] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   15.219760] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   15.221101] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[   18.063145] 8021q: 802.1Q VLAN Support v1.8
[   18.500110] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[   18.947949] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   20.375428] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x5DE1

There are some error messages at the end of dmesg output connected to brcfmac, but my Linux Fu is not sufficient to interprete this.

moodeutl -l and aplay -l show no HDMI out at all, this fits to the "ALSA Invalid card number. volume set to (Invalid card number.)" message, I guess.

Code:

pi@moode:~ $ moodeutl -l
20200722 164219 worker: -- Start
20200722 164219 worker: Successfully daemonized
20200722 164220 worker: Integrity check (passed)
20200722 164220 worker: Session loaded
20200722 164220 worker: Debug logging (off)
20200722 164220 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty
20200722 164220 worker: Device i2s: (none)
20200722 164220 worker: Device mpd: (1:Pi Headphone jack)
20200722 164220 worker: Device ses: (1|Pi Headphone jack|Headphone|0%)
20200722 164220 worker: ALSA Invalid card number. volume set to (Invalid card number.)
20200722 164220 worker: -- System
20200722 164221 worker: Host     (moode)
20200722 164221 worker: moOde    (6.7.1 2020-07-22)
20200722 164221 worker: RaspiOS  (10.4)
20200722 164221 worker: Kernel   (5.4.51-v7+ #1325)
20200722 164221 worker: Platform (Pi-3B 1GB v1.2)
20200722 164221 worker: ARM arch (armv7l, 32-bit kernel)
20200722 164221 worker: MPD ver  (0.21.24)
20200722 164221 worker: CPU gov  (ondemand)
20200722 164222 worker: USB boot enabled
20200722 164222 worker: File system not expanded yet
20200722 164222 worker: HDMI port on
20200722 164222 worker: File check (OK)
20200722 164222 worker: -- Network
20200722 164223 worker: eth0 exists
20200722 164223 worker: IP addr (192.168.178.53)
20200722 164223 worker: Netmask (255.255.255.0)
20200722 164223 worker: Gateway (192.168.178.1)
20200722 164223 worker: Pri DNS (192.168.178.1)
20200722 164223 worker: Domain  (fritz.box)
20200722 164223 worker: wlan0 exists
20200722 164223 worker: wifi country (US)
20200722 164223 worker: wlan0 SSID is blank
20200722 164223 worker: eth0 addr exists, AP mode not started
20200722 164223 worker: wlan0 address not assigned
20200722 164223 worker: -- Audio
20200722 164224 worker: MPD conf updated
20200722 164224 worker: ALSA outputs unmuted
20200722 164224 worker: ALSA card number (1)
20200722 164225 worker: Audio output ()
20200722 164225 worker: Audio formats (Unable to detect formats)
20200722 164225 worker: ALSA mixer name (Invalid card number.)
20200722 164225 worker: MPD volume control (software)
20200722 164226 worker: Hdwr volume controller exists
20200722 164226 worker: Max ALSA volume (100%)
20200722 164226 worker: Reset renderer active flags
20200722 164226 worker: -- MPD
20200722 164226 worker: MPD started
20200722 164226 worker: MPD accepting connections
20200722 164226 worker: Configure MPD outputs
20200722 164226 worker: MPD output 1 ALSA default (on)
20200722 164226 worker: MPD output 2 ALSA crossfeed (off)
20200722 164226 worker: MPD output 3 ALSA parametric eq (off)
20200722 164226 worker: MPD output 4 ALSA graphic eq (off)
20200722 164226 worker: MPD output 5 ALSA polarity inversion (off)
20200722 164226 worker: MPD output 6 ALSA bluetooth (off)
20200722 164226 worker: MPD output 7 HTTP stream (off)
20200722 164226 worker: MPD crossfade (off)
20200722 164226 worker: -- Feature availability
20200722 164226 worker: Source select (available)
20200722 164226 worker: Source select (source: MPD)
20200722 164227 worker: Source select (output: )
20200722 164227 worker: Bluetooth (available)
20200722 164227 worker: Airplay renderer (available)
20200722 164227 worker: Spotify renderer (available)
20200722 164227 worker: Squeezelite renderer (available)
20200722 164227 worker: UPnP renderer (available)
20200722 164227 worker: DLNA server (available)
20200722 164227 worker: UPnP browser (available)
20200722 164227 worker: Audio scrobbler (available)
20200722 164227 worker: GPIO button handler (available)
20200722 164227 worker: -- Music sources
20200722 164227 worker: USB sources (none attached)
20200722 164227 worker: NAS and UPnP sources (none configured)
20200722 164227 worker: -- Miscellaneous
20200722 164227 worker: USB volume knob (Off)
20200722 164227 worker: USB auto-mounter (udisks-glue)
20200722 164227 worker: LED0 (On)
20200722 164227 worker: LED1 (On)
20200722 164227 worker: Saved MPD vol level (0)
20200722 164227 worker: Preamp volume level (0)
20200722 164227 worker: MPD volume level (0) restored
20200722 164228 worker: ALSA Invalid card number. volume (Invalid card number.)
20200722 164228 worker: Auto-play (Off)
20200722 164228 worker: Maintenance interval (3 hrs)
20200722 164228 worker: Screen saver activation (Never)
20200722 164228 worker: Session permissions (OK)
20200722 164228 worker: Watchdog started
20200722 164228 worker: Ready

Code:

pi@moode:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
 Subdevices: 8/8
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
 Subdevice #4: subdevice #4
 Subdevice #5: subdevice #5
 Subdevice #6: subdevice #6
 Subdevice #7: subdevice #7

Btw: After first boot and also after several reboots, the GUI does not show up on the touchscreen (hangs after login prompt), but GUI is available on remote PC. Dunno whether this is relevant for the current issue.
All in all, this seems to be a hardware / kernel issue outside moode. So for the time being, I will stick to my good old 4.2 and wait for better times

Thanks again to all and have a nice Xmas!