[Bug] NVRM: Bar1 - Sits on setting up bar whilst preparing. What is it doing?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- operating-systems
Research direction
The payload names no source files or tests. Start by searching the repository for the log string "Bar1" or "NVRM" to find where the BAR setup message is emitted, then read the code around it. Done means a maintainer-confirmed explanation of what that step does during boot, and a concrete change only if the thread settles on one. Expect kernel-driver and macOS boot knowledge to be needed.
Written by the indexing model from the issue text.
Description
Send logs report ID
No log required. Is generic.
Where does it go wrong?
Booting macOS after the driver (black / grey screen, restarts)
What happens
Wonder what happens here. Is it a safety check in the code or something? Realistically as soon as BAR is placed the login should be shown no?
Written by you
- I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)
1.15
Did you change anything yourself?
No response
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nullmoth/nvidia-macos-driver
-
[Bug] `nullmoth-wsreset.sh` never restarts WindowServer at the real login window: `/dev/console` is `_windowserver`, not `root` (guard + test blind spot)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 10/100
nullmoth/nvidia-macos-driver#212 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 12/100
nullmoth/nvidia-macos-driver#211 ·
Maintainers usually reply within 1 day
-
[Bug] <what happens>Openbug
Difficulty 5/5 Over a week Newbie friendliness 8/100
nullmoth/nvidia-macos-driver#210 ·
Maintainers usually reply within 1 day
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
RUSTSEC-2026-0348: Brotli certificate decompression can allocate up to 1 GiB before authenticationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
core: Amount::from_str panics on values above 21M BTC instead of returning an errorPossibly taken @bhuvan-somisetty claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
crate: spate-s3
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
write_iceberg ignores the table's write.parquet.compression-codec propertyPossibly taken @YuangGao claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Eventual-Inc/Daft#7606 ·
Maintainers usually reply within 1 day