05-05-2023, 12:02 AM
@Tim Curtis
So continuing with the booting problem I mentioned in Inno-maker HiFi DAC Pro HAT - first impressions
The problem with a Inno-maker HiFi DAC Pro HAT mounted on a Pi4B:
I looked at the output from systemctl and see several odd lines, notably, but not solely (with some white space removed for readibility)
Looking at /etc/rc,local, I discovered a potential cause of my problem
The if-test for this work-around should definitely trigger on my Pi4---I tried executing the lines manually---but the log file is never written. Looks like this may be where moOde is falling down.
If I execute the lines below manually I get
I'm not absolutely confident this is what's happening during the startup however.
If I simply comment out the work-around and reboot, moOde comes up fresh as paint and I can exercise the DAC. This is great because now, for example, the chip options are accessible via the webUI.
Any thoughts?
Regards.
Kent
So continuing with the booting problem I mentioned in Inno-maker HiFi DAC Pro HAT - first impressions
The problem with a Inno-maker HiFi DAC Pro HAT mounted on a Pi4B:
- moOde 8.3.2 boots and runs fine when I specify the DT Overlay to be "allo-katana-dac-audio" and reboot
- moOde stalls during boot---the webUI comes up but is basically catatonic---if I instead specify the NamedI2SDevice to be "Allo Katana DAC" and reboot
Code:
pi@moode:~ $ systemctl is-system-running
starting
I looked at the output from systemctl and see several odd lines, notably, but not solely (with some white space removed for readibility)
Code:
rc-local.service loaded deactivating stop-sigterm start/etc/rc.local Compatibility
...
getty.target loaded inactive dead start Login Prompts
...
multi-user.target loaded inactive dead start Multi-User System
Looking at /etc/rc,local, I discovered a potential cause of my problem
Code:
# Work around for Katana driver load failure on Pi-4B
AUDIO_DEVICE=$(sqlite3 $SQLDB "select value from cfg_system where param='i2sdevice'")
PI_REVNUM_SEGMENT=$(awk '{if ($1=="Revision") print substr($3,3,3)}' /proc/cpuinfo)
if [ "$AUDIO_DEVICE" = "Allo Katana DAC" ] && [ $PI_REVNUM_SEGMENT = "311" ]; then
rmmod snd_soc_allo_katana_codec
rmmod snd_soc_audio_graph_card
modprobe snd_soc_audio_graph_card
modprobe snd_soc_allo_katana_codec
echo `date +'%Y%m%d %H%M%S'` "rc.local ran Katana|Pi-4B driver reload" > /var/log/moode_katana.log
fi
The if-test for this work-around should definitely trigger on my Pi4---I tried executing the lines manually---but the log file is never written. Looks like this may be where moOde is falling down.
If I execute the lines below manually I get
Code:
root@moode:/etc# rmmod snd_soc_allo_katana_codec
rmmod snd_soc_audio_graph_card
modprobe snd_soc_audio_graph_card
modprobe snd_soc_allo_katana_codec
rmmod: ERROR: Module snd_soc_allo_katana_codec is in use
I'm not absolutely confident this is what's happening during the startup however.
If I simply comment out the work-around and reboot, moOde comes up fresh as paint and I can exercise the DAC. This is great because now, for example, the chip options are accessible via the webUI.
Any thoughts?
Regards.
Kent