This was working great. (Fedora 14 current update - Xastir from CVS today)
PL-1203 USB to RS-232 to a KPC3+ (serial, no KISS), but I was using a
'keyspan' adapter. Switched to a 'no-name' PL-1203 adapter and now I can
no longer 'open' the TNC under interfaces. However, I can access the TNC
There's a bug in the PL2303 driver introduced in the latest kernel. Google the
correct name (I think it's PL2303) and linux bug and you should get details and
a workaround.
-Jason
___
Xastir mailing list
Xastir@lists.xastir.org
Yup, PL2303 is correct. However, it seems it might not be a 'bug' per
se. Seems it's becoming a larger problem. See below. FWIW, the
'workaround' didn't work for me here.
I'll test here by going back a few revs in kernel - see what happens.
73
2011-04-25: #12
I was hit with this
On 04/30/2011 07:16 PM, ka7o wrote:
I'll test here by going back a few revs in kernel - see what happens.
Nope - no change by going back to an older kernel, one I know things
have worked with in the past.
73
___
Xastir mailing list
On Sat, Apr 30, 2011 at 8:16 PM, ka7o k...@ka7o.net wrote:
Yup, PL2303 is correct. However, it seems it might not be a 'bug' per se.
Seems it's becoming a larger problem. See below. FWIW, the 'workaround'
didn't work for me here.
the workaround I recall involved a udev rule, IIRC.
-Jason
I'll have to dig further, one I found was
modprobe -r pl2303
modprobe pl2303
Digging
On 04/30/2011 07:30 PM, Jason KG4WSV wrote:
On Sat, Apr 30, 2011 at 8:16 PM, ka7ok...@ka7o.net wrote:
Yup, PL2303 is correct. However, it seems it might not be a 'bug' per se.
Seems it's becoming a
On 4/30/2011 9:08 PM, xastir-requ...@lists.xastir.org wrote:
Subject:
[Xastir] USB to RS-232 issue
From:
ka7o k...@ka7o.net
Date:
Sat, 30 Apr 2011 18:24:23 -0600
To:
Xastir - APRS client software discussion xas...@xastir.org
This was working great. (Fedora 14 current update - Xastir from CVS
DOH!
found the workaround - the
modprobe -r pl2303
modprobe pl2303
dance does work - so long as you point the NEW serial TNC interface in
xastir to ttyUSB0 and not ttyS0. ttySO simple doesn't exist, never will
work no matter what workarounds are attempted.
This workaround was mentioned
Yup, it's a kernel module. But it appears the problem isn't really in
the driver itself, but rather in a change in how the Kernel's serial API
is used.
But, It's beyond my abilities to verify one way or the other. All I know
is minicom and gpsd both work great - xastir don't.
73
On
