Hi there,
I'm a bit confused by how xrandr seems to accomplish the same things
in two different ways.
For example:
xrandr --output LVDS1 --mode 1366x768 VERSUS to xrandr -s 1366x768
xrandr --output HDMI1 --rotate left VERSUS xrandr -o left
Of course I prefer `xrandr -s` or `xrandr -o` as it's
Hi there,
What's good general advice for dealing with xrandr issues for end users?
I tried to help a user here:
http://askubuntu.com/questions/123953/
And I ended up pointing him to Intel's report bug page
http://intellinuxgraphics.org/how_to_report_bug.html which does seem
to be a really high ba
Thanks, if you don't know if the screen is LVDS1, HDMI1 or VGA1 etc.
How are people expected to script it? Just grep " connected"?
Thanks,
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/m
Firstly why CC both xorg@lists.x.org, x...@freedesktop.org ?
On 25 April 2012 01:02, Alex Deucher wrote:
> The names give a pretty good indication as they generally map to the
> physical connector.
Understood, but I'm looking for a simple "default", which I have seen
on some setups in the past.
On 25 April 2012 20:05, Marius Gedminas wrote:
> Do you find the existing GUI tools for monitor configuration inconvenient?
Yes. In Webconverger's case, we deploy kiosks for use in schools and
libraries. We need to set them up in advance on different sorts of
hardware.
Hardware that could be LVD
On 25 April 2012 20:24, Alex Deucher wrote:
> If the are locked down kiosks then just configure them how you want
> them statically and then don't let the user change the configuration.
> If (B) is the most important then why allow users to mess with the
> displays at all?
Unfortunately I'm relia
On 25 April 2012 20:49, Alex Deucher wrote:
> Then perhaps provide instructions to walk them through the process?
Well, atm I tell the to go into debug mode and launch a terminal.
Which is obviously too difficult for many.
> Is all the hw the same or does it vary from kiosk to kiosk? Maybe you
On 25 April 2012 21:08, Simon Farnsworth wrote:
> Unless I'm misunderstanding, you have one connected display - you want to
> configure just that display. XRandR tells you which outputs are connected
> (exposed in the xrandr utility as "connected", "unknown" or "disconnected"),
> so your script ca
On 25 April 2012 21:20, Alex Deucher wrote:
> an xorg.conf with several monitor sections whose identifiers match the
Thanks for the suggestion, though I'm trying to avoid the clunky
xorg.conf changes / API. Prefer the xrandr API, but I'm seeing its
limitations.
Hoping someone will get back to m
Hi there,
I'm trying to reliably configure a touch input device in X. However the
IDs can change between reboots.
From doing some googling, it seems that most people script something
like:
ID=`xinput list | grep -Eo 'ouchpad\s*id\=[0-9]{1,2}' | grep -Eo
'[0-9]{1,2}'`
To find the ID reliably. I
On Mon, 8 Jun 2015, at 03:17 PM, Ingo Krabbe wrote:
> the IDs are a property of the XINPUT extension and the xinput(1) tool can
> be used to modify XINPUT properties. It's the tool of choice for XINPUT
> devices. What you might think of is a modification of the kernel (evdev)
> devices, for example
On Mon, 8 Jun 2015, at 03:27 PM, Ingo Krabbe wrote:
> No, I say, you can view/change USB Properties finding the a devices
> through USB IDs and you can view/change XINPUT Properties addressing the
> device via xinput and it's XINPUT.ID.
Ok, I think I understand that.
But how do I permanently set
On Tue, 9 Jun 2015, at 01:23 PM, Peter Korsgaard wrote:
> In the likely situation that the touchscreens are of the same type they
> will have the same device name, so you need to fish out the
> corresponding /dev/input/event* device node and pass it to udevadm info
> (assuming that the server is lo
13 matches
Mail list logo
