2.6.13 mkiss update?

2.6.13 mkiss update?

[Mike McCarthy, W1NR]

I am running opensuse 10.0 with kernel 2.6.13-15.7 and the mkiss module is 
broken.  In looking through the archives it appears that it got fixed in 
2.6.14.  Will there be a patch released for the 2.6.13 kernel that will 
propagate to the opensuse online update?  Where can I get the latest source 
file for mkiss that I can manually compile it under 2.6.13?

Thanks,
Mike, W1NR

Re: 2.6.13 mkiss update?

[Bob Nielsen]

I thought it was the ax25 module that was broken.  In any case,  
2.6.14 (and presumably 2.6.15) works, so you could try one of them.   
If there is some other reason why you need 2.6.13, download a later  
kernel and try replacing ax25.c and mkiss.c with the later versions  
and recompiling the kernel (this may or may not work, depending on  
other changes).  You can get the source from ftp.kernel.org in the / 
pub/linux/kernel/v2.6 directory.

Bob, N7XY
On Jan 4, 2006, at 8:22 AM, Mike McCarthy, W1NR wrote:

> I am running opensuse 10.0 with kernel 2.6.13-15.7 and the mkiss  
> module is broken.  In looking through the archives it appears that  
> it got fixed in 2.6.14.  Will there be a patch released for the  
> 2.6.13 kernel that will propagate to the opensuse online update?   
> Where can I get the latest source file for mkiss that I can  
> manually compile it under 2.6.13?
>
> Thanks,
> Mike, W1NR
>
> -
> 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: 2.6.13 mkiss update?

[oz6bl]

Bob Nielsen wrote:
> I thought it was the ax25 module that was broken.  In any case,
> 2.6.14 (and presumably 2.6.15) works, so you could try one of them.
> If there is some other reason why you need 2.6.13, ...

The 'problem' with Suse is that once they have made a release they stick
to the kernel version with which the original release was made. They will
provide security updates but not kernel updates. For this very reason I'm
seriously considering switching to e.g. Gentoo, because there you can
update the kernel. I use Gentoo on my router/gateway but am still on Suse
with my workstation.

Best 73 de Bent/OZ6BL

Re: 2.6.13 mkiss update?

[Bob Nielsen]

With any distribution (I think) you do not need to use their kernel  
(although sometimes there desirable patches).  For instance, I am  
running Ubuntu on both my Linux machines, using 2.6.14.2 kernels,  
although Ubuntu 5.10 comes with 2.6.12.  I took the Ubuntu  
config-2.6.12 file and copied it to /usr/src/linux/.config, ran 'make  
menuconfig' and
compiled my new kernels.  I think some of the distributions even  
package up their standard patches, although the stock kernel works  
fine for me (I needed ndiswrapper on one of the machines to use my  
unsupported 802.11g PCI card, but was able to find a Ubuntu package  
which allowed me to create the module with my new kernel).  I have  
been compiling my own kernels for about 11 years (when it was  
necessary to do so in order to  have AX.25 support) and have never  
run into insurmountable problems.

73, Bob N7XY

On Jan 4, 2006, at 12:46 PM, oz6bl@amsat.dk wrote:

> Bob Nielsen wrote:
>> I thought it was the ax25 module that was broken.  In any case,
>> 2.6.14 (and presumably 2.6.15) works, so you could try one of them.
>> If there is some other reason why you need 2.6.13, ...
>
> The 'problem' with Suse is that once they have made a release they  
> stick
> to the kernel version with which the original release was made.  
> They will
> provide security updates but not kernel updates. For this very  
> reason I'm
> seriously considering switching to e.g. Gentoo, because there you can
> update the kernel. I use Gentoo on my router/gateway but am still  
> on Suse
> with my workstation.
>
> Best 73 de Bent/OZ6BL
>
> -
> 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: 2.6.13 mkiss update?

[Mike McCarthy, W1NR]

I have no problem with kernel hacking and compilation when it involves a
desktop machine that is used for personal use, development and testing.
However, my production server is my DX cluster node, email server, WEB
server for multiple domains, time server, etc.  I have a real hard time
using a kernel outside of the normal support channels on production machines
that are exposed to the internet.  Currently, SuSE 10.0 ships with 2.6.13.
If the maintainer gets bug fixes (like the broken AX25 support) into the CVS
for it, then SuSE should pick them up for the next live update.  That would
make me real happy.  From what I have read, it did not get into .13 and may
not.  Looks like I will need to wait until 10.1.  For now, I tried the SuSE
kotd (kernel of the day) build 2.6.15 but loading the AX25 and mkiss modules
with that patched into 10.0 causes a hard lockup of the whole machine.  Next
I will try 10.1 alpha4 to see if that works.  Hopefully 10.1 will be better.

For now, my production machine will stay on SuSE 9.3.

Mike, W1NR


-----Original Message-----
From: linux-hams-owner@vger.kernel.org
[mailto:linux-hams-owner@vger.kernel.org] On Behalf Of Bob Nielsen
Sent: Wednesday, January 04, 2006 4:19 PM
To: linux-hams@vger.kernel.org
Subject: Re: 2.6.13 mkiss update?

With any distribution (I think) you do not need to use their kernel
(although sometimes there desirable patches).  For instance, I am running
Ubuntu on both my Linux machines, using 2.6.14.2 kernels, although Ubuntu
5.10 comes with 2.6.12.  I took the Ubuntu
config-2.6.12 file and copied it to /usr/src/linux/.config, ran 'make
menuconfig' and compiled my new kernels.  I think some of the distributions
even package up their standard patches, although the stock kernel works fine
for me (I needed ndiswrapper on one of the machines to use my unsupported
802.11g PCI card, but was able to find a Ubuntu package which allowed me to
create the module with my new kernel).  I have been compiling my own kernels
for about 11 years (when it was necessary to do so in order to  have AX.25
support) and have never run into insurmountable problems.

73, Bob N7XY

On Jan 4, 2006, at 12:46 PM, oz6bl@amsat.dk wrote:

> Bob Nielsen wrote:
>> I thought it was the ax25 module that was broken.  In any case,
>> 2.6.14 (and presumably 2.6.15) works, so you could try one of them.
>> If there is some other reason why you need 2.6.13, ...
>
> The 'problem' with Suse is that once they have made a release they 
> stick to the kernel version with which the original release was made.
> They will
> provide security updates but not kernel updates. For this very reason 
> I'm seriously considering switching to e.g. Gentoo, because there you 
> can update the kernel. I use Gentoo on my router/gateway but am still 
> on Suse with my workstation.
>
> Best 73 de Bent/OZ6BL
>
> -
> 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
>

-
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: 2.6.13 mkiss update?

[Mike McCarthy, W1NR]

I was successful in building 2.6.14-5 from source via kernel.org and loading 
and configuring ax25 on my 10.0 test system.  I have not yet connected a TNC 
and radio yet.  That will come next.  At least the modules load and 
kissattach works.

There are too many changes to easily back patch the sources to the 2.6.13 
kernel.  The SuSE kotd 2.6.15 build from January 2 hard locks the system 
when doing kissattach.  I hope that isn't a bad sign for future releases.

Once OpenSuSE 10.1 beta is available, I'll try loading that.  My production 
servers will stay at 9.3 until 10.1 gets officially released and I have 
tested it thoroughly.

Mike, W1NR

----- Original Message ----- 
From: "Bob Nielsen" <nielsen@oz.net>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: <linux-hams@vger.kernel.org>
Sent: Wednesday, January 04, 2006 12:03 PM
Subject: Re: 2.6.13 mkiss update?


>I thought it was the ax25 module that was broken.  In any case,  2.6.14 
>(and presumably 2.6.15) works, so you could try one of them.   If there is 
>some other reason why you need 2.6.13, download a later  kernel and try 
>replacing ax25.c and mkiss.c with the later versions  and recompiling the 
>kernel (this may or may not work, depending on  other changes).  You can 
>get the source from ftp.kernel.org in the / pub/linux/kernel/v2.6 
>directory.
>
> Bob, N7XY
> On Jan 4, 2006, at 8:22 AM, Mike McCarthy, W1NR wrote:
>
>> I am running opensuse 10.0 with kernel 2.6.13-15.7 and the mkiss  module 
>> is broken.  In looking through the archives it appears that  it got fixed 
>> in 2.6.14.  Will there be a patch released for the  2.6.13 kernel that 
>> will propagate to the opensuse online update?   Where can I get the 
>> latest source file for mkiss that I can  manually compile it under 
>> 2.6.13?
>>
>> Thanks,
>> Mike, W1NR
>>
>> -
>> 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
>>
>
> -
> 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: 2.6.13 mkiss update?

[Joni Bäcklund]

I can confirm that running kissattach produces kernel panic with 2.6.15. 
So do not use it until there is a patch available ! Seems that kernel 
ax25 developers are not quite sync with the kernel network code..

I have 2.6.14.5 running quite fine, tested both with kiss and 6pack. 
Also 2.6.13.X seriers runs fine with
6pack TNC driver that is way better than kiss anyhow :)

Joni

Mike McCarthy, W1NR wrote:
> I was successful in building 2.6.14-5 from source via kernel.org and 
> loading and configuring ax25 on my 10.0 test system.  I have not yet 
> connected a TNC and radio yet.  That will come next.  At least the 
> modules load and kissattach works.
> 
> There are too many changes to easily back patch the sources to the 
> 2.6.13 kernel.  The SuSE kotd 2.6.15 build from January 2 hard locks the 
> system when doing kissattach.  I hope that isn't a bad sign for future 
> releases.
> 
> Once OpenSuSE 10.1 beta is available, I'll try loading that.  My 
> production servers will stay at 9.3 until 10.1 gets officially released 
> and I have tested it thoroughly.
> 
> Mike, W1NR
> 
> ----- Original Message ----- From: "Bob Nielsen" <nielsen@oz.net>
> To: "Mike McCarthy, W1NR" <lists@w1nr.net>
> Cc: <linux-hams@vger.kernel.org>
> Sent: Wednesday, January 04, 2006 12:03 PM
> Subject: Re: 2.6.13 mkiss update?
> 
> 
>> I thought it was the ax25 module that was broken.  In any case,  
>> 2.6.14 (and presumably 2.6.15) works, so you could try one of them.   
>> If there is some other reason why you need 2.6.13, download a later  
>> kernel and try replacing ax25.c and mkiss.c with the later versions  
>> and recompiling the kernel (this may or may not work, depending on  
>> other changes).  You can get the source from ftp.kernel.org in the / 
>> pub/linux/kernel/v2.6 directory.
>>
>> Bob, N7XY
>> On Jan 4, 2006, at 8:22 AM, Mike McCarthy, W1NR wrote:
>>
>>> I am running opensuse 10.0 with kernel 2.6.13-15.7 and the mkiss  
>>> module is broken.  In looking through the archives it appears that  
>>> it got fixed in 2.6.14.  Will there be a patch released for the  
>>> 2.6.13 kernel that will propagate to the opensuse online update?   
>>> Where can I get the latest source file for mkiss that I can  manually 
>>> compile it under 2.6.13?
>>>
>>> Thanks,
>>> Mike, W1NR
>>>
>>> -
>>> 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
>>>
>>
>> -
>> 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
>>
> 
> -
> 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


-- 
Joni Bäcklund, Tel +358400665775, FAX +35898042007
      Email: joni@connect.fi, oh2njr@sral.fi
   Amateur packet radio AX25: oh2njr@oh2rbj.fin.eu
  Some kind of Homepage: http://www.connect.fi/joni
" The Choice of a GNU generation:  Debian Linux 3.1 "
-
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: 2.6.13 mkiss update?

[jarmo]

Joni Bäcklund wrote (lähetysaika torstai, 5. tammikuuta 2006 16:34):
> I can confirm that running kissattach produces kernel panic with 2.6.15.
> So do not use it until there is a patch available ! Seems that kernel
> ax25 developers are not quite sync with the kernel network code..

Must be SuSe related, I have 2.6.15 (vanilla) working fine in
my Mandriva cooker version.
[root@oh1mrr oh1mrr]# /etc/rc.d/init.d/rc.ax25 start
Loading module ax25                                             [  OK  ]
Loading module netrom                                           [  OK  ]
Loading module 6pack                                            [  OK  ]
Setting up radio @ ttyS0 sp0AX.25 port radio bound to device sp0
                                                                [  OK  ]
Setting radio parameters                                        [  OK  ]
Setting netrom for node NET/ROM port netrom bound to device nr0
                                                                [  OK  ]
Setting radio IP-parameters                                     [  OK  ]
Setting netrom IP-parameters                                    [  OK  ]
Starting ax25d                                                  [  OK  ]
Starting netromd                                                [  OK  ]
Starting ax25rtd                                                [  OK  ]
Starting rxecho                                                 [  OK  ]
Starting rip98d                                                 [  OK  ]
Starting mheard                                                 [  OK  ]
Setting local routes/usr/sbin/nrparms -routes radio oh1rcf-4 + 200
/usr/sbin/nrparms -nodes OH1RCF-4 + RCFLIN 120 6 radio oh1rcf-4
/usr/sbin/nrparms -routes radio oh1rdf-0 +2
/usr/sbin/nrparms -nodes OH1RDF-0 + PORNIX 120 6 radio oh1rcf-4
                                                                [  OK  ]
All Done  !

Jarmo
-- 
Linux is the answer.
What was your question?
(Brian Lane)
-
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: 2.6.13 mkiss update?

[Markus Roch]

Hi,

I'm running Debian testing and have also some problems with mkiss since
2.6.15. In 2.6.14 everything went fine, since 2.6.15 I get a kernel
panic after I try to connect via the KISS Interface.

Setting it up with kissattach ist no problem, but when I use the
"call" programm or LinKT to establish a connection the machine
locks up completly!

Any ideas?

Best 73
Markus, DL2KMR


Zitat von jarmo <oh1mrr@nic.fi>:

> Joni Bäcklund wrote (lähetysaika torstai, 5. tammikuuta 2006 16:34):
>> I can confirm that running kissattach produces kernel panic with 2.6.15.
>> So do not use it until there is a patch available ! Seems that kernel
>> ax25 developers are not quite sync with the kernel network code..
>
> Must be SuSe related, I have 2.6.15 (vanilla) working fine in
> my Mandriva cooker version.
> [root@oh1mrr oh1mrr]# /etc/rc.d/init.d/rc.ax25 start
> Loading module ax25                                             [  OK  ]
> Loading module netrom                                           [  OK  ]
> Loading module 6pack                                            [  OK  ]
> Setting up radio @ ttyS0 sp0AX.25 port radio bound to device sp0
>                                                                [  OK  ]
> Setting radio parameters                                        [  OK  ]
> Setting netrom for node NET/ROM port netrom bound to device nr0
>                                                                [  OK  ]
> Setting radio IP-parameters                                     [  OK  ]
> Setting netrom IP-parameters                                    [  OK  ]
> Starting ax25d                                                  [  OK  ]
> Starting netromd                                                [  OK  ]
> Starting ax25rtd                                                [  OK  ]
> Starting rxecho                                                 [  OK  ]
> Starting rip98d                                                 [  OK  ]
> Starting mheard                                                 [  OK  ]
> Setting local routes/usr/sbin/nrparms -routes radio oh1rcf-4 + 200
> /usr/sbin/nrparms -nodes OH1RCF-4 + RCFLIN 120 6 radio oh1rcf-4
> /usr/sbin/nrparms -routes radio oh1rdf-0 +2
> /usr/sbin/nrparms -nodes OH1RDF-0 + PORNIX 120 6 radio oh1rcf-4
>                                                                [  OK  ]
> All Done  !
>
> Jarmo
> --
> Linux is the answer.
> What was your question?
> (Brian Lane)
> -
> 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
>



-
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: 2.6.13 mkiss update?

[Mike McCarthy, W1NR]

Jarmo,
   You are not using the mkiss module or kissattach.  There in lies the 
problem.

   I have confirmed that a hard system lockup occurs with 2.6.15-default 
even when all of the ax25 tools and libraries are recompiled from source. 
2.6.14-5 appears to be OK.

Mike, W1NR

----- Original Message ----- 
From: "jarmo" <oh1mrr@nic.fi>
To: <linux-hams@vger.kernel.org>
Sent: Thursday, January 05, 2006 2:29 PM
Subject: Re: 2.6.13 mkiss update?


> Joni Bäcklund wrote (lähetysaika torstai, 5. tammikuuta 2006 16:34):
>> I can confirm that running kissattach produces kernel panic with 2.6.15.
>> So do not use it until there is a patch available ! Seems that kernel
>> ax25 developers are not quite sync with the kernel network code..
>
> Must be SuSe related, I have 2.6.15 (vanilla) working fine in
> my Mandriva cooker version.
> [root@oh1mrr oh1mrr]# /etc/rc.d/init.d/rc.ax25 start
> Loading module ax25                                             [  OK  ]
> Loading module netrom                                           [  OK  ]
> Loading module 6pack                                            [  OK  ]
> Setting up radio @ ttyS0 sp0AX.25 port radio bound to device sp0
>                                                                [  OK  ]
> Setting radio parameters                                        [  OK  ]
> Setting netrom for node NET/ROM port netrom bound to device nr0
>                                                                [  OK  ]
> Setting radio IP-parameters                                     [  OK  ]
> Setting netrom IP-parameters                                    [  OK  ]
> Starting ax25d                                                  [  OK  ]
> Starting netromd                                                [  OK  ]
> Starting ax25rtd                                                [  OK  ]
> Starting rxecho                                                 [  OK  ]
> Starting rip98d                                                 [  OK  ]
> Starting mheard                                                 [  OK  ]
> Setting local routes/usr/sbin/nrparms -routes radio oh1rcf-4 + 200
> /usr/sbin/nrparms -nodes OH1RCF-4 + RCFLIN 120 6 radio oh1rcf-4
> /usr/sbin/nrparms -routes radio oh1rdf-0 +2
> /usr/sbin/nrparms -nodes OH1RDF-0 + PORNIX 120 6 radio oh1rcf-4
>                                                                [  OK  ]
> All Done  !
>
> Jarmo
> -- 
> Linux is the answer.
> What was your question?
> (Brian Lane)
> -
> 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
> 

-
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: 2.6.13 mkiss update?

[Bernard Pidoux]

Hi,

Running here Mandriva Linux 2006 distro with updated kernels (2.6.14-3 
on one machine and 2.6.14-4 on another) without any problem with AX25 
code, even with mkiss.

It would be nice to have a small group of beta testers before a 
modification is introduced in AX25 drivers for future kernels.

I volunteer for beta testing.

73 de Bernard, f6bvp

http://f6bvp.free
http://f6bvp.org (mirror)

----------------

Mike McCarthy, W1NR a écrit :
> Jarmo,
>   You are not using the mkiss module or kissattach.  There in lies the 
> problem.
> 
>   I have confirmed that a hard system lockup occurs with 2.6.15-default 
> even when all of the ax25 tools and libraries are recompiled from 
> source. 2.6.14-5 appears to be OK.
> 
> Mike, W1NR
> 
> ----- Original Message ----- From: "jarmo" <oh1mrr@nic.fi>
> To: <linux-hams@vger.kernel.org>
> Sent: Thursday, January 05, 2006 2:29 PM
> Subject: Re: 2.6.13 mkiss update?
> 
> 
>> Joni Bäcklund wrote (lähetysaika torstai, 5. tammikuuta 2006 16:34):
>>
>>> I can confirm that running kissattach produces kernel panic with 2.6.15.
>>> So do not use it until there is a patch available ! Seems that kernel
>>> ax25 developers are not quite sync with the kernel network code..
>>
>>
>> Must be SuSe related, I have 2.6.15 (vanilla) working fine in
>> my Mandriva cooker version.
>> [root@oh1mrr oh1mrr]# /etc/rc.d/init.d/rc.ax25 start
>> Loading module ax25                                             [  OK  ]
>> Loading module netrom                                           [  OK  ]
>> Loading module 6pack                                            [  OK  ]
>> Setting up radio @ ttyS0 sp0AX.25 port radio bound to device sp0
>>                                                                [  OK  ]
>> Setting radio parameters                                        [  OK  ]
>> Setting netrom for node NET/ROM port netrom bound to device nr0
>>                                                                [  OK  ]
>> Setting radio IP-parameters                                     [  OK  ]
>> Setting netrom IP-parameters                                    [  OK  ]
>> Starting ax25d                                                  [  OK  ]
>> Starting netromd                                                [  OK  ]
>> Starting ax25rtd                                                [  OK  ]
>> Starting rxecho                                                 [  OK  ]
>> Starting rip98d                                                 [  OK  ]
>> Starting mheard                                                 [  OK  ]
>> Setting local routes/usr/sbin/nrparms -routes radio oh1rcf-4 + 200
>> /usr/sbin/nrparms -nodes OH1RCF-4 + RCFLIN 120 6 radio oh1rcf-4
>> /usr/sbin/nrparms -routes radio oh1rdf-0 +2
>> /usr/sbin/nrparms -nodes OH1RDF-0 + PORNIX 120 6 radio oh1rcf-4
>>                                                                [  OK  ]
>> All Done  !
>>
>> Jarmo
>> -- 
>> Linux is the answer.
>> What was your question?
>> (Brian Lane)
>> -
>> 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
>>
> 
> -
> 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
> 
> 
-
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: 2.6.13 mkiss update?

[jarmo]

Mike McCarthy, W1NR wrote (lähetysaika torstai, 5. tammikuuta 2006 22:41):
> Jarmo,
>    You are not using the mkiss module or kissattach.  There in lies the
> problem.
 Nope, not mkiss, but kissattach and spattach is same?  So it has to
be mkiss, which is broken...
Any ideas Ralf?

Jarmo
-- 
Linux is the answer.
What was your question?
(Brian Lane)
-
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: 2.6.13 mkiss update?

[Hamish Moffatt]

On Fri, Jan 06, 2006 at 05:58:19AM +0200, jarmo wrote:
> Mike McCarthy, W1NR wrote (lähetysaika torstai, 5. tammikuuta 2006 22:41):
> > Jarmo,
> >    You are not using the mkiss module or kissattach.  There in lies the
> > problem.
>  Nope, not mkiss, but kissattach and spattach is same?  So it has to
> be mkiss, which is broken...

Does your configuration use the mkiss module?

User-space (kissattach/spattach/whatever) can't make the kernel crash.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
-
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: 2.6.13 mkiss update?

[jarmo]

Hamish Moffatt wrote (lähetysaika perjantai, 6. tammikuuta 2006 09:27):

> Does your configuration use the mkiss module?
>
> User-space (kissattach/spattach/whatever) can't make the kernel crash.
>
>
> Hamish

No, I use 6pack.
I have mkiss compiled as a module, but no need to call it.

Jarmo 
-- 
Linux is the answer.
What was your question?
(Brian Lane)
-
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