MikeMcGrath/HardwareProfiler

Hardware Profiler

Initial Release

For its initial release the hardware profiler will only gather harware information which could be linked to a bugzilla via a UUID. Information to be kept:

UUID	To idenfity individual machines
OS	Initially just /etc/redhat-release
lsbRelease	output from 'lsb_release'
Platform	i386/ppc/x86_64, etc
bogomips	An idea of CPU speeds
systemMemory	System Memory (total)
systemSwap	System Swap (total)
CPU Vendor	CPU Brand and model
language	Default language listed in /etc/sysconfig/i18n
defaultRunlevel	The default runlevel listed in /etc/inittab
vendor	System Vendor
system	System Model

Device Description	Description of the device
Class	Device class (USB, CDROM, audio)
Driver	Current loaded driver if known
Bus	Device Bus (PCI, IDE, etc)

Road Map

1. Automatic phone home (with opt out or opt in of course) 2. Add Some sort of reporting mechanism (Does everything work? If not, what is broken?) 3. Automate as much as possible 4. Keep a list of known crashes/problems and provide an answer to users having issues 5. Automatically link to bugzilla or something bugzilla-ish

Whats been done so far

http://publictest4.fedora.redhat.com/stats

http://publictest4.fedora.redhat.com/raw

To submit your profile:

wget -qO- http://mmcgrath.net/~mmcgrath/rhn/test.sh | bash

Comments

Have you looked at sysreport in Fedora Core or the next generation at https://sos.108.redhat.com/ ? - RahulSundaram

From thl:

• For certain hardware (Onboard-Sound and -Modems, maybe networks sometimes, too) the PCI-IDs are sometimes not a big help. Rather it's important that the codecs or the PHY that sits behind the PCI-device is supported by the driver, too.

• Some parts of hardware (the SATA-Controller on ICH-Southbridges for example) change thir ID based on a BIOS-setting (AHCI, RAID, native, compatible). What will we do about that?