From ArchWiki
Revision as of 01:08, 11 December 2013 by Mrmazda (Talk | contribs) (fix incorrect/incomplete attribution)

Jump to: navigation, search

Xinput and how-to about InputClasses

Shouldn't this page also say something about how you are supposed to look for the properties that you can actually put in the conf files? I mean, there's no way you can "guess" which properties each device you own has or how xorg "identify it" to use the the Match* option. Maybe a reference to another page (non-existent atm) could help.

The closest thing I've found is the Mouse acceleration page, so it could work as a start.

As long as you comply with Help:Style#Hypertext metaphor you are free and encouraged to add whatever you want and especially link to other related articles if relevant. In particular, Mouse acceleration is what is called an "orphan" article, meaning that it's not linked from any other (which is usually bad), so if you can fix that it's nothing but a good thing ;) -- Kynikos (talk) 16:05, 23 August 2012 (UTC)

Sample configurations

Anyone who has a verified working current or unique xorg.conf file written up that works, go ahead and post a link to it here for others to look at. Please do not in-line the entire configuration file; upload it somewhere else and link to it.

Please post input hotplugging configurations only, otherwise note that your config is not using input hotplugging. (Xorg 1.8 = udev) (From original editor on the article's section in question. AdamT (Talk) 00:09, 24 August 2013 (UTC))

Setting DPI manually

I'm not an Archlinux user, but Google sends me to this Wiki often. As a non-user, I cannot confirm this error on Archlinux unless I find time to learn how to install it. That's unlikely to happen in the foreseeable future.

The example 'Option "DPI" "96 x 96"' is invalid, because 96 x 96 is forced by the Xorg Xserver to start with as default to match Mac and Windows.

Unless the Archlinux X servers are different from other distros I've used, Option "DPI" "120 x 120" and others (144, 192, 108, etc) AFAICT only work for users of proprietary NVidia drivers, fail for certain on MGA (e.g. G400), Intel (e.g. 810, 845, 865, 915, 945, 3000, 4000), Radeon (e.g. rv200, rv250, rv380) & Nouveau (e.g. nv11, G84) on openSUSE 12.2, openSUSE 13.1, Fedora 20 and Mageia 4. I've been using Xorg for many many years and have never yet found any version in which this option is valid using any of the 4 FOSS drivers indicated. Mrmazda (talk) 05:25, 10 December 2013 (UTC)

As you probably noticed, Xorg#Display_size_and_DPI is marked as inaccurate with links to several bug reports about Xorg forcing 96x96. Part of Arch's philosophy is to avoid patching of packages whenever possible, but I see that xorg-server uses several patches (see [1]). I don't know which patches other distros use, but this option is not likely to depend on the patches.
Anyway, if you know a functioning method of manually setting DPI, feel free to share it - even a link to external documentation might be better than the current inaccurate information.
-- Lahwaacz (talk) 07:34, 10 December 2013 (UTC)
As help situations arise I point people to my which is mostly a lookup table designed to avoid need to calculate values for DisplaySize that will produce a desired DPI. DisplaySize in 'Section "Monitor"' has been reliable long-term with non-broken drivers, but since KScreen was released last summer, a workaround is required to get xorg.conf* to be obeyed at all by KDE. According to Alex Fiestas, KScreen 1.1 is proposed to allow xorg.conf* to be obeyed by default on single display systems. The workaround is to put [Module-kscreen]\nautoload=false in kdmrc. Whether other DEs have similar obstacles I have no idea. It would really be nice for those only wishing to force the hardware native DPI instead of an arbitrary one (which is usually what 96 is) for to be fixed, which means letting the server automatically as it already knows how make logical and physical DPI match. is one place that shows how to perform the calculations.

"To reduce scaling artifacts to GUI that use bitmaps" is not the only reason to choose +25% steps (96, 120, 144, 168, 192...). Most scalable fonts are tuned to 96 DPI, and step from pixel size to pixel size best at specific steps, of which +25% are the best. Mrmazda (talk)