[SOLVED] Centos 5.5, Marvell 88E8057, Shuttle SA76G2(V2!), 10/100 only, no Gigabit

wpns · 01-09-2011, 11:04 AM

I've got a Shuttle barebones SA76G2 V2 box, with a Marvell 88E8057 Ethernet interface, and I'm trying to install Centos 5.5 on it.

[Note that this is not the Shuttle SA76G2 V1 box, but a new hardware spin, V2]

[Note this is not the Marvell 88E8056, which is known to have (had?) problems with the sky driver]

The box only connects to the Ethernet if plugged into a 10/100 port, if allowed to autonegotiate to gigabit, it thinks the cable is disconnected.

I get the same results with the default sky driver (V1.22) and the latest marvel driver (from http://extranet.marvell.com/drivers/...85.9.3.tar.bz2).

Any ideas for additional troubleshooting or information I can gather?

Many Thanks in advance!

On the V2 box that doesn't work in gigabit mode:
lspci -vvxx
/*
03:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4380 (rev 10)
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Unknown device 5113
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, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 50
Region 0: Memory at feafc000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at d800 [size=256]
Expansion ROM at feac0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable+
Address: 00000000fee03000 Data: 4032
Capabilities: [c0] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s unlimited, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1
Link: Latency L0s <1us, L1 <32us
Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
00: ab 11 80 43 07 05 10 00 10 00 00 02 10 00 00 00
10: 04 c0 af fe 00 00 00 00 01 d8 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 97 12 13 51
30: 00 00 ac fe 48 00 00 00 00 00 00 00 0a 01 00 00
*/

On the (V1) box that does work in Gigabit mode:
/*
02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4380 (rev 10)
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Unknown device 5113
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, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 169
Region 0: Memory at fddfc000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at de00 [size=256]
[virtual] Expansion ROM at fda00000 [disabled] [size=128K]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [c0] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s unlimited, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 2048 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1
Link: Latency L0s <1us, L1 <32us
Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [100] Advanced Error Reporting
Capabilities: [130] Device Serial Number 00-30-1b-ff-ff-be-65-37
00: ab 11 80 43 07 00 10 00 10 00 00 02 08 00 00 00
10: 04 c0 df fd 00 00 00 00 01 de 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 97 12 13 51
30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 01 00 00
*/

vectordrake · 01-09-2011, 11:44 AM

When you have this issue, its either the cable or one of the Ethernet devices, usually (a hardware issue). Try a new cable.

wpns · 01-09-2011, 02:01 PM

Many Thanks, Vector, you were absolutely right! The cable had been jammed into a connector (or just used too many times), and the plastic between pins 7 and 8 got bent so as to keep 8 from connecting.

Time for a new cable, and Yet Another Thing to check in the future.

It was a hardware problem after all!

vectordrake · 01-09-2011, 03:01 PM

Its always the thing that we assume is fine that we should look at first. LOL. I learned about the cable thing a long time ago. Never trust your cables! :-D