Network Setup

[GBoon]

I've just installed Linux for the first time (Caldera eDesktop 2.4).

I need to get the PC connected to a network I'ce had running uncer Windows for some time.

However, I cannot ping other machines on the network. Although pinging itself is ok.

if I issue ifconfig eth0 up I get:

SIOCSIFFLAGS: Resource temporarily unavailable

The network card I have is an Netgear FA310TX.

Could anyone give me a pointer as to what I need to do to get it working?

[FoBoT]

Originally posted by GBoon:
<STRONG>
if I issue ifconfig eth0 up I get:
</STRONG>

if the card is already up, then ??
what if you try "ifconfig eth0" without the up, since the card might already be running

what do you get?

[GBoon]

if I issue ifconfig eth0 I get:

eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xx
inet addr:1.1.1.2 BCast:1.1.1.255 Mask: 255.255.255.0
BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Rx Packets:0 errors:0 dropped:0 overruns:0 frame:0
Tx Packets:0 errors:0 dropped:0
overruns:0 carrier:0
Collisions:0 txqueuelen:100
Base address: 0xa400

[FoBoT]

Originally posted by GBoon:
<STRONG>if I issue ifconfig eth0 I get:
inet addr:1.1.1.2 BCast:1.1.1.255 </STRONG>
did you set your ip address to 1.1.1.2 on porpoise?? that is kinda unusual, although it can work

looks like your card is working just fine
you said you could ping 1.1.1.2 also right?

so , uh, that should all be good, what exactly isn't doing what you want?
if you can't ping another local box, from their then how is the other boxen setup??

[GBoon]

I setup 1.1.1.2 on purpose, no particular reason. This is what is used on Windows on the same box. I have another PC setup with 1.1.1.1. Which from windows I can ping, but when I try it from linux I get network unreachable returned. pinging 1.1.1.2 works fine.

if I do dmesg I get:

eth0: Lite-On 82c168 PNIC rev 32 at 0xa400, xx:xx:xx:xx:xx:xx, IRQ 0

IRQ 0 seems possibly wrong to me?

[DMR]

Turn off Plug-N-Play in your BIOS (before mdwatts reads your post and goes ballistic on you ;) ). The SIOCSIFFLAGS error, combined with the IRQ0 message, indicate a resource conflict usually caused by having PNP enabled.

[Dylan]

type:

insmod rtl8139
then go to www.linux.com/firststep/newsitem.phtml?sid=10&aid=4173 (http://www.linux.com/firststep/newsitem.phtml?sid=10&aid=4173)

ignore the ether= part, just type in the other commands

[FoBoT]

uh no, if the card has an ip, then it is working just fine
the funny message is showing when ifconfig eth0 up is issued after the card is already up

it is a routing issue, i will bet one pie! ;)

check the routing part of this NHF (http://www.linuxnewbie.org/nhf/intel/network/nicinstall.html)

Adding routes
- If your machine doesn't know wich interface to get to the network from, you will get a "Network is unreachable" error. The following command will tell your machine to send all internet bound packets out through your eth0 interface.

route add default eth0

[GBoon]

if I issue route add default eth0 then I get the following response:

SIOCADDRT: Network is down

Even though I can still ping the box with it's own IP address (1.1.1.2).

However, I did as suggested also that I turn off PnP in the bios and I can now ping the network.

A couple of Q's, why do I need to turn PnP off? and when I add Windows to the PC am I going to have to turn PnP on and off when switching between Linux and Windows. Seems a bit of a bind to me.

[Bills_a_bub]

GBoon,

Can't help you much on the networking issue, but a comment you made caught my eye:

A couple of Q's, why do I need to turn PnP off? and when I add Windows to the PC am I going to have to turn PnP on and off when switching between Linux and Windows. Seems a bit of a bind to me.

First off, no you won't have to switch PnP on and off between OSs. Windows will actually work with it.

Now the part that concerns me. My understanding is that if you are to run both Windows and Linux on the same machine, you must install Windows first and then Linux.

Reason being when you install Windows, it rewrites the Master Boot Record (MBR) regardless of the content. So you'll lose any reference to Linux.

Thought I'd give you a heads-up.

Now back to your regularly scheduled thread...

[FoBoT]

D'oh!
guess i owe somebody a pie :(

this is why dual booting isn't quite as "neeto" as it sounds

there are differences in how linux and windows access certain types of hardware, like nics, and so you may have to setup the hardware differently for different OS's to access it correctly

glad you got it working :)

[bdg1983]

Turn off Plug-N-Play in your BIOS (before mdwatts reads your post and goes ballistic on you ). The SIOCSIFFLAGS error, combined with the IRQ0 message, indicate a resource conflict usually caused by having PNP enabled.

Am I that bad? I'll stay away from the resource conflict posts in the future. Just let everyone know to search the forums before posting their ethernet/resource problems. ;)

Shouldn't be too hard to do.

Take note for self... No more PnP OS threads. Click on 'Back Button' immediately. :(

Gonna be hard though. I will succeed.