|
Jacob Coby wanted us to know:
>I've got a Dell 2450 with a built-in Intel Pro/100. I need to add a
>second NIC to the system for backing-up our data, so we purchased an
>Intel Pro/100 card. Every time I install this card, Linux (RedHat 7.3)
>insists on forcing the new card to be eth0 and the built-in to be eth1.
> This completely screws up the networking to the system due to ARP
>issues. Is there any way I can force the built-in to be eth0 and the
>new card to be eth1?
Easies method IMHO, is to change the PCI card to a non eepro100 device
and then you can control in /etc/modules.conf:
alias eth0 eepro100
alias eth1 new_chipset_driver
But that doesn't fix your problem. If you do an lspci, you'll probably
see that your PCI card is listed before the onboard ethernet. Since
they both use the same driver, it's simply finding them by walking down
the pci device list. The order it finds them is the order it assigns
them. There doesn't seem to be any way of telling the module that it
should do one then the other:
[root@tlyons ~]# modinfo -p eepro100
debug:debug level (0-6)
options:Bits 0-3: transceiver type, bit 4: full duplex, bit 5: 100Mbps
full_duplex:full duplex setting(s) (1)
congenb:Enable congestion control (1)
txfifo:Tx FIFO threshold in 4 byte units, (0-15)
rxfifo:Rx FIFO threshold in 4 byte units, (0-15)
txdmaccount:Tx DMA burst length; 128 - disable (0-128)
rxdmaccount:Rx DMA burst length; 128 - disable (0-128)
rx_copybreak:copy breakpoint for copy-only-tiny-frames
max_interrupt_work:maximum events handled per interrupt
multicast_filter_limit:maximum number of filtered multicast addresses
So you're stuck unless you can do option 1.
--
Regards... Todd
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. --Benjamin Franklin
Linux kernel 2.6.8.1-12mdkenterprise 2 users, load average: 0.07, 0.04, 0.03
|
