/proc/cpuinfo missing Processor and Hardware info

Whilst the /proc/cpuinfo virtual file on my Raspberry Pi 3 running
SLES12 SP2 (from SUSECON 2016) has the four processor sections none of
those sections includes the ‘model name’ line.

The file is also missing ‘Hardware’, ‘Revision’, and ‘Serial’ lines from
the end of the file.

Presumably this is known and will be resolved in a later build/update?

Thanks.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

[QUOTE=smflood;35388]Whilst the /proc/cpuinfo virtual file on my Raspberry Pi 3 running
SLES12 SP2 (from SUSECON 2016) has the four processor sections none of
those sections includes the ‘model name’ line.

The file is also missing ‘Hardware’, ‘Revision’, and ‘Serial’ lines from
the end of the file.
[/QUOTE]

The format of /proc/cpuinfo varies on different architectures. On s390x for example, it looks like this: [QUOTE]
$ cat /proc/cpuinfo
vendor_id : IBM/S390

processors : 2

bogomips per cpu: 2913.00
features : esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te
processor 0: version = 00, identification = 0E9A27, machine = 2827
processor 1: version = 00, identification = 0E9A27, machine = 2827
[/QUOTE]

On ppc64le it looks like this: [QUOTE]

processor : 152
cpu : POWER8E (raw), altivec supported
clock : 3690.000000MHz
revision : 2.1 (pvr 004b 0201)

timebase : 512000000
platform : PowerNV
model : 8247-22L
machine : PowerNV 8247-22L
firmware : OPAL
[/QUOTE]

For AArch64 (64bit ARM), the format is pretty simplistic and doesn’t mention much real information apart from the core id:[QUOTE]

processor : 3
BogoMIPS : 38.40
Features : fp asimd evtstrm crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
[/QUOTE]

If you want to figure out the hardware model type or seral number on AArch64, please refer to the “dmidecode” command. It provides all information available about the underlying system rather than the CPU only:[QUOTE]
$ dmidecode

dmidecode 3.0

Getting SMBIOS data from sysfs.
SMBIOS 3.0 present.
6 structures occupying 196 bytes.
Table at 0x35B0F020.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: U-Boot
Version: 2016.07
Release Date: 09/14/2016
ROM Size: 64 kB
Characteristics:
PCI is supported
BIOS is upgradeable
Selectable boot is supported
I2O boot is supported
Targeted content distribution is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: raspberrypi
Product Name: rpi
Version: Not Specified
Serial Number: 00000000ac88fXXX
UUID: 30303030-3030-3030-6163-383866XXXXXX
Wake-up Type: Reserved
SKU Number: Not Specified
Family: Not Specified

Handle 0x0002, DMI type 2, 14 bytes
Base Board Information
Manufacturer: raspberrypi
Product Name: rpi
Version: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Features:
Board is a hosting board
Location In Chassis: Not Specified
Chassis Handle: 0x0000
Type: Motherboard

Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
Manufacturer: raspberrypi
Type: Desktop
Lock: Not Present
Version: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: Unspecified
Contained Elements: 0

Handle 0x0004, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected

Handle 0x0005, DMI type 127, 4 bytes
End Of Table[/QUOTE]

An alternative source for now for AArch64 (until it switches to ACPI for some systems) is to look at the device tree manally:[QUOTE]
$ more /proc/device-tree/model
Raspberry Pi 3 Model B
[/QUOTE]