I started a thread on this a little while back, but have more info now.
At first I thought that all modules were being compiled with unresolved
symbols. I figured there was something wrong with my install, so I made
a fresh install. I finally downloaded 2.2.12 after doing the fresh
install, but am having the same problems. Here's what I noticed this
time that I didn't before. Not all of the drivers configured as modules
end up with unresolved symbols, and the ones which do depends on whether
I compiled under the 2.2.5-22-SMP or 2.2.5-22 RedHat binary RPM kernels.
(I have the same problem compiling the 2.2.5-22-sources RPM kernel). I
have attached 3 text files: a list of drivers configured as modules; a
list of modules with unresolved symbols compiled under 2.2.5-22-SMP; and
a list of modules with unresolved symbols compiled under 2.2.5-22.
The most significant problem here is that my box is running off a SCSI
drive and I normally compile the aic7xxx (I have an onboard AIC-7895 as
used on an AHA-3940-AUW) driver as a module. So I can't boot this way.
I'm about to try compiling it in the kernel, but I'd rather have a
choice on the matter.
--
________________________________________________________________________
Justin Georgeson
Metrowerks - Desktop Java QA Engineer
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
