linuxboot / linuxboot/heads

Heads' System Information is x86 centric

Open
#1,220 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
1.6k
Forks
211
Avg merge
4d 21h
Merged PRs (30d)
6

Description

`![2022-09-26-150328](https://user-images.githubusercontent.com/827570/192359540-d5b0304b-6c6b-41d3-bdce-c433084bb6b7.png)

Missing above:
- Firmware version
- CPU model
- Disk size
----

- for x86, CPU version can easily be obtained grepping "cpu model" from /proc/cpuinfo.
On Power, it seems that this is `model` only.

- x86:
`cat /proc/cpuinfo | grep "model name"|awk -F ":" {'print $2'} | uniq`
Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz

- Power:
`cat /proc/cpuinfo | grep "model name"|awk -F ":" {'print $2'} | uniq`
nothing
`cat /proc/cpuinfo | grep "model"| awk -F ":" {'print $2'} | uniq`
`T2P9D01 REV 1.00`: not good. It's the motherboard, not the CPU.

-----

- FW_VER cannot be extracted from dmesg grepping DMI/BIOS information as on x86.
Both can have the firmware version extracted through coreboot console output with the following:
```
cbmem -1 | grep Heads | awk -F " " {'print $1'} | awk -F "--" {'print $NF'}
| uniq
```
Outputs: `Heads-v5.0.1-212-g585e581d`

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing system-information entry point that reads /proc/cpuinfo and firmware data, then compare the x86 and Power cases described in the issue. Use cbmem console output for the firmware version and verify that the displayed information includes firmware version, CPU model, and disk size on both platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.