| View previous topic :: View next topic |
| Author |
Message |
Peace Frog
Apprentice
Joined: 12 Dec 2006
Posts: 185
|
 Posted: Fri Dec 22, 2006 8:25 pm Post subject: Will it never end? System didn't recognize eth0 [SOLVED] |
 |
|
Alright, I selected the apropriate driver from the kernel config and I still can't get Eth0 to be recognized as even existing.
| Code: |
network interface eth0 does not exist
Please verify hardware or kernel module (driver)
ERROR: problem starting needed service net.eth0
netmount was not started
|
*sigh*
Is this something simple that I'm not getting because I'm not a gentoo guru? or is this something a lttle more serious?
-Thanks
Last edited by Peace Frog on Fri Dec 22, 2006 10:09 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W
|
| Posted: Fri Dec 22, 2006 8:35 pm Post subject: |
|
|
Peace Frog,
Its probably something simple like not loading the driver after having made it a module, or having several ethernet intefaces but the names have swapped since you made your own kernel
Post the ethernet line(s) from lspci please, or try this guide
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Fri Dec 22, 2006 8:38 pm Post subject: |
|
|
If you've got the driver as a module, you can runto see all the ethernet interfaces, even the inactive ones. You can then runwhere <driver> is the module for your ethernet controller, and then runagain to see what's popped up.
It can happen that eth0 is linked to another interface by the kernel/udev and that the one you want is eth1.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
Peace Frog
Apprentice
Joined: 12 Dec 2006
Posts: 185
|
| Posted: Fri Dec 22, 2006 8:51 pm Post subject: |
|
|
Alright, I'm thuroughly convinced I did something seriously wrong at some point in time. There are no modules loaded on boot, modprobe can't find the network module (8139too)... Where did I go wrong?
-Thanks |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W
|
| Posted: Fri Dec 22, 2006 8:59 pm Post subject: |
|
|
Peace Frog,
What does | Code: | | grep 8139 /usr/src/linux/.config |
tell you?
CONFIG_8139TOO=m or
CONFIG_8139TOO=y are both good, if you really have a Realtek 8139 or clone
#CONFIG_8139TOO is not set means the module is not made. Thats no hardship, the fix will take about five minutes.
Post back before you go rebuilding your kernel
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Peace Frog
Apprentice
Joined: 12 Dec 2006
Posts: 185
|
| Posted: Fri Dec 22, 2006 9:03 pm Post subject: |
|
|
Both 8139CP and TOO are not set. I'm not entirely sure how to recompile the kernel on my own, I can do a fresh install and recompile, and that doesn't take too much longer than downloading and emerging the tarball and portage files. I can also go back and boot from the live CD, mount my filesystem by hand and go in to a chroot environment, but from there I only have the vaguest idea of how to recompilI know wynn explaine dit once, but I'm not sure it realy sunk in. :~/
EDIT: alright, I can try the recompile on my own, but what can I di diferriently this time?
-Thanks |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W
|
| Posted: Fri Dec 22, 2006 9:57 pm Post subject: |
|
|
Peace Frog,
Do the following, we will add a module to your existing kernel, not recompile it all.
| Code: | cd /usr/src/linux
make menuconfig
/ fill in 8139too |
Navigate to the location the serch has shown you and change the
| Code: | < > Realtek 8139
<M> Realtek 8139 |
That tells the kernel makefile we want it as a module
Exit make menuconfig and save the change.
Continue with
| Code: | make modules
make modules_install |
which makes the new module(s) and puts in the the proper place
Test with | Code: | modprobe 8139too
ifconfig -a |
You should have an eth0 now.
Start it with | Code: | | /etc/init.d/net.eth0 start |
IF you are a dhcp user, it should just work.
No reboot required.
Now to automate it on startup. Add 8139too to a new line in | Code: | | /etc/modules.autoload.d/kernel-2.6 |
That file exists and has a sample commented out entry.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Peace Frog
Apprentice
Joined: 12 Dec 2006
Posts: 185
|
| Posted: Fri Dec 22, 2006 10:08 pm Post subject: |
|
|
W00TEH!  It worketh!!
Gorgeous, now I just have to finish aditing the kernel with the REST of my hardware... Thanks to both Ned and wynn.
-Peace Out |
|
| Back to top |
|
|
|
Installing Gentoo
