Help! linux networking!!!

goal: connect Linux to Windows XP through TCP/IP (I don't need to
share the filesystem, only communicate)
Linux version: Red Flag Linux Desktop 2.4

in /proc/pci:
......
Bus 0, device 12, function 0:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
16)
IRQ 11.
Master Capable. Latency=32. Min Gnt=32. Max Lnt=64.
I/O at 0xe000 [0xe0ff].
Non-prefetchable 32 bit memory at 0xec102000 [0xec1020ff].
.......

So, I guess my network adaptor's IRQ=11, I/O=0xe000


Then I run "netconf" to configure the network:

Client tasks

Host name and IP network devices:

Host name:
Host name + domain: mypc.mydomain
Adaptor:
[x] Enabled
Config mode: (o) Manual ( ) Dhcp ( ) Bootp
Primary name + domain: mypc.mydomain
Aliases (opt): mypc
IP address: 169.254.39.149
Netmask (opt): 255.255.0.0
Net device: eth0
Kernel module: ne
I/O port (opt): 0xe000
Irq (opt): 11

Name Server Specification (DNS):

DNS usage: [ ] DNS is required for normal operation
default domain: mydomain
IP of name server 1: 169.254.39.149
IP of name server 2 (opt):
IP of name server 3 (opt):
search domain 1 (opt):
search domain 2 (opt):
search domain 3 (opt):
search domain 4 (opt):

The rest parts keep default. Click "Accept", unsuccessful.

Type command: ping 127.0.0.1
ok.

Type command: ping 169.254.39.149
Connect: Network is unreachable.


I also changed the file /etc/lilo.conf with:
append="console=/dev/tty2 CONSOLE=/dev/tty2 ether=11,0xe000,eth0"

run lilo. reboot. but the same thing.

when the system was starting, I found the following message on the
screen:
.......
Bringing up interface eth0: insmod: Hint: insmod errors can be caused
by incorrect module parameters, including invalid IO or IRQ parameters
Delaying eth0 initialization. [FAILED]
.......


Can anybody help? Thanks.

John

John X wrote:
>
> goal: connect Linux to Windows XP through TCP/IP (I don't need to
> share the filesystem, only communicate)
> Linux version: Red Flag Linux Desktop 2.4
>
> in /proc/pci:
> .....
> Bus 0, device 12, function 0:
> Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
> 16)
> IRQ 11.
> Master Capable. Latency=32. Min Gnt=32. Max Lnt=64.
> I/O at 0xe000 [0xe0ff].
> Non-prefetchable 32 bit memory at 0xec102000 [0xec1020ff].
....

So, it's an RTL8139 chipset which uses the rtl8139 or 8139too modules.

> Then I run "netconf" to configure the network:
....
> Kernel module: ne

So why are you using the ne module, which is for NE2000 clones?
....

> Bringing up interface eth0: insmod: Hint: insmod errors can be caused
> by incorrect module parameters, including invalid IO or IRQ parameters
> Delaying eth0 initialization. [FAILED]

Hardly surprising.

Use the right module and it should work.

Regards, Ian

Thank you, Ian.

I tried using "rtl8139", "rtl", "8139" and "rtl-8139" as the module
parameter, but still failed.

When reboot:
Setting network parameters: [OK]
Bringing up interface lo: [OK]
Bringing up interface eth0: Delaying eth0 initialization [FAILED]

When ping mypc:
Cennect: Network is unreachable


Anothing I can tell you is, I found in /proc/pci, the IRQ of USB
Controller is the same as that of Ethernet Controller, say IRQ 11.


What should I do? Thanks for help.

John





Ian Northeast <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> John X wrote:
> >
> > goal: connect Linux to Windows XP through TCP/IP (I don't need to
> > share the filesystem, only communicate)
> > Linux version: Red Flag Linux Desktop 2.4
> >
> > in /proc/pci:
> > .....
> > Bus 0, device 12, function 0:
> > Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
> > 16)
> > IRQ 11.
> > Master Capable. Latency=32. Min Gnt=32. Max Lnt=64.
> > I/O at 0xe000 [0xe0ff].
> > Non-prefetchable 32 bit memory at 0xec102000 [0xec1020ff].
> ...
>
> So, it's an RTL8139 chipset which uses the rtl8139 or 8139too modules.
>
> > Then I run "netconf" to configure the network:
> ...
> > Kernel module: ne
>
> So why are you using the ne module, which is for NE2000 clones?
> ...
>
> > Bringing up interface eth0: insmod: Hint: insmod errors can be caused
> > by incorrect module parameters, including invalid IO or IRQ parameters
> > Delaying eth0 initialization. [FAILED]
>
> Hardly surprising.
>
> Use the right module and it should work.
>
> Regards, Ian

On Thu, 03 Jul 2003 08:59:33 -0700, John X wrote:

> Thank you, Ian.
>
> I tried using "rtl8139", "rtl", "8139" and "rtl-8139" as the module
> parameter, but still failed.
>
<snip>

You'll want to use the 8139too module. I'm using the same kind of card
now on a 2.4.20 kernel, and the 8139too module works fine.

The rtl8139 module has (kind of) been replaced by 8139too.

HTH

G

Sometimes when you have an IRQ conflict regardless of module, the eth? will
fail.

In your case if the 8139too ain't available you might have to disable the
USB at BIOS or move the eth? card to a different PCI slot, persuming the
eth? is a PCI card.

"Glen Smith" <(E-Mail Removed)> wrote in message
news(E-Mail Removed) oof.com...
> On Thu, 03 Jul 2003 08:59:33 -0700, John X wrote:
>
> > Thank you, Ian.
> >
> > I tried using "rtl8139", "rtl", "8139" and "rtl-8139" as the module
> > parameter, but still failed.
> >
> <snip>
>
> You'll want to use the 8139too module. I'm using the same kind of card
> now on a 2.4.20 kernel, and the 8139too module works fine.
>
> The rtl8139 module has (kind of) been replaced by 8139too.
>
> HTH
>
> G

You should look at the networking how-to on www.tldp.org

Most 8139's use the 8139too module these days. Have you brought the card
up, and added the route/default route?

ifconfig eth0 192.168.?.? netmask 255.255.?.? up
route add -net 192.168.?.? netmask 255.255.?.? eth0

You can run these to verify:

route -n
netstat -r

If you're using a gateway/router this syntax might help?

route add default gw 192.168.?.? eth0

NOTE: the IP's can be anything allocated to a private network. All of
which is discussed in the how-to's. There are other parts to configure
though. Some of which have scripts that are fairly comprehensive. Others
require you to tack on your rocket science degree and get busy.

HTH,
Shadow_7

"Hal Davison" <(E-Mail Removed)> wrote in message news:3f035b32_4@newsfeed...
> Sometimes when you have an IRQ conflict regardless of module, the eth?
will
> fail.
>

The PCI cards are prepared to share an interrupt request.

Just use the proper driver module. Try:

modprobe 8139too

HTH

Tauno Voipio
tauno voipio @ iki.fi

Thank you all. And thank you very much, James (I failed replying your
email because of the rejecting).

I didn't try because of a busy project. I intended to
reply you after I tried, but it was too long until
today. Sorry for that.

To solve the linux networking problem is important for
me. I think I will follow your instruction to try it
these days. I will report to you then.

Thanks again.



John




(E-Mail Removed) (John X) wrote in message news:<(E-Mail Removed). com>...
> goal: connect Linux to Windows XP through TCP/IP (I don't need to
> share the filesystem, only communicate)
> Linux version: Red Flag Linux Desktop 2.4
>
> in /proc/pci:
> .....
> Bus 0, device 12, function 0:
> Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
> 16)
> IRQ 11.
> Master Capable. Latency=32. Min Gnt=32. Max Lnt=64.
> I/O at 0xe000 [0xe0ff].
> Non-prefetchable 32 bit memory at 0xec102000 [0xec1020ff].
> ......
>
> So, I guess my network adaptor's IRQ=11, I/O=0xe000
>
>
> Then I run "netconf" to configure the network:
>
> Client tasks
>
> Host name and IP network devices:
>
> Host name:
> Host name + domain: mypc.mydomain
> Adaptor:
> [x] Enabled
> Config mode: (o) Manual ( ) Dhcp ( ) Bootp
> Primary name + domain: mypc.mydomain
> Aliases (opt): mypc
> IP address: 169.254.39.149
> Netmask (opt): 255.255.0.0
> Net device: eth0
> Kernel module: ne
> I/O port (opt): 0xe000
> Irq (opt): 11
>
> Name Server Specification (DNS):
>
> DNS usage: [ ] DNS is required for normal operation
> default domain: mydomain
> IP of name server 1: 169.254.39.149
> IP of name server 2 (opt):
> IP of name server 3 (opt):
> search domain 1 (opt):
> search domain 2 (opt):
> search domain 3 (opt):
> search domain 4 (opt):
>
> The rest parts keep default. Click "Accept", unsuccessful.
>
> Type command: ping 127.0.0.1
> ok.
>
> Type command: ping 169.254.39.149
> Connect: Network is unreachable.
>
>
> I also changed the file /etc/lilo.conf with:
> append="console=/dev/tty2 CONSOLE=/dev/tty2 ether=11,0xe000,eth0"
>
> run lilo. reboot. but the same thing.
>
> when the system was starting, I found the following message on the
> screen:
> ......
> Bringing up interface eth0: insmod: Hint: insmod errors can be caused
> by incorrect module parameters, including invalid IO or IRQ parameters
> Delaying eth0 initialization. [FAILED]
> ......
>
>
> Can anybody help? Thanks.
>
> John