After much searching and gleaning of details from various on-line docs,
including the AX.25 Howto, I have reached a dead end with an attempt to
find a new use for an old Baycom serial modem. The flavor of Linux is
Gentoo 2.6.11 r3

The ultimate goal is to use it with Xastir, which appears to be
functioning properly.

The specific problem is with transmitted data. I can issue a CALL or
BEACON at the bash prompt and the radio transmits data that sounds like
2400bps packet. I am also monitoring the data from a Windows PC with
with a PK-232. Every time that I transmit from the Linux / baycom, DCD
is active on the PK-232 and it "sounds" like packet on the scanner, but
nothing shows on the terminal on the Windows PC. The monitor level on
the PK-232 is set to 6 (highest / most data).
I can change the radio connected to the Windows PC / PK-232 to 144.390
(APRS) and the data streams in like crazy.

I can boot the Linux PC with my old DOS / Baycom boot disk and
transmitted data is monitored fine on the Windows / PK-232 PC when I
transmit via the Baycom.

The Baycom is receiving fine on the Linux PC. I can fire up Xastir and
watch the local APRS activity, no problem.
Here are some of the config details:

AXPORTS
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
baycom-com2 KD4TWJ-9 1200 250 2 144.390 APRS (1200 bps)

:ifconfig bcsf1
bcsf1 Link encap:AMPR AX.25 HWaddr KD4TWJ-9
inet addr:192.168.10.10 Mask:255.255.255.0
UP RUNNING MTU:256 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:16
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x2f8

:sethdlc -i bcsf1 -a
sethdlc: Version 0.5; (C) 1996-1997 by Thomas Sailer HB9JNX/AE4WA
current parameters: TX delay 300ms, TX tail 300ms, slottime 100ms,
p-persistence 40/256, Half duplex

:sethdlc -i bcsf1 -p
sethdlc: Version 0.5; (C) 1996-1997 by Thomas Sailer HB9JNX/AE4WA
driver name: baycom_ser_fdx
current parameters: mode ser12* io 0x2f8 irq 3

If I use "Listen -a -h -p baycom-com2" while using Call in another
term, here is what I see;
baycom-com2: fm KD4TWJ-9 to KD4TWJ-1 ctl SABM+
baycom-com2: fm KD4TWJ-9 to KD4TWJ-1 ctl SABM+
baycom-com2: fm KD4TWJ-9 to KD4TWJ-1 ctl DISC+

I am cancelling Call after the second attemp, that is why DISC is the
third entry.
This looks like the right stuff.
It is as if the packets are empty by the time that they reach the radio
for transmission.
Any ideas?

Thanks

Dean