开云体育

New Mint on Wo-We 73 Linux build - Packet modem failed to start

Dave Christensen All Messages By This Member #13371 My first time trying to run a new Mint/73Linux build on a Wo-We PC.? I am getting a PACKET modem failed to start AFTER seeing Conky Indicate that DIREWOLF is running but KISSATTACH failed to go ready.? I opened /etc/ax25/ax25ports and saw two entries for WL2K.? My other working system has only one so I took the extra one out.? Same results.? Where are the messages going that PAT Menu interprets as a modem failed to start? ? When I try the command listed in PATMenu for the Kiss attach (sudo /usr/sbin/kissattach /tmp/kisstnc) on both the working and non-working system I get the same error message: ? usage: kissattach [-b] [-l] [-m mtu] [-v] tty port [inetaddr] ? Any ideas? ? Thanks Dave ?
Marty Hartwell All Messages By This Member #13372 开云体育 Hi Dave I don't have any answer for you, but maybe you can help me a little. I also have a Wo-We and haven't found the magic way to get into the bios to overwrite the disk with my Xubuntu OS. Any help on the magic. Marty kd8bj On 11/19/24 12:33, Dave Christensen via groups.io wrote: toggle quoted message Show quoted text My first time trying to run a new Mint/73Linux build on a Wo-We PC.? I am getting a PACKET modem failed to start AFTER seeing Conky Indicate that DIREWOLF is running but KISSATTACH failed to go ready.? I opened /etc/ax25/ax25ports and saw two entries for WL2K.? My other working system has only one so I took the extra one out.? Same results.? Where are the messages going that PAT Menu interprets as a modem failed to start? ? When I try the command listed in PATMenu for the Kiss attach (sudo /usr/sbin/kissattach /tmp/kisstnc) on both the working and non-working system I get the same error message: ? usage: kissattach [-b] [-l] [-m mtu] [-v] tty port [inetaddr] ? Any ideas? ? Thanks Dave ?
Dave Christensen All Messages By This Member #13373 Oddly Enough..... ? I unplugged the USB radio interface cable to my IC-705 and moved it to another port on the Wo-We and no more KISSATTACH issues.? I moved it back to the original port and it worked there also.? So my problem is fixed but I don't know how if got fixed.
Dave Christensen All Messages By This Member #13380 Marty, I had a real problem getting into the Bios on my Wo-We.? I can confirm it is the F2 key but it didn't work until I unplugged my radio USB connection from the Wo-We.? I should note that I was using a mouse and keyboard that uses a USB Dongle and I was running the monitor on USBC.? I never could get the HDMI ports to work.? I suspect a driver issue.
Dave Christensen All Messages By This Member #13384 My problem of starting the Packet modem with PAT Menu is back.? It turns out that it isn't a KISSATTACH issue but a Wo-We PC/Direwolf issue.? Direwolf says that the audio codec for my IC-70r is in use by another process so it quits.? If I unplug my IC-705 and power off the Wo-We and power it on without connecting the IC-705, a aplay -l command still shows the audio codec available.? The codec I am using is: ? card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio] ? Subdevices: 0/1 ? Subdevice #0: subdevice #0 ? The Audio Codec for the IC-705 shows in a aplay -l command even when the radio is not connected and stays listed across reboots and power offs of the PC with the radio disconnected.? Leaving the PC powered off for some period still shows the audio codec there with the radio disconnected but will allow Direwolf to startup OK. ? A couple of questions: 1.? Is there a command to list processes attached to a device and how would I specify plughw 3:0 as the device I am interested in? 2.? Is there something in Mint that leaves a process attached to the codec? 3.? Is there something in the PC hardware that leaves the device busy from the last boot? ? This is a total mystery to me Thanks Dave ?
Dave Christensen All Messages By This Member #13385 Final Update to this problem (I hope) ? If I start the Wo-We BEFORE powering up a connected IC-705 the Packet modem will fail to start with a Direwolf message that the Audio Codec devices are in use by another process.? Rebooting does not clear this condition even with the IC-705 left powered on.? What clears this condition is if I shut the power off the Wo-We and let it sit for several minutes.? Make sure the 705 is powered up and then power up the Wo-We and it will work again. ? I don't know how but the Wo-We is maintaining the busy status of the audio codec device after a restart or a short power down, ? Any thoughts? ? Thanks. Dave ?

Previous Topic Next Topic