Setting up network?
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:
|
To determine your equipment
Code:
lspci -v |
This is what it says:
Code:
00:10.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 05) No idea where to go from here. I tried following that guide somewhat (using eepro100), but have failed to get online. |
Hello,
Sorry I didnt read through the thread you linked but have you got the module you need for your card loaded? Quote:
If it does show up as loaded then run through netconfig again. Or maybe just ifconfig eth0 up. |
Yes, it shows up in lsmod, like this:
Code:
eepro100 18836 1 If I type: Code:
/etc/rc.d/rc.netdevice Code:
modprobe: Can't locate module eepro100.o |
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? |
Here's netstat -r:
Code:
Destination Gateway Genmask Flags MSS Window irtt Iface Code:
lo Link encap:Local Loopback 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. |
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. |
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:
Thanks though. |
Maybe it is the wrong module?
When a live cable is connected to the computer, no lights turn on... |
sounds like a driver error to me
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 -dave |
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:
|
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 |
I think the card is fried..?
http://www.gaiaonline.com/forum/view...php?t=11820385 |
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.
|
All times are GMT -5. The time now is 10:23 PM. |