Octo not showing up on booting

[flashbacker]

Hello,

I'm running into the exact same problem here, but the Octo is recognized maybe only around 50% of times.
I've tried all fixes on this thread besides the last one flatmax talked about...
Is there some real fix on its way or the issue is still blurry?
Flatmax, could you explain some steps to change the reset code so I can try it?

I'm suppose to use the Octo for an installation which will run for one month, and be turned on by random people, so this situation is really problematic for me, I can't ask them to do some fixes in the terminal time to time...

[flatmax]

You may find it better to use the modprobe commands to manually reload the card's drivers every boot.

Here they are again :

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

You can put them in an autostart script to make it execute every boot. I think the file to make this happen is still :

Code: Select all

~/.config/lxsession/LXDE-pi/autostart

Matt

[flashbacker]

Hi,

so as a follow up as this conversation in case somebody has the same problem, putting the above code in autostart somehow didn't work.
Instead the solution which worked was to create a script with this code, then:

Code: Select all

sudo chmod 755 myscript

then i put in the autostart file

Code: Select all

@./myscript

I don't really understand what the difference is, but it works this way

[dakyri]

I had this problem as well, and it seems to be a not uncommon issue. I was panicking that perhaps the octo was faulty, but the sudo modprobe fix definitely did the trick for me, at least as far as this first test goes.
Hopefully the Octo keeps jumping through the hoops successfully.
It would perhaps be a good idea to add that modprobe fix to the "How to setup" thread.
Thanks for all the great work.

[richardash1981]

See this message, which forces the order of module load and seems to fix the problem (works for me)
viewtopic.php?f=9&t=1795&p=3419#p3419
without having to reload everything.

[PromElectric]

I cant speak of Mk3, but IIRC there are script commands to explicitly update the flight plan info and some routines do use them. Perhaps the Mk3 does not?

<a href=https://prom-electric.ru/>.</a>