Console driven flashrom write progress sometimes stay at 0% on internal firmware upgrade
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
>On the second x230 i had a issue where flashrom inside heads when saving the changed configuration stayed endless at 0%. Because of my experience how long this in general take to flash it, i knew after 10 minutes, that it have to have finished if it even started. After force turning it off, spi write protection in the OS was disabled.
_Originally posted by @fhvyhjriur in https://github.com/linuxboot/heads/issues/1657#issuecomment-2094802719_
----
We would gladly get rid of this console based progress bar if flashrom was finally integrating the --progress bar natively.
I checked recently and even flashrom 1.3.0 doesn't yet support it back....
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the console-based progress bar and the flashrom write path used during internal firmware upgrades. Reproduce the x230 configuration-save scenario if possible, then determine why progress can remain at 0% and verify that the displayed progress reflects completion without disabling SPI write protection.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100