Dell Inspiron 15 7559
-
@Sebastian-Roth said in Dell Inspiron 15 7559:
Looks like our iPXE script (see here) is not behaving the way we intended it to.
Well that may explain why I didn’t see the main dhcp server responding with next server. I was going to have the OP post his ltsp.conf again on monday to see if we had something in the wrong spot and/or capture another pcap file. We might want to do that just to be clear that dnsmasq isn’t doing something unexpected.
-
Alright I’m back (a day late). We’re trying to move fast with this so I’ve gone ahead and began building the FOG server on our production side. Again though, I’m stuck on breaking DNS once DNSMasq is installed. I don’t remember how I got around this before to do the DNSMasq build/upgrade to 2.76 unfortunately…
You had mentioned disabling dnsmasq from taking over DNS through ltsp.conf. Here is my current running ltsp.conf:
Don't function as a DNS server: port=0 # Log lots of extra information about DHCP transactions. log-dhcp # Set the root directory for files available via FTP. tftp-root=/tftpboot # Disable re-use of the DHCP servername and filename fields as extra # option space. That's to avoid confusing some old or broken DHCP clients. dhcp-no-override # inspect the vendor class string and match the text to set the tag dhcp-vendorclass=BIOS,PXEClient:Arch:00000 dhcp-vendorclass=UEFI32,PXEClient:Arch:00006 dhcp-vendorclass=UEFI,PXEClient:Arch:00007 dhcp-vendorclass=UEFI64,PXEClient:Arch:00009 dhcp-match=set:ParallelsEFI,97,00:ef:e3:6d:16:10:6f:46:9d:87:12:5a:12:c2 # Set the boot file name based on the matching tag from the vendor class (above) dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,10.100.10.22 dhcp-boot=net:UEFI,ipxe.efi,,10.100.10.22 dhcp-boot=net:UEFI64,ipxe.efi,,10.100.10.22 dhcp-boot=tag:UEFI,tag:ParallelsEFI,intel.efi,10.100.10.22,10.100.10.22 # The boot filename, Server name, Server Ip Address dhcp-boot=undionly.kpxe,,10.100.10.22 # PXE menu. The first part is the text displayed to the user. The second is t$ pxe-prompt="Booting FOG!",1 pxe-service=X86PC, "Boot to FOG", undionly.kpxe pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi dhcp-range=10.100.10.22,proxyHere is my NetworkManager.conf where I removed the “DNS=DNSMASQ” line:
[main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=falseI noticed that I get a new connection named en32 when I install DNSMasq (or somewhere along the lines of installing FOG and DNSMasq). I went in that connections settings and saw 127.0.0.1 as the DNS entries so I updated them to our proper DNS entries, reset networkmanager and dnsmasq services, but still could not ping google but 8.8.8.8 pinged fine. Any ideas?
-
@Merilious if your DNS is behind a domain you may need to add the domain name to search from. Just a theory no real clue though.
-
@Merilious said in Dell Inspiron 15 7559:
port=0
It looks like @Quazz has a solution for this here: https://forums.fogproject.org/topic/7193/ubuntu-14-04-lts-with-dnsmasq-no-external-dns/8
I did a little research on this and specifically the command “port=0” and its working as designed (??). From Quazz’s post it looks like you just need to adjust the dnsmasq startup scripts to not throw 127.0.0.1 into the resolv.conf file.
-
So that did the trick! I added that line and got both EFI and BIOS to boot up to FOG. One thing always needs to another though…
I tried doing a quick registration for each BIOS and EFI. BIOS goes through just fine, but the EFI gets stuck at bzIMAGE… 0%. I tried going in to the FOG web portal and updating the kernel but it still won’t budge. Any ideas?
-
@Merilious said in Dell Inspiron 15 7559:
but the EFI gets stuck at bzIMAGE… 0%.
This is an issue with (around) the iPXE kernel for efi. What file name are you sending for a efi system? ipxe.efi?
If so, for grins try this iPXE kernel instead: ipxe7156.efi Sometimes we’ll find hardware with flaky firmware (not so much Dells). Also make sure your firmware is up to date on that device.
-
I tried both the ipxe7156.efi and the intel.efi. Both had the same effect. Looked in the syslog and here’s the print out of one of the attempts. Just for verification I went in to the ltsp and changed all bootfile options to either the ipxe7156.efi or intel.efi. The one thing that pops out a little is the line saying
Apr 28 10:33:54 fogprod in.tftpd[24188]: tftp: client does not accept optionsApr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 vendor class: PXEClient:Arch:00007:UNDI:003016 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 PXE(ens32) 00:1c:42:9a:b9:f7 proxy Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 tags: UEFI, ens32 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 next server: 10.100.10.22 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 broadcast response Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size: 1 option: 53 message-type 2 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size: 4 option: 54 server-identifier 10.100.10.22 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 Apr 28 10:33:50 fogprod dnsmasq-dhcp[24056]: 1914483971 sent size: 17 option: 97 client-machine-id 00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba... Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1914483971 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1914483971 vendor class: PXEClient:Arch:00007:UNDI:003016 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 vendor class: PXEClient:Arch:00007:UNDI:003016 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 PXE(ens32) 00:1c:42:9a:b9:f7 proxy Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 tags: UEFI, ens32 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 bootfile name: ipxe7156.efi Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 server name: 10.100.10.22 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 next server: 10.100.10.22 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size: 1 option: 53 message-type 5 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size: 4 option: 54 server-identifier 10.100.10.22 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 Apr 28 10:33:53 fogprod dnsmasq-dhcp[24056]: 1049156094 sent size: 17 option: 97 client-machine-id 00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba... Apr 28 10:33:54 fogprod in.tftpd[24188]: tftp: client does not accept options Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 vendor class: PXEClient:Arch:00009:UNDI:003010 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 user class: iPXE Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 PXE(ens32) 00:1c:42:9a:b9:f7 proxy Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 tags: UEFI64, ens32 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 next server: 10.100.10.22 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 broadcast response Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 1 option: 53 message-type 2 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 4 option: 54 server-identifier 10.100.10.22 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 17 option: 97 client-machine-id 00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba... Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 vendor class: PXEClient:Arch:00009:UNDI:003010 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 user class: iPXE Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 vendor class: PXEClient:Arch:00009:UNDI:003010 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 user class: iPXE Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 PXE(ens32) 00:1c:42:9a:b9:f7 proxy Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 tags: UEFI64, ens32 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 bootfile name: ipxe.efi Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 server name: 10.100.10.22 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 next server: 10.100.10.22 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 1 option: 53 message-type 5 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 4 option: 54 server-identifier 10.100.10.22 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 Apr 28 10:33:59 fogprod dnsmasq-dhcp[24056]: 3502022152 sent size: 17 option: 97 client-machine-id 00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba... Apr 28 10:36:55 fogprod in.tftpd[24329]: tftp: client does not accept options Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 vendor class: PXEClient:Arch:00009:UNDI:003010 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 user class: iPXE Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 PXE(ens32) 00:1c:42:9a:b9:f7 proxy Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 tags: UEFI64, ens32 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 next server: 10.100.10.22 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 broadcast response Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 1 option: 53 message-type 2 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 4 option: 54 server-identifier 10.100.10.22 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 17 option: 97 client-machine-id 00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba... Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 vendor class: PXEClient:Arch:00009:UNDI:003010 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 user class: iPXE Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 available DHCP subnet: 10.100.10.22/255.255.255.0 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 vendor class: PXEClient:Arch:00009:UNDI:003010 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 user class: iPXE Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 PXE(ens32) 00:1c:42:9a:b9:f7 proxy Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 tags: UEFI64, ens32 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 bootfile name: ipxe.efi Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 server name: 10.100.10.22 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 next server: 10.100.10.22 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 1 option: 53 message-type 5 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 4 option: 54 server-identifier 10.100.10.22 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 Apr 28 10:36:59 fogprod dnsmasq-dhcp[24056]: 3812542537 sent size: 17 option: 97 client-machine-id 00:7c:9f:53:d6:94:0e:4c:00:b1:f3:2c:59:ba... -
So I’ve gone through all the combos that I could find between the boot files found in tftpboot and the NICs provided by the Parallel VM options.
Bootfiles tried:
intel.efi
intel7156.efi
ipxe.efi
ipxe7156.efi
realtek.efi
realtek7156.efi
snp7156.efi
snp.efi
snponly.efi
snponly7156.efiNIC options:
Intel PRO/1000 MT
Intel Gigabit CT (82574L)
Realtek RTL8029AS
Virtio network adapterSome would fail to get to the FOG boot screen. Most would get the previously stated bzIMAGE… 0 to 1%. A few got slightly further but would fail at this part:
-
@Merilious So just to be clear this issue is with your Parallel VM and not with the Dell?
-
For now yes…I shamefully forgot my Dell test laptop at home. That’d be the big test to see if I can get that to register with FOG. Will post here soon as I get that test done. Thanks a bunch for all the info!
-
@Merilious That is fine, I just wanted to be clear because something with the parallel vm may be causing your specific issue with bzImage not downloading correctly. We typically see strangeness like this with host systems with flaky uefi firmware.
Be sure to let us know on the Inspiron.
-
Fired up my test Dell Inspiron 7559 through UEFI boot and it first failed but that was my fault. I forgot to undo all the changes to the ltsp.conf I had done on Friday. After I changed the boot files all back to ipxe.efi the Dell 7559 booted just fine to the FOG menu and also successfully registered with the FOG server using the quick registration. I guess your assumption was correct about the funky setup of the Parallels UEFI VMs. BIOS works GREAT on those VMs, it’s just the EFI boot that doesn’t get through the bzImage phase.
