IPXE Invalid Arguments



  • Since September I have been having no issues with FOG until today. When I tried to Fog a client I get an IP address then after some text flashes across the screen I see something to the effect "cannot boot: invalid argument ipxe.org/1c1c2002. At ipxe.org that error is unsurprisingly invalid argument.

    I did some troubleshooting by using some test that Junkhacker recommended in the thread “PXE issues?”

    1. Does default.ipxe exisit in the tftpboot directory? - yes
    2. Does the line chain http://… look correct? - yes
    3. When you go to the website listed in the chain command what do you see? - I see a php text file. OK that is not what he said to expect.

    Next bit of troubleshooting. I booted from a ipxe live cd. I issued the dhcp command to get an address then the chain command in the default.ipxe file. I got the following error:
    colour:command not found
    could not boot: Exec format error(http://ipxe.org/2e022001)

    At ipxe that error is an improper command or argument. Checking the php doc I got in step 3 above I see the command colour --rgb 0xff0000 0

    Did something change so the English way of spelling no longer works? How can I correct this issue? Or am I missing something else?

    version 1.20 on ubuntu 12.04.5 LTS server

    Mark



  • https://rom-o-matic.eu , to build my ipxe.iso.
    I’m guessing that I’m missing some build options that deal with the command tools.
    Have any of you used this site before to build your ISO? If so can you tell me what option(s) I must select in order to rectify this issue?


  • Developer

    the error code you mentioned references a frame buffer console initialization function of the ipxe codebase, so i’d be pretty surprised if Tom was incorrect.



  • Before I try Tom’e suggestion I wanted to update the thread. I found a forum thread about issues with the DC7800 from June, 2014. The solution provided was to replace undionly.kpxe with undionly.kkpxe. It worked for that user and another user stated they had not had issues with DC7800’s. I tried the change and I get the same error as before.

    Tom. the fact you mentioned a frame/console buffer had me check my video of the error messages and I see that there is an error message “Could not configure Console Invalid Argument”. This adds weight to your suggestion. However before I proceed I need to determine how many of these PC’s I have to Fog and if it is a single device causing the error of a whole group. No need to spend hours on one device if that is the only one effected.


  • Senior Developer

    My guess is it’s dealing with the Console/Frame buffer.

    If you want, you can try SVN directly to see if it will help you out.



  • Here’s and update. It is not the Fog installation because I can Fog other devices. So it must be something specific to the PC. It is an HP Compaq DC7800 small form factor. I will do some research in the forums to see if I can find out what it could be.



  • When I say the output is a text file, what I meant was that a text file was displayed in the browser window. I copied it:

    http://192.168.1.30/fog/service/ipxe/bg.png --left 100 --right 80
    :MENU
    menu
    colour --rgb 0xff0000 0
    cpair --foreground 0 3
    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.sysinfo Client System Information (Compatibility)
    choose --default fog.local --timeout 3000 target && goto ${target}
    :fog.local
    sanboot --no-describe --drive 0x80 || goto MENU
    :fog.memtest
    kernel memdisk iso raw
    initrd memtest.bin
    boot || goto MENU
    :fog.reginput
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=192.168.1.30/fog/ consoleblank=0 loglevel=4 mode=manreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.reg
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=192.168.1.30/fog/ consoleblank=0 loglevel=4 mode=autoreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.sysinfo
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=192.168.1.30/fog/ consoleblank=0 loglevel=4 mode=sysinfo
    imgfetch init_32.xz
    boot || goto MENU
    autoboot

    %(#000000]
    So if I understand correct when you say)[
    All the error you’re seeing means is that the ipxe.iso you have does not have the command tools built into it.]
    You are talking about the ISO I used on the live CD, which is not the same as the using the ipxe in Fog?

    I am doing some more troubleshooting this morning and see if I can narrow down what is happening. One think I will do is try to Fog a client that was Fogged last week.


  • Senior Developer

    http://… look correct? - yes
    http://ipxe.org/2e022001)

    At ipxe that error is an improper command or argument. Checking the php doc I got in step 3 above I see the command %(#000000]colour --rgb 0xff0000 0[/quote]
    colour --rgb 0xff0000 0 is the correct syntax

    @Mark Carrara, post)[Did something change so the English way of spelling no longer works? How can I correct this issue? Or am I missing something else?]

    version 1.20 on ubuntu 12.04.5 LTS server

    Mark

    The english spelling never worked. iPXE was never coded using US English syntax. All the error you’re seeing means is that the ipxe.iso you have does not have the command tools built into it.


Log in to reply
 

424
Online

38715
Users

10543
Topics

99813
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.