can't get rtl8139 to work

pr0vidence · n00b Joined: 12 Apr 2002 Posts: 47 Location: Connecticut

I had a similar problem with my 8139.

when I booted off the gentoo CD and it probed my NIC it found (what seemed like) 2 cards (even though there was only one) an "8139too" and a "mii" first I tried to modprobe just "8139too" and that sort of worked, I was able to ping anything on the internet (by the way I have dhcp, so I just did a 'dhcpcd eth0' to get an IP), but as soon as I chroot-ed to the gentoo installation the nic was cut off and I could not access the internet.

Then I tried it again but this time modprobe-ed "mii" and that worked perfectly thoughout the entire installation process.

Try it with only "modprobe mii" and see if that works.

note that once I compiled the kernel and the installation was complete the module I use now when I boot my gentoo system is "8139too" NOT "mii"

DiskDoc · Posted: Fri Apr 26, 2002 9:02 pm Post subject: 8139too experience

I use a Reaktek 8139 card (and the 8139too driver) and had no problems during the initial install like the ones you describe. Everything worked sweetly..with DHCP anyway.

AutoBot · l33t Joined: 22 Apr 2002 Posts: 968 Location: Usually Out

Since your having that problem trevor, why don't you go ahead and just compile your NIC driver into the kernel instead of having it as a module. I have a feeling that might solve your problem, also don't forget if you do that to take out the 8139too from /etc/modules.autoload.
_________________
This message self destructed a long time ago.

fuji · Tux's lil' helper Joined: 26 Apr 2002 Posts: 111

I had no problems with the 8139too drivers as well. Here's some basic info in case you want to compare:

I compiled the driver into my kernel
I run kernel 2.4.18
I use a static ip while connecting through a router (linksys)

AutoBot may be correct with his suggestion to compile it into the kernel.

Hope it all works out for you.

taskara · Posted: Sun Apr 28, 2002 9:54 am Post subject:

what network do you run at home ?

is it 100 mb full duplex?

often the speed setting causes problems.

if you are running a 10 mbit half duplex network, then no way your card is going to work

niyogi · Posted: Sun Apr 28, 2002 8:32 pm Post subject:

1) ignore mii during installation.. but add it to modules.autoload BEFORE 8139too

2) change pci slots and see if that does anything (it can)

just do insmod 8139too as the first command when gentoo installation boots up

-S

Trevor_ · Guest

Sorry for the late reply - I was on a holiday

I tried compiling the driver into the kernel, but that doesn't help. I noticed some unusual output when I try to use the card (ping). Here are the lines from dmesg:

Guest · Posted: Tue May 07, 2002 3:07 pm Post subject:

I do not know how much this will help but I have that card running very well...

<y server (desktop is gentoo) is running slackware 8 with stock 2.4.18 kernel. I chose 8139too as module with no other "sub-options" enabled.The machine has 4 of those cards (and a NE2000 ISA).

3 of them are running at 10Mbit/hd and 4th one in 100Mbit/FD. (It you wonder, the machine is a bridge and a router w/ firewall)

I only had a problem once. The card was proben and was giving "strange" pci errors or invalid ids. I replaced it.

Again, I do not know how much this helps, but I can at least say that the card works perfectly on bare 2.4.18 kernel.