From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211189] vgaarb overrides boot device unexpectedly with Intel and discrete AMDGPU
Date: Mon, 09 Jan 2023 17:53:39 +0000 [thread overview]
Message-ID: <bug-211189-2300-gikmsEE0qV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211189-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211189
--- Comment #7 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Eduardo Medina from comment #6)
> How I do to check that? I force the use of the iGPU from the motherboard,
> but even with that the system identifies the dedicated card as the iGPU and
> vice versa.
When you boot the system, before the OS loads, what GPU displays the sbios
splash screen? If it's always the dGPU, regardless of what you set in the
sbios, it sounds like the sbios is broken and just always sets the dGPU as
default. The Linux kernel looks at what the pre-OS environment left when the
kernel loads.
--
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 prev parent reply other threads:[~2023-01-09 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-211189-2300@https.bugzilla.kernel.org/>
2021-01-14 19:16 ` [Bug 211189] vgaarb overrides boot device unexpectedly with Intel and discrete AMDGPU bugzilla-daemon
2021-01-14 19:35 ` bugzilla-daemon
2021-01-16 13:57 ` bugzilla-daemon
2021-01-17 10:09 ` bugzilla-daemon
2023-01-09 16:52 ` bugzilla-daemon
2023-01-09 17:10 ` bugzilla-daemon
2023-01-09 17:28 ` bugzilla-daemon
2023-01-09 17:53 ` bugzilla-daemon [this message]
2023-01-09 18:36 ` bugzilla-daemon
2023-01-09 19:03 ` bugzilla-daemon
2023-01-09 19:24 ` bugzilla-daemon
2025-10-28 16:52 ` bugzilla-daemon
2025-10-28 16:52 ` 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-211189-2300-gikmsEE0qV@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.