Hello Tom,
As noted you could try bcs[fh]0, but wasn't told that this depends on
which kernel version.
If using 2.2.xx use bcs[fh][01234] and correct ax25utils etc. If still
using 2.0.xx i suggest upgrading to 2.2.xx(specially for the baycom-kiss
to baycom-network interface changes).
On Thu, 22 Jul 1999, Tom Edwards wrote:
> Hi I would be most pleased if anyone could help me with this little conundrum.
>
> I have a BayCom Serial modem and I believe I compiled support into the
> Kernel (I used menuconfig and it had a [*] and everything!!!) and now I am
> trying to get the bc0 devices going.
Why not use modules ?
> I have tried using the sethdlc -i bc0 mode "Ser12*" io 0x2d8 irq 3
> howver it comes back with....
>
> sethdlc: Version 0.5, (C) 1996 - 1997 by Thomas Sailer HB9JNY/AE4WA
Same verison here.
> sethdlc: Error No such device (19), Cannont ioctl bc0
Use correct devicename
>
> I am trying to set it up on what would be COM2 in DOS or ttyS1 and have tried
> setserial /dev/ttyS1 uart none
>
> but it has no effect.
>
> Does this support actually require the device to be plugged as the cable I
> have is a little dodgy and so may be the problem.
Nope, driver doens't care much.
> I also do not have it
> connectted to a radio at the moment. Am I right in beliveing that this
> should not affect operation.
Nope, just connect baycom after proper configuration.
> Many Thanks
>
> Tom Edwards
>
> ps the modem is an RS232
>
I tested baycom with using modules (speaking about 2.2.xx) by using:
# cat ./test-baycom-sf.sh
#!/bin/sh
set -v
setserial /dev/ttyS1 uart none
sleep 1
insmod hdlcdrv
# choose inmod options or use sethdlc
#insmod baycom_ser_fdx mode="ser12*" iobase=0x2f8 irq=3
#first baycom modem
sethdlc -p -i bcsf0 mode "ser12*" io 0x2f8 irq 3
#second baycom modem
#sethdlc -p -i bcsf0 mode "ser12*" io 0x2f8 irq 3
sethdlc -a -i bcsf0 txd 300 txtail 50 slot 150 ppersist 32 half
#sethdlc -a -i bcsf1 txd 300 txtail 50 slot 150 ppersist 32 half
sleep 1
ifconfig bcsf0
sleep 60
rmmod baycom_ser_fdx
rmmod hdlcdrv
and
# cat ./test-baycom-sh.sh
#!/bin/sh
set -v
setserial /dev/ttyS1 uart none
sleep 1
insmod hdlcdrv
#
#insmod baycom_ser_hdx mode="ser12*" iobase=0x2f8 irq=3
#first baycom modem
sethdlc -p -i bcsh0 mode "ser12*" io 0x2f8 irq 3
#second baycom modem
#sethdlc -p -i bcsh0 mode "ser12*" io 0x2f8 irq 3
sethdlc -a -i bcsh0 txd 300 txtail 50 slot 150 ppersist 32 half
#sethdlc -a -i bcsh1 txd 300 txtail 50 slot 150 ppersist 32 half
sleep 1
ifconfig bcsh0
sleep 60
rmmod baycom_ser_hdx
rmmod hdlcdrv
With using in /etc/conf.modules:
# grep bcs /etc/conf.modules
alias bcsf0 baycom_ser_fdx
alias bcsf1 baycom_ser_fdx
alias bcsf2 baycom_ser_fdx
alias bcsf3 baycom_ser_fdx
alias bcsh0 baycom_ser_hdx
alias bcsh1 baycom_ser_hdx
alias bcsh2 baycom_ser_hdx
alias bcsh3 baycom_ser_hdx
(For some reason at testing time (1.3.xx) hdlcdrv would not load atomagic
at that thime on my machine, so perhaps insmod hdlcdrv is irrelevant.)
Arjan Filius
mailto:[EMAIL PROTECTED]
--------------------------------------------------------------
Argh! All right, so how am I supposed to work with Linux when
everything's already been done?! Can't these people leave some
broken MSDOS like parts so there's problems left to solve!?....
