Bob Bob wrote:
Just an extra thought or two Dean

Have you tried setting up soundmodem or a vanilla TNC with the same box?
Thinking in terms of checking that AX25 is working in the kernel properly.

I wonder if "baycom-com2" can be a real valid port name. Mine have
always been real short names like "radio".

Is 300ms long enough TXD for your TX?
I am starting to wonder about the kernel also. I was not able to get
Harv's Knoppix to load properly on this Notebook, but I was able to get
AFU Knoppix (2.4 kernel) to load. It all worked fine, the Windows /
PK-232 decoded the packets perfectly. I knew that the UART worked fine
when booted with DOS and this now leads me to think that it is OK with
Linux AX.25. I used baycom-com2 as the port name and also 300ms was
plenty for the TX Delay.


Is the PK232 DCD only based on audio present (unsquelched) or has it
detected a valid set of tones? (ie soft DCD)
It is just audio present, nothing fancy.


And rather than using "call" also try and ping a box in the interface
subnet and monitoring the activity on the other PC (say 192.168.10.11).
I can never remember whether connect mode (ie "call") runs on top of the
IP interface or at a layer beneath...
Tried that also. Same result, sounds like packet, but nothing usable
on Windows / PK-232 terminal.

Have you tried telling setserial uart 8250?
Yes, however the Baycom module needs control of the UART, so this will
not fly. You can still load the module, but the network interface will
not come up, since it sees a conflict with the serial module. Seems
strange until you see how the baycom module works.

I will have to try making a new Harv's Knoppix CD and see if that will
load OK. I am starting to wonder about Baycom with 2.6 kernels.

Thanks

Dean KD4TWJ