8139cp: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.24
PCI: Found IRQ 10 for device 00:0e.0
eth0: RealTek RTL8139 Fast Ethernet at 0xcc81a000, 00:e0:7d:91:86:e7, IRQ 10
eth0: Identified 8139 chip type 'RTL-8139C'
I verified on my ethernet board and it says 8139C
which one its on use? 8139cp and 8139too module? Where can I setup them?
----- Original Message -----
From: "Johan Ehnberg" <johan@ehnberg.net>
To: "specz" <specz@terra.com.br>; <debian-user@lists.debian.org>
Sent: Monday, August 26, 2002 10:54 AM
Subject: Re: internet access using DHCP works only on windows
specz wrote:
actually, this modem works as a hub too, so anyone who plugs in one of
its 4
ports can surf the internet, you only have to set it up as a dhcp
client. I
don't have to set any server to do NAT stuff, the modem does it for us.
OK. So it should work on linux as long as your modem's connection
sharing is transparent to all workstations.
What aditional parameters for example? On module load?
Look at /proc/pci by issuing 'cat /proc/pci'. Can you find an entry of
your network card? Also try 'lspci', it will give you a shorter list.
Your network catd should have an IRQ if it is working. When you load the
module you can specify the IRQ, but for PCI systems with only one card
it is seldom necessary. 'insmod -v [module name]' might give you useful
information. Also look at your dmesg ('dmesg') and look for any messages
by the module. If you compiled it into the kernel, look in the middle
somewhere. If it's a module, look at the end. With modules it's easier
way to find the problem, btw. Use 'modinfo [module name] to see what you
can tweak. Did you try both 8139cp and 8139too modules? Only one of them
will work.
Good luck!
--
Johan Ehnberg
johan@ehnberg.net
"Windows? No... I don't think so."
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org