Dell Venue Pro 8 PXE boot issues



  • [quote=“rball01, post: 46196, member: 29220”]Ok, we are making progress, so far we see the FOG menu now, and we can select boot to hard disk and that works.

    but selecting any other option we first get two lines of text:
    /bzimage
    /init.xz…OK

    then it cycles back to the menu. Selecting any option other than boot to hard disk after that shows

    /init.xz…OK

    Then back to the menu again and repeat

    FOG does not seem to be honoring the FOG_PXE_MENU_TIMEOUT (always 3) and FOG_QUICKREG_AUTOPOP either - not sure if this is due to using SVN/Trunk

    Thanks again for your help[/quote]

    Set the hide-menu timeout and the menu timeout to 4 or 5.
    Also, the menu might be “There” but the graphics controller and/or monitor just hasn’t started showing it yet because it’s changing over.

    As soon as you see “initializing devices” on the screen, start hitting the down arrow. This will “Catch” the menu.



  • Ok, we are making progress, so far we see the FOG menu now, and we can select boot to hard disk and that works.

    but selecting any other option we first get two lines of text:
    /bzimage
    /init.xz…OK

    then it cycles back to the menu. Selecting any option other than boot to hard disk after that shows

    /init.xz…OK

    Then back to the menu again and repeat

    FOG does not seem to be honoring the FOG_PXE_MENU_TIMEOUT (always 3) and FOG_QUICKREG_AUTOPOP either - not sure if this is due to using SVN/Trunk

    Thanks again for your help



  • [quote=“rball01, post: 46192, member: 29220”]Ok, is there a certain file or group of files I should update, or is there a compiled install for trunk? Do I need to compile from source and reinstall?

    And thank you for your reply Tom, I really appreciate your help

    EDITI found the SVN on the Wiki, we are building another server to test

    Thanks,
    Rob[/quote]

    You can follow this: [url]http://fogproject.org/wiki/index.php/SVN[/url]


  • Testers

    As per SVN just download the latest trunk and rerun the installer.



  • Ok, is there a certain file or group of files I should update, or is there a compiled install for trunk? Do I need to compile from source and reinstall?

    And thank you for your reply Tom, I really appreciate your help

    EDITI found the SVN on the Wiki, we are building another server to test

    Thanks,
    Rob


  • Senior Developer

    It’s that reasoning I request you to update as that is already handled



  • Sure, how do I do that?

    Also, I got this back from the iPXE IRC if it helps.

    [COLOR=#000000][FONT=Consolas] topazdemon: it seems as though you don’t have PNG support enabled via IMAGE_PNG in general.h[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:24] <mcb30> Even if you did enable it, there’s no support for graphical framebuffers in UEFI iPXE yet[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:24] <mcb30> so you won’t be able to display the .png[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:25] <topazdemon> ok, could that cause all subsequent activity to fail?[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:25] <[COLOR=red]mcb30[/COLOR]> topazdemon: yes; iPXE scripts will exit on error[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:26] <mcb30> If you want a specific script line to ignore errors, you have to indicate how errors should be handled[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:26] <mcb30> e.g. “console -p bg.png ||”[/FONT][/COLOR]
    [COLOR=#000000][FONT=Consolas][11:26] <mcb30> would say to ignore errors[/FONT][/COLOR]


  • Senior Developer

    You willing to try out SVN/Trunk?



  • OK, progress is good. We re-downloaded the i386 efi files from the sourceforge trunk tftp folder and deleted the old ipxe.efi just to be safe.

    The new one seems to be working much better, maybe a copy error before?

    Now the error is different, see the attached picture. Looks like maybe UEFI [32 bit] binary is not there? or iPXE can’t understand the menu[ATTACH=full]1923[/ATTACH]

    [url="/_imported_xf_attachments/1/1923_fog error uefi 32 boot.png?:"]fog error uefi 32 boot.png[/url]



  • Ok, no legacy option on these unfortunately, even with safe boot turned off.

    I did get on IRC with the iPXE channel, and they gave me a 32 bit ipxe.efi which I dropped into the tftp folder. It was able to get to the iPXE prompt I am familiar with. The file is attached, just change the extension to .efi

    So next question is, is there a 32 bit efi binary that is programmed for FOG? It doesn’t seem to be an EFI issue, but rather a 32 vs 64 bit efi binary issue.

    Thanks,
    Rob

    [url="/_imported_xf_attachments/1/1921_ipxe.txt?:"]ipxe.txt[/url]



  • The last thing to check is to see if you can enable some sort of “Legacy” mode in the firmware of the target-device.

    Look for stuff like “UEFI”, “BIOS”, “LEGACY”, “Compatibility”, and “Legacy Rom”.

    Remember how it was before, and just poke around and see if you can change it from UEFI to BIOS. Then try the undionly.kpxe file with BIOS mode.



  • Thanks for your reply Wayne,

    I have pointed DHCP at all the efi files you mentioned, and intel.efi, also undionly.kpxe.INTEL as I saw suggested in another forum on another site. No dice.

    I changed all the permissions to the same as the undionly.kpxe file. Before that, I actually got an error message about reading the TFTP file or something, flashed very quickly. It seems like it gets the file now, but just ignores it.

    Updated the firmware “bios” to latest revision “A10”. Unfortunately, still only 32bit.

    I also tried plugging up to clonezilla, and it gets a tiny bit futher:

    “Succeed to download NBP. Getting Cached packet. My IP is xx.xx.xx.xx”, then just hangs forever.

    At this point, looking at WDS as a bandaid until I can get it working with FOG.



  • There are several EFI files to try.

    ipxe.efi
    snp.efi
    snponly.efi

    You’ll need to change your DHCP option 067 to point to each one to try it (looks like you have a handle on that part). I don’t believe there’s any need to restart any services for changing your boot file, although you might want to double check your permissions for the files you move around. They should have the same as the others, like undionly.kpxe

    Also, I’ve been heavily researching UEFI in the last month… 32bit UEFI support is sketchy at best… Maybe there’s a firmware update for this machine?

    Let us know how it goes.


Log in to reply
 

325
Online

5.8k
Users

13.1k
Topics

123.3k
Posts