Hmm,
You say that you think there is something wrong with the
out of box kernel source, but then the next thing you say is
that you "patched" the kernel. If that's true, then you no
longer have out-of-box kernel source....
Do you mean that you "configured" the kernel to include
SB AWE 32 support?
I think your problem is that you failed to (re)move the old modules
before doing a "make modules_install."
This step should be covered in the Kernel-HOWTO, but in my
copy (which I admit is probably outdated) it is missing.
Try moving the old modules out of the modules directory prior
to the "make modules_install". This is best accoplished by
renaming the directory containing modules to something else.
I forget what the directory is, but it sholdn't be too hard to
figure out. Not at my linux-box right now.
Also, that whole "preferred" thing is F***ed-Up. A stock RedHat
install will give a warning on startup about failing to find
<something>/preferred/<dependency-file>. I STRONGLY suggest going
to redhat's errata page and downloading the updated init-scripts
rpm, as that doesn't use the "preferred" sym-link. Also,
you might want to pick up the source RPMs for the 2.0.35 kernel.
Make sure you get both the kernel-source and kernel-header RPMs.
Bryan Scaringe
>
> OK, I give up.... I appeal to the newbie list, and my new local
> friends:
>
> I've been attempting to recompile the stock Redhat 5.1 kernel to add
> support for my Soundblaster AWE32 card, and I'm convinced that there is
> something wrong with the "out of the box" kernel source configuration.
> This is what I did:
>
> Patched the source to include low level AWE sound support.
>
> In /usr/src/linux make config (I've done this a zillion times, also
> used make xconfig and make menuconfig several times each). I've done it
> many different ways -- leaving it default except for AWE support,
> trimming it down to only the items I need, and everything in between)
>
> make dep
> make clean
> make zlilo
>
> Reboot, and everything comes up fine. Now back in /usr/src/linux:
>
> make modules
> make modules_install
>
> When I reboot, I get loads of modprobe errors, all reading something
> like:
>
> modprobe: no dependencies found for /usr/lib/modules/2.0.34/vfat.o
>
> I get an error like this for EVERY module that would normally be loaded
> on the fly my kerneld. In the /usr/lib/modules directory, I found two
> directories full of modules 2.0.34 (newly created) and 2.0.34-0.6 (out
> of the box modules, I guess). There is also a symbolic link to
> 2.0.34-0.6 called "preferred" which seems to be created at boot time by
> some code in the rc.sysinit script. I fiddled with this for HOURS until
> I was able to get "preferred" to point to the new modules, but still,
> every module gets the modprobe dependency error on bootup. The modules
> are physically present, and there is a file called modules.dep (or
> something similar) in the directory that points to the right directory.
> I learned a lot about modprobe and the rc.sysinit script, but I must
> still be missing something.
>
> I was so frustrated that I went ahead and coughed up the $30 for
> osssound and the AWE module, but I'd still like to be able to recompile
> the kernel someday. Does anyone have personal experience with compiling
> modules in Redhat 5.1 -- I followed the instructions in the Kernel-HOWTO
> to the letter, and as far as I can tell, the new module dependencies are
> supposed to be setup automatically when I make modules_install. I'm
> assuming that something in the default setup is hosed, because I read
> nothing that led me to believe that I'd ever need to manually do
> anything to make module dependencies.
>
> ?????
>
> Thanks,
>
> Dave
>
> David Lambermont
> DIGICON Corp.
> 614-692-4694 - Voice
> 614-665-6937 - Pager
> mailto:[EMAIL PROTECTED]
>
>
