New raspberry Pi 3 hardware revision

[strickon]

I just got a new pi and it won't load the drivers correctly. The audio driver doesn't load. The latest pi 3 is A52082

https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision-codes/README.md

in utils.py you are missing the new hardware revision.

    # The order of checks here is done Descending by Most Likely Model.
    if revision_hex & 0x00FFFFFF in (0x00A02082, 0x00A22082, 0x00A32082):
        model_name = RPI_3_KEY

[Ealdwulf]

Thanks, that's really helpful 👍
The audio issue is probably because we have some products which use the PWM output for something else, so we prevent the audio driver from loading automatically until the OS is sure it is not running on one of those (otherwise it would make a horrible noise). Once it decides what product it is running on it should load it - it would make sense that the revision code woudl confuse it. Did you find that manually editting utils.py fixed the issue?

[strickon]

I couldn’t figure out where the file gets installed. Can you tell me the path and I can try it?

…

On Aug 20, 2018, at 7:22 AM, Alex Burr ***@***.***> wrote: Thanks, that's really helpful 👍 The audio issue is probably because we have some products which use the PWM output for something else, so we prevent the audio driver from loading automatically until the OS is sure it is not running on one of those (otherwise it would make a horrible noise). Once it decides what product it is running on it should load it - it would make sense that the revision code woudl confuse it. Did you find that manually editting utils.py fixed the issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Ealdwulf]

Depending on the OS version, it is either:
/usr/lib/python2.7/dist-packages/kano/utils/hardware.py
Or
/usr/lib/python2.7/dist-packages/kano/utils.py

[strickon]

I tried changing that, no go. It no longer writes the error of unknown device to the kano log file, but it doesn’t load the audio driver either. Any other ideas?

…

On Aug 20, 2018, at 9:06 AM, Alex Burr ***@***.***> wrote: Depending on the OS version, it is either: /usr/lib/python2.7/dist-packages/kano/utils/hardware.py Or /usr/lib/python2.7/dist-packages/kano/utils.py — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#294 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAy-tnlZ14Bhv8wgFlzB2K9fDYXn2vfZks5uSrQ-gaJpZM4WCyEn>.

[Ealdwulf]

What version of the OS are you running? (please run kanux-version to find out)
If you run sudo modprobe -i snd_bcm2835 does it start working?

[strickon]

Kanux-Beta-3.15.0-Lovelace If you run modprobe, the driver does load aplay -l shows the device aplay /usr/share/sounds/Front_Center.wav does play This doesn’t allow any of the os sounds to play. Maybe it is an issue of the alsa mixer settings for the os and not having a device set?

…

On Aug 20, 2018, at 10:43 AM, Alex Burr ***@***.*** ***@***.***>> wrote: What version of the OS are you running? (please run kanux-version to find out) If you run sudo modprobe -i snd_bcm2835 does it start working? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#294 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAy-tvQd1xzRhMKqnKt1iZdjnMHT7LEdks5uSssUgaJpZM4WCyEn>.

[strickon]

Is there a fix for this beyond just adding the hardware id? That didn't seem to do it.

[radujipa]

Hi @strickon. Sorry for the delay in getting back to you, it's been a hectic period for us.

While looking to update the revision codes and add ones for the RPi 3B+, this issue came to mind. I noticed an issue when testing said changes that kano-boards-daemon crashes:

radu@kano ~ $ systemctl --user status kano-boards -l
● kano-boards.service - Kano Boards Daemon
   Loaded: loaded (/usr/lib/systemd/user/kano-boards.service; static; vendor preset: enabled)
   Active: failed (Result: core-dump) since Thu 2018-10-04 14:06:43 UTC; 9min ago
  Process: 2084 ExecStop=/usr/bin/sudo /usr/bin/kano-boards-daemon stop (code=dumped, signal=SEGV)
  Process: 1758 ExecStartPost=/bin/sleep 3 (code=exited, status=0/SUCCESS)
  Process: 1755 ExecStart=/usr/bin/sudo /usr/bin/kano-boards-daemon (code=dumped, signal=SEGV)
 Main PID: 1755 (code=dumped, signal=SEGV)

Oct 04 14:06:36 kano sudo[2084]:   File "/usr/bin/kano-boards-daemon", line 67, in only_hope
Oct 04 14:06:36 kano sudo[2084]:     pi_hat = KanoHatLeds()
Oct 04 14:06:36 kano sudo[2084]:   File "/usr/lib/python2.7/dist-packages/kano_pi_hat/kano_hat_leds.py", line 35, in __init__
Oct 04 14:06:36 kano sudo[2084]:     self._leds.begin()
Oct 04 14:06:36 kano sudo[2084]:   File "/usr/lib/python2.7/dist-packages/neopixel.py", line 114, in begin
Oct 04 14:06:36 kano sudo[2084]:     raise RuntimeError('ws2811_init failed with code {0}'.format(resp))
Oct 04 14:06:36 kano sudo[2084]: RuntimeError: ws2811_init failed with code -1
Oct 04 14:06:43 kano systemd[1520]: kano-boards.service: Control process exited, code=dumped status=11
Oct 04 14:06:43 kano systemd[1520]: kano-boards.service: Unit entered failed state.
Oct 04 14:06:43 kano systemd[1520]: kano-boards.service: Failed with result 'core-dump'.

Then I was curious if some workarounds were still viable. Clearly not:

radu@kano ~ $ lsmod | grep "snd_bcm2835"
radu@kano ~ $ 

I suggest you try running the following as an interim solution to your problem:

sudo rm /etc/modprobe.d/snd_bcm2835_blacklist.conf && sudo reboot

[strickon]

I just did the big update and saw the interim solution. It brought back audio. I tried this on both a b+ and the newer b by swapping the sd card and it worked for both of them.

[radujipa]

@strickon Thanks for giving that a try, great to hear it worked. The real fix for OS-469 As an engineer, I want to make sure the audio driver gets loaded even in catastrophic cases will be released with the next version (v4.2.0) soon and you won't need to remove the blacklist file manually.

Unfortunately, I have noticed another problem with audio to do with switching the audio output to HDMI. In this case, the channel is switched live correctly to HDMI with Kano Settings, but after a reboot the config is lost and switched back to analogue. I suspect this was introduced when migrated to stretch, but the hardware config masked the problem.

[hahtse]

Issue still seems to persist - is the fix in the current downloadable version, yet?