Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3124 - ethernet

Attached to Project: Arch Linux
Opened by Claudio Riva (Firetux) - Monday, 29 August 2005, 08:42 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I'm not able to connect to my router ADSL using ethernet card of my portable pc. If I run "dhcpcd eth0" after a couple a minutes it hungs and if I watch dmesg I got this:

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008a05a. (queue head)
eth0: Tx descriptor 1 is 0008a24e.
eth0: Tx descriptor 2 is 0008a04e.
eth0: Tx descriptor 3 is 0008a046.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0000 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008a24e. (queue head)
eth0: Tx descriptor 1 is 0008a046.
eth0: Tx descriptor 2 is 0008a046.
eth0: Tx descriptor 3 is 0008a24e.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

...if I try to set eth0 manually:
ifconfig eth0 192.168.1.2 up
route add default gw 192.168.1.1
and I ping my router or other pc on my LAN I got "Host unrecheable"

The same configuration works well on the other computer. What's the problem?
This task depends upon

Closed by  Tobias Kieslich (tobias)
Sunday, 02 October 2005, 13:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  opener reported that works with new kernel
Comment by Jan de Groot (JGC) - Monday, 29 August 2005, 11:36 GMT
I think your network card is broken somehow. What card is it and what kernel are you using?
Comment by Claudio Riva (Firetux) - Monday, 29 August 2005, 12:00 GMT
The network card works with Windows. So I thinks is not an hardware problem.
lshwd:
02:01.0 Ethernet controller: Realtek|RTL-8139 (8139too)

hwd -s:
Ethernet : Realtek|RTL-8139 module: 8139too device: eth0

lspci:
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)

do you need more information?
Comment by Claudio Riva (Firetux) - Monday, 29 August 2005, 12:03 GMT
I forgot to say that I'm using kernel 2.6.12.2-1
Comment by Jan de Groot (JGC) - Monday, 29 August 2005, 13:18 GMT
What driver is loaded for this card? 2 drivers exist: 8139too and 8139cp. One of them should work, but as usual with bad cards with bad device descriptions, the wrong one gets loaded all the time...
Comment by Claudio Riva (Firetux) - Monday, 29 August 2005, 13:48 GMT
8139too is loaded, I try with 8139cp but I got the same results
Comment by Claudio Riva (Firetux) - Thursday, 01 September 2005, 09:39 GMT
I made a new installation via ethernet. I loaded 8139too as module, I configured network using DHCO, and during the installation the network card works very well.
When the installation ended I rebooted...but when I login into the system eth0 doesn't work :(
Comment by Claudio Riva (Firetux) - Thursday, 01 September 2005, 20:12 GMT
I made another installation but now via CD (0.7) after reboot the card works well. So I upgrade only pacman and kernel to the version 2.6.12.2 and after reboot the card stop to works! The problem is in the kernel
Comment by Claudio Riva (Firetux) - Thursday, 01 September 2005, 20:38 GMT
I try to use kernel in the testing tree (2.6.13-2) and the card works.
The problem was the kernel. I think that this bug can be closed. Thank you Jan ;)

Loading...