# Audio Problems similar to X86\_64 latest kernel in latest Raspberry Pi Appliance Kernel **URL:** \ **Category:** AllStarLink\ **Created:** [January 31, 2025, 6:20pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829 "2025-01-31T18:20:45Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![va3aum](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/e9bcb4/32.png) [@va3aum](https://community.allstarlink.org/u/va3aum)\ **Post date:** [January 31, 2025, 6:20pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/1 "2025-01-31T18:20:45Z")
Hello folks, I have just learned, through personal experience, that the latest kernel that just dropped for the Raspberry Pi ASL3 Appliance (6.6.74+rpt-rpi-v8) has similar or same audio problems over a radio audio interface as the latest X86\_64 kernels. Recommend that everyone running an ASL3 Pi appliance hold off on running sudo apt update && apt upgrade until the ASL3 team evaluates this and comes up with a fix. An audio example is located at: [https://media.fedi.adamm.cc/media\_attachments/files/113/924/316/565/808/973/original/9e21cafd2bb47a5b.mp3](https://media.fedi.adamm.cc/media_attachments/files/113/924/316/565/808/973/original/9e21cafd2bb47a5b.mp3) Regards, Adam, VA3AUM ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [January 31, 2025, 7:09pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/2 "2025-01-31T19:09:48Z")
Ughhh… I hope not. Testing this out now… ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [January 31, 2025, 7:17pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/3 "2025-01-31T19:17:35Z")
Yeah, that gremlin has popped up in the latest Pi image. Everyone running a Pi should immediately: ```bash apt-mark hold linux-image-rpi-v8 apt-mark hold linux-headers-rpi-2712 apt-mark hold linux-headers-rpi-v8 apt-mark hold linux-image-rpi-2712 ``` ---
**Author:** ![Chuck](https://community.allstarlink.org/user_avatar/community.allstarlink.org/chuck/32/3682_2.png) [@Chuck](https://community.allstarlink.org/u/Chuck)\ **Post date:** [January 31, 2025, 7:40pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/4 "2025-01-31T19:40:03Z")
6.6.62 apppears to be the lastest safe kernel on RPi. ---
**Author:** ![va3aum](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/e9bcb4/32.png) [@va3aum](https://community.allstarlink.org/u/va3aum)\ **Post date:** [January 31, 2025, 8:03pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/5 "2025-01-31T20:03:27Z")
Hello N8EI. Thank you for your prompt response in testing, confirming, and providing a temporary fix to this problem for users who haven’t already hosed their systems. I’m curious though, since I’ve already updated to the problematic kernel, and a hold would do me little good at this point, what would be the proper rollback procedure on a Pi appliance to a known good kernel? I’ve done this on vanilla Debian X86\_64 systems before, but never to a Pi. Yep, I failed to back up the card before upgrading. LOL. I’m usually good with backups, but of course, the one time you don’t… Thanks, Adam, VA3AUM ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [January 31, 2025, 8:20pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/6 "2025-01-31T20:20:28Z")
> [@Chuck](#): > > 6.6.69 apppears to be the lastest safe kernel on RPi. Did you mean to write 6.6.69? or 6.6.62? ---
**Author:** ![Chuck](https://community.allstarlink.org/user_avatar/community.allstarlink.org/chuck/32/3682_2.png) [@Chuck](https://community.allstarlink.org/u/Chuck)\ **Post date:** [January 31, 2025, 11:11pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/7 "2025-01-31T23:11:47Z")
6.6.62, corrected above. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [February 1, 2025, 12:40am UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/8 "2025-02-01T00:40:12Z")
I believe I have developed a hotfix for the issue. Please try: ```bash wget -O- https://repo.allstarlink.org/hotfix/asl3-pi12-kernel62-fix.sh | sudo bash ``` Note: this worked on my system but has not been widely tested. YMMV. Please report back. ---
**Author:** ![va3aum](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/e9bcb4/32.png) [@va3aum](https://community.allstarlink.org/u/va3aum)\ **Post date:** [February 1, 2025, 2:48am UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/9 "2025-02-01T02:48:14Z")
> [@N8EI](#): > > `wget -O- https://repo.allstarlink.org/hotfix/asl3-pi12-kernel62-fix.sh | sudo bash` Hello N8EI, Thank you! Thank you! You totally saved the day on this one for me! Your BASH script worked. Audio to/from the radio is fixed, and the Pi 4B reports: Linux ASL3-1 6.6.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 Thanks again! Adam, VA3AUM ---
**Author:** ![va3duk](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/7feea3/32.png) [@va3duk](https://community.allstarlink.org/u/va3duk)\ **Post date:** [February 1, 2025, 3:43am UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/10 "2025-02-01T03:43:20Z")
I’ve run this script on my own personal node with no issues at all, and things are running properly. I’m about to help a friend apply this fix to his node. I’ll report back. ---
**Author:** ![va3duk](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/7feea3/32.png) [@va3duk](https://community.allstarlink.org/u/va3duk)\ **Post date:** [February 1, 2025, 4:33am UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/11 "2025-02-01T04:33:24Z")
Hello, I applied this fix to a friends node as well and it went off without a hitch. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [February 1, 2025, 5:27pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/12 "2025-02-01T17:27:47Z")
A fix has been identified. Put the following in the file `/etc/modprobe.d/asl3-snd-usb-audio.conf`: ```txt options snd_usb_audio lowlatency=0 ``` Then reboot your system. This is being tested and packaged for a release today. ---
**Author:** ![KD5FMU](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kd5fmu/32/2113_2.png) [@KD5FMU](https://community.allstarlink.org/u/KD5FMU)\ **Post date:** [February 1, 2025, 7:35pm UTC](https://community.allstarlink.org/t/audio-problems-similar-to-x86-64-latest-kernel-in-latest-raspberry-pi-appliance-kernel/22829/13 "2025-02-01T19:35:37Z")
Worked for me. Raspberry Pi 4 using a URIx on ASL3