More information

From: ezjab (ezjab_at_ieee.org)
Date: 12/02/04 

Date: Thu, 02 Dec 2004 20:55:33 GMT

I have talked to tech support of the motherboard manufacturer
and was told that I would need a linux driver for the
onboard device which turns out to be from Marvell Technology
and is a Yukon 88E8001 device. I've looked at their website
and there is a driver, but I have not downloaded it yet.

In the meantime, I have installed an ethernet PCI card into
the PC. When I reboot and try to connect to the ethernet
through the PCI card, I still get:

        connect: Network is unreachable

when I try to ping the router. So, I still need help to get
an ethernet connection working.

ezjab wrote:
>
> Hi,
>
> I have a new PC where I have installed Red Hat Fedora Core 1.
> Among other things, my ethernet interface is not working.
>
> My other LAN PCs are working with my current router so I know
> it is working properly. I know I have a 'live' ethernet cable
> because I'm switching it from my laptop to the new PC to test.
> I checked the BIOS and onboard LAN support is enabled.
>
> I noticed some error messages when booting but they scrolled
> by quickly. When I look in /var/log/messages, I find this
> error message, but I don't know the impact:
>
> Dec 2 11:11:10 jjapc9 modprobe: FATAL: Could not load
> /lib/modules/2.6.8.1-10mdk/modules.dep: No such file
> or directory
> There are another 300 lines, give or take, that have similar
> message related to modprobe. This looks suspicious to me.
> Since the floppy disk drive and ethernet interface are not
> working, I cannot get the log messages off the PC to include
> in this post.
>
> If I enter:
>
> ping 192.168.1.101
>
> on a PC already working on the LAN, I get back the expected
> output.
>
> If I enter the same command on the new PC, I get back the
> message:
>
> connect: Network is unreachable
>
>
>
> My assumption is that 'ping' is a very low level command
> and that interfaces directly to a s/w driver that interacts
> with the ethernet hardware. If it is not working, then
> I must have a BIOS or hardware problem. Is there anything
> in Linux that needs to be configured to make ping work?
>
> Jim Anderson