Marvell 88E8056 gigabyte LAN interface on asus p5b doesn't work

[neutrico]

Binary package hint: linux-image-2.6-686

Asus P5B Deluxe mobo has two onboard network interfaces.

First is MArvell 88E8001 Gigabit Ethernet Controller and second is Marvell 88E8056.

And while 88E8001 is supported (although reports that is 10/100 interface - not 1000 - second doesn't work and isn't recognized by kernel.

lspci -v says that:

0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd.: Unknown device 4364 (rev 12)
        Subsystem: ASUSTeK Computer Inc.: Unknown device 81f8
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at fe7fc000 (64-bit, non-prefetchable) [size=16K]
        I/O ports at 9800 [size=256]
        Expansion ROM at fe7c0000 [disabled] [size=128K]

[Vassilis Pandis (pandisv)]

I'm going to reject one of the bug tasks. Don't take this wrong - your report is not being ignored/rejected. It simply applies only to linux-source-2.6.15 . Thanks for reporting this.

[neutrico (neutrico)]

I'm not sure if I undestood your comment properly. Does it mean that this bug is fixed in 2.6.17? Can you confirm that?

I found some interesting thread in kerneltrap. It seems that this bug is fixed in 2.6.18.....
http://kerneltrap.org/node/7135

"Support for the chip is in Andrew Morton's 2.6.18-rc7-mm patch"

Can this patch be backported to 2.6.15? Edgy is really not ready to install - specifically because of jmicron issue - and it could be nice to have both NIC's workable on Asus p5b mobo.

[Giblet5 (pw-byteshuffler)]

It is worth noting that Asus does have Marvell linux drivers (and other linux drivers for the Deluxe P5B) on their support web.

IMO, that is the best solution at this time.

The driver worked just fine for me on Dapper and Edgy EFT. Yes, I have both (mostly) working on a P5B Deluxe. With Beryl, no-less.

I'm skeptical that this can be considered a bug, even with linux-source.

Yes, you have to build the vendor's driver every time your kernel image or modules get updated, but vendor-created drivers make a lot more sense than having the Ubuntu-Dev-Team (or kernel devs, or RedHat devs, etc) knocking themselves out every time a new IC chip is released... Just sayin' is all.

Hardware issues with Linux (or MS Windows, or MacOS, or BillyBobsOS) should always be directed to the hardware vendor first, and in the strongest (but fair) terms. They own the entire device driver and customer satisfaction development tree for your product. Period. If the vendor is unresponsive, don't buy from them and tell everyone you know about your experience.

[neutrico (neutrico)]

Well, I totally disagree with you that I should build the vendor's driver. I really don't want to do this. I just want this to work out of the box. And if it doesn't then I consider this a bug.

IMHO there should be some package with this driver as external module (just like drivers for nvidia graphics cards or ati) and ubuntu should be able to install this package if it is required or at last should give an ability to install this driver manually and run hardware in easy way.

If Marvell is so nice and provides drivers for it's hardware and these drivers are on GPL!!! then come on - grab them and use them!

I very often can hear that linux users and developers complains that these ugly vendors don't want to provide drivers or provide these drivers in binary and restricted formats/licenses. Marvell is really nice exception so please someone prepare package with driver or patch kernel and provide package. I would like to do this myself but currenlty I don't have skills to prepare such package.

[Xaignar (xaignar)]

As mentioned in the kerneltrap thread above, all that is needed to get the 88E8056 NIC working is to add an entry for the card to the sky2_id_table array in sky2.c. So far, I've made do by manually patching the sky2.ko file, but having the NIC work out of the box would be nice, especially since it's the only NIC on the motherboard I have (Gigabyte GA-965P-S3), and I don't expect that most users are able to add support for the NIC themselves.

[Chuck Short (zulcss)]

Added to my git tree.

[Chuck Short (zulcss)]

Ditto

[Leann Ogasawara (leannogasawara)]

This report was marked 'Fix Committed' a while ago and there hasn't been any activity in it recently. I'm going to go ahead and mark the status as 'Fix Released'. If this is not the case, please retest against the latest Hardy Alpha release and report back your results. Thanks in advance.

[Tog (tony-hessler-btinternet)]

ASUS P5Q-E motherboard, two on-board Marvell ethernet adapters, neither of which works.
lspci -v output:
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
 Subsystem: ASUSTeK Computer Inc. Device 81f8
 Flags: bus master, fast devsel, latency 0, IRQ 219
 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
 I/O ports at c800 [size=256]
 Expansion ROM at fe9c0000 [disabled] [size=128K]
 Capabilities: [48] Power Management version 3
 Capabilities: [50] Vital Product Data <?>
 Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
 Capabilities: [e0] Express Legacy Endpoint, MSI 00
 Capabilities: [100] Advanced Error Reporting <?>
 Kernel driver in use: sky2
I have tried the sk98lin driver but this does not work either.
hwinfo:
13: PCI 200.0: 0200 Ethernet controller
  [Created at pci.310]
  UDI: /org/freedesktop/Hal/devices/pci_11ab_4364
  Unique ID: mY_N.lJIN+p5NzvB
  Parent ID: HnsE.cl8tOgOWATC
  SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "Marvell 88E8056 PCI-E Gigabit Ethernet Controller"
  Vendor: pci 0x11ab "Marvell Technology Group Ltd."
  Device: pci 0x4364 "88E8056 PCI-E Gigabit Ethernet Controller"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x81f8
  Revision: 0x12
  Driver: "sky2"
  Driver Modules: "sky2"
  Device File: eth2
  Memory Range: 0xfe9fc000-0xfe9fffff (rw,non-prefetchable)
  I/O Ports: 0xc800-0xc8ff (rw)
  Memory Range: 0xfe9c0000-0xfe9dffff (ro,prefetchable,disabled)
  IRQ: 219 (1 event)
  HW Address: 00:22:15:63:bb:6f
  Module Alias: "pci:v000011ABd00004364sv00001043sd000081F8bc02sc00i00"
  Driver Info #0:
    Driver Status: sky2 is active
    Driver Activation Cmd: "modprobe sky2"