wok-current annotate dmidecode/description.txt @ rev 25095
Up libkeybinder (0.3.1)
author | Pascal Bellard <pascal.bellard@slitaz.org> |
---|---|
date | Sat Jun 18 13:48:16 2022 +0000 (2022-06-18) |
parents | |
children |
rev | line source |
---|---|
Hans-G?nter@24489 | 1 Dmidecode reports information about your system's hardware as described |
Hans-G?nter@24489 | 2 in your system BIOS according to the SMBIOS/DMI standard. |
Hans-G?nter@24489 | 3 This information typically includes system manufacturer, model name, |
Hans-G?nter@24489 | 4 serial number, BIOS version, asset tag as well as a lot of other details |
Hans-G?nter@24489 | 5 of varying level of interest and reliability depending on the manufacturer. |
Hans-G?nter@24489 | 6 This will often include usage status for the CPU sockets, expansion slots |
Hans-G?nter@24489 | 7 (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports |
Hans-G?nter@24489 | 8 (e.g. serial, parallel, USB). |
Hans-G?nter@24489 | 9 |
Hans-G?nter@24489 | 10 DMI data can be used to enable or disable specific portions of kernel code |
Hans-G?nter@24489 | 11 depending on the specific hardware. Thus, one use of dmidecode is for kernel |
Hans-G?nter@24489 | 12 developers to detect system "signatures" and add them to the kernel source |
Hans-G?nter@24489 | 13 code when needed. |
Hans-G?nter@24489 | 14 |
Hans-G?nter@24489 | 15 Beware that DMI data have proven to be too unreliable to be blindly trusted. |
Hans-G?nter@24489 | 16 Dmidecode does not scan your hardware, it only reports what the BIOS told |
Hans-G?nter@24489 | 17 it to. |