View previous topic :: View next topic |
Author |
Message |
BenTheMeek n00b
Joined: 02 Feb 2006 Posts: 3
|
Posted: Thu Feb 02, 2006 5:54 am Post subject: [solved] Custom Kernel Compile No eth0 |
|
|
I did read https://forums.gentoo.org/viewtopic-p-2990710.html#2990710 (rough guide to fix networking before making this post).
Perhaps My understanding of how linux and drivers work is off and maybe someone here can set me straight. I have custom compiled my kernel with what I beleive is the correct driver added in. However after a reboot Ifconfig eth0 reveals none installed. I tried recompiling the kernel again to no avail ether. I gave up and then decided to attempt to load the module i want (which incidently is e1000 on the LiveCD). No modules called e1000 existed on my hardisk installation. So i emerged e1000 once i was back in the live cd and chrooted and rebooted again. Still no e1000.o or e1000.ko just e1000.c and .h. so modprobe is confused and can find nothing.
I am working off a stage 3 tarball and using the latest live cd. The live cd network detection of course works fine. At this point im a little frustrated so to make a long story short here are my questions:
1.) It is possible to install network drivers etc. as part of the kernel right? When I reboot is that all there is to it for it to see a eth0 when i type ifconfig if my kernel compiled right with the network driver?
2.) Where are all the modules? Is it because I'm not using genkernel that i dont have see any and emerge doesnt seem to put them on the system?
Any insight you have I would br greatful for. Thanks,
Ben
Last edited by BenTheMeek on Fri Feb 03, 2006 4:01 am; edited 1 time in total |
|
Back to top |
|
|
brims Guru
Joined: 19 Apr 2004 Posts: 492 Location: Arizona
|
Posted: Thu Feb 02, 2006 6:41 am Post subject: |
|
|
1) Yes it is possible. If you tell us what card/onboard NIC you have, we can give you hints as to what you need to enable in the kernel, if you don't already have the needed item/items enabled.
Did you build the driver into the kernel <*> or as a module <M>?
2) Modules are in /lib/modules/<kernel version>/
If you have the drivers compiled into the kernel, or as a module, from the kernel config, you shouldn't have to emerge the drivers from Portage. I am not familiar with the e1000 drivers, or supported cards, I can't be sure. _________________ Adopt an Unanswered Post
Report violations, duplicates, misplaced, etc |
|
Back to top |
|
|
BenTheMeek n00b
Joined: 02 Feb 2006 Posts: 3
|
Posted: Thu Feb 02, 2006 3:38 pm Post subject: |
|
|
I installed it as a <*> at least for the second time around (Im nto sure what i did the first kernel compile.)
The Nic is a onboard intel gigabit adapter I will try to get more information about it but I am not at home at the moment. So in the case where the kernel is compiled with the correct options; upon reboot to the HD eth0 will just show up when an ifconfig is ran, correct? Then at least I know I must not be choosing the correct driver or package or something...
About the second answer, I'm curious as to why it did what it did. When I emerged e1000 it created a folder called e1000 with a Makefile and e1000.c and e1000.h but no module (as i beleive they have a different file extension .o or .ko) Was I supposed to compile the module from those files or something through a make process? Is that normally how adding additional modules works? |
|
Back to top |
|
|
nixnut Bodhisattva
Joined: 09 Apr 2004 Posts: 10974 Location: the dutch mountains
|
Posted: Thu Feb 02, 2006 4:58 pm Post subject: |
|
|
Moved from Installing Gentoo to Networking & Security.
postinstallation network problem. _________________ Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
Back to top |
|
|
Kenji Miyamoto Veteran
Joined: 28 May 2005 Posts: 1452 Location: Looking over your shoulder.
|
Posted: Thu Feb 02, 2006 5:31 pm Post subject: |
|
|
BenTheMeek wrote: | I installed it as a <*> at least for the second time around (Im nto sure what i did the first kernel compile.)
The Nic is a onboard intel gigabit adapter I will try to get more information about it but I am not at home at the moment. So in the case where the kernel is compiled with the correct options; upon reboot to the HD eth0 will just show up when an ifconfig is ran, correct? Then at least I know I must not be choosing the correct driver or package or something...
About the second answer, I'm curious as to why it did what it did. When I emerged e1000 it created a folder called e1000 with a Makefile and e1000.c and e1000.h but no module (as i beleive they have a different file extension .o or .ko) Was I supposed to compile the module from those files or something through a make process? Is that normally how adding additional modules works? | Try building both the e1000 and the sk89lin as modules: <M>. Then, add one (base namd minus ".ko") to your /etc/modules.autoload.d/kernel-2.6. If the first one doesn't work, try the second. |
|
Back to top |
|
|
BenTheMeek n00b
Joined: 02 Feb 2006 Posts: 3
|
Posted: Fri Feb 03, 2006 4:02 am Post subject: |
|
|
a third compile of the kernel reveals i must of gotten the right module included this time. i just checked all the intels and the one you mentioned. Thanks |
|
Back to top |
|
|
|