CentOS 5.3 Anaconda nic device ordering

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I have a bunch of HP BL465c G5 blades, with additional dual-port network
adapters. The onboard interfaces use the bnx2 driver, while the
expansion card uses tg3.

All 4 interfaces are detected by both Anaconda and the installed system,
but Anaconda is reversing the ordering:

Anaconda:
	eth0 Card 2, Port 1
	eth1 Card 2, Port 2
	eth2 Card 1, Port 1
	eth3 Card 1, Port 2

BIOS and Installed Kernel:
	eth0 Card 1, Port 1
	eth1 Card 1, Port 2
	eth2 Card 2, Port 1
	eth3 Card 2, Port 2

The main problem I have is that the ifcfg-eth* files have the wrong
HWADDR lines in them for the actual network cards. dmesg shows the
interfaces in the correct order.

I've tried, unsuccessfully to use the "device eth bnx2:tg3" syntax
within my kickstart file, as suggested here:
http://fedoraproject.org/wiki/Anaconda/NetworkIssues#Mixed_NIC_Cards_and_Drivers

If I just use the device line in my kickstart, this doesn't appear to
have any effect on the device ordering at all, and using "noprobe nonet"
just stops anything from being detected at all.


Is there any way to get anaconda to load the drivers in a different
order on CentOS 5.3?

Mark.

-- 
Mark Watts BSc RHCE MBCS
Senior Systems Engineer, Managed Services Manpower
www.QinetiQ.com
QinetiQ - Delivering customer-focused solutions
GPG Key: http://www.linux-corner.info/mwatts.gpg

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux