Latitude 5410 No Legacy boot
-
@george1421 I am looking at this and got to the part where i have to edit the config.h and mine does not look the same.
This is what I see.
-
@John-L-Clark In the picture you posted, scroll down abit that section mentioned in the tutorial is there (I just checked). Its about line 173 in the config file.
-
@george1421 Ok thank you I was able to get through the rest of it to the Make install part and this is what I got.
-
@John-L-Clark so did everything on this line get installed correctly?
sudo apt-get install -y wget libdbus-1-dev libnetfilter-conntrack-dev idn libidn11-dev nettle-dev libval-dev dnssec-toolslibidn11-dev should have installed that header file.
If you just can’t get idn to load correctly then go back into the config file and remove these two lines and it should compile.
#define HAVE_DBUS >> #define HAVE_IDN >> #define HAVE_IDN_STATIC #define HAVE_CONNTRACK #define HAVE_DNSSECjust remove the lines completely from the config file.
-
@george1421 Removed the 2 lines and this is what I got. Thank you again for your help.
-
@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.
