Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jan 2009 13:06:26 +0000
From:      "Bruce M. Simpson" <>
To:        Yony Yossef <>
Cc:        Liran Liss <>,, Oleg Kats <>, "'H.fazaeli'" <>, Eitan Shefi <>,
Subject:   Re: howto determine network device unit number? device.hints?
Message-ID:  <>
In-Reply-To: <000c01c976ec$87e040b0$>
References:  <>	<>	<000b01c9768e$745aa160$>	<> <000c01c976ec$87e040b0$>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Yony Yossef wrote:
> Thanks for the explanation.
> So there's no way to determine this in advance.. 
> I must build a script that contains my own mapping between MAC addresses and
> the wanted interface names and run it after each driver load, rename the
> interfaces if necessary.
> It seems quite wrong, don't you agree?
> And how come the unit number is given an arbitrary value? Is there a good
> reason for that?

Normally the PCI probe runs in the opposite direction from that of 
Linux. It's largely to do with how the NEWBUS code walks the PCI bus. 
 From a systems management point of view, yeah, it's irritating, however 
it would probably take more effort (i.e. kernel code) to try to patch it 
to work differently, and not everyone has free time to sit down and 
patch the kernel.

That and (unlike Solaris) there is no *direct* mapping between the 
card's driver number on the bus and its network driver number.

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?

Want to link to this message? Use this URL: <>