Reply to Thread

all,
I just reinstalled and everything is a-ok!!

thanks to all

I will commence the reinstallation........

Gotta love this Linux though.....

modprobe: Can't locate module 3c90x

not too good I guess??

No other Nic just the pci one.

I will try the code right now....

I just tried to open the linux kernel config in the Control Center and it reads:

cannot open /usr/src/linux-2.4/arch//config.in for reading

I guess the kernel is skrewey, correct?

For kicks try this.
ifconfig eth0 down
modprobe 3c90x
ifconfig eth0 up
ifconfig eth0 (Paste results here)
route (paste results here)

Is there more than one Nic in this machine (one on-board possibly?)

Jkrohn

Honestly I would resinstall. Something looks pretty darn messed up.

1) You seem to have an IP on eth0, but the module for your card doesn't show as loaded.
I don't think it is compiled into the kernel, so this is strange
2) Even though you have an IP from DHCP, it isn't making the appropriate routing table entries.
Even if you manually make the entries now, you would have to make them every time as network scripts are not working correctly it seems.

It would probably be easiest to simply reinstall. We know that your network card is supported (using the 3c90x module) so that isn't the issue.

Jkrohn

my IP address should not be affected if Linux is unable to read my Device Identity Structure of hda correct?

I would have to say that the router is set up correctly since this whole system worked properly about 3-4 days ago.

I just upgraded to Fedora 1 and then boom, the internet connection is not working?

should I reload Fedora?

Jkrohn

I ran the lsmod |grep 3c90 and it comes up with nothing?
Just enters me down another line?

ya it seems your default gateway isn't showing up.

You could try setting it manually

route add default gw 192.168.1.1 (or whatever your gateway IP is)

If you're on DHCP this should be set automatically though.
Is it set correctly in your router?
Is your router set to work in the correct mode?
The linksys router has two different modes.. although I can't remember what they're called at the moment

I checked sys info (Info Center) and under the network interfaces header I found the ip and net mask.

all info matches the routing table.....

Only thing is that the state is down for the broadcast dev not the loopback dev?

Yes, I am running DHCP, I believe?

I ran ifconfig eth0 and the second line reads:
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0

is that the info I should plug into the route table?

there is a See Documentation/networking/vortex.txt message under the /network/vortex.html section....

Your routing table does not look correct at all.
1) You have no default route
2) It looks like you have an IP in the 169 range.
3) Everything in your routing table is going out the loopback device.

Go ahead and paste the output of ifconfig eth0 here.
Also what is your IP/Gateway suppossed to be. Do you have DHCP setup?
Also do this as root or su.
lsmod |grep 3c90

Jkrohn

Vass

I just ran it and it is bringing up information from only today, is that sufficient?

here is what the route command returns:

Destination: Gateway: Genmask: Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Does that look correct?

to get the actual message you should be able to do a

tail -100 /var/log/messages

(change 100 to whatever you need to get the last 100 or so messages)

Maybe that will help us figure out what's going on.

krohnjw

the device is working properly and yes the IP, Subnet, and Gateway are all set properly.

I will check the routing table in a few minutes.

I am still getting the error on boot stating that the eth0 device is failing to ini...

ok, so you have a proper IP address, subnet mask and gateway?
Is the device up? ifconfig eth0 up (although if you have an IP etc it sould be)
Can you ping the gateway? Where is your connection dying?

You might want to take a look at the routing table also (the route command)