On Saturday 26 March 2005 09:25 pm, Kathy Wills wrote:
> I've tried everything I can find by googling. Tried the forums. Can't
> find anything that solves the issue. I have noapic as a kernel parameter
> in grub. I still get this error in dmesg:
>
> tulip0: MII transceiver #1 config 1000 status 786d advertising 01e1.
> eth0: ADMtek Comet rev 17 at d12c8000, 00:03:6D:1D:89:41, IRQ 9.
> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
> 0000:02:0d.0: tulip_stop_rxtx() failed
> eth0: Setting half-duplex based on MII#1 link partner capability of 0021.
>
> Here is the relevant result of lspci-vv:
>
> 0000:02:0d.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
> Ethernet 10/100 (rev 11)
> Subsystem: Linksys: Unknown device 0570
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (63750ns min, 63750ns max), cache line size 08
> Interrupt: pin A routed to IRQ 9
> Region 0: I/O ports at d000
> Region 1: Memory at ed800000 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [c0] 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-
>
> Here is the result of mii-diag:
>
> Using the default interface 'eth0'.
> Basic registers of MII PHY #1: 1000 786d 0022 5410 01e1 0021 0004 2001.
> Basic mode control register 0x1000: Auto-negotiation enabled.
> You have link beat, and everything is working OK.
> Your link partner is generating 10baseT link beat (no autonegotiation).
> End of basic transceiver information.
>
> Does anyone have anymore ideas on what to try to get rid of the
> tulip_stop_rxtx() failed problem? The patches I found by googling this
> error didn't work.
What kernel version are you running? Tulip reports version 1.1.13 with this
kernel, 2.6.11. I've run my linksys cards with most 2.2.x and all 2.4.x an
2.6.x version kernels and never saw your reported error message. The config
file in 2.6.11 has a couple of configure options that may be of help to you.
Cheers....
dmesg
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0: MII transceiver #1 config 3000 status 786d advertising 01e1.
eth0: ADMtek Comet rev 17 at f0812c00, 00:03:6D:1C:70:0E, IRQ 10.
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
lspci
spinner ~ # lspci -vv
0000:00:0a.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
Ethernet 10/100 (rev 11)
Subsystem: Linksys: Unknown device 0574
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min, 63750ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at e400 [size=dffc0000]
Region 1: Memory at dffffc00 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at 00020000 [disabled]
Capabilities: [c0] 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-
mii-diag
spinner ~ # mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 1000 786d 0022 5410 01e1 45e1 0005 2801.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x1000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT, w/ 802.3X flow control.
End of basic transceiver information.
--
******************************************************************************
Registered Linux User Number 185956
FSF Associate Member number 2340 since 05/20/2004
Join me in chat at #linux-users on irc.freenode.net
Buy an Xbox for $149.00, run linux on it and Microsoft loses $150.00!
11:16pm up 168 days, 7:02, 8 users, load average: 0.10, 0.13, 0.09
--
[email protected] mailing list
