• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Pyrol
    3. Topics
    P
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 5
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by Pyrol

    • P

      PXE-E18: Server response timeout

      FOG Problems
      • • • Pyrol
      3
      0
      Votes
      3
      Posts
      1.8k
      Views

      S

      @Pyrol said in PXE-E18: Server response timeout:

      I reinstalled FOG and PFSense and it’s still the same.

      You are using pfSense as DHCP server. Please share the settings you have in there (picture) as well as the information requested by George.

    • P

      Shutdown host after deploy, change BIOS time?

      FOG Problems
      • • • Pyrol
      3
      0
      Votes
      3
      Posts
      310
      Views

      george1421G

      now with that said linux has a command hwclock that can set the hardware clock to local time. That command does exist in FOS Linux, but it appears to have a dependency that is not met. The other missing command is ntpdate to set the FOS Linux clock to some ntp server on your network.

      So in theory we can get to where you need with a little black magic.

      ref: https://docs.fedoraproject.org/en-US/Fedora/26/html/System_Administrators_Guide/sect4-synchronizing-date-time-hwclock.html

    • P

      FOG Kernel update: "Preparing to move to tftp server"

      FOG Problems
      • • • Pyrol
      7
      0
      Votes
      7
      Posts
      1.6k
      Views

      george1421G

      @Pyrol said in FOG Kernel update: "Preparing to move to tftp server":

      and the final step was to go into WebGui>fog settings>tftp server
      and here changed bzImage to bzImage.64 the same with bzImage32

      I would back up to this step. Replace the existing bzImage with the .64 bit one keeping it bzImage and the 32 bit image should be named bzImage32 (watch your case because it is important). Leave everything else FOG defaults. It will save you headaches in the future. Then pxe boot the client once you are on 5.6.18 it will see the network adapter.

      Then we can look back to why the update process is not working as it should. What version of FOG are you running?

    • 1 / 1