@rodluz said in Lenovo ThinkPad L14 Gen 5 - kernel panic:

@jflash Great! Did you use the default kernel from FOG after the update, or did you use the kernel from my repo?

I don’t try older kernel, just put new one 🙂

@jfernandz https://stackoverflow.com/questions/4713088/how-do-i-use-git-bisect

This is just very basic overview and probably unhelpful.

If you’re familiar with git, you can switch to different points in time (via the dev-branch) to figure out when we last knew things were good. So first, I’d suggest trying to find exactly when that would’ve been.

I’d likely start, using dev-branch as the primary “tester case”

git checkout -b dev-branch

If you haven’t already done so of course.

Then I’d put the branch at the same level as when we pushed out 1.5.10:

git checkout 081d1f4

Run your install and see if things worked, if they do:

git checkout dev-branch git bisect start git bisect bad git bisect good 081d1f4

Of course the 081d1f4 is the hash of the commit where things were good: this might or might not be the 1.5.10 release, so your mileage may very and may need some more adjustment.

You can find these hashes on https://github.com/FOGProject/fogproject/commits/dev-branch/?after=f7fd3a7a3f188b4540f089a7f38c4d368b53376c+174 using the different pages at the bottom to find a point in time, and they show the hashes on the right and side of each commit.

It will iterate through things and you just mark after each install/test what worked (as good or bad) by testing:

If it still fails, you’d run git bisect bad, if it succeeds, you would run git bisect good each iteration.

It’s tedious I know. but it will help us find the exact point things broke and hopefully from what (maybe it’s something we did, maybe something within ipxe, but gives us a starting point to test things out.)

Thanks

Hello All! (Especially Wilsol)

I used the top configuration ideas from Wilsol, and before I could get through the entire list, darned thing started working. (yeah probably secure boot, thanks Tom for pointing us in the right direction)

Thanks to everyone for the assist.

-Jim

@Tom-Elliott Yes correct, if its not to do with R8169, then I am unsure what is going on.

@Tom-Elliott is there a way to find out where its failing

i have the PCAP file if interested?

@Faurel ok good that looks like a clean dhcp process. It would be helpful to have the pcap file in my hand, but you want to expand the OFFER packet. The OFFER packet you can tell from the Info column.

In the packet you may need to expand the dhcp section. You should see the image similar to below. What is important is the next server IP address should point to IP address of your fog server. and boot file name should be ipxe.efi. You see in this example that the boot file name was not given, this is the error with this packet. The next server and boot file are in the ethernet header. This is the legacy bootp pxe section.

The next place you need to check is the dhcp options below. You should see dhcp options 66 which should be the IP address of the fog server and dhcp 67 should be the boot file name of ipxe.efi. In this picture this packet is also in error since the dhcp server is not sending out all of the pxe booting info. So if your offer packet looks like this you have a problem.

Screenshot from 2025-05-07 17-14-20.png

@rodluz

ok scrap the local GPO done this and it works

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v firstlogon /t REG_SZ /d powershell -noexit -ep bypass c:\users\admin\sysprep\firstlogon.ps1 /f

@pilipp_edv I had a very similar issue to this a while back but it was with an HP laptop. It turned out to be a hardware defect. I was able to get the motherboard replaced under warranty, so maybe you can too for this laptop.

@george1421 thanks for continuing to provide such detailed information.

I believe the best way to learn is to do, so i am going to go shopping for an SSD (and perhaps some RAM to be safe). Once I have everything in place, I am going to do a test run on our machines as well as those of an associate just to see what happens when the network changes. Following this, I will check back with you if you don’t mind to go through the results.

@alterak said in FOG operation in different network segments:

is there a possibility of automatic separation of locations,

I’m not sure I fully understand the question, but if you are asking can it automatically pick which location to select based on the IP address of the computer being registered. The quick answer is no, FOG doesn’t currently have that capabilities.

The bit longer answer is it could if you can be a little creative and can do a little linux bash script programming. In a nutshell, you can customize the bash script that is setup for full registration of computers. The basics of what needs to be done is covered in this tutorial: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

The IP address bit can come from this script: https://forums.fogproject.org/post/69725 This post is for getting the IP address to be used in a FOG postdownload script. But the concept will be the same for the fog.man.reg script.

@JeremyL Hi, yes I am sure I have run Fog under Proxmox as well successfully but this time it didn’t want to work. Anyway once I switched to using Fog running under a Container, it uses much fewer resources and runs just as well.
So I would recommend switching to running it under a container when possible.

@ingemedia We just released new experimental kernel/initrd. I included the r8126 drivers. I don’t have any devices to test with so would you be willing to test it and let me know?

@Ced58 I use this model. It’s best to get either the official Lenovo usb c ethernet adapter or the proprietary Lenovo adapter for the special ethernet port on these. Also in the bios there’s a Mac pass through option that you want to set to internal or second Mac address. With the latest version of fog and kernel it should see that internal mac even if you share an adapter for imaging multiple of that device.

@rodluz

Alright it works thank you.

@Itay1787 I just pushed a change to the dev-branch. Please try installing it again from there and let me know how it goes.

That would definitely be useful.

@alterak If you know how to program linux bash scripts this is possible. You will need to edit a script called fog.man.reg that is in FOS Linux (the OS that runs on the target computer to capture/deploy images). I have a tutorial on modifying that program to set a default hostname. But the concepts you need to do what you ware are listed here: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

I found out what’s causing the problem. The HP BIOS somehow configured the hard disk as a RAID by default. Removing the RAID, and the machine will boot to Windows after iPXE instead of looping.
Thank you for your input.

This tutorial will give you a good general overview. https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Since you are talking XP, then you are also meaning bios firmware. For bios you can use a utility called memdisk.

https://forums.fogproject.org/post/142041 step #18. The memdisk program is only supported under a bios based computer. If you have uefi there is a different process. There are some limitations with bios mode, your iso file MUST be less than 2GB, this is a limitation of a 32 bit bios.

Hi mwestaph,

I am also new here but I believe I can take a crack at your image.
Snapins I feel are great, they automatically install after your machine is imaged. The other tool you would want to consider here are the “Groups” feature. While this isn’t a traditional group where new hosts inherit group settings, its a good way to apply settings on mass.

Here is my basic setup:
I have 2 images and 6 groups. I then onboard all of the client machines / hosts and assign them to the appropriate group. In the group setup, I then choose the correct image and snapins for that group. This applies these settings to all associated hosts (ie. All current hosts that are associated with this groups now have the same settings.)
The only downside currently is if you need to assign a new host machine to this group, you need to re-apply the image and snapin settings for the group to apply it appropriately to this machine.

Let me know if this helps and if there is anyone more experienced out there feel free to tell me if I am wrong.