Just to follow up, I believe it turns out that this card does not follow 
mini-PCI
specification correctly.  It is apparently designed for some proprietary 
motherboard's
mini-PCI express slot and the second 82574 chip is only operable in those 
boards,
so there is probably nothing to fix this here.

On Mon, Nov 07, 2011 at 06:45:34PM -0800, Chad Cantwell wrote:
> Hi,
> 
> I have a net6501, and need more than 4 ethernet ports.  I was originally
> planning to use the PCI-E slot, but I could not find any good low-powered
> cards that would fit in an x1 connector, and wanted to avoid hacking the
> slot or cards up.  I did find a nice dual gigabit ethernet mini pci
> express card, with the same intel 82574L as the soekris has onboard, here,
> which I thought would be perfect:
> 
> http://www.commell.com.tw/Product/Peripheral/PCI%20Express%20mini%20card/MPX-574D2.HTM
> 
> So I bought one, and I've installed it, but it is only recognized as one
> ethernet card.  I'm using the latest bios I could find (revision h) and the
> vanilla linux kernel 2.6.39.4, since the 3.x versions had the same serial
> port panic as others reported.  I don't think it would matter, since I'm using
> my own kernel, but if anyone cares I am running Ubuntu 10.04.3.  Here is the
> lspci:
> 
> 00:00.0 Host bridge: Intel Corporation Tunnel Creek PCI Host Bridge #1 (rev 
> 05)
> 00:01.0 Host bridge: Intel Corporation Tunnel Creek Configuration Unit
> 00:17.0 PCI bridge: Intel Corporation Tunnel Creek PCI Express Port 1
> 00:18.0 PCI bridge: Intel Corporation Tunnel Creek PCI Express Port 2
> 00:19.0 PCI bridge: Intel Corporation Tunnel Creek PCI Express Port 3
> 00:1a.0 PCI bridge: Intel Corporation Tunnel Creek PCI Express Port 4
> 00:1f.0 ISA bridge: Intel Corporation Tunnel Creek LPC Bridge
> 01:00.0 PCI bridge: Intel Corporation Topcliff PCI Express Port (rev 01)
> 02:00.0 Class ff00: Intel Corporation Topcliff Packet Hub (rev 01)
> 02:00.1 Ethernet controller: Intel Corporation Topcliff Gigabit Ethernet 
> Controller (rev 01)
> 02:00.2 Class ff00: Intel Corporation Topcliff General Purpose IO Controller
> 02:02.0 USB Controller: Intel Corporation Topcliff USB OHCI Controller #4 
> (rev 01)
> 02:02.1 USB Controller: Intel Corporation Topcliff USB OHCI Controller #5 
> (rev 01)
> 02:02.2 USB Controller: Intel Corporation Topcliff USB OHCI Controller #6 
> (rev 01)
> 02:02.3 USB Controller: Intel Corporation Topcliff USB2 EHCI Controller #2 
> (rev 01)
> 02:02.4 USB Controller: Intel Corporation Topcliff USB Client Controller (rev 
> 01)
> 02:04.0 SD Host controller: Intel Corporation Topcliff SDIO Controller #1 
> (rev 01)
> 02:04.1 SD Host controller: Intel Corporation Topcliff SDIO Controller #2 
> (rev 01)
> 02:06.0 SATA controller: Intel Corporation Topcliff SATA AHCI Controller (rev 
> 01)
> 02:08.0 USB Controller: Intel Corporation Topcliff USB OHCI Controller #1 
> (rev 01)
> 02:08.1 USB Controller: Intel Corporation Topcliff USB OHCI Controller #2 
> (rev 01)
> 02:08.2 USB Controller: Intel Corporation Topcliff USB OHCI Controller #3 
> (rev 01)
> 02:08.3 USB Controller: Intel Corporation Topcliff USB2 EHCI Controller #1 
> (rev 01)
> 02:0a.0 Class ff00: Intel Corporation Topcliff DMA Controller #1
> 02:0a.1 Serial controller: Intel Corporation Topcliff UART Controller #1
> 02:0a.2 Serial controller: Intel Corporation Topcliff UART Controller #2
> 02:0a.3 Serial controller: Intel Corporation Topcliff UART Controller #3
> 02:0a.4 Serial controller: Intel Corporation Topcliff UART Controller #4
> 02:0c.0 Class ff00: Intel Corporation Topcliff DMA Controller #2
> 02:0c.1 Serial bus controller [0c80]: Intel Corporation Topcliff Serial 
> Peripheral Interface Bus
> 02:0c.2 Serial bus controller [0c80]: Intel Corporation Topcliff I2C 
> Controller
> 02:0c.3 CANBUS: Intel Corporation Topcliff Controller Area Network (CAN) 
> Controller
> 02:0c.4 Class ff00: Intel Corporation Topcliff IEEE 1588 Hardware Assist (rev 
> 01)
> 03:00.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 04:02.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 04:03.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 04:04.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 08:00.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 09:02.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 09:03.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 09:04.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express 
> Switch (rev 0e)
> 0a:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 0b:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 
> As you can see, there are 5 lines with 82574L:
> 05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 0a:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 0b:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
> Connection
> 
> Where I would expect 6.  I read somewhere that there is only one PCI-E lane
> hooked up to the mini PCI slot.  Does anyone know if it makes sense that a 
> mini
> pci express card might be a "dumb" device that tries to hook itself up as two
> indepedant 82574L chips on separate lanes, and maybe that is why only one
> interface shows up?  If this is the case, obviously there is nothing that can 
> be
> done.  But, if the problem is something more complicated, like a 
> compatibility issue
> with the way the bios initializes or looks for hardware on the PCI express 
> bus,
> maybe it could be fixed?
> 
> Chad
> _______________________________________________
> Soekris-tech mailing list
> [email protected]
> http://lists.soekris.com/mailman/listinfo/soekris-tech
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech

Reply via email to