It turns out that I had two problems that I have reduced to one.
Simon Geard wrote:
I also have an nForce2 board using that driver for the onboard
controller, but in my case hotplug correctly identifies and loads the
forcedeth driver on bootup.
Since that's apparently not happening in your case, it might be a place
to start - find out why it isn't automatically loading the driver...
Andrew Benton wrote:
Have you tried building the driver into the kernel, not as a module?
While I was recompiling the kernel to see if the driver would run
compiled in, I found (errr--reread <BG>) in the LFS-6.0 book that
modules to be loaded on boot are listed in /etc/sysconfig/modules. Not
only did the driver work as part of the kernel, but now it loads on boot.
I still cannot connect to my DSL. I will, for clarity, reproduce my
/etc/sysconfig/network-devices/ifconfig.eth0/ipv4 file:
ONBOOT=yes
SERVICE=ipv4-static
IP=<static addr given to me by ISP>
GATEWAY=<another static addr given to me by ISP>
PREFIX=32
BROADCAST=<yet another static addr given to me by ISP>
All addr's are in the form xxx.xxx.xxx.xxx, ergo PREFIX=32.
Here's the problem. If I don't comment out the GATEWAY line, I get the
RTNETLINK errors. (The error sequence starts with "Removing default
gateway" or something like that.) If I comment the line, the networking
starts with no errors, but I cannot connect.
My research indicates that there may be something wrong (or not present)
in the IP Route Table. I found an interesting entry in the Mandrake
side of my box when I ran 'routel.' I'm going to try to manually change
that in BLFS, but right now I'm wondering if I haven't missed changing
some script or file in BLFS. Does any one have any ideas? It's
possible that I forgot to compile something into the kernel.
Thanks,
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
