Help NIC Problem!

[Hunkah]

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]

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]

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]

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]

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]

No devicemanager, but a commandline:

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

modprobe 8139too - but step by step...

[Hunkah]

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]

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



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:


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:


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:)


modprobe eepro100
modprobe e100


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


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]

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



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:


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:


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:)


modprobe eepro100
modprobe e100


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


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]

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.


locate eepro100
locate e100
should show you without searching.

Trying the next steps - lsmod (not lsmdo -sorry) and modprobe will tell you, if they don't find the driver.

[Hunkah]

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]

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]

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]

Then forget about the e100 driver.

After
modprobe eepro100, if there is no error, test with

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
ifconfig eth0 192.168.0.2 up

[Hunkah]

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!

[user unknown]

You're welcome.