Help NIC Problem!

**Hunkah** · 05-27-2004, 10:39 PM

Help, I don't know where to go about finding a "device manager" in Linux.

I don't know what my NIC is, (Other then imbedded).

My NIC gets discovered and works great in live boot, but not in knx2hd install.

How do I fix it and configure it? Please explain in detail. I don't know Linux shortcuts yet.

**pulsar** · 05-28-2004, 02:16 PM

To configure your network card press the penquin icon on the taskbar next to Kmenu. Then select Network/Internet > Network card configuration. Select your card wich is mostly eth0 > then select dhcp.
Hopefully this will help you out.

**Hunkah** · 05-29-2004, 05:46 AM

Nope, It said that there were no supported network cards found.

My problem is that it isn't even being detected. Yet if I boot from the cd it works perfect.

**DimGR** · 05-29-2004, 11:56 AM

Originally Posted by Hunkah

Nope, It said that there were no supported network cards found.

My problem is that it isn't even being detected. Yet if I boot from the cd it works perfect.

before you do what pulsar said you need to load the card's driver
do a modprobe driver_name

I am assuming you know the name of the driver ...

**Hunkah** · 05-31-2004, 03:40 AM

If this was a windows OS I could do everything in a heart beat.

I am new to *nix in every way!

I don't even have my feet wet yet. I am doing this install for the first real time. I actually intend to use this one.

I don't know the driver name, nor the NIC manufacturer. It is an on board NIC. I was hoping to get some information on how to find out what Knoppix CD knows, that the knx2hd install doesn't.

Anyone know how to find out that information? Wanna tell me how to find it.

Is there a device manager in Linux? Is there a command in the command line that would tell me?

When I find out the driver name how do I install it in the knx2hd?

**user unknown** · 05-31-2004, 05:13 AM

No devicemanager, but a commandline:

Code:

lspci | grep Ethernet

should help.
lspci: LiSt PCI
|: don't show the output, but send it to the next command, which is:
grep: grep grabs a token (Ethernet) in the input, and prints the line, containing the token to the screen.
For me it looks like this:
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
If there is no output, call lspci without grep. You might detect the device.

The next step will be to try to load the kernelmodule, which is for me

Code:

modprobe 8139too

- but step by step...

**Hunkah** · 05-31-2004, 10:08 AM

So far so good. I loaded knoppix from the disk and did what you said, now I have some information for you.

Here is my NIC info:
0000:00:06.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 02)

But now what do I need to do to get it up and running on the HD install?

**user unknown** · 05-31-2004, 07:15 PM

My next step was to search for the token '82557' in the kernel-sources:

Code:

cd /usr/src/linux
grep -R 82257 * 2>/dev/null

grep is a command-line search utility.
-R means: recursively, look in the subdirectorys
82257 is the expression to search for
* is the filepattern: every file
2>/dev/null means: send errormessages (2=erroroutput, 1=normal output) to /dev/null, a phantom-device which means 'nowhere' (so it will not been sent to the console).

Grep finds matches in:

Code:

drivers/net/eepro100.c
drivers/net/e100.c
drivers/pci/devlist.h
drivers/pci/pci.ids

I would guess the eepro100 is apropriate. We could read the sourcecode now, or simply test.
I would prefer a simple test:

Code:

lsmod | grep eepro100
lsmdo | grep e100

should show, if one of these drivers is actually loaded.
If none of these is loaded, I would try to load one of them, and perhaps - if errors occur, the other:
(as root

Code:

modprobe eepro100
modprobe e100

No output indicates success.
Next step on success is setup:

Code:

ifconfig eth0 192.168.0.2 up

But now I wait for your response.

Note: The driver could be compiled into the kernel, which would lead to no response when 'lsmod' is called, and maybe to an error, when 'modprobe' is called.

**Hunkah** · 06-01-2004, 05:01 AM

Originally Posted by user unknown

My next step was to search for the token '82557' in the kernel-sources:

Code:

cd /usr/src/linux
grep -R 82257 * 2>/dev/null

grep is a command-line search utility.
-R means: recursively, look in the subdirectorys
82257 is the expression to search for
* is the filepattern: every file
2>/dev/null means: send errormessages (2=erroroutput, 1=normal output) to /dev/null, a phantom-device which means 'nowhere' (so it will not been sent to the console).

Grep finds matches in:

Code:

drivers/net/eepro100.c
drivers/net/e100.c
drivers/pci/devlist.h
drivers/pci/pci.ids

I didn't get this output at all, it just paused for a few seconds and then I got the empty prompt.

I would guess the eepro100 is apropriate. We could read the sourcecode now, or simply test.
I would prefer a simple test:

Code:

lsmod | grep eepro100
lsmdo | grep e100

should show, if one of these drivers is actually loaded.
If none of these is loaded, I would try to load one of them, and perhaps - if errors occur, the other:
(as root

Code:

modprobe eepro100
modprobe e100

No output indicates success.
Next step on success is setup:

Code:

ifconfig eth0 192.168.0.2 up

But now I wait for your response.

Note: The driver could be compiled into the kernel, which would lead to no response when 'lsmod' is called, and maybe to an error, when 'modprobe' is called.

**user unknown** · 06-01-2004, 06:45 AM

I didn't get this output at all, it just paused for a few seconds and then I got the empty prompt.

That needn't be a problem.
Your installation is just without the kernel-sources, but the driver might be there though.
The installed driver should be in /lib/modules/2.x.y/...somewhere
with x.y as your major-minor kernel-numbers.

Code: