This confirm that probably what I have backported is not enough to have full MST support. If not then read on. Comment 40 Julien Cristau 2010-04-15 08:25:35 UTC *** Bug 27660 has been marked as a duplicate of this bug. *** Comment 41 Antti Mäkelä 2010-04-15 09:04:17 UTC My workaround right now Standard VESA modes can be generated with the utility cvt. check over here
And while the xrandr --fbmm hack posted above (that parses the xrandr output to get the physical size to pass to xrandr) works without patching Xorg, it's just too absurd to Before your comment 58 reached my eyes, I had to put that Intel host aside to work on the MGA host, so I used that to demonstrate what I wrote in I will summarize the points that I think are important and add a few points. Fair enough. > That said, I reread comment 6, which does indicate manual intervention via > config file or xrandr is normally required to achieve accurate DPI, normal > meaning ATI,
And, you can even use xrandr to change > > things on the fly. > > That's good, but I really don't know why it's necessary. In case anyone's interested, here's the patch I've been applying which adds a so-called "knob" to restore the original behaviour. Read more...
Look into the future. Yes, and the default font size should be set to match the screen resolution, as is the practice in many other desktop environments. This also means that I can't suspend and resume without losing the external monitors. The time now is 04:38 PM.
Would you mind giving the patched kernel from ppa:dgadomski/linux-mst a try? Comment 6 Keith Packard 2009-09-16 21:20:56 UTC The 'screen size' as reported in the core protocol now respects the DPI value given by the user or config file and ignores the The options available in this section strongly depend on the driver used. http://www.nvidia.com/object/solaris-display-302.17-driver Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search
It is referenced by its descriptive name. Dariusz Gadomski (dgadomski) wrote on 2014-11-26: #96 I'm glad it works for you Ben. so I can keep an eye out for the update I need. If the X server resolution is set smaller than the actual, then fonts will be smaller than expected, not larger. > (**) intel(0): DPI set to (363, 486) This looks to
Dariusz Gadomski (dgadomski) wrote on 2014-12-11: #112 Krzysztof, you don't have to downgrade the kernel. Again, I am happy to test, but I could really help some instructions and help from the people here that seem to be able to install it. With laptops, you can't really choose the distance at which you sit from the screen, you're bound by the keyboard. I've just set "Xft.dpi: 135" in /etc/X11/xdm/Xresources with the result that the fonts and the mouse pointer in xdm are bigger now so it seems that xdm has now the right
Using your instructions, I installed the new kernel and intel driver. http://consumer5online.com/driver-not/driver-not-capable-db2.php Use this only, when using non RandR 1.2 capable drivers. But, every time I plugged in a second monitor the display would get screen corruption and the display would get garbled. However, these units are only meaningful if the DPI is correct.
Click the Back button to try another link. xdpyinfo always reports a 96x96 DPI value. Justin Standring (b-me-f) wrote on 2015-04-08: #128 I'd like to confirm that Jace's solution (#127) worked for me using a Lenovo T440s on an Ultra Dock with two displays connected on http://consumer5online.com/driver-not/driver-not-capable-0.php Then you will get a warning and you need to keep your new configuration.
I just tested the 3.16.0-28 kernel and unfortunately it doesn't even detect all of my displays correctly -- it only shows 1 external monitor in the display settings rather than both. I got no external monitors recognised (instead of 1, but had 2 connected) and my external usb from the replicator ports did not work. Monitors have not attained the highest useful DPI.
Even though it's listed in lspci as a 'Network controller: Intel Corporation Wireless 7260 (rev 6b)', rfkill list shows nothing. Display manager is xdm. UPDATE: Updated the bug report after it was pointed out that the original test hardware, a Lenovo x230 isn't DP 1.2 capable. because it isn't working for me..
For example: $ xrandr --output VGA-0 --mode 800x600There are two disadvantages to using .xprofile for xrandr settings. Will try to set size via config then. However, as one can see in my attachment this has to be set for every monitor and then the correct Monitor section associated with the output. have a peek at these guys I upgraded to 14.10, updated to the 3.17.4 kernel, and rebooted.
Donate to FreeBSD . GeForce 600 series:GTX 690, GTX 680, GTX 670, GT 645, GT 640, GT 630, GT 620, GT 610, 605GeForce 600M series:GTX 675M, GTX 670M, GTX 660M, GT 650M, GT 640M LE, While we do value strict technical correctness, > we don't value it to the point of crippling everything else. Fixed a bug that caused audio over HDMI to not work on some GPUs after querying the RandR configuration (e.g., `xrandr -q`).