レナート   TBFKAYIBYNYAAYB   ﻟﻴﻨﺎﺭﺕ

Fri, 06 Nov 2009

Public Service Announcement

Folks! Since quite some time now the kernel exports the DMI machine information below /sys/class/dmi/id/. You may stop now parsing the output of dmidecode thus depending on external tools and privileged code.

For example, to read your BIOS vendor string all you need to do is this:

$ read bv < /sys/class/dmi/id/bios_vendor
$ echo $bv

Which is of course much simpler, and cleaner, and safer than anything involving dmidecode.

Thank you for your time!

posted at: 11:14 | path: /projects | permanent link to this entry | 5 comments


Posted by S Wild at Fri Nov 6 15:15:19 2009
If you're using Linux, presumably.  We don't all do that...

Posted by Tim Bosse at Fri Nov 6 15:28:25 2009
This may be true for most modern distributions, however, RHEL5 based distributions will most likely not have this (I wasn't able to it).

Do you have a suggestion other than dmidecode in this case?  Keep in mind, using packages or source outside of official repositories is not an option for some--if not most--who use RHEL-ish distributions.

Posted by robbat2 at Fri Nov 6 16:34:07 2009
There's a lot of DMI info that's not present in that directory yet.

DMI Type - name (grouped related fields)

0 - BIOS, Characteristics field missing
4 - CPU
5,6 - Memory Controller/Memory Module
7 - Cache
8 - Port Connector
9 - System Slot
10 -  On Board Device
15 - System Event Log
16,19,17,20 - Physical Memory Array/Memory Array Mapped Address/Memory Device/Memory Device Mapped Address
32 - System Boot Information

Type 7 (cache) is partially represented elsewhere in the kernel, and Type 9 was intended to be represented by the pci_slots module, but that doesn't seem to work.

5,6 and 16,19,17,20 both useful combined and separate.

Of these missing ones, I've used them as follows:
5,6,8,9 - seeing what free slots/connectors are available for use remotely. (Eg: Can I install more RAM? What type?)
16,19,17,20 - Combined with memtest86, identifying a bad DIMM.

Posted by Marco Diego Aurélio Mesquita at Sat Nov 21 17:55:06 2009
Hi!

This is absolutely off-topic here, but I did not find othe way to talk to you, so I am posting my idea here.

There's currently a problem with audio on linux: real-time (pro or semi-pro) applications use jack, while desktop applications have no problem with pulseaudio. The problem comes when we need to run both kinds of applications! Switching between jack and pulse audio is no simple for the average user; setting pulse audio to redirect its output to jack, much less.

What I propose is that jack and pulseuadio should agree with a protocol:
  If jackd comes up and pulse is already running, then jackd should say: "Hey pulse I am here! Send-me your output and I'll the input you need!"
  If pulseaudio comes up and jackd is already running, then pulse should say: "Hey jack, give me the input I need and I'll give my output."
  If jackd must go away and pulseaudio is running, then it must say: "Hey pulse, I'm going. Take the sound card to you."

Is it possible? Is it do-able? Would pulseaudio and jack developers agree with this?

Posted by Mathieu at Sun Dec 20 14:26:03 2009
Wow didnt know DMI info was present there! Thanks for the hint.

Leave a Comment:

Your Name:


Your E-mail (optional):


Comment:


As a protection against comment spam, please type the following number into the field on the right:
Secret Number Image

Please note that this is neither a support forum nor a bug tracker! Support questions or bug reports posted here will be ignored and not responded to!


It should be obvious but in case it isn't: the opinions reflected here are my own. They are not the views of my employer, or Ronald McDonald, or anyone else.

Please note that I take the liberty to delete any comments posted here that I deem inappropriate, off-topic, or insulting. And I excercise this liberty quite agressively. So yes, if you comment here, I might censor you. If you don't want to be censored your are welcome to comment on your own blog instead.


Lennart Poettering <mzoybt (at) 0pointer (dot) net>
Syndicated on Planet GNOME, Planet Fedora, planet.freedesktop.org, Planet Debian Upstream. feed RSS 0.91, RSS 2.0
Archives: 2005, 2006, 2007, 2008, 2009, 2010

Valid XHTML 1.0 Strict!   Valid CSS!