Do an apt update followed by apt upgrade.
Iām seeing this same issue on a node I built today.
I have one mini PC w/ASL3 that has not been updated in a few weeks and it works perfectly.
I built a new node today for a customer and loaded a clonezilla image of the above node onto it and then did an apt update & upgrade. This node now gives crackly Tx audio exactly like in OPās youtube video. URI and radio are identical thus appears the apt upgrade is what broke things. Fortunately I have lots of clonezilla images so looks like Iāll be sticking with those and not updating for now. TIA for any help in finding and fixing the cause of the issue.
1 Like
Well I did that of course ā yesterday
and it remained on .29
Tried again today.
Itās now
uname -a
Linux ASL3 6.1.0-30-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.124-1 (2025-01-12) x86_64 GNU/Linux
The problem still persists, no different.
Thanks!
And:
apt update
Hit:1 Index of /debian bookworm InRelease
Hit:2 Index of /debian bookworm-updates InRelease
Hit:3 Index of /debian-security bookworm-security InRelease
Hit:4 Index of /public/ bookworm InRelease
Reading package listsā¦ Done
Building dependency treeā¦ Done
Reading state informationā¦ Done
All packages are up to date.
Good to know.
Thanks for reporting the same is happening on your end.
I opened a bug report at: ASL3 Debian12 app_rpt interrupted/distorted USB device transmit audio on current and recent kernel updates Ā· Issue #456 Ā· AllStarLink/app_rpt Ā· GitHub
I wish to continue work on it here if anyone has any ideas.
I will keep both updated and in sync.
-Steve
N8LBV
Hereās a question for those who are experiencing this issue.
Q? do you have any pre-upgraded systems that are not experiencing the problem? If so, can you capture the output from :
sudo asl-show-version
Then, can you capture the output from the same command on a system where you are hearing the distortion. Even better if you can capture the output from a system running the same or very similar hardware.
What Iām trying to understand is whether your update/upgrade was just OS packages or whether there were also ASL3 package updates.
I built up a new system today (Dell Wyse 3040/URI100/HT) and noticed this audio issue as well.
I have an older node working that does not have this issue at all (Dell Wyse 3040/Rim/Maxtrac). The results of sudo asl-show-version (of the older node NOT showing this issue) are listed below:
********** AllStarLink [ASL] Version Info **********
OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-28-amd64
Asterisk : 20.11.0+asl3-3.2.0-2.deb12
ASL [app_rpt] : 3.2.0
Installed ASL packages :
Package Version
============================== ==============================
allmon3 1.4.2-1.deb12
asl3 3.6.0-1.deb
asl3-asterisk 2:20.11.0+asl3-3.2.0-2.deb12
asl3-asterisk-config 2:20.11.0+asl3-3.2.0-2.deb12
asl3-asterisk-modules 2:20.11.0+asl3-3.2.0-2.deb12
asl3-menu 1.11-1.deb12
asl3-update-nodelist 1.5.1-1.deb12
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-4+asl
dahdi-linux 1:3.4.0-4+asl
Iād be glad to help with this. I was troubleshooting the audio problem until I stumbled across this.
Thank you everyone for all you do to support this effort.
Tom
1 Like
Here is the version information from the newly built system that is exhibiting this audio issue (Same compute hardware, Dell Wyse 3040).
********** AllStarLink [ASL] Version Info **********
OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-30-amd64
Asterisk : 20.11.0+asl3-3.2.0-2.deb12
ASL [app_rpt] : 3.2.0
Installed ASL packages :
Package Version
============================== ==============================
allmon3 1.4.2-1.deb12
asl3 3.6.0-1.deb
asl3-asterisk 2:20.11.0+asl3-3.2.0-2.deb12
asl3-asterisk-config 2:20.11.0+asl3-3.2.0-2.deb12
asl3-asterisk-modules 2:20.11.0+asl3-3.2.0-2.deb12
asl3-menu 1.11-1.deb12
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-4+asl
dahdi-linux 1:3.4.0-4+asl
Can you try booting into the -28 kernel on the box thatās running -30 and see if the issue persists?
On my end not really-
This system was installed yesterday.
At the GRUB menu my only options are -25(old) and -29(new).
Presumably- it was -25 when installed then after apt update apt upgrade it went to -29. (yesterday).
If I do an apt update + apt upgrade now it will go to -30 and then my only boot options will be -29 or -30.
I tried booting with -25 and with this - the USB device does not work at all (no flashing status LED) and throws errors if you try to run anything in the alignment menu that acceses the USB audio device.
Rebooting back to -29 makes it work again.
My production system which is now on -30 is remote and I do not have easy access right now to grub or booting a different kernel.
This was updated earlier today - Iām guessing the only kernel options will also be -29 or -30
If thereās anything I can do on my end please let me know.
Put me to work if I can do anything.
I have a good high level understanding of how things work but I would really like to learn more.
Iām not a programmer developer but I keep seeing that I think I need to dive into it and start learning new things.
Iād like to better understand app_rpt and the audio hardware and how the audio/buffering and all that works.
I donāt think there is any really good āblock level diagramā how all the software works how interrupts are serviced and all that.
I also have no idea how to revert to previous kernels other than Debianās default single previous kernel.
I tried reverting to -25 kernel on one of our boxes and this resulted in the USB audio device not working at all and not being able to use it āno matter what I triedā and I had to put it back to -29.
There are obviously some kind of dependencies that do not let this work, and as discovered: I canāt just go back to a previous kernel willy-nilly.
-25 and -29 were my only choices in the grub boot menu (as detailed on the forum and no response yet).
I also realize this is not really the place for these type of questions.
But just want to take this opportunity to put forth I want to learn and work on this stuff!
And this problem seems like a great opportunity for me to start learning more and get into the areas of work I am actually very interested inā¦ lower level hardware stuff.
-SteveG
Since it sounds like -28 was still working for most people, it would be helpful for people having the problem to install it and see if the problem is there - i.e. does it vary depending on what kernel is installed. This is doable by:
apt install linux-image-6.1.0-28-amd64
Then you should be able to reboot and select the -28 kernel. Nothing about -25 should be broken so the report of -25 being a problem is likely a configuration or USB-moved issue.
Also, is this limited to a particularly platform like those Dell Wyse 3040s?
No, itās not limited to Dell 3040s at all.
It was asked if somebody could post software versions and other items on exact same hardware if available and somebody did.
I am testing on totally different systems (that are not anything like a Dell 3040) and having the same problem.
Iāll try the: apt install linux-image-6.1.0-28-amd64
And see if this gives me the option to boot -28 and try it if it does.
When I tried the -25 there were no configuration changes or USB-moved issues.
It just ādoes not workā.
From what I can tell this was the installed kernel when it was installed, then running update/upgrade immediately after install/reboot brought this to -29 before ever installing ASL3.
-25 really does not work.
If you want- I can try loading that again (before it gets wiped or gone by updates etc. and troubleshoot it further why it does not work.
But really, it does not!
Do we really want to spend any time on that? or should we keep trying to move forward with -28 -29 and now -30 which is what you get if you update.
Iāll see if I can actually try -28 that easily.
I was able to switch to -28 as suggested, but just like I mentioned with switching to -25, āit doesnāt workā.
USB audio device cannot be communicated with anymore no flashing status LED on USB device.
Any kind of reboot or replugging has no affect.
Switching back to -29 works fine.
[2025-01-16 15:55:39.657] ERROR[879] loader.c: res_timing_dahdi declined to load.
[2025-01-16 15:55:39.721] NOTICE[922] app_rpt.c: Normal Repeater Init 272981
[2025-01-16 15:55:39.722] WARNING[927][C-00000001] chan_dahdi.c: Unable to open '/dev/dahdi/pseudo': No such file or directory
[2025-01-16 15:55:39.722] ERROR[927][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-01-16 15:55:39.722] ERROR[927] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-01-16 15:55:39.723] NOTICE[928] chan_simpleusb.c: Channel 272981: Automatically assigned USB device 1-2:1.0 to SimpleUSB channel
[2025-01-16 15:55:39.780] WARNING[927] app_rpt.c: Disabled broken repeater 272981
root@OctoASL:/var/log/asterisk#
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@OctoASL:/var/log/asterisk#
Your system has skewed kernel structure and is missing DAHDI not the USB card. Do the follolwing:
apt install linux-headers-$(uname -r)
apt install --reinstall dahdi-dkms
modprobe dahdi
modprobe dahdi_dummy
modprobe dahdi_transcode
Well that was very helpful.
Thanks.
I had no idea how to pull that off on my own or that I needed to.
Up & running on -28 now with all that done.
Audio problem is gone!
asl-show-version
dpkg-query: no packages found matching cockpit*
********** AllStarLink [ASL] Version Info **********
OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-28-amd64
Asterisk : 20.11.0+asl3-3.2.0-2.deb12
ASL [app_rpt] : 3.2.0
Installed ASL packages :
Package Version
============================== ==============================
asl3 3.6.0-1.deb
asl3-asterisk 2:20.11.0+asl3-3.2.0-2.deb12
asl3-asterisk-config 2:20.11.0+asl3-3.2.0-2.deb12
asl3-asterisk-modules 2:20.11.0+asl3-3.2.0-2.deb12
asl3-menu 1.11-1.deb12
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-4+asl
dahdi-linux 1:3.4.0-4+asl
So we have some kind of kernel problem newer than -28?
What do we do next?
Also consider me an active beta tester by all means by now since maybe a month ago.
It looks like -29 and -30 have some sort of bug that causes problems. On a radio-less node I cannot replicate the problem so I suspect itās with the PCM-OSS module and not DAHDI. Iām going to build an amd64 node this weekend on a spare laptop and do some testing.
How potentially destructive are you comfortable with? The other thing to test would be if enabling bookworm-backports and installing kernel 6.11 also addresses the issue.
I have test nodes on the bench: Destruction sounds fun- itās no big deal to just mess these up
and re-install if needed and try all sorts of things.
Iāve been living with the audio problem on our on the air āproduction systemā.
I may roll it back to -28 however thatās not very convenient.
Itās remote, needs a KB and monitor hooked up to mess with the kernel.
And I still would need to figure out how to boot the alternate kernel by default.
It may be just a simple grub edit but Iām not sure and never done that yet.
My preference on the production node is just to wait that out for a real fix while temporarily living with the transmit audio issue.
I have some time this weekend to play.
Your kernel (and other stuff) rollback was a bit over my head as I do not fully understand all the parts that make this work and how they work.
Iād like to better understand.
This appears to be a major and global problemā¦ Meaning any/all PC new installs AND ones that have simply been updated recently are subject to this problem.
I suspect this will be worked out soon due to its severity and potential widespread problems once it is really impacting more users.