NIC onboard Realtek 8111E



  • Hi All,

    I just buy a new mainboard with NIC onboard ( Realtek 8111E), When i install Pfsense V2, this version cannot detect my NIC onboard, I also try to install FreeNAS new realease version for test and it success, so i wonder how i can bring Pfsense V2 Detect my NIC as FreeNAS ( copy some file from FreeNAS to Pfsense… or do something for this).
    Thanks for any help.



  • Based on fast search i didn't found that nic on supported hardwarelist



  • I don't know much about compile new driver from Realtek with FreeBSD and still trying to…



  • Strange, my NC9C has RTL8111E PCIe and both onboard NIC's are detected, re0 re1.



  • @trunglam:

    I just buy a new mainboard with NIC onboard ( Realtek 8111E), When i install Pfsense V2, this version cannot detect my NIC onboard,

    In the light of:@onhel:

    Strange, my NC9C has RTL8111E PCIe and both onboard NIC's are detected, re0 re1.

    please explain how you determined the pfSense can't detect the onboard NIC.

    What mainboard are you using?



  • My new mainboard is ASUS P8H61-V with new update bios version and still not auto recognize NIC onboard. I also try to load some driver into kernel and now continue find solution…If don't want to buy another mainboard.



  • @trunglam:

    My new mainboard is ASUS P8H61-V with new update bios version and still not auto recognize NIC onboard.

    By auto recognize NIC onboard I presume you mean the automatic assignment option to pfSense console dialog Assign Interfaces in which pfSense prompts for the interface and you insert an active cable into the appropriate socket. Is that correct?

    Can you get past that to interface to the web GUI? If not, what is stopping you? (I would like to see the output from the pfSense shell command pciconf -l -v; dmesg to determine the identification codes in the onboard NIC).



  • I just find more infor about it

    dmesg | grep 're0"

    Re0: <realtek 8111="" 8168="" b="" c="" cp="" dp="" e="" pcie="" gigabit="" ethernet="">Port 0xe000-0xe0ff mem 0xd0004000-0xd0004fff, 0xd0000000 - 0xd0003fff irq 18 at device 0.0 on pci 4
    Re0: Using 1 MSI Messages
    Re0 : Chip Rev. 0x2c800000
    Re0 : MAC Rev. 0x00000000
    Re0: Unknow H/W Revison : 0x2c800000
    Device_attach: re0 attach returned 6

    …and

    picconf -lv | grep 're0"

    re0@pci0:4:0:0: class=0x020000 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x06

    So any suggest for more?

    Thanks alot...!</realtek>



  • If you do a ifconfig re0, what is the output?

    Since re0 is present, the NIC is detected and a driver loaded.  However, you might have to manually assign the interface?



  • Thanks for reply,

    I try to find re0 but no interface return so how can i manual assign this interface?



  • @trunglam:

    I try to find re0 but no interface return so how can i manual assign this interface?

    You can't. The re driver is recognising the NIC but (cautiously?) refusing to take ownership of it (Device_attach: re0 attach returned 6) apparently because Re0: Unknow H/W Revison : 0x2c800000

    You need an updated driver. Without some investigation it is not possible to say whether a more recent re driver than the re driver built into pfSense 2.0 fixes the problem nor is it possible to say (without investigation) if it is a trivial task to backport a suitable driver to pfSense 2.0 (FreeBSD 8.1).

    Since you are set on using the motherboard you have I think the best (least hassle to you) solution is buy another NIC and not use the onboard NIC for the time being. If you already have one or more expansion NICs you might be able to use a VLAN capable switch to get additional interfaces: search the forums for VLAN port multiplier to see some posts that discuss this.



  • My mainboard is running success with FreeNAS new version so can i copy some thing form FreeNAS to Pfsense or recompile with this kernel? for help pfsense to recognize this NIC?

    Thanks



  • @trunglam:

    can i copy some thing form FreeNAS to Pfsense or recompile with this kernel?

    In pfSense most drivers are built into the kernel. If FreeNAS has chosen to do likewise there probably won't be anything useful you can copy. If there is a if_re.ko you can copy it might not even load with the pfSense kernel and even if it does it may cause havoc if the FreeNAS derived driver doesn't have the same idea as the pfSense kernel about the layout of shared data structures.

    OK, suppose it doesn't work and you decide to rebuild pfSense with your own device driver.  Where will you get the device driver that fixes the problem? Do you have the necessary skills and experience to backport a "more modern" driver from a later version of FreeBSD to FreeBSD 8.1? If not, are you prepared to put in many hours to acquire those skills? Are you expecting to get lots of "free" help? How many hours are you prepared to spend to says yourself the $10 to $70 a new NIC is likely to cost?



  • Thanks wallabybob

    In my plan I expectation to have 4 physics interface for Network card ( 1 Onboard and 3 PCIs) but now current version only recognized 3 PCIs NIC, so now quick solution is change to other board and waiting for next pfsense snaphots with hope.

    One more time thanks alot for your help.



  • @onhel:

    Strange, my NC9C has RTL8111E PCIe and both onboard NIC's are detected, re0 re1.

    onhel: Did you manage to use the NC9C with pfSense 2.0 working with the Re0 and Re1 ?  (8111E)
    (i know that these where PCIe board with chip on it)

    I'm planning of using a Shuttle XG41 with "Intel G41 Express+ ICH7 Chipset" and it has 2
    Realtek 8111E ports on the board and get a bit scared that I will end up with useless unit.
    I do not have any space to fit any additional NIC but must rely on the ones on the motherboard.

    Anyone else who have tested motherboards with Realtek 8111E network chipset  and PF2.0 ?

    Btw. Found this on BSD forum.
    http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/062886.html



  • @mrzaz:

    Btw. Found this on BSD forum.
    http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/062886.html

    That forum item suggests that, at worst, to run pfSense on your preferred motherboard it will be necessary to backport the current stable driver to FreeBSD 8.1. See my previous post for discussion of that challenge.

    There are other mainboards with two better supported (e.g. Intel) NICs.



  • @mrzaz:

    onhel: Did you manage to use the NC9C with pfSense 2.0 working with the Re0 and Re1 ?  (8111E)
    (i know that these where PCIe board with chip on it)

    Using 2.0 Release, and my Jetway's NC9C-550 onboard NICs have always worked.  I cant speak for other boards but judging from other users I've heard on this forum, the NC9C-550's 8111E works just fine with pfSense.



  • wallabybob:
    Thanks for the comment!

    The reason why I wanted the Shuttle XG41 was that it was a ready made and tested HW solution
    (MB, CPU, Cooling, Memory, good case …) as I am NOT looking for a Atom based MB.  I wanted a
    minimum Core 2 Duo CPU to get some decent power under the hood to handle both 100Mbit
    WAN connection and one or two IPSec with decent speed.

    The normal CPU score for most Atom based CPUs is between 300-700 and the box (CPU) I am looking at
    has a score on about 3600. (Core 2 Quad Q8400)  And that CPU is on the "verified" list on Shuttles
    homepage for that case.

    I have been looking at few different solutions (including a MB with Intel chipset) but it all ends up
    with a risky situation that all parts, when put together, maybe doesn't work well.  And then I have
    spent a lot of money for nothing.  The biggest concern is heat.  Getting a good Mini-ITX motherboard,
    CPU, Small formfactor case and enough cooling that will fit inside the case.

    And If I look at ready-made appliances with aprox. the same spec it costs 2-3 times the amount of money.

    Do you know in what timeframe that 8.2 will be included ? (1, 3, 6, 12 months ?)  just a rough estimate.

    I'm currently running the pfSense as a secondary solution right now in a VMWare for testing
    but would like to make it primary but would rather wait for pfSense to support the XG41 (8111E)
    with BSD 8.2 than to look for another HW solution. So it depends on how long that wait would be.

    onhel:
    Thanks for the info.



  • @mrzaz:

    Do you know in what timeframe that 8.2 will be included ? (1, 3, 6, 12 months ?)  just a rough estimate.

    When pressed for release dates the pfSense developers consistently say "When it is ready." Is that estimate rough enough?  :) The only discussion about next version of FreeBSD in pfSense I have seen suggests the jump will be to FreeBSD 9.x rather than FreeBSD 8.x

    If your VMWare solution works well enough I suggest you stick with that. If you really want to run without VMWare there could still be other options. I don't know the details of the XG41 but presume since you mention mini-ITX it has a mini-ITX board with an expansion slot. (But maybe the box doesn't provide for use of the expansion slot.) Is there an expansion slot you can use?



  • @wallabybob:

    @mrzaz:

    Do you know in what timeframe that 8.2 will be included ? (1, 3, 6, 12 months ?)  just a rough estimate.

    When pressed for release dates the pfSense developers consistently say "When it is ready." Is that estimate rough enough?  :) The only discussion about next version of FreeBSD in pfSense I have seen suggests the jump will be to FreeBSD 9.x rather than FreeBSD 8.x

    If your VMWare solution works well enough I suggest you stick with that. If you really want to run without VMWare there could still be other options. I don't know the details of the XG41 but presume since you mention mini-ITX it has a mini-ITX board with an expansion slot. (But maybe the box doesn't provide for use of the expansion slot.) Is there an expansion slot you can use?

    The board does have one PCIe but the case doesn't so that's a dead end. :-/

    I may start look around for other options as well. Found a few boards that looks OK
    with Intel LAN chipset like the MSI IM-Q35 or the new MSI IM-QM67.
    Or Supermicros X9SCV-Q or X9SCV-QV4. (based on the QM67 chipset)

    The size of the case that I'm looking  at is aprox like this:
    http://www.e-itx.com/mini-box-m350.html
    The main concern will be the heat and what cooling to use.
    Time will tell.

    Found some recommendations about cooling:
    http://www.cooljag.com/INTEL/Socket G1_PGA989/JACDD01C-1.html

    /Dan



  • @mrzaz:

    I may start look around for other options as well. Found a few boards that looks OK
    with Intel LAN chipset like the MSI IM-Q35 or the new MSI IM-QM67.
    Or Supermicros X9SCV-Q or X9SCV-QV4. (based on the QM67 chipset)

    I dont think the Intel 82579LM LAN ports are supported with pfSense 2.0 based on FreeBSD 8.1.



  • onhel:
    I checked the HWdoc for 8.1 and you right.  At least it is not mentioned there.
    The only one I found was the 82573,82574 supported by the em(4) driver.
    82567, 82579 and 82566 isn't.  :-/  Not even in 8.2

    There is a lot of references to Intel-cards that does not specify chipset though
    so it is hard to know if it will work or not.  Pure gamble.

    Then I'm really back to square one as these boards are really the only ones
    that I could see as alternatives that does not have 8111E chipset and
    is Mini-ITX size and is supporting Core2Duo or Core2Quad.

    Unless someone else has another tip of a board that would fit the above criteria.
    Maybe the only option is to gamble and try the XG41 and if it doesn't work,
    either put up a bounty or put it on the backburner until later BSD is included in PfS.



  • I can now confirm that the chipset in the Shuttle XG41 board reports as HWRev "0x2c000000" instead of the not working "0x2c800000".  ;D

    I had a discussion with people at Shuttle and they made a test of booting a XG41 with a FreeBSD 8.1 LiveCD
    and the chipset seems to work/load OK.  (see attached screenshot)

    I will buy the unit soon and make additional tests and can give some small feedback later.
    http://www.shuttle.eu/products/slim/xg41/overview/

    I will use the following spec initially:

    • Shuttle XG41
    • INTEL Core2Quad Q8400 2660MHz 4MB CPU (BX80580Q8400)   CPU-score: 3689  (Passmark CPUscore)
    • KINGSTON 4GB 1333MHz DDR3 Non-ECC CL9 DIMM (KVR1333D3N9/4G)
    • WESTERN DIGITAL HD AV-25/ 160GB SATA 3Gb/s 5400rpm 32MB (WD1600BUDT) (changed the SSD to HD)

    And will, when everything is up, add a WLAN b/g/n MiniPCI card and 2x cable/antennas.
    Any recommendations on this, anyone ?

    MiniPCIe bus and support for b/g/n spec.  Preferable both 2.4 and 5GHz and dual antenna connector.

    I have been looking into this board but not sure about the support in BSD.
    http://www.icd.se/index.php?main_page=product_info&products_id=1426

    Best regards
    Dan Lundqvist

    Ps. One good thing is that it has physical COM-ports as well for Console support and
    is shipped with tested CPU-cooling and a "verified" CPU and Memory list as well.
    It has space for 2.5" drive (not included) and a slim CD/DVD bay (not included).
    And also pre-made holes for 2 WiFi-antennas.

    UPDATE 2011-10-26:
    Machine has now arrived and installed. Installation of pfSense went without problem
    and all HW incl. the CPU/Memory/LAN-ports/SATA/USB/Serial is detected OK.
    The SMP with 4 cores is also working.

    UPDATE 2011-10-28:
    Added a bootlog from the Shuttle XG41.

    Some notes:
    cryptosoft0: <software crypto="">on motherboard</software>

    re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" pcie="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xfdeff000-0xfdefffff,0xfdef8000-0xfdefbfff irq 18 at device 0.0 on pci2
    re0: Using 1 MSI messages
    re0: Chip rev. 0x2c000000
    re0: MAC rev. 0x00000000
    .
    .
    rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus0
    rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
    re0: [FILTER]

    re1: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" pcie="" gigabit="" ethernet="">port 0xe800-0xe8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 19 at device 0.0 on pci3
    re1: Using 1 MSI messages
    re1: Chip rev. 0x2c000000
    re1: MAC rev. 0x00000000
    .
    .
    rgephy1: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus1
    rgephy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
    re1: [FILTER]

    And will try to do some performance measurements as well.



    ShuttleXG41_bootlog.txt</rtl8169s></realtek></rtl8169s></realtek>



  • New member here with a Jetway JNC9C-550-LF.  This unit also has two Realtek 8111E's onboard.  I have no issue running pfSense; both NIC's detected, perfectly usable, VLAN's and all.  I must note, I also have 're0: Chip rev. 0x2c000000' in my dmesg dump.  I did a test install of ESXi 5 for the hell of it, but reverted back to a straight pfSense install.  If your ESXi install is suiting you at the moment, stick with it, you have plenty of processing power at bay.  Anything "lost in translation" so to speak is minimal in your case.



  • I also faced with problem of onboard nic.. it is simply doesn`t work at pfsense 2.0. using dmesg i discovered that hardware revision of my Realtek 8111E newer then driver existed at system. Here you can find resolution: http://forums.freebsd.org/showthread.php?t=24362
    For now I am trying to compile official realtek driver at 8.2 freebsd.



  • @krylou:

    For now I am trying to compile official realtek driver at 8.2 freebsd.

    You should really be trying to compile the driver on FreeBSD 8.1 because that is the version of FreeBSD used in pfSense 2.0. This might turn out to be easy, it might turn out to be difficult. If you want to get something working quickly I suggest you would be better off purchasing another NIC to use instead of the Realtek device. If you already have one or more working expansion NICs you might be able to use a VLAN capable switch to get additional interfaces: search the forums for VLAN port multiplier to see some posts that discuss this.


  • Rebel Alliance Developer Netgate

    Since this topic still comes up in Google searches:

    You can use a 2.1 snapshot if you need to use this NIC.

    There are other forum threads that talk about compiling the driver and adding it yourself, but at this stage, using 2.1 is easier and preferably than manually hacking in a new driver.


Log in to reply