From owner-freebsd-net@FreeBSD.ORG Wed May 17 04:24:41 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B48116A400 for ; Wed, 17 May 2006 04:24:41 +0000 (UTC) (envelope-from mosfet@planet.eon.net) Received: from priv-edtnes10.telusplanet.net (outbound02.telus.net [199.185.220.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id E184243D48 for ; Wed, 17 May 2006 04:24:40 +0000 (GMT) (envelope-from mosfet@planet.eon.net) Received: from priv-edtnaa05.telusplanet.net ([142.179.216.126]) by priv-edtnes10.telusplanet.net (InterMail vM.6.01.05.04 201-2131-123-105-20051025) with ESMTP id <20060517042440.XTDQ5352.priv-edtnes10.telusplanet.net@priv-edtnaa05.telusplanet.net>; Tue, 16 May 2006 22:24:40 -0600 Received: from ephialtes (s142-179-216-126.ab.hsia.telus.net [142.179.216.126]) by priv-edtnaa05.telusplanet.net (BorderWare MXtreme Infinity Mail Firewall) with SMTP id A3XM1WR4LU; Tue, 16 May 2006 22:24:35 -0600 (MDT) Message-ID: <002a01c67969$8108c380$6f3010ac@ephialtes> From: "sfp" To: , References: <200605161242.k4GCgmS8006842@lurza.secnetix.de> Date: Tue, 16 May 2006 22:22:26 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cc: Subject: Re: disable kernel driver at boot? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2006 04:24:42 -0000 From: "Oliver Fromme" > sfp 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 Thanks for the info! > > You will have to compile a kernel that does not include > the driver. > > > I don't have the option of recompiling the kernel to exclude EM(4). > > Too bad. (Why don't you have that option?) > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > With Perl you can manipulate text, interact with programs, talk over > networks, drive Web pages, perform arbitrary precision arithmetic, > and write programs that look like Snoopy swearing. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"