adding hdt.c32 in Core* ISOs

[genec]

I'm posting this in part on behalf of Erwan Velu, author of hdt.c32 (Hardware Detection Tool), a COM32 module for Syslinux.  He'd like to see if there's interest in adding hdt.c32 to some/all of the Core* ISOs.

To this, I'd add that if included, it could also be beneficial to take advantage of the pci.ids, module.alias, and modules.pcimap behavior, all of which can be GZIP compressed in the ISOs.  I'd see inclusion of these three as more likely for CorePlus.iso due to size.

[curaga]

You didn't list the sizes of all those components

[bmarkus]

Since the 3.74 release, the Syslinux project hosts the Hardware Detection Tool (HDT) project. This tool is a Syslinux com32 module that displays low-level information for any x86 compatible system. It provides both a command-line interface and a semi-graphical menu mode for browsing. HDT is available as a com32 file, a bootable ISO and a 2.88MB floppy disk.

Syslinux supports simple standalone programs, using a file format
similar to DOS ".com" files.  A 32-bit version, called COM32, is also
provided.  A simple API provides access to a limited set of filesystem
and console functions.

While it is interesting, I do not see any practical benefits to add.

[tinypoodle]

The way I understand it, such modules are discarded from memory together with the basic bootloader once latter hands over to the kernel.
If so, the only impact of size I can see would be on iso files.
Someone correct me if I overlooked or misunderstood anything...

[genec]

The way I understand it, such modules are discarded from memory together with the basic bootloader once latter hands over to the kernel.
If so, the only impact of size I can see would be on iso files.
Someone correct me if I overlooked or misunderstood anything...

You are 100% correct.  It only occupies RAM while running.

You didn't list the sizes of all those components

hdt.c32 from Syslinux-4.05 is 342452 B.  advdef -4 of current pci.ids is 187761 B.  advdev -4 of modules.alias is 14943 B.

[genec]

While it is interesting, I do not see any practical benefits to add.

I could certainly see a few. 

• Identifying problematic wireless is one.  Last I checked, I actually have to blacklist a Broadcom wireless driver from loading for some hardware if two of them are present.
• Identifying NICs requiring a firmware package.  Broadcom NetXtreme cards come to mind.
• Finding your forgotten/remapped TC partitions
• Identifying problematic graphics cards.  Perhaps special options are needed or you need to prevent XVesa from loading.

[gerald_clark]

All those can be done with the existing DVD.

[tinypoodle]

Can be done at current by loading extensions lspci, lsusb and friends.
The advantage would be that unlike extensions (or whatever is included in initramfs) this would have a zero memory cost when running in cloud mode.

[genec]

Can be done at current by loading extensions lspci, lsusb and friends.
The advantage would be that unlike extensions (or whatever is included in initramfs) this would have a zero memory cost when running in cloud mode.

Add to that the fact that you don't need to boot, find the offending hardware then reboot.  Load the boot loader, peek at hdt.c32, then boot once with the needed options.