8139too device eth1 does not seem to be present, delaying initializing

[sebasr]

hi all,

I have added a new nic (RTL 8139) to my pci slot as eth1. I have the same RTL8139 as my eth0 also.
Both the NICs are working fine in windows, but, in FC5 eth1 is not working,

when i try.
#service network restart

it is showing the error " Bringing up eth1: 8139too device eth1 does not seem to be present, delaying initializing"

what should i do to have my eth1 up?? I found the sam type of problems faced my many others, but none of them gives a clean and crisp solution to the end.

Thanks in advance.

Seban

[giulix]

Have you tried adding a line

alias eth1 8139too

to your /etc/modprobe.conf and rebooting ?

[sebasr]

Yes I tried it before. but when i restart, the same error "...delaying initialization..." is shown.

I am attaching the modprobe.conf file. please check it.

#alias eth0 8139too
#alias eth1 8139cp
alias eth0 8139too
alias eth1 8139too
#options eth0 -o 8139too-0 io=0xb400 irq=23
#options eth1 -o 8139too-1 io=0xb800 irq=17
options eth0 io=0xb400 irq=23
options eth1 io=0xb800 irq=17
alias scsi_hostadapter ata_piix
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
options snd-intel8x0 index=0
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0

The commented codes are the previous values.

[giulix]

It's the same as mine (I have 2 very similar NICs that use the same driver, 8139too). When you added the new NIC, did Kudzu recognize it and try to configure it after you rebooted ?

[sebasr]

what is Kudzu? How could i know whether it had recognized my NIC? Else, how can i configure it?

[sebasr]

Yes! eth1 is detected in kudzu.

class: NETWORK
bus: PCI
detached: 0
device: eth1
driver: 8139too
desc: "Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+"
network.hwaddr: 00:07:40:8e:95:6a
vendorId: 10ec
deviceId: 8139
subVendorId: 1154
subDeviceId: 0313
pciType: 1
pcidom: 0
pcibus: 1
pcidev: 2
pcifn: 0
-
class: NETWORK
bus: PCI
detached: 0
device: eth0
driver: 8139too
desc: "Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+"
network.hwaddr: 00:16:76:a7:22:29
vendorId: 10ec
deviceId: 8139
subVendorId: 8086
subDeviceId: 0c4a
pciType: 1
pcidom: 0
pcibus: 1
pcidev: 3
pcifn: 0

[giulix]

Kudzu is that piece of software supposed to detect changes in your hardware configuration. When I plugged in my second NIC, I remember it popping up during boot (it's an application written in curses, with a character interface) to ask me if I wanted to configure my new NIC straight away, and of course I answered yes. Now, I don't know whether it is still supposed to behave like that in FC6, but I think so.
If the same didn't happen to you, that may mean that either it didn't recognize your new NIC or there is something different or broken in your installation (or possiblly in FC6).
Let's see if someone else comes to the rescue, as I really don't know the inner workings of Kudzu and the man page advises against running it to detect a NIC after the network's started.

[sebasr]

Anyway, thanks for the pain you have taken.
Hope someone else could save me and my NIC. :-)

[giulix]

Good! Next step: Can you please list the contents of /etc/sysconfig/network-scripts ?

[sebasr]

Sure, here it is..

total 32
drwxr-xr-x 2 root root 4096 Oct 31 15:30 ./
drwxr-xr-x 4 root root 4096 Aug 31 16:04 ../
-rw-r--r-- 3 root root 257 Oct 31 15:09 ifcfg-eth0
-rw-r--r-- 3 root root 253 Oct 31 15:09 ifcfg-eth1

[giulix]

Weird... it's there, but the system doesn't see it. Check the contents of ifcfg-eth1 to make sure everything's fine. Here's mine with the MAC address anonymized, for reference:

# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth1
BOOTPROTO=none
BROADCAST=192.168.1.255
HWADDR=XX:XX:XX:XX:XX:XX
IPADDR=192.168.1.1
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
TYPE=Ethernet

Anyway, it seems that I have no clean and crisp solution fot that, after all. Let's hope someone who has solved this problem joins in...

[sebasr]

My ifcfg-eth0 is like this:

# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:16:76:A7:22:29
IPADDR=10.101.63.195
NETMASK=255.255.255.0
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=no
GATEWAY=10.101.63.1
TYPE=Ethernet
DHCP_HOSTNAME=192.168.10.1
/etc/sysconfig/networking/devices/ifcfg-eth0 (END)

While ifcfg-eth1 is like..

# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
DEVICE=eth1
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.10.10
GATEWAY=192.168.10.1
/etc/sysconfig/networking/devices/ifcfg-eth1 (END)

In eth1 two things are missing,
1. HWADDR
2. DHCP ip (i am using static ip so dhcp server is not used).

[giulix]

Yes, I use eth0 for my external connection and eth1 for my LAN. Yours are the other way round. I don't think the HWADDR is absolutely necessary, but you can add it if you still have the package the NIC came into (is usually written on the box). Still, I can't figure out what's wrong...

[sebasr]

I am using the same way you use. I use eth0 for internet and eth1 for local connection.

[giulix]

Then there is something wrong. If you get your IP address from your ISP, BOOTPROTO should be dhcp for eth0. Also, PEERDNS should be no for eth1, but yes for eth0. Anyway, I don't think this is the reason why the interface cannot be initialized...