Sorry for reposting this but my subject line was inadequate.

I am trying to get my ethernet device working. It uses the Realtek 8139
chip and I am using RedHat 9.0 (kernel 2.4.20-6). After booting lsmod
reports that the 8139too module (driver) is loaded but during the
initialization part of booting I get the following error messgage:

Determining IP information for eth0...iptables: No chain/target/match by
that name failed.
iptables: Bad rule (does a matching rule exist in that chain?)
[FAILED]

I have seen some reports that suggest using the noapic option during
boot so I edit grub.conf to read:

kernel /vmlinuz-2.4.20-6 ro root=LABEL=/ hdc=ide-scsi noapic


However, this does not appear to be solving the problem.

Did I modify the grub.conf file correctly?

Does anyone have suggestions on how to fix this problem?

I think there is nothing to do with kernel parms. Looks like eth0 is down or has no IP address assigned. Firstly boot the system and check if 'ifconfig' shows that eth0 is up and have an IP address set up.

what are you doing to get that error? iptables is responsible for doing firewalls etc, and is not related to the actual NIC at all. try a simple command like "ifup eth0" and see what happens then. check "dmesg" and "ifconfig" for changes if there is nothing more obvious.

Thank you!

Here are the results of ifconfig:

eth0 Link encap:Ethernet HWaddr 00:0D:88:18:E7:E0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:2052 (2.0 Kb)
Interrupt:11 Base address:0xac00

Thanks again

Here is what I get from ifup eth0:

Determining IP information for eth0...iptables: No chain/target/match by that name
failed.
iptables: Bad rule (does a matching rule exist in that chain?)


Which is the same message I get during initialization stage of booting.

Daniel

Eth is up but has no IP address. Probably it is setup to use DHCP and no DHCP client is started. So check firstly the init scripts. Ifconfig has to show the following:
eth0 Link encap:Ethernet HWaddr 00:0D:88:18:E7:E0
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:xxx.xxx.xxx.xxx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

One more thing:

I can ping 10.0.0.1 just fine. So perhaps my Linux configuration is somehow wrong?

Thanks again

what is 10.0.0.1 ? Your IP address? Or external one?

10.0.0.1 is the NIC itself. I think. I found a DSL HOWTO and it suggested pinging
10.0.0.1 as a check on the NIC hardware.

Daniel

So why ifconfig doesn't show this address?

The NIC doesn't have an IP, at least according to your output, so pinging anything is pretty irrelevant at this point.

You need to either enable DHCP for that interface (if you have a DHCP server present, such as on the DSL router), or statically assign an IP with ifconfig (you'll also need to add that to your system configuration so it will get the same IP when it reboots).