Surface Pro 3 PXE:

Matt Edwards

We are running FOG Version 1.2.0 on Ubuntu 12:10

Thanks

Matt

Tom Elliott

okay, Matt, can you attempt upgrading to SVN? The command line you’re missing (causing your boot problem) is initrd=init.xz. This is corrected for in SVN, though I am aware of some issues potentially with the init and am working hard to try correcting them.

Matt Edwards

I’m really sorry Tom, are you able to guide me to what I should be doing exactly to achieve what you say. I’m not too familiar with the background workings of Linux.

Thanks

Matt

Wolfbane8653

[url]http://fogproject.org/wiki/index.php/Upgrade_to_trunk[/url]

d4rk3

Do this:

[SIZE=13px][INDENT]Go here:

[URL=‘https://rom-o-matic.eu/’]https://rom-o-matic.eu[/URL]

Advanced - EFI PXE Bootstrap 32-bit

Check these boxes:

[URL=‘http://www.ipxe.org/buildcfg/PARAM_CMD’][FONT=Arial][COLOR=#000000]PARAM_CMD[/COLOR][/FONT][/URL][FONT=Arial][COLOR=#000000], Form parameter commands [/COLOR][/FONT]
[URL=‘http://www.ipxe.org/buildcfg/CONSOLE_CMD’][FONT=Arial][COLOR=#000000]CONSOLE_CMD[/COLOR][/FONT][/URL][FONT=Arial][COLOR=#000000], Console command [/COLOR][/FONT]
[URL=‘http://www.ipxe.org/buildcfg/CPUID_SETTINGS’][FONT=Arial][COLOR=#000000]CPUID_SETTINGS[/COLOR][/FONT][/URL][FONT=Arial][COLOR=#000000], CPUID settings[/COLOR][/FONT]

And paste this script in the script box (Replace x.x.x.x with your FOG server’s IP or hostname):

#!ipxe

dhcp
cpuid --ext 29 && set arch i386 ||
params
param mac0 ${net0/mac}
param arch ${arch}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain [url]http://x.x.x.x/fog/service/ipxe/boot.php##params[/url]

Click Proceed, and voila! Copy the new EFI bootfile to your /tftpboot folder and give it a whirl![/INDENT][/SIZE]
[SIZE=11px] [/SIZE]

Matt Edwards

Thanks - I’ll give this another shot - but I tried this a few days back after reading your earlier post and couldn’t get it to work!

d4rk3

I’m hoping that once you make a 32-bit bootfile that it’ll work. Unless you already have…

Matt Edwards

Morning,

I’ve tried again using the modified ipxe.efi file created from the website - When I set that as the bootfile and boot up the Surface Pro 3 I get…

Checking Media Presence…
Media Present…
Start PXE over IPv4

It flicks then to saying

Downloading NBP file… (this appears for a second or two)

Then moves onto

Checking Media Presence…
Media Present…
Start PXE over IPv6

Before continuing to boot up the Surface Pro 3.

I don’t get any Fog Menu

Thanks

Matt

d4rk3

Try making a 32-bit EFI bootfile with a script that only has these contents:

#!ipxe

dhcp
shell

If that doesn’t work either, make a 64-bit one with the same script.

One of those should bring you to an iPXE shell.

Matt Edwards

Thanks - will try this tomorrow when I’m back in work.

If I manage to get it working, will this then boot up the fog menu or will I need to enter some command in the iPXE shell to load fog? If so, what will I need to enter?

Thanks

Matt

Sebastian Roth

You’ll end up in an iPXE shell…
dhcp, ifstat, ipstat and ping will be helpful to debug you network connection. When it is up you can just chainload default.ipxe (chain tftp://<tftp-ip>/default.ipxe) OR run all the commands by hand (see d4rk3’s earlier post #45).

d4rk3

Correct. Once we get you to a shell we can go from there.

On that note, once you are able to boot to an iPXE shell make a note of the architecture of the EFI bootfile. Go back to [url]https://rom-o-matic.eu[/url] and re-compile an EFI bootfile with the correct architecture for your Surfaces.

Keep us posted.

Matt Edwards

I’ve tried doing this…

I first tried with the 32 bit and it flashed up saying downloading NBP File very quickly then moved onto IPv6 before continuing to load up Windows…

I then tried using the 64 bit version, again it came up with Downloading NBP file and appeared to be doing a little more then the 32 bit version, but then it continued to load up Windows!!

What else can I try??!?!?

Thanks

Matt

d4rk3

Ok, I just re-read this thread and I missed your earlier message:

“I then tried the snp.efi which booted to a very basic looking menu”

The snp.efi is what you’ll want to use for these.

Now, we just need to find a good kernel for these to boot with and you should be all set.

d4rk3

Ok. I just re-read it again and Tom is correct, you’ll need to upgrade to the latest SVN for these to work.

[CODE]apt-get install subversion
svn co https://svn.code.sf.net/p/freeghost/code/trunk/ /opt/trunk
cd /opt/trunk/bin
./installfog.sh[/CODE]

Once upgraded use the snp.efi bootfile and see if you’re able to register the Surface with FOG.

A Former User

I am experiencing a similar issue.

I was able to get a Surface Pro 3 to PXE boot and recognize my FOG server, but when I attempted to either Quick Host Register or Full Host Register, I received the following error:

“Error ident-mapping new memmap (ox13ac72000)!
i8042: No controller found”

Then, at the usual FOG registration screen, it says:
“An error has been detected!
Cannot find HDD on system”

I tested using a USB keyboard instead of the Surface keyboard, and made sure that the server could still register and deploy images to other computers.

I also tried snp.efi and ipxe.efi with no luck. FOG 1.2 and my trunk is up-to-date as of yesterday (9/22/15) and the FOG server has been restarted.

Any ideas out there?

Sebastian Roth

There are several other threads about Surface Pro 3 in the forums (https://www.google.com/?gws_rd=ssl#q=site:fogproject.org+surface) but non of them is talking about HDD problems I wonder.

AFAIK there is a SSD drive in the Surface Pro 3, right? Please add the device as a new host with it’s MAC address by hand in the webinterface. Then boot it up in a debug session (Host -> Basic Tasks -> Debug) and issue the following command:

dmesg | grep sd

What do you see?

A Former User

Thanks Uncle Frank . Please see the attached image of what I saw after entering the debug command.

Sebastian Roth

What about this:

dmesg | grep ATA

Sorry, this is just guessing in the dark so far. Probably best if you could upload the whole output so we can have a look. Again, boot into debug mode and then:

mkdir -p /mnt
mount -o nolock <your-fog-server-ip>:/images/dev /mnt
dmesg > /mnt/dmesg.txt
umount /mnt

Edit: Just for the records, here is what dmesg on a Surface Pro 3 might look like: https://gist.github.com/altercation/30776be1078eac2b0cc6

A Former User

Here’s what I got:

tech@fog14VM:/images/dev$ less dmesg.txt
[ 0.000000] Linux version 4.2.0 (root@debian64) (gcc version 4.9.2 (Debian 4.9.2-10) ) #8 SMP Thu Sep 17 09:02:24 EDT 2015
[ 0.000000] Command line: bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.2.16.9/fog/ consoleblank=0 mac=c0:33:5e:73:cf:a2 ftp=10.2.16.9 storage= storageip= web=10.2.16.9/fog/ osid= consoleblank=0 irqpoll hostname=MIC-SURFACE-02 mode=onlydebug
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Legacy x87 FPU detected.
[ 0.000000] x86/fpu: Using ‘lazy’ FPU context switches.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000008efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000000090000-0x000000000009dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x00000000ba96efff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000ba96f000-0x00000000bac6efff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bac6f000-0x00000000bad6efff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bad6f000-0x00000000bb3bffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bb3c0000-0x00000000bbaccfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bbacd000-0x00000000bbad0fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bbad1000-0x00000000bbad1fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bbad2000-0x00000000bbffffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fea00000-0x00000000feafffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed03000-0x00000000fed03fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed06000-0x00000000fed06fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed08000-0x00000000fed09fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1cfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fedbffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved

Surface Pro 3 PXE:

241

11.7k

17.1k

154.6k