Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Intel i354 support in 2.1

    Scheduled Pinned Locked Moved Hardware
    25 Posts 9 Posters 12.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Aluminum
      last edited by

      @demco:

      Anyone know if i354 works with pfsense 2.1? This ethernet controller is built into the Avoton/Rangeley CPU.

      It uses the same intel igb driver that i350 does even though it has a marvell PHY, but its very new. Probably still only bleeding edge 10, wasn't in 9.x release last I looked. 8.x? forgetaboutit.

      1 Reply Last reply Reply Quote 0
      • D
        diablo266
        last edited by

        Is it possible to compile the modules for pfsense from source like on a normal freebsd/linux system or is it more complex for some reason?

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          There are no build tools in pfSense so you have build the modules in an equivalent FreeBSD system and transfer them. For pfSense 2.1 you need FreeBSD 8.3 for which source code may or may not be available.

          Steve

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            @stephenw10:

            There are no build tools in pfSense so you have build the modules in an equivalent FreeBSD system and transfer them. For pfSense 2.1 you need FreeBSD 8.3 for which source code may or may not be available.

            Steve

            Seriously, Stevenw10?

            http://svn0.freebsd.org
            http://svnweb.freebsd.org/base/release/8.3.0/

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by

              Assuming you want the i354 support for the new Rangely/Avocet platforms..

              • No, it's not in 2.1 (8.3)

              • Yes, we're working on it.

              • Support was added to FreeBSD 10 for these 5 weeks ago

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                @gonzopancho:

                Seriously, Stevenw10?

                Ah. I could have worded that better!  ;)
                Obviously the source for FreeBSD 8.3, including all the drivers, is available. What I meant was that if you want a newer driver version that supports more hardware it may not exist as code that can be compiled against 8.3. Unless it has been backported it may be only available for 9 or 10.

                Sorry if I mislead anyone.

                Steve

                1 Reply Last reply Reply Quote 0
                • P
                  peersu
                  last edited by

                  Looking forward to the update… I just bought the SuperMicro Rangeley 1U kit, and would love to get pfSense working on it :)

                  1 Reply Last reply Reply Quote 0
                  • J
                    jasonlitka
                    last edited by

                    @peersu:

                    Looking forward to the update… I just bought the SuperMicro Rangeley 1U kit, and would love to get pfSense working on it :)

                    In the interim you could install vSphere on it and create a VM.

                    http://www.servethehome.com/how-to-intel-i354-avoton-rangeley-adapter-vmware-esxi-5-5/

                    I can break anything.

                    1 Reply Last reply Reply Quote 0
                    • P
                      peersu
                      last edited by

                      Ah, that is exactly what I will do…thank you for the suggestion.

                      One other thing I never had to deal with until I bought this barebones kit... it seems overly difficult to find SODIMM DDR3 w/ ECC from a vendor 'in stock'.

                      Any suggestions for this new board? The compatible memory modules listed by SuperMicro turn up nothing.  Alternatively,  I found one DIMM from Amazon of:

                      Kingston Technology ValueRAM 8GB 1333MHz DDR3L ECC CL9 SODIMM 1.35V Notebook Memory KVR13LSE9/8

                      ... which I bought because it's all I could find from a vendor that has a return policy I trust.  I'd much prefer two sticks of  DDR3-1600 if I can find it.

                      1 Reply Last reply Reply Quote 0
                      • J
                        jasonlitka
                        last edited by

                        @peersu:

                        Ah, that is exactly what I will do…thank you for the suggestion.

                        One other thing I never had to deal with until I bought this barebones kit... it seems overly difficult to find SODIMM DDR3 w/ ECC from a vendor 'in stock'.

                        Any suggestions for this new board? The compatible memory modules listed by SuperMicro turn up nothing.  Alternatively,  I found one DIMM from Amazon of:

                        Kingston Technology ValueRAM 8GB 1333MHz DDR3L ECC CL9 SODIMM 1.35V Notebook Memory KVR13LSE9/8

                        ... which I bought because it's all I could find from a vendor that has a return policy I trust.  I'd much prefer two sticks of  DDR3-1600 if I can find it.

                        Kingston:
                        http://shop.kingston.com/partsinfo.aspx?ktcpartno=KVR16LSE11/8 - Due 11/25/2013
                        http://shop.kingston.com/partsinfo.aspx?ktcpartno=KVR13LSE9/8 - In Stock

                        Crucial (not sure if they have real-time inventory):
                        http://www.crucial.com/store/partspecs.aspx?IMODULE=CT102472BF1339

                        I can break anything.

                        1 Reply Last reply Reply Quote 0
                        • D
                          demco
                          last edited by

                          @peersu:

                          Looking forward to the update… I just bought the SuperMicro Rangeley 1U kit, and would love to get pfSense working on it :)

                          Did you test if pfSense will boot on the machine? Will usb, sata and other peripherals be recognized? Since this is a complete new SoC.

                          1 Reply Last reply Reply Quote 0
                          • P
                            peersu
                            last edited by

                            Nope… I'm installing ESXi first, and then pfSense... at least until it's supported; not going to waste so much time trying to get /maybe/ one thing to work, for another to break, etc.

                            1 Reply Last reply Reply Quote 0
                            • ?
                              Guest
                              last edited by

                              Looking forward to the update… I just bought the SuperMicro Rangeley 1U kit, and would love to get pfSense working on it

                              This is the same Supermicro hardware (maybe your ram and disk are different).

                              I wouldn't say the port is complete by any stretch (for example, the QuickAssist part isn't working), but there are results 8) :

                              enjoy!  :D

                              KDB: debugger backends: ddb      1                                                 
                              KDB: current backend: ddb
                              Copyright © 1992-2012 The FreeBSD Project.
                              Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
                              The Regents of the University of California. All rights reserved.
                              FreeBSD is a registered trademark of The FreeBSD Foundation.
                              FreeBSD 8.3-RELEASE-p12 #0: Thu Dec  5 16:03:14 EST 2013
                                  root@rebrand-dedicated-<redacted>-8.3-amd64.builders.pfsense.org:/usr/obj.<also-redacted>/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
                              Timecounter "i8254" frequency 1193182 Hz quality 0
                              CPU: Genuine Intel(R) CPU        @ 2.40GHz (2400.10-MHz K8-class CPU)
                                Origin = "GenuineIntel"  Id = 0x406d8  Family = 6  Model = 4d  Stepping = 8
                                Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x43d8e3bf<sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,movbe,popcnt,tscdlt,aesni,<b30>>
                                AMD Features=0x28100800 <syscall,nx,rdtscp,lm>AMD Features2=0x101 <lahf,prefetch>TSC: P-state invariant
                              real memory  = 8589934592 (8192 MB)
                              avail memory = 8203595776 (7823 MB)
                              ACPI APIC Table: <intel  tiano ="">FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
                              FreeBSD/SMP: 1 package(s) x 8 core(s)
                              cpu0 (BSP): APIC ID:  0
                              cpu1 (AP): APIC ID:  2
                              cpu2 (AP): APIC ID:  4
                              cpu3 (AP): APIC ID:  6
                              cpu4 (AP): APIC ID:  8
                              cpu5 (AP): APIC ID: 10
                              cpu6 (AP): APIC ID: 12
                              cpu7 (AP): APIC ID: 14
                              ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20101013/tbfadt-392)
                              ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20101013/tbfadt-707)
                              ioapic0 <version 2.0="">irqs 0-23 on motherboard
                              wlan: mac acl policy registered
                              ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                              ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff804aa8d0, 0) error 1
                              ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                              ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff804aa970, 0) error 1
                              ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                              ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff804aaa10, 0) error 1
                              kbd1 at kbdmux0
                              cryptosoft0: <software crypto="">on motherboard
                              padlock0: No ACE support.
                              acpi0: <alaska a="" m="" i="">on motherboard
                              acpi0: [ITHREAD]
                              acpi0: Power Button (fixed)
                              Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
                              acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
                              cpu0: <acpi cpu="">on acpi0
                              cpu1: <acpi cpu="">on acpi0
                              cpu2: <acpi cpu="">on acpi0
                              cpu3: <acpi cpu="">on acpi0
                              cpu4: <acpi cpu="">on acpi0
                              cpu5: <acpi cpu="">on acpi0
                              cpu6: <acpi cpu="">on acpi0
                              cpu7: <acpi cpu="">on acpi0
                              pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
                              pci0: <acpi pci="" bus="">on pcib0
                              pcib1: <acpi pci-pci="" bridge="">mem 0xdf2e0000-0xdf2fffff irq 16 at device 1.0 on pci0
                              pci1: <acpi pci="" bus="">on pcib1
                              pcib2: <acpi pci-pci="" bridge="">at device 0.0 on pci1
                              pci2: <acpi pci="" bus="">on pcib2
                              vgapci0: <vga-compatible display="">port 0xd000-0xd07f mem 0xde000000-0xdeffffff,0xdf000000-0xdf01ffff irq 16 at device 0.0 on pci2
                              pcib3: <acpi pci-pci="" bridge="">mem 0xdf2c0000-0xdf2dffff irq 16 at device 2.0 on pci0
                              pci3: <acpi pci="" bus="">on pcib3
                              pci3: <serial bus,="" usb="">at device 0.0 (no driver attached)
                              pcib4: <acpi pci-pci="" bridge="">mem 0xdf2a0000-0xdf2bffff irq 20 at device 3.0 on pci0
                              pci4: <acpi pci="" bus="">on pcib4
                              pci0: <processor>at device 11.0 (no driver attached)
                              pci0: <base peripheral=""> at device 15.0 (no driver attached)
                              pci0: <base peripheral=""> at device 19.0 (no driver attached)
                              igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0="">port 0xe0c0-0xe0df mem 0xdf260000-0xdf27ffff,0xdf30c000-0xdf30ffff irq 20 at device 20.0 on pci0
                              igb0: Using MSIX interrupts with 9 vectors
                              igb0: [ITHREAD]
                              igb0: Bound queue 0 to cpu 0
                              igb0: [ITHREAD]
                              igb0: Bound queue 1 to cpu 1
                              igb0: [ITHREAD]
                              igb0: Bound queue 2 to cpu 2
                              igb0: [ITHREAD]
                              igb0: Bound queue 3 to cpu 3
                              igb0: [ITHREAD]
                              igb0: Bound queue 4 to cpu 4
                              igb0: [ITHREAD]
                              igb0: Bound queue 5 to cpu 5
                              igb0: [ITHREAD]
                              igb0: Bound queue 6 to cpu 6
                              igb0: [ITHREAD]
                              igb0: Bound queue 7 to cpu 7
                              igb0: [ITHREAD]
                              igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0="">port 0xe0a0-0xe0bf mem 0xdf240000-0xdf25ffff,0xdf308000-0xdf30bfff irq 21 at device 20.1 on pci0
                              igb1: Using MSIX interrupts with 9 vectors
                              igb1: [ITHREAD]
                              igb1: Bound queue 0 to cpu 0
                              igb1: [ITHREAD]
                              igb1: Bound queue 1 to cpu 1
                              igb1: [ITHREAD]
                              igb1: Bound queue 2 to cpu 2
                              igb1: [ITHREAD]
                              igb1: Bound queue 3 to cpu 3
                              igb1: [ITHREAD]
                              igb1: Bound queue 4 to cpu 4
                              igb1: [ITHREAD]
                              igb1: Bound queue 5 to cpu 5
                              igb1: [ITHREAD]
                              igb1: Bound queue 6 to cpu 6
                              igb1: [ITHREAD]
                              igb1: Bound queue 7 to cpu 7
                              igb1: [ITHREAD]
                              igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0="">port 0xe080-0xe09f mem 0xdf220000-0xdf23ffff,0xdf304000-0xdf307fff irq 22 at device 20.2 on pci0
                              igb2: Using MSIX interrupts with 9 vectors
                              igb2: [ITHREAD]
                              igb2: Bound queue 0 to cpu 0
                              igb2: [ITHREAD]
                              igb2: Bound queue 1 to cpu 1
                              igb2: [ITHREAD]
                              igb2: Bound queue 2 to cpu 2
                              igb2: [ITHREAD]
                              igb2: Bound queue 3 to cpu 3
                              igb2: [ITHREAD]
                              igb2: Bound queue 4 to cpu 4
                              igb2: [ITHREAD]
                              igb2: Bound queue 5 to cpu 5
                              igb2: [ITHREAD]
                              igb2: Bound queue 6 to cpu 6
                              igb2: [ITHREAD]
                              igb2: Bound queue 7 to cpu 7
                              igb2: [ITHREAD]
                              igb3: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.4.0="">port 0xe060-0xe07f mem 0xdf200000-0xdf21ffff,0xdf300000-0xdf303fff irq 23 at device 20.3 on pci0
                              igb3: Using MSIX interrupts with 9 vectors
                              igb3: [ITHREAD]
                              igb3: Bound queue 0 to cpu 0
                              igb3: [ITHREAD]
                              igb3: Bound queue 1 to cpu 1
                              igb3: [ITHREAD]
                              igb3: Bound queue 2 to cpu 2
                              igb3: [ITHREAD]
                              igb3: Bound queue 3 to cpu 3
                              igb3: [ITHREAD]
                              igb3: Bound queue 4 to cpu 4
                              igb3: [ITHREAD]
                              igb3: Bound queue 5 to cpu 5
                              igb3: [ITHREAD]
                              igb3: Bound queue 6 to cpu 6
                              igb3: [ITHREAD]
                              igb3: Bound queue 7 to cpu 7
                              igb3: [ITHREAD]
                              ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xdf317000-0xdf3173ff irq 23 at device 22.0 on pci0
                              ehci0: [ITHREAD]
                              usbus0: EHCI version 1.0
                              usbus0: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0
                              ahci0: <ahci sata="" controller="">port 0xe150-0xe157,0xe140-0xe143,0xe130-0xe137,0xe120-0xe123,0xe040-0xe05f mem 0xdf316000-0xdf3167ff irq 19 at device 23.0 on pci0
                              ahci0: [ITHREAD]
                              ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported
                              ahcich0: <ahci channel="">at channel 0 on ahci0
                              ahcich0: [ITHREAD]
                              ahcich1: <ahci channel="">at channel 1 on ahci0
                              ahcich1: [ITHREAD]
                              ahcich2: <ahci channel="">at channel 2 on ahci0
                              ahcich2: [ITHREAD]
                              ahcich3: <ahci channel="">at channel 3 on ahci0
                              ahcich3: [ITHREAD]
                              ahci1: <ahci sata="" controller="">port 0xe110-0xe117,0xe100-0xe103,0xe0f0-0xe0f7,0xe0e0-0xe0e3,0xe020-0xe03f mem 0xdf315000-0xdf3157ff irq 19 at device 24.0 on pci0
                              ahci1: [ITHREAD]
                              ahci1: AHCI v1.30 with 2 6Gbps ports, Port Multiplier not supported
                              ahcich4: <ahci channel="">at channel 0 on ahci1
                              ahcich4: [ITHREAD]
                              ahcich5: <ahci channel="">at channel 1 on ahci1
                              ahcich5: [ITHREAD]
                              isab0: <pci-isa bridge="">at device 31.0 on pci0
                              isa0: <isa bus="">on isab0
                              pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
                              acpi_hpet0: <high precision="" event="" timer="">on acpi0
                              device_attach: acpi_hpet0 attach returned 12
                              atrtc0: <at realtime="" clock="">port 0x70-0x77 irq 8 on acpi0
                              atrtc0: Warning: Couldn't map I/O.
                              uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
                              uart0: [FILTER]
                              uart0: console (115200,n,8,1)
                              uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
                              uart1: [FILTER]
                              orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff on isa0
                              sc0: <system console="">at flags 0x100 on isa0
                              sc0: CGA <16 virtual consoles, flags=0x300>
                              vga0: <generic isa="" vga="">at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0
                              atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
                              atkbd0: <at keyboard="">irq 1 on atkbdc0
                              kbd0 at atkbd0
                              atkbd: unable to get the current command byte value.
                              atkbd0: [GIANT-LOCKED]
                              atkbd0: [ITHREAD]
                              psm0: unable to get the current command byte value.
                              ppc0: cannot reserve I/O port range
                              est0: <enhanced speedstep="" frequency="" control="">on cpu0
                              p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
                              est1: <enhanced speedstep="" frequency="" control="">on cpu1
                              p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
                              est2: <enhanced speedstep="" frequency="" control="">on cpu2
                              p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
                              est3: <enhanced speedstep="" frequency="" control="">on cpu3
                              p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
                              est4: <enhanced speedstep="" frequency="" control="">on cpu4
                              p4tcc4: <cpu frequency="" thermal="" control="">on cpu4
                              est5: <enhanced speedstep="" frequency="" control="">on cpu5
                              p4tcc5: <cpu frequency="" thermal="" control="">on cpu5
                              est6: <enhanced speedstep="" frequency="" control="">on cpu6
                              p4tcc6: <cpu frequency="" thermal="" control="">on cpu6
                              est7: <enhanced speedstep="" frequency="" control="">on cpu7
                              p4tcc7: <cpu frequency="" thermal="" control="">on cpu7
                              Timecounters tick every 1.000 msec
                              IPsec: Initialized Security Association Processing.
                              usbus0: 480Mbps High Speed USB v2.0
                              ugen0.1: <intel>at usbus0
                              uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
                              uhub0: 8 ports with 8 removable, self powered
                              ugen0.2: <vendor 0x8087="">at usbus0
                              uhub1: <vendor 2="" 9="" 0x8087="" product="" 0x07db,="" class="" 0,="" rev="" 2.00="" 0.02,="" addr="">on usbus0
                              uhub1: 4 ports with 4 removable, self powered
                              ugen0.3: <avocent>at usbus0
                              ukbd0: <ep1 interrupt="">on usbus0
                              kbd2 at ukbd0
                              ums0: <ep2 interrupt="">on usbus0
                              ums0: 5 buttons and [XYZ] coordinates ID=1
                              ugen0.4: <vendor 0x0000="">at usbus0
                              uhub2: <vendor 4="" 9="" 0x0000="" product="" 0x0001,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
                              uhub2: 4 ports with 3 removable, self powered
                              ugen0.5: <vendor 0x0557="">at usbus0
                              ukbd1: <vendor 0="" 5="" 0x0557="" product="" 0x2419,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus0
                              kbd3 at ukbd1
                              ums1: <vendor 0="" 5="" 0x0557="" product="" 0x2419,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus0
                              ums1: 3 buttons and [Z] coordinates ID=0
                              ada0 at ahcich4 bus 0 scbus4 target 0 lun 0
                              ada0: <intel ssdsc2bb080g4="" d2010355="">ATA-8 SATA 3.x device
                              ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
                              ada0: Command Queueing enabled
                              ada0: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
                              SMP: AP CPU #7 Launched!
                              SMP: AP CPU #3 Launched!
                              SMP: AP CPU #1 Launched!
                              SMP: AP CPU #6 Launched!
                              SMP: AP CPU #5 Launched!
                              SMP: AP CPU #2 Launched!
                              SMP: AP CPU #4 Launched!
                              Trying to mount root from ufs:/dev/ada0s1a
                              Configuring crash dumps…
                              Using /dev/ada0s1b for dump device.
                              Mounting filesystems...
                              ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
                                          Consider tuning vm.kmem_size and vm.kmem_size_max
                                          in /boot/loader.conf.
                              ZFS filesystem version 5
                              ZFS storage pool version 28

                              ___
                              / f
                              / p _                              / Sense
                              _                              / 
                                  _                              _/

                              Welcome to pfSense 2.1p1-RELEASE  ...

                              No core dumps found.
                              Creating symlinks......done.
                              External config loader 1.0 is now starting...
                              Launching the init system... done.
                              Initializing............................. done.
                              Starting device manager (devd)...done.
                              Loading configuration......done.
                              Updating configuration...done.
                              Cleaning backup cache............done.
                              Setting up extended sysctls...done.
                              Setting timezone...done.
                              Configuring loopback interface...done.
                              Starting syslog...done.
                              Starting Secure Shell Services...done.
                              Setting up polling defaults...done.
                              Setting up interfaces microcode...done.
                              Configuring loopback interface...done.
                              Creating wireless clone interfaces...done.
                              Configuring LAGG interfaces...done.
                              Configuring VLAN interfaces...done.
                              Configuring QinQ interfaces...done.
                              Configuring WAN interface...done.
                              Configuring LAN interface...done.
                              Configuring OPT1 interface...done.
                              Syncing OpenVPN settings...done.
                              Configuring firewall......done.
                              Starting PFLOG...done.
                              Setting up gateway monitors...done.
                              Synchronizing user settings...done.
                              Starting webConfigurator...done.
                              Configuring CRON...done.
                              Starting DNS forwarder...done.
                              Starting NTP time client...done.
                              Configuring firewall......done.
                              Generating RRD graphs...done.
                              Starting syslog...done.
                              Starting CRON... done.
                              Bootup complete

                              FreeBSD/amd64 (pfSense.localdomain) (console)

                              *** Welcome to pfSense 2.1p1-RELEASE-pfSense (amd64) on pfSense ***

                              WAN (wan)      -> igb0      -> v4: 10.0.1.10/24
                              LAN (lan)      -> igb1      -> v4: 192.168.1.65/24
                              OPT1 (opt1)    -> igb2      -> v4: 172.27.44.45/24

                              1. Logout (SSH only)                  8) Shell
                              2. Assign Interfaces                  9) pfTop
                              3. Set interface(s) IP address      10) Filter Logs
                              4. Reset webConfigurator password    11) Restart webConfigurator
                              5. Reset to factory defaults        12) pfSense Developer Shell
                              6. Reboot system                    13) Upgrade from console
                              7. Halt system                      14) Enable Secure Shell (sshd)
                              8. Ping host                        15) Restore recent configuration

                              Enter an option:</intel></vendor></vendor></vendor></vendor></vendor></ep2></ep1></avocent></vendor></vendor></intel></intel></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></isa></at></high></serial></isa></pci-isa></ahci></ahci></ahci></ahci></ahci></ahci></ahci></ahci></ehci></ehci></intel(r)></intel(r)></intel(r)></intel(r)></processor></acpi></acpi></serial></acpi></acpi></vga-compatible></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></alaska></software></version></intel ></lahf,prefetch></syscall,nx,rdtscp,lm></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,movbe,popcnt,tscdlt,aesni,<b30></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe></also-redacted></redacted>

                              1 Reply Last reply Reply Quote 0
                              • J
                                jasonlitka
                                last edited by

                                Does the 2.4.0 driver you're using fix the mbuf allocation issue in the current one?

                                I can break anything.

                                1 Reply Last reply Reply Quote 0
                                • ?
                                  Guest
                                  last edited by

                                  I'll just quote myself:

                                  "I wouldn't say the port is complete by any stretch (for example, the QuickAssist part isn't working), but there are results."

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    piotrasd
                                    last edited by

                                    hi, where we can get this build ?? for i354  ???

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      peersu
                                      last edited by

                                      You have to go the VM route with ESX or some other to have supported drivers.  Not in current pfSense build, and I don't think generally available anywhere I can find.

                                      1 Reply Last reply Reply Quote 0
                                      • ?
                                        Guest
                                        last edited by

                                        @peersu:

                                        You have to go the VM route with ESX or some other to have supported drivers.  Not in current pfSense build, and I don't think generally available anywhere I can find.

                                        Well, not in a build you have, but still coming.

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          piotrasd
                                          last edited by

                                          Hi
                                          someone could confirm me if exist any build of pfsense with support Intel i354 ??

                                          I want order mainboard Supermicro A1SAi-2750F special for pfSense.
                                          There is possibility build pfSense on FreeBSD 10 ? just for get driver working ?

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            There is no public build that will support it currently. As far as I know only the bleeding edge pre-alpha builds of 2.2 (built on FreeBSD 10) will support it and they are not available for good reason, they are not functional in many areas as of the last report.
                                            It's not possible to to just build ontop of FreeBSD 10 either, all the current development effort is to get this working.

                                            That said it's not necessary to use the complete FreeBSD code base to get drivers. If the newer igb driver, with i354 support, becomes available as a backport it would be possible to load it under 2.1.

                                            Steve

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.