-
Notifications
You must be signed in to change notification settings - Fork 320
Description
On both the latest version of Raspberry pi os, ubuntu server 24.04 (for rpi) and server 22.04(for rpi)
Direwolf is failing to write to any /dev/hidraw* (substitute * for device number)
I get the following errors on all flavors of rpi:
Audio input device 0 error code -19: No such device
Write to /dev/hidraw3 failed, n=-1, errno=32
ERROR: PTT for channel 0 has failed. See User Guide for troubleshooting tips.
Audio input device 0 error code -19: No such device
This is with both the latest version of direwolf AND 1.7 on rpi across all OS versions listed above.
Oddly enough it starts to key up the radio and then fails with the errors above and then exits direwolf.
My config looks like this:
ADEVICE plughw:2,0
CHANNEL 0
MYCALL K*******
MODEM 1200
PTT CM108 (I have also tried with /dev/hidraw* where * represents hid device output when using cm108 utility)
GPSD
AGWPORT 8000
KISSPORT 8001
Now here is the interesting part:
Direwolf successfully keys up the radio (without gps puck data, not sure how to incorporate this) on windows 10 and windows 11 with version 1.7
Additionally when booting up from a Ubuntu USB of 24.04 for OS demo and running direwolf I get the following errors:
could not open /dev/hidraw1 for write, errno=13
Type "ls -l /dev/hidraw1" and verify that it has audio group rw similar to this:
crw-rw---- 1 root audio 247, 0 Oct 6 19:24 /dev/hidraw1
rather than root-only access like this:
crw------- 1 root root 247, 0 Sep 24 09:40 /dev/hidraw1
ERROR: PTT for channel 0 has failed. See User Guide for troubleshooting tips.
But I have modified the permissions to look like this VERBATIM.
--------Now here is the most interesting part------:
If I run direwolf as sudo in the usb bootable ubuntu (even though I shouldn't), it keys up the radio just fine, everytime and the packets sound normal with out ANY of the above errors.