On Sun, 19 Aug 2007 18:15:47 -0700 (PDT)
Kevin E <[EMAIL PROTECTED]> wrote:
> 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
>
On Sun, 19 Aug 2007 18:15:47 -0700 (PDT)
Kevin E [EMAIL PROTECTED] wrote:
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
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
On 19-Aug-07, at 2:34 PM, Stephen Hemminger wrote:
The driver prints some chip version info at startup, that might
be helpful in disambiguating good/bad versions:
dmesg | grep sky2
sky2 :03:00.0: v1.16 addr 0xfa00 irq 16 Yukon-EC Ultra (0xb4)
rev 2
sky2 eth0: addr
> 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:00.0 Ethernet controller: Marvell Technology Group Ltd.
--- 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
The driver prints some chip version info at startup, that might
be helpful in disambiguating good/bad versions:
dmesg | grep sky2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
--- 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
>
On Sat, 18 Aug 2007 06:59:08 -0700 (PDT)
Kevin E <[EMAIL PROTECTED]> wrote:
> --- 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
On Sat, 18 Aug 2007 06:59:08 -0700 (PDT)
Kevin E [EMAIL PROTECTED] wrote:
--- 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
--- 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:00.0
The driver prints some chip version info at startup, that might
be helpful in disambiguating good/bad versions:
dmesg | grep sky2
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
--- 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 Ultra
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:00.0 Ethernet controller: Marvell Technology Group Ltd.
On 19-Aug-07, at 2:34 PM, Stephen Hemminger wrote:
The driver prints some chip version info at startup, that might
be helpful in disambiguating good/bad versions:
dmesg | grep sky2
sky2 :03:00.0: v1.16 addr 0xfa00 irq 16 Yukon-EC Ultra (0xb4)
rev 2
sky2 eth0: addr
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
--- 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
On Sat, Aug 18, 2007 at 04:45:26AM -0700, Kevin E wrote:
>
> --- 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
--- 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
--- 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
On Sat, Aug 18, 2007 at 04:45:26AM -0700, Kevin E wrote:
--- 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
--- 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' and
On Fri, Aug 17, 2007 at 05:03:41PM -0700, Stephen Hemminger wrote:
> On Fri, 17 Aug 2007 05:42:13 -0700 (PDT)
> Kevin E <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> >
> > I've read where the onboard Marvell lan controller on
> > some Gigabyte boards don't work. I've got two systems
> > using
On Fri, 17 Aug 2007 05:42:13 -0700 (PDT)
Kevin E <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've read where the onboard Marvell lan controller on
> some Gigabyte boards don't work. I've got two systems
> using the same Gigabyte board, on one the LAN works on
> the other it dies like
Hi all,
I've read where the onboard Marvell lan controller on
some Gigabyte boards don't work. I've got two systems
using the same Gigabyte board, on one the LAN works on
the other it dies like described by others. Here's
the systems:
Working system:
Gigabyte 965P-DS3 rev 3.3 (BIOS
Hi all,
I've read where the onboard Marvell lan controller on
some Gigabyte boards don't work. I've got two systems
using the same Gigabyte board, on one the LAN works on
the other it dies like described by others. Here's
the systems:
Working system:
Gigabyte 965P-DS3 rev 3.3 (BIOS
On Fri, 17 Aug 2007 05:42:13 -0700 (PDT)
Kevin E [EMAIL PROTECTED] wrote:
Hi all,
I've read where the onboard Marvell lan controller on
some Gigabyte boards don't work. I've got two systems
using the same Gigabyte board, on one the LAN works on
the other it dies like described by
On Fri, Aug 17, 2007 at 05:03:41PM -0700, Stephen Hemminger wrote:
On Fri, 17 Aug 2007 05:42:13 -0700 (PDT)
Kevin E [EMAIL PROTECTED] wrote:
Hi all,
I've read where the onboard Marvell lan controller on
some Gigabyte boards don't work. I've got two systems
using the same
28 matches
Mail list logo
