More > JRiver Media Center 28 for Linux
MC28 on Rpi4 - system hanging
JimH:
Is this the Pi not working or is it VNC not working?
Peter_RN:
--- Quote from: BryanC on March 08, 2022, 06:26:59 am ---There are really only two main logs that you should be interested in:
1. `dmesg`: this will give you some clues if you've got faulty hardware (look for red error output)
2. `sudo journalctl -r`: Scroll down and check around and before the time(s) that the Pi becomes unresponsive for clues
--- End quote ---
That is a great help Bryan thank you.
There are red entries in both these files which I don't really understand as they refer to i2c which is not enabled, I have never used i2c so unsure of the significance of this. It also complains about "module-alsa-card" I can only wonder if this refers to the 'Player' output that might be used to play a file locally - this is set to 'null output' in the option.
I will reproduce the end section of code here that shows errors.
'dmesg'
12.373803] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.374385] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.374913] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.382013] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.382374] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.382659] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.409147] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.409688] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.410202] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.416905] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.417202] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 12.417475] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.180990] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.181596] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.182164] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.189367] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.189660] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.190049] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.218294] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.218900] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.219604] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.226413] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.226834] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.227165] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 13.276087] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 13.276117] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 31.835895] cam-dummy-reg: disabling
[ 31.835907] vcc-sd: disabling
[ 31.835914] cam1-reg: disabling
[ 202.254947] v3d fec00000.v3d: MMU error from client CLE (4) at 0x36a1000, pte invalid
and from `sudo journalctl -r` which reproduces the above errors plus:
Mar 06 17:35:56 rpi x11vnc[722]: Libgcrypt warning: missing initialization - please fix the application
Mar 06 17:35:48 rpi pulseaudio[588]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="platform-f>
Mar 06 17:35:48 rpi pulseaudio[588]: Failed to find a working profile.
The above error are then displayed followed by:
Mar 06 17:35:48 rpi pulseaudio[588]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-f>
Mar 06 17:35:48 rpi pulseaudio[588]: Failed to find a working profile.
The above error are then displayed followed by:
Mar 06 17:35:48 rpi lightdm[613]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus>
Although I don't know the true significance of the above I would think it can't be good, so start again I think is the best idea. I have new SD cards and thumb drives that I can use and if I preserve the current ones I can then compare them.
Thanks again for your information, I would never have found those files.
Peter
[Correction - Sorry seems I can't read now, The log refers ti i2s not i2c]
Wheaten:
What kind of DAC are you using, a HAT?
Peter_RN:
--- Quote from: JimH on March 08, 2022, 06:33:09 am ---Is this the Pi not working or is it VNC not working?
--- End quote ---
Hi Jim
The Pi is working fine as a general computer running Raspberry OS and Ubuntu Mate and it ran for a short while with OpenMediaVault - no problems of any sort.
Because I could not get another 4GB Pi due to the shortage at this time I did get a 2GB model and decided that the 4GB would be better used to run J River MC as OMV runs well on a 2GB Pi. Only when I put MC28 on a new Sandisk USB3 drive and followed instructions kindly posted by Wheaten and tried running headless did the problem arise.
Now, please don't misunderstand me, I am NOT suggesting for a moment that there is anything wrong with the instructions, there clearly is not. In fact I used them back when the Pi 3b was the current model very successfully.
The thing that puzzled me and the reason I came to the forum was the fact that if I switch on the Pi it boots up and I open MC I can select and play music all day long provided I don't leave MC open but not playing music for too long a period (I am not sure exactly how long too long is) certainly if I go to bed at midnight the system is completely locked up by the morning but I think a couple of hours was also long enough to cause this to happen.
I shut MC down on Saturday (5th) early evening and have left the Pi running ever since and I can still access it both by SSH and VNC.
Clearly as nobody else is having this issue it has to be something specific to the way I am trying to set it up. The folks here on the Forum have been trying to guide me in finding the cause and I am extremely grateful to you all for your efforts.
VNC is not a problem Jim, I use it a lot on several of my Pi's it was just that it was extremely sluggish with MC but again Wheaten explained why and how to improve this.
We love MC in this house it passes our files without any interference and the ability to build complex Smartlists is a genuine bonus.
Peter_RN:
--- Quote from: Wheaten on March 08, 2022, 10:36:29 am ---What kind of DAC are you using, a HAT?
--- End quote ---
Hello again, no hat just the Pi streaming across the network to two locations, there is a Naim Audio streamer at each location.
The lounge has an NDX streamer which then passes the data to a separate Naim DAC before the preamp. The Dining Rm has a Qute.
I must thank you for your info on the VNC setup - this also led me to discover 'Screen Sharing' which I was unaware of.
Navigation
[0] Message Index
[*] Previous page
Go to full version