Octo fails to register with current 4.19.25 kernel

Moderator: flatmax

Post Reply
nettings
Posts: 20
Joined: Sat Sep 23, 2017 7:31 am

Octo fails to register with current 4.19.25 kernel

Post by nettings » Sat Mar 02, 2019 11:47 pm

Hi *,


I'm testing an Octo rev. 1.16 with RCA boards v. 1.6, using the manual setup method. Base system is Raspbian Stretch, updated today.
rpi-update pulls the 4.19.25 kernel, and it seems there is a problem with setting up the card:

Code: Select all

[    6.981819] audioinjector-octo soc:sound: ASoC: CODEC DAI cs42448 not registered - will retry
[    6.981839] audioinjector-octo soc:sound: snd_soc_register_card failed (-517)
[    7.635876] IPv6: ADDRCONF(NETDEV_CHANGE): medianet0: link becomes ready
[    8.541717] audioinjector-octo soc:sound: ASoC: CODEC DAI cs42448 not registered - will retry
[    8.541727] audioinjector-octo soc:sound: snd_soc_register_card failed (-517)
[   11.587498] random: crng init done
[   11.587509] random: 7 urandom warning(s) missed due to ratelimiting
[  510.464005] audioinjector-octo soc:sound: ASoC: CODEC DAI cs42448 not registered - will retry
[  510.464014] audioinjector-octo soc:sound: snd_soc_register_card failed (-517)
[  529.333206] audioinjector-octo soc:sound: ASoC: CODEC DAI cs42448 not registered - will retry
[  529.333214] audioinjector-octo soc:sound: snd_soc_register_card failed (-517)
Those later errors after 510 are me manually rmmoding and modprobing the module, in case there is a race condition early on. No luck, same error. As expected, aplay -L will constitently report "No soundcards found."

Can anybody reproduce this issue? Meanwhile, I'll see how I can downgrade the kernel. What is the last-known-good version that people have been using?

Reading through the forum, this might be related to
viewtopic.php?f=9&t=5493
viewtopic.php?f=9&t=5718

nettings
Posts: 20
Joined: Sat Sep 23, 2017 7:31 am

Re: Octo fails to register with current 4.19.25 kernel

Post by nettings » Sun Mar 03, 2019 1:36 am

Turns out that if I remove the entire module stack and reload, the device appears.

Code: Select all

sudo modprobe -r snd_soc_audioinjector_octo_soundcard
sudo modprobe -r snd_soc_cs42xx8_i2c
sudo modprobe -r snd_soc_cs42xx8
sudo modprobe snd_soc_cs42xx8
sudo modprobe snd_soc_cs42xx8_i2c
sudo modprobe snd_soc_audioinjector_octo_soundcard

Code: Select all

[  529.333206] audioinjector-octo soc:sound: ASoC: CODEC DAI cs42448 not registered - will retry
[  529.333214] audioinjector-octo soc:sound: snd_soc_register_card failed (-517)
[ 7423.839738] cs42xx8 1-0048: 1-0048 supply VA not found, using dummy regulator
[ 7423.839778] cs42xx8 1-0048: Linked as a consumer to regulator.0
[ 7423.839785] cs42xx8 1-0048: 1-0048 supply VD not found, using dummy regulator
[ 7423.839815] cs42xx8 1-0048: 1-0048 supply VLS not found, using dummy regulator
[ 7423.839845] cs42xx8 1-0048: 1-0048 supply VLC not found, using dummy regulator
[ 7423.872427] cs42xx8 1-0048: found device, revision 4
[ 7428.143356] audioinjector-octo soc:sound: cs42448 <-> 3f203000.i2s mapping ok
[ 7433.266894] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 7433.276734] bcm2835-i2s 3f203000.i2s: I2S SYNC error!

richardash1981
Posts: 3
Joined: Sun Apr 28, 2019 2:36 am

Re: Octo fails to register with current 4.19.25 kernel

Post by richardash1981 » Sun Apr 28, 2019 3:16 am

Rather late, but I hit this problem using stock Raspbian (4.14.98) as well. The modprobe sequence worked, so I dug around in the forum and found
viewtopic.php?f=9&t=1795&p=3419#p3419 which has a proper solution.

I made the same change as suggested and rebooted, and the device is up and working on reboot, without having to reload the modules. The solution is presumably to force the modules to load in the correct order, as that is what I think the configuration file does.

Code: Select all

pi@raspberrypi:~ $ cat /etc/modprobe.d/audioinjector-octo.conf
softdep snd_soc_audioinjector_octo_soundcard pre: snd_soc_cs42xx8 snd_soc_cs42xx8_i2c
The file doesn't exist, so create it (you will need root access, so use sudoedit) and paste in the above line (all on one line), save and reboot, The card should then be detected on boot correctly.

There is probably a way to change the module sourcecode to make the modules load in this order always, but I don't know what it is.

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests