Steven G Wagner wrote:
I have a working hardened system, 2.6.16-hardened-r11, but I can't seem to
get eth0 recognized. My NIC is a Netgear FA310TX Rev D2 and I found that it
uses the "Tulip" driver.
I've tried compiling this driver by itself into the kernel both built-in and
as a module. I've tried compiling the entire "Tulip" family of drivers into
my kernel, trying <*> next to every possible selection under "Tulip" and
again using <m> in every instance allowed. I listed "tulip" in
/etc/modules.autoload.d and it failed at boot, even though it was compiled
as a module.
Everything is copasetic when I boot off the livecd and I can ping google,
etc. I tried emerging hotplug as one forum post I found indicated, but to no
avail. I've done my best to find posts related to this, seemingly, common
issue, but nothing has worked for me and I can't think of anything else to
try. I've combed the handbook as well, but nothing there has helped me.
If anyone could help me I would really appreciate it. I have used Hardened
Gentoo before, but not on this older machine.
Thanks a lot for any help,
Steve
Hi,
I'm using the Tulip driver on one of my older boxes too. Under the
"Tulip family" selection in menuconfig, only one of them actually
compiles the tulip.o module - I forget the name of it (DEC something),
but last time I built a kernel it was second in the list. For it to
work properly, I had to enable all the options for the tulip module -
new bus layout, interrupt mitigation, whatever other fancy things it has
there. Are you sure it's the tulip.o driver you want, or is it some
other driver from the tulip family?
You said that autoloading failed - can you paste the *exact* error
message? What happens if you try 'modprobe tulip' by hand, as root?
Ryan
--
gentoo-user@gentoo.org mailing list
