Re: howto determine network device unit number? device.hints?

Yony,

Bruce M. Simpson wrote:

And how come the unit number is given an arbitrary value? Is there a good
reason for that?
...

In your case I'm not sure why your two cards would flip order. Could it be how your BIOS and hardware set up the PCI IDSEL lines at boot?

If this is the case on your system, then you really need to provide more data about your hardware, i.e. motherboard, BIOS, vendor information etc. as others point out.

Based on the data you've provided about the issue to date, my best guess is that something in the above is different on your system (which is why I mentioned IDSEL lines -- the mechanism PCI uses to actually assign bus numbers electrically).

Normally the behaviour of FreeBSD's bus probes is well known -- nexus is walked for child buses, then these buses are plumbed into NEWBUS, e.g. cpu0...cpuN on nexus itself, PCI buses, and PCI subordinate buses in that order.

* You mention you don't encounter the issue with Linux, but you may already be aware that udev can tie driver instance number(s) to specific MAC addresses, although this process isn't fully automatic and any given distro may or may not create the persistent udev rules on a first run -- so this is comparing apples with oranges.

* [PCI-Express is a special case though, and I've had to sit down and do some work with commercial clients to make sure their appliance was able to detect devices being in particular slot numbers. Again, though, it's just as subject to the PCI enumeration order further up on the bus hierarchy as non-PCI-Express drivers.]

So your issue may not be a simple matter of "this seems wrong, this doesn't work", though I am sorry to hear it isn't working for you right now.

There are a lot of dynamic factors in the overall picture of the system, and what seems to work as expected for many users, may not be working for you, and we really need basic hardware information, when folk see things like this happening, for any volunteer(s) out there to come up with the right solution, let alone the true picture of what's actually going on in your specific case.

thanks
BMS
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: SCO Technical Articles to say "tata".
    ... They recently quit making the isa version of the ... Considering the ISA bus runs at 8MHz and PCI bus runs at 33MHz or ... >hardware support. ... Many of the PCI devices on iNTEL run on Macs. ...
    (comp.unix.sco.misc)
  • Re: PQOAL PCI BusID vs Bus Number Problem
    ... Original intention is add support for system with multiple PCI buses ... with bus number. ... In most cases, the BusID parameter would be zero, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: howto determine network device unit number? device.hints?
    ... Could it be how your BIOS and hardware set up the PCI IDSEL lines at boot? ... Based on the data you've provided about the issue to date, my best guess is that something in the above is different on your system (which is why I mentioned IDSEL lines -- the mechanism PCI uses to actually assign bus numbers electrically). ... Normally the behaviour of FreeBSD's bus probes is well known -- nexus is walked for child buses, then these buses are plumbed into NEWBUS, e.g. cpu0...cpuN on nexus itself, PCI buses, and PCI subordinate buses in that order. ...
    (freebsd-questions)
  • Re: Interfacing the c64
    ... bus between these two chips also has at least 14 address lines. ... > I'd rather design for the future. ... As you have apparently absolutely no idea about hardware, ... > PCI-X is not PCI Express. ...
    (comp.sys.cbm)
  • Re: KITL with Product Ethernet, not working
    ... I am not a hardware expert. ... internal PCI bus/bridge should be able to respond to some ... What about the I/O port space that your PCI network devices claim? ... >bus and another for the external PCI bus. ...
    (microsoft.public.development.device.drivers)