[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: AX25 kernel compiling



Ed

I am very new to debian and relativley new to linux.  When you have things
like the AX25 Howto to follow you have to allow for a few slip ups.

I have never used apt before so wouldn't have thought to go down that line.

I would love to use linux more often but as I dont always have a spare day
or 2 to learn how to install a few bits of software it has to play second
fiddle to windows.

So, I am am using debian and you have made me aware of the fact that all I
need to do is install a different kernel using apt.

How do I do that?

When I have fixed Lilo, I will have a go at doing it your way hopefully
things will work.

Regards

Jon


----- Original Message -----
From: "K1VP" <k1vp@grizzy.com>
To: "Jon" <debian@blueyonder.co.uk>
Cc: <debian-hams@lists.debian.org>
Sent: Monday, August 30, 2004 6:46 PM
Subject: Re: AX25 kernel compiling


> Jon wrote:
>
> > I have decided to bite the bullet and downloaded kernel 2.4.27 compiled
it as per the ax25 howto.
>
> I don't intend to be obnoxious, but you were running Debian correct? And
> you were told that if you installed a stock Debian kernel it would have
> everything you needed compiled in.  And all you need to do to install a
> different kernel is use apt.  So why did you compile a kernel from source?
>
> Since you have not yet changed lilo.conf which in turn means the machine
> will boot into the original kernel, do yourself a favor and use apt to
> install the current 2.4 kernel from Debian which will give you the ax25
> abilities you seek including driver modules for the BayCom.
> >
> >
> > I have done this and lilo returns:
> >
> > Warning: Int 0x13 function 8 and function 0x48 return different
> > head/sector geometries for BIOS drive 0x80
> > Fatal: Kernel /usr/src/linux-2.4.27/vmlinux is too big
> >
> > What do I need to do?
>
> The warning about drive geometry is not a big deal, but the second one is.
>
> Did you compile using command "make zImage"?
> If so and you really, really want to compile your own, then use the
> command "make bzImage" which should create an image that will not result
> in the error message you got.
>
> Ed Lawson
>
>
>



Reply to: