Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fe-pi audio line in/out not working on 4.19.97 (raspberrypi-kernel_1.20200212-1) #3502

Open
preparationh67 opened this issue Mar 13, 2020 · 4 comments

Comments

@preparationh67
Copy link

Describe the bug
After upgrading a Pi 4 B Raspbian system to raspberrypi-kernel_1.20200212-1 from the previous version audio capture from the line input and audio play from the line output stopped working when using the Fe-Pi audio hat. Both devices are still visible to alsa and no errors are reported by applications trying to use them, but there is only silence on the line input and output. Output from the headphone port works as expected. Downgrading the kernel package to the old cached version, raspberrypi-kernel_1.20190925+1-1, restored the functionality of the line input and output. raspberrypi-firmware did not have to be downgraded.

To reproduce
Attach and enable a fe-pi audio hat. Update to the system to use raspberrypi-kernel_1.20200212-1 and attempt to capture audio from the line input using arecord, ffmpeg, or audacity or attempt to play audio via the line out instead of the headphone out.

Expected behaviour
Audio is captured or played through the audio cards line in and out when using appropriate software

Actual behaviour
No sound output via the line output and no audio is captured from the line input.

System

raspinfo: https://pastebin.com/WrH5Gv1J

  • Which model of Raspberry Pi? Pi 4 B
  • Which OS and version (cat /etc/rpi-issue)? 175dfb027ffabd4b8d5080097af0e51ed9a4a56c, stage4
  • Which firmware version (vcgencmd version)?
    Feb 12 2020 12:37:37
    Copyright (c) 2012 Broadcom
    version c3c8dbdf147686fb0c3f32aece709d0653368810 (clean) (release) (start_x)
  • Which kernel version (uname -a)? 4.19.97-v7l+

Logs
Log output from dmesg when broken: https://pastebin.com/trVRjpq2
Log output from dmesg when working: https://pastebin.com/5Bxun60p

Additional context
Presumably other audio cards using the SGTL5000 codec have the same issue, but I have no way to confirm that.

@pelwell
Copy link
Contributor

pelwell commented Mar 13, 2020

@Fe-Pi Is this something you can reproduce?

@Fe-Pi
Copy link

Fe-Pi commented Mar 13, 2020

This issue has been fixed.
#3468
Let me know if there still is an issue.

@Dloranger
Copy link

@Fe-Pi, @pelwell,

I think I might be running into a similar issue today (first update to kernel in a LONG time). I only did the update to get support for the 4B/8G hardware. This is running a lite distro (completely headless)

#uname -a
Linux openrepeater 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux

dmesg | grep sgtl5000

[ 7.203881] sgtl5000 1-000a: sgtl5000 revision 0x11

dmesg | grep fe-pi

The hardware is seen an loaded in the device tree as far as I can tell

i2cdetect -y 1

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00: -- -- -- -- -- -- -- UU -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

The hardware hat uses the SGTL5000 codec with line-in/line-out ports and everything has been working for years prior to the update. Now I get no audio at all and the SVXLINK package that consumes the audio behaves like it is not getting any audio packets at all on the line-in port (long story how I know this, but this is the symptom I have seen before). This has been reproduced on multiple pieces of hardware both rpi (4b) and hats.

Further, running speaker-test -c 2 -t sine -f 500 never toggles away from channel 0, so it appears the output is broken there as well.

Any ideas what might be the issue?

@Dloranger
Copy link

I think there is still something not quite right here, but I was able to get it working finally.

https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=306337

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants