Re: Tying down network interfaces

2014-12-31 Thread Martin Birgmeier
The devices are PCI cards, no USB is involved. I assume that I'd have to add lines similar to hint.sis.0.at="pci0:9:0" to /boot/device.hints, but I am unsure of the correct syntax. See also these old articles (which ultimately seem to have gone unanswered): http://lists.freebsd.org/pipermail/

Re: Tying down network interfaces

2014-12-30 Thread Freddie Cash
On Dec 30, 2014 10:02 AM, "Martin Birgmeier" wrote: > > Hi, > > I have two network interfaces as follows: > > sis0: port 0xa400-0xa4ff mem > 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 > sis1: port 0x9400-0x94ff mem > 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 > > When sis0 breaks

Re: Tying down network interfaces

2014-12-30 Thread Chris H
On Tue, 30 Dec 2014 19:02:30 +0100 Martin Birgmeier wrote > Hi, > > I have two network interfaces as follows: > > sis0: port 0xa400-0xa4ff mem > 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 > sis1: port 0x9400-0x94ff mem > 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 > > When sis

Tying down network interfaces

2014-12-30 Thread Martin Birgmeier
Hi, I have two network interfaces as follows: sis0: port 0xa400-0xa4ff mem 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 sis1: port 0x9400-0x94ff mem 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 When sis0 breaks down, sis1 gets renumbered as sis0, wreaking havoc (mostly on my brains