Help NIC Problem!

**Hunkah** · 06-01-2004, 08:46 AM

OK my driver exists, if I continue with all the rest of the commands, will it automatically locate the driver by knowing the results of the previous command? Because I tried that and it didn't work.

**user unknown** · 06-01-2004, 05:36 PM

Which exist? eepro100 or e100 or both?

The other commands only depend on the fine location of the drivers, not on commands you used to find them.
You can assume the location IS fine.

'Didn't work' is a very general report.
What didn't work?
modprobe eepro100?

What is the output?

**Hunkah** · 06-01-2004, 06:00 PM

Sorry I am using two computers to work this out. I shut the other one off. I will give you the full output if you need it. I will give you what I remember in hopes that it is enough.

I noticed that there were no errors with the eepro100.

When I did the modprobe e100 there was an error.

I found both drivers witht the "locate" command.

**user unknown** · 06-01-2004, 06:06 PM

Then forget about the e100 driver.

After

Code:

modprobe eepro100

, if there is no error, test with

Code:

lsmod | grep eepro100

This should show the driver being loaded.
A loaded driver normally indicates a matching between hardware and driver.

The next command is

Code:

ifconfig eth0 192.168.0.2 up

**Hunkah** · 06-02-2004, 04:49 AM

HOLY CRAP!!! It works!!! I tried this friggin three times and said, "Man do I ever suck"! I can't get this to work. Then I tried the internet configurations wizard in the "Control Center" and changed the proxy settings to automatic and presto! I can connect to the internet! FINALLY!

Thank-you for all your hard work and patience. I couldn't have done this without your help.

Actually, I know I wouldn't have been able to do this without your help. I might have gotten it to connect to the internet, but there is no way I would have known how to install the driver for the NIC.

Thanks again!