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

NVRAM Boot Entries Are Shown As Shell Tools #184

Closed
emperor06 opened this issue Jun 15, 2024 · 4 comments
Closed

NVRAM Boot Entries Are Shown As Shell Tools #184

emperor06 opened this issue Jun 15, 2024 · 4 comments
Labels
Bug Something Went Wrong Resolved Issue Has Been Resolved

Comments

@emperor06
Copy link

RefindPlus Version

v0.14.1.AA Release

Device Type

UEFI PC

Problem Description

My tool row is filled with many shell icons, corresponding to the various entries I have in nvram (like local HD, usb, optical, or OS boot entries).
My config contains showtools shell

Problem Point

Before starting a loader or tool

Affected Items

One or More Tools (Second Row Items)

Debug Log

Debug logs are on the way, but I've been browsing scan.c and found 2 suspicious things. I don't know if that could help.

First, ScanForTools, case TAG_SHELL always calls ScanFirmwareDefined(), even if a shell has already been found. Maybe that's intended, I don't know, but I found it strange to search the firmware if we've already found the tool.

Second, in ScanFirmwareDefined(), if DontScanFirmware is empty, then every nvram entries are scanned and added, regardless of MatchThis (which, in this case, should contain L"shell"). I think that's why all the firmware entries become uefi shells in my toolbar.

Additional Context

No response

@github-actions github-actions bot added the Triage Evaluating label Jun 15, 2024
@emperor06
Copy link
Author

I've added a dummy dont_scan_firmware "hello world" to my config and the wrong shell tools are gone.

Here are the logs.
24k15s4428.log

@dakanji
Copy link
Owner

dakanji commented Jun 15, 2024

Thanks for the report and input.
That aspect does need a revisit.
Will get to it presently.

@dakanji dakanji added the Acknowledged Something Was Wrong label Jun 15, 2024
@github-actions github-actions bot added Unresolved Noy Yet Resolved and removed Triage Evaluating labels Jun 15, 2024
Copy link

github-actions bot commented Jun 19, 2024

This item was addressed by Commit 00dcb08.

Current RefindPlus Release: v0.14.1.AA.
Refer to BUILDING.md to access functionality before the next release.

Note

Alternatively, the issue can be worked around pending the next release by setting the dont_scan_firmware configuration token to a random string.
For example, dont_scan_firmware ForgetMeNot

Thank you for taking the time to report a problem with RefindPlus.

@github-actions github-actions bot added Bug Something Went Wrong Resolved Issue Has Been Resolved and removed Acknowledged Something Was Wrong Unresolved Noy Yet Resolved labels Jun 19, 2024
Copy link

This thread is being locked.

Please use the Discussions Feature for follow-on discussion or raise a new issue if appropriate.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 21, 2024
@dakanji dakanji changed the title All my firmware entries end up as shell tools NVRAM Boot Entries Show As Shell Tools Jun 26, 2024
@dakanji dakanji changed the title NVRAM Boot Entries Show As Shell Tools NVRAM Boot Entries Are Shown As Shell Tools Jun 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Something Went Wrong Resolved Issue Has Been Resolved
Projects
None yet
Development

No branches or pull requests

2 participants