[Bug] 2.6.3-2.6.6: display never comes up on small-BAR1 fallback (HP t740, RTX A3000 12GB 0x24B8); 2.6.2 works fine

Aperta
  • Qualcosa non va?
#489 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
macos, rust
Ambito
operating-systems

Direzione di ricerca

The report needs the BAR1 fallback path (rule bar1-resize-8gb in the 1401 state log) and the NVRM/NVAccel/NVRMFB/NVRMAGDC kext bring-up, which changed between 2.6.2 and 2.6.3. Start by diffing the driver's display-head arming code between those versions, and confirm which step never completes on 2.6.6. Done means identifying the change and a fix verified on a small-BAR1 machine, which requires hardware most contributors lack.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Machine
  • HP t740 thin client (Ryzen Pro 4750GE, Barcelo), OpenCore boot
  • GPU: RTX A3000 12GB Laptop GPU (GA104GL, PCI ID 10de:24b8)
  • Firmware Resizable BAR: Disabled -> driver uses the BAR1 fallback path (1401 state log shows rule bar1-resize-8gb)
  • macOS 15.8.2, installed/managed with the latest 1401 Mac app (1.15), all installs via 1401
What works / what fails
Driver Result
2.6.0-2.6.2 Works fine: accelerated desktop, Metal 3, stable for days
2.6.3 WindowServer watchdog death loop: launchd relaunches WindowServer forever; every report says "WindowServer initialization not complete (post IOKitWaitQuiet)"; stackshot shows the WindowServer main thread stuck in an uninterruptible kernel wait (TH_UNINT) with NVRM-family kext frames
2.6.4 Same death loop
2.6.5 Same death loop
2.6.6 Behavior changed: no more hang (bootguard logs "came up and stayed up"), WindowServer starts on the firmware framebuffer - black screen with live cursor, 1920x1080, no acceleration. All 4 kexts (NVRM/NVAccel/NVRMFB/NVRMAGDC) load, but the display head is never armed. Waited 10+ minutes (well beyond the documented 100 s settle + 40 s bring-up) - display never takes over. Tried 3 boots, same result every time.
Config (all README requirements verified present)
  • boot-args: nvfb=1 nvaccel=1 nvfbheads=4 -nvkmsnosmooth amfi_get_out_of_my_way=0x1 amfi=0x80 ipc_control_port_options=0 (added by 1401 2.6.6)
  • Kernel -> Block: com.apple.iokit.IONDRVSupport, Strategy Exclude (present since 2026-10-31)
  • csr-active-config includes 0x0A43, SecureBootModel Disabled, Lilu + AMFIPass enabled, Above 4G Decoding ON, CSM OFF
Notes
  • 2.6.2 also shows occasional gpuRestart self-heals, so this card on this firmware sits near the edge already.
  • 2.6.6's change from "watchdog loop" to "black desktop, system alive" already helped a lot - it looks like the GPU/VRAM bring-up path changed in 2.6.3 and on this fallback-BAR machine the display arm never completes.
Report

Sent via 1401 "Send logs": report ID NM-GQ7QERDV (batch 1401-mac-f93766f80f755a9f). It contains the driver state, kernel log ring and the watchdog reports from all failed boots.

Happy to test 2.6.7 on this machine - the fallback-BAR path here is fully reproducible (3/3 boots fail identically).

Lingua principale
Rust
Stelle
2.5k
Fork
233
Merge medio
3g 14h
PR unite (30g)
14

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nullmoth/nvidia-macos-driver

Tutte le issue di nullmoth/nvidia-macos-driver

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.