Bug 107262 - [drm] BIOS signature incorrect 0 0 with Ryzen 3 2200g
Summary: [drm] BIOS signature incorrect 0 0 with Ryzen 3 2200g
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-17 12:07 UTC by Paul Menzel
Modified: 2019-11-19 08:44 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Linux 4.18-rc5+ messages (112.22 KB, text/plain)
2018-07-17 12:07 UTC, Paul Menzel 		no flags Details
Extracted firmware (53.00 KB, application/octet-stream)
2018-07-17 12:08 UTC, Paul Menzel 		no flags Details
View All

Description Paul Menzel 2018-07-17 12:07:41 UTC 
Created attachment 140665 [details]
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
[…]
```
Comment 1 Paul Menzel 2018-07-17 12:08:55 UTC 
Created attachment 140666 [details]
Extracted firmware

Video BIOS extracted with writing `1` to `/rom`, and then copying that.
Comment 2 Alex Deucher 2018-07-17 15:01:09 UTC 
The driver tries multiple methods to fetch the vbios depending on the platform.  One of the methods fails and this message is the result.  The driver is ultimately able to find a proper vbios, otherwise the driver would fail to load.
Comment 3 Paul Menzel 2018-07-17 15:03:08 UTC 
Thank you for the explanation. Could the message then please be improved to not cause confusion?
Comment 4 Paul Menzel 2019-08-06 07:32:06 UTC 
Any suggestions regarding this? I see this on all recent AMD systems.
Comment 5 Martin Peres 2019-11-19 08:44:04 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/450.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.