I’m fairly sure the Surface Pro can only UEFI boot, so you need to make an UEFI image

@Jerry29445 Any news on this?

@jphillip5 Ok the dumb switch resolved (masked) your issue.

Your building switch, is it an advanced switch like the Catalyst series?

Do you have fast STP, port fast, or RSTP enabled on the ports that go to these HP targets?

Do you have green ethernet or 802.1az enabled on these switches? (if so turn it off).

@csurepair You should really start your own thread because the conditions could be different.

Things that we would need to know is the version of FOG you have installed (on or about the cloud on the management home page).

What is your dhcp server?

Is the HP in uefi or bios (legacy) mode?

Since you are getting to the download of bzImage, it probably safe to assume you have the correct iPXE kernel loaded into dhcp option 67.

Are you using dnsmasq in your environment?

you guys can mark this as solved I posted how I resolved this issue above

Could it be that was a RAW image deployment error vs a multiple partition image deployment? Yes, imaging is going well.
We had to downgrade the TPM from 2.0 to 1.2, since we are not doing UEFI.

Cross linking post: https://forums.fogproject.org/topic/7851/intel-raid0-image-capture

We now know what is going on with this and there is a work around pending.

What George said.

Hello Again,

Upgraded to 8143 - I was able to register the machine successfully.

Thanks,

Tom

@mandrade I was just on a side chat with Tom. He said that the FOS kernels were updated earlier this week to 4.6.2. What is on the usb image is older than those. It would be interesting to see if the newer bzImage allowed that onboard nic to work.

You might want to download and refresh these files on the usb stick and try again.
https://fogproject.org/inits/init.xz
https://fogproject.org/inits/init_32.xz
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32

@tmerrick I know this is asking a bit much, but if you swap one of the class 10 or class 20 with a samsung evo’s do they exit correctly with San boot? That would help us identify that it is clearly something different with these class 10+ drives or the motherboard. If you don’t have time to debug that is ok. It would just help the next guy with the same issue.

I’m going to mark this thread as solved either way. Thanks again for your feedback.

i was stuck at the same screen for days before i found the solution

fog server ip 172.16.1.105
fog hostname debianfog
fog fqdn debianfog.debianfog.local

juts edit your hosts file … nano /etc/hosts and add
172.16.1.105 debianfog.debianfog.local debianfog

Now mullticast starts without any problem

@forte647 Too bad you got one of those ugly NICs running the r8169 driver. We have seen a lot of trouble with those lately. If I remember correctly this was an auto-negotiation issue most times. As George already said, can you try setting link speed to static GbE or 100M Fast Ethernet on your managed switch and try again? Please keep an eye on the link LEDs (switch and NIC) as well.

Are we allowed to use your picture in the wiki once we figure this issue out? As you are within a private IP range this shouldn’t be an issue privacy wise. Or we can mask the IP and MAC information if you don’t want to see those in the wiki.

@george1421 The article I am working on (don’t find the time to do get this finished) is linked in my signature…

@Wayne-Workman said in Surface Pro 4 on 7977:

@fry_p Once DHCP is configured, you will never have to change it. It takes 10 minutes to setup, every step is laid out for you in here:

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

I was able to set this up this morning. Works perfectly. The only thing is we have many scopes in the building I set up Surfaces at, so I set the policy at server level. Thanks for the tip!

@SteveB689 OK so this is just research then. Fair enough.

I’m sorry you had so much frustration setting up FOG. I know it is a complex environment especially for those coming from a purely MS Windows background. Hopefully you found the support you needed in the FOG forums.

On a positive note it sounds like Arrowhead-IT has personal experience with this hardware so you have someone that already went down the path you are on.

@the_great_heed I’m using the trunk version, not 1.2.0, so I’m not sure. This will become our production FOG server since we are adding another 600-700 G2 SFFs.

I agree with Wayne that 0.32 is fairly old and so is the linux kernel for that. What version number of the kernel do you have installed?

For the Win10 you will need to ensure your master (reference) image uses a MBR style disk. GPT is not supported on that old version of FOG. Don’t get me wrong FOG 0.32 will work here as long as you take precautions and have supported hardware/linux kernel. You could “try” to slide in the latest version of the FOG kernel that is 4.5.3. If I remember correctly 0.32 only supported a 32 bit linux kernel so you will need bzImage32 and then rename it to bzImage to be compliant with your inits. DON’T upgrade the to the latest inits because that for sure will break your boot.

You can get the latest 32 bit kernel here, just be sure to rename your original kernel and then rename this one to match your original kernel.
sudo wget https://fogproject.org/kernels/bzImage32

I do have to say the best path (but not the easiest) for you on this endeavor would be to spin up a new FOG server running the trunk version of fog 1.2.0. You will have better success with new hardware, uefi systems, gpt disks, and native win10 support.

@ga1985 Welcome to the forums. This is definitely kind of an unusual FOG question but I am happy to try and find out if we can help you.

Do I get you right there? You are trying to PXE boot and image this network device? As this seems to be kind of a black box device I guess it will be quite hard to find out the drivers we need in the kernel to PXE boot this device. Are you able to boot any kind of live linux (USB key or CDROM) on it? If yes, then give us the full output of lspci -nn and lsblk!

I am unable to get through the registration process.

Any error message you see? Please post a picture here!

@arnaudrigole That’s one way, albeit incredibly labor intensive.

Since you have a 2008 server, maybe you give a shot at setting a vendor class filter in it? There are some screenshots in the below article from 2008 to help you along your way, but I’ve not been successful yet. That’s not to say it can’t be done, it’s just saying it hasn’t been done yet. I was working on a community member’s production 2008 DHCP server and messed with it for a while but no luck. I’m not entirely sure his environment was even setup correctly…

If you are successful, we will be wanting screen-shots and steps for the Wiki.