Hello, all!
In former times configuring a kernel was a bit more cumbersome,
yet more straightforward than is today:
device isa
device sio0 at isa? port IO_COM1 flags 0x10 irq 4
device sio1 at isa? port IO_COM2 flags 0x0 irq 3
to keep the kernel from messing with the second device
completely, you simply removed the second line.
Today I have:
device pci
device miibus
device bge
I have a particular system that uses what FreeBSD 6.2 detected
as bge1 for remote console access over IP. As soon as the
interface is probed and activated by the kernel, the connection
to the remote management controller breaks.
Is there a way to limit the number of probed entities for
a certain pci device class to, say, 1 in my case?
I'd like to use bge0 for FreeBSD but the kernel should leave
everything else that might be a bge interface alone.
Thanks,
Patrick
P.S. If anyone is interested: it's a Fujitsu-Siemens iRMC on an
RX100 server. While HP uses a dedicated port for their iLO,
FSC decided to piggyback that function onto a regular
network port.
--
punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info@punkt.de http://www.punkt.de
Gf: J?rgen Egeling AG Mannheim 108285
Patrick M. Hausen wrote:> Hello, all! > > In former times configuring a kernel was a bit more cumbersome, > yet more straightforward than is today: > > device isa > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 flags 0x0 irq 3 > > to keep the kernel from messing with the second device > completely, you simply removed the second line. > > > Today I have: > > device pci > device miibus > device bge > > I have a particular system that uses what FreeBSD 6.2 detected > as bge1 for remote console access over IP. As soon as the > interface is probed and activated by the kernel, the connection > to the remote management controller breaks. > > Is there a way to limit the number of probed entities for > a certain pci device class to, say, 1 in my case? > I'd like to use bge0 for FreeBSD but the kernel should leave > everything else that might be a bge interface alone. > > Thanks, > Patrick >Would the following in /boot/device.hints achieve what you are after? hint.bge.1.disabled="1" hint.bge.2.disabled="1" ... -Proto
On Thu, May 03, 2007 at 08:49:40AM -0400, Michael Proto wrote:> Would the following in /boot/device.hints achieve what you are after? > > hint.bge.1.disabled="1" > hint.bge.2.disabled="1" > ...You can put these in /boot/loader.conf, thus leaving /boot/device.hints alone; one less file to deal with during mergemaster... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |