@george1421 said in Microsoft Surface Go - USB-C to Ethernet Adapter Compatibility:

Just be aware I only gave you the 64 bit kernel. So the step you did above will break a 32 bit computer.

Gotcha.

If everything works OK with bzImage4186 you can leave it in the bzImage place. The only thing that is different is I added the microsoft nic. With the next release of the official FOG kernel they will add in the new Microsoft NIC.

I’ll leave it under bzImage4186 until the next release. We don’t have any other machine right now that uses a USB-C NIC Adapter, so it should be fine.

@geardog said in No configuration methods succeeded (I210 NIC):

It turned out to be a bios/UEFI setting “option rom launch policies.” New to me. In my defense, this box’s bios is pretty massive and clumsy to navigate through, but works now!

Well that is a new one for me too. You might want to post the model of HP computer this is just in case someone else has the same issue in the future. This issue does sound a bit unique to this hardware.

@Sebastian-Roth

lspci -nn showed the drive to be in raid mode

using a tutorial on bcdedit via cmd for safemode boot I was able to change the setting without reinstalling windows

now the machine is imaged

resolved and thankyou

coming back to this with a fresh mind and some new info helped

@ttrammell said in Asus ZenBook Flip UX360U - PXE Assistance Needed:

UEFI BIOS on the Zenbook still doesn’t recognize the USB-to-Ethernet adapter,

FWIW: To get this to work, you need network adapters supported by your hardwares UEFI firmware. Think of uefi as a very limited operating system. If it doesn’t have the drivers built in, then it can’t initialize the device. So if you want to pxe boot on that zenbook you need to contact the manufacturer to find out what usb network adapters are supported by the firmware … or … just boot fos from the usb stick and move on to the next problem.

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

The issues with the Dell x90s and x010s are know, but thank you for confirming on 390 and 3010 variants.

Yes, but it’s for wiki =]

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

As for the 3020s, I know that uefi device initialization does take time. Its almost at the point where you think its locked up, it will finish initializing the device.

Exactly and it’s aggaining!

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

FWIW, refind is used on the other end. When leaving the FOG iPXE menu to attempting to boot from the local uefi hard drive. So refind will not help you get iPXE to run.

Yes I know, but SANBOOT does not work.

@george1421 said in [ipxe.efi] No menu with Optiplex 3010:

You can use the FOS usb boot stick if you need to image these systems to bypass pxe booting if you need.

It’s true, but UEFI is only for test at the moment. I’ve made an image for notebook now.

@george1421 0_1535146823857_Surface_4.JPG

After reflexion, i wiil use the postinit script … Why ? Because if i receive a new model with the VBoxMouse.sys conflit driver, i will need to search again the culprit file into the Driver Pack … and waste many times …

So, in the fog.bonus, i added this :

# suppression du fichier VBoxMouse.sys ... eviter conflit et BSOD avec les Optiplex5050 durant SYSPREP (au 2nd reboot, durant verif perf. videos) rm /ntfs/Windows/System32/drivers/VBoxMouse.sys echo "Suppression du fichier VBoxMouse.sys pour eviter BSOD durant SYSPREP (au 2nd reboot) ... Done !";

I also added this in the SetupComplete.cmd :

rem uninstall VirutalBox Guest Additions : eviter les BSOD comme VBoxMouse.sys sur machine cible "C:\Program Files\Oracle\VirtualBox Guest Additions\uninst.exe" /S

I retried a download task on the Optiplex 5050 … and no BSOD 🙂

So … just many thanks again George for your help ! Knowledge growth up !

PS : how can pass the subject to “Solved” ?!

@jkoch any update?

for downloading any hp drivers
visit http://www.downloadhpdrivers.com/

@mecsr Great. I’m glad you have it working.

Just as a word of warning, don’t advanced past the 4.15.2 version of the kernel until you update FOG, and even then stick with 4.15.2 until the developers can dig into why 4.17.0 is acting slow.

@george1421 oh ok i see, thank you so much george, i will test this one

The kernel has nothing to do with initial iPXE boot though, the iPXE binaries are only updated through updating all of FOG.

@psycholiquid I was able to resolve the refinduefi issue with the HP ProDesk 400s by pulling the old refind.conf file from the backup fog server and reverting refind.efi to version 0.11.0

@jester805 We just got in a Precision 3530 that will only boot to the hard drive if it is plugged in with the network cable. As soon as we unplug it, it will say no drive found… My coworker did these steps:

(If you can get in windows like we can) run an elevated cmd prompt, run this mbr2gpt.exe /convert /allowos boot back into the BIOS and set boot back to UEFI It should show the drive in there now.

If you cant get in windows I assume you would be able to do this with a restore disk or something similar to runt the command.

**Side note Once imaging is done here for the summer, we are going to look at moving to UEFI images and setting FOG to handle both using THIS ARTICLE.

@tom-elliott

Thanks I will build a new server with the newest FOG client. ( Never built one so here goes)… ( of course I will keep the old until the new one is tested.)

@Amerhbb Which version of FOG do you use?

@george1421

Thank you for the insight. Let me look at those items a little further.

@sebastian-roth

Success! We had the fields reversed for 32 and 64 bit UEFI. Thanks!

@imagingmaster21 If you are keen to get into the details of why iPXE is hanging you can go ahead and compile your own debug enabled iPXE binaries to find out what’s exactly wrong on this hardware? Read the last two dozen messages of this forum thread to see if you wanna give it a try: https://forums.fogproject.org/topic/11348/hyper-v-and-pxe-boot-to-fog-problems

Let us know if you need support with that.

@george1421 I have had to disable secure boot to PXE boot at all with FOG, but I think you can re-enabled it after the image deploys but before it starts the OOBE experience (meaning you will need to have it shut down after imaging or catch it on reboot). One of the more experienced guys might prove me wrong though.
You will have to leave it disabled if you want to PXE boot in the future though.