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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/