Hello Robert,
After banging into the "Error writing" issue, I used
your document to build direwolf DEV/1.8 on the most recent DRAWS
hat image Raspbian GNU/Linux 11 (bullseye)
starting the direwolf service still fails but no longer hangs the
service start
Can you be specific on which document you're following?? Btw, I
believe this impactful change is only for the Bookworm OS release
running the new 6.6.x kernel series. Bullseye with it's 6.1.x kernel
series is not impacted.
Jun 05 07:44:07? direwolf[15736]: Error writing "12"
to /sys/class/gpio/export, errno=22
Jun 05 07:44:07? direwolf[15736]: Invalid argument
Jun 05 07:44:07? direwolf[15736]: It looks like gpio with sysfs is
not supported on this operating system.
Jun 05 07:44:07? direwolf[15736]: Rather than the following form,
in the configuration file,
Jun 05 07:44:07 direwolf[15736]: ? ? PTT GPIO ?12
Jun 05 07:44:07 direwolf[15736]: try using gpiod form instead.
?e.g.
Jun 05 07:44:07? direwolf[15736]: ? ? PTT GPIOD ?gpiochip0 ?12
Jun 05 07:44:07 direwolf[15736]: You can get a list of gpio chip
names and corresponding I/O lines with "gpioinfo" comma>
Jun 05 07:44:07 systemd[1]: direwolf.service: Main process exited,
code=exited, status=1/FAILURE
Jun 05 07:44:07? systemd[1]: direwolf.service: Failed with result
'exit-code'.
You MAY want to add that installing gpiod and manually modifying
the direwolf config is needed
I believe the issue here is that you haven't installed and enabled
the gpiod system in your Bullseye system.? It might not even be
present in that OS.? As such, I recommend you REVERT your
configuration to use the non-GPIOD Direwolf configuration on your
system and you should be ok.
--David
KI6ZHD
