Hi again,


After having had some basic success using the Baycom ser12 modem with Linux
(linkt worked, though pms was somewhat stubborn), I tried to upgrade to a
Baycom par96, which left me with a bunch of new problems at the lowest level.

After compiling the suitable module it loaded perfectly upon a "modprobe
baycom_par" (as well as "modprobe baycom_par mode="par96*") command:

betazed:~# lsmod
Module                  Size  Used by
parport_pc              5632   0  (autoclean) (unused)
baycom_par              4736   0  (unused)
parport                 6852   0  [parport_pc baycom_par]
hdlcdrv                 7032   4  [baycom_par]
ax25                   35136   0  [hdlcdrv]
...

However, I am unable to configure the corresponding port:

betazed:~ # ifconfig bcp0
bcp0      Link encap:AMPR AX.25  HWaddr LINUX-1
          [NO FLAGS]  MTU:256  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          Base address:0x378

betazed:~ # ifconfig bcp0 hw ax25 DL8AM-15 up
SIOCSIFFLAGS: Device not configured

but then...

betazed:~ # ifconfig bcp0
bcp0      Link encap:AMPR AX.25  HWaddr DL8AM-15
          RUNNING  MTU:256  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          Base address:0x378

Apparently it adapted the call, still I cannot use that port:

betazed:~ # call pr DB0FC
axconfig: port pr not active
call: no AX.25 port data configured

Even though "pr" is defined in /etc/axports:

# /etc/ax25/axports
#Name   Rufzeichen      Baudrate        PacLen  MaxFrame        Beschreibung
pr      DL8AM-15        9600            256     3

This leaves me clueless. The are no problems like this when I use the serial
Baycom.

And there is another thing. It seems like my copy of sethlc is broken (I got
it from the SuSE 6.2 update directory as part of ax25tool-0.0.3-8.i386.rpm).
No matter what command line parameter is given, it _always_ prints out the
syntax help:

betazed:~ # sethdlc -i bcp0 -a txd 200 slot 50 ppersist 128 half
sethdlc: Version 0.5; (C) 1996-1997 by Thomas Sailer HB9JNX/AE4WA
sethdlc: invalid option -- i
usage: sethdlc [-b] [-i] [-d] [-i <baycomif>] [-h] [-c <cal>]
[-p] [hw <hw>] [type <type>] [io <iobase>] [irq <irq>] [dma <dma>]
    [options <opt>] [serio <serio>] [pario <pario>] [midiio <midiio>]
[-a] [txd <txdelay>] [txtail <txtail>] [slot <slottime>]
    [ppersist <ppersistence>] [full] [half]
  -a: set or display channel access parameters
  -b: trace demodulated bits
  -s: trace sampled input from tcm3105 (ser12 only)
  -d: trace dcd and ptt status on stdout
  -i: specify the name of the baycom kernel driver interface
  -c: calibrate (i.e. send calibration pattern) for cal seconds
  -h: this help

This also happens when I use the Baycom ser12. Has anybody else noticed the
same problem?

Well, you see, I am quite stuck here. Please help! :-)


73,
Martin

Reply via email to