Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Mike McCarthy, W1NR" <lists@w1nr.net>
To: Douglas Cole <doug.n7bfs@gmail.com>
Cc: Jeremiah <jjgpg@cet.com>, linux-hams@vger.kernel.org
Subject: Re: error when trying to run kissattach on 2.6.13-15.8 Suse Kernel
Date: Wed, 19 Apr 2006 08:18:46 -0400	[thread overview]
Message-ID: <001f01c663ab$6866e8d0$650ea8c0@LoJackOne.LoJack.com> (raw)
In-Reply-To: 9923fd660604181755w2ecde9e1p919138d1bea9d6b9@mail.gmail.com

My mistake.  There are no YaST control files present in that directory.  You 
need to download the RPM's and install manually.  If you are using Grub, 
everything should get taken care of.  However, there will be no automatic 
updating via YOU.  Other things like wireless and third party video might 
have problems with this approach also.

The problem is a broken mkiss kernel module.  I tried to update this from 
source a while back and got nowhere.  There are too many other dependencies. 
A lot of work was done on the AX.25 kernel modules recently and will be 
present when SuSE 10.1 gets released (with 2.6.16 kernel).  Currently RC1 is 
available and the official release of 10.1 is scheduled for April 25.  That 
would be the best solution and one I am waiting for.

My cluster server is still running 9.3 because of the mkiss issue.  I will 
be putting 10.1 RC1 on a test machine this weekend to try things out.  Beta 
9 looked good as far as AX.25 was concerned.  About a month after the 10.1 
release, I might upgrade my main server.

Mike, W1NR

----- Original Message ----- 
From: "Douglas Cole" <doug.n7bfs@gmail.com>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: "Jeremiah" <jjgpg@cet.com>; <linux-hams@vger.kernel.org>
Sent: Tuesday, April 18, 2006 8:55 PM
Subject: Re: error when trying to run kissattach on 2.6.13-15.8 Suse Kernel


On 4/18/06, Mike McCarthy, W1NR <lists@w1nr.net> wrote:
> There is one other possible cure I forgot to mention...
> Point a YaST install source to
> ftp://ftp.esat.net/mirrors/ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/
> and try the "kotd - kernel of the day"

Will this be an "easy" kernel upgrade or will it break a system if one
just installs the rpm and that is it? Or will YaST "magically" make
the initrd file and put the new kernel where it should be and make an
entry in Grub?

I am still very green to kernel upgrading (normally I will wait for
the next distro' version) and so don't have all the steps burned into
my cortex like most of the folks on this list, so please pardon the
ignorance...

Thanks for the link :)

Doug
N7BFS


  reply	other threads:[~2006-04-19 12:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18  3:21 error when trying to run kissattach on 2.6.13-15.8 Suse Kernel Jeremiah
2006-04-18 11:51 ` Mike McCarthy, W1NR
2006-04-18 23:33   ` Mike McCarthy, W1NR
2006-04-19  0:55     ` Douglas Cole
2006-04-19 12:18       ` Mike McCarthy, W1NR [this message]
2006-04-19 12:26         ` Jeremiah
2006-04-19 12:04     ` Jeremiah
2006-04-19 12:28       ` Mike McCarthy, W1NR
2006-04-19 13:25         ` Douglas Cole
2006-04-19 16:02           ` Mike McCarthy, W1NR
2006-04-20 19:15             ` Mike McCarthy, W1NR
2006-05-02 12:35               ` Jeremiah
     [not found] ` <000701c6629a$f803c4c0$e14689d8@oem7paq6co5hph>
2006-04-19 11:59   ` Jeremiah

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='001f01c663ab$6866e8d0$650ea8c0@LoJackOne.LoJack.com' \
    --to=lists@w1nr.net \
    --cc=doug.n7bfs@gmail.com \
    --cc=jjgpg@cet.com \
    --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