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

    2.0 Install - License + Error message

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    5 Posts 2 Posters 4.3k 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.
    • P
      pf123user
      last edited by

      A few questions:

      First is an "error 11" which is memory size. I'm not sure if this is an issue or not - or what causes this, etc. (this is why I recently asked about memory limitations of pfsense, etc.). Is there a way I can fix this? Seems as though no matter what RAM config I use this error comes up - is this just an error related to actual/physical memory vs. available memory?

      From bootup log:
      RTC BIOS diagnostic error 11 <memory_size>Second this isn't an error but is there any way to change the time counters down to 0.001 msec? Or anything faster than 1.000 msec? Even if this results in crazy CPU usage or needs large amounts of memory, etc. I'm willing to accept that tradeoff so that I could use it for testing purposes either on a dedicated test box or to change lower than 1msec for testing then back to 1msec for normal operations.

      From bootup log:
      Timecounters tick every 1.000 msec

      Third is the license issue below. I've never changed the config files - how does one go about doing this? Is this just an acknowledgement of Intel's open-source license, etc. that pfsense uses? Should I worry about this? There is an error message in there - I assume this is because I haven't agreed with the license.

      From bootup log:
      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, 0xffffffff80470e30, 0) error 1
      wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
      wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/l
      oader.conf.
      module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806548f0, 0) error 1
      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 /bo
      ot/loader.conf.
      module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80470cf0, 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 /b
      oot/loader.conf.
      module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80470d90, 0) error 1
      kbd1 at kbdmux0

      Whole bootup log:

      ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD?
      3                                        3
      3                                        3
      3                                        3
      3          Welcome to pfSense!            3
      3                                        3                ______
      3                                        3                /     
      3  1. Boot pfSense [default]              3          /    f 
      3  2. Boot pfSense with ACPI disabled    3        /    \        /
      3  3. Boot pfSense using USB device      3        /  p  _
      /  Sense
      3  4. Boot pfSense in Safe Mode          3        \      /     
      3  5. Boot pfSense in single user mode    3        _____/       
      3  6. Boot pfSense with verbose logging  3              \        /
      3  7. Escape to loader prompt            3                ______/
      3  8. Reboot                              3
      3                                        3
      3                                        3
      3                                        3
      3  Select option, [Enter] for default    3
      3  or [Space] to pause timer  0          3
      @DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDY

      KDB: debugger backends: ddb
      KDB: current backend: ddb
      Copyright © 1992-2010 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.1-RELEASE-p4 #0: Tue Sep 13 17:04:54 EDT 2011
          root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj./usr/pfSensesr
      c/src/sys/pfSense_SMP.8 amd64
      Timecounter "i8254" frequency 1193182 Hz quality 0
      CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3191.87-MHz K8-class CPU)
        Origin = "GenuineIntel"  Id = 0xf64  Family = f  Model = 6  Stepping = 4
        Features=0xbfebfbff<fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br>MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
        Features2=0xe43d <sse3,dtes64,mon,ds_cpl,vmx,cnxt-id,cx16,xtpr,pdcm>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant
      real memory  = 8589934592 (8192 MB)
      avail memory = 8261218304 (7878 MB)
      ACPI APIC Table: <dell  b8k =""  ="">FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
      FreeBSD/SMP: 2 package(s) x 2 core(s) x 2 HTT threads
      cpu0 (BSP): APIC ID:  0
      cpu1 (AP/HT): APIC ID:  1
      cpu2 (AP): APIC ID:  2
      cpu3 (AP/HT): APIC ID:  3
      cpu4 (AP): APIC ID:  4
      cpu5 (AP/HT): APIC ID:  5
      cpu6 (AP): APIC ID:  6
      cpu7 (AP/HT): APIC ID:  7
      ioapic0: Changing APIC ID to 8
      ioapic1: Changing APIC ID to 9
      ioapic0 <version 2.0="">irqs 0-23 on motherboard
      ioapic1 <version 2.0="">irqs 24-47 on motherboard
      netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling
      wlan: mac acl policy registered
      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, 0xffffffff80470e30, 0) error 1
      wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
      wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/l
      oader.conf.
      module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806548f0, 0) error 1
      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 /bo
      ot/loader.conf.
      module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80470cf0, 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 /b
      oot/loader.conf.
      module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80470d90, 0) error 1
      kbd1 at kbdmux0
      cryptosoft0: <software crypto="">on motherboard
      padlock0: No ACE support.
      acpi0: <dell b8k =""  ="">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 0x808-0x80b 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
      acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
      Timecounter "HPET" frequency 14318180 Hz quality 900
      acpi_button0: <power button="">on acpi0
      acpi_button0: enable wake failed
      pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
      pci0: <acpi pci="" bus="">on pcib0
      pcib1: <acpi pci-pci="" bridge="">at device 2.0 on pci0
      pci1: <acpi pci="" bus="">on pcib1
      pcib2: <acpi pci-pci="" bridge="">irq 16 at device 0.0 on pci1
      pci2: <acpi pci="" bus="">on pcib2
      pcib3: <acpi pci-pci="" bridge="">irq 16 at device 0.0 on pci2
      pci3: <acpi pci="" bus="">on pcib3
      em0: <intel(r) 1000="" pro="" network="" connection="" 7.2.3="">port 0xdcc0-0xdcdf mem 0xfcd80
      000-0xfcd9ffff,0xfcda0000-0xfcdbffff irq 16 at device 0.0 on pci3
      em0: Using an MSI interrupt
      em0: [FILTER]
      em1: <intel(r) 1000="" pro="" network="" connection="" 7.2.3="">port 0xdce0-0xdcff mem 0xfcdc0
      000-0xfcddffff,0xfcde0000-0xfcdfffff irq 17 at device 0.1 on pci3
      em1: Using an MSI interrupt
      em1: [FILTER]
      pcib4: <pci-pci bridge="">irq 16 at device 1.0 on pci2
      pci4: <pci bus="">on pcib4
      pcib5: <acpi pci-pci="" bridge="">at device 0.3 on pci1
      pci5: <acpi pci="" bus="">on pcib5
      pcib6: <pci-pci bridge="">at device 6.0 on pci5
      pci6: <pci bus="">on pcib6
      em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xcc00-0xcc3f mem
      0xfcc80000-0xfcc9ffff irq 30 at device 4.0 on pci6
      em2: [FILTER]
      em3: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xcc40-0xcc7f mem
      0xfcca0000-0xfccbffff irq 31 at device 4.1 on pci6
      em3: [FILTER]
      em4: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xcc80-0xccbf mem
      0xfccc0000-0xfccdffff irq 32 at device 6.0 on pci6
      em4: [FILTER]
      em5: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xccc0-0xccff mem
      0xfcce0000-0xfccfffff irq 33 at device 6.1 on pci6
      em5: [FILTER]
      pcib7: <acpi pci-pci="" bridge="">at device 3.0 on pci0
      pci7: <acpi pci="" bus="">on pcib7
      pcib8: <pci-pci bridge="">at device 0.0 on pci7
      pci8: <pci bus="">on pcib8
      pcib9: <pci-pci bridge="">at device 0.0 on pci8
      pci9: <pci bus="">on pcib9
      em6: <intel(r) 1000="" pro="" network="" connection="" 7.2.3="">port 0xbcc0-0xbcdf mem 0xfc980
      000-0xfc99ffff,0xfc9a0000-0xfc9bffff irq 16 at device 0.0 on pci9
      em6: Using an MSI interrupt
      em6: [FILTER]
      em7: <intel(r) 1000="" pro="" network="" connection="" 7.2.3="">port 0xbce0-0xbcff mem 0xfc9c0
      000-0xfc9dffff,0xfc9e0000-0xfc9fffff irq 17 at device 0.1 on pci9
      em7: Using an MSI interrupt
      em7: [FILTER]
      pcib10: <pci-pci bridge="">at device 1.0 on pci8
      pci10: <pci bus="">on pcib10
      em8: <intel(r) 1000="" pro="" network="" connection="" 7.2.3="">port 0xacc0-0xacdf mem 0xfc780
      000-0xfc79ffff,0xfc7a0000-0xfc7bffff irq 17 at device 0.0 on pci10
      em8: Using an MSI interrupt
      em8: [FILTER]
      em9: <intel(r) 1000="" pro="" network="" connection="" 7.2.3="">port 0xace0-0xacff mem 0xfc7c0
      000-0xfc7dffff,0xfc7e0000-0xfc7fffff irq 18 at device 0.1 on pci10
      em9: Using an MSI interrupt
      em9: [FILTER]
      pcib11: <acpi pci-pci="" bridge="">at device 4.0 on pci0
      pci11: <acpi pci="" bus="">on pcib11
      pcib12: <acpi pci-pci="" bridge="">at device 5.0 on pci0
      pci12: <acpi pci="" bus="">on pcib12
      pcib13: <acpi pci-pci="" bridge="">at device 6.0 on pci0
      pci13: <acpi pci="" bus="">on pcib13
      pcib14: <acpi pci-pci="" bridge="">at device 7.0 on pci0
      pci14: <acpi pci="" bus="">on pcib14
      pcib15: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
      pci15: <acpi pci="" bus="">on pcib15
      pcib16: <acpi pci-pci="" bridge="">at device 30.0 on pci0
      pci16: <acpi pci="" bus="">on pcib16
      ath0: <atheros 5212="">mem 0xfc5f0000-0xfc5fffff irq 18 at device 2.0 on pci16
      ath0: [ITHREAD]
      ath0: AR5212 mac 5.9 RF5112 phy 4.3
      isab0: <pci-isa bridge="">at device 31.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <intel 63xxesb2="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,
      0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0
      ata0: <ata 0="" channel="">on atapci0
      ata0: [ITHREAD]
      atapci1: <intel 63xxesb2="" sata300="" controller="">port 0xfe00-0xfe07,0xfe10-0xfe13,0x
      fe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfedf mem 0xff970000-0xff9703ff irq 20 at devi
      ce 31.2 on pci0
      atapci1: [ITHREAD]
      atapci1: AHCI called from vendor specific driver
      atapci1: AHCI v1.10 controller with 6 3Gbps ports, PM not supported
      ata2: <ata 0="" channel="">on atapci1
      ata2: [ITHREAD]
      ata3: <ata 1="" channel="">on atapci1
      ata3: [ITHREAD]
      ata4: <ata 2="" channel="">on atapci1
      ata4: [ITHREAD]
      ata5: <ata 3="" channel="">on atapci1
      ata5: [ITHREAD]
      ata6: <ata 4="" channel="">on atapci1
      ata6: [ITHREAD]
      pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
      atrtc0: <at realtime="" clock="">port 0x70-0x7f irq 8 on acpi0
      ppc0: <parallel port="">port 0x378-0x37f,0x778-0x77f irq 7 on acpi0
      ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
      ppc0: FIFO with 16/16/8 bytes threshold
      ppc0: [ITHREAD]
      ppbus0: <parallel port="" bus="">on ppc0
      plip0: <plip network="" interface="">on ppbus0
      plip0: [ITHREAD]
      lpt0: <printer>on ppbus0
      lpt0: [ITHREAD]
      lpt0: Interrupt-driven port
      ppi0: <parallel i="" o="">on ppbus0
      uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
      uart0: [FILTER]
      uart0: console (9600,n,8,1)
      orm0: <isa option="" roms="">at iomem 0xc0000-0xc1fff,0xc2000-0xc47ff,0xc4800-0xc7fff
      on isa0
      atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
      atkbd0: <at keyboard="">irq 1 on atkbdc0
      kbd0 at atkbd0
      atkbd0: [GIANT-LOCKED]
      atkbd0: [ITHREAD]
      p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
      p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
      p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
      p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
      p4tcc4: <cpu frequency="" thermal="" control="">on cpu4
      p4tcc5: <cpu frequency="" thermal="" control="">on cpu5
      p4tcc6: <cpu frequency="" thermal="" control="">on cpu6
      p4tcc7: <cpu frequency="" thermal="" control="">on cpu7
      RTC BIOS diagnostic error 11 <memory_size>Timecounters tick every 1.000 msec
      IPsec: Initialized Security Association Processing.
      ad4: 35304MB <wdc wd360gd-00fla2="" 31.08f31="">at ata2-master UDMA100 SATA 1.5Gb/s
      ad6: 35304MB <wdc wd360gd-00fla2="" 31.08f31="">at ata3-master UDMA100 SATA 1.5Gb/s
      SMP: AP CPU #1 Launched!
      SMP: AP CPU #5 Launched!
      SMP: AP CPU #3 Launched!
      SMP: AP CPU #4 Launched!
      SMP: AP CPU #2 Launched!
      SMP: AP CPU #6 Launched!
      SMP: AP CPU #7 Launched!
      GEOM_MIRROR: Device mirror/pfSenseMirror launched (2/2).
      Trying to mount root from ufs:/dev/mirror/pfSenseMirrors1a
      Configuring crash dumps…
      Using /dev/mirror/pfSenseMirrors1b for dump device.
      Mounting filesystems...

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

      Welcome to pfSense 2.0-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.
      Starting Secure Shell Services...done.
      Setting up polling defaults...done.
      Setting up interfaces microcode...done.
      Configuring LAGG interfaces...done.
      Configuring VLAN interfaces...done.
      Configuring QinQ interfaces...done.
      Configuring WAN interface...done.
      Configuring LAN interface...done.
      Configuring WIFI interface...done.
      Configuring HW_LAN interface...done.
      Configuring OPT3 interface...done.
      Configuring OPT4 interface...done.
      Configuring OPT5 interface...done.
      Configuring OPT6 interface...done.
      Configuring OPT7 interface...done.
      Configuring OPT8 interface...done.
      Configuring OPT9 interface...done.
      Syncing OpenVPN settings...done.
      Starting syslog...done.
      Configuring firewall......done.
      Starting PFLOG...done.
      Setting up gateway monitors...done.
      Synchronizing user settings...done.
      Starting webConfigurator...done.
      Configuring CRON...done.
      Starting DHCP service...done.
      Starting DNS forwarder...done.
      Configuring firewall......done.
      Starting OpenNTP time client...done.
      Generating RRD graphs...done.
      Starting CRON... done.
      Bootup complete

      FreeBSD/amd64 (pfSense.wcm.net) (ttyu0)

      login: admin
      Password:
      *** Welcome to pfSense 2.0-RELEASE-pfSense (amd64) on pfSense ***

      WAN (wan)                -> em0        -> 123.456.789.000
        LAN (lan)                -> em1        -> 123.456.789.000
        WIFI (opt1)              -> ath0_wlan1 -> 123.456.789.000
        LAN2 (opt2)            -> em2        -> 123.456.789.000
        OPT3 (opt3)              -> em3        -> NONE
        OPT4 (opt4)              -> em4        -> NONE
        OPT5 (opt5)              -> em5        -> NONE
        OPT6 (opt6)              -> em6        -> NONE
        OPT7 (opt7)              -> em7        -> NONE
        OPT8 (opt8)              -> em8        -> NONE
        OPT9 (opt9)              -> em9        -> NONE

      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

      Enter an option:</wdc></wdc></memory_size></cpu></cpu></cpu></cpu></cpu></cpu></cpu></cpu></at></keyboard></isa></parallel></printer></plip></parallel></parallel></at></serial></ata></ata></ata></ata></ata></intel></ata></intel></isa></pci-isa></atheros></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></intel(r)></intel(r)></pci></pci-pci></intel(r)></intel(r)></pci></pci-pci></pci></pci-pci></acpi></acpi></intel(r)></intel(r)></intel(r)></intel(r)></pci></pci-pci></acpi></acpi></pci></pci-pci></intel(r)></intel(r)></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></power></high></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></dell></software></version></version></dell ></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,vmx,cnxt-id,cx16,xtpr,pdcm></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br></memory_size>

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        @pf2.0nyc:

        First is an "error 11" which is memory size. I'm not sure if this is an issue or not - or what causes this, etc. (this is why I recently asked about memory limitations of pfsense, etc.). Is there a way I can fix this? Seems as though no matter what RAM config I use this error comes up - is this just an error related to actual/physical memory vs. available memory?

        From bootup log:
        RTC BIOS diagnostic error 11

        That'd be from your BIOS… probably safe to ignore, but if you can find a BIOS update, it wouldn't hurt to run it.

        @pf2.0nyc:

        Second this isn't an error but is there any way to change the time counters down to 0.001 msec? Or anything faster than 1.000 msec? Even if this results in crazy CPU usage or needs large amounts of memory, etc. I'm willing to accept that tradeoff so that I could use it for testing purposes either on a dedicated test box or to change lower than 1msec for testing then back to 1msec for normal operations.

        From bootup log:
        Timecounters tick every 1.000 msec

        Might be able to tinker with kern.hz

        @pf2.0nyc:

        Third is the license issue below. I've never changed the config files - how does one go about doing this? Is this just an acknowledgement of Intel's open-source license, etc. that pfsense uses? Should I worry about this? There is an error message in there - I assume this is because I haven't agreed with the license.

        Unless you have an Intel wireless card, those are safe to ignore.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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

          Might be able to tinker with kern.hz

          I assume this means that I'm going to have to learn how to play with/manipulate config files?

          Unless you have an Intel wireless card, those are safe to ignore.

          The wireless card is a Cisco AIR-PI21AG-A-K9 Cisco 802.11G PCI Wireless Adapter 2.4 - I don't know if that uses an Intel chipset but I haven't had any issues - should I ignore this error?

          Thx Jim for the reply.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            Search the doc wiki and forum, several places mention how to adjust kern.hz

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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

              Also, i'm on the latest BIOS update for that mobo and the RAM is totally fine (Dell RAM, Dell mobo, Dell latest BIOS). I don't get errors when I boot any other OS on that system???

              I'm wondering if I should be worried about a possible failure coming up on one of the memory slots (since swapping out the memory produced same result) - or if possible there is something else wrong.

              or should I just ignore?

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