Sample Header Ad - 728x90

SMBIOS Data Not Displayed Correctly by dmidecode and lshw

0 votes
0 answers
40 views
I'm encountering an issue where the dmidecode and lshw commands are not displaying the correct SMBIOS data on my Linux machine. **Most of the fields are showing up as "NONE".** **System Information:** - **Operating System:** Debian 12 Bookworm with Backported Kernel 6.11
root@DEB-NONE-NONE:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/ "
SUPPORT_URL="https://www.debian.org/support "
BUG_REPORT_URL="https://bugs.debian.org/ "
root@DEB-NONE-NONE:~# cat /etc/debian_version
12.8
root@DEB-NONE-NONE:~# uname -r
6.11.5+bpo-amd64
root@DEB-NONE-NONE:~#
- **BIOS Version:** American Megatrends International, LLC. E7000MBXX00004, dated 10/24/2024 - **SMBIOS Version:** 3.6.0 - **Machine Type:** Barabone machine with Intel(R) Core(TM) Ultra 7 165U - **CPU Details:**
root@DEB-NONE-NONE:~# lscpu
    Architecture:             x86_64
      CPU op-mode(s):         32-bit, 64-bit
      Address sizes:          46 bits physical, 48 bits virtual
      Byte Order:             Little Endian
    CPU(s):                   14
      On-line CPU(s) list:    0-13
    Vendor ID:                GenuineIntel
      BIOS Vendor ID:         Intel(R) Corporation
      Model name:             Intel(R) Core(TM) Ultra 7 165U
        BIOS Model name:      Intel(R) Core(TM) Ultra 7 165U NONE CPU @ 1.5GHz
        BIOS CPU family:      1
        CPU family:           6
        Model:                170
        Thread(s) per core:   2
        Core(s) per socket:   12
        Socket(s):            1
**Commands and Output:** **dmidecode:**
# dmidecode -t1
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.

Handle 0x0001, DMI type 1, 27 bytes
System Information
    Manufacturer: NONE
    Product Name: NONE
    Version: NONE
    Serial Number: NONE
    UUID: 11372406-101c-2f75-ffff-ffffffffffff
    Wake-up Type: Power Switch
    SKU Number: NONE
    Family: NONE
**lshw:**
root@DEB-NONE-NONE:~# lshw
deb-none-none
    description: Desktop Computer
    product: NONE (NONE)
    vendor: NONE
    version: NONE
    serial: NONE
    width: 64 bits
    capabilities: smbios-3.6.0 dmi-3.6.0 smp vsyscall32
    configuration: chassis=desktop family=NONE sku=NONE uuid=11372406-101c-2f75-ffff-ffffffffffff
  *-core
       description: Motherboard
       product: NONE
       vendor: NONE
       physical id: 0
       version: B
       serial: NONE
       slot: NONE
     *-firmware
          description: BIOS
          vendor: American Megatrends International, LLC.
          physical id: 0
          version: E7000MBXX00004
          date: 10/24/2024
          size: 64KiB
          capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd acpi biosbootspecification uefi
     *-memory
          description: System Memory
          physical id: 9
          slot: System board or motherboard
**Edited :** Based on my understanding, OEM manufacturers are responsible for storing hardware information, such as manufacturer, product name, and serial numbers, in a structured format in the SMBIOS (System Management BIOS) or BIOS during the manufacturing or assembly process. Linux tools, such as dmidecode and lshw, retrieve this information from the DMI tables within the SMBIOS. Here are the product details: Vecow SPC-9100 that we are currently using. Ref Link : https://www.vecow.com/dispPageBox/vecow/VecowCT.aspx?ddsPageID=PRODUCTDTL_EN&dbid=5111101416 I have cross-referenced the dmidecode and lshw commands with similar systems (Intel NUC and ASUS hardware). These systems correctly display SMBIOS/DMI fields under the same Linux environment. Intel NUC hardware
root@DEB-NUC11TNH-BTTN2290#######:~# dmidecode -t baseboard
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Intel Corporation
Product Name: NUC11TNBv5
Version: M11900-405
Serial Number: BTTN2290#######
Asset Tag:
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Asus hardware
root@DEB-NUC14RVS-S5ARYZ00X########:~# dmidecode -t system
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: NUC14RVS-B
Version: 90AR0051-M000E0
Serial Number: S5ARYZ00X########
UUID: a232847d-f66a-593e-40dd-88aedd65a6f4
Wake-up Type: Power Switch
SKU Number: NUC14RVS-B
Family: RV
This leads me to suspect that the problem might be OEM-specific and related to the Vecow SPC-9100 hardware. I am in touch with the product's OEM regarding this issue and have received the following response from them:
Vecow does not write any information to the DMI TABLE when the product is shipped.
However, is there still any possibility of addressing this using Linux tools or other methods?
Asked by Samadhan Fuke (21 rep)
Jan 13, 2025, 09:23 AM
Last activity: Jan 16, 2025, 12:58 PM