| View previous topic :: View next topic |
| Author |
Message |
Grik
Tux's lil' helper
Joined: 30 Sep 2004
Posts: 88
Location: Netherlands
|
 Posted: Fri Feb 11, 2005 8:18 pm Post subject: When autoloading module, eth0 doesn't work |
 |
|
(I figured this post best fitted in this forum, if not: sorry, and please move it.)
I am running the same Gentoo installation for a few months now. I started with Genkernel, just to try which hardware could be used. After the genkernel setup I compiled my own kernel.
If you use genkernel, you need hotplug. So I installed that. After compiling the new kernel I never removed it. But now hotplug was bothering me at getting my tvtuner working.
So I disabled hotplug. I noticed that hotplug took care of loading the right modules for my eth0 (module forcedeth). So after disabling hotplug and rebooting, I need to load the module automatically, and activate eth0. This is how I do that:
| Code: | | root@riksbox rik # modprobe forcedeth |
after that ifconfig automagically activates eth0 
But as you propably will understand, I don't want to activate the module forcedeth every day. So I wrote "forcedeth" in /etc/modules.autoload.d/kernel-2.6.
When I reboot, according to lsmod, the module is loaded. But eth0 doesn't work. So I do a "ifconfig eth0 down" and a "ifconfig eth0 up" which results in nothing. So I do a "modprobe -r forcedeth" and a "modprobe forcedeth" and eth0 works!
So... long story short: When I autoload the forcedeth module, it doesn't work. When I manually load it, everything works.
How can I solve this problem? |
|
| Back to top |
|
 |
ikaro
Advocate
Joined: 14 Jul 2003
Posts: 2527
Location: Denmark
|
| Posted: Fri Feb 11, 2005 8:49 pm Post subject: |
|
|
if you dont want to load/unload the network device driver, why dont you just simply ... really .. compile the driver in the kernel _not_ as a module ??
_________________
linux: #232767 |
|
| Back to top |
|
|
Grik
Tux's lil' helper
Joined: 30 Sep 2004
Posts: 88
Location: Netherlands
|
| Posted: Fri Feb 11, 2005 8:54 pm Post subject: |
|
|
| ikaro wrote: | if you dont want to load/unload the network device driver, why dont you just simply ... really .. compile the driver in the kernel _not_ as a module ??
|
Because menuconfig dissuades you to compile forcedeth into the kernel  |
|
| Back to top |
|
|
Grik
Tux's lil' helper
Joined: 30 Sep 2004
Posts: 88
Location: Netherlands
|
| Posted: Fri Feb 11, 2005 9:41 pm Post subject: |
|
|
| Well, I did it anyway and now it works. But I still wonder why it doesn't work if I autoload the module |
|
| Back to top |
|
|
|
Kernel & Hardware
