From: Michael Conry (michael.conry at domain ucd.ie)
Date: Wed 04 Sep 2002 - 02:25:10 IST
Hi Eric,
On 0020 -0700 %{!Tue, Sep 03, 2002 at 4:21:55PM -0700}, eric nichols wrote:
> Thanks everyone for the help.
> I didn't know it was part of the problem, so I didn't say that I had
> already installed the glibc-kernheaders and the kernel-source (it was
> a missing modversions.h after the ./configure that led me to install
> it). Unfortunately it working was another problem. Do you think that a
> change to the /usr/src/linux-2.4.18-3/.configure file might fix the
> problem. I took a look at the file, it's a massive nearly 4,000 lines,
> if part of this file might be the problem, any ideas where I should
> start?
> Also, when I halt and reboot the computer, I see "Kernel 2.4.18-3 on
> an i686" The glibc-kernheaders file I installed ended in i386.rpm.
> Might there be a clash between i686 and i386?
No, i don't believe that is the problem. the kernheaders or kernel
source are called i386 to distinguish them from other architectures
(like ia64, or m68k or whatever else). i686 is the actual architecture
of your system (meaning something later than i586 pentium). Anyway,
this is not very important (AFAIK!).
I saw a similar error to the one you describe (missing modversions.h)
when I was corresponding with a guy having trouble installing ALSA.
ALSA needed access to kernel source (header) files, but was not finding
them. This guy had two problems:
1) Telling ALSA where to find the kernel sources
2) Missing modversions.h
The first was solved by using a flag that could be passed to the
./configure command, "./configure --with-kernel=dir"
You seem to be doing something similar by using a flag
--with-kernel-includes=/usr/src/linux-2.4
The modversions.h file was missing because this guy had simply unpacked
a kernel source, but had not compiled from it (I was puzzled, I compile
my own kernels and so never ran into this problem).
To create the modversions.h file, we had to take the following steps...
unpack the source
tar -xjvf linux-2.4.18.tar.bz2
cd into the source directory, then configure the kernel
make menuconfig
note this command gives you a menu system through which to edit/create
the very long .configure file you noticed. Take a look around if you
like, then exit, and when it asks say "YES" to saving the configuration.
Then run the make dep command, which checks dependencies
make dep
At this point, a modversions.h file will appear in the include/
directory of your linux source.
As an aside, you should note that at this stage you have almost compiled
a kernel. To fill in the details look at the kernel howto.
http://www.tldp.org/HOWTO/Kernel-HOWTO.html
Hope that helps you along towards the solution
> Would the purchase of a new inexpensive (if it's possible) modem be
> the only real solution for this new one at this point?
I'm sure you will get the modem driver to compile, though it might take
some messing around. If it is any consolation, I'm sure most people on
this list have had similar troubles from time to time, and will tell you
that when you finally do find the solution you will realise that you
have learned some useful skills and gotten to know your system that bit
better.
mick
-- Michael Conry Ph.:+353-1-7161987, Web: http://www.acronymchile.com Key fingerprint = 5508 B563 6791 5C84 A947 CB01 997B 3598 09DE 502C
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:18:37 GMT