iPXE input/output error (since update SVN 7687)



  • Hi,

    Using FOG in my university. Until last week we used 1.2.0 (and everything was great) but because of incompatibility with new hardware (DELL Optiplex 7040, Dell AIO 7440), we had to move the server from 1.2.0 to SVN.
    It seems to be the only solution for our new hardware work with FOG, according many of the posts.

    After the update to SVN last friday, no longer renaming of our clients, and following the posts here, we updated again our server this morning. BUT since, it’s worse…
    No reaction on the menu and the same error as in this post appears:

    https://forums.fogproject.org/topic/5510/svn-ipxe-input-output-error

    What happens during the update? Which files changed during the update?

    our clients are in legacy mode, pointing to undionly.kpxe.

    thx



  • @Tom-Elliott
    Indeed, last week was 7575 i think (but not sure) but now everything is ok.


  • Moderator

    Marking this thread solved.



  • Solved thx to SVN 7695 ;-)


  • Moderator

    @hernani said:

    Using FOG in my university. Until last week we used 1.2.0 (and everything was great) but because of incompatibility with new hardware (DELL Optiplex 7040, Dell AIO 7440), we had to move the server from 1.2.0 to SVN.

    Just for confirmation here, the above is true statement. You need to the FOS (the Fog Operating System that captures and deploys images on the target computers) kernels for new hardware support. These kernels are not available for 1.2.0 stable. If you plan on deploying win10, gpt disks, or uefi firmware you also need 1.2.0 trunk because the trunk version supports these features much better than 1.2.0 stable. So when you get there the trunk version gives you better client environment support all around.


  • Senior Developer

    Found the issue and it is now corrected for in the latest pull (7691 now).


  • Senior Developer

    Since update 7687?

    7687 wasn’t released until this morning. There is no possible way that you could’ve had these issues last week under this version.

    Because of the error, what’s in your apache error logs?


Log in to reply
 

364
Online

38989
Users

10712
Topics

101691
Posts

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