@westcustom I had this issue with some of my HP workstations. I had to change the DHCP bootfile setting from ipxe.efi to snp.efi and that fixed it.
Posts made by rodluz
-
RE: HP Probook 440 G11 iPXE initialising devices
-
RE: Windows on ARM
@stokehall @george1421 I have the 6.11 kernel booting, however I am unable to get the keyboard and networking working. It seems like this keyboard issue is also affecting Linux distributions trying to build for the X1 SOCs like Ubuntu.
I have not been able to test anything on the init (imaging, registering, etc) because of the networking and keyboard issue. Also, Buildroot has not updated their linux headers to include 6.11 so I can build the new init needed. -
RE: Windows on ARM
@stokehall Thank you for the update. I didn’t think Ubuntu was going to start using kernel 6.11 for their 24.10 release, but it seems like they are, so I’ll take a look over the weekend.
-
RE: Windows on ARM
@george1421 I’m getting an X Plus, X1P-64-100 (10 cores up to 3.4GHz, NPU integrated). I’ll be getting an X Elite probably a few weeks later but from my understanding, they are the same generation.
-
RE: Windows on ARM
I will be getting a snapdragon laptop on Monday for FOG/FOS testing.
It looks like kernel 6.11 will most likely be released Sunday but there already is a release candidate that I could build to test with.@Tom-Elliott Implemented some changes to support ARM by default on the 1.6-alpha branch of FOG.
I am currently porting it over to the 1.5 dev-branch -
RE: Problem Capturing right Host Primary Disk with INTEL VROC RAID1
@george1421 Let me know how that goes. I remember that I had to patch something on buildroot for partclone and ncurses. A new patch may be needed if they made changes for 2024.05.1.
I can give it a try as well.Are you trying to build the newest version of partclone?
-
RE: Does Fog work with Proxmox?
@Cire3 FOG 100% works in Proxmox. My FOG install runs on my Proxmox server without any issues.
How is your storage pool for your images setup? -
RE: Cannot find disk on system (get harddisk) - Dell Latitude 3140
@Kureebow Kernel version 6.1.63 is the one with changes for UFS. You can try updating the kernel on its own first.
-
RE: Can't upload Arch Image
@VegaFlash I just published the new inits that include a newer version of e2fsck.
If you have the newest version of FOG installed from the dev-branch1.5.10.18
, you should be able to update it easily through the settings page.
If your FOG server isn’t on the newest dev-branch release, either update it or follow the next steps.
- SSH into your FOG server
cd /var/www/fog/service/ipxe
mv init.xz init_original.xz
#Not necessary but recommended so you can revert if there are any issueswget https://github.com/FOGProject/fos/releases/download/EXP_20240430/init.xz
chmod 644 init.xz
chown fogproject:www-data init.xz
-
RE: Can't upload Arch Image
@Tom-Elliott I am working on newer inits with the updated
e2fsck
package to resolve this issue.@VegaFlash I will update you when the new inits are available, for you to try it out.
-
RE: The version fogproject-1.5.10 is unable to download the kernel.
@mrowand I just tried installing 1.5.10 on a fresh Rocky 8.9 VM. It went through and downloaded everything correctly.
Try running these commands on the server to see if you can manually download the files.curl -kOL https://github.com/FOGProject/fos/releases/latest/download/bzImage curl -kOL https://github.com/FOGProject/fos/releases/latest/download/bzImage32 curl -kOL https://github.com/FOGProject/fos/releases/latest/download/init.xz curl -kOL https://github.com/FOGProject/fos/releases/latest/download/init_32.xz curl -kOL https://github.com/FOGProject/fog-client/releases/download/0.13.0/FOGService.msi curl -kOL https://github.com/FOGProject/fog-client/releases/download/0.13.0/SmartInstaller.exe
Let us know if this works.
Edit by Tom to ensure urls were accurate for fos files
-
RE: The version fogproject-1.5.10 is unable to download the kernel.
@JackYwn You did not provide enough information on how/when you are getting this error.
I am assuming that the message you posted is from the installation script, meaning that it errors when trying to download the kernel during an install. If that is the case, please try re-running the installer using the newest dev-branch version, 1.5.10.17. -
RE: Pulling Reports for Host Motherboards
@iljared98 There is a way. The CSV will contain more information than just the
Motherboard Product Name
, but that is easy to clean.
On FOG, go to theReports
tab and selectInventory Report
from the left side menu. Don’t change anything there, just click onSearch
. Download the CSV from the page using the excel sheet icon. When you open the CSV, columnR
should bembproductname
which is what you are looking for. -
RE: "Not shrinking (/dev/nvme0n1p1) as it is detected as fixed size
@sami-blackkite What filesystem are you using on your device?
-
RE: Microsoft 365 install / update via snapin pack
@pauleb I use this powershell script for my M365 snappin. Hope it helps you.
$username = "DOMAIN\USERNAME" $password = ConvertTo-SecureString "PASSWORD" -AsPlainText -Force $creds = New-Object System.Management.Automation.PSCredential $username, $password New-PSDrive -Persist -Name "Z" -PSProvider FileSystem -Root "\\SHARE\AppRepo" -Credential $creds Start-Process -Wait -FilePath "Z:\Microsoft\Microsoft365_x64\setup.exe" -ArgumentList '/configure "Z:\Microsoft\Microsoft365_x64\configuration.xml"' -NoNewWindow Remove-PSDrive -Name "Z"
-
RE: Invalid Token.dat with Deep Freeze
@PCF24 Here is a quick and dirty script to reset all your hosts.
I tested it with two hosts and it is working for me. I don’t want to reset all my hosts.You will have to paste your FOG server IP, FOG user api token, and FOG settings api token to the script.
You will also need to installjq
in your FOG server.
Debian base:sudo apt install jq
. RHEL based:sudo dnf install jq
#!/bin/bash server_ip="http://10.10.10.10" fog_user_token="PASTE_YOUR_USER_API_TOKEN_HERE" fog_api_token="PASTE_YOUR_FOG_SETTINGS_API_TOKEN_HERE" all_hosts=$(curl -S -s -X GET -H 'content-type: application/json' -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" $server_ip/fog/host/ | jq '.hosts[]') all_ids=$(echo "$all_hosts" | jq '.id') all_ids=${all_ids//\"/} for host_id in $all_ids do curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"pub_key":""}' $server_ip/fog/host/$host_id/edit curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_tok":""}' $server_ip/fog/host/$host_id/edit curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_time":"0000-00-00 00:00:00"}' $server_ip/fog/host/$host_id/edit done
-
RE: Client hangs at EFI stub:
@sgilbe Okay, I did some changes and reuploaded
dist_virt_1
&dist_virt_2
. Can you try them again? -
RE: Client hangs at EFI stub:
@sgilbe I uploaded two more kernels with virtualization enabled (
dist_virt_1
&dist_virt_2
). Let me know if this works for you.
https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n -
RE: Client hangs at EFI stub:
@SaturTP That’s an interesting find, I’ll check why this would be the problem.
@sgilbe If disabling virtualization makes it work for you too, I’ll add one more kernel to the drive share for you to try. -
RE: Client hangs at EFI stub:
@sgilbe Hi, sorry for the delay.
I have 3 new kernels to try. I hope one of these works for you https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n?usp=drive_linkIf any one of these works, please let me know which one so I can document it.