<sigh>
Yea gods, not another one.
How on this earth can you expect people to help you if you do not provide
information. We have no idea what machine you have, what network card, what
errors are taking place, what modules, what kernel or anything else that's
important to help you, because you did not say.
My initial opinion as to why your network does not work is that your card is
physically fucked.
Feel free to disagree and prove me wrong by means of:
- relevant dmesg output
- relevant /var/log/messages output
- relevant lspci output
- relevant lsmod output
- relevant uname -a output
- relevant kernel configuration output
- relevant verbose output on the shell when starting the interface
- anything else relevant
--
alan dot mckinnon at gmail dot com
We will never know if you don't give some detail about your hardware,
kernel configuration, etc.
At the bare minimum, the output of lspci -vv relevant to your network card.
In the meantime, read this:
http://catb.org/~esr/faqs/smart-questions.html
Hope it helps!
m.
My cristal ball isn't on-line now.
Please feed us with more *usable* information guy.
Thanks.
hint: You're compiled your kernel with support to your ethernet card?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktF4y0ACgkQ35zeJy7JhCgCEACdGFnib/eUcES8+1yVB5Q7dv6k
U9cAn00GVUaD4EwHb+LTJwjmhha6Z5q1
=zdyV
-----END PGP SIGNATURE-----
You might also want to add /etc/conf.d/net to the list of things to look
through.
OT: I had the same reaction Alan, i had just finished reading the other
one who provided no information. It really is dumbfounding.
--
Zeerak