All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209373] Pixels
Date: Thu, 24 Sep 2020 12:01:27 +0000	[thread overview]
Message-ID: <bug-209373-2300-N3Tz6kv3Jk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209373-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209373

--- Comment #4 from Jens R. (rapp.jens@gmail.com) ---
(In reply to Michel Dänzer from comment #3)
> Yeah, the BIOS seems very picky about which partitions it boots from. With
> GParted or a similar tool, check that the partition which contains the EFI
> directory has at least the boot & esp flags set. (I only realized this might
> be enough after manually extracting the BIOS image to a USB HD, and updating
> from that)

You're right... it's really picky.. You need to switch to insecure boot and
after,  legacy boot before uefi. 
Updating BIOS seems to work
I'll watch behaviour for a while but I think that the issue is fixed by BIOS
update.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-09-24 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  9:24 [Bug 209373] New: Pixels bugzilla-daemon
2020-09-24 10:11 ` [Bug 209373] Pixels bugzilla-daemon
2020-09-24 10:39 ` bugzilla-daemon
2020-09-24 11:06 ` bugzilla-daemon
2020-09-24 12:01 ` bugzilla-daemon [this message]
2020-10-06 10:12 ` 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-209373-2300-N3Tz6kv3Jk@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 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.