--- Willy Tarreau <[EMAIL PROTECTED]> wrote:
> No Stephen, look again, he says that moving the
> video card into the broken
> system does not change anything.
Correct, I've used three different video cards in the
broken machine. I've used an old PCI vid card, the
PCI-X vid card from the working
--- Willy Tarreau <[EMAIL PROTECTED]> wrote:
> OK, in this trace, both controllers are on the same
> bus. The broken
> one has 'Capabilities: [100] Advanced Error
> Reporting' the other
> does not have, and the bridge to this bus has two
> more capabilities :
> 'Capabilities: [100] Virtual Channel
--- Stephen Hemminger
<[EMAIL PROTECTED]> wrote:
> The working board has a different version of the
> Marvell chip:
>
> $ grep Marvell working-MB
> 04:00.0 Ethernet controller: Marvell Technology
> Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller
> (rev 14)
> $ grep Marvell broken-MB
> 04:
--- Stephen Hemminger
<[EMAIL PROTECTED]> wrote:
> The driver prints some chip version info at startup,
> that might
> be helpful in disambiguating good/bad versions:
>
> dmesg | grep sky2
Here's the output from the working MB:
sky2 :04:00.0: v1.14 addr 0xf800 irq 16
Yukon-EC Ult
Someone wrote me with a solution to try and so far
it's working. They suggested I try the driver up on
Marvell's website but to make sure I powered off the
machine completely and when it rebooted to not have
any of the regular kernel drivers for the Marvell
chipset to load. They had found that le
--- Stephen Hemminger
<[EMAIL PROTECTED]> wrote:
> The sky2 driver clears some bits in the PHY control
> register, that cause
> the PHY interface to get changed. Some of these
> deal with voltage and power
> savings as well. This may explain some of the
> failures on Gigabyte DS-3 motherboard.
>
