On Sat, Nov 28, 2009 at 2:55 PM, Ross Walker rswwal...@gmail.com wrote:
On Nov 28, 2009, at 3:10 PM, Les Mikesell lesmikes...@gmail.com wrote:
Tom H wrote:
Digging around google a bit more I came up with different rules,
and
fingers crossed, they seem to work!
SUBSYSTEM==net,
On Nov 29, 2009, at 3:27 AM, Rob Townley rob.town...@gmail.com wrote:
On Sat, Nov 28, 2009 at 2:55 PM, Ross Walker rswwal...@gmail.com
wrote:
There was a kernel update maybe the move from C4 to C5 which caused
grief with Dell hardware, where it reversed the order Broadcom
devices
are
Rob Townley wrote:
NIC ordering is a problem. Some say it is the multi cpu, some say bad
BIOS, some say MAC address ordering is better, some say PCI bus
enumeration is better. The netdev mailing list has had a long running
discussion on this issue. The CTO of Dell and members of HP along
On Sun, Nov 29, 2009 at 10:57 AM, Les Mikesell lesmikes...@gmail.com wrote:
Rob Townley wrote:
NIC ordering is a problem. Some say it is the multi cpu, some say bad
BIOS, some say MAC address ordering is better, some say PCI bus
enumeration is better. The netdev mailing list has had a long
KERNEL==eth?, SYSFS{address}==00:21:e9:17:64:b5, NAME=eth1 #
Now, all three network cards get assigned as eth0! eth1 and eth2 are
no longer found. The pci-express nics (onboard) get detected first,
and the pci nic is last, so it ends up owning the eth0 alias.
Changing SYSFS to ATTR should
On 11/22/2009 8:38 PM, Gordon McLellan wrote:
I have two servers with identical hardware ... TYAN i3210w system
boards with dual intel gigabit interfaces, and a PCI intel gigabit
nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5
Every other time I reboot, the nics initialize in a
Digging around google a bit more I came up with different rules, and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0 #
pro/1000gt
SUBSYSTEM==net, SYSFS{address}==00:e0:81:b5:7a:30, NAME=eth1 #
internal 1
SUBSYSTEM==net,
Digging around google a bit more I came up with different rules, and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0
# pro/1000gt
SUBSYSTEM==net, SYSFS{address}==00:e0:81:b5:7a:30, NAME=eth1
# internal 1
SUBSYSTEM==net,
Tom H wrote:
Digging around google a bit more I came up with different rules, and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0
# pro/1000gt
SUBSYSTEM==net, SYSFS{address}==00:e0:81:b5:7a:30, NAME=eth1
# internal 1
SUBSYSTEM==net,
On Nov 28, 2009, at 2:15 PM, Tom H tomh0...@gmail.com wrote:
Digging around google a bit more I came up with different rules,
and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0
# pro/1000gt
SUBSYSTEM==net,
On Nov 28, 2009, at 3:10 PM, Les Mikesell lesmikes...@gmail.com wrote:
Tom H wrote:
Digging around google a bit more I came up with different rules,
and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0
# pro/1000gt
SUBSYSTEM==net,
The formula that ended up working for me:
undo modifications to udev rules
comment out the alias ethX lines that anaconda had placed in my modprobe.conf
use HWADDR= in the ifcfg-ethX config files.
slave interfaces have onboot=yes in them, despite no IP address information
The nics are correctly
On Sun, Nov 22, 2009 at 9:33 PM, Tom H tomh0...@gmail.com wrote:
On Mon, Nov 23, 2009 at 2:38 AM, Gordon McLellan gordonth...@gmail.com
wrote:
KERNEL==eth?, SYSFS{address}==00:21:e9:17:64:b5, NAME=eth1 #
Now, all three network cards get assigned as eth0! eth1 and eth2 are
no longer found.
On Mon, Nov 23, 2009 at 8:04 AM, Gordon McLellan gordonth...@gmail.com wrote:
Digging around google a bit more I came up with different rules, and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0 #
pro/1000gt
SUBSYSTEM==net,
Gordon McLellan wrote:
On Mon, Nov 23, 2009 at 8:04 AM, Gordon McLellan gordonth...@gmail.com
wrote:
Digging around google a bit more I came up with different rules, and
fingers crossed, they seem to work!
SUBSYSTEM==net, SYSFS{address}==00:1b:21:4d:c3:e8, NAME=eth0 #
pro/1000gt
On Nov 23, 2009, at 8:29 AM, Gordon McLellan gordonth...@gmail.com
wrote:
On Mon, Nov 23, 2009 at 8:04 AM, Gordon McLellan gordonth...@gmail.com
wrote:
Digging around google a bit more I came up with different rules, and
fingers crossed, they seem to work!
SUBSYSTEM==net,
I have two servers with identical hardware ... TYAN i3210w system
boards with dual intel gigabit interfaces, and a PCI intel gigabit
nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5
Every other time I reboot, the nics initialize in a different order.
anaconda had setup
On Mon, Nov 23, 2009 at 2:38 AM, Gordon McLellan gordonth...@gmail.com wrote:
The archives seem to suggest fiddling with udev to
be the answer. So I modify /etc/udev/rules.d/60-net (or something)
and add a few rules found in an ancient example (those aren't my mac
addresses):
KERNEL==eth?,
18 matches
Mail list logo
