THanks for you help
cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
BROADCAST=66.xxx.xxx.255
HWADDR=00:08:A1:7D:7A:A2
IPADDR=66.xxx.xxx.240
NETMASK=255.255.255.128
NETWORK=66.xxx.xxx.128
GATEWAY=66.xxx.xxx.254
ONBOOT=yes
TYPE=Ethernet
cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
BOOTPROTO=static
BROADCAST=192.168.0.255
HWADDR=00:0E:2E:65:8C:B4
IPADDR=192.168.0.159
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes
TYPE=Ethernet
cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
BOOTPROTO=static
BROADCAST=192.168.1.255
IPADDR=192.168.1.55
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
TYPE=Ethernet
ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:A1:7D:7A:A2
inet addr:66.xxx.xxx.240 Bcast:66.208.187.255 Mask:255.255.255.128
inet6 addr: fe80::208:a1ff:fe7d:7aa2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:114818 errors:0 dropped:0 overruns:0 frame:0
TX packets:2548892 errors:0 dropped:0 overruns:5 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11340784 (10.8 MiB) TX bytes:2739165429 (2.5 GiB)
Interrupt:217 Base address:0xcc00
eth1 Link encap:Ethernet HWaddr 00:0E:2E:65:8C:B4
inet addr:192.168.0.159 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:2eff:fe65:8cb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2028781 errors:0 dropped:3 overruns:0 frame:0
TX packets:220425 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:306640355 (292.4 MiB) TX bytes:53857017 (51.3 MiB)
Interrupt:225 Base address:0x4800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:103089 errors:0 dropped:0 overruns:0 frame:0
TX packets:103089 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:117074950 (111.6 MiB) TX bytes:117074950 (111.6 MiB)
lo:0 Link encap:Local Loopback
inet addr:66.208.187.10 Mask:255.255.255.255
UP LOOPBACK RUNNING MTU:16436 Metric:1
On 2/11/06, Jeff Vian <jvian10@xxxxxxxxxxx> wrote:
> On Sat, 2006-02-11 at 01:21 -0600, Randy Paries wrote:
> > Man this is driving me crazy
> >
> > I tried your suggestion
> >
> > here is dmesg part
> > eth0: RealTek RTL8139 at 0xf883cc00, 00:08:a1:7d:7a:a2, IRQ 217
> > eth0: Identified 8139 chip type 'RTL-8100B/8139D'
> > r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> > ACPI: PCI Interrupt 0000:01:09.0[A] -> GSI 17 (level, low) -> IRQ 225
> > eth1: Identified chip type is 'RTL8169s/8110s'.
> > eth1: RTL8169 at 0xf8844400, 00:12:17:5c:af:72, IRQ 225
> > r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> > ACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 233
> > eth2: Identified chip type is 'RTL8169s/8110s'.
> > eth2: RTL8169 at 0xf8846800, 00:0e:2e:65:8c:b4, IRQ 233
> >
> >
>
> excellent
>
> > cat /etc/modprobe.conf
> > alias eth1 r8169
> > alias eth0 8139too
> > alias eth2 r8169
> >
> excellent
>
>
> > cat ifcfg-eth2
> > DEVICE=eth2
> > BOOTPROTO=static
> > BROADCAST=192.168.1.255
> > IPADDR=192.168.1.55
> > NETMASK=255.255.255.0
> > NETWORK=192.168.1.0
> > ONBOOT=yes
> > TYPE=Ethernet
> >
> What about the contents of ifcfg-eth0 and ifcfg-eth1
> The only thing different in my file than yours above is that I have
> BOOTPROTO=none
> where you have
> BOOTPROTO=static
>
> I am not sure it is important, but it is a difference.
> I am more inclined to think it is something else in the files above and
> we need to see all 3 at the same time to tell.
>
> Also please send the output of an "ifconfig" command as well.
>
> > from /var/logs/messages
> > Feb 11 01:07:58 lovejoy kernel: eth0: RealTek RTL8139 at 0xf883cc00,
> > 00:08:a1:7d:7a:a2, IRQ 217
> > Feb 11 01:07:58 lovejoy kernel: r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> > Feb 11 01:07:58 lovejoy kernel: ACPI: PCI Interrupt 0000:01:09.0[A] ->
> > GSI 17 (level, low) -> IRQ 225
> > Feb 11 01:07:58 lovejoy kernel: eth1: RTL8169 at 0xf8844400,
> > 00:12:17:5c:af:72, IRQ 225
> > Feb 11 01:07:58 lovejoy kernel: r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> > Feb 11 01:07:58 lovejoy kernel: ACPI: PCI Interrupt 0000:01:0a.0[A] ->
> > GSI 21 (level, low) -> IRQ 233
> > Feb 11 01:07:58 lovejoy kernel: eth2: RTL8169 at 0xf8846800,
> > 00:0e:2e:65:8c:b4, IRQ 233
> >
> excellent
>
> > BUT!!!!!!!!!!!!!!!!!!!!
> > still no work ARG!
> >
> > i still get the error
> > can not change name of eth2 to eth1 file exists
> > and
> >
> > R8169 device eth2 does not seem to be present
> >
> > Any other suggestions
> >
> I suspect it is now an error in the ifcfg-ethX files.
> Send the listing of all 3 and lets look at them.
>
> All 3 devices were created as seen from the output of dmesg and
> in /var/log/messages.
>
> >
> > On 2/9/06, Jeff Vian <jvian10@xxxxxxxxxxx> wrote:
> > > On Wed, 2006-02-08 at 22:58 -0600, Randy Paries wrote:
> > > > hello,
> > > > I am running fedora 4
> > > > 2.6.15-1.1830_FC4smp
> > > >
> > > > I am having problems adding a second RTL-8169 G GB Nic card
> > > >
> > > > when the system boots it says "can not change name of eth2 to eth1 file exists
> > > >
> > > > does not even try to install load eth2
> > > >
> > > > on the ifconfig -a (see below) there is a device dev5036 . Not sure
> > > > what that is
> > > >
> > > > Thanks for any help
> > > >
> > > > #======================================================
> > > > cat /etc/modprobe.conf
> > > > alias eth1 r8169
> > > > alias scsi_hostadapter ata_piix
> > > > alias usb-controller ehci-hcd
> > > > alias usb-controller1 uhci-hcd
> > > > alias ieee1394-controller ohci1394
> > > > alias eth0 8139too
> > > >
> > > You have added the second adapter but not added an alias line here.
> > > Thus it is trying to load the driver r8169 and reassign eth1 to the
> > > second instance of that but fails because it is already used.
> > >
> > > My suggestion:
> > > 1. copy /etc/sysconfig/network-scripts/ifcfg-eth1
> > > to /etc/sysconfig/network-scripts/ifcfg-eth2.
> > > 2. Edit the new file and change the device name and IP address
> > > 3. Edit /etc/modprobe.conf to add a new alias for eth2
> > > alias eth2 r8169
> > > 4. Reboot and see if that fixes things.
> > >
> > > You can look at the output of dmesg to see what devices are
> > > detected/configured during boot (and also a lot of detail
> > > in /var/log/messages).
> > >
> > >
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
