[Solved]Fresh install… attempts. Read errors! [Unsolved]NIC not loading
-
Thanx for the response.
The NIC shows 4 ports on usbus00 thru usbus40, but doesn't show up as usable interfaces once the LiveCD boots.
I have tried the 40GB drive again and I get the same issue. It is SATA as well. I don't own any IDE drives except a DVD drive somewhere in my attic. I have trimmed BIOS down to Legacy IDE and no items I won't be using. I'll try a few more things and then try to get this PC refunded ($50 special). I doubt they will, so I'm trying my hardest to get this functioning.
-
So I found the problem. The SATA controller only supports SATA150 (SataI) and the HDD the recycle center put in was a SataII. Theoretically, the drive should be able to communicate at SataI but I'm not sure which end the negotiation happens (obviously controller side on this board). It took me awhile to find a sata drive that was old enough, lol.
As far as the NIC issue, I was mistaken, the board is all Intel so I mistook the actual USB controller for the NIC (I R Dufus). Turns out the issue is not being able to allocate memory…
Here is my dmesg for my server:ACPI APIC Table: <intel d915gux=""> ... igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.1=""> at device 0.0 on pci3 igb0: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). igb0: Unable to allocate bus resource: memory igb0: Allocation of PCI resources failed device_attach: igb0 attach returned 6 igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.1=""> at device 0.1 on pci3 igb1: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). igb1: Unable to allocate bus resource: memory igb1: Allocation of PCI resources failed device_attach: igb1 attach returned 6 pcib4: <pci-pci bridge=""> at device 4.0 on pci2 pci4: <pci bus=""> on pcib4 igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.1=""> port 0xac00-0xac1f irq 16 at device 0.0 on pci4 igb2: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). igb2: Unable to allocate bus resource: memory igb2: Allocation of PCI resources failed device_attach: igb2 attach returned 6 igb3: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.1=""> at device 0.1 on pci4 igb3: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). igb3: Unable to allocate bus resource: memory igb3: Allocation of PCI resources failed device_attach: igb3 attach returned 6</intel(r)></intel(r)></pci></pci-pci></intel(r)></intel(r)></intel > -
Hmm, that's a tricky one. Looks like no obvious solution to that. Looks like the card isn't being initialised properly. Are you on the latest BIOS version? Is it set for "OS allocates resources", I forget the exact wording but FreeBSD doesn't do that. It relies on the BIOS to correctly setup PCI cards.
Steve
Edit: It's 'PNP aware OS'. Should be disabled.
-
I'm not sure. The only option in BIOS is Auto and IRQ8/9. Could be unrelated. BIOS is up to date circa 2005, nothing newer out there. Maybe it is PCI speed? 33 vs 166? Or is that PCI-X only?
-
Bus speed shouldn't effect memory allocation. My money would be on finding the right BIOS setting. Google's giving me nothing! ::)
Steve
-
Ditto
-
Well, my lack of experience with Linux, specifically BSD, has crippled me. Forum page after blog after video, after my outdated pfSense guide… I'm lost. :( Halp?
Time to make a new thread on parts for new build....
EDIT So I found an article on ark.intel.com stating that some older NICs would not function in PCIe 2.0 slots. In this article it specifically states my card (E1G44ET2) is a good replacement for this problem. It got me wondering how I can eliminate this as a possibility... doh, nvm. It works in Ubuntu... Let me go double check... /EDIT
To be continued....
-
Have you tried that combination of hardware with any other OS?
Steve
-
Ok, this is going to be a lot of logs, my apologies. Here are the results:
Ubuntu 13.04 LiveCD:```
id:
network:0
description: Ethernet interface
product: 82576 Gigabit Network Connection
vendor: Intel Corporation
physical id:
0
bus info:
pci@0000:03:00.0
logical name:
eth0
version: 01
serial: [REMOVED]
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration:
autonegotiation = on
broadcast = yes
driver = igb
driverversion = 4.1.2-k
firmware = 1.80, 0x61690001
latency = 0
link = no
multicast = yes
port = twisted pair
resources:
irq : 18
memory : 41000000-4101ffff
memory : 40000000-403fffff
ioport : 9000(size=32)
memory : 41040000-41043fff
memory : 40400000-407fffff
memory : 41044000-41063fff
memory : 41064000-41083fff
id:
network:1
description: Ethernet interface
product: 82576 Gigabit Network Connection
vendor: Intel Corporation
physical id:
0.1
bus info:
pci@0000:03:00.1
logical name:
eth1
version: 01
serial: [REMOVED]
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration:
autonegotiation = on
broadcast = yes
driver = igb
driverversion = 4.1.2-k
firmware = 1.80, 0x61690001
latency = 0
link = no
multicast = yes
port = twisted pair
resources:
irq : 19
memory : 41020000-4103ffff
memory : 40800000-40bfffff
ioport : 9020(size=32)
memory : 41084000-41087fff
memory : 40c00000-40ffffff
memory : 41088000-410a7fff
memory : 410a8000-410c7fff
id:
network:0
description: Ethernet interface
product: 82576 Gigabit Network Connection
vendor: Intel Corporation
physical id:
0
bus info:
pci@0000:04:00.0
logical name:
eth2
version: 01
serial: [REMOVED]
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration:
autonegotiation = on
broadcast = yes
driver = igb
driverversion = 4.1.2-k
duplex = full
firmware = 1.80, 0x616a0001
ip = [REMOVED]
latency = 0
link = yes
multicast = yes
port = twisted pair
speed = 1Gbit/s
resources:
irq : 16
memory : 41200000-4121ffff
memory : 41400000-417fffff
ioport : ac00(size=32)
memory : 41240000-41243fff
memory : 41800000-41bfffff
memory : 41244000-41263fff
memory : 41264000-41283fff
id:
network:1
description: Ethernet interface
product: 82576 Gigabit Network Connection
vendor: Intel Corporation
physical id:
0.1
bus info:
pci@0000:04:00.1
logical name:
eth3
version: 01
serial: [REMOVED]
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration:
autonegotiation = on
broadcast = yes
driver = igb
driverversion = 4.1.2-k
firmware = 1.80, 0x616a0001
latency = 0
link = no
multicast = yes
port = twisted pair
resources:
irq : 17
memory : 41220000-4123ffff
memory : 41c00000-41ffffff
ioport : a000(size=32)
memory : 41284000-41287fff
memory : 42000000-423fffff
memory : 41288000-412a7fff
memory : 412a8000-412c7fff
id:
network
description: Ethernet controller
product: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id:
8
bus info:
pci@0000:09:08.0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm cap_list
configuration:
latency = 32
maxlatency = 56
mingnt = 8
resources:
memory : fbe00000-fbe00fff
ioport : bc00(size=64)Works fine on all 4 ports with speeds of 1Gbs on each port. FreeBSD 9.1 (only 2/4 ports work..?):``` igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.4=""> at device 0.0 on pci3 igb0: Using MSIX interrupts with 3 vectors igb0: Ethernet address: 90:e2:ba:23:2d:f0 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.4=""> at device 0.1 on pci3 igb1: Using MSIX interrupts with 3 vectors igb1: Ethernet address: 90:e2:ba:23:2d:f1 igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.4=""> port 0xac00-0xac1f irq 16 at device 0.0 on pci4 igb2: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). igb2: Unable to allocate bus resource: memory igb2: Allocation of PCI resources failed device_attach: igb2 attach returned 6 igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.3.4=""> at device 0.1 on pci4 igb2: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). igb2: Unable to allocate bus resource: memory igb2: Allocation of PCI resources failed device_attach: igb2 attach returned 6 module_register: module pci/igb already exists! Module pci/igb failed to register: 17 module_register: module pci/igb already exists! Module pci/igb failed to register: 17 igb1: link state changed to U</intel(r)></intel(r)></intel(r)></intel(r)>Why does it only load 2 of 4? How do I get this to function on pfSense?
-
Hmm, does the card have a pci bridge chip on it? Many multiport card do and they can be a problem.
I notice that the two interfaces that worked under 9.1 are on a different pci bus. Also they are using MSI instead of IRQs.
Under Ubuntu they are all using IRQs and are each on a separate one.
Steve
-
I have no idea. I didn't find anything on Intel's site and I don't know what a PCI Bridge chip looks like. There are pictures on Newegg that are the exact card I have and they offer hi-res zoom in. You are welcome to take a peek and let me know (if interested). Just click on one of the pics and zoom away. Gets close enough to read the text next to each diode sometimes.
Link: http://www.newegg.com/Product/Product.aspx?Item=N82E16833106074
-
Ah nice. I see it has a number of large and expensive looking ICs including this:
http://www.idt.com/products/interface-connectivity/pci-express-solutions/pci-express-switches/io-expansion-switches/89hpes12n3a-12-lane-3-port-pcie-io-expansion-switch
It's entirely possible that your BIOS is not playing nicely with this. I don't know enough about PCIe to give you any real clues here though.
The only time I've seen a similar situation resolved the bridge chip was hiding the interfaces entirely. The fact the pfSense is able to detect and talk to the NICs at all suggests this PCIe switch is working. :-
It's probably not worth the effort to make this work to be honest.Steve
