Elitepad 1000
-
Well, just got around to installing the file on the server and still no boot. Not it hangs at “Boot Succeeded - Ethernet IPV4” for about 20 seconds and brings me back to the choice of IPv4 or IPv6 boot.
Head > Desk > Repeat.
-
You still have to setup the chainloading, as Uncle Frank said.
I’m new to it, Uncle Frank will have to confirm if [URL=‘http://www.fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0’]THIS[/URL] will do it, or help at all.
-
Yeah I’m waiting for his response, as when I hear chainloading, I think of putting chains in the back of my truck. :rolleyes:
-
Sorry if my last comment wasn’t clear. With “you’d still need to chainload iPXE” I meant that using SmscUsbNetUtility.efi doesn’t help at all as you need iPXE to use FOG (version 1.2.0 and newer)!
I didn’t have much time today so I had no chance to really find out where this “Boot Succeeded - Ethernet IPV4” is coming from. It’s definitely not iPXE. I guess it’s the manufacturer binary that’s burned into the NIC ROM. So it seams like iPXE hands back to the NIC at some point…?!?
Maybe it’s time to get into compiling your own iPXE binary with debugging ON!
[CODE]make … DEBUG=efi_init,efi_snp[/CODE]
-
[quote=“Uncle Frank, post: 44071, member: 28116”]Sorry if my last comment wasn’t clear. With “you’d still need to chainload iPXE” I meant that using SmscUsbNetUtility.efi doesn’t help at all as you need iPXE to use FOG (version 1.2.0 and newer)!
I didn’t have much time today so I had no chance to really find out where this “Boot Succeeded - Ethernet IPV4” is coming from. It’s definitely not iPXE. I guess it’s the manufacturer binary that’s burned into the NIC ROM. So it seams like iPXE hands back to the NIC at some point…?!?[/quote]
Very well could be, these Elitepad 1000 tablets are pretty new so it doesn’t surprise me that the issues I’m having are undocumented.
[quote=“Uncle Frank, post: 44071, member: 28116”]Maybe it’s time to get into compiling your own iPXE binary with debugging ON!
[CODE]make … DEBUG=efi_init,efi_snp[/CODE][/quote]
Hmmm, when I run this in the console, what should I expect for an output? Probably not what I got.
[CODE]make: *** No rule to make target `…'. Stop.[/CODE] -
Don’t add the literal …
It’s to include any of the other options you normally would.
-
What’s the literal?
Again, keep in mind I have NO Linux knowledge. In the past 20 years all I’ve dealt with is DOS & Windows-based OS
-
You’ve made it pretty far with “NO” Linux knowledge. So you’ll be able to learn the rest too I reckon. Please make yourself familiar with GNU MAKE and play around with building your own ipxe binarys ([url]http://fogproject.org/forum/threads/build-ipxe-from-source.10152/[/url]).
We try hard to answer all the questions properly but we can’t give a step by step solution for everything. No offense!
-
Yeah I’ve gotten pretty far between tutorials and the almighty Google.
-
Well, I’ve had to shelf this project as it was taking up entirely way too much of my time and I’ve been unable to complete other tasks. We hired an outside firm to clone the tablets, and they’re having just as much trouble as I did. Not looking good at all.
-
The factory images these things somehow… they should offer imaging services before shipment IMO.
It really sucks that we couldn’t get this going faster…
But, seeing that this IS a windows tablet, your imaging needs for them are not likely to just go away. You’ll probably have to come back to this problem sooner or later. IMO, I think we should work towards a solution for these before then.
-
I compiled three binaries with debugging enabled for you, find them atteched! I’d be very interested to see the debugging output… please take a picture of even video.
Please try out snp.efi or snponly.efi instead of ipxe.efi as well! Do they all fail at the same point (I doubt it!)…
[url=“/_imported_xf_attachments/1/1814_efi-binaries.zip?:”]efi-binaries.zip[/url]
