From: "Mike McCarthy, W1NR" <lists@w1nr.net>
To: linux-hams@vger.kernel.org
Subject: Re: 2.6.13 mkiss update?
Date: Thu, 5 Jan 2006 09:17:57 -0500 [thread overview]
Message-ID: <001901c61202$d3f79310$680ea8c0@LoJackOne.LoJack.com> (raw)
In-Reply-To: 8BD9A378-7AF9-41DB-BE04-1EAD876ECB5D@oz.net
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
>
next prev parent reply other threads:[~2006-01-05 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 16:22 2.6.13 mkiss update? Mike McCarthy, W1NR
2006-01-04 17:03 ` Bob Nielsen
2006-01-04 20:46 ` oz6bl
2006-01-04 21:19 ` Bob Nielsen
2006-01-05 0:16 ` Mike McCarthy, W1NR
2006-01-05 14:17 ` Mike McCarthy, W1NR [this message]
2006-01-05 14:34 ` Joni Bäcklund
2006-01-05 19:29 ` jarmo
2006-01-05 20:35 ` Markus Roch
2006-01-05 20:41 ` Mike McCarthy, W1NR
2006-01-05 23:08 ` Bernard Pidoux
2006-01-06 3:58 ` jarmo
2006-01-06 7:27 ` Hamish Moffatt
2006-01-06 9:48 ` jarmo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001901c61202$d3f79310$680ea8c0@LoJackOne.LoJack.com' \
--to=lists@w1nr.net \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox