Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Help with setup
|
Johnny Twist
Good day Direwolf Users,
I'm trying to setup my Raspberry Pi with Direwolf, and I'm just having a few issues.? Each time I boot up Direwolf, it's telling me that my USB audio dongle is in use. This is the output of arecord -l: card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio] ? ?Subdevice: 1/1 ? ?Subdevice #0: subdevice #0 This is the output of sudo lsof /dev/snd/*: lsof: Warning: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs ? ? ? ? Output information may be incomplete. Command ? PID ? USER ? FD ? TYPE ? DEVICE ? SIZE/OFF ? NODE ? NAME pulseaudi ? ?767 ? jtwist ? 36u ? CHR ? ?116,32 ? ? ? ? ? 0t0 ? ? ? ? ?272 ? ?/dev/snd/controlC1 I installed pavucontrol as the pdf suggests for pulse audio, and I'm not exactly sure what setting to adjust within that, everything looks right as far as I can tell. Thanks in advance, Johnny W5KV |
开云体育Hello Johnny, Can you share what you've configured for your ADEVICE lines in your direwolf.conf file? --David KI6ZHD On 10/11/2023 10:28 AM, Johnny Twist
wrote:
Good day Direwolf Users, |
|
toggle quoted message
Show quoted text
|
|
Hi Johnny,
The information you listed looks correct, but omits much that may be helpful in determining what is wrong. 1.) What exactly does Direwolf report when you start it (include any lines output prior to the error message) ? 2.) For completeness, also show what "aplay -l" outputs (Audio Playback devices) since "arecord -l" only shows Audio Capture Devices. 3.) Is user "jtwist" a member of group "audio" ? If in doubt, show the output of the "id" command. 4.) Probably the most important question is "what is in your direwolf.conf file ?" since that determines which audio device Direwolf tries to open. 73 Thomas KK6FPP |
开云体育Ok, that looks right.?You only have one copy of direwolf running, right? If you can, ?install something like lsof (list open files) and you can run that and look for the device to see if something else is grabbing the device.? --Mark?
|
开云体育Oh, as an aside, this is the line?ADEVICE ?plughw:1,0 and it should not be commented out..? -Mark
|
|
Johnny Twist
Thomas,
I get the following: Could not open audio device plight:1,0 for input Device or resource busy This means that some other application is using that device. The solution is to identify that other application and stop it. Pointless to continue without audio device. This is Direwolf 1.7 Beta Test 7 The 'id' command shows that I am a member of the (29,(audio)) group.? aplay -l shows the following: card 0: Headphones (bcm2835), device 0: bcm2835 headphones card 1: Device ?[USB Audio Device], device 0: USB Audio card 2: vc4hdmi [vc4-hdmi], device 0: MAI PCM i2s-hifi-0 Thanks so much! Johnny |
|
(1) Run the "cm108" utility and you should see something like this:
??? VID? PID?? Product????????????????????????? Sound????????????????? ADEVICE??????? ADEVICE??????????? HID [ptt] ??? ---? ---?? -------????????????????????????? -----????????????????? -------??????? -------??????????? --------- **? 0d8c 0012? USB Audio Device???????????????? /dev/snd/pcmC1D0c????? plughw:1,0???? plughw:Device,0??? /dev/hidraw0 **? 0d8c 0012? USB Audio Device???????????????? /dev/snd/pcmC1D0p????? plughw:1,0???? plughw:Device,0??? /dev/hidraw0 **? 0d8c 0012? USB Audio Device???????????????? /dev/snd/controlC1?????????????????????????????????????? /dev/hidraw0 (2)? Find the device path, under the sound column, which ends in c for capture.?? In this case, /dev/snd/pcmC1D0c . (3) Use lsof command to see what process has this device open.? e.g. $ lsof /dev/snd/pcmC1D0c COMMAND???? PID USER?? FD?? TYPE DEVICE SIZE/OFF NODE NAME direwolf 278160?? pi??? 4u?? CHR 116,56????? 0t0? 268 /dev/snd/pcmC1D0c 73, John WB2OSZ |
|
Johnny Twist
Hello John,?
?I entered that command and received an output of 2 pulse audio items, but when I went to restart the Pi, and came back in and entered the same command, those items were now gone, and I could pull up Direwolf and it said the device was now available. Weird! Not sure what I did, all I did was restart the Pi, and went back in to do that command again. Igate is now on the map. Thank you. Johnny W5KV |
|
Good morning folks,
I have a Linux box and the problem, that "ADEVICE plughw:1,0" in the config file does not work without complaining that a resource or device is busy. But commenting out this statement works, i.e. I can hear packet sound on the headphones. I am not sure if PTT cm108 works - because it is not yet checked. Here are some details of my situation: $ cm108 VID PID Product Sound ADEVICE ADEVICE HID [ptt] --- --- ------- ----- ------- ------- --------- ** 0d8c 013c USB PnP Sound Device /dev/snd/pcmC1D0c plughw:1,0 plughw:Device,0 /dev/hidraw0 ** 0d8c 013c USB PnP Sound Device /dev/snd/pcmC1D0p plughw:1,0 plughw:Device,0 /dev/hidraw0 ** 0d8c 013c USB PnP Sound Device /dev/snd/controlC1 /dev/hidraw0 $ lsof /dev/snd/pcmC1D0c pulseaudi 14545 username mem CHR 116,3 678 /dev/snd/pcmC1D0c pulseaudi 14545 username 36u CHR 116,3 0t0 678 /dev/snd/pcmC1D0c $ ps axv | grep 14545 14545 ? S<sl 0:05 186 40 2422663 21372 0.2 /usr/bin/pulseaudio --daemonize=no --log-target=journal I am currently a bit confused where I probably find the second process of the resource/device for isolating it, so that the plughw statement can be issued. It is up to now unclear why I see two lines after the lsof statement in my case and what actions could follow on. I would appreciate any helpful ideas on this matter. Greetings. Karl, DK7AL |
|
After a heavy tinkering session with the CM108 USB sound card this morning I managed to separate the bindungs of the USB sound card modem from the sound system of my Linux box. Now I can operate this item secure with the indication of "ADEVICE plughw:2,0" in the config file even after a reboot of my Linux box. If the LED D1 is permanently lid, which is a good indication that the chip is not in connection of the Linux system, further system calls will no longer appear via the USB sound card. After starting SW direwolf from CLI, D1 flashes on regular intervals and indicates it is in action by SW.
Now I am also impressed that the PTT (Pin 13) and COS (Pin 48) work both with the help of the CM108 chip. Time to bring these items in a plastic/metal box for a more durable handling in the next time. Thank you all. Greetings. Karl, DK7AL |
开云体育Hi Karl You have a pulseaudio installation. In many (but not all) of the basic Linux distributions the user cannot access the ALSA device directly, instead pulseaudio does that. This explains why on your first post that you had a resource busy error. The device list query allows a limited read only access of sorts. It also explains why it worked when you removed the audio device spec from the DIrewolf config file. This causes the default? sound car device under pulseaudio to be used. In most distros you would use "pavucontrol" to set which device is used by which application, and the per application volume controls, If the Linux box is dedicated for single app radio/sound card use then it is probably worth removing pulseaudio entirely. Giving your login user membership to the audio group may also work with pulseaudio left in place, but there may be random device locks if pulseaudio is left running. It is best to kill with "pulseaudio --kill" then checking the daemon has not respawned to test that direwolf is working okay. There are so many possible permutations how pulseaudio can be setup that I can only generalise. If pulseaudio is being used by direwolf you may run into (random load dependent) latency and PTT/audio window issues during transmit (RX works fine). The general recommendation is not to run it, although I have personally worked through the problems and use it here. Hope this info helps Cheers Bob VK2YQA
On 13/4/25 01:58, DK7AL wrote:
After a heavy tinkering session with the CM108 USB sound card this morning I managed to separate the bindungs of the USB sound card modem from the sound system of my Linux box. Now I can operate this item secure with the indication of "ADEVICE plughw:2,0" in the config file even after a reboot of my Linux box. If the LED D1 is permanently lid, which is a good indication that the chip is not in connection of the Linux system, further system calls will no longer appear via the USB sound card. After starting SW direwolf from CLI, D1 flashes on regular intervals and indicates it is in action by SW. Now I am also impressed that the PTT (Pin 13) and COS (Pin 48) work both with the help of the CM108 chip. Time to bring these items in a plastic/metal box for a more durable handling in the next time. Thank you all. Greetings. Karl, DK7AL |
|
have you run :
toggle quoted message
Show quoted text
aplay -l & a record -l to see what devices are on your ports ? On Apr 12, 2025, at 9:58 AM, DK7AL <dk7al@...> wrote: |
|
Yes Sir,
toggle quoted message
Show quoted text
that's what I did during my experiments and investigations. In the meantime I've managed to get my system running in good order. Thank you for your request. Greetings. Karl, DK7AL Am 13.04.25 um 02:37 schrieb uspt via groups.io: have you run : |
to navigate to use esc to dismiss