How to map depth=30 fb to XBGR instead of XRGB?
NVIDIA hardware, prior to Kepler, only supports XBGR2101010. However drmAddFB with depth = 30 will use the mapping in drm_mode_legacy_fb_format and pick the XRGB version of the format. One solution is to tell userspace "stop using addfb, move to addfb2". However I'm hoping that there's some sort of semi-clean way of dealing with such driver eccentricities without resorting to changing userspace. Can the ioctl be handled in the driver perhaps? Or would it be reasonable to add a callback in drm_driver? Suggestions welcome. -ilia ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[pull] amdgpu and ttm drm-next-4.16
Hi Dave, Last few updates for 4.16: - Misc fixes for amdgpu - Enable swapout for reserved BOs during allocation for ttm - Misc cleanups for ttm The following changes since commit df2869abd92b740af141ee2eb081bfc69bd80877: Merge branch 'drm-next-4.16' of git://people.freedesktop.org/~agd5f/linux into drm-next (2017-12-21 11:17:45 +1000) are available in the git repository at: git://people.freedesktop.org/~agd5f/linux drm-next-4.16 for you to fetch changes up to 104bd2ca1124dfd9aa904d5f5a96253ef2b580f6: drm/amdgpu: Correct the IB size of bo update mapping. (2017-12-30 22:24:20 -0500) Christian König (5): drm/amdgpu: separate VMID and PASID handling drm/amdgpu: rename vm_id to vmid drm/amdgpu: drop client_id from VM drm/ttm: drop the spin in delayed delete if the trylock doesn't work drm/amdgpu: fix VM faults with per VM BOs Emily Deng (1): drm/amdgpu: Correct the IB size of bo update mapping. Rex Zhu (1): drm/amd/pp: Get and save CZ/ST smu version Roger He (7): drm/ttm: call ttm_bo_swapout directly when ttm shrink drm/ttm: use an operation ctx for ttm_mem_global_alloc drm/ttm: use an operation ctx for ttm_mem_global_alloc_page drm/ttm: use an operation ctx for ttm_tt_populate in ttm_bo_driver (v2) drm/ttm: use an operation ctx for ttm_tt_bind drm/ttm: add new function to check if bo is allowable to evict or swapout drm/ttm: enable swapout for reserved BOs during allocation Tan Xiaojun (10): drm/ttm: add ttm_bo_io_mem_pfn to check io_mem_pfn drm/ast: remove the default io_mem_pfn set drm/bochs: remove the default io_mem_pfn set drm/cirrus: remove the default io_mem_pfn set drm/mgag200: remove the default io_mem_pfn set drm/nouveau: remove the default io_mem_pfn set drm/qxl: remove the default io_mem_pfn set drm/radeon: remove the default io_mem_pfn set drm/virtio: remove the default io_mem_pfn set drm/vmwgfx: remove the default io_mem_pfn set drivers/gpu/drm/amd/amdgpu/Makefile | 3 +- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 6 +- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v7.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_cgs.c | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c| 9 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c | 459 + drivers/gpu/drm/amd/amdgpu/amdgpu_ids.h | 91 + drivers/gpu/drm/amd/amdgpu/amdgpu_ih.h| 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 8 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h | 28 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 9 +- drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_vce.h | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c| 468 +++--- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h| 48 +-- drivers/gpu/drm/amd/amdgpu/cik_ih.c | 2 +- drivers/gpu/drm/amd/amdgpu/cik_sdma.c | 14 +- drivers/gpu/drm/amd/amdgpu/cz_ih.c| 2 +- drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c | 14 +- drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c | 18 +- drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 18 +- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 18 +- drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c | 2 +- drivers/gpu/drm/amd/amdgpu/gmc_v7_0.c | 2 +- drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c | 2 +- drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 16 +- drivers/gpu/drm/amd/amdgpu/iceland_ih.c | 2 +- drivers/gpu/drm/amd/amdgpu/sdma_v2_4.c| 16 +- drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c| 16 +- drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c| 18 +- drivers/gpu/drm/amd/amdgpu/si_dma.c | 16 +- drivers/gpu/drm/amd/amdgpu/si_ih.c| 2 +- drivers/gpu/drm/amd/amdgpu/tonga_ih.c | 2 +- drivers/gpu/drm/amd/amdgpu/uvd_v4_2.c | 2 +- drivers/gpu/drm/amd/amdgpu/uvd_v5_0.c | 2 +- drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c | 26 +- drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c | 36 +- drivers/gpu/drm/amd/amdgpu/vce_v3_0.c | 10 +- drivers/gpu/drm/amd/amdgpu/vce_v4_0.c | 18 +- drivers/gpu/drm/amd/amdgpu/vcn_v1_0.c | 36 +- drivers/gpu/drm/amd/amdgpu/vega10_ih.c| 4 +- drivers/gpu/drm/amd/powerplay/smumgr/cz_smumgr.c | 13 + drivers/gpu/drm/ast/ast_ttm.c | 6 +- drivers/gpu/drm/bochs/bochs_mm.c | 1 - drivers/gpu/drm/cirrus/cirrus_ttm.c | 6 +-
Re: [drm-tip:drm-tip 1/7] drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:219:6: error: redefinition of 'dm_dp_mst_dc_sink_create'
Drm-tip rebuild created this function duplication in some merge resolution... not sure where that came from or started... But Lucas had warned me yesterday morning... So, yesterday night I added a fix-up on drm-rerere that remove the duplication on drm-tip... and that should be fixed by now I think... Could you please fetch and recheck?! On Dec 30, 2017, at 9:10 AM, Wu, Fengguang> wrote: tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: 16432d39f2cbdc7a8798df3ebb4f7c882fb23132 commit: a79b622ef5cad1b3a868a1d7250494e39bb04c05 [1/7] Merge remote-tracking branch 'airlied/drm-next' into drm-tip config: i386-randconfig-b0-12302345 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: git checkout a79b622ef5cad1b3a868a1d7250494e39bb04c05 # save the attached .config to linux build tree make ARCH=i386 Note: the drm-tip/drm-tip HEAD 16432d39f2cbdc7a8798df3ebb4f7c882fb23132 builds fine. It only hurts bisectibility. All errors (new ones prefixed by >>): drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:219:6: error: redefinition of 'dm_dp_mst_dc_sink_create' void dm_dp_mst_dc_sink_create(struct drm_connector *connector) ^ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:183:6: note: previous definition of 'dm_dp_mst_dc_sink_create' was here void dm_dp_mst_dc_sink_create(struct drm_connector *connector) ^ vim +/dm_dp_mst_dc_sink_create +219 drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c 54427651 Jerry Zuo 2017-09-20 218 becd0875 Jerry (Fangzhi Zuo 2017-12-01 @219) void dm_dp_mst_dc_sink_create(struct drm_connector *connector) becd0875 Jerry (Fangzhi Zuo 2017-12-01 220) { becd0875 Jerry (Fangzhi Zuo 2017-12-01 221)struct amdgpu_dm_connector *aconnector = to_amdgpu_dm_connector(connector); becd0875 Jerry (Fangzhi Zuo 2017-12-01 222)struct edid *edid; becd0875 Jerry (Fangzhi Zuo 2017-12-01 223)struct dc_sink *dc_sink; becd0875 Jerry (Fangzhi Zuo 2017-12-01 224)struct dc_sink_init_data init_params = { becd0875 Jerry (Fangzhi Zuo 2017-12-01 225).link = aconnector->dc_link, becd0875 Jerry (Fangzhi Zuo 2017-12-01 226).sink_signal = SIGNAL_TYPE_DISPLAY_PORT_MST }; becd0875 Jerry (Fangzhi Zuo 2017-12-01 227) becd0875 Jerry (Fangzhi Zuo 2017-12-01 228)edid = drm_dp_mst_get_edid(connector, >mst_port->mst_mgr, aconnector->port); becd0875 Jerry (Fangzhi Zuo 2017-12-01 229) becd0875 Jerry (Fangzhi Zuo 2017-12-01 230)if (!edid) { becd0875 Jerry (Fangzhi Zuo 2017-12-01 231) drm_mode_connector_update_edid_property( becd0875 Jerry (Fangzhi Zuo 2017-12-01 232)>base, becd0875 Jerry (Fangzhi Zuo 2017-12-01 233)NULL); becd0875 Jerry (Fangzhi Zuo 2017-12-01 234)return; becd0875 Jerry (Fangzhi Zuo 2017-12-01 235)} becd0875 Jerry (Fangzhi Zuo 2017-12-01 236) becd0875 Jerry (Fangzhi Zuo 2017-12-01 237)aconnector->edid = edid; becd0875 Jerry (Fangzhi Zuo 2017-12-01 238) becd0875 Jerry (Fangzhi Zuo 2017-12-01 239)dc_sink = dc_link_add_remote_sink( becd0875 Jerry (Fangzhi Zuo 2017-12-01 240)aconnector->dc_link, becd0875 Jerry (Fangzhi Zuo 2017-12-01 241)(uint8_t *)aconnector->edid, becd0875 Jerry (Fangzhi Zuo 2017-12-01 242) (aconnector->edid->extensions + 1) * EDID_LENGTH, becd0875 Jerry (Fangzhi Zuo 2017-12-01 243)_params); becd0875 Jerry (Fangzhi Zuo 2017-12-01 244) becd0875 Jerry (Fangzhi Zuo 2017-12-01 245)dc_sink->priv = aconnector; becd0875 Jerry (Fangzhi Zuo 2017-12-01 246)aconnector->dc_sink = dc_sink; becd0875 Jerry (Fangzhi Zuo 2017-12-01 247) becd0875 Jerry (Fangzhi Zuo 2017-12-01 248) amdgpu_dm_add_sink_to_freesync_module( becd0875 Jerry (Fangzhi Zuo 2017-12-01 249)connector, aconnector->edid); becd0875 Jerry (Fangzhi Zuo 2017-12-01 250) becd0875 Jerry (Fangzhi Zuo 2017-12-01 251) drm_mode_connector_update_edid_property( becd0875 Jerry (Fangzhi Zuo 2017-12-01 252) >base, aconnector->edid); becd0875 Jerry (Fangzhi Zuo 2017-12-01 253) } becd0875 Jerry (Fangzhi Zuo 2017-12-01 254) :: The code at line 219 was first introduced by commit :: becd0875f4393a992afbf57aa323f7bf1a71c3ff drm/amd/display: Fix rehook MST display not light back on :: TO: Jerry (Fangzhi) Zuo > :: CC: Alex Deucher > --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation <.config.gz> ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104347] AMD RX 580: Hide/Show window sometimes corrupts screen (see screenshot)
https://bugs.freedesktop.org/show_bug.cgi?id=104347 --- Comment #9 from Arthur Borsboom--- Hi Michel, Although I have not tested yet about mesa 17.2, I have noticed that this issue only appears in the full or small sized window of Chromium. So, until now it only has happened to Chromium; but this did not happen with my previous Nvidia card, so I guess there is a relationship with my (new) RX 580. I also noticed that it only happens, once in a while (every 15-30 minutes) and when I active the Chromium window (bring it to the front). The garbled window auto recovers after a short time, I guess 5 seconds. Does this new information help to narrow the search? Do you still want me to try with mesa 17.2? Or do you have another plan of attack? Since I am on a rolling release these are currently my key components: * Kernel: 4.14.8 * Kernel driver: amdgpu * X11: xf86-video-amdgpu 1.4.0 * Mesa: mesa 17.3.1 * Chromium: 63.0.3239.108 * chrome://gpu/ gives: https://bugs.freedesktop.org/attachment.cgi?id=136453> Maybe the chrome gpu page gives a clue? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104347] AMD RX 580: Hide/Show window sometimes corrupts screen (see screenshot)
https://bugs.freedesktop.org/show_bug.cgi?id=104347 --- Comment #8 from Arthur Borsboom--- Created attachment 136453 --> https://bugs.freedesktop.org/attachment.cgi?id=136453=edit Chrome GPU detailed overview -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 100759] [r600] System freeze on resume from sleep on battery with DPM enabled and linux 4.10
https://bugs.freedesktop.org/show_bug.cgi?id=100759 --- Comment #1 from Nicola Mori--- I found the time to bisect and found that the culprit is: commit 1c331f75aa6ccbf64ebcc5a019183e617c9d818a Author: Lucas Stach Date: Sun Oct 23 01:05:33 2016 +0200 drm/radeon/pm: autoswitch power state when in balanced mode The current default of always using the performance power state leads to increased power consumption of mobile devices, which have a dedicated battery power state. Switch between the performance and battery power state automatically, dpending on the current AC power status, when the user asked for the balanced power state. The user can still override this logic by asking for the performance or battery power state explicitly. Tested-by: Michel Dänzer Acked-by: Christian König Signed-off-by: Lucas Stach Signed-off-by: Alex Deucher I don't have the skills to understand what's broken, but I can test an eventual patch if someone provides it. Thanks. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[drm-tip:drm-tip 1/7] drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:219:6: error: redefinition of 'dm_dp_mst_dc_sink_create'
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: 16432d39f2cbdc7a8798df3ebb4f7c882fb23132 commit: a79b622ef5cad1b3a868a1d7250494e39bb04c05 [1/7] Merge remote-tracking branch 'airlied/drm-next' into drm-tip config: i386-randconfig-b0-12302345 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: git checkout a79b622ef5cad1b3a868a1d7250494e39bb04c05 # save the attached .config to linux build tree make ARCH=i386 Note: the drm-tip/drm-tip HEAD 16432d39f2cbdc7a8798df3ebb4f7c882fb23132 builds fine. It only hurts bisectibility. All errors (new ones prefixed by >>): >> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:219:6: >> error: redefinition of 'dm_dp_mst_dc_sink_create' void dm_dp_mst_dc_sink_create(struct drm_connector *connector) ^ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:183:6: note: previous definition of 'dm_dp_mst_dc_sink_create' was here void dm_dp_mst_dc_sink_create(struct drm_connector *connector) ^ vim +/dm_dp_mst_dc_sink_create +219 drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c 54427651 Jerry Zuo 2017-09-20 218 becd0875 Jerry (Fangzhi Zuo 2017-12-01 @219) void dm_dp_mst_dc_sink_create(struct drm_connector *connector) becd0875 Jerry (Fangzhi Zuo 2017-12-01 220) { becd0875 Jerry (Fangzhi Zuo 2017-12-01 221) struct amdgpu_dm_connector *aconnector = to_amdgpu_dm_connector(connector); becd0875 Jerry (Fangzhi Zuo 2017-12-01 222) struct edid *edid; becd0875 Jerry (Fangzhi Zuo 2017-12-01 223) struct dc_sink *dc_sink; becd0875 Jerry (Fangzhi Zuo 2017-12-01 224) struct dc_sink_init_data init_params = { becd0875 Jerry (Fangzhi Zuo 2017-12-01 225) .link = aconnector->dc_link, becd0875 Jerry (Fangzhi Zuo 2017-12-01 226) .sink_signal = SIGNAL_TYPE_DISPLAY_PORT_MST }; becd0875 Jerry (Fangzhi Zuo 2017-12-01 227) becd0875 Jerry (Fangzhi Zuo 2017-12-01 228) edid = drm_dp_mst_get_edid(connector, >mst_port->mst_mgr, aconnector->port); becd0875 Jerry (Fangzhi Zuo 2017-12-01 229) becd0875 Jerry (Fangzhi Zuo 2017-12-01 230) if (!edid) { becd0875 Jerry (Fangzhi Zuo 2017-12-01 231) drm_mode_connector_update_edid_property( becd0875 Jerry (Fangzhi Zuo 2017-12-01 232) >base, becd0875 Jerry (Fangzhi Zuo 2017-12-01 233) NULL); becd0875 Jerry (Fangzhi Zuo 2017-12-01 234) return; becd0875 Jerry (Fangzhi Zuo 2017-12-01 235) } becd0875 Jerry (Fangzhi Zuo 2017-12-01 236) becd0875 Jerry (Fangzhi Zuo 2017-12-01 237) aconnector->edid = edid; becd0875 Jerry (Fangzhi Zuo 2017-12-01 238) becd0875 Jerry (Fangzhi Zuo 2017-12-01 239) dc_sink = dc_link_add_remote_sink( becd0875 Jerry (Fangzhi Zuo 2017-12-01 240) aconnector->dc_link, becd0875 Jerry (Fangzhi Zuo 2017-12-01 241) (uint8_t *)aconnector->edid, becd0875 Jerry (Fangzhi Zuo 2017-12-01 242) (aconnector->edid->extensions + 1) * EDID_LENGTH, becd0875 Jerry (Fangzhi Zuo 2017-12-01 243) _params); becd0875 Jerry (Fangzhi Zuo 2017-12-01 244) becd0875 Jerry (Fangzhi Zuo 2017-12-01 245) dc_sink->priv = aconnector; becd0875 Jerry (Fangzhi Zuo 2017-12-01 246) aconnector->dc_sink = dc_sink; becd0875 Jerry (Fangzhi Zuo 2017-12-01 247) becd0875 Jerry (Fangzhi Zuo 2017-12-01 248) amdgpu_dm_add_sink_to_freesync_module( becd0875 Jerry (Fangzhi Zuo 2017-12-01 249) connector, aconnector->edid); becd0875 Jerry (Fangzhi Zuo 2017-12-01 250) becd0875 Jerry (Fangzhi Zuo 2017-12-01 251) drm_mode_connector_update_edid_property( becd0875 Jerry (Fangzhi Zuo 2017-12-01 252) >base, aconnector->edid); becd0875 Jerry (Fangzhi Zuo 2017-12-01 253) } becd0875 Jerry (Fangzhi Zuo 2017-12-01 254) :: The code at line 219 was first introduced by commit :: becd0875f4393a992afbf57aa323f7bf1a71c3ff drm/amd/display: Fix rehook MST display not light back on :: TO: Jerry (Fangzhi) Zuo:: CC: Alex Deucher --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation .config.gz Description: application/gzip ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 101739] An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly
https://bugs.freedesktop.org/show_bug.cgi?id=101739 --- Comment #6 from ysblo...@gmail.com --- addendum : using the glsl_correct_derivatives_after_discard=true commandline option does work. But a big but : FPS took a nosedive. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 101739] An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly
https://bugs.freedesktop.org/show_bug.cgi?id=101739 --- Comment #5 from ysblo...@gmail.com --- (In reply to nadro-linux from comment #4) > You can fix that issue by added this entry to drirc file: > --- > > > > --- > I hope that it will be permanently added to mesa official drirc file. I just tried this, has no effect for me. At least not on mesa 17.3.1 -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 101739] An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly
https://bugs.freedesktop.org/show_bug.cgi?id=101739 --- Comment #4 from nadro-li...@wp.pl --- You can fix that issue by added this entry to drirc file: --- --- I hope that it will be permanently added to mesa official drirc file. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104412] RX 460 HDMI 4k 60fps not working, DisplayPort is.
https://bugs.freedesktop.org/show_bug.cgi?id=104412 --- Comment #7 from S.H.--- Hello, me again. I reverted the patch mentioned in Comment #4 and now I can enable 60Hz via modeline on both cards. I still don't get it automatically, which means console and X are still 30Hz at boot but I can force X at least manually to 60Hz. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104412] RX 460 HDMI 4k 60fps not working, DisplayPort is.
https://bugs.freedesktop.org/show_bug.cgi?id=104412 --- Comment #6 from S.H.--- Hello, Last night I was able to get my hands on a Gigabyte RX460 and did some testing. Booting and normal startup with the Gigabyte also only used 4k@30Hz but I was able to reach 4k@60Hz by adding a modeline via xrandr. With the Saphhire I am not able to get 4k@60Hz even with a custom modeline set via xrandr. Something seems broken here and I don't think both vendors messed up their cards. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel