Problem...

Problem...

[Pontus Falk]

Hi!

I try to get the AX.25 functions to work on my Linux box, but I've got
some problems...

I have compiled the kernel (2.4.18) according to the AX25 HOWTO. The new
kernel boots fine. I have compiled and installed libax25-0.0.10.tar.gz,
ax25-tools-0.0.8.tar.gz and ax25-apps-0.0.6.tar.gz according to the AX25
HOWTO.

I then edited the /etc/ax25/axports to look like

ax0 SM0RUX-2 9600 255 7 144.950 MHz
ax1 SM0RUX-7 9600 255 7 433.xxx MHz
sl0 SM0RUX-11 38400 255 7 SLIP

My TNC is a dual port KPC-4 connected to COM1.

Then I enter "/usr/sbin/mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1"
without any error messages (without any messages at all).

The I enter "/usr/sbin/kissattach /dev/ttyq0 ax0 44.140.16.35" but get an
error message like:

kissattach: Error setting line dicipline: TIOCSETD: invalid argument
Are you sure you have enabled MKISS support in the kernel
or, if you made it a module, that the module is loaded?

Any ideas?

Pontus/SMØRUX


-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Problem...

[pa3gcu]

On Monday 17 March 2003 21:07, Pontus Falk wrote:
> Hi!
>
> I try to get the AX.25 functions to work on my Linux box, but I've got
> some problems...
>
> I have compiled the kernel (2.4.18) according to the AX25 HOWTO. The new
> kernel boots fine. I have compiled and installed libax25-0.0.10.tar.gz,
> ax25-tools-0.0.8.tar.gz and ax25-apps-0.0.6.tar.gz according to the AX25
> HOWTO.
>
> I then edited the /etc/ax25/axports to look like
>
> ax0 SM0RUX-2 9600 255 7 144.950 MHz
> ax1 SM0RUX-7 9600 255 7 433.xxx MHz
> sl0 SM0RUX-11 38400 255 7 SLIP
>
> My TNC is a dual port KPC-4 connected to COM1.
>
> Then I enter "/usr/sbin/mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1"
> without any error messages (without any messages at all).
>
> The I enter "/usr/sbin/kissattach /dev/ttyq0 ax0 44.140.16.35" but get an
> error message like:
>
> kissattach: Error setting line dicipline: TIOCSETD: invalid argument
> Are you sure you have enabled MKISS support in the kernel
> or, if you made it a module, that the module is loaded?

And.?? Do you have "mkiss" support compiled into your kernel or is it a 
module, ?? looks like its a module so you need to load the module beforehand.

'modprobe mkiss'   ?????

If that fails then you possably do not have the required kernel configuration.
Check /usr/src/linux/.config for MKISS you could try;

cat /usr/src/linux/.config | grep MKISS
You should get CONFIG_MKISS=m or CONFIG_MKISS=y if you get
# CONFIG_MKISS is not set
that means you dont have mkiss at all.

> Any ideas?
>
> Pontus/SMØRUX
>

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Problem...

[Pontus Falk]

>> The I enter "/usr/sbin/kissattach /dev/ttyq0 ax0 44.140.16.35" but get
>> an error message like:
>>
>> kissattach: Error setting line dicipline: TIOCSETD: invalid argument
>> Are you sure you have enabled MKISS support in the kernel
>> or, if you made it a module, that the module is loaded?
>
> And.?? Do you have "mkiss" support compiled into your kernel or is it a
> module, ?? looks like its a module so you need to load the module
> beforehand.
>
> 'modprobe mkiss'   ?????
>
> If that fails then you possably do not have the required kernel
> configuration. Check /usr/src/linux/.config for MKISS you could try;
>
> cat /usr/src/linux/.config | grep MKISS
> You should get CONFIG_MKISS=m or CONFIG_MKISS=y if you get
> # CONFIG_MKISS is not set
> that means you dont have mkiss at all.

Yes, I have CONFIG_MKISS=y in /usr/src/linux/.config. But, I have
CONFIG_HAMRADIO=m if that is any problem. I don't know where to set this
to y in menuconfig... When I try to set it manually and recompile the
kernel I get an error message...

Pontus

Re: Problem...

[Shane Deering]

On Tue, 18 Mar 2003 09:09, Pontus Falk wrote:

> >
> > 'modprobe mkiss'   ?????
> >
> > If that fails then you possably do not have the required kernel
> > configuration. Check /usr/src/linux/.config for MKISS you could try;
> >
> > cat /usr/src/linux/.config | grep MKISS
> > You should get CONFIG_MKISS=m or CONFIG_MKISS=y if you get
> > # CONFIG_MKISS is not set
> > that means you dont have mkiss at all.
>
> Yes, I have CONFIG_MKISS=y in /usr/src/linux/.config. But, I have
> CONFIG_HAMRADIO=m if that is any problem. I don't know where to set this
> to y in menuconfig... When I try to set it manually and recompile the
> kernel I get an error message...
>
> Pontus

That looks like the redhat bug that stops default kernels from using ax25.
You can change it to "y" if you use "make xconfig" or edit by hand.

I've found the 2.4.18 kernel has unstable (buggy) ax25 and it would rarely run 
for more than a day without crashing. This is on Redhat 7.2. I haven't had 
that problem since compiling and installing 2.2.17-21mdk kernel over two 
weeks ago (and before trying 2.4 kernels).

-- 
Shane Deering                   Sent using Kmail v1.4.3
vk3bvp@qsl.net                  on Mandrake Linux, the Desktop OS
vk3bvp@vk3bvp.#sev.vic.aus.oc   MDK9.0 Up 43 minutes 
http://www.qsl.net/vk3bvp/      RH7.2 Up 16 days, 12 hours and 57 minutes 

Re: Problem...

[pa3gcu]

On Monday 17 March 2003 22:09, Pontus Falk wrote:

> > cat /usr/src/linux/.config | grep MKISS
> > You should get CONFIG_MKISS=m or CONFIG_MKISS=y if you get
> > # CONFIG_MKISS is not set
> > that means you dont have mkiss at all.
>
> Yes, I have CONFIG_MKISS=y in /usr/src/linux/.config. But, I have
> CONFIG_HAMRADIO=m if that is any problem. I don't know where to set this
> to y in menuconfig... When I try to set it manually and recompile the
> kernel I get an error message...

Why not do it the other way round, compile tham all as modules.

> Pontus
>

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

RE: Problem...

[Henk Remijn]

Pontus,

With lsmod you can check if modules are loaded.

1. I would not use 2.4.18, this was is buggy. Try a later kernel.
But this has nothing to do with your problem now.

2. Try to build as much drivers as modules, especially the ham radio ones.

If nothing is going to work, you might consider switching to debian. This
distro has ham-radio enabled by default. No kernel recompiling necessary.

73, Henk PA5KT

> -----Original Message-----
> From: linux-hams-owner@vger.kernel.org
> [mailto:linux-hams-owner@vger.kernel.org]On Behalf Of pa3gcu
> Sent: dinsdag 18 maart 2003 16:50
> To: Pontus Falk
> Cc: linux-hams@vger.kernel.org
> Subject: Re: Problem...
>
>
> On Monday 17 March 2003 22:09, Pontus Falk wrote:
>
> > > cat /usr/src/linux/.config | grep MKISS
> > > You should get CONFIG_MKISS=m or CONFIG_MKISS=y if you get
> > > # CONFIG_MKISS is not set
> > > that means you dont have mkiss at all.
> >
> > Yes, I have CONFIG_MKISS=y in /usr/src/linux/.config. But, I have
> > CONFIG_HAMRADIO=m if that is any problem. I don't know where to set this
> > to y in menuconfig... When I try to set it manually and recompile the
> > kernel I get an error message...
>
> Why not do it the other way round, compile tham all as modules.
>
> > Pontus
> >
>
> --
> Regards Richard
> pa3gcu@zeelandnet.nl
> http://people.zeelandnet.nl/pa3gcu/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Problem...

[bernard pidoux]

Henk Remijn wrote:

