HP EliteDesktop 800 G2 SFF
-
I am having difficulties connecting the HP EliteDesktop 800 G2 SFF to Fog. It boots with PXE, but when Fog tries to get the systems inventory, nothing happens. Is there a specific kernel that I should use? Other ideas?
-
Lets collect a little more info here.
Can we assume you are using either FOG 1.2.0 stable or a trunk build?
When you pxe booted into FOG is your device in BIOS or (u)EFI mode?
Can you define what “nothing” is?
If you can take a screen shot of any error or warning message that would be helpful to help you.
-
First we need information please.
What version of FOG?
Is this UEFI or BIOS booting (legacy)?
What have you tried already? Most times the issue you’re describing comes from a missing driver in the kernel. However, I don’t know what FOG you’re running, therefore I don’t know what version of kernel you’re running with currently.
-
I am currently running 1.2.0. I have tried the kernels that were suggested for use with the HP ED 800 G1. I am using BIOS booting, had tried network boot with UEFI, but it did not recognize the network card, BIOS worked.
The screen indicates that it is trying to get the inventory, but “blank” lines are returned until the screen is entirely black. I have allowed it to sit idle for over an hour.
-
@ohlensehlenji Can you upgrade to trunk? While I do understand hesitation, I think it may help with the issue you’re seeing. 1.2.0, while the latest stable, had a bunch of issues that were/are too hard to determine especially considering how far forward FOG has come since 1.2.0’s release.
-
Upgrade to trunk instuctions: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
-
This is largely a “test” environment at this point, so upgrading to trunk isn’t a problem. I will give it a shot.
-
Upgrading to trunk fixed the problem with the client connecting and registering. I was able to upload an image, but deploying failed. I will get back to that one this afternoon. Thanks for your help!
-
Did you find a fix for the image not deploying or did you have to go another route.
-
@Rwest Are you using FOG trunk or version 1.2.0. Please post a picture of the error you see when trying to deploy!