Thank you for your donation!


Official moOde 6.5.2 support thread
(06-15-2020, 04:01 PM)TheOldPresbyope Wrote:
(06-15-2020, 03:39 PM)moodenigo Wrote: Hello. Technically this is not a moOde but a MPD problem. However MPD crashes while trying to add .wv (WAVPACK) files. I still have a couple of .wv files in my library, and I realised that regenerating the library always failed on a disk I rarely use, but I decided to reconnect. Looking at the log, it would stop and restart from scratch once it tried to parse one such file. I converted them all to ALAC and so far no crashes.

This with the 0.21 version by default installed on 6.5.2.

Curious. 

I don't pretend to know the nuances of the Wavpack format but just for grins I've now downloaded two sample files (from https://filesamples.com/formats/wv) onto my uSD card. One file is tagged, the other isn't.

moOde 6.5.2/ MPD 0.21 happily scanned these two files and is playing them as I type. 

There would seem to be an issue with your specific files but without more information I couldn't possibly guess what it is.

Well, I overwrote them with ALAC files now, but I may be able to recover them from an old backup.
Reply
Hello Forum!
As this is my first post, I would like to thank everyone involved for providing such a great system (i enjoy it every day)!
Secondly I would like to report a bug on moOde 6.5.2 on a Pi-4B 4GB v1.2 with hifiberry dac+ pro: as soon as I switch to 64bit kernel wifi becomes unavailable (system information tells me: WLAN address = unassigned WLAN MAC = no adapter) and I only can connect via ethernet. Changing back to 32bit kernel fixes the problem. I've got another Pi-4B 4GB running the same exact setup, the only difference is that on this one wifi works flawlessly with the 64bit kernel (another difference is the microsd with 32 on this vs 128 gb on the other one). I've formated the microsd and flashed the image again, but the problem persits.
This said, I can happily live with the 32bit kernel - just wanted to report this bug.
Reply
Thanks. The 64-bit kernel is still kind of messy and experimental. It seems that some libraries and drivers crash when running in 64 bit. Maybe when moOde switches to the 5.4.y kernel branch there will be more stability in 64-bit.
Reply
(06-17-2020, 08:28 AM)rAudio Wrote: Hello Forum!
As this is my first post, I would like to thank everyone involved for providing such a great system (i enjoy it every day)!
Secondly I would like to report a bug on moOde 6.5.2 on a Pi-4B 4GB v1.2 with hifiberry dac+ pro: as soon as I switch to 64bit kernel wifi becomes unavailable (system information tells me: WLAN address = unassigned WLAN MAC = no adapter) and I only can connect via ethernet. Changing back to 32bit kernel fixes the problem. I've got another Pi-4B 4GB running the same exact setup, the only difference is that on this one wifi works flawlessly with the 64bit kernel (another difference is the microsd with 32 on this vs 128 gb on the other one). I've formated the microsd and flashed the image again, but the problem persits.
This said, I can happily live with the 32bit kernel - just wanted to report this bug.

Recapping:
- two RPi 4B 4GB v1.2 (both... ??)
- two different-size uSD cards (32 GB and 128 GB)
- MoOde 6.5.2 loaded on both uSD cards
- HiFiBerry DAC+ Pro (used on both RPi's... ??)
- WiFi fails on the RPI running  64bit-kernel 128GB uSD card (even after re-imaging)
- WiFi works on the RPi running 64bit-kernel 32GB uSD card

If the above is correct:
- (no HAT DAC) how is the WiFi connection on both RPi's running their original 64bit-kernel uSD cards... ?
- (no HAT DAC) how is the WiFi connection on the 'suspect' RPi running a NEW 64bit-kernel ~32GB~ uSD card... ?
- repeat the above TWO test; how is the WiFi connection on both RPi's... ?
Reply
(06-17-2020, 08:28 AM)rAudio Wrote: Hello Forum!
As this is my first post, I would like to thank everyone involved for providing such a great system (i enjoy it every day)!
Secondly I would like to report a bug on moOde 6.5.2 on a Pi-4B 4GB v1.2 with hifiberry dac+ pro: as soon as I switch to 64bit kernel wifi becomes unavailable (system information tells me: WLAN address = unassigned WLAN MAC = no adapter) and I only can connect via ethernet. Changing back to 32bit kernel fixes the problem. I've got another Pi-4B 4GB running the same exact setup, the only difference is that on this one wifi works flawlessly with the 64bit kernel (another difference is the microsd with 32 on this vs 128 gb on the other one). I've formated the microsd and flashed the image again, but the problem persits.
This said, I can happily live with the 32bit kernel - just wanted to report this bug.

Quote:Pi-4B 4GB v1.2  another Pi-4B 4GB

Are they both running the same firmware ?  Were they purchased at the same time ? Is the one running wifi fine a later purchase..?

https://www.raspberrypi.org/documentatio.../README.md

Reply
@rAudio

1. uSD cards are not all the same. Have you tried the simple expedient of swapping the 32GB and 128GB cards between the two RPi4Bs and rebooting? Is the behavior related to a specific RPi4B or to the 128GB card?

2. To expand on @DRONE7's post, the RPi model 4 differs from earlier models in that it has some of its firmware stored in eeprom so that It is available at boot but can be updated from time to time. (Previous models use the contents of the bootcode.bin file.)

Check your two RPi4Bs using the vcgencmd command to be sure they are running the same firmware version. Here's an example for the moOde player in my living room:

Code:
pi@moodelr:~ $ /opt/vc/bin/vcgencmd bootloader_version
Apr 16 2020 18:11:26
version a5e1b95f320810c69441557c5f5f0a7f2460dfb8 (release)
timestamp 1587057086

If they are not the same, then consult the RPi booteeprom documentation on the update process.

Regards,
Kent

PS - (my favorite soapbox topic) This is not a moOde 6.5.2 bug report. It should be the subject of a separate thread.
Reply
(06-18-2020, 11:30 AM)TheOldPresbyope Wrote: @rAudio

1. uSD cards are not all the same. Have you tried the simple expedient of swapping the 32GB and 128GB cards between the two RPi4Bs and rebooting? Is the behavior related to a specific RPi4B or to the 128GB card?

2. To expand on @DRONE7's post, the RPi model 4 differs from earlier models in that it has some of its firmware stored in eeprom so that It is available at boot but can be updated from time to time. (Previous models use the contents of the bootcode.bin file.)

Check your two RPi4Bs using the vcgencmd command to be sure they are running the same firmware version. Here's an example for the moOde player in my living room:

Code:
pi@moodelr:~ $ /opt/vc/bin/vcgencmd bootloader_version
Apr 16 2020 18:11:26
version a5e1b95f320810c69441557c5f5f0a7f2460dfb8 (release)
timestamp 1587057086

If they are not the same, then consult the RPi booteeprom documentation on the update process.

Regards,
Kent

PS - (my favorite soapbox topic) This is not a moOde 6.5.2 bug report. It should be the subject of a separate thread.

As a first step, update your pis.

sudo apt update
sudo apt full-upgrade

Then reboot.

This will not break Moode.

After rebooting,

sudo rpi-eeprom-update

to see the firmware versions.

Cheers,

Phil
Pi 4B 1GB / SMSL Sanskrit 10th MK II USB  DAC / Pro-ject Elemental / Marantz CD6004 / Marantz PM6004 / Monitor Audio Bronze 2
Reply
Sure, I was just hoping to find out if the difference in firmware was the root cause before he upgraded.
Reply
(06-18-2020, 08:50 PM)TheOldPresbyope Wrote: Sure, I was just hoping to find out if the difference in firmware was the root cause before he upgraded.

My (too) many years in IT have led me to the 'patch everything first and see if it is still broken" mantra Tongue
Pi 4B 1GB / SMSL Sanskrit 10th MK II USB  DAC / Pro-ject Elemental / Marantz CD6004 / Marantz PM6004 / Monitor Audio Bronze 2
Reply
(06-18-2020, 09:28 PM)philrandal Wrote:
(06-18-2020, 08:50 PM)TheOldPresbyope Wrote: Sure, I was just hoping to find out if the difference in firmware was the root cause before he upgraded.

My (too) many years in IT have led me to the 'patch everything first and see if it is still broken" mantra Tongue

My many years have led me to start my check list with "it's plugged in, right?" [1]

Naturally, that's followed by "it's turned on, right?"

If both answers are yes, then we move on to "have you tried rebooting?"

Only then do I get to your mantra Rolleyes

Regards,
Kent

[1] Let me tell you about the time the overnight cleaning crew unplugged the power feed to my cubicle so they could run their vacuum cleaner without going to find an extension cord. My Apollo workstation---yes, this happened that long ago---clearly was plugged into the cubicle's power strip but wouldn't power up. The disconnection was behind a modesty panel where I couldn't see it. What a hoot!
Reply


Forum Jump: