Setting up network?

Zeno McDohl · 01-15-2006, 09:26 PM

Okay so I just installed Slackware following this guide:
http://www.bitbenderforums.com/vb22/...?postid=311808

Now I'm at the part where I have to setup the network.

Quote:

The netconfig utility that ran during setup, could not probe for my network adapter. However, I know that it uses the sundance module.

I have no idea what my NIC is, nor what module it uses. Where do I go from here?

J.W. · 01-15-2006, 10:30 PM

To determine your equipment

Code:

lspci -v

The module you might need depends on the NIC you're using. Note that I'm assuming you have a NIC card; if you're using an onboard LAN, please specify the exact mobo you are using

Zeno McDohl · 01-15-2006, 11:32 PM

This is what it says:

Code:

00:10.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 05)

There are more details, but I think we have what is needed.

No idea where to go from here. I tried following that guide somewhat (using eepro100), but have failed to get online.

lord-fu · 01-16-2006, 12:30 AM

Hello,
Sorry I didnt read through the thread you linked but have you got the module you need for your card loaded?

Quote:

Intel Corporation 82557/8/9

lsmod will show you whether it is loaded or not. If it is not then you will have to compile it into your kernel or as a module.
If it does show up as loaded then run through netconfig again. Or maybe just ifconfig eth0 up.

Zeno McDohl · 01-16-2006, 12:36 AM

Yes, it shows up in lsmod, like this:

Code:

eepro100        18836   1

I went through netconfig (using DHCP), then tried ifconfig eth0 up but I still can't like ping google.com or anything.

If I type:

Code:

/etc/rc.d/rc.netdevice

It gives me the error:

Code:

modprobe: Can't locate module eepro100.o

lord-fu · 01-16-2006, 12:40 AM

Hello,
Maybe try
dhcpcd eth0
If that doesnt work.
Whats the output of ifconfig, and netstat -r?

Why try to modprobe when it was already loaded?

Zeno McDohl · 01-16-2006, 12:49 AM

Here's netstat -r:

Code:

Destination      Gateway        Genmask    Flags     MSS Window irtt Iface
loopback         *              255.0.0.0  U           0 0         0 lo

ifconfig:

Code:

lo     Link encap:Local Loopback
       inet addr:127.0.0.1     Mask:255.0.0.0
       UP LOOPBACK RUNNING   MTU:16436  Metric:1
       RX packets:16 errors:0 dropped:0 overruns:0 frame:0
       IX packets:16 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:0
       RX bytes:1216 (1.1 Kb)   TX bytes:1216 (1.1 Kb)

eth0 disappears off ifconfig if I do dhcpcd eth0

As for modprobe, I'm not sure. I was looking around sites to help me with this, and that is what one said to try.

lord-fu · 01-16-2006, 01:03 AM

Ok so whats you setup like any routers, you do want a dynamic ip right? I am sorry that I wont be able to stay and help you more. But I can offer you this
http://slackbook.org/html/book.html
Look at the part about static and dhcp learn to do it from the command line and it will pay off. It is a simple matter of making sure that module is the correct one for your card, making sure its loaded. Then setting up your ip and then your done. Good luck, but I have to go to sleep now.
PS: Dont fret Im sure someone lese will come alon really soon to fill the rest in.
And Im truly sorry if anything I posted was wrong.

Zeno McDohl · 01-16-2006, 01:18 AM

I'm pretty sure that module is for mine, this says so:
http://www.scyld.com/eepro100.html
Correct me if I'm wrong about that.

I've tried it with DHCP, and also setting the IP/etc manually and still can't get online.

Quote:

connect: Network is unreachable

That's what I get everytime.

Thanks though.

Zeno McDohl · 01-16-2006, 12:25 PM

Maybe it is the wrong module?

When a live cable is connected to the computer, no lights turn on...

dombrowsky · 01-16-2006, 12:36 PM

Make sure you've got the correct and most updated driver for your card, and compile it locally on the system. That's how I've always gotten network cards to work with linux. I have very bad luck with pre-built anything. For example, here's my makefile for my rtl8139 card (driver can by found somewhere at scyld.com)

Code:

CC=/usr/bin/gcc

all: rtl8139.o rtl8139-diag
.SUFFIXES: .c.o
.c.o:
        /usr/bin/gcc -I/usr/src -DMODULE -D__KERNEL__ -O6 -c $<

rtl8139.o: kern_compat.h pci-scan.o pci-scan.h

rtl8139-diag:
        gcc -O -o rtl8139-diag rtl8139-diag.c

install:
        install -m 644 rtl8139.o /lib/modules/`uname -r`/net/
        install -m 644 pci-scan.o /lib/modules/`uname -r`/net/

clean:
        rm -f *.o rti8139-diag

you'll need your kernel headers on your system. On my Debian/GNU, they're in a package on the install disks, which makes it nice and easy (package is kernel-headers-2.4.16-686).

-dave

Zeno McDohl · 01-16-2006, 12:47 PM

I'm already lost...

I don't know where to get the most updated version of the driver, and I don't know where I would find it locally or how to compile it. I know how to use gcc, but not a whole lot.

According to this page too, eepro100 is the right module:
http://www.linuxquestions.org/hcl/sh...cat/140/page/1

Now on this page:
http://www.scyld.com/eepro100.html

Quote:

You may install just one driver (see below), or install all updated drivers using either the netdriver.tgz file or the SRPM.

So I just want to update all drivers. But I can't find the netdriver.tgz file it talks about...

dombrowsky · 01-16-2006, 01:46 PM

If you can type 'gcc' or 'make' then you can do this. Setting up a network card is always the first thing I do on a new machine (which are usually 5 year old boxes someone gave to me). Rarely do the default modules do the trick for me (I don't use the user-friendly distros). I configure things like this:

1) use lspci(8) to find exactly what my card is and which bus its on.
2) find the linux driver, and compile using something like that makefile I posted
3) install the driver in /lib/modules/`uname -r`/net (or wherever your kernel modules go)
4) become root
5) run 'depmod -a'
6) run 'modprobe <modulename>' where <modulename> is the same as the *.o file you compiled minus the '.o', (for rtl8139.o, the module name is rtl8139).
7) look at the tail of dmesg to find out if the module installed correctly
7.a) if it didn't, then either your card is fried or the module is wrong or your system is cursed.
8) find whatever it is on your system which creates /etc/modules.conf. on Debian, is update-modules(8).
9) add an alias for eth0 (this might not be needed). Here's what it is on my system ->
$ cat /etc/modutils/net
alias eth0 rtl8139
options rtl8139 debug=6 full_duplex=1,0,1

piece..of...cake.

btw, I'm pretty sure 'eth0' is just a string. You could name your network interface 'alfonz0' if you wanted. But I've never tried that.

-dave

Zeno McDohl · 01-16-2006, 03:14 PM

I think the card is fried..?
http://www.gaiaonline.com/forum/view...php?t=11820385

maxfacta · 01-16-2006, 10:15 PM

If eepro100 loads into the kernel, then the driver believes there is hardware there to talk to. Forgive me for asking a potentially insulting question, but there is no onboard LAN (ie, another ethernet controller)? For if the driver loads, yet you do not even get a link light when plugging a live cable into your card, the card is likely broken.