RE: AX.25 on 2.6.8 kernel and sarge?
Xavier,
Thank you for youur response. Your success brings me hope!
My hardware is a little different than yours. My specifics are as follows:
-VIA EPIA 5000 Eden motherboard (this is a single-board computer w/1 pci
slot)
-Comtrol Rocketport 8 port serial port pci card
-1 TNC-X (kiss only tnc kit) on port #8 of the comtrol card (known as
/dev/ttyR7 to the kernel)
I can monitor the incoming APRS frames using minicom on /dev/ttyR7
successfully, so I think the serial hardware interface is working OK.
I've compiled in all the AX25 functionality into the kernel vs. modules. Do
you use modules or did you compile the AX25 stuff into the kernel?
Can you send me a copy of your ".config" for your 2.6.9 kernel?
One other detail of my problem is that "listen" outputs the following to the
screen before the Oops grabs control of the machine:
ax0: code 13 arg 147
ax0: code 8 arg 207
ax0: Hardware 235
Do you have any idea what this is? I suspect these are coming from the
kernel, but I haven't examined the source code yet to see if I can find out.
Thanks for your encouragement,
73 de Rick, KG4OFO
> -----Original Message-----
> From: François-Xavier ROL [mailto:f6fkq@free.fr]
> Sent: Friday, December 31, 2004 5:00 AM
> To: debian-hams@lists.debian.org
> Subject: Re: AX.25 on 2.6.8 kernel and sarge?
>
>
> Le Vendredi 31 Décembre 2004 05:45, Rick Bolen a écrit :
>
> Hello Rick
>
> My station server runs on a P4 box with Debian 2.6.9 the
> following hamradio
> services without any trouble :
>
> Ax25 stuff with 4 modem (9k6, 1k2, 300, 300) + 1 PTCII controller
> for Pactor2,
> all modem are connected to a 8 ports PCI serial card
> (X)Net 1.36 acting as an ax25 node
> digi_Ned for aprs digi
> aprsd acting as a tcp/ip server for the hamnet network, not connected to
> Internet.
> various hamradio applications under kde3
>
> Plus a bunch of tcp/ip services : apache2, bind9, samba3, dhcp3,
> wu-ftp, ntpd,
> etc... (you may have a look on http://linux-moon.org:81, which is
> a partial
> access to the web site made fully available only for the hamnet network
> 44.0.0.0)
>
> reading your command lines
>
> axports looks ok excepted your ttySx speed which looks low, the
> rule is to set
> it at two times the on air baud rate. Therefore any speed above
> 1200b should
> be ok.
> If you define an internal connection to a pseudo port the speed
> can be set at
> 0.
>
> kissattach is more curious : why /dev/ttyR7 ? Typing mistake for
> /dev/ttyS7 ?
> In this case 7 is not a common figure for a ttySx, generally 0 or
> 1 are more
> standard.
>
> in my kissattach I define the device : /dev/ttySx for serail ports, the
> axports name : aprs in your case, the IP address : 10.71.36.65 in
> your case
> and that's it
>
> Then in your case : "kissattach /dev/ttySx aprs 10.71.36.65"
> should be good
> enough
>
> for kissparms I am used to define :
> the port : -p aprs
> the duplex mode : -f n (means no duplex)
> the tx delay : -t 320 (very high value ! generally -t 200 works
> with standard
> tx, -t 30 is ok for data transceivers)
> the slot time : -s 320 (set at the same value of tx delay, with the same
> comment for the high value)
> the ppersist : -r 32 (settting value is 255 / by number of stations in
> network, that's mean your 32 is a very gentle value)
>
> so in your case : "kissparms -p aprs -t 320 -s 320 -r 32" is well ok.
>
> Your tnc should be put in kiss or smack mode, connected to the
> serial port and
> under tension before to launch kissattach an kissparms. If not
> you will loose
> all the kissparms setting in your tnc.
> One time I got a big kernel panic due to this problem.
>
> I hope this info will help you to find your mis-configuration
>
> 73 de Xavier, F6FKQ
>
> > Anyone have this working on a 2.6.x kernel?
> >
> > Using the following config for a kiss tnc...
> >
> > axports...
> > aprs KG4OFO-14 1200 255 2 MHz (1200bps TNC-X)
> >
> > then:
> > /usr/sbin/kissattach -l -v /dev/ttyR7 aprs 10.71.36.65
> > /usr/sbin/kissparms -p aprs -f no -l 50 -r 32 -s 320 -t 320
> >
> > ... after 30 seconds I'm getting Oops with:
> >
> > bad: scheduling while atomic!
> > <memaddress and function calls> etc,etc,
> >
> > I've installed everything from apt-get pointing to debian/testing
> >
> > 73
> > Rick
>
>
Reply to: