9 replies to this topic

[Icecube]

HDT 0.3.4 has just been released.

Since April, due to some important changes, HDT was no more in sync with
Syslinux. The 0.3.4 release will solve that major issue and will be part
of Syslinux-3.83-pre8.

Beside this syncing with Syslinux, this release aims at solving disk's
detection bugs and improving the DMI reporting.

I would like to thank pam for that though work. He did most (who said
all ? )) the work needed for making that release existing.

Here come the changelog of 0.3.4:

- Add SMBIOS Memory Module Support (CLI)
Add `show module <module_nb>' in the DMI module to display
SMBIOS 3.3.7 Memory Module Information (Type 6, Obsolete).

- Add SMBIOS Cache Information (Type 7) (CLI)
'dmi> show cache <cache nb>' to get information about CPU cache devices
in the system.

- Add System Boot Information to System output (dmi) (CLI)
Output System Boot Information along System information, just like
dmidecode does.

- Only output Firmware Revision when present (dmi) (CLI)

- Add SMBIOS System Configuration Options (Type 12) (CLI)
Add type 12, displayed in the system summary.

- Add SMBIOS System Reset (Type 23) (CLI)
Add type 23, displayed in the system summary.

- Add SMBIOS On Board Devices Information (Type 10) (CLI)
Add information about devices found on the baseboard. Note that this is
displayed only if information about the baseboard itself can be
retrieved via SMBIOS Type 2.

- Add SMBIOS OEM Strings (Type 11) (CLI)
'dmi> show oem' to get information about OEM specific strings.

- Add SMBIOS Hardware Security Information (Type 24) (CLI)
'dmi> show security' to get information about the system-wide hardware
security settings.

- disklib
Re-implement the logic to parse extended partitions to correctly go
through the linked list of partitions.

Updated the CLI in hdt and tested it both on Qemu (Debian Lenny
installation) and on DELL E6400 (6 partitions).

Greetings goes to Gert for helping us pointing new bugs in that code.

- Make the menu and cli use the new disk interfaces

- Fixing one memory corruption that occurs on partitions' display
Thanks to Brian Hardbarger for reporting it.

Download:
http://konilope.linu...t/hdt_0_3_4.c32

Feel free to report any bugs/comments/ideas on HDT's mailing list:
http://www.zytor.com...an/listinfo/hdt

Erwan & Pierre.

http://www.zytor.com...ust/000043.html

HDT (for "Hardware Detection Tool") is a Syslinux com32 module designed to display low-level information for any x86 compatible system.

HDT can inspect multiple subsystems:

• CPU (via cpuid)
• PCI
• DMI

• Memory modules
• BIOS
• Motherboard
• IPMI base board
• Chassis
• Batteries
• CPU

• Disks (work in progress)
• Syslinux
• Linux Kernel modules needed by this host
• PXE environment
• VESA
• ...

HDT runs directly on the SYSLINUX bootloader. So it doesn't need to boot first into an operating system like DOS, linux or Windows.

Home page: http://www.hdt-project.org


Contents of syslinux.cfg:

DEFAULT hdt

PROMPT 0



LABEL hdt

COM32 hdt.c32

APPEND modules_pcimap=modules.pcimap modules_alias=modules.alias pciids=pci.ids

If you put modules.pcimap, modules.alias and pci.ids in another directory (e.g.: /hdt) than the syslinux.cfg, use this:

DEFAULT hdt

PROMPT 0



LABEL hdt

COM32 /hdt/hdt.c32

APPEND modules_pcimap=/hdt/modules.pcimap modules_alias=/hdt/modules.alias pciids=/hdt/pci.ids

In the attached file you can find all needed files:

hdt.c32 ==> Actual program

modules.alias

modules.pcimap

pci.ids

syslinux ==> Linux version of SYSLINUX installer

syslinux.cfg ==> example config for HDT

syslinux.exe ==> Windows version of SYSLINUX installer

Attached Files

•  hdt_0.3.4.zip   318.95KB   39 downloads

[Icecube]

See post #6 for the new way to create the image:
See post #9 for a newer floppy image build.

Original post:

To run it from GRUB4DOS you need to make a floppy image (2.88MB).

In Linux run the following commands with root rights:

mkfs.msdos -v -n HDT034 -C hdt034.img 2880

./syslinux hdt034.img

mkdir /tmp/hdt

mount -o loop hdt034.img /tmp/hdt



cp hdt.c32 /tmp/hdt

cp modules.alias /tmp/hdt

cp modules.pcimap /tmp/hdt

cp pci.ids /tmp/hdt

cp syslinux.cfg /tmp/hdt



umount /tmp/hdt



gzip -9 -c hdt034.img > hdt034.img.gz

For the lazy people, download the attached file (gzipped floppy image).

In your menu.lst, use:

title Hardware Detection Tool v0.3.4

map --mem /hdt034.img.gz (fd0)

map --hook

root (fd0)

chainloader (fd0)+1

[steelbone]

Hi there,

i have a litte Problem.

i tryed to build this image from the likemkfs.msdos Description.

i got this error:

""This is not a bootable disk. Please insert a bootable floppy and press any key to try again....""


i found a information that mkfs.msdos has a bug that it couldn't create bootable devices.

so my question how you @Icecube made this Image bootable?

Many thanks

[Icecube]

With the code in my second post (updated: uses the right filename now).

The following command will create a file hdt034.img which contains a FAT formatted floppy image of 2.88MB with "HDT034" as label.

mkfs.msdos -v -n HDT034 -C hdt034.img 2880

Install syslinux to this floppy image (will make it bootable):

./syslinux hdt034.img

[steelbone]

ah i see. thx

[Icecube]

There is a new way to generate a floppy image for HDT (no root rights needed). With some luck, this patch makes it into Syslinux 3.83.

It is now possible to build a bootable floppy image which contains HDT,
with my patch applied (with some help and modifications from Erwan) to Erwans HDT branch:


http://git.zytor.com...94243b71218d871

Unpack the Syslinux archive and build whole Syslinux first,
then cd to ./com32/hdt/ and make hdt.img

$ make
$ cd ./com32/hdt/
$ make hdt.img

Now you have a 2.88 MB floppy image which contains HDT (hdt.img),
which you can use to boot with MEMDISK or Grub4Dos floppy emulation.

MEMDISK:
========

LABEL hdtfloppy
LINUX memdisk
INITRD hdt.img

Grub4Dos floppy emulation:
==========================

title Hardware Detection Tool
map --mem /hdt.img (fd0)
map --hook
root (fd0)
chainloader (fd0)+1


You can also compress hdt.img with gzip (hdt.img.gz), which results
in a much smaller file (400KB compared to 2.88MB).

MEMDISK:
========

LABEL hdtfloppy
LINUX memdisk
INITRD hdt.img.gz

Grub4Dos floppy emulation:
==========================

title Hardware Detection Tool
map --mem /hdt.img.gz (fd0)
map --hook
root (fd0)
chainloader (fd0)+1




More info can be found in the README:

---------------------------
Creating a bootable floppy
---------------------------
To build a bootable HDT floppy image, you can do a "make hdt.img" call.
This will requires the mtools (http://mtools.linux.lu) to be installed.
The script will try to pick several files from your system :
- /lib/modules/`uname -r`/modules.alias
- /lib/modules/`uname -r`/modules.pcimap
- /usr/share/pci.ids or /usr/share/hwdata/pci.ids

This paths can be overrided with the following command line:
make MODULES_ALIAS_FILE=$(PWD)/floppy/modules.alias MODULES_PCIMAP_FILE=$(PWD)/floppy/modules.pcimap PCI_IDS_FILE=$(PWD)/floppy/pci.ids hdt.img

If your system doesn't have pci.ids, please download it from http://pciids.sourceforge.net/ and put it into the floppy/ directory.


Greetings,
- Gert Hulselmans

http://www.zytor.com...ber/000046.html

[steelbone]

Hello,

i have a little Problem.

i used the attached HDT Image.

the Problem is every time i try to boot over grub4dos i will get following error:


"Error 60: file for drive emulation must be in one contiguous disk area."


i tryed to fix with contig + wincontig but error still exists.

i'am not able to use the image.

Any hints on that?

thx

steel

[was_jaclaz]

You get that error using:

title Hardware Detection Tool v0.3.4
map --mem /hdt034.img.gz (fd0)
map --hook
root (fd0)
chainloader (fd0)+1

jaclaz

[Icecube]

In the attachment you can find a new gzipped floppy image (SYSLINUX 3.83 installed) which contains HDT 0.3.4.
It is not much different from the previous version.

Attached Files

•  hdt.img.gz   333.48KB   9 downloads

[steelbone]

;9

thx very much



i really forgot the --mem function.

i never asked this question *g*

thx

Steel