b1cq7

Group: Members
Posts: 2
Joined: Feb. 2006 |
 |
Posted: Feb. 12 2006,00:06 |
 |
I have a PC with a nforce2 based motherboard. After booting DSL 2.2 I note the my network is not activated. After doing a lsmod I noticed that forcedeth was not loaded. When using other versions of Linux (i.e. MEPIS 3.3.1 which is based upon kernel 2.4.29) I have the same issue. However if I issue the command "insmod forcedeth" the module loads fine and my eth0 port is then active. When attempting this same command with DSL 2.2 I receive the following error:
"using /lib/modukes/2.4.26/kernel/drivers/net/forcedeth.o /lib/modules/2.4.6/kernel/drivers/net/forcedeth.o:init_module: no such device"
Is this kernel difference issue between MEPIS 3.3.1(kernel 2.4.29) vs DSL 2.2 (kernal 2.4.26)?
Thanks for any assistance offered
|