From: jabennett (nbfvvx@gsf.fi)
Date: Sun Aug 19 2001 - 05:41:24 EEST
Hmmm...
In the midst of doing the same thing. For what it's worth, I will relate
what I have discovered so far. Keep in mind I am no expert on this.
Caveat...
After enduring some rather screwy attempts to correctly build a new kernel
with ax25 from the 7.1 release sources, I obtained and used the rpm upgrades
on the RH site for the kernel (2.4.3-12) and the gcc compiler (2.96-85).
This resulted in causing a major system crash on the HP Vectra VL5/133 I was
using. Was not recoverable - the HD was scrambled beyond repair.
The next attempt was to use RH 6.2 as it was released. No disk crashes, but
things were still screwy. At that point, I suspected the memory might be bad
on the HP and replaced it. 7.1 installed without a glitch this time. Using
the updated kernel sources and gcc, the kernel built w/ax25 enabled without
any errors or crashes.
The modules are a different story. Using 'make menuconfig' it appears that
many options were simply not enabled on the HP. Also, the configuration tool
(or the OS - don't know which) determines what type of processor is on the
machine and makes that the default selection under that section. I selected
the modules that I knew were required (that doesn't mean what was really
required...) and compiled in record time. I have not installed the new
kernel on the HP but believe it will not function correctly. Still a ways to
go on this box...
I then tried the same thing with a different box - this time a P3/500. Zero
problems. Built/installed and now successfully using the new kernel.
Although I have built and installed the ax25 tools, apps, etc., I have not
tried them as yet. I suspect they will work.
So...
* BIOS could be causing problems. Can't say I'm really fond of the BIOS used
in the HP - have had compatibility problems before. I've had better luck
with Intel and generic motherboards than I have with computer name-brand
boards (Intel being the exception). In the context of building the kernel
and modules my suspicion is that it may not permit the correct detection of
hardware on the motherboard. This is a purely a WAG on my part.
* Bad memory can cause un-imaginable grief no matter what OS you are
running.
* Could be how the configuration handles the different types of processors.
I don't know what differences there are in coding between the 486, 586, 686,
etc. but I could see a bad line in a makefile script causing mischief.
Perhaps someone with more experience and a better understanding of building
kernels and modules might be able to shed some light on this.
* Might suggest following Red Hat's instructions on their web site (or
printed documentation) on how to build and install upgraded kernels so that
you have the option of booting the old one if there are problems. It's a
simple procedure and is worth the few extra minutes to do. It has saved my
butt on several occasions.
73,
John Bennett
n4xi
----- Original Message -----
From: "R&C" <terhi.victor@logonet.com>
To: <terhi.victor@logonet.com>
Sent: Saturday, August 18, 2001 5:29 PM
Subject: compiling kernel 2.4.2
> Hi,
>
> I have been using Redhat from kernel 2.0.35 up to 2.2.14 and have had NO
> trouble compiling a new kernel to incorporate the ax25 stuff. I have been
> on RH 6.2 for a while with everything running smoothly.
> I just acquired RH 7.1 (kernel 2.4.2) and spend two days trying to compile
> a new kernel without success.
> The System I end up with has all the right modules made and installed but
> modprobe for any module comes up with 10000 unresolved symbol errors.
> Even access to my dos partitions fails.
>
> Can anyone tell me where I go wrong. Is there a problem with this
> particular kernel (2.4.2-2)?
> It would be nice if there was a .config file available for the default
> kernel as supplied on the distribution disc, because this works fine and
> only needs the ax25 stuff added.
>
> 73
>
> Rein vk4alj
>
>
>
> ----------------
> R&C Mann
> terhi.victor@logonet.com
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to plpbsgi.irvnabo@sernapesca.cl
> 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 ywkkaw@citicorp.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Sun Aug 19 2001 - 05:42:33 EEST