public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 7/9] report: add info of the mainboard in use
Date: Thu, 11 Apr 2024 19:14:24 +0200	[thread overview]
Message-ID: <a82b50b58e795e5555623c720d9d9448e8239bf5.camel@proxmox.com> (raw)
In-Reply-To: <1858f426-47cc-41cf-bbc4-523ab2bff4e9@proxmox.com>

On Fri, 2024-03-22 at 15:26 +0100, Aaron Lauterer wrote:
> If we add more info, then dmidecode -t {1,2,3} might be interesting as 
> well as those deliver motherboard, system and chassis infos.
> 
> If you want to see what you get there, run them on some decent servers 
> as most consumer boards and systems will not show useful information here

Thanks! I've now looked at the output from different servers/motherboards
from the past years (ASUS, Dell, GIGABYTE, HP, 2x Supermicro).


In the system and base board output there was (only) the following
relevant information:

System Information
	Manufacturer: Thomas-Krenn.AG
	Product Name: RS700-E11-RS12U 1HE Intel Dual-CPU RI2112-ASXSN Server CHECKLISTE
	Version: 00
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: Z13PP-D32 Series
	Version: 60SB09M0-SB0G11

But to avoid blindness, and since the unfiltered output is not that long,
we could include it as a whole.


The chassis output contains several potentially interesting lines. So we
could include that as a whole too:

Handle 0x0300, DMI type 3, 21 bytes
Chassis Information
->	Manufacturer: HP
->	Type: Rack Mount Chassis
	Lock: Not Present
	Version: Not Specified
	Serial Number: (...)
	Asset Tag:
->	Boot-up State: Critical
->	Power Supply State: Critical
->	Thermal State: Safe
	Security Status: Unknown
	OEM Information: 0x00000000
	Height: 2 U
->	Number Of Power Cords: 2
	Contained Elements: 0

> 
> On  2024-03-22  14:59, Alexander Zeidler wrote:
> > Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> > ---
> >   PVE/Report.pm | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/PVE/Report.pm b/PVE/Report.pm
> > index 3a81bdb2..f28d7b38 100644
> > --- a/PVE/Report.pm
> > +++ b/PVE/Report.pm
> > @@ -104,6 +104,7 @@ my $init_report_cmds = sub {
> >   	hardware => {
> >   	    order => 70,
> >   	    cmds => [
> > +		'cd /sys/devices/virtual/dmi/id; cat board_vendor board_name',
> >   		'dmidecode -t bios -q',
> >   		'lscpu',
> >   		'lspci -nnk',





  reply	other threads:[~2024-04-11 17:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 13:59 [pve-devel] [PATCH manager 1/9] report: add kernel command line including boot time Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 2/9] report: add `jobs.cfg` to debug related network/load/backup/etc issues Alexander Zeidler
2024-03-25  8:08   ` Thomas Lamprecht
2024-04-11 17:07     ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 3/9] report: add list of upgradable packages Alexander Zeidler
2024-03-25  8:02   ` Thomas Lamprecht
2024-04-11 17:08     ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 4/9] report: add `apt-cache policy` to list recognized APT sources Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 5/9] report: move `lscpu` & cluster info to more appropriate sections Alexander Zeidler
2024-03-25  8:11   ` Thomas Lamprecht
2024-04-11 17:12     ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 6/9] report: switch `dmidecode` to quiet to omit almost never needed info Alexander Zeidler
2024-03-25  8:20   ` Thomas Lamprecht
2024-04-11 17:13     ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 7/9] report: add info of the mainboard in use Alexander Zeidler
2024-03-22 14:26   ` Aaron Lauterer
2024-04-11 17:14     ` Alexander Zeidler [this message]
2024-03-22 13:59 ` [pve-devel] [PATCH manager 8/9] report: add info about (un)used memory slots Alexander Zeidler
2024-03-22 18:05   ` Alexander Zeidler
2024-03-22 13:59 ` [pve-devel] [PATCH manager 9/9] report: add microcode info to better assess possible system impacts Alexander Zeidler
2024-03-22 16:44   ` Stoiko Ivanov
2024-03-22 18:54     ` Alexander Zeidler
2024-03-25  9:00   ` Thomas Lamprecht
2024-04-11 17:15     ` Alexander Zeidler
2024-03-25  7:52 ` [pve-devel] [PATCH manager 1/9] report: add kernel command line including boot time Thomas Lamprecht
2024-04-11 17:07   ` Alexander Zeidler
2024-04-11 17:20     ` Thomas Lamprecht
2024-04-18 15:57 ` Alexander Zeidler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a82b50b58e795e5555623c720d9d9448e8239bf5.camel@proxmox.com \
    --to=a.zeidler@proxmox.com \
    --cc=a.lauterer@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal