I’ve been trying on this on quite a variety on Intel CPU hardware.
Different chipsets different CPUs.
Should I bother trying it on and old AMD64 CPU computer?
It seems pretty universal; not sure what’s gained by more random testing.
Also just to create a little “same pageness”
I also tested my clean install just after installing ASL3 and rebooting BEFORE applying any kind of nodeconfig or restores.
Out of the box the node can “talk to itself” at nodenumber 1999 and is working with simpleusb.
And I am able to test the for the audio problem by enabling command *904
and testing it like that right out of the box from the asterisk console.
I upgraded my system that was “broke” from the -28 downgrade with the current hotfix and I’m up and running again 100%. Thank you!!! Wondering what my corner case could be tho, I thought I had a fairly “normal” system!
Thanks again.
Tom
I made some assumptions of package history that aren’t universally valid. I ended up building a VM and kept testing and rolling back.
Well it worked this time on my clean install.
“it” meaning:
wget -O- https://repo.allstarlink.org/hotfix/asl3-deb12-kernel28-fix.sh | sudo bash -x
Only thing different this time is I applied this script BEFORE configuring anything on the node out of the box using all defaults it came with.
A head scratcher for sure.
I’m not doing anything out of the ordinary with this test node config.
If you need me to share the config or backup file somehow I can.
I could also clean install again, apply my very simple node config as I was doing FIRST observer the expected noise issue by running *904 and then try applying the
script + reboot.
I also noticed your comment about building on a VM and testing…
So maybe the script has been updated or changed. And could be why it worked.
As said above, I fixed some stuff.
Great!
I was a bit slow at interpreting that exactly or noticing if W6NIJ comment meant he accomplished this with the single script. “the current hotfix”.
I just now scrolled up and noticed his post after trying this.
What’s next?
If I can be helpful in any way testing the newer kernel stuff please let me know.
I’m very interested in both being helpful if possible and learning new stuff.
Asking again if that’s alright: " “What’s next?”
And is there anything I can do on my end to help with testing newer kernels etc.
And are we just waiting on work from the Debian team (the bug report filed there) for this or
for what we do next.
Thanks!
-sg
I don’t expect meaningful help from Debian over a bug in an obscure module.
I’ve been working over the weekend on changes to the asl3 package to include a script that can be run that will automatically configure Bookworm Backports, install the latest 6.11 kernel from backports, and rebuild DKMS for the 6.11 kernels.
I will be starting a new forum thread specifically for testing that process and reporting on status of that. But the general workflow will be:
- Get the latest asl3 package
- The latest package will have a warning that you need to run
asl-kernel-manager - The script will be run and prompt you to reboot
- Reboot and everything should be running on Linux 6.11 with a functional USB sound
1 Like
Thanks!!
Happy to test it out when you are ready.
Take care.
-sg
Reopening this topic due to Pi problems now.
A fix has been identified. Put the following in the file /etc/modprobe.d/asl3-snd-usb-audio.conf:
options snd_usb_audio lowlatency=0
Then reboot your system. This is being tested and packaged for a release today.
I can confirm that this fix works on RPi 3 with kernel 6.6.74.