Elitepad 1000
-
[quote=“FSIT, post: 43920, member: 29030”]When installing FOG it asked me if it wanted to provide DHCP and I said yes, which would make me thing that FOG is providing DHCP services and not Kubuntu. Where do I find any of FOG’s DHCP server settings?[/quote]
So, if you’re running DHCP on your FOG server, then this is it I think: [url]http://fogproject.org/wiki/index.php/FOGUserGuide#Linux_Server_DHCP[/url]
I don’t use FOG for DHCP so, I wouldn’t be able to verify that. BUT, it’s probably accurate.
Let us know.
-
[QUOTE]
[SIZE=4][B]Linux Server DHCP[/B][/SIZE](content missing)
[/QUOTE]Sadly there’s only Windows, Novell & Mac server settings on that page.
-
Browsing around I found what I believe to be the FOG DHCP settings file in /etc/dhcp/dhcpd.conf
There’s no /usr/share/doc/dhcp*/dhcpd.conf.sample for me to have examples, but it’s a little bit of progress.[CODE]# DHCP Server Configuration file.
see
This file was created by FOG
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.10.10.10;subnet 10.10.10.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.10.10.10 10.10.10.254;
default-lease-time 21600;
max-lease-time 43200;option domain-name-servers x.x.x.x;
option routers 10.10.10.1; filename "undionly.kpxe";}
[/CODE] -
[quote=“FSIT, post: 43923, member: 29030”]Sadly there’s only Windows, Novell & Mac server settings on that page.[/quote]
Oh I didn’t even see that line. I am sorry. I looked up some stuff on Ubuntu DHCP and found this:
/etc/dhcp/dhcpd.conf
Inside of there, you might find something that looks like this:
[CODE]ddns-update-style none;
option domain-name “example.org”;
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet 192.168.100.0 netmask 255.255.255.0 {
range 192.168.100.100 192.168.100.200;
}[/CODE]I think that all you need to do is add this line between/around the other “option” lines in there:
[CODE]option bootfile-name “ipxe.efi”;[/CODE]
You can edit that file like this, probably:
[CODE]sudo apt-get install gedit[/CODE]
[CODE]sudo gedit /etc/dhcp/dhcpd.conf[/CODE]Resources used:
[url]https://help.ubuntu.com/community/gedit[/url]
[url]http://askubuntu.com/questions/162695/setup-dhcp-server-for-lan-party[/url]
[url]http://www.ipamworldwide.com/dhcp-options/isc-dhcpv4-options.html[/url]
[url]http://ubuntuforums.org/showthread.php?t=2131666[/url] -
See my previous post.
I’m trying to change undionly.kpxe to ipxe.efi and seeing if that works. I’ll report back shortly.
-
[quote=“FSIT, post: 43924, member: 29030”]Browsing around I found what I believe to be the FOG DHCP settings file in /etc/dhcp/dhcpd.conf
There’s no /usr/share/doc/dhcp*/dhcpd.conf.sample for me to have examples, but it’s a little bit of progress.[CODE]# DHCP Server Configuration file.
see
This file was created by FOG
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.10.10.10;subnet 10.10.10.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.10.10.10 10.10.10.254;
default-lease-time 21600;
max-lease-time 43200;option domain-name-servers x.x.x.x;
option routers 10.10.10.1; filename "undionly.kpxe";}
[/CODE][/quote]Oh, that’s great!
So, according to that file, all you have to do is change the value of
[CODE]filename “undionly.kpxe”;[/CODE]to:
[CODE]filename “ipxe.efi”;[/CODE] -
Use sudo with Gedit. The post above describes this.
Gedit is a GUI based text editor.
[CODE]sudo apt-get install gedit[/CODE]
[CODE]sudo gedit /etc/dhcp/dhcpd.conf[/CODE]
-
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]