>Pontus,
>
>With lsmod you can check if modules are loaded.
>
>1. I would not use 2.4.18, this was is buggy. Try a later kernel.
>But this has nothing to do with your problem now.
>
>2. Try to build as much drivers as modules, especially the ham radio ones.
>
>If nothing is going to work, you might consider switching to debian. This
>distro has ham-radio enabled by default. No kernel recompiling necessary.
>
>73, Henk PA5KT
>
>  
>
>>-----Original Message-----
>>From: linux-hams-owner@vger.kernel.org
>>[mailto:linux-hams-owner@vger.kernel.org]On Behalf Of pa3gcu
>>Sent: dinsdag 18 maart 2003 16:50
>>To: Pontus Falk
>>Cc: linux-hams@vger.kernel.org
>>Subject: Re: Problem...
>>
>>
>>On Monday 17 March 2003 22:09, Pontus Falk wrote:
>>
>>    
>>
>>>>cat /usr/src/linux/.config | grep MKISS
>>>>You should get CONFIG_MKISS=m or CONFIG_MKISS=y if you get
>>>># CONFIG_MKISS is not set
>>>>that means you dont have mkiss at all.
>>>>        
>>>>
>>>Yes, I have CONFIG_MKISS=y in /usr/src/linux/.config. But, I have
>>>CONFIG_HAMRADIO=m if that is any problem. I don't know where to set this
>>>to y in menuconfig... When I try to set it manually and recompile the
>>>kernel I get an error message...
>>>      
>>>
>>Why not do it the other way round, compile tham all as modules.
>>
>>    
>>
>>>Pontus
>>>
>>>      
>>>
>>--
>>Regards Richard
>>pa3gcu@zeelandnet.nl
>>http://people.zeelandnet.nl/pa3gcu/
>>
>>    
>>

Here is my own experience (using Linux and AX25 applications for 3 years 
since kernel 2.0.19).
I was not able to achieve a normal functionning of Linux as soon as AX25 
was set up with mkiss connexions with any of 2.4.xx kernels. And I tried 
with different PCs.
In 2.4 kernel, there are major problems with interruptions (and kernel 
panics after a few minutes or hours) that should be corrected in kernel 
version under development (actually around 2.5.65) leading to a possible 
return to correct functionning (I hope) in 2.2.6 kernel.
I strongly suggest you use kernel 2.2.x (with x greater than 19, last is 
2.2.25) for AX25 purpose.
Thats what I am using without any serious problem with AX25 applications 
(two mkiss serial port handling 9600 and 1200 bauds links each, plus an 
ethernet 10 Mb LAN).
For example,  install Mandrake Linux distro 7.2, then update with 7.2 
update (february 2003 delivery or so) that can be found on any Linux 
distro mirror.
Then install (optionally) the last 2.2 kernel if you want.

Bernard Pidoux, F6BVP

Re: Problem...

[Jarmo]

On Tuesday 25 March 2003 18:42, bernard pidoux wrote:

> For example,  install Mandrake Linux distro 7.2, then update with 7.2
> update (february 2003 delivery or so) that can be found on any Linux
> distro mirror.
> Then install (optionally) the last 2.2 kernel if you want.
>
> Bernard Pidoux, F6BVP

Hi

I have all ax25 stuff compiled as modules and working like charm
in mandrake 9.0 with kernel 2.4.20.

Have one 9k6 port using 6pack...So with 2.4.x series kernel ax25
IS working fine...
Have tested 2.5.x series and there ax25 does not work....

Jarmo

Re: Problem...

[bernard pidoux]

Jarmo wrote:

>On Tuesday 25 March 2003 18:42, bernard pidoux wrote:
>
>  
>
>>For example,  install Mandrake Linux distro 7.2, then update with 7.2
>>update (february 2003 delivery or so) that can be found on any Linux
>>distro mirror.
>>Then install (optionally) the last 2.2 kernel if you want.
>>
>>Bernard Pidoux, F6BVP
>>    
>>
>
>Hi
>
>I have all ax25 stuff compiled as modules and working like charm
>in mandrake 9.0 with kernel 2.4.20.
>
>Have one 9k6 port using 6pack...So with 2.4.x series kernel ax25
>IS working fine...
>Have tested 2.5.x series and there ax25 does not work....
>
>Jarmo
>  
>

I am glad that your AX25 applications are working fine with Linux kernel 
2.4.x
I was only reporting that this is not the case when serial link are 
handled by mkiss.
I assume that it is a question of heavy interrupts load for I have 
traced the problem and found that kernel panics occur very often around 
the same address in ax25 input routines.
This is probably related to the lot of cli() instructions and the new 
way interrupts are managed in 2.4 kernels.
All these cli() sti() have been removed in 2.5 kernel. Thats why I hope 
mkiss will work again on 2.6.

Best 73 de Bernard, F6BVP

Re: Problem...

[pa3gcu]

On Tuesday 25 March 2003 16:42, bernard pidoux wrote:
> Henk Remijn wrote:
> >Pontus,
> >
> >With lsmod you can check if modules are loaded.
> >
> >1. I would not use 2.4.18, this was is buggy. Try a later kernel.
> >But this has nothing to do with your problem now.

> Here is my own experience (using Linux and AX25 applications for 3 years
> since kernel 2.0.19).

O, i used kernel 2.0.19 6 and one half years ago when it came out, you 
possably mean when you started using it.
I hope i am correct in the 6 + years as i checked on kernel.org, 2.0.19 is 
archived with a date of; Sep 11  1996, i'm getting older.....

> I was not able to achieve a normal functionning of Linux as soon as AX25
> was set up with mkiss connexions with any of 2.4.xx kernels. And I tried
> with different PCs.
> In 2.4 kernel, there are major problems with interruptions (and kernel
> panics after a few minutes or hours) that should be corrected in kernel
> version under development (actually around 2.5.65) leading to a possible
> return to correct functionning (I hope) in 2.2.6 kernel.

I have encountered problems when ifconfig'ing down a kiss interface in 2.4 
kernels, however that has been fixed now, i have tryed 2.4 kernels and my 
feelings are mixed, i certainly have not encountered any interrupt problems 
either with AX25 or Inet networking. Of course i am not saying there are none.

> I strongly suggest you use kernel 2.2.x (with x greater than 19, last is
> 2.2.25) for AX25 purpose.

I still use 2.2.19 with AX25, i have no problem what so ever with it. Or i 
should say the following.
  9:31pm  up 147 days, 18:25,  1 user,  load average: 0.00, 0.00, 0.00 
3 ethernet cards one scc card 3 IPIP links and AFAIK no problems.
The box is certainly not busy, but when it was years back it stayed up untill 
i buggered something up and for easyness sake hit the restset button because 
i was enoyed with myself otheriwse uptimes would have been higher.

> Thats what I am using without any serious problem with AX25 applications
> (two mkiss serial port handling 9600 and 1200 bauds links each, plus an
> ethernet 10 Mb LAN).
> For example,  install Mandrake Linux distro 7.2, then update with 7.2
> update (february 2003 delivery or so) that can be found on any Linux
> distro mirror.
> Then install (optionally) the last 2.2 kernel if you want.

IMHO 2.2.xx has yet to be beaten when it comes to stability.

I do however belive that my learned friend Henk PA5KT uses 2.4.xx kernels on 
his DXcluster gateway and it is always accessable.
The last time i saw him he mentioned he had no such problems with his 2.4 
kernel, now i hope i understood him properly.

>
> Bernard Pidoux, F6BVP
>

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

Re: Problem...

[M Taylor]

On Tue, Mar 25, 2003 at 05:42:14PM +0100, bernard pidoux wrote:
> 
> I was not able to achieve a normal functionning of Linux as soon as AX25 
> was set up with mkiss connexions with any of 2.4.xx kernels. And I tried 
> with different PCs.
> In 2.4 kernel, there are major problems with interruptions (and kernel 
> panics after a few minutes or hours) that should be corrected in kernel 
> version under development (actually around 2.5.65) leading to a possible 
> return to correct functionning (I hope) in [2.6.x -ve1mct] kernel.

Bugs can only be fixed if people take the time to make a bug report.

There are developers here willing to help you if you need assistance
with finding the cause of the problem. (Myself included, though I am
not a kernel developer)

One thing I would really like to know is if certain protocols cause
problems, i.e. does plain AX.25 cause problem, or NetRom traffic,
what about AXIP traffic? Did you have a large route table (that is,
are your an AMPRnet gateway)? Any idea of the CPU load when the kernel
panic occured? Was there multiple connections/traffic on different or 
same RF ports? Error messages in the syslog or messages file relating
to networking or amateur radio stuff?

The problems that exist in the 2.4 kernel also exist in the 2.2 kernel,
it is just that there are harder to trigger. They will become worst in
2.5/2.6 unless they are fixed, so the best time is now, while 2.5 is
still a development kernel.

Thank you,
ve1mct