Hey,
I had some time to bisect again tonight and it seems
018d82e5f02ef3583411bcaa4e00c69786f46f19
got back in again through:
# first bad commit: [d98c71dadc2d0debdb80beb5a478baf1e6f98758] Merge
drm-upstream/drm-next into drm-misc-next
/ Daniel
On Wed, 29 Aug 2018 at 16:02, Daniel Andersson wrot
gt;>>1024x768 59.95
>>>>800x600 59.95
>>>>640x480 59.95
>>>> DisplayPort-1 disconnected (normal left inverted right x axis y axis)
>>>> HDMI-A-0 disconnected (normal left inverted right x axis y axis)
>>>
ht x axis y axis)
>>> HDMI-A-1 disconnected (normal left inverted right x axis y axis)
>>>
>>> Where does dm_error and dm_output_to_console end up?
>>>
>>
>> dm_error -> DRM_ERROR will end up in dmesg as an error message
>> dm_output_to_console -&
curious what the driver thinks the major and minor are.
>
> Harry
>
>> // Daniel
>>
>> On 5 July 2018 at 18:42, Deucher, Alexander
>> wrote:
>>> So your vbios has table v3.1 so it should not be affected by that patch.
>>> Does reverting that patch a
that patch actually fix the issue?
>>
>>
>> Alex
>>
>>
>> From: amd-gfx on behalf of Daniel
>> Andersson
>> Sent: Thursday, July 5, 2018 12:22:17 PM
>> To: Alex Deucher
>> Cc: amd-gfx@lists.freedesktop.org
>> Subject: R
patch actually fix the issue?
>
>
> Alex
>
>
> From: amd-gfx on behalf of Daniel
> Andersson
> Sent: Thursday, July 5, 2018 12:22:17 PM
> To: Alex Deucher
> Cc: amd-gfx@lists.freedesktop.org
> Subject: Re: BUG: *ERROR* No EDID read
>
> I have n
@lists.freedesktop.org
Subject: Re: BUG: *ERROR* No EDID read
I have not flashed any GPU BIOS. It's not a reference Vega though,
Sapphire something. Maybe they made changes?
vbios is attached.
// Daniel
On 5 July 2018 at 15:38, Alex Deucher wrote:
> On Mon, Jul 2, 2018 at 5:39 PM, Daniel Andersso
I have not flashed any GPU BIOS. It's not a reference Vega though,
Sapphire something. Maybe they made changes?
vbios is attached.
// Daniel
On 5 July 2018 at 15:38, Alex Deucher wrote:
> On Mon, Jul 2, 2018 at 5:39 PM, Daniel Andersson wrote:
>> Sure, bisecting gets me 6e65fb862064663ad3a08f9
On Mon, Jul 2, 2018 at 5:39 PM, Daniel Andersson wrote:
> Sure, bisecting gets me 6e65fb862064663ad3a08f964af1e8f3f2abf688 .
>
> In drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c,
> get_firmware_info_v3_1() works but get_firmware_info_v3_2() does not
> do the right thing for my Vega.
>
> Could
Sure, bisecting gets me 6e65fb862064663ad3a08f964af1e8f3f2abf688 .
In drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c,
get_firmware_info_v3_1() works but get_firmware_info_v3_2() does not
do the right thing for my Vega.
Could I break my GPU if I were to set some bad/wrong frequency there?
lsp
On Mon, Jul 2, 2018 at 3:21 PM, Daniel Andersson wrote:
> I get:
> [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
> on boot. This started happening on 4.17 and is still an issue on 4.18-rc2.
>
> I have a Vega64 connected on Display Port to a monitor(1440p). The monitor
> doesn't have any addi
I get:
[drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
on boot. This started happening on 4.17 and is still an issue on 4.18-rc2.
I have a Vega64 connected on Display Port to a monitor(1440p). The monitor
doesn't have any additional ports so I can't test HDMI.
xrandr:
Screen 0: minimum 320 x
12 matches
Mail list logo
