Re: PCI ethernet card from ebay doesn't work at all. Some progress...
--- On Mon, 12/1/08, A. F. Cano <afc@shibaya.lonestar.org> wrote:
> From: A. F. Cano <afc@shibaya.lonestar.org>
> Subject: Re: PCI ethernet card from ebay doesn't work at all. Some progress...
> To: debian-user@lists.debian.org
> Date: Monday, December 1, 2008, 2:22 AM
> First, thanks to all that have replied to my orignial query.
> I have
> made some progress, but I still can't even ping.
>
> On Sun, Nov 30, 2008 at 05:00:51AM -0800, Angus Auld wrote:
> >
> > ...
> > I have a cardbus adapter called "Zonet ZEN 1201
> >10/100 Mbps Fast Ethernet 32-bit", which is actually a
> >Realtek RTL-8139/8139C/8139C+. It was very inexpensive, but
> >it works extremely well for me in my Dell Inspiron 1150
> >using Lenny.
> > It is identified thusly by lshw:
> > *-network
> >...
> > logical name: eth0
>
> This is interesting. On my machine it is eth4, I have no
> idea why.
> So, when I modified /etc/network/interfaces and replaced
> eth0 with eth4,
> ifup eth4 now works. This is the only ethernet card in the
> machine.
>
> >...
> > And lspci -v shows this about it:
> > 03:00.0 Ethernet controller: Realtek Semiconductor
> Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
> >...
> > Kernel driver in use: 8139too
> > Kernel modules: 8139cp, 8139too
>
> This I'm not getting. I suppose the Etch version of
> lspci doesn't
> show this.
>
> I have tested loading 8139too by itself and both 8139cp and
> 8139too.
> No errors but ping fails with "Destination Host
> Unreachable" in both
> cases. Interestingly, the LED at the back of the card
> flashes and
> the LED at the network hub flashes, both when initiating
> the ping
> locally or remotely.
>
> So it looks like the proper driver for this card is
> 8139too, but
> something is not quite right (tested on kernels 2.6.18,
> 2.6.24 and
> 2.6.26, all locally compiled)
>
> > I have had no problems whatsoever with this card on
> >several different Linux distributions.
>
> > I am more than willing to post any of my configs that
> >could be of help.
>
> Any other hint as to why ping (or any other data transfer)
> doesn't work
> would be welcome.
>
> Thanks!
>
> A.
>
Networking has always proved sort of a "mystery" to me, and I have had my share of difficulties in the past. My worst difficulty was traced to the on-board nic in this machine, a Broadcom based interface, which would work intermittently, causing lots of grief. I believe it may be due to a cold or broken solder joint on the board. I considered trying to fix it, but rather than dismantling and risk damaging something, I simply disabled the on-board nic and went with the cardbus adapter.
This card has just worked for me, right out of the box. It got set up "magically" by Debian during install, and has been working seemlessly since.
I have been using Debian for several months or so, and I must say that I am very impressed.
This list has a broad base of very knowledgeable users, (I'm not one of them though), so I am sure someone here can likely help you sort this out.
My /etc/network/interfaces loks like this:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
Regards.
--
Angus
"All churches, whether Jewish, Christian, or Muslim, appear
to me no other than human inventions, setup to terrify and
enslave mankind - and to monopolize power and profit."
--
Thomas Paine (1737-1809)
######Laptop powered by Linux######
######Reg. Linux User #278931######
Reply to: