search for: 88e8056

on an ASUS P5K-E wifi (wifi disabled in bios) board with: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) centos 5.1 did not configure the device. Anyone else see this or have a solution? Tried forcing sky2 module, but init just says device does not seem to be present even tho lspci shows it on the bus. Is there another kernel module that also needs to...

...does not start. The startup script says something like "The 8169 is not available..." ifconfig -a shows a device with the right mac address called __tmpsomethingorother I can get it going if I remod the r8169 driver and load it again. Then ifup eth1 works. There's also a Marvell 88E8056 on the motherboard. /var/log/messages shows the 8169 as eth0 and the Marvell as eth1 but when the network is finally up they are the other way round. ifcfg-eth0 has the mac address of the Marvell in it and ifcfg-eth1 doesn't have a mac address in it. Should I wipe those scripts and start ag...

...CH10 Family) SATA AHCI Controller 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 03:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon HD 4670] 03:00.1 Audio device: ATI Technologies Inc RV710/730 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) 05:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 05:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 P...

I have a CentOS 5.2 install on a machine with the Marvell nic issue outlined in http://bugs.centos.org/view.php?id=2612. I have a few questions regarding this, what does the # echo "11ab 4364" > /sys/bus/pci/drivers/sky2/new_id line do? Obviously it starts right after but what specifically is the "11ab 4364" part? Also, how do I get this to load across reboots? I have the

Hello, I'm trying to install CentOS 5.2 on an HP 6730s notebook. All's going well except for one little item -- the networking. Never thought I'd have trouble with an Ethernet adapter, so I didn't even check before buying this machine; it was cheap. The adapter is a Marvell Yukon 88E8042 PCI-E Fast Ethernet controller. I can't find a Linux driver for it except one that

...7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 +-1c.0-[0000:03]----00.0 LSI Logic / Symbios Logic MegaRAID SAS 1078 +-1c.4-[0000:02]----00.0 JMicron Technologies, Inc. JMB368 IDE controller +-1c.5-[0000:01]----00.0 Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller +-1d.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 +-1d.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 +-1d.2 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 +-1d.7 Int...

Hi, I have a problem with file transfers between a windows systems and unix systems. I have one win32 desktop (intel e6400 2Gb Ram), one win32 laptop (p-m 2Ghz). Also one linux laptop (p-m 1.4GHz) and one opensolaris desktop (intel e4400 1GB Ram). The two laptops have built-in 100Mbit ethernet and desktops have 1Gbit ethernet on the motherboard. Both desktops use a Marvell Yukon. The file

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can

Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and was given this error: make CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-x86 CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC drivers/acpi/acpica/hwsleep.o drivers/acpi/acpica/hwsleep.c: In function

Now that x86-64 has directly accessible percpu variables, it can also implement the direct versions of these operations, which operate on a vcpu_info structure directly embedded in the percpu area. In fact, the 64-bit versions are more or less identical, and so can be shared. The only two differences are: 1. xen_restore_fl_direct takes its argument in eax on 32-bit, and rdi on 64-bit.