Re: udev rules help with usb>serial adapters
Hello Dave MM0RFN & John AC6SL
Thank you so much for chiming in.
I will admit much of this is beyond my understanding. However, I'm
going to add the output files from this end.
As you can see, the rule for my Kenwood radio port works perfectly. Yet
every iteration I've tried for the dual port has failed.
I have difficulty trying to understand this syntax, or really
understanding it. Bugger. But I have to be close. Since I posted my
first message, the new "Bmax Mini PC B3" has arrived! So I really need
to dial this in so I can port it to the replacement computer.
I had to reboot the computer several times during power outages. So
understand that some commands might look at one port then another port
for same device. The devices change places each boot. The glory is at
least my Kenwood now stays working!
I'll need both ports of the dual port USB>serial cable; one for my aprs
Igate, the other for my packet.
If either of you can cobble a rule for this adapter, I'm MORE THAN
WILLING to try it!
Thank you! 73
Jaye ke6sls
On 11/7/24 4:13 PM, Dave Hibberd wrote:
> Hi Jaye,
>
> On Thursday, 7 November 2024 22:56:52 GMT MJ Inabnit wrote:
>> I am going to retire an old thinkpad with a real serial port. Found
>> some good how-to about writing a udev rule to id and make new device for
>> usb to serial adapters. One rule works great for my TS-590sg, but my
>> second adapter (which has two serial ports) rule isn't working.
>>
>
> We have been doing similar in my online club - sadly it's 2 TNCs with onboard
> USB/Serial devices not 2 ports on one adaptor. I do have one of those *and* a
> radio that enumerates as 2 serial ports attached just now, so that'll maybe
> help to point you in the right direction!
>
>> Is there anyone here able to assist. If not, perhaps someone can point
>> out where I might get some assistance? Googled for weeks and not
>> finding the key to my rule.
>
> We've been using serial numbers to modify the symlink so the ports have their
> service name on them, see the first part of the linux notes:
> https://wiki.oarc.uk/packet:ninotnc?s[]=udev#misc_linux_notes
>
> How is the device enumerating currently - I assume it's connecting and
> presenting new ports in `/dev` ?
>
> What about somewhere like `/dev/serial/by-id`?
> If I look in my raspi's /dev/serial/by-id, I see what is in the attached text
> file.
>
> Reading `udevadm info -a /dev/ttyUSB0` and `udevadm info -a /dev/tty/USB1` has
> pointed me to ATTRS{bInterfaceNumber}=="00" - I wonder if there is a way to
> combine that, the serial number of the adaptor ATTRS{serial} to create
> different devices.
>
> There was also a hint of this approach here, where the two serial ports showed
> different serial numbers and that was used to give then pretty names:
> https://wiki.oarc.uk/persistent_sound_interface?
> s[]=udev#transceiver_device_names
>
> Hopefully that's enough of a starter for you to break the deadlock! If not,
> feel free to reach out again.
>
> Cheers,
> --
> Hibby <hibby@debian.org>
> Debian Developer
> Packet Radioist
> MM0RFN
>
--
wishing you well
Jaye, ke6sls--via the toshiba w/thunderchicken
Reply to: