Bug 212959 - [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! - Exclusively an issue by booting from mounted ISOs of respective OS.
Summary: [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for ...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: Other Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-06 00:23 UTC by tob88570
Modified: 2021-05-11 00:03 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.4, 5.8
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Dmesg output (90.98 KB, text/plain)
2021-05-10 23:58 UTC, tob88570 		Details
Add an attachment (proposed patch, testcase, etc.)

Description tob88570 2021-05-06 00:23:18 UTC 
This error occurs on all distros based on Ubuntu 20.04 with Linux Kernel 5.4 as well as Kernel 5.8, that attempt to load a GUI, upon booting from a mounted iso into said Operating Systems installations.

This error occurs at least for AMD RYZEN 7 4700U Apus with AMD VEGA 7 RENOIR graphics.
Comment 1 tob88570 2021-05-06 00:25:16 UTC 
Little correction *as well as Linux Distros with Kernel 5.8 not necessarily based on Ubuntu 20.04.
Comment 2 Alex Deucher 2021-05-06 02:20:07 UTC 
Please attach the dmesg output for your system.  Other than the error, is the GPU otherwise working correctly?
Comment 3 tob88570 2021-05-10 23:58:44 UTC 
Created attachment 296713 [details]
Dmesg output
Comment 4 tob88570 2021-05-11 00:01:00 UTC 
(In reply to Alex Deucher from comment #2)
> Please attach the dmesg output for your system.  Other than the error, is
> the GPU otherwise working correctly?

The GPU otherwise is working correctly. On other Operating Systems.

Also this issue is exclusive to attempting to boot the live systems or installations from a mounted version of the respective downloaded ISO file.

If you flash it to USB, the installation works fine, despite somewhat the same errors. I am writing this currently from a working PopOS installation.
Note You need to log in before you can comment on or make changes to this bug.