Latitude 5410 No Legacy boot
-
@John-L-Clark again did running this line give no errors?
sudo apt-get install -y wget libdbus-1-dev libnetfilter-conntrack-dev idn libidn11-dev nettle-dev libval-dev dnssec-tools -
@george1421 It fails
-
@John-L-Clark
Temporary failure resolving 'us.archive.ubuntu.com'. Works fine on my end:nslookup us.archive.ubuntu.com Server: 192.168.24.1 Address: 192.168.24.1#53 Non-authoritative answer: Name: us.archive.ubuntu.com Address: 91.189.91.38 Name: us.archive.ubuntu.com Address: 91.189.91.39 -
@george1421 Ok that finally ran and i was able to run the Make Install and this is what I got.
-
@John-L-Clark So then I checked the version and tried to restart the service and this is what I got.
-
@george1421 This is what I see. Any ideas?
-
@John-L-Clark Ok it looks like you have it compiled and working. I realize this is quite an intensive process. If your distro had an up to date version it would not be necessary.
The first thing I see is that you have your compiler files extracted into the /etc/dnsmasq.d directory. IMO it should not be there but in your home directory instead. dnsmasq searching the /etc/dnsmasq.d directory and sub directory for configuration files. Who knows what I might find if it searched the build path files. So move that /etc/dnsmasq.d/dnsmasq-2.76.orig directory out of there. You see in the error message *bad option in line 1 of /etc/dnsmasq.d/dnsmaq… dnsmasq found a file it didn’t like in its config file path, so move it.
Second what you want to do in install the distro’s version of dnsmasq. I know it will be 2.75 but what we are going to do is slide in your compiled version of dnsmasq in place of the distro’s version.
So once you move that compiler directory out key in
which dnsmasqthat will tell you where the distro placed its file. Then copy the dnsmasq you just compiled over and replace the distro’s version. -
@george1421 Ok so I got it running and can boot EFI but get this error.
-
@John-L-Clark On the plus side dnsmasq appears to be working.
So is your fog server at 192.168.101.29? I think yes because it found default.ipxe and then chained to boot.php. So is the web ui running on that server? You didn’t do anything like setup https on that server did you?
-
@george1421 no we didnt change any of that I can still boot legacy just fine with the undionly.kkpxe I used the ipxe.efi for the efi boot.
-
@John-L-Clark From the same subnet? What the error is telling us/me is that ipxe.efi is working because its picking up an up address AND tftping from the FOG server. What is failing is connecting from this computer to the fog server over http. Is it possible some kind of screening router or other is blocking http access from this client to the FOG server?
-
@george1421 If i hit the s button i can get into the ipxe command line. I am able to ping the fog server from there. I can even type in login and it brings up the username and password prompt and i can login there with my fog username and password. It then takes me back to the ipxe screen. All machines that are working on legacy are on the same subnet.
-
@John-L-Clark So from a computer on the same subnet as the target computer, can you open a browser and browse to
http://192.168.101.29/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00That should give you the text configuration behind the iPXE menu.While sitting at the iPXE command prompt (from the error in the picture where you hit ‘s’) what happens if you
ping 192.168.101.29and then key in
chain http://192.168.101.29/fog/service/ipxe/boot.phpWhat you are telling me should not be happening.
Also I looked through the thread quickly but I didn’t see where I asked what version of FOG are you running?
-
@george1421 I can ping the 192.168.101.29 from the prompt and then i type in the chain command and it times out. I can browse to the http://192.168.101.29/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00 from my machine on the same subnet I can get there. The version of fog is 1.3.5
-
@John-L-Clark said in Latitude 5410 No Legacy boot:
The version of fog is 1.3.5
Well I didn’t see that coming. 1.3.5 is pretty old. If you want to stay in the pre-1.5 version branch you might consider to upgrade to at least 1.4.4 using the tarball method to upgrade. Version 1.5 add quite a bit of enhancements that require more CPU, 1.4.4 was the last stable image in the pre-1.5 world of FOG.
Lets try downloading a more current version of
ipxe.efifrom here: https://github.com/FOGProject/fogproject/tree/master/packages/tftp the file gets downloaded to the /tftpboot directory on the FOG server. -
@george1421 i downloaded the new ipxe.efi and put it in the tftpboot and renamed the old one .old
It did the same thing. I will have to talk to the team about availability to upgrade fog. This time of year is our busiest. This is a picture of Legacy booting on that same table as the other and it just works. Sorry I am such a problem!!
-
@John-L-Clark Is there any possibility to take a single computer, configure it for bios and then take that same computer and configure it for uefi and boot it from the same network jack.
I’m having a hard time understanding why bios works to chain to boot.php but uefi is getting a connection timeout.
We can surely rule out everything before iPXE starts up because iPXE is getting to both systems. So its not pxe boot or most likely not iPXE itself. dnsmasq is not the issue because again the right boot loader is being sent to the target computer.
We can see clearly that the http protocol is loaded in both of the pictures you provided for bios as well as efi.
When you pxe boot and get the connection timeout with the uefi image, look in the apache log directory on the FOG server. It may be in /var/log/apache2 or somwhere in that area. There should be an error_log in that dirctory. Tail that log realtivly close to the time you get the chain load error. See if apache is throwing an error when the target computer requests boot.php, I’m really grabbing at straws here, but it should NOT do this.
-
@george1421 ok progresss, the Lenovo E550 that was booting to legacy but installing an EFI image can boot EFI only and has legacy completely disabled. The Dell Latitude 5410 still times out. I will keep testing tomorrow and Will update the Feed. Thank you again for all the help.
-
@george1421 I have tried several other machines and we are able to boot to Fog using ipxe.efi. The Latitude 5410 I still can not get it to boot to Fog. I have tried the old ipxe.efi and the new ipxe.efi. I have tried several of the other .efi boot files and i just can not get it to boot. Any Ideas? Thanks
-
@John-L-Clark make sure you have the latest version of the firmware installed on this 5510.
