Created attachment 124654 [details] HD resolution not getting enabled - log message with drm.debug=0x06 I am currently working on an embedded project using Minnowboard max. I have builded a customized Linux kernel-v4.4 and using u-boot (latest version) as Boot loader. The VESA driver in the u-boot takes more time to initialize,so I have disabled it. I am passing the kernel parameters "video=" to enable the HDMI port to which a monitor is connected. The monitor is connected via HDMI-DVI cable The video parameter arguments "video=HDMI-A-1:1920x1200@60mD video=VGA-1:d video=DP-1:d" From the dmesg I got to know that the 1920x1200 is not getting supported or there is some probing issue [ 2.922671] [drm:drm_mode_prune_invalid] Not using 1920x1200 mode: CLOCK_HIGH and the resolution is set to '1024x768' [ 3.153392] [drm:intel_dump_pipe_config] adjusted mode: [ 3.153399] [drm:drm_mode_debug_printmodeline] Modeline 0:"1024x768" 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0 Do you have any idea why this is happening ?. I have attached the dmesg logs - HD_resolution_not_working.txt With no video parameters passed , I am seeing that the display is not coming up. Please note that in both cases if I enable the VESA driver in the u-boot its working fine.
try removing the margins and reducing the blanking, video=HDMI-A-1:1920x1200@60RD
I have tried also with the argument video=HDMI-A-1:1920x1200@60RMD and have the same issue display not coming up. I saw from the logs and found that there is a parsing error and gone through the modedb.txt file and found a small mistake in the arguments passing The structure is, <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd] So I tried using the parameter video=HDMI-A-1:1920x1200MR@60D. Now the display is coming up in HD resolution. Thanks for your reply
Closing the bug since this is resolved. If you encounter any further issue, please open a new one.
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.