HP 8300 Elite All-in-One with Intel 82579LM iPXE loading problem



  • Hello all

    I am having a problem with iPXE and a specific model of machine and Ethernet adaptor: HP 8300 Elite All-in-One (AIO) with the Intel 82579LM Gigabit Ethernet Controller (Intel Boot Manager v1.3.81)

    http://www.fogproject.org/wiki/index.php/Building_undionly.kpxe): but no change
    http://www.fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0) but again, I don’t think I totally understand what it going on here, so wasn’t a help yet
    error.txtfoginstall.txt



  • https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/quote]

    That’s awesome, Tom. We love FOG here at our School (and so does my brother at his School) and I’m glad I’ve been able to contribute.


  • Senior Developer

    The IMAGE_TRUST_CMD is not referring to “images” in the sense of FOG, but rather literal “images” such as Pictures. So having it or not having it shouldn’t really matter.

    They are rebuilt in SVN Trunk:
    https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/



  • Just to confirm: it’s IMAGE_TRUST_CMD commented out.

    It’s worth a try, even as a test for others with trouble with similar model Intel NICs. I’m at home at the moment, but I’ll post my iPXE config files / undionly.kpxe next week.

    FOG menu appears to all be working OK, but I haven’t got the storage node up yet to test an upload and download of images yet. I’m worried that this definition might be doing something else that is broken by leaving it out.

    I’ll test an uploads/downloads next week and report back.

    Thanks for your reply, Tom.


  • Senior Developer

    Okay, I’ll rebuild with image_trust_cmd, maybe we’ll see more success with others?



  • SUCCESS!! Again… :)

    OK, I feel a little silly about the ugly menu above now. Becuase I didn’t initially edit any of the config files before doing a build, some settings were left out. I realized, as soon as I opened up %(#0000ff]console.h that line 25 was still commented out)[]

    #define    CONSOLE_VESAFB        /* VESA framebuffer console */
    

    %(#0000ff]meaning the vesa console menu wouldn’t be able to load properly, hence my ugly menu above. Kinda reminds me of the ol’ DOS days…

    []

    Now I have functioning AND pretty FOG menu! I’m now going to set up a storage node at each of our campuses (seperated by a WAN link) for imaging at both locations from the one main FOG server.

    I hope these posts help someone else around the 'net in the future.

    Thanks again FOG!



  • SUCCESS! Well sort of…

    What I have now is a fully this process as I did above, except this time, I only edited the %(#0000ff]ipxescript file)[general.h], %(#0000ff]console.h or settings.h files before building. I ran make and copied the reuslting files to /tftpboot and voila! The painful 8300 boots and gets to the above working, but ugly FOG boot menu!

    The line that causes the HP 8300 Elite All in One with the 82579LM NIC to freeze is line 145 of general.h

    #define IMAGE_TRUST_CMD   /* Image trust management commands */
    

    If I comment out this line and rebuild, the 8300 boots OK. Leave it un-commented, and the 8300 hangs as in my first post.

    The contents of my working ipxescript file are)[]

    #!ipxe
    sync --timeout 500
    dhcp || reboot
    cpuid --ext 29 && set arch x86_64 || set arch i386
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    :bootme
    chain http://10.0.115.43/fog/service/ipxe/boot.php##params
    

    This is a combination of the lines recommened on the Wiki how to page, what’s is in default.ipxe and another I have seen around the 'net. So far, changes in this file make no difference to the outcome of the build.

    So what does this all mean? I hoping a one of the developers can explain, becuase it’s getting over my head! It may also need to be something to take over to the iPXE forums…



  • @Jaymes Driver, post: 31265, member: 3582 said:

    Have you tried to Undionly.kpxe.INTEL version yet? Normally we would recommend this if it was flashing an error, but to me it seems it never get far enough to error out. I am curious to figure out why.
    Sorry, I omitted that one in my original post. Yes, I tried that one first and again just now to make sure, but the same problem.
    @Jaymes Driver, post: 31265, member: 3582 said:
    Thanks for all your documentation on your troubleshooting steps, it really help sot visualize what is going on.

    Thank you for your reply and help!


  • Developer

    Have you tried to Undionly.kpxe.INTEL version yet? Normally we would recommend this if it was flashing an error, but to me it seems it never get far enough to error out. I am curious to figure out why.

    Thanks for all your documentation on your troubleshooting steps, it really helps to visualize what is going on.

    You could run this code, you are welcome to change the first line it is simply renaming your current undionly.kpxe we want to keep it since the rest of your network seems to like the file. This is a different version of the boot file and may help with resolution.

    
    sudo mv /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe.6.25
    wget -O /tftpboot/undionly.kpxe http://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe.INTEL
    

Log in to reply
 

477
Online

38710
Users

10537
Topics

99776
Posts

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