Surface Pro 3 PXE:
-
Just tried with the file supplied in the link and it still won’t boot to the Fog menu - I get downloading NBP? File…
Then blips saying successful and then continues to load up Windows.
-
OK,
I originally tried using the ipxe.efi which failed to boot the surface to the fog menu,
I then tried the snp.efi which booted to a very basic looking menu, I tried to register the host and I get the message:-
i8042: Can’t read CTR while initializing i8042
usb usb2-port1: couldn’t allocate usb_device
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
—[ end of Kernal panic - not syncing: VFS: Unable to mount fs on unknown-block(1,0)I’ve also tried changing the bootfile to snponly.efi and get the same error as above.
Thanks
Matt
-
What version of fog?
-
We are running FOG Version 1.2.0 on Ubuntu 12:10
Thanks
Matt
-
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.
-
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
-
-
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] -
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!
-
I’m hoping that once you make a 32-bit bootfile that it’ll work. Unless you already have…
-
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 IPv4It 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 IPv6Before continuing to boot up the Surface Pro 3.
I don’t get any Fog Menu
Thanks
Matt
-
Try making a 32-bit EFI bootfile with a script that only has these contents:
#!ipxe
dhcp
shellIf that doesn’t work either, make a 64-bit one with the same script.
One of those should bring you to an iPXE shell.
-
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
-
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). -
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.
-
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
-
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.
-
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.
-
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?
-
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 sdWhat do you see?
