Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Management Engine status menu #140

Open
miczyg1 opened this issue Jun 8, 2022 · 4 comments
Open

Management Engine status menu #140

miczyg1 opened this issue Jun 8, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@miczyg1
Copy link
Contributor

miczyg1 commented Jun 8, 2022

The problem you're addressing (if any)
Lack of management Engine status in the firmware. Management Engine may be often disabled or non functional for various reasons during POST. The firmware will disable HECI device and save the last known state in SMBIOS for proprietary firmware. Dasharo lacks this mechanism.

Describe the solution you'd like
The Management Engine status menu would show either the current status retrieved from HECI or the SMBIOS if HECI is hidden or not functional. Implement SMBIOS ME status if HECI is not functional in coreboot. Also implement showing ME state when HAP bit is enabled or ME is soft disabled.

Where is the value to a user, and who might that user be?
Better UX and proof that ME is disabled. May also show some Boot Guard status.

Describe alternatives you've considered
None

Additional context
None

@miczyg1 miczyg1 added the enhancement New feature or request label Jun 9, 2022
@pietrushnic
Copy link

@miczyg1 isn't it duplicate of #111 ?

@miczyg1
Copy link
Contributor Author

miczyg1 commented Jul 12, 2022

@pietrushnic not exactly. #111 aims to implement options to trigger ME disable or set the HAP bit. This request aims to present in human readable form the state of ME based on hardware registers. Although these two requests may be closely related, i.e. land in the same submenu.

@pietrushnic
Copy link

@miczyg1 I wonder if those are very useful for end user when separated. From engineering point of view those are 2 things from user point it is one feature.

@miczyg1
Copy link
Contributor Author

miczyg1 commented Jul 13, 2022

@pietrushnic yes it can be viewed like that. But note aggregation of features doesn't play well for us. it is easier to deliver smaller blocks that still have value for users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants