[NTLUG:Discuss] kernel upgrade via rpm on RH7.0

[Chris Cox]

Sounds like a bug in the 2.2.17 kernel build somehow.
You can "fix" this by renaming the directory to 2.2.16... but
something is wrong about this.

Perhaps the Redhat rpm is messed up... I know that a pure
(non RH) 2.2.18 kernel doesn't have this type of problem.

Regards,
Chris

saluki wrote:
> 
> Here's a good one :
> 
> I just upgraded my kernel on my RH7 box, from 2.2.16 to the 2.2.17 via
> the rpm's using the redhat up2date tool, but upon boot up it still says
> 2.2.16. Ok, no problem -- however, now no modules will load.  Everytime
> I do a insmod <anything>, I get the can't find <anything> error
> message.  I checked in my  /lib/modules directory and I now have two
> directories there, the old 2.2.16 directory, which is empty, and a
> 2.2.17 directory where it looks like everything resides.  When I do a
> modprobe -c is still points to the 2.2.16 directory.  I read the 'man
> modprobe' pages, but it doesn't tell me how to tell modprobe to look for
> the modules in the proper directory....  modprobe's help says I can
> specify a file to use, but having never done that before, or seen an
> example, I don't know where to start.  Any ideas?
> 
> Don
> _______________________________________________
> http://ntlug.org/mailman/listinfo/discuss