hi justin,
it sounds like you are fighting a battle on many fronts. i'd suggest
isolating one issue at a time. so you tried modules with the aic7xxx
driver, did you try compiling support right in and avoiding modules?
i suggest you LEAVE KERNEL RPMs ALONE.
i don't know anything about 3dfx support under linux, but keep in
mind that rpms don't compile (i think), so compiling src for yourself
is always better.
you are running make modules; make modules_install; before the
make zImage; step of kernel compilation right? and
/lib/modules/<kernel version>/ exists with said modules?
if you need these modules at boot i'd look into /etc/modules, read
about how to load modules at boot time.
another thought occured to me, there are prerequisities to using
the 2.2.x tree of kernels, i forgot what they were, but there are
certain version levels that your libs should be. 2.2.x may work
under lower versions of these libs, but you could have the problems
you're describing. ie: maybe your glibc is old and lacks those
needed symbols.
hope this helps...
Justin Georgeson wrote:
> This message is two-fold. First, the last two kernels I've tried to
> compile beyond RedHat's kitchen-sink config compile fine, and lilo works
> fine, the modules install, everything is funky-dorey. Then I try to boot
> it and the aic7xxx driver seems to have unresolved symbols, can't mount
> root device, kernel panic. This happened with 2.2.9 from kernel.org and
> from the 2.2.12-4 RPMS obtained from rpmfind.net's rawhide tree. I don't
> recall if I've tried to compile the 2.2.5-22 RPM kernel source.
>
> I also have a 3Dfx Voodoo3 that I'm trying to make work. The Device_3Dfx
> src RPM doesn't compile, I don't recall the exact message. So I took the
> source and tried to compile it by hand using the supplied Makefile. The
> Makefile gives a different kernel version than `uname -a` (2.2.12-4 vs
> 2.2.12-4smp) and I think it fails to recognize I have an SMP box. anyhow
> If I try to do some of the Makefile myself (like the above two) the
> driver compile fine, but then fails to load due to unresolved symbols.
>
> So I think there is a problem with how modules in general are compiled
> on my box. I've been planning on buying a new drive and starting fresh,
> but I'd still like to know what's going on. Kernel modules seem to be
> the only thing that aren't compiling right.
>
> --
> ________________________________________________________________________
> Justin Georgeson
> Institute for Advanced Technology -- System Administrator
> University of Texas at Austin -- Dept. of Computer Science
> http://www.cs.utexas.edu/users/pyros
> mailto:[EMAIL PROTECTED]
> ---------------------------------------------------------------------------
> Send administrative requests to [EMAIL PROTECTED]
--
tom carlile [EMAIL PROTECTED]
professional systems wrangler
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
