| View previous topic :: View next topic |
| Author |
Message |
Forse
Apprentice
Joined: 26 Dec 2002
Posts: 260
Location: /dev/random
|
 Posted: Mon May 26, 2003 6:53 pm Post subject: |
 |
|
ok...something must be wrong with eth0, coz I get all *the time this error*:
| Code: | NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1. |
I am now compiling drivers for NIC's in modules 
_________________
[ My sites ]: UnixTutorials : AniFIND : AnimeYume |
|
| Back to top |
|
 |
Forse
Apprentice
Joined: 26 Dec 2002
Posts: 260
Location: /dev/random
|
| Posted: Mon May 26, 2003 8:26 pm Post subject: |
|
|
Now I finally know where is the problem. My netwotk card "VIA Technologies, Inc. VT86C100A [Rhine] (rev 06)" doesn't work correctly. I recompiled kernel with this options:
| Code: | <M> VIA Rhine support
[*] Use MMIO instead of PIO (EXPERIMENTAL) |
I also tried without "[*] Use MMIO instead of PIO (EXPERIMENTAL)"...Funny thing is that card works but I get:
| Code: | NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: Setting full-duplex based on MII #8 link partner capability of 41e1. |
And card performance is soooo....poor...Only 200kb/s and it's 10/100 card, that's why my samba is sooo slow
Any ideas? plz I am going mad....and I mean mad  Thnx in advance
BTW here is lsmod:
| Code: | Module Size Used by Not tainted
via-rhine 13680 1
8139too 14952 1
mii 2560 0 [via-rhine 8139too]
i2c-piix4 4204 0 (unused)
dmi_scan 1572 0 [i2c-piix4]
ipt_state 536 17 (autoclean)
ipt_LOG 3352 1 (autoclean)
iptable_filter 1708 1 (autoclean)
iptable_nat 17272 1
eeprom 3636 0 (unused)
w83781d 20464 0 (unused)
i2c-isa 1128 0 (unused)
i2c-proc 6992 0 [eeprom w83781d]
i2c-core 16072 0 [i2c-piix4 eeprom w83781d i2c-isa i2c-proc]
usbcore 61760 1 |
_________________
[ My sites ]: UnixTutorials : AniFIND : AnimeYume |
|
| Back to top |
|
|
ARC2300
Apprentice
Joined: 30 Mar 2003
Posts: 267
|
| Posted: Mon May 26, 2003 10:57 pm Post subject: |
|
|
Okay, so now we have it down to a driver problem. WOOHOO!!
Uh, what motherboard do you have?? There might have been a change in the VIA driver between 2.4.19 and 2.4.20.
Have you checked to see if it is a VIA NIC, or maybe someone else made the chip?? I've never worked with onboard NIC cards, so I could be wrong.
And I don't know, but what is the mii module??? That seems to be thoroughly pissed off. |
|
| Back to top |
|
|
Forse
Apprentice
Joined: 26 Dec 2002
Posts: 260
Location: /dev/random
|
| Posted: Tue May 27, 2003 7:30 am Post subject: |
|
|
| ARC2300 wrote: | Okay, so now we have it down to a driver problem. WOOHOO!!
Uh, what motherboard do you have?? There might have been a change in the VIA driver between 2.4.19 and 2.4.20.
Have you checked to see if it is a VIA NIC, or maybe someone else made the chip?? I've never worked with onboard NIC cards, so I could be wrong.
And I don't know, but what is the mii module??? That seems to be thoroughly pissed off. |
I got enough of this....I went to store and got new NIC realtek based. Now everything is fine Thnx a lot for help ARC2300 
_________________
[ My sites ]: UnixTutorials : AniFIND : AnimeYume |
|
| Back to top |
|
|
Reformist
Guru
Joined: 06 Oct 2002
Posts: 323
|
| Posted: Sat Oct 04, 2003 9:09 pm Post subject: |
|
|
This is unacceptable. There is a wisespread issue with with the VIA Rhine drivers in the kernel. I have 3 VIA Rhine cards myself, they are often included as the onboard cards for laptops and desktops. It's not practical to ignore that chipset and move on to another one... it's everywhere.
I get 5MB transfer speeds to a machine with a rhine card, and about 5000 B/s (5K) a second from it... this is with samba and ssh (scp).
I haven't found a solution yet.
_________________
-Phil Crosby |
|
| Back to top |
|
|
JjcampNR
Tux's lil' helper
Joined: 02 Mar 2003
Posts: 127
Location: Massachusetts, USA
|
| Posted: Thu Oct 16, 2003 5:43 am Post subject: |
|
|
Well, the first thing I would do is search bugs.gentoo.org and if nothing matches your problem, file a new bug report. The only way things are going to get fixed is if people report problems so that developers and others know about them.
Josh
_________________
Damn the man, fight the power!
http://www.torquenetworks.com |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
