From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107262] [drm] BIOS signature incorrect 0 0 with Ryzen 3 2200g
Date: Tue, 17 Jul 2018 12:07:41 +0000 [thread overview]
Message-ID: <bug-107262-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107262
Bug ID: 107262
Summary: [drm] BIOS signature incorrect 0 0 with Ryzen 3 2200g
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop@molgen.mpg.de
Created attachment 140665
--> https://bugs.freedesktop.org/attachment.cgi?id=140665&action=edit
Linux 4.18-rc5+ messages
On a MSI B350M MORTAR with Linux 4.18-rc5+ and Debian Sid/unstable Linux logs
that the Video BIOS signature is incorrect.
```
$ git log --oneline -1
30b06abfb92b (HEAD -> master, origin/master, origin/HEAD) Merge tag
'pinctrl-v4.18-3' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
$ git describe --dirty
v4.18-rc5-36-g30b06abfb92b
$ sudo dmesg
[…]
[ 15.713799] [drm] BIOS signature incorrect 0 0
[ 15.713832] ATOM BIOS: 113-RAVEN-106
[…]
```
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2633 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-07-17 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:07 bugzilla-daemon [this message]
2018-07-17 12:08 ` [Bug 107262] [drm] BIOS signature incorrect 0 0 with Ryzen 3 2200g bugzilla-daemon
2018-07-17 15:01 ` bugzilla-daemon
2018-07-17 15:03 ` bugzilla-daemon
2019-08-06 7:32 ` bugzilla-daemon
2019-11-19 8:44 ` 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-107262-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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;
as well as URLs for NNTP newsgroup(s).