Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GTX 1650 Max-Q (TU117, 10DE:1F9D) on muxless laptop: dGPU inits fully but heads 0 connectors 0, no display; request for iGPU-scanout path

Open
  • Is something wrong?
#76 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@TararaDotJoshua is already working on this.

Since Oct 11, 2026.

  • #131 by @TararaDotJoshua — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
backend, desktop

Research direction

Start by reading the NVRM-fb and NVAccel initialization paths, especially where heads and connectors are discovered and where framebuffer publication gates accelerator startup; the issue does not name source files or tests. The proposed iGPU-scanout path would need design work across display ownership and rendering. Done would mean NVAccel can arm Metal and render to a framebuffer owned by the iGPU on a muxless laptop.

Written by the indexing model from the issue text.

Description

Hardware: MSI GF63, i5-11400H, GTX 1650 Max-Q (10DE:1F9D, subsys 132E1462), Intel UHD iGPU (8086:9A68). Muxless, with the internal panel and HDMI both on the iGPU (NVIDIA Control Panel on Windows shows the laptop display attached only to Intel). No DP or USB-C DP output.

Software: macOS Sequoia, OpenCore, driver 1.2.0, MacBookPro16,2. Boot-args as per the docs (nvfb=1 nvaccel=1 nvfbheads=4 ...).

What works: RmInitAdapter succeeded, GSP-RM running, 4 GB VRAM published, BAR1 256 MB mapped.

What fails: every NVRM-fb instance logs heads 0 connectors 0 and getDisplays: none, then kapiInit failed. After 20 s: heads published mask 0x0, NVAccel no framebuffer has published yet, accelerator never arms. macOS then boots headless, and blind typing at the login window works.

Question: is there any plan for muxless laptops, for example a mode where NVAccel arms Metal without NVRMFB heads and renders for a framebuffer owned by another driver? I can provide full logs and photos.

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

  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.

More from nullmoth/nvidia-macos-driver

All issues in nullmoth/nvidia-macos-driver

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.