From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215003] New: apple_gmux fails to initialize and iGPU unclaimed on MacBook Pro 16" 2019
Date: Sat, 13 Nov 2021 11:47:07 +0000 [thread overview]
Message-ID: <bug-215003-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215003
Bug ID: 215003
Summary: apple_gmux fails to initialize and iGPU unclaimed on
MacBook Pro 16" 2019
Product: Drivers
Version: 2.5
Kernel Version: 5.14.y
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: dreifachstein@gmail.com
Regression: No
MBP2019 can be tricked into booting with the iGPU enabled
(https://github.com/0xbb/apple_set_os.efi) but i915 does not claim the iGPU
after booting.
I have tracked down the direct cause but do not how to fix it.
When booting with the iGPU enabled `apple_gmux_present` returns true because
GMUX_ACPI_HID ("APP000B") is present in the ACPI tables.
Because apple_gmux fails to initialize with "Failed to find gmux I/O resource"
and never registers with vgaswitcheroo the i915 probe routine always bails out
after `vga_switcheroo_client_probe_defer` lefting the device unclaimed.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-11-13 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 11:47 bugzilla-daemon [this message]
2021-11-13 11:49 ` [Bug 215003] apple_gmux fails to initialize and iGPU unclaimed on MacBook Pro 16" 2019 bugzilla-daemon
2021-11-13 13:04 ` bugzilla-daemon
2021-11-14 6:08 ` bugzilla-daemon
2021-11-14 6:12 ` bugzilla-daemon
2021-11-14 7:33 ` bugzilla-daemon
2021-11-14 8:11 ` bugzilla-daemon
2021-11-14 8:28 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215003-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox