disable kernel driver at boot?

John-Mark Gurney gurney_j at resnet.uoregon.edu
Wed May 17 17:45:31 UTC 2006


sfp wrote this message on Tue, May 16, 2006 at 22:22 -0600:
> From: "Oliver Fromme" <olli at lurza.secnetix.de>
> 
> > sfp <mosfet at planet.eon.net> wrote:
> >  > Is it possible to disable a driver compiled into a 4.10 kernel at
> >  > boot time by feeding a (set?) command to the loader?
> >  >
> >  > In this case I want to turf the EM(4) driver that was compiled into
> >  > the kernel I've inherited and substitute it with a new if_em.ko using
> >  > kldload.
> >
> > That's not possible.  You might disable a driver through
> > loader variables (or kernel hints, or whatever), but the
> > driver will still be present in the kernel image, so you
> > cannot load a module that uses the same symbols.
> 
> I may have answered my own question.  Compiled em-4.1.6,  replaced if_em.ko
> & loaded it from /boot/loader.conf.
> 
> The reason I need this is 4.10 enumerates the Pro/1000 GT (PWLA8391GT,
> 82541PI chipset) as unknown.  Need a newer driver to support the hardware.
> 
> I'd still like to find a way to suppress the driver in the kernel entirely
> though :P

Since the kernel driver it's attaching, you could always rename the
em module that you compile...  just a few things to change, and you
have a different name, and no conflicts w/ the kernel...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."


More information about the freebsd-net mailing list