Mark wrote:
> Allen Kistler wrote:
>>Allen Kistler wrote:
>>
>>>I saw this occasionally in FC3 when booting, but I think I see it more
>>>often in FC5. My relevant modprobe.conf lines are as follows ...
>>>
>>>alias eth0 tg3
>>>alias eth1 ipw2200
>>>
>>>Yet sometimes ...
>>
>>... ipw2200 gets eth0 and tg3 gets eth1....
>>
>>> [snip]
>>>
>>>Thanks in advance for any info.
>
> I think you can go into the respective ifcfg-eth{0,1} files
> in /etc/sysconfig/network-scripts and set the HWADDR
> values to the ones for each HW address for the cards
> (which you can see by using {if/iw}config commands to see the reported
> HWaddr for each one).
> Mark

I'm pretty sure the ifcfg-ethX scripts only run when the interface comes
up, after the alias is assigned, which should happen at module load.

Interestingly there is a new FC5 initscripts rpm (dated 7/7) which lists
as its changes:

> initscripts-8.31.5 adds a udev helper for renaming devices,
> so that devices are renamed to their configured name on
> module load, as opposed to when they are brought up. It also
> fixes initialization of bridging interfaces, and cleans up
> an error message on boot from newer CUPS packages.

I haven't dug into the package to see what the new "udev helper"
actually does, but I'll give it a whirl and see if it appears to help.