• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Wolfbane8653
    3. Posts
    W
    • Profile
    • Following 2
    • Followers 3
    • Topics 29
    • Posts 572
    • Best 19
    • Controversial 0
    • Groups 1

    Posts made by Wolfbane8653

    • Basics for WinPE PXE boot using fog

      Re: Using FOG to PXE boot into your favorite installer images

      Please Add “Paragon Hard Disk Manager” to your list this should work with any WinPE

      Configuration currently works for UEFI only. It appears the wim file is missing bootmgr.exe for the BIOS booting systems

      It is highly recommended to use this on a machine that has 4GB+ RAM.

      First we’ll create the required directories:

      mkdir -p /var/www/fog/Tools/{iso folder name}
      chmod -R 777 /var/www/fog/Tools/{iso folder name}
      

      Now we’ll mount the WinPE iso over the loop directory. Then we’ll copy the contents of the DVD to the directory we built above.

      mkdir -p /mnt/loop
      mount -o loop /{full path where you have the iso stored}/{iso file} /mnt/loop
      

      We are going to copy to /var/www/fog/Tools so we can use the http protocal already setup for fog management.

      cp /mnt/loop/bootmgr /var/www/fog/Tools/{iso folder name}
      cp /mnt/loop/boot/bcd /var/www/fog/Tools/{iso folder name}
      cp /mnt/loop/boot/boot.sdi /var/www/fog/Tools/{iso folder name}
      cp /mnt/loop/sources/boot.wim /var/www/fog/Tools/{iso folder name}
      cp /mnt/loop/efi /var/www/fog/Tools/{iso folder name}
      
      umount /mnt/loop
      

      Download and install the latest wimboot kernel and extract it from the zip file.

      • https://github.com/ipxe/wimboot/blob/master/wimboot
        The issue was discussed in this post: https://forums.fogproject.org/post/144293
        We will use tftp protocal for this file in the fog menu.
      cd /tmp
      wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip
      unzip wimboot-latest.zip
      

      Copy the wimboot file from the archive directory to root of the os directory (we’ll need this for every windows boot media, so we’ll place it in a common spot).

      mkdir -p /tftpboot/os
      cp ./wimboot-2.6.0-signed/wimboot /tftpboot/os
      chmod -R 777 tftpboot/os
      

      The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS.
      In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry
      Set the following fields

      Menu Item: os.{iso file name}
      Description: {iso file you would like to boot from}
      Parameters:
      set tftp-path tftp://${fog-ip}
      set http-path http://${fog-ip}/fog/Tools/HD_Manager
      kernel ${tftp-path}/os/wimboot gui
      imgfetch --name bootmgr ${http-path}/bootmgr bootmgr
      imgfetch --name bootx64.efi ${http-path}/efi/boot/en_us/bootx64.efi bootx64.efi
      imgfetch --name BCD ${http-path}/bcd BCD
      imgfetch --name boot.sdi ${http-path}/boot.sdi boot.sdi
      imgfetch --name boot.wim ${http-path}/boot.wim boot.wim
      boot || goto MENU
      

      That’s it, just pxe boot your target system and pick os.{iso file name} from the FOG iPXE boot menu.

      posted in Tutorials
      W
      Wolfbane8653
    • RE: Fog & Windows 11

      I can also atest to this. Windows 11 is not having any issue with my Dell Latitude 7440 2-in-1’s. Select “Windows 10” as your OS and you should be just fine…for now 🤛

      posted in Windows Problems
      W
      Wolfbane8653
    • RE: Dell Latitude 7420 w/ USB-C network adapter

      @george1421 worked like a charm when switching to REFIND.

      posted in Hardware Compatibility
      W
      Wolfbane8653
    • RE: Dell Latitude 7420 w/ USB-C network adapter

      @george1421 Cool I’ll switch to that after my image is done uploading.

      @developers Still the Esc key is used to access the menu instead of my web gui set key of F12.

      posted in Hardware Compatibility
      W
      Wolfbane8653
    • RE: Dell Latitude 7420 w/ USB-C network adapter

      Updated to Kernel 5.15.34 AMD/Intel 64 Bit.
      Updated BIOS to 1.17.2

      Access menu key is set to Esc but it is set to F12 in fog gui.

      @george1421 this is a bug.

      posted in Hardware Compatibility
      W
      Wolfbane8653
    • RE: lenovo thinkcentre failed to boot windows if first boot option is network boot

      Change your Boot Exit settings in the fog web GUI to GRUB. If that is your current setting change to SANBOOT.

      posted in Hardware Compatibility
      W
      Wolfbane8653
    • Dell Latitude 7420 w/ USB-C network adapter

      Good morning all,

      It’s been a very long time. Fog has been running smoothly for years for me and I haven’t really had an issue… till now.

      Got a new shipment of Dell Latitude 7420’s and they don’t have a eth jack on the main board and I want to keep the UEFI enabled. This is different from my other configuration of disabling UEFI set AHCI on and use the undionly.kpxe boot file.

      Here is what I had to do to get to where I’m getting my Chainloading issue:

      • FOG VERSION: 1.5.9.154

      • Dell Latitude 7420
        –BISO Version 1.162

      • Bios Setup

      1. Boot configuration – > Turn Off Secure Boot
      2. Integrated Devices --> USB/Thunderbolt Configuration --> Enable External USB Ports
      3. Integrated Devices --> USB/Thunderbolt Configuration --> Enable USB Boot Support
      4. Integrated Devices --> Enable Thunderbolt Boot Support --> On
      5. Integrated Devices --> Enable Thunderbolt (and PCIe behind TBT) pre-boot modules --> On
      6. Connection Enable UEFI Network Stack --> On
      7. Pre-boot Behavior -->Fastboot Thorough

      **These settings are recommended by Dell: https://www.dell.com/support/kbdoc/en-ca/000131551/bios-settings-to-allow-pxe-boot-on-newer-model-dell-latitude-laptops

      • DCHP server Scope Options
      1. 066: <fog server ip address>
      2. 067: ipxe.efi
      • USB-C to eth adapter Spec’ed for Dell Latitude 7000 series

      And here is my problem. IPXE shows that link is up and has and ip addresss when I request one from DHCP.

      It gets to the prompting of my F12 hot key to to (access the menu)

      Any suggestions?

      half20220711_085947.jpg

      posted in Hardware Compatibility
      W
      Wolfbane8653
    • RE: Proper way to install client on Linux hosts

      I find that installing the client on the deployed image saves the most time. Unless you do not want to image the current machines. If you do not want to image them you can just install the client and when you are ready to image those machines make sure the client is on the deployed image.

      posted in Linux Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      Current Solution set Kernel to 4.19.64 and set global option in Fog Configuration–> FOG Settings --> General Settings --> Kernel ARGS to tsc=unstable

      Luckly this is the last year for these machines.

      posted in FOG Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      So I’m guessing I’m going to need to edit all 100 of my units to have this argument? Or are you working on having a new bzImage for me to test?

      posted in FOG Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      @Quazz

      • tsc=unstable – works with Kernel 4.19.64
      • clocksource=hpet – works with Kernel 4.19.64

      So both of these commands work!

      @george1421 – bzImageNoACPI creates a kernal panic. IDE is turned on in the BIOS. I do not use the RAID function for these machines.
      8db818e6-c69c-48eb-b6dc-307b5f989e36-image.png

      posted in FOG Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      BIOS updated to v1.35 (Latest)
      Kernal 4.19.64 still does not work.

      Custom Kernal still does not work
      32de5071-ae8c-4d5e-8605-b933e9487a51-image.png

      posted in FOG Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      @Quazz –

      HP Compaq dc7800p Small Form Factor
      Intel® Core™2 Duo CPU E6750 @ 2.66GHz
      6GB RAM
      160 GB HDD – WDC WD1600AAJS-00B4A0

      BIOS Version786F1 v01.04
      Motherboard 0AA8h

      posted in FOG Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      Kernal 4.17.0 64 – does not work.

      • Kernal 4.19.64 with acpi=off
        49df2ac0-baf5-4aa8-9c3c-99374a3a1a54-image.png
      posted in FOG Problems
      W
      Wolfbane8653
    • RE: rcu_sched self detected stall on CPU when Deploying

      FYI 4.16.6 64 – works

      • Reset Kernals back to v4.19.64
      • Deleted host from Fog database
      • Manual registration
      • Set Host Kernel Arguments with acpi=off
      • Set to Deploy
      • Kernal panic
        d59d6733-31fb-4df5-9ce3-1bd9da3c4cb8-image.png
      posted in FOG Problems
      W
      Wolfbane8653
    • rcu_sched self detected stall on CPU when Deploying

      Fog v1.5.4
      Kernal 4.19.64
      Device: HP DC7800 (YES OLD!)

      When deploying image “rcu_sched self detected stall on CPU when” is displayed an some cpu statics are shown. I figured bad motherboard or cpu so I replaced the entire board and still the same issue occurred. Tried 3 other machines of the same model and no luck. rcu_sched self detected stall on CPU when capture gave me the info I needed but this apparently has not been fixed.

      Is this due to a conflict with the age of the hardware and the new kernal updates?

      This does not effect my other hardware at all they all imaged perfectly with Kernal 4.19.64. Only dc7800’s are the issue.

      FYI:
      Kernal 4.19.64 64 – not working
      Kernal 4.19.48 64 – not working
      Kernal 4.19.36 64 – not working
      Kernal 4.19.6 64 – need to test
      Kernal 4.19.1 64 – need to test
      …
      Kernal 4.17.0 64 – not working
      Kernal 4.16.6 64 – works
      Kernal 4.15.2 64 – works

      HP Compaq dc7800p Small Form Factor
      Intel® Core™2 Duo CPU E6750 @ 2.66GHz
      6GB RAM
      160 GB HDD – WDC WD1600AAJS-00B4A0

      BIOS Version786F1 v01.04 v01.35
      Motherboard 0AA8h

      2019-10-14_10-05-49.png

      posted in FOG Problems
      W
      Wolfbane8653
    • RE: Fog Web GUI Login Problem

      Confirm this plz…

      mysql -u fog -p fog
      

      Then type in the password. Do you get…

      ERROR 1045 (28000): Access denied for user 'fog'@'localhost' (using password: YES)
      

      Just had a small hickup in svn 5680. Had to do the following…

      mysql> create user 'fog'@'localhost' identified by 'your password here';
      Query OK, 0 rows affected (0.00 sec)
      
      mysql> GRANT ALL PRIVILEGES ON * . * TO 'fog'@'localhost';
      Query OK, 0 rows affected (0.00 sec)
      
      mysql> FLUSH PRIVILEGES;
      
      posted in FOG Problems
      W
      Wolfbane8653
    • RE: DNS Name Goes to Old FOG Installation

      Did you create an A Record pointer on your DNS Server to point FOG-SERVER to IP xxx.xxx.xxx.xxx.?

      posted in FOG Problems
      W
      Wolfbane8653
    • Typo In Groups

      0_1464806492893_Capture.PNG

      “System Cerial” sooo yummy!

      Duh.

      posted in Bug Reports
      W
      Wolfbane8653
    • RE: Disable Client Auto-update

      @Jbob nicely done making it 100% isolated.

      @Wayne-Workman I stuck with the old client this past year as Joe was still pushing the development of the new client. I’m interested in using the new client. Try not to strike things down so quickly.

      When working in a school and pulling out 30+ laptops in a classroom you want to cut down as much as you can on the wifi traffic. As our current setup can easily accommodate the 6MB download per laptop, it just seems like it’s wasted. Is there any possible way only have a select clients not update?

      posted in Feature Request
      W
      Wolfbane8653
    • 1 / 1