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?

I got two identical network cards in my server that I run Proxmox VE on. One of them is unclaimed, the other one is running fine. Can anyone help with this? I understand that unclaimed usually is a hint for a missing driver. But why does the second card work? Might this be a hardware failure? Thanks for any answer! lshw -class network Output: root@pve:~# lshw -class network *-network:0 UNCLAIMED description: Ethernet controller product: NetXtreme BCM5720 Gigabit Ethernet PCIe vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@0000:04:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm vpd msi msix pciexpress cap_list configuration: latency=0 resources: memory:91930000-9193ffff memory:91940000-9194ffff memory:91950000-9195ffff memory:91d40000-91d407ff *-network:1 description: Ethernet interface product: NetXtreme BCM5720 Gigabit Ethernet PCIe vendor: Broadcom Inc. and subsidiaries physical id: 0.1 bus info: pci@0000:04:00.1 logical name: eno2 version: 00 serial: 2c:ea:7f:e0:4a:59 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=6.2.16-3-pve duplex=full firmware=FFV21.60.8 bc 5720-v1.39 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s The entire dmesg output is available as [a gist](https://gist.github.com/ihrigb/db085235b837c8593f20be2032a10d48) but what I think are the relevant parts (dmesg | grep tg3) are here: [ 1.076509] tg3 0000:04:00.0: phy probe failed, err -19 [ 1.094731] tg3 0000:04:00.0: Problem fetching invariants of chip, aborting [ 1.117495] tg3 0000:04:00.1 eth0: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address 2c:ea:7f:e0:4a:59 [ 1.117499] tg3 0000:04:00.1 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed, EEE) [ 1.117500] tg3 0000:04:00.1 eth0: RXcsums LinkChgREG MIirq ASF TSOcap [ 1.117502] tg3 0000:04:00.1 eth0: dma_rwctrl dma_mask[64-bit] [ 1.125569] tg3 0000:04:00.1 eno2: renamed from eth0 [ 8.677752] tg3 0000:04:00.1 eno2: Link is up at 1000 Mbps, full duplex [ 8.677755] tg3 0000:04:00.1 eno2: Flow control is off for TX and off for RX [ 8.677756] tg3 0000:04:00.1 eno2: EEE is disabled [ 1190.696920] dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c hid_generic usbmouse usbhid hid xhci_pci xhci_pci_renesas intel_lpss_pci crc32_pclmul ahci spi_intel_pci i2c_i801 intel_lpss mpt3sas raid_class spi_intel i2c_smbus idma64 tg3 libahci xhci_hcd scsi_transport_sas video pinctrl_cannonlake wmi Kernel identifies at boot time with this message Linux version 6.2.16-3-pve (tom@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) () lspci | grep net Output: root@pve:~# lspci | grep net 04:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe 04:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe

I've been running Ubuntu 22.04 since it came out. The last reboot prior to the problem was 42 days with no issue. During that period I took all the updates that apt offered including kernel and firmware patches, but didn't reboot. I run Canonical's Livepatch (Landscape) so rebooting isn't critical, even if there are kernel security patches. After 42 days I did manually reboot for some logistical reason, and after boot several devices including Audio and Bluetooth show up in lshw as UNCLAIMED, and of course don't work. Their drivers don't show up in lsmod. How can I diagnose/fix this. I have to guess that some patch or kernel update is catching me, but there are many that went in during the 42 days.

I have been running Lubuntu on my old late 2008 Macbook successfully for a couple of years. This week, the WiFi has suddenly stopped working. Running lshw, lsusb and lspci shows no sign of the WiFi interface at all. I've run a full software update over ethernet, and restarted the system a couple of times, but to no avail. The fault appeared from one day to the next, and did not follow a software update or any other obvious change to the system. I'm leaning towards a hardware fault currently (it is a 15yo laptop, after all), but is there anything else I can do to try and diagnose/fix this fault?

Relevant to laptops only - I am trying to list all on-board (integrated) devices on laptops - such as on board keyboard, mouse touchpad, video card, etc shipped with the machine. 1. What is the best command for the job ? dmidecode, lspci, lshw ? Can all this data be extracted using a single tool ? For instance, I have not been able to locate any data pertaining to the on-board keyboard neither in dmidecode nor in lshw. lspci shows only a header line. 2. For the sake of understanding, do all such devices fall into the category of PCI devices - where each of them has its specific way to interface with the motherboard (ISA Bridge, IDE interface, different controllers, etc) ? I am testing this on a Lenovo EThink Pad 470

I have used mdadm, lspci -vvv, and lshw -c disk -c storage and I can seem to find the physical addresses of all my NVMEs as well as the logical addresses on the system (minus the missing drive), but I cant find anyway to link the information of nvme of PCIe bus 6.000 to nvme0n1 (just an example).

I have to extend my RAM memory, Because I need to use Android Studio.
I need to find out how many RAM slot via lshw command or greping /proc contents.I don't want to open my laptop.
How can I find out?

I recently acquired an older motherboard with SiS built-in graphics and installed Xubuntu on it. I wanted to challenge myself and see if I could figure out how to install a graphics driver for SiS. After a bit of work, I believe I actually managed to do just that by using [this](https://wiki.archlinux.org/index.php/SiS) guide with a few tweaks. I have come to the conclusion that I was successful because originally, */var/log/Xorg.0.log* was showing an error saying that the "sis" module I was trying to use failed to load. With a final tweak, */var/log/Xorg.0.log* was showing the "sis" module being successfully loaded, and the resolution of the display also increased. However, when I checked the output of lspci -v and lshw -c video, there was no reference to the sis driver. Do these commands always show the graphics driver being used? Am I wrong in thinking that I did this successfully?

I know commands like lshw and dmidecode, but all they do is list the detected hardware attributes, right? I can get all the information I want about the hardware in my computer. But I would also like to check if that device which has been detected is working properly or not. flathub…hw-probe from flatpak does the work, but it dumps the info into its online database/repo.  This is an example of it. Is there any way I can save this offline or redirect its output to somewhere else I like? Is there any tool which can do the same work offline?

I'm trying to mix two 4Gb DDR3 modules from G.Skill with another two 4Gb DDR3 from a generic Chinese brand called Ankowall. The BIOS detects all modules and automatically clocks them at 1333MHz but neither 64bit (Linux & Windows 10) nor memtest 86+ detect the 16Gb, only 8Gb. I've tried all combinations, testing each module and any combination of them in each slot. I've tried mixing a G.Skill module with an Ankowall module. They are compatible between different brands and the OSes detect the 8Gb no problem, clocking the modules at 1333MHz with no problems. But as soon as I plug another two modules the OSes don't detect more than 8Gb in any combination. So the problem seems to be with quad channel configuration maybe? I've also tried to force 1333MHz and 1066MHz in the BIOS, setting the memory voltage, the primary timings and secondary timings to no avail. Checked all the timings were correct in HWInfo64. I haven't tweaked the CPU values in the BIOS My CPU: INTEL i7-2600K My mobo:ASUS Maximus IV ExtremeZ Mem: Ankowall modules Here's the output of two memory diagnostics commands: dmidecode -t memory # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.6 present. Handle 0x0060, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 32 GB Error Information Handle: 0x0062 Number Of Devices: 4 Handle 0x005F, DMI type 17, 28 bytes Memory Device Array Handle: 0x0060 Error Information Handle: 0x0064 Total Width: 64 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: ChannelA-DIMM0 Bank Locator: BANK 0 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: 0080 Serial Number: 7A0F265B Asset Tag: 9876543210 Part Number: ANKOWALL Rank: 2 Handle 0x0061, DMI type 17, 28 bytes Memory Device Array Handle: 0x0060 Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: ChannelA-DIMM1 Bank Locator: BANK 1 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: 04CD Serial Number: 00000000 Asset Tag: 9876543210 Part Number: F3-17600CL9-4GBXLD Rank: 2 Handle 0x0066, DMI type 17, 28 bytes Memory Device Array Handle: 0x0060 Error Information Handle: 0x0065 Total Width: 64 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: ChannelB-DIMM0 Bank Locator: BANK 2 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: 0080 Serial Number: 7A0F265A Asset Tag: 9876543210 Part Number: ANKOWALL Rank: 2 Handle 0x0068, DMI type 17, 28 bytes Memory Device Array Handle: 0x0060 Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: ChannelB-DIMM1 Bank Locator: BANK 3 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: 04CD Serial Number: 00000000 Asset Tag: 9876543210 Part Number: F3-17600CL9-4GBXLD Rank: 2 And lshw -class memory *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 3603 date: 11/09/2012 size: 64KiB capacity: 8MiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification *-cache:0 description: L1 cache physical id: 5 slot: L1-Cache size: 256KiB capacity: 256KiB capabilities: internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 6 slot: L2-Cache size: 1MiB capacity: 1MiB capabilities: internal varies unified configuration: level=2 *-cache:2 DISABLED description: L3 cache physical id: 7 slot: L3-Cache size: 8MiB capacity: 8MiB capabilities: internal unified configuration: level=3 *-memory description: System Memory physical id: 60 slot: System board or motherboard size: 8GiB *-bank:0 description: DIMM DDR3 Synchronous 1333 MHz (0,8 ns) [empty] product: ANKOWALL vendor: 0080 physical id: 0 serial: 7A0F265B slot: ChannelA-DIMM0 width: 64 bits clock: 1333MHz (0.8ns) *-bank:1 description: DIMM DDR3 Synchronous 1333 MHz (0,8 ns) product: F3-17600CL9-4GBXLD vendor: Fujitsu physical id: 1 serial: 00000000 slot: ChannelA-DIMM1 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:2 description: DIMM DDR3 Synchronous 1333 MHz (0,8 ns) [empty] product: ANKOWALL vendor: 0080 physical id: 2 serial: 7A0F265A slot: ChannelB-DIMM0 width: 64 bits clock: 1333MHz (0.8ns) *-bank:3 description: DIMM DDR3 Synchronous 1333 MHz (0,8 ns) product: F3-17600CL9-4GBXLD vendor: Fujitsu physical id: 3 serial: 00000000 slot: ChannelB-DIMM1 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns)

I have a "Qualcomm Atheros AR93xx Wireless Network Adapter" installed. But - I need to determine exactly what the model is, i.e. what numbers replace those x's. Unfortunately, I'm not near the machine physically and can't do it the old-fashioned way (= open it up, screw it out and check). And the box and booklet have been left in a different country... So, can I determine exactly what I've got? I'll mention that so far I've tried lspci, lshw -c net and inxi -n. I'm using Devuan GNU/Linux Beowulf (kernel version 5.2.17-1).

#  lspci | grep -i wireless
04:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
# lspci -n -s  04:00.0
04:00.0 0280: 168c:0030 (rev 01)

I just came across an odd thing while looking at my disks with lshw. I have a 4 TB and a 6 TB disk. lshw shows the expected 6 TB for size but nearly 8 TB for capacity. The 4 TB disk has the same values on both properties: *-disk:1 product: HUS726060AL5210 size: 5589GiB (6001GB) capacity: 7231GiB (7764GB) *-disk:2 product: HGST HUS724040AL size: 3726GiB (4TB) capacity: 3726GiB (4TB) Where does the difference come from for the 6 TB disk? Is the additional space somehow usable?

I have a hard drive (model: ST9100822A), which I think is IDE, because of the look of its interface pins, and accordingly the instruction of my SATA/IDE-USB adapter. But lshw shows it as a SCSI disk *-disk description: SCSI Disk product: 2A vendor: ST910082 physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sdb size: 93GiB (100GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=7 guid=42c2216a-4117-4d4e-8273-e307120f9816 logicalsectorsize=512 sectorsize=512 Some search on the internet seems to say that IDE and SCSI disks are different. Is it a IDE or SCSI disk? Thanks. More output from lshw *-usb:2 description: USB controller product: FCH USB EHCI Controller vendor: Advanced Micro Devices, Inc. [AMD] physical id: 12.2 bus info: pci@0000:00:12.2 version: 39 width: 32 bits clock: 66MHz capabilities: pm debug ehci bus_master cap_list configuration: driver=ehci-pci latency=32 resources: irq:17 memory:f294c000-f294c0ff *-usbhost product: EHCI Host Controller vendor: Linux 4.15.0-45-generic ehci_hcd physical id: 1 bus info: usb@1 logical name: usb1 version: 4.15 capabilities: usb-2.00 configuration: driver=hub slots=4 speed=480Mbit/s *-usb description: Mass storage device vendor: Innostor Technology Corporation physical id: 1 bus info: usb@1:1 logical name: scsi0 version: 0.06 serial: 20140403 capabilities: usb-2.10 scsi emulated scsi-host configuration: driver=usb-storage maxpower=500mA speed=480Mbit/s *-disk description: SCSI Disk product: 2A vendor: ST910082 physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sdb size: 93GiB (100GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=7 guid=42c2216a-4117-4d4e-8273-e307120f9816 logicalsectorsize=512 sectorsize=512 *-volume description: data partition vendor: Windows physical id: 1 bus info: scsi@0:0.0.0,1 logical name: /dev/sdb1 serial: d25b0434-005b-4880-8f60-85d3590f63c5 capacity: 93GiB configuration: name=pimary