Comment # 5
on bug 108778
from Garth Theisen
Reviewing my 4.18.18 log, the dce110_link_encoder_construct is present, but not 'amdgpu: [powerplay] Failed to retrieve minimum clocks.'. [ 3.314952] [drm] amdgpu: 8192M of VRAM memory ready [ 3.314954] [drm] amdgpu: 8192M of GTT memory ready. [ 3.314967] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 3.315973] [drm] PCIE GART of 1024M enabled (table at 0x000000F4007E9000). [ 3.317330] [drm] Internal thermal controller with fan control [ 3.343843] random: alsactl: uninitialized urandom read (4 bytes read) [ 3.343850] random: alsactl: uninitialized urandom read (4 bytes read) [ 3.347055] [drm] Invalid PCC GPIO: 13! [ 3.347057] [drm] amdgpu: dpm initialized [ 3.356305] [drm] Found UVD firmware Version: 1.64 Family ID: 9 [ 3.357433] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [ 3.357629] [drm] PCIE gen 2 link speeds already enabled [ 3.365448] [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4! [ 3.365462] [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4! [ 3.365475] [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4! [ 3.377133] [drm] Display Core initialized with v3.1.44! [ 3.403803] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.403805] [drm] Driver supports precise vblank timestamp query. [ 3.442064] [drm] UVD initialized successfully. [ 3.570052] [drm] VCE initialized successfully. [ 3.572268] [drm] fb mappable at 0xD0BD0000 [ 3.572269] [drm] vram apper at 0xD0000000 [ 3.572270] [drm] size 8294400 [ 3.572271] [drm] fb depth is 24 [ 3.572271] [drm] pitch is 7680 [ 3.572350] fbcon: amdgpudrmfb (fb0) is primary device [ 3.576367] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 681000 pix_clk 148500 [ 3.593179] Console: switching to colour frame buffer device 240x67 [ 3.599360] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device [ 3.607152] [drm] Initialized amdgpu 3.26.0 20150101 for 0000:01:00.0 on minor 0 (In reply to Garth Theisen from comment #4) > After applying the patch 4.19.2 boots without the Init failure. > > There seems to be some additional issues present in the dmesg log after the > patch ... but this might be occurring for the 4.18.x series also. > > [ 3.705820] amdgpu: [powerplay] Failed to retrieve minimum clocks. > [ 3.705821] amdgpu: [powerplay] Error in phm_get_clock_info > [ 3.705922] [drm] dce110_link_encoder_construct: Failed to get > encoder_cap_info from VBIOS with error code 4! > [ 3.705932] [drm] dce110_link_encoder_construct: Failed to get > encoder_cap_info from VBIOS with error code 4! > [ 3.705943] [drm] dce110_link_encoder_construct: Failed to get > encoder_cap_info from VBIOS with error code 4! > [ 3.720386] [drm] Display Core initialized with v3.1.59! > [ 3.748551] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 3.748552] [drm] Driver supports precise vblank timestamp query. > [ 3.786502] [drm] UVD initialized successfully. > [ 3.907523] [drm] VCE initialized successfully. > [ 3.911228] [drm] fb mappable at 0xD0BD0000 > [ 3.911230] [drm] vram apper at 0xD0000000 > [ 3.911232] [drm] size 8294400 > [ 3.911233] [drm] fb depth is 24 > [ 3.911234] [drm] pitch is 7680 > [ 3.911401] fbcon: amdgpudrmfb (fb0) is primary device > [ 3.937471] Console: switching to colour frame buffer device 240x67 > [ 3.942828] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device > [ 3.949554] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:01:00.0 on > minor 0
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
