<div dir="ltr"><div dir="ltr">I'm seeing an issue where xrandr selects an invalid screen resolution/rate.<br><div dir="ltr"><div><div><div>It attempts to select 1920x1080@71 Hz, which my TV does not like.<br><br></div>I don't know exactly when this problem arose, as this system has been going for 6 months since power cycle. <br></div>This week, it got power cycled, and has been causing all sorts of problems.<br><br></div>It
have traced it down to the code thinking that 71 Hz is a valid refresh
rate. It seems to get this from xrandr. I don't know how.<br><br>xrandr gives me what appears to be reasonable: <br>dragon@mythfe1:~$ DISPLAY=:0.0 xrandr -q<br>Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767<br>DVI-D-0 disconnected (normal left inverted right x axis y axis)<br>HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1872mm x 1053mm<br> 3840x2160 60.00 + 59.94 50.00 29.97 25.00 23.98 <br> 4096x2160 59.94 50.00 29.97 25.00 24.00 23.98 <br> 2880x576 50.00 <br> 2880x480 59.94 <br> 1920x1080 60.00* 59.94 50.00 29.97 25.00 23.98 60.00 50.04 <br> 1680x1050 59.95 <br> 1600x900 60.00 <br> 1440x900 59.89 <br> 1440x576 50.00 <br> 1440x480 59.94 <br> 1280x1024 75.02 60.02 <br> 1280x800 59.81 <br> 1280x720 60.00 59.94 50.00 <br> 1152x864 75.00 <br> 1024x768 75.03 70.07 60.00 <br> 800x600 75.00 72.19 60.32 <br> 720x576 50.00 <br> 720x480 59.94 <br> 640x480 75.00 72.81 59.94 <br>DP-0 disconnected (normal left inverted right x axis y axis)<br>DP-1 disconnected (normal left inverted right x axis y axis)<br></div><div dir="ltr"><br></div><div>Here is the verbose output if anyone is interested: <a href="https://pastebin.com/qNYbjJg5" target="_blank">https://pastebin.com/qNYbjJg5</a></div><div><br></div><div>If i try to select 1920x1080@60.. I get an error <br></div><div>dragon@mythfe1:~$ DISPLAY=:0.0 xrandr -r 60<br>Rate 60.00 Hz not available for this size</div><div><br></div><div>Using
the myth gui i was very surprised to see 50, 64,65,66,67,68,69,70,71 as
viable choices.. not 60 hz.. These didn't make any sense to me..</div><div>I was able to figure out that they did infact from from xrandr... which i found (by accident), if i try to select 50 hz:</div><div><br></div><div>dragon@mythfe1:~$ DISPLAY=:0.0 xrandr --verbose -r 50<br> SZ: Pixels Physical Refresh<br><b>*0 1920 x 1080 ( 487mm x 274mm ) *50 64 65 66 67 68 69 70 71 </b><br> 1 4096 x 2160 (1040mm x 548mm ) 51 52 53 54 55 56 <br> 2 3840 x 2160 ( 975mm x 548mm ) 57 58 59 60 61 <br> 3 2880 x 576 ( 731mm x 146mm ) 62 <br> 4 2880 x 480 ( 731mm x 121mm ) 63 <br> 5 1680 x 1050 ( 426mm x 266mm ) 72 <br> 6 1600 x 900 ( 406mm x 228mm ) 73 <br> 7 1440 x 900 ( 365mm x 228mm ) 74 <br> 8 1440 x 576 ( 365mm x 146mm ) 75 <br> 9 1440 x 480 ( 365mm x 121mm ) 76 <br> 10 1280 x 1024 ( 325mm x 260mm ) 77 78 <br> 11 1280 x 800 ( 325mm x 203mm ) 79 <br> 12 1280 x 720 ( 325mm x 182mm ) 80 81 82 <br> 13 1152 x 864 ( 292mm x 219mm ) 83 <br> 14 1024 x 768 ( 260mm x 195mm ) 84 85 86 <br> 15 800 x 600 ( 203mm x 152mm ) 87 88 89 <br> 16 720 x 576 ( 182mm x 146mm ) 90 <br> 17 720 x 480 ( 182mm x 121mm ) 91 <br> 18 640 x 480 ( 162mm x 121mm ) 92 93 94 <br> 19 2560 x 1600 ( 650mm x 406mm ) 95 <br> 20 2560 x 1440 ( 650mm x 365mm ) 96 <br> 21 1920 x 1200 ( 487mm x 304mm ) 97 <br> 22 1600 x 1200 ( 406mm x 304mm ) 98 <br> 23 1366 x 768 ( 346mm x 195mm ) 99 <br>Current rotation - normal<br>Current reflection - none<br>Rotations possible - normal left inverted right <br>Reflections possible - X Axis Y Axis<br>Setting size to 0, rotation to normal<br>Setting reflection on neither axis</div><div><br></div><div>Incidentally if i issue the -r 50 command to xrandr, the TV is happy, and the tv info displays 1920x1080 60p.</div><div><br></div><div>So
my options are to turn off xrandr support.. (not ideal, as I use it to
change the resolution when watching 4k stuff [which works fine])..or
manually change the rate with xrandr -r 50 (with an laptop - not WAF
friendly!).</div><div><br></div><div>TV is a Samsung 4k (from 2016), video card is nvidia 1050.<br></div><div>I
originally found this on ubuntu 16.04.5 with myth master from the
summer. I don't quite know what changed following the reboot.. maybe
unapplied updates?</div><div>I tested today with ubuntu 18.04 with latest myth master, same behavior.<br></div><div><br></div>Any suggestions? </div></div>