Elitepad 1000
-
You can also do this as root.
[CODE]su root[/CODE]
enter your password.
[CODE]apt-get install gedit[/CODE]
[CODE]gedit /etc/dhcp/dhcpd.conf[/CODE] -
Well, so much for that.
Same exact issue.[CODE]>>Start PXE over IPv4, Press [ESC] to EXIT…
Station IP address is 10.10.10.13Server IP address is 10.10.10.10
NBP filename is ipxe.efi
NBP filesize is 903232 Bytes
Downloading NBP file…Succeed to download NBP file.
_[/CODE]Then it tries to boot IPv6 and gives me the selected boot image did not Authenticate error.
BUT - it’s at least seeing the new boot file. So, a little bit of progress. -
Just tried this with an Elitepad 900 tablet which is a little bit different.
It went through the same PXE boot as above, then said “Network not found”Also tried changing the boot file to snp.efi with no change.
-
Well, the NBP file did change, and the file size changed… It is indeed getting ipxe.efi
I’m not entirely sure where to go from here.
Someone else with more experience might need to pick this up (pretty much everyone else here has more experience than me, lol).
maybe re-read through that thread for the Surface Pro 3’s.
Hopefully someone will hop in here to help.
-
UPDATE: Disabled secure boot and I got “iPXE initializing devices” & “iPXE 1.0.0+ open source network boot firmware”, which promptly disappeared and sent me back to BIOS boot options (Ethernet IPV4 or Ethernet IPV6)
SO CLOSE.
-
Before we can get any closer I guess we need to know which ethernet connector you use. Searching the web I found people using docking stations (e.g. C0M84AA) or ElitePad Ethernet Adapter or even USB hubs like LAN951x to add ethernet to their elite pad…
Please let us know about your ethernet adapter! Maybe even let us know about the PCI IDs found in windows device manager…
-
Using the HSTNN-C75X dock with a TekRepublic TUN-300 dedicated to the FOG VM. I can use a TUN-300 attached to the Elitepad, but then it only runs on battery because there’s only a single port on the tablet.
The dock’s ethernet adapter shows up as [B]LAN9512/LAN9514 USB 2.0 to Ethernet 10/100 Adapter[/B] with the hardware ID being [B]USB\VID_0424&PID_EC00$REV_0200[/B]
I updated to the beta version of FOG (3121) but still nadda. Tried ipxe.efi snp.efi and default.kpxe
-
Let me explain: Your network card requests an IP via DHCP and loads the boot image over the network, first step done. Now iPXE has to detect your network card to be able to talk on the network and request things via TFTP and HTTP. This is where things go wrong I suppose. iPXE can either use native drivers (someone has to write a driver for each and every piece of hardware) or UNDI (see here for more information about this: [url]http://fogproject.org/wiki/index.php/IPXE[/url]). As far as I could find out this piece of hardware should actually be able to talk UNDI. The only native driver I could find in iPXE source code is smc9000 which seems to only support LAN91xx devices and it’s kind of old anyway.
And then there is another thing. BIOS vs. (U)EFI. As you already saw undionly.kpxe is not working for you. That’s only made for BIOS type PCs. You need to use .efi files OR you need to switch your elitepad to legacy BIOS mode (not 100% sure if this can be done, a quick search on the web mentioned something like this). iPXE support on BIOS is definitely a lot better than with EFI (see here: [url]http://ipxe.org/efi/vision[/url])! As you see there are a lot of combinations and it’s up to you to fiddle with those till you get it right. Although there is no garantee that it’ll work (see below) there is a high chance that you will learn a lot about all those things and hopefully will get it working too!!
With some of our EFI Macintoshs I had to compile my own patched version of iPXE to get it working. See here on how to build your own iPXE files: [url]http://fogproject.org/forum/threads/build-ipxe-from-source.10152/[/url]
-
I agree with you on where it’s failing. Here’s a complete log (I had to take a video because it goes by so fast I can’t read it)
[CODE]>>Start PXE over IPv4, Press [ESC] to EXIT…
Station IP address is 10.10.10.13Server IP address is 10.10.10.10
NBP filename is ipxe.efi
NBP filesize is 903232 Bytes
Downloading NBP file…
_
Succeed to download NBP file.
_[/CODE]SCREEN CHANGE
[CODE]IPXE Initialising devices…ok
IPXE 1.0.0+ (334ee) – Open Source Network Boot Firmware – http://ipxe.org
Features: DNS FTP HTTP HTTPS NFS TFTP VLAN EFI Menu
Boot Succeeded - Ethernet IPV4
_[/CODE]SCREEN CHANGE
[CODE]Boot Succeeded - Ethernet IPV4
_[/CODE]BACK TO BOOT MENU
-
Also, I forgot to mention the tablets will only PXE boot when docked. I cannot use the USB Ethernet adapters, only the dock’s Ethernet adapter which is really just a USB one. I have secure boot disabled, but there’s no legacy boot mode on these tablets.
I did find a UNDI driver on the manufacturer’s website. They listed it as “LAN95xx and LAN7500 UEFI PXE (UNDI) Driver” I’m going to import that to the server and see if I can use that file “SmscUsbNetUtility.efi” tomorrow since it’s quitting time.
I’ll look into that link you shared for making an iPXE file.
-
[quote=“FSIT, post: 44018, member: 29030”]Also, I forgot to mention the tablets will only PXE boot when docked. I cannot use the USB Ethernet adapters, only the dock’s Ethernet adapter which is really just a USB one. I have secure boot disabled, but there’s no legacy boot mode on these tablets.
I did find a UNDI driver on the manufacturer’s website. They listed it as “LAN95xx and LAN7500 UEFI PXE (UNDI) Driver” I’m going to import that to the server and see if I can use that file “SmscUsbNetUtility.efi” tomorrow since it’s quitting time.
I’ll look into that link you shared for making an iPXE file.[/quote]
I bet the manufacturer’s driver will work.
-
[quote=“Wayne Workman, post: 44019, member: 28155”]I bet the manufacturer’s driver will work.[/quote]
Sure it will! I saw that on their website too. But what will it do?? To get FOG running you’d still need to chainload iPXE…So far I haven’t found anyone on the web having the same message: “Boot Succeeded - Ethernet IPV4”. Are you sure that’s what it says?? I will grep through the ipxe code when I get back…
-
I haven’t had time to mess with this today, but as soon as I do I’ll post an update.
[quote=“Uncle Frank, post: 44035, member: 28116”]So far I haven’t found anyone on the web having the same message: “Boot Succeeded - Ethernet IPV4”. Are you sure that’s what it says??[/quote]
Very sure: [URL=‘https://www.dropbox.com/s/yorinty6htozsqu/20150317_102709.mp4?dl=0’]https://www.dropbox.com/s/499pqb88bvi6k4m/Tablet PXE.mp4?dl=0[/URL]
-
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
