• Hello again,

    we all wonder about compatibility when we update FOG to the last version and we don’t all have the time to search the forum for our brand or just inform people on forum of our solutions.

    Could it be possible to add a “send anonymous data” that would bring back usage of tftp files and boot exit type with which computers brands and series of the FOG users ?
    This could be store to a database that would give us a list of what tftp file choose and what boot exit type ?

    Thank you.

  • I’ve created a table in FOG that does, more or this, exactly what’s being requested.

    Because of this, for the most accurate of data, please use the proper filenames as it’s the best method I can come up with.

    If you’re interested in finding out what files work and such, hence the idea behind the generation of this table, rather than setting your dhcp filename option to undionly.kpxe, start out with ipxe.pxe. Test your systems, and find out if the systems can boot under ipxe.pxe.

    If they can, there’s little more you need to do.

    If not all your systems work, then try the undionly.kpxe file. The table will read the new file name and create a new entry if it makes it into the menu. If it doesn’t make it into the menu it won’t enter it.

    The basic construct of the table currently is:

    Product, Manufacturer, Boot file, and mac address.

    It will not keep making entries in the table for every mac address. It will only make new entries if the filename, product, and the manufacturer does not already exist.

    This way, let’s say you changed undionly.kpxe to ipxe, you may end up with an entry for the same model of system for multiple files.

    The ideology of this table is to eventually allow centralized place for fog and the ipxe team to better know what systems work and with which files.

    Of course, when this gets entered, it will be completely optional to send this data to us.

    Once we have the “central” table setup, the table will allow us (the developers) to hopefully code in what systems and what files to use for those systems.

    For example, if we know the ipxe.pxe works for the Dell ts1700, and you’re booting to undionly.kpxe, We can supposedly cause the undionly.kpxe to rechain to ipxe.pxe. This would allow better operation of the nic during the ipxe state.

  • Hmm… not sure it’s so easy to do, or maybe the Wiki compatibility table can be re used for that (not so “automatic”). But the anonymous data would provide a view of how it’s setup, not necessarily how it’s working 🙂

    For Dells, so far, the basic .ipxe thing works, and exit strategy “grub” allows all models (including the T1700) to properly boot on disk after ipxe’d…