Lenovo Miix 700
-
Yes my dhcp option 67 is set and string value: undionly.kpxe
-
@arton This device is in UEFI mode, and requires a
.efiboot file. You’ll need to find one of fog’s .efi files that will work with this device. You can find a listing of possible files by running this command on your fog server:ls -lahRt /tftpboot | grep .efiHowever, most timesipxe.efiworks.You’ll probably also be interested in setting up BIOS and UEFI co-existence for your DHCP server so you can boot both BIOS and UEFI devices without having to change DHCP every-single-time. Instructions on this are here:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence -
Hi here is what i get when i run that command on my fog server
-
Right the NBP indicates this is a uefi device. In this case you need to use a uefi compatible boot kernel. As a suggestion, change your dhcp option 67 to ipxe.efi. Then pxe boot the target computer again.
FWIW, the undionly.kpxe is for bios (legacy) devices.
Looking at your ls command, ipxe.efi doesn’t exist. This IS an issue. Please confirm that you have ipxe.efi as well as about 4 others in that /tftpboot directory.
-
that all what i have on tftpboot directory
-
@arton Well that’s not right for 1.3.0-rcX series. Did you upgrade this install from a previous release? This looks a bit like a FOG 0.30 tftp directory.
How did you install 1.3.0? I assume you downloaded the installer from git or svn, then did you run the installfog.sh script in the bin directory?
-
yes what i did fallow the command on the how to upgrade so they it sad to make a Dir under root name fog-project then run the download svn then i did run installfog.sh from that directory.
Now when i look under fogproject/packages/tftp/ I see
-
@arton that’s very strange why the tftpboot directory is that why. Your screen shot contains what I would expect in the /tftpboot dir
Did the fog installer run to completion? Please run the installfog script again. If you are using a Debian based Linux you will need sudo then installfog.sh.
-
thank you i did run the install again now the tftpboot has all the files now i getting different error here is the picture
-
@arton Did the installer complete?
-
yes it did finish completely
-
@arton What’s doing DHCP there? Did you follow the article I posted earlier? Do you hae PortFast enabled on your switch? Can you try to place a mini-switch between the computer and the building network?
-
i dont see any post about port fast on network
-
@arton Can you answer the other questions please?
-
yes i can put a mini switch between building network and pc i let y know the results
-
here is the error
-
@arton This last picture is what I might expect to see from pxe booting a bios (legacy) system with undionly.kpxe (not an uefi boot, it doesn’t matter but just trying to set the context). Is this the case? I’m still getting the impression that your install is broken.
What I want you to do next is to (with a web browser) key in http://192.168.15.187/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00 and post the results here. Ideally this should display the FOG ipxe boot menu in its entirety (> 20 lines of stuff). If you get 3 or 4 lines and that is it, then we will need you to post (tail) the apache error log because something is broken.
-
The calls look good in the last picture, is the firewall on for the fog server? What OS is it running?
-
#!ipxe
set fog-ip 192.168.15.187
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
iseq ${platform} efi && set key 0x1b || set key 0x01
iseq ${platform} efi && set keyName ESC || set keyName CTRL + A
prompt --key ${key} --timeout 3000 Booting… (Press ${keyName} to access the menu) && goto menuAccess || exit
:menuAccess
login
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param username ${username}
param password ${password}
param menuaccess 1
param debug 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://192.168.15.187/fog/service/ipxe/boot.php##paramsServer is Ubuntu 14.04 LTS
-
@arton Just for clarity what were you trying to do when it created this menu? Were you trying to boot an unregistered device into the FOG iPXE menu or were you trying to deploy to this device?
The reason why I ask is that this menu isn’t complete. It has more lines than I expected but it isn’t what I expected. We may need to have the developers look at this.
I would have expected something like this based on the command I gave you
#!ipxe set fog-ip 192.168.1.88 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set colour --rgb 0x00567a 1 || colour --rgb 0x00567a 2 || colour --rgb 0x00567a 4 || cpair --foreground 7 --background 2 2 || goto MENU :alt_console cpair --background 0 1 || cpair --background 1 2 || goto MENU :get_console console --picture http://192.168.1.88/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console :MENU menu colour --rgb 0x00567a 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap Host is NOT registered! item --gap -- ------------------------------------- item fog.local Boot from hard disk item fog.memtest Run Memtest86+ item fog.reginput Perform Full Host Registration and Inventory item fog.reg Quick Registration and Inventory item fog.deployimage Deploy Image item fog.multijoin Join Multicast Session item fog.sysinfo Client System Information (Compatibility) item mdtlti.x86 MDT LiteTouch x86 Boot item winpe7a WinPE tester choose --default fog.local --timeout 3000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.88/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 imgfetch init_32.xz boot || goto MENU :fog.memtest kernel memdisk iso raw initrd memtest.bin boot || goto MENU kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.88/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 imgfetch init_32.xz boot || goto MENU :fog.reginput kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.88/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg imgfetch init_32.xz boot || goto MENU :fog.reg kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.88/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg imgfetch init_32.xz boot || goto MENU :fog.deployimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.88/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :mdtlti.x86 initrd http://192.168.1.88/fog/iso/LiteTouchPE_x86.iso chain memdisk iso raw :winpe7a initrd http://192.168.1.88/fog/iso/winpe_amd64.iso chain memdisk iso raw :bootme chain -ar http://192.168.1.88/fog/service/ipxe/boot.php##params || goto MENU autobootSince you are running ubuntu can you tail the apache error log. I think its called error.log.
One last question, was this system upgraded or did you install it new?Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
