"Best" way to get 8139too Driver working under ker

[kd4d]

Hello, all:

I just installed gentoo, using genkernel and development sources.

As soon as I rebooted, the network connection quit working.

I can get the network back up by typing the following as root:
# modprobe 8139too
# ifconfig eth0 up
# dhcpcd eth0

I have read everything I can find on this issue in the gentoo forums.
Suggested "fixes" include, but aren't limited to:

Adding 8139too to /etc/modules.autoload.d/kernel-2.6
Adding alias eth0 8139too to /etc/modules.conf
Adding 8139cp to hotprobe/blacklist
Enabling Kernel Options "Support for uncommon RTL-8139 rev. k"
and "Support for older RTL-8129/8130 boards"
Try gentoo-sources-2.4.22-r5 (I don't know how to do this?!)

and others. I have some Unix experience, but am new to Linux.

I'm leaning towards trying the /etc/modules.autoload.d approach
for starters.

However, given my poor understanding of how genkernel and
hotprobe work together, I think the real issue may be addressed
by the hotprobe/blacklist!

Comments? Help!!!

Mark

[sieter]

Do you have net.eth0 in your default runlevel?

[kd4d]

Hi:

Yes, I've done the rc-update several times. ifconfig
only shows the loopback device until I do the
modprobe.

/etc/conf.d/net is trivial, since I'm using dhcp.

I believe the problem is that the automatic hardware
detection (either boot time or that was used in genkernel)
isn't finding the 8139 and loading the appropriate driver.

I've checked these settings many times.

Thanks! Quick response.

Mark

[Peracles]