I have two systems. one which is too old and another I just bought. both running ubuntu 24 I backed up some app configurations from old one to transfer them in new one. one of the apps configuration stored some data about model of the device for example device-xx. when I transfer it to new one everything goes fine except the device name. the app failed with error "product name changed.. blah blah". the old one's device product name is for example device-yy. I grabbed this information from sudo dmidecode | grep Product which outputed like this Product Name : device-xx. the exact thing that app shows me in the error. sorry! for some security reasons I cannot mention the exact product name and exact app name. all I want is force the system to fake the product name that app in new device runs without problem. I cannot change configuration of that app because its binary. I don't seek a way to transfer data nor reinstalling the app in the new one. just force the system to advertise a fake product name. that's it. I must mention that: the app is working fine and there is no problem about dependencies and hardware requirements.

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?

# dmidecode --string system-uuid I'm using the code above get the UUID on each host in my environment. As far as I understand the UUID should not change between different Linux distributions on the same host with the same hardware configuration. But after some tests on different Linux distributions I encountered different uuid with this same command. It seems that older dmidecode version will get different UUID result. For example dmidecode 2.9 from SLES11.2 result with string A and dmidecode 2.12 from Debian 8 result with string B. How can I get the same uuid no matter the Linux distribution I deploy on my machine? **Additional information:** I wanted to use dmidecode and not MAC address as UUID because i saw that if I replace my network adapter or some other hardware's settings the UUID will not change. What I need is some unique identifier that I can have on my machine to identify it across minor hardware changes and different OS. Using dmidecode cannot be fake in some level I guess instead of just generating UUID and writing it to a file and using it. I'm working with VMware and machine clones are often used and that's why I need something that will not be replicated with the clone.

So I'm writing a program in c, and I want to get the firmware (e.g. BIOS, UEFI, Coreboot). Since I'm writing a c program it shouldn't really be running commands, I want to be able to check via files or a library but preferably files. I know /sys/firmware/efi in created for UEFI systems, but then what about BIOS and Coreboot? DMI doesn't even seem to have a nice answer either since it seems to consider UEFI as BIOS I guess for compatibility reasons, meaning it's all just called BIOS when it may or may not be. I couldn't find anything under /sys/class/dmi/id that mentioned what firmware was running, only stuff about that firmware, though somehow the command dmidecode listed 'UEFI is supported' under the characteristics of my 'BIOS Information' (I'm using UEFI, not BIOS), I couldn't find where it got that information from though. In the first place DMI instead a great solution since I need this to be able to work for ARM and RISC-V, not just x86 which I think DMI is for.

I used a system information utility to take the model number of a system, and also of the motherboard. DMI System Manufacturer LENOVO DMI System Product 2306CTO DMI System Version ThinkPad X230 DMI Motherboard Product 2306CTO Is there a way to get model number, in this case 2306CTO, in Linux?

I'm using a Lenovo ThinkPad. How can I find the serial number on this machine without shutting down?

Presently I'm checking by running dmidecode -s bios-version and grepping against major cloud vendors. Ex: `# From an amazon ec2 VM $ sudo dmidecode -s bios-version 4.2.amazon` Is there a generic and more reliable approach for finding this?

we have Linux RHEL server - 7.6 version in server disks are : lsblk -S NAME HCTL TYPE VENDOR MODEL REV TRAN sda 0:2:0:0 disk DELL PERC FD33xD 4.27 sdb 1:0:0:0 disk ATA INTEL SSDSC1BG40 DL2B sata sdc 2:0:0:0 disk ATA INTEL SSDSC1BG40 DL2B sata sdc and sdb are the OS disks about sda is disk that represented by RAID so sda include number of disks , but the question is how to count the number of disks in RAID we tried the following but we not sure if this cli described the number of disks in RAID? smartctl --scan /dev/sda -d scsi # /dev/sda, SCSI device /dev/sdb -d scsi # /dev/sdb, SCSI device /dev/sdc -d scsi # /dev/sdc, SCSI device /dev/bus/0 -d megaraid,0 # /dev/bus/0 [megaraid_disk_00], SCSI device /dev/bus/0 -d megaraid,1 # /dev/bus/0 [megaraid_disk_01], SCSI device /dev/bus/0 -d megaraid,2 # /dev/bus/0 [megaraid_disk_02], SCSI device /dev/bus/0 -d megaraid,3 # /dev/bus/0 [megaraid_disk_03], SCSI device /dev/bus/0 -d megaraid,4 # /dev/bus/0 [megaraid_disk_04], SCSI device /dev/bus/0 -d megaraid,5 # /dev/bus/0 [megaraid_disk_05], SCSI device /dev/bus/0 -d megaraid,6 # /dev/bus/0 [megaraid_disk_06], SCSI device /dev/bus/0 -d megaraid,7 # /dev/bus/0 [megaraid_disk_07], SCSI device /dev/bus/0 -d megaraid,8 # /dev/bus/0 [megaraid_disk_08], SCSI device /dev/bus/0 -d megaraid,9 # /dev/bus/0 [megaraid_disk_09], SCSI device /dev/bus/0 -d megaraid,10 # /dev/bus/0 [megaraid_disk_10], SCSI device /dev/bus/0 -d megaraid,11 # /dev/bus/0 [megaraid_disk_11], SCSI device /dev/bus/0 -d megaraid,12 # /dev/bus/0 [megaraid_disk_12], SCSI device /dev/bus/0 -d megaraid,13 # /dev/bus/0 [megaraid_disk_13], SCSI device /dev/bus/0 -d megaraid,14 # /dev/bus/0 [megaraid_disk_14], SCSI device /dev/bus/0 -d megaraid,15 # /dev/bus/0 [megaraid_disk_15], SCSI device lspci -vv | grep -i raid 06:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] (rev 02) Kernel driver in use: megaraid_sas mdadm --detail /dev/sda mdadm: /dev/sda does not appear to be an md device cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb2 sdc2 390054912 blocks super 1.2 [2/2] [UU] bitmap: 2/3 pages [8KB], 65536KB chunk md0 : active raid1 sdb1 sdc1 524224 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk unused devices: lsscsi [0:2:0:0] disk DELL PERC FD33xD 4.27 /dev/sda [1:0:0:0] disk ATA INTEL SSDSC1BG40 DL2B /dev/sdb [2:0:0:0] disk ATA INTEL SSDSC1BG40 DL2B /dev/sdc cat /proc/partitions major minor #blocks name 8 0 13670809600 sda 8 16 390711384 sdb 8 17 524288 sdb1 8 18 390185984 sdb2 8 32 390711384 sdc 8 33 524288 sdc1 8 34 390185984 sdc2 9 0 524224 md0 9 1 390054912 md1 253 0 104857600 dm-0 253 1 16777216 dm-1 253 2 104857600 dm-2 253 3 10485760 dm-3 ll /sys/block/ total 0 lrwxrwxrwx 1 root root 0 Oct 17 07:27 dm-0 -> ../devices/virtual/block/dm-0 lrwxrwxrwx 1 root root 0 Oct 17 07:27 dm-1 -> ../devices/virtual/block/dm-1 lrwxrwxrwx 1 root root 0 Oct 17 07:27 dm-2 -> ../devices/virtual/block/dm-2 lrwxrwxrwx 1 root root 0 Oct 17 07:27 dm-3 -> ../devices/virtual/block/dm-3 lrwxrwxrwx 1 root root 0 Oct 17 07:27 md0 -> ../devices/virtual/block/md0 lrwxrwxrwx 1 root root 0 Oct 17 07:27 md1 -> ../devices/virtual/block/md1 lrwxrwxrwx 1 root root 0 Oct 17 07:27 sda -> ../devices/pci0000:00/0000:00:03.0/0000:02:00.0/0000:03:01.0/0000:04:00.0/0000:05:01.0/0000:06:00.0/host0/target0:2:0/0:2:0:0/block/sda lrwxrwxrwx 1 root root 0 Oct 17 07:27 sdb -> ../devices/pci0000:00/0000:00:11.4/ata1/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Oct 17 07:27 sdc -> ../devices/pci0000:00/0000:00:11.4/ata2/host2/target2:0:0/2:0:0:0/block/sdc ll /sys/block/ |grep 'primary' no output

the cmd command:

-s processor-version

gives me the same andswer 125 times. I want the commande to andswer only one time. how can break the loop ?

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 am trying to find out the cache mapping scheme for all the levels of class of a Linux server, including associativity, however I do not have root access. I would just use dmidecode for this but you need root access. Is there another way of getting the same information without root?

Having had a bit of an internet-scour, I think the answer may be "No", but: Can I find the USB port description (as per dmidecode) corresponding to the USB device from sysfs? We can enumerate all USB hubs and devices by listing /sys/bus/usb/devices. For example:

1 root root 0 May 18 09:36 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 May 18 09:40 1-2 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-2
lrwxrwxrwx 1 root root 0 May 18 09:40 1-2:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
lrwxrwxrwx 1 root root 0 May 18 09:36 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 May 18 09:36 2-3 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-3
lrwxrwxrwx 1 root root 0 May 18 09:36 2-3:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0
lrwxrwxrwx 1 root root 0 May 18 09:36 usb1 -> ../../../devices/pci0000:00/0000:00:14.0/usb1
lrwxrwxrwx 1 root root 0 May 18 09:36 usb2 -> ../../../devices/pci0000:00/0000:00:14.0/usb2

…And we can list all built-in USB ports on the machine by doing dmidecode -t connector. For example it shows (among many other connectors):

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: USB REAR
	Internal Connector Type: Proprietary
	External Reference Designator: Rear: USB-1
	External Connector Type: Access Bus (USB)
	Port Type: USB

[...]

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: USB 3.0 REAR
	Internal Connector Type: Proprietary
	External Reference Designator: Rear: USB 1
	External Connector Type: Access Bus (USB)
	Port Type: USB

(On my machine, it looks like each USB port appears twice, in the guise of "USB" and "USB 3.0".) I’d love to be able show the connector description ("Rear: USB 1") corresponding to a particular USB device— but there does not seem to be a reliable way to relate /sys/bus/USB devices to dmidecode connectors— Is there? (In my particular case, it would be tempting to relate "usb1" from the bus to "USB 1" from Dmidecode… but I’m willing to bet that that’s a coincidence.) Edit: Or if not dmidecode, some other tool which could provide an external description of the port.

When I run command sudo dmidecode -t 17 I see : Bank Locator: P0 CHANNEL A 1. What this means ?? I searched dmidecode site and docs but not found any information. I just wanted to check memory mode, but sudo dmidecode 2.3 | grep Interleaved only prints: Interleaved Data Depth: Unknown 2. Is there other way to detect what memory mode is used (8+16 on AMD 4600) ??

When I run the command sudo dmidecode, **OEM Strings** entries change everyday. Yesterday, they were like the following: OEM Strings String 1: 2WYGio4ByI3fS String 2: Mqd4eRO2YezsP String 3: 3N0poAdRciCcs Now, they are like the following: OEM Strings String 1: VNJq-77fKzTx+ String 2: h+8cgFuyKXP-o String 3: 2l25nHrRCEgKb What does "OEM strings" mean in dmidecode output?

I have a nice laptop - 32 GB of RAM, M2 (SATA) and 2.5' SSD (also SATA) - dual boot, Fedora 33 & Windows 2019 Server. I ran dmidecode and found a Maximum Capacity of 64GB - but the manufacturer (ASUS) says 32GB is the max! Now, I know that dmidecode isn't perfect , but I want to hear from those who have upgraded their RAM based on dmidecode despite the manufacturer's recommendations? Quote from link above: > Beware that DMI data have proven to be too unreliable to be blindly > trusted. Dmidecode does not scan your hardware, it only reports what > the BIOS told it to. I also found this , which doesn't inspire confidence, where it says: > Aniruddh yes the H300's only support 32gb ram max (officially) its not > the cpu support in this case its the mobo limited/locked support all > bios are locked so unless its a modded bios (which i strongly dont > recommend doing neither its allowed to discuss anything about it in > this community ) probably it wont support so until someone buys 32gb > sodimms and test them theres no way to know if its will support or not > and i doubt anyone would take such a risk on a such high priced ram > without having sure if it would really work or not but anyway of you > are willing to go for it also why would u need 64gb 32 its already too > much no one will ever use them in full and its not having 64gb that > would make the laptop faster in some rare cases too much unused ram > could also cause some bottleneck and decrease the performance but good > luck :) So, it appears even if the mobo specs **allow** a certain amount of RAM, the manufacturer may or may not have reduced this capacity from within the BIOS? Have I grasped the picture - am I taking a big chance going by dmidecode or should I persevere? Any references/URLs, tips - anything appreciated!

We have Kafka machines installed with RHEL 7.2 servers on Dell HW and a shelf includes 15 disks. We want to understand what happens when we push out one of the Kafka disks, and see if Kafka is still functional. So the easy solution is just to push out the disk from the shelf. But is it possible to simulate this situation without pushing out the disk? For example we can umount the disks from the mount point, but this isn't enough good like pushing out the disks from the shelf.

I am trying to identify with dmidecode whether my computer has DDR3 or DDR4 memory. But, when I run it, it does not provide any information that would let me identify the installed memory. For memory type it provides: Type: Unknown Why is the type of memory "unknown"? How can I make it show the type of memory?

I wonder if this dmidecode output suggests that one can put 2x16GB or 2x32GB? I have seen that in different version of dmidecode information about total system maximum capacity and maximum module capacity was separated, but not in this one. Also, I haven't seen anything useful in manpages.

# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.1.1 present.

Handle 0x003E, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 32 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

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)

Is it possible to find out the details about Linux cards? For example we tried: dmidecode | grep -i network Function key-initiated network boot is supported Port Type: Network Port Port Type: Network Port Port Type: Network Port Port Type: Network Port # dmidecode | grep -i eth Type: Ethernet Type: Ethernet Type: Ethernet Type: Ethernet This details doesn't say anything about the network cards and performance etc. Any advice about tools that can give these details about network cards?