From owner-freebsd-questions@freebsd.org Tue Jun 19 18:00:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44E711004378 for ; Tue, 19 Jun 2018 18:00:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A56B16DFA6 for ; Tue, 19 Jun 2018 18:00:56 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.97.38]) by mrelayeu.kundenserver.de (mreue105 [212.227.15.183]) with ESMTPA (Nemesis) id 0Lbr40-1fx0Bm1GpI-00jFDC; Tue, 19 Jun 2018 20:00:54 +0200 Date: Tue, 19 Jun 2018 20:00:54 +0200 From: Polytropon To: Eric Joyner Cc: freebsd-questions Subject: Re: Is there a way to disable PCI devices before a driver attaches to them? Message-Id: <20180619200054.1232602d.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:TW1XvyKqxcAEYxRBzGvb9WVtDMYAYeAXxtZyTqX/cFWrSjI5e9O afrK8cLr5T5oqcRNieFImwaGOkk+w/UYzp6CRhbH2G8PUDfahGR1bQU8Pfg+mt+I5s2AGCo Fe2DSnGXhu3Zrkh5g/dIJAHLfiWUgSXublZuyxUWxR04Z/FquP9fj0Fyc9DOfpa9eAFz2VK UJLocaKZudYwlD42JleMQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:BHyOoy003C4=:9BW86Jk0pl6jQzsoF3ldMx /O0SzwL56ij4crF9mft1fNLYvwfIl7Br6UBnUbLV+VC9V19r0tdTGMVjpIcOOHbxrZmMKaDcG kRWx3wCltxP6o4FCdriQ12jzzSF8Goll9/esdxI8QwA8Z7J3XEwL2IEylVNQySkjHjG5Zl1KI IztvseGuINyToP6ULm2zJIfz1X9U3JJJU7YjW6/iKmRMZT2HOkAGZ1a9M6W2T4pnj7/rltrIq krVjIDkle11R1WViDj6i8nBY6xtk3qvpYwSYgHY2xxFI6tkBfeAkPOvuSbVn1r2LrdDvMMyYE 6+c7ZZCKcnn5mkVTX3I5qwzz0dic2jDjMj94EjnHfJCIJ0l9ooI9QeVHqZHt2zAsKoMgXQjyY tjSCY38tBUoueybFKW1jm+Npcunsj1PR4e2Ne9qwepcm06iCkFgeqOY7hUYySSSWp/v8cPyQV u5ncPKFsYv7P5jLf1pwINJ0sC0gdWpCx9cq22tSNBMEGD3/rtjPbs+qg964w/fwmnspciDAeK 3oOLJZQrqAK6IEnqD1AHdVHGgMsd6N/Qzx7dEuGgHnqg59XAgpbc3EfyLSQbw/Xl1kM1GUB+Q I1PtaUa8cF79fBPC5exz34mEcG7Bfc/mcTmuFBhMzq7bonHzC5D1FX7HEZsNUK1uLgrOLfO7X NTqkM3Psqa29d86/DocedCJ3HlX1ys+0Rj9fJ2NiXhKEKhqXuzsvvfRNYtq/TtU5jaLjTfc4Q nG22LlGWEFb9RSiI X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jun 2018 18:00:57 -0000 On Tue, 19 Jun 2018 10:36:43 -0700, Eric Joyner wrote: > ^ See subject ^ > > The only method I know of atm is to load vmm via loader.conf and use the > pptdev variable to make the devices that I want to disable just "ppt" > devices. Maybe you can use /boot/device.hints to disable the device you don't want a driver to attach to? Example: hint.ppt.0.disable="YES" You should also be able to add such a statement to /boot/loader.conf because device.hints might get replaced during updates (and it is a system-provided file, while loader.conf usually is a user-spplued file), See "man device.hints", or: https://www.freebsd.org/doc/handbook/device-hints.html https://forums.freebsd.org/threads/disable-driver.14402/ -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...