ipxe login after upgrading to latest trunk + no such file or directory
-
@Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:
@Cavender Well if all that has been set and verified, then it should be fixed. If you can upload successfully, then it’s fixed.
That’s why I’m stumped. Registration / Imaging still says “no such file or directory” and I still get a login prompt for the main menu.
-
@Cavender Well the two are separate issues. However in another thread we may be onto something… Another person is having the same issue: https://forums.fogproject.org/topic/7774/default-ipxe/2
-
-
@Wayne-Workman said in [ipxe login after upgrading to latest trunk + no such file or directory](/topic/7763/ipxe-login-after-upgrading-
What boot file do you have set in DHCP?
subnet 172.16.0.0 netmask 255.255.255.0{
option subnet-mask 255.255.255.0;
range dynamic-bootp 172.16.0.10 172.16.0.254;
default-lease-time 21600;
max-lease-time 43200;
option routers 172.16.0.1;
option domain-name-servers 8.8.8.8;
next-server 172.16.0.33;
class “Legacy” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00000”;
filename “undionly.kkpxe”;
}
class “UEFI-32-2” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00002”;
filename “i386-efi/ipxe.efi”;
}
class “UEFI-32-1” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00006”;
filename “i386-efi/ipxe.efi”;
}
class “UEFI-64-1” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00007”;
filename “ipxe.efi”;
}
class “UEFI-64-2” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00008”;
filename “ipxe.efi”;
}
class “UEFI-64-3” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00009”;
filename “ipxe.efi”; -
Any more information on this?
-
Again? Anything to report for this?
-
@Tom-Elliott said in ipxe login after upgrading to latest trunk + no such file or directory:
Again? Anything to report for this?
I eventually went with a clean install of 14.04 and a new database and the problem went away. In that way it’s resolved on my end though I don’t know what was in my old database that could have caused this.
