Intel 82574L Not Detected? But 82574 is supported….
-
Can anyone help me out with this one?
Intel states that it uses the same driver, but I cannot get PFsense to detect it.
I did test it on another pc and it works fine (Server 2008)
If I need to add additional drivers, I'd love to know how to do that. I have searched for a few hours now and all the steps that people describe involve having to compile the kernel myself and then reinstall. That seems to be a little bit extreme to me for drivers, but I'm greener than green on BSD and still very green to Linux in general (I know, they are not the same thing).
Trying to branch out from M$ products but i'm always running into these fundamental issues with other OSes.
-
82574L works fine. You should provide more details about the hardware you're using.
-
Indeed, it should work fine. I'm using several here right now.
It's possible to add drivers for some hardware without compiling a new kernel but usually you shouldn't have to, in this case definitely not.I'm greener than green on BSD and still very green to Linux in general (I know, they are not the same thing)
Already you've understood more than many people. ;)
Steve
-
Sorry for the long delay on a reply. I'm a Jr Windows Analyst and I'm on call for this holiday weekend and of course, someone broke something… I'll leave it at that. :P
Ok, here is the hardware:
Specs- Asus E35M1-I (Motherboard)
Integrated AMD Dual-Core Processor E-350
8GB Ram (only had an 8Gig stick laying around
36Gig Raptor HDD
Standard ATX PSU
DVD Drive
Basic stuff really…
The NIC in question:
- Intel
Gigabit CT Desktop Adapter – EXPI9301CT
Intel 82574L Gigabit Ethernet Controller
PCIe Interface
Now I did test the PCIe slot itself with a PCIe video card and it lights up a monitor just fine. So I’m I really am stumped as to why I cannot get this pfSense to see the card. I also booted up a Ubuntu live cd and it saw it just fine.
This is a new install of 2.1.3 BTW
Shrugs
- Asus E35M1-I (Motherboard)
-
Ok. Basic question; what makes you think it's not detected?
I assume that the onboard Realtek NIC is recognised so you can complete the install with one NIC?
At the console (physically or via SSH) bring up a command prompt and enter:
pciconf -lvIf you do it via ssh you can just copy and paste the result here.
Steve
-
Oh i need more time. In the console, the adapter never shows up, and in effect, not in the web interface. What do you make of this Boss?
hostb0@pci0:0:0:0: class=0x060000 card=0x84a51043 chip=0x15101022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
vgapci0@pci0:0:1:0: class=0x030000 card=0x84a51043 chip=0x98021002 rev=0x00 hdr=0x00
class = display
subclass = VGA
atapci0@pci0:0:17:0: class=0x010601 card=0x84961043 chip=0x43911002 rev=0x40 hdr=0x00
class = mass storage
subclass = SATA
ohci0@pci0:0:18:0: class=0x0c0310 card=0x84961043 chip=0x43971002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
ehci0@pci0:0:18:2: class=0x0c0320 card=0x84961043 chip=0x43961002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
ohci1@pci0:0:19:0: class=0x0c0310 card=0x84961043 chip=0x43971002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
ehci1@pci0:0:19:2: class=0x0c0320 card=0x84961043 chip=0x43961002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
none0@pci0:0:20:0: class=0x0c0500 card=0x84961043 chip=0x43851002 rev=0x42 hdr=0x00
class = serial bus
subclass = SMBus
isab0@pci0:0:20:3: class=0x060100 card=0x84961043 chip=0x439d1002 rev=0x40 hdr=0x00
class = bridge
subclass = PCI-ISA
pcib1@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x40 hdr=0x01
class = bridge
subclass = PCI-PCI
ohci2@pci0:0:20:5: class=0x0c0310 card=0x84961043 chip=0x43991002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
pcib2@pci0:0:21:0: class=0x060400 card=0x00001002 chip=0x43a01002 rev=0x00 hdr=0x01
class = bridge
subclass = PCI-PCI
pcib3@pci0:0:21:1: class=0x060400 card=0x00001002 chip=0x43a11002 rev=0x00 hdr=0x01
class = bridge
subclass = PCI-PCI
ohci3@pci0:0:22:0: class=0x0c0310 card=0x84961043 chip=0x43971002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
ehci2@pci0:0:22:2: class=0x0c0320 card=0x84961043 chip=0x43961002 rev=0x00 hdr=0x00
class = serial bus
subclass = USB
hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x17001022 rev=0x43 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x17011022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x17021022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x17031022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb5@pci0:0:24:4: class=0x060000 card=0x00000000 chip=0x17041022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb6@pci0:0:24:5: class=0x060000 card=0x00000000 chip=0x17181022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb7@pci0:0:24:6: class=0x060000 card=0x00000000 chip=0x17161022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb8@pci0:0:24:7: class=0x060000 card=0x00000000 chip=0x17191022 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
re0@pci0:3:0:0: class=0x020000 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00
class = network
subclass = ethernet -
Hmm, OK. So the reason the card isn't appearing is nothing to do with the driver but that it isn't showing up on the PCI bus at all. Usually that is caused by some sort of PCI bridge chip that isn't supported being on the card (or the board). Sometimes it can be the BIOS is not initialising something correctly.
Are you running the most recent BIOS?
It might show what the difference is if you could give us a similar readout from Ubuntu. 'lspci' should be sufficient.
Steve
-
To avoid family & friend wrath, I only brought the router down long enough to pull and plop into another machine.
This came from windows, and is this what you're looking for?
PCI\VEN_8086&DEV_1502&SUBSYS_102517AA&REV_05\3&11583659&0&C8 -
Hmm, OK. Some interesting info there.
The chip on the card VID 8086 (Intel) PID 1502 appears to be an 828579 rather than an 82574.
http://pci-ids.ucw.cz/read/PC/8086/1502
However the 82579 is reportedly a separate PHY so gard to say what's going on there. The subsys IDs don't tell us much, they appear as either Acer or Lenovo. :-\ Is this an actual Intel card?It should be supported. 1502 is listed in the FreeBSD driver:
@http://svnweb.freebsd.org/base/releng/8.3/sys/dev/e1000/e1000_hw.h?revision=232438&view=markup:#define E1000_DEV_ID_PCH2_LV_LM 0x1502
It doesn't really matter because the card doesn't appear at all in pciconf. The only unknown device listed is the SMBus controller which isn't important.
The output from Ubuntu would be more telling.Steve
-
Can you see the device in the bios setup? Most bios screens show the devices that are detected, so if it's not detected there then pfSense has little hope of finding it.
I see that the 82579 is not PCIe compliant, according to Intel's own datasheet for the chip, as it operates at half the PCIe 1.1 speed. Perhaps this MB has trouble with that. You said the card worked OK in another PC and another OS; the difference may well have been the MB rather than the OS.
Try to boot a linux live cd on that machine, and see what's reported. And don't worry about the wrath, just tell em you're doing your job …
-
lspci for Ubuntu…. and I don't see the card in there nor is it working
The motherboard is on the latest BIOS as well...
Poo..
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310]
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1)
00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 0 (rev 43)
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 6
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 5
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 7
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) -
It's probably some problem with the BIOS not initialising the a PCI bridge chip correctly. There are unfortunately many bioses that only work fully under windows. >:( It might also be a more fundamental hardware incompatibility PCIe bus versions for example.
There may be something you can adjust in the BIOS setup to get this working, some resource change for example. More research needed. ;)Steve
