You are not logged in.

#1 2007-07-17 18:11:01

sfabius
Member
Registered: 2007-07-07
Posts: 153

network stopped working: nv_stop_tx error

I just installed arch on a newly-built machine with a asus m2n motherboard. This has an nvidia nforce mac.
I'm connecting with a static IP address. When I first connected, after loading the forcedeth module, all went well and I started upgrading the system. It stopped in mid-dowload, and I haven't been able to get it back. The one error clue I've been able to find is an error that says "nv_stop_tx: TransmitterStatus remained busy" in dmesg, and googling that didn't really give me much help. I've tried all sorts of network starting and stopping, but still nothing. I'd appreciate any help. Below I paste relevant data.

End of dmesg, convering two tries at manually installing the forcedeth module and starting the network:

Jul 18 14:33:49 trane nv_stop_tx: TransmitterStatus remained busy<7>Losing some ticks... checking if CPU frequency changed.
Jul 18 14:33:57 trane ACPI: PCI interrupt for device 0000:00:07.0 disabled
Jul 18 14:34:04 trane forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.59.
Jul 18 14:34:04 trane ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LMAC] -> GSI 23 (level, low) -> IRQ 23
Jul 18 14:34:04 trane forcedeth: using HIGHDMA
Jul 18 14:34:05 trane eth0: forcedeth.c: subsystem: 01043:8234 bound to 0000:00:07.0
Jul 18 14:34:12 trane eth0: no link during initialization.
Jul 18 14:34:52 trane eth0: link up.
Jul 18 14:35:05 trane nv_stop_tx: TransmitterStatus remained busy<6>ACPI: PCI interrupt for device 0000:00:07.0 disabled
Jul 18 14:35:08 trane forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.59.
Jul 18 14:35:08 trane ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LMAC] -> GSI 23 (level, low) -> IRQ 23
Jul 18 14:35:08 trane forcedeth: using HIGHDMA
Jul 18 14:35:09 trane eth0: forcedeth.c: subsystem: 01043:8234 bound to 0000:00:07.0
Jul 18 14:35:31 trane eth0: link down.

ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:1A:92:66:62:69  
          inet addr:136.142.130.89  Bcast:136.142.0.0  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:23 Base address:0xc000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2080 (2.0 Kb)  TX bytes:2080 (2.0 Kb)

Happy to post other info as needed.

Offline

#2 2007-07-18 16:48:14

sfabius
Member
Registered: 2007-07-07
Posts: 153

Re: network stopped working: nv_stop_tx error

Some updates:
1. I managed to upgrade everything by bringing the packages over manually. Still no network.
2. here's the lspci:

00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 8234
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0 (250ns min, 5000ns max)
        Interrupt: pin A routed to IRQ 23
        Region 0: Memory at ddefd000 (32-bit, non-prefetchable) [size=4K]
        Region 1: I/O ports at d480 [size=8]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3 Enable-
                Address: 0000000000000000  Data: 0000
                Masking: 00000000  Pending: 00000000
        Capabilities: [6c] HyperTransport: MSI Mapping

3. The machine I'm currently using to type this is connected using the same internet setup. Here is the ifconfig from the current machine:

eth0      Link encap:Ethernet  HWaddr 00:0D:60:D0:20:ED  
          inet addr:136.142.130.89  Bcast:136.142.255.255  Mask:255.255.0.0
          inet6 addr: fe80::20d:60ff:fed0:20ed/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7380740 errors:4294967242 dropped:4294967287 overruns:0 frame:4294967260
          TX packets:6377776 errors:57136 dropped:0 overruns:0 carrier:57127
          collisions:186355 txqueuelen:100 
          RX bytes:1827519853 (1742.8 Mb)  TX bytes:3243736442 (3093.4 Mb)
          Base address:0x8000 Memory:c0220000-c0240000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:21902 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21902 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:11551437 (11.0 Mb)  TX bytes:11551437 (11.0 Mb)

4. It looks like there is some info here, but I'd appreciate knowing what to do with the info (adding some code to forcedeth).

Offline

#3 2007-07-20 16:44:35

sfabius
Member
Registered: 2007-07-07
Posts: 153

Re: network stopped working: nv_stop_tx error

I gave up -- scrounged an old 3com network card and it works fine.

Offline

Board footer

Powered by FluxBB