Direwolf Dev on Debian Trixie, hamlib looking for ttyS0, not ttyACM0

[craigerl]

Per topic, direwolf.conf specified ttyACM0, however direwolf log shows hamlib trying to open ttyS0

grep ^PTT /run/direwolf.tnc.conf
PTT RIG 3085 /dev/ttyACM0

rigctld --version
rigctl Hamlib 4.6.2 2025-02-09T21:03:50Z SHA=870364 32-bit

direwolf -d t -d o -p -q d -t 0 -c /run/direwolf.tnc.conf
Dire Wolf DEVELOPMENT version 1.8 E (Sep 5 2025)
Includes optional support for: gpsd hamlib cm108-ptt libgpiod-2.2.1 dns-sd

Reading config file /run/direwolf.tnc.conf
Audio device for both receive and transmit: default (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, Tx AX.25.
Initializing GPIO common structure
Opening GPIO line 16 on chip /dev/gpiochip0
DCD 0 = 0
Hamlib determined CAT control serial port rate of 19200.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Hamlib Rig open error -6:
rig.c(947):rig_open entered
rig_settings_get_path: path=/home/pi/.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=1
serial_open: /dev/ttyS0
serial_open(335): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open**(/dev/ttyS0**) status=-6, err=No such file or directory
rig.c(1178):rig_open returning2(-6) IO error

rig.c(947):rig_open entered
rig_settings_get_path: path=/home/pi/.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=1
serial_open: /dev/ttyS0
serial_open(335): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
rig.c(1178):rig_open returning2(-6) IO error

IO error

[craigerl]

Not a real solution, but linking ttyS0 -> ttyACM0 works just fine

[craigerl]

MYCALL KM6LYW-2

IGSERVER noam.aprs2.net
IGLOGIN KM6LYW-2 00000

PBEACON sendto=IG compress=1 delay=00:15 every=30:00 symbol="igate" overlay=R lat=38.9999 long=-120.9999

DCD GPIOD gpiochip0 16

PTT RIG 3085 /dev/ttyACM0

DWAIT 0
TXDELAY 30
TXTAIL 10

AGWPORT 8000
KISSPORT 8001

[craigerl]

Disregard, compiled against local/old version of hamlib.

we had a slight weapons malfunction. But, everything's perfectly alright now. We're... fine. We're all fine here now. Thank you. How are you?

[wb2osz]

In case you hadn't heard, libgpiod v2 has a completely new API incompatible with v1.
Debian / RPi 13 trixie has this new library version.
Applications using libgpiod won't even come close to building if they have not been updated to accommodate v2 as well as v1.
I haven't tried it, but I think this means that an application, using GPIO, built on bookworm can't be copied over to trixie and expected to work.

See issue 590.

direwolf was updated a couple days ago and you have that updated version.
I can tell because it says: Includes optional support for: ... libgpiod-2.2.1 ...
Previously there was no version mentioned.

The good news is that, with trixie, the RPi 5 now has gpiochip0, same as all the others, for the user GPIO pins.

[craigerl]

Yah, I spent a day rewriting direwatch (https://github.com/craigerl/direwatch) which is a direwolf display driver, with GPIO Led's, displays etc. It's really a disservice to the maker community to completely break every bit of GPIO code and every document with each release of Debian.

Yay, gpiochip0! :) I still scan the lines on the chip to be sure. Given the history here, we can't make any assumptions about GPIO.

Thank you for porting direwolf to the new libgpio - we really appreciate it. I'm sure it's full of #defines in the wake of the GPIO destruction !

-craig
KM6LYW