public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin E <kevin360@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Marvell 88E8056 gigabit ethernet controller
Date: Fri, 17 Aug 2007 05:42:13 -0700 (PDT)	[thread overview]
Message-ID: <424491.59139.qm@web38906.mail.mud.yahoo.com> (raw)

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 F10)
Core2 Q6600
2GB Corsair XMS2 memory
kernel 2.6.22.3

lspci for LAN controller:
04:00.0 Ethernet controller: Marvell Technology Group
Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev
14)


Broken system:
Gigabyte 965P-DS3 rev 3.3  (BIOS F10)
Core2 E4400
2GB Corsair XMS2 memory
kernel 2.6.22.3

lspci for LAN controller:
03:00.0 Ethernet controller: Marvell Technology Group
Ltd. Unknown device 4364 (rev 12)


	The BIOS for the two systems are setup the same and
the config for the kernels are the same too.  I've
actually tried taking the kernel from the working
system and booting it on the broken one but still the
LAN dies after a couple of seconds.  The working
system has one card plugged in (nvidia based PCI-X
video card), I've taken that card and plugged into the
broken system, booted the same kernel, and it still
dies after a while.

	I will gladly provide any info needed if it can help
in getting this chipset working on the Gigabyte
boards.

	Thanks,
	Kevin


       
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. 
http://answers.yahoo.com/dir/?link=list&sid=396545433

             reply	other threads:[~2007-08-17 12:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 12:42 Kevin E [this message]
2007-08-18  0:03 ` Marvell 88E8056 gigabit ethernet controller Stephen Hemminger
2007-08-18  5:38   ` Willy Tarreau
2007-08-18 11:45     ` Kevin E
2007-08-18 12:17       ` Willy Tarreau
2007-08-18 13:59         ` Kevin E
2007-08-19 16:32           ` Stephen Hemminger
2007-08-19 16:42             ` Kevin E
2007-08-21 17:07               ` [RFT] sky2: yukon-ec-u phy power problems Stephen Hemminger
2007-08-22 22:37                 ` Kevin E
     [not found]             ` <2456F7EB-000C-4B71-B002-64340DD17BA8@linuxmontreal.com>
2007-08-19 18:34               ` Marvell 88E8056 gigabit ethernet controller Stephen Hemminger
2007-08-19 19:13                 ` Kevin E
2007-08-19 23:04                 ` Eric Preston
2007-08-20  1:15               ` Kevin E
2007-08-20 15:01                 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2007-08-19 22:45 Eric Preston

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=424491.59139.qm@web38906.mail.mud.yahoo.com \
    --to=kevin360@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox