Posts made by x23piracy

Hi,

i have FOG 1.5.0 running on an ESX Host and a Storage Node on a bare metal machine.
Works like a charm since years.

Best Regards X23

No idea anyone?

Quickreg Pending MAC Filter doesn’t seem to ignore MAC Addresses starting with 54 when i delete the host, restart the FOG Client i can see that the pending client still want to add a mac starting with 54:

The Most strange thing is that it tried the VPN Client MAC as primary while it’s not connected, i would expect the Cable NIC which is also connected while the FOG client reports the client to the FOG’s Webif.

I need to finally ban MAC from interest from FOG that are starting with 54, how can i do that?

Best Regards X23

Hi,

i have an repeated issue wirth the mac adress of a virtual vpn network adapter, it seems that the alternation of that mac isn’t working from time to time or fog is collecting the mac before it’s alternated.

if this happens i try to search for the mac directly on the db and correct the error if found but this happens again and again, therefore i tried to add this mac to the ignore list:

For some reason that doesnt seem to work, maybe i missunderstood the option itself.
How can i tell FOG to ignore any MAC starting with 54?

Additional how can i remove a specific mac address from db from all hosts where it occours?

Normally i goto the infected client and get me the mac addresslist with:

getmac

Then i search for that:

mac SELECT hmHostID FROM hostMAC where hmMAC IN ('54:4B:2D:5B:69:02');

With the found host-id i open the fog webif and look for the client:

In most of the cases i just delete it and try of the fog client is not claiming about duplicate mac entrys anymore, but i want to get rid of the problem.

Best Regards X23

@sebastian-roth Hi Sebastian i was able to fix my issue with compiling my own and latest ipxe.efi binary: https://forums.fogproject.org/post/145594

I had this Problem for months and also with Lenovo P15 devices, now with the new ipxe.efi i don’t need to use a dock anymore to deploy them, before i had connect the devices nics twice, onboard and the one from the usb-c dock because while booting tftp it uses the internal and since it drops into FOS it used the one from the Dock.

But this is an old story now

I am still using FOG 1.5.0, it works fine for us even with the new Windows 11 seems to be really similar to Windows 10 Imaging, even my nice tricks for sysprepping Win 10 also work for Win 11 thanks Microsoft

Is reading the SLIC from Bios still in the current releases of FOG? I have a nice customisation from Tom running in my current installation:

Best Regards X23

@george1421 just a moment ago i successfully compiled my own ipxe.efi binary and it works fine https://forums.fogproject.org/post/141618

@nate-baker said in Lenovo E15 Gen2 won't PXE boot (bzImage):

For anyone else coming across this thread, we had the same problem. The iPXE from the latest version of FOG (1.5.9) did not work, but building the latest iPXE binaries using the instructions on this post worked fine:

https://forums.fogproject.org/post/141618

After that, the Linux kernel we were using also worked fine.

Hi @Nate-Baker can you share the kernel please?

Best Regards X23

@francois said in Fujitsu A3510 PXE UEFI Boot:

@sebastian-roth I had a similar issue with Fujitsu Q7010, your advice about building latest iPXE binaries fixed mine. Now it boots just fine, thank you !

Hi, is it possible that you share that kernel?

Best Regards X23

Hi,

this seems to be a kernel issue, i cannot get any E15 to work without the dock connected twice with a network cable. The internal nic isn’t working after PXE boot, if it’s trying to boot in to FOS it won’t work until you connect the USB-C Dock with a network cable too.

I was trying several kernel’s since months but nothing. Any idea howto fix it?

Best Regards X23

@george1421 hi george i am currently not on site (home office) i can try this when i am back in the office.

Best Regards X23

@sebastian-roth yes i am still on 1.5.0, i tried to update to the latest but update repository problems kicked my ass.

Best Regards X23

@george1421 we have a supernet at work 172.19.100.0/22 (100.0/24, 101.0/24, 102.0/24 & 103.024) the two fog servers are reachable under the following ip addresses (172.19.102.17 (fog), 172.19.102.18 (fog-image) storage node. All other clients do well with current ipxe.efi (fog 1.5.0).

when i change back from snponly.efi to ipxe.efi all my other devices work well as before.

When i deploy the E15 devices with their dock it works fine, the dock nic seems to be propperly detected, the bad thing is if the device goes into windows it doesnt know the docks nic driver the first time but the internal nic is working, so we put the network cable after deployment into internal nic so fog client can do his job (rename, ad-join etc.) another solution (workaround) would be to deploy the device with both nics connected to the network.

Best Regards X23

@george1421 @sebastian-roth said in Lenovo E15 Gen2 won't PXE boot (bzImage):

snponly.efi

Hi,

i tried it but anyway same error like before.

Best Regards X23

@george1421 can i temporary use snponly.efi for this specific host instead of change it for all? but how to, i think i need to specify a filter in dhcp for this specific device?

For the first test i can change for all temporary but later on if that works i need to integrate this.
Can you give me a hint?

@george1421 I’ll try and report.

@sebastian-roth @george1421

Secure Boot is disabled else you won’t get to this point (picture) am i wrong?

@george1421 said in Lenovo E15 Gen2 won't PXE boot (bzImage):

@x23piracy Here is 5.6.18RT3 which has the updated realtek drivers in them. https://drive.google.com/file/d/1O-4tvx4DywWef75qfSxLRK9M6CoDS9pd/view?usp=sharing See how well these work with that nic.

Good morning George, unfortenately the error sticks, the kernel you provided doesn’t make the device able to pxe boot, same error. Is there another kernel i can try? Is hasusbnic=1 an option? I just ask maybe this crazy thing is internally tight to usb (would be strange).

Best Regards X23

@george1421 thanks, i will report tomorrow, i am in the home office and my collegue already left the office. Thanks so far i’ll report. Realtek? Wasn’t it Realcrap?

Best Regards X23

Hi,

@george1421 the vendor is 10ec and device 8168, we use 40AS009 Docks with that device while PXE booting was not possible with the native NIC it worked with the Docks NIC, after the Deployment the Docks NIC was not available before the device has been rebooted, the fun part is the latest Windows (20H2, Patch level from December) detects the native NIC that FOG does not while trying to PXE boot.

I am happy to test a kernel that may can run the native NIC.

Best Regards X23

Hi,

we have a couple of that new Lenovo E15 Gen2 and it seems to that both kernels 4.19.143 and 5.6.18 won’t boot that device.

There seems to be a newer Realtek NIC inside:
https://linux-hardware.org/index.php?probe=87d5cec59e

Haha the Lenovo technical informations only list the nic as network connector lan/rj45 no further informations, lan seems to be something from yesterday the youth uses WLAN

Any idea, is there maybe a newer kernel i can try?

Best Regards X23

Hi,

thanks for your suggestions, i made another try i gave the first login more time, after 10 minutes the first login attempt worked, i maybe was to impatient usually a login doesnt take such long, every login attempt after that first one is working normally.

Hmpf, i will try recreate the image from scratch to see if this impact occours again.

Best Regards X23