1 |
waltdnes@××××××××.org wrote: |
2 |
> Approx a week ago, I got a new computer, AMD64 on a K8 Triton Gigabyte |
3 |
> Triton Nforce 4 motherboard. Today, ethernet stopped functioning. I |
4 |
> couldn't even get it to work with the Gentoo minimal install CD. It was |
5 |
> running OK the past week with... |
6 |
> "<*> Reverse Engineered nForce Ethernet support (EXPERIMENTAL)" built |
7 |
> into the kernel (would be forcedeth as a module). I looks like it has |
8 |
> died on me. My old backup machine, hooked up to the same 4-port |
9 |
> ADSL-modem/router connects to the net just fine. I swapped the ethernet |
10 |
> cables to check if it was a bad router port or cable. The old machine |
11 |
> works, the new one doesn't. "m3000" is the machine's hostname. The |
12 |
> following message shows up in my logs (and on tty12) when I try to |
13 |
> access a web site... |
14 |
> |
15 |
> NETDEV WATCHDOG: eth0: transmit timed out |
16 |
> Sep 4 11:47:31 m3000 nv_stop_tx: TransmitterStatus remained busy<7>eth0: tx_timeout: dead entries! |
17 |
hi, |
18 |
I've got an AMD64 assus nfore 4 mobo with on board eth, and I started to |
19 |
have the same problem some time ago. Was just wondering wether it is |
20 |
just a driver problem or should take it back to shop... |
21 |
The thing is, that when I power the computer off completely (take it off |
22 |
ac completely, so the motherboard gets shut down completely) and then |
23 |
boot it again, it seems to work again... I wasn't able to find any |
24 |
reason for it to fail, sometimes it failed 2-3 times a day, then it ran |
25 |
on for about a week... |
26 |
|
27 |
I'm running the same driver (forcedeth), logs show the same messages, |
28 |
nothing interesting before them... |
29 |
I've got win installed on the machine and even rebooting to them didn't |
30 |
help (tought, that the win driver could somehow reset the card back ;), |
31 |
only the hard power-down. I do not use the win instalation much (at |
32 |
least it is newer booted for longer than 2-3 hours...) so I can't say if |
33 |
it happens in win too... |
34 |
|
35 |
|
36 |
lspci -vv |
37 |
|
38 |
0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) |
39 |
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard |
40 |
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- |
41 |
ParErr- Stepping- SERR- FastB2B- |
42 |
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- |
43 |
<TAbort- <MAbort- >SERR- <PERR- |
44 |
Latency: 0 (250ns min, 5000ns max) |
45 |
Interrupt: pin A routed to IRQ 177 |
46 |
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=4K] |
47 |
Region 1: I/O ports at b000 [size=8] |
48 |
Capabilities: [44] Power Management version 2 |
49 |
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA |
50 |
PME(D0+,D1+,D2+,D3hot+,D3cold+) |
51 |
Status: D0 PME-Enable+ DSel=0 DScale=0 PME- |
52 |
|
53 |
|
54 |
|
55 |
yoyo |
56 |
|
57 |
> |
58 |
> lspci -vv shows the following... |
59 |
> |
60 |
> 0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a2) |
61 |
> Subsystem: Giga-byte Technology: Unknown device e000 |
62 |
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- |
63 |
> Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- |
64 |
> Latency: 0 (250ns min, 5000ns max) |
65 |
> Interrupt: pin A routed to IRQ 11 |
66 |
> Region 0: Memory at ea104000 (32-bit, non-prefetchable) [size=4K] |
67 |
> Region 1: I/O ports at e000 [size=8] |
68 |
> Capabilities: [44] Power Management version 2 |
69 |
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) |
70 |
> Status: D0 PME-Enable+ DSel=0 DScale=0 PME- |
71 |
> |
72 |
> |
73 |
> It's Sunday afternoon, and tomorrow's a holiday. Any last-minute ideas |
74 |
> or tweaks before I take it back to the shop on Tuesday? |
75 |
> |
76 |
|
77 |
|
78 |
-- |
79 |
gentoo-user@g.o mailing list |