Re: xorg disable GPU acceleration
Dnia sobota, 13 października 2018 09:22:16 Иван Талалаев pisze: [...] > Do you know how to disable xorg hardware acceleration? If you don't need hardware acceleration, maybe you could use the generic VESA driver instead of the NVidia one? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: X server
Dnia poniedziałek, 26 czerwca 2017 15:38:04 Lightning pisze: > Whenever I try to log on to my Raspberry pi the screen goes black and then > reappears. > When I try to do it from terminal, using the startx command, it says: > > (EE) > Fatal server error: > (EE) Could not write pid to lock file in /tmp/.tX1-lock > (EE) > (EE) > Please consult the The X.Org Foundation support > at http//wiki.x.org > for help. > (EE) > xinit: giving up > xinit: unable to connect to X server: Connection refused > xinit: server error Do you have the /tmp directory with proper permissions? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Xserver crashes whenever I reconnect my laptop to the docking station.
It used to work some time ago, but now it doesn't. I have a Dell latitute E7250 and a docking station. Whenever I connect my laptop, it crashes with the following message in the log: [ 396.530] (II) intel(0): Enabled output DP1-1 [ 396.530] (II) intel(0): Enabled output DP1-2 [ 396.530] (II) intel(0): Enabled output DP1-3 [ 396.530] (EE) [ 396.530] (EE) Backtrace: [ 396.531] (EE) 0: /usr/lib64/xorg/Xorg (OsLookupColor+0x139) [0x473999] [ 396.533] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7fc2063db41f] [ 396.533] (EE) 2: /lib64/libc.so.6 (readdir+0x2f) [0x7fc205cba15f] [ 396.534] (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x62730) [0x7fc1ff958180] [ 396.535] (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x64ff3) [0x7fc1ff95daa3] [ 396.535] (EE) 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6c1ad) [0x7fc1ff96bf0d] [ 396.536] (EE) 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6c1f1) [0x7fc1ff96c101] [ 396.537] (EE) 7: /usr/lib64/xorg/Xorg (RRGetInfo+0xa2) [0x50b7b2] [ 396.538] (EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x64f9b) [0x7fc1ff95da4b] [ 396.539] (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6c1ad) [0x7fc1ff96bf0d] [ 396.539] (EE) 10: /usr/lib64/xorg/Xorg (OsCleanup+0x641) [0x474901] [ 396.539] (EE) 11: /usr/lib64/xorg/Xorg (WaitForSomething+0xcc) [0x46ac6c] [ 396.539] (EE) 12: /usr/lib64/xorg/Xorg (SendErrorToClient+0x13a) [0x4364fa] [ 396.539] (EE) 13: /usr/lib64/xorg/Xorg (InitFonts+0x428) [0x43a7b8] [ 396.540] (EE) 14: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7fc205c225a1] [ 396.540] (EE) 15: /usr/lib64/xorg/Xorg (_start+0x2a) [0x42436a] [ 396.541] (EE) 16: ? (?+0x2a) [0x2a] [ 396.541] (EE) [ 396.541] (EE) Segmentation fault at address 0x4 [ 396.541] (EE) Fatal server error: [ 396.541] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 396.541] (EE) [ 396.541] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 396.541] (EE) Please also check the log file at "/home/users/ed/.local/share/xorg/Xorg.0.log" for additional information. [ 396.541] (EE) [ 396.541] (II) AIGLX: Suspending AIGLX clients for VT switch [ 396.600] (EE) Server terminated with error (1). Closing log file. Is it a kernel driver problem or Xserver itself? I'm using xorg-xserver-server 1.19.1-1 and kernel 4.9.6-1. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: xrandr weird issue running from a script
Dnia wtorek, 8 listopada 2016 14:19:08 Ratin pisze: > I am testing this simple script, calling it from php via apache web server. > But anything to do with xrandr is simply omitted by the scipt while > everything else include system calls like reboot etc works fine. Initially > I thought its because the DISPLAY env variable issue but it gets the > variable correctly in the logs, so now I am totally baffled. > > #! /bin/bash > > #export DISPLAY=:0 > export Dis=$(echo $DISPLAY) > echo "Display: $Dis" > /var/log/updateDDInfo.log > > checkHDMI=`sudo /usr/bin/xrandr| grep -i "HDMI1.*\ connected"` > checkDP=`sudo /usr/bin/xrandr --display :0| grep -i "DP1.*\ connected"` > echo "p.sh: HDMI Check: $checkHDMI " > /var/log/updateDDInfo.log > echo "p.sh: DP Check: $checkDP " > /var/log/updateDDInfo.log > > > If I run from command prompt I get the usual response: > "p.sh: DP Check: DP1 connected 3840x2160+1920+0 (normal left inverted right > x axis y axis) 607mm x 345mm" > > Anybody has any clue? Probably the problem is with X authorization, DISPLAY variable is not enough. In my scripts I do something like this: export XAUTHORITY=/home/users/$USER/.Xauthority export DISPLAY=:0 export QT_X11_NO_MITSHM=1 # don't now if xrandr needs this, probably not and then xrandr and other commands work. But these are bash scripts. You have to probaby do something similar. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Video projector not detected anymore (under Xorg 1.18.4)
Dnia czwartek, 3 listopada 2016 15:41:52 Philippe Dosch pisze: > Hi Folks, > > I'm assistant professor and I teach with the same video projectors > since years (with each of the last three kubuntu releases on my > laptop). I have a strange trouble since my last kubuntu update (2 > > weeks ago). Now I'm under kubuntu 16.10, with a 1.18.4 Xorg server: Hello! I have exactly the same problem and it lies in the kernel itself, probably in i915 driver, not in X. The change was introuced in kernel 4.7.0, the last of the 4.6.x line (4.6.7) works fine. The changes deal with detection of external Display Port and as a result I get first an error like this: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training at the kernel start (visible in dmesg). And then this output is not recognized anymore. I have filed a bug report https://bugs.freedesktop.org/show_bug.cgi?id=97397 Maybe you can confirm it or append yours so we make developers fix this? I have no idea how to fix this myself. I'm just keeping kernel 4.6.7 to use when I want to do my presentations. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Flickering single display in multi-head XRandR setup
Dnia piątek, 25 marca 2016 10:22:41 Andreas Mohr pisze: > On Thu, Mar 24, 2016 at 11:18:01AM +, xorg-requ...@lists.x.org wrote: > > Date: Thu, 24 Mar 2016 12:12:34 +0100 > > From: martin f krafft > > There is something very weird going on, which you may witness in the > > video downloadable here: > > http://scratch.madduck.net/xorg-display-flicker.mp4 (8Mb) > > > > The left-most display (DP0) keeps turning off and on (or resets > > itself), and generally, it flickers and the pixels jiggle around. > > The other two displays are perfectly fine. The monitor on DP1 is of > > exactly the same make as that on DP0. > > While it wasn't explicitly written, > let me just assume that you did try > actively connector/cable-swapping those "exactly the same make" monitors, > with identical results. I don't know how about Martin, but in my case it is the internal laptop screen which is flickering (very rarely, but it does). So it is not the matter of cables. In both cases (mine and Martin's) it affects the first, main screen (DP0 / eDP1). -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Flickering single display in multi-head XRandR setup
Dnia czwartek, 24 marca 2016 12:12:34 martin f krafft pisze: > Hello, > > I have a new Radeon R9 390 card, driving three monitors, two on > DisplayPort and one on DVI, in this order from left to right: [...] Wow! I mean, great - I'm not the only one to spot such weird behavior. In my case, I observed pretty weird screen flickers, also with the main screen. But in my case, it's about Intel HD graphics 5500. The main screen eDP1 is the FullHD interlan dislay, while external DP1 was FullHD Samsung SyncMaster 2270. I oserved it twice. At the first time, it disapeared after I switched off the external display with xrandr (after restoring it, the flicker did not reappea. Second time was just today, but it just settled after few seconds and few mouse movements. I don't understand it. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Can I set different DPI for two displays in my system?
Dnia czwartek, 10 marca 2016 12:15:58 Thomas Lübking pisze: [...] > Yes, but he mentioned moving windows across outputs, ie. explicitly NOT a > zaphod setup. Definitely, I'm not talking about zaphod setup. I want to have one desktop. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Can I set different DPI for two displays in my system?
Dnia wtorek, 8 marca 2016 11:31:25 Thomas Lübking pisze: [...] > In theory™ such could be achieved on the client level, ie. if you move a > window, it checks where it resides, calculates the natural dpi from device > measures and resolution, alters (in case of Qt, not idea about gtk ;-) the > device pixel ratio setting and cause a full update. That's how I think about it. But at this level I'm just a KDE user, I'm not going to implement such behavior myself. Unfortunately. I'll have to keep living with what we have ;-) > Of course you're still > in some conflict whenever the window is between two screens. MS Windows 8.1 does it in such way, that window is redrawn at some point between the screens, so its state may be "big" or "small", when it is on the boundary, depending on the screen to which the system assigns it. But it is completly not important. I'm thinking about windows, which are full on one of the screens - then it's fine. Anyway - thanks for your answer. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Can I set different DPI for two displays in my system?
Dnia wtorek, 8 marca 2016 00:22:39 Thomas Lübking pisze: > Nope, sorry. I was affraid of that... Windows, as I observed yesterday by accident, does some kind of window redraw, when I drag it between two screend with diferent DPIs. At certain point it - as I suppose - sends to a window a redraw request and provides it with a diffrent DPI setting, and you can easily bserve the window being redrawn with a ew DPI. I hoped we could obtain someting similar... -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Can I set different DPI for two displays in my system?
Hello. I have a laptop with 12.5" display and FullHD resolution, which means 176dpi density. I also use, in parallel, another FullHD 21.5" monitor, giving me almost half of the density as on the main screen. You can easily imagine, that since DPI is set the same for both screens, the window moved from one screen to another changes its physical size, which is pretty logical - although a bit annoying. Is it possible to configure X in such way, that each screen would work according to its own, real physical DPI? I know I can obtain an approximation of the thing I'm talking about if I set the frambuffer to around 4800x1800 and scale the output to the exterlan monitor twice: $ xrandr --fb 4800x1800 --output DP1-3 --scale-from 2880x1800 --output eDP1 -- pos 2880x0 But it looks awfull and is not usable. PS. My laptop has Intel(R) HD graphics 5500. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: What changes in xserver-1.18.x could affect KDE desktop effects?
Dnia niedziela, 28 lutego 2016 00:52:17 Thomas Lübking pisze: > You're running into this: > https://bugs.kde.org/show_bug.cgi?id=356992 > > => You need a more recent KWin (looks like you're on KDE4?) and until then > simply use GLX instead of EGL (you're enforcing latter by some > "KWIN_OPENGL_INTERFACE=egl" environment export) BINGO! I had it for some historical reasons, about which I remember nothing now. I have removed it and it works. Thanks. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: What changes in xserver-1.18.x could affect KDE desktop effects?
Dnia sobota, 27 lutego 2016 13:01:37 Thomas Lübking pisze:
> Please provide /var/log/Xorg.0.log and the glxinfo output.
Find all the files attached. *good are for xserver-1.17.4 while *bad are for
1.18.1.
I can observe, that KDE prints such messages during its startup:
kwin(12849) KWin::Compositor::slotCompositingOptionsInitialized: Initializing
OpenGL compositing
kwin(12849) KWin::SceneOpenGL::createScene: Forcing EGL native interface
through environment variable
kwin(12849) KWin::EglOnXBackend::initRenderingContext: EGL version: 1 . 4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500
(Broadwell GT2)
OpenGL version string: 3.0 Mesa 11.1.2
OpenGL shading language version string: 1.30
Driver: Intel
GPU class: Unknown
OpenGL version: 3.0
GLSL version: 1.30
Mesa version: 11.1.2
X server version: 1.18.1
Linux kernel version: 4.4.1
Direct rendering: yes
Requires strict binding:no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine:no
kwin(12849) KWin::EglOnXBackend::init: eglPostSubBufferNV not supported, have
to enable buffer preservation - which breaks v-sync and performance
kwin(12849) KWin::SceneOpenGL2::slotColorCorrectedChanged: Color correction:
false
kwin(12849) KWin::checkGLError: GL error ( Init ): "GL_INVALID_OPERATION"
kwin(12849): OpenGL 2 compositing setup failed
kwin(12849) KWin::checkGLError: GL error ( Init ): "GL_INVALID_OPERATION"
kwin(12849): OpenGL 1 compositing setup failed
QObject::connect: Cannot connect (null)::resetCompositing() to
KWin::Compositor::restart()
kwin(12849): Failed to initialize compositing, compositing disabled
These erors correspond to the following pieces of code:
ShaderManager::instance()->pushShader(ShaderManager::SimpleShader);
if (checkGLError("Init")) {
kError(1212) << "OpenGL 2 compositing setup failed";
init_ok = false;
return; // error
}
and
ShaderManager::disable();
setupModelViewProjectionMatrix();
if (checkGLError("Init")) {
kError(1212) << "OpenGL 1 compositing setup failed";
init_ok = false;
return; // error
}
I don't know, why they fail.
--
Łukasz Maśko_o)
Lukasz.Masko(at)ipipan.waw.pl /\\
Registered Linux User #61028 _\_V
Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana"
[ 21759.263]
X.Org X Server 1.18.1
Release Date: 2016-02-08
[ 21759.265] X Protocol Version 11, Revision 0
[ 21759.265] Build Operating System: PLD/Linux PLD/Team
[ 21759.266] Current Operating System: Linux laptok 4.4.1-1 #1 SMP Sun Jan 31
23:46:08 CET 2016 x86_64
[ 21759.266] Kernel command line: BOOT_IMAGE=/boot/vmlinuz
root=UUID=e6e08a9a-8085-4051-b0ab-2770c10383ae ro panic=300 quiet
intel_iommu=igfx_off
[ 21759.267] Build Date: 09 February 2016 07:04:22AM
[ 21759.268]
[ 21759.268] Current version of pixman: 0.34.0
[ 21759.270]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 21759.270] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 21759.273] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 27 23:45:45
2016
[ 21759.274] (==) Using config file: "/etc/X11/xorg.conf"
[ 21759.275] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 21759.275] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 21759.276] (**) Option "defaultserverlayout" "standard"
[ 21759.276] (**) ServerLayout "standard"
[ 21759.276] (**) |-->Screen "Screen" (0)
[ 21759.276] (**) | |-->Monitor ""
[ 21759.276] (**) | |-->Device "Card"
[ 21759.276] (==) No monitor specified for screen "Screen".
Using a default monitor configuration.
[ 21759.276] (**) Option "DontZap" "off"
[ 21759.276] (==) Automatically adding devices
[ 21759.276] (==) Automatically enabling devices
[ 21759.276] (==) Automatically adding GPU devices
[ 21759.276] (==) Max clients allowed: 256, resource mask: 0x1f
[ 21759.276] (**) FontPath set to:
/usr/share/fonts/local,
/usr/share/fonts/misc,
/usr/share/fonts/TTF,
/usr/share/fonts/OTF,
/usr/share/fonts/Type1,
What changes in xserver-1.18.x could affect KDE desktop effects?
Hello. I knw, this is not 100% X-related question, but... I'm using PLD linux distribution, where we are trying to have all the latest versions of packets. The problem is with xserver - everything works fine with 1.17.4, but if I switch to 1.18.0 (1.18.1 is the same), then KDE desktop (ver. 4.14) refuses to turn on desktop effects complaining about OpenGL. At the same time, glxinfo reports, that there are no problems with that, glxgears works fine... I'm confused. Maybe someone already knows, what changes between 1.17.4 and 1.18.0 od xserver paskage might influence KDE behavior here? If not, I'll keep on searching. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: How to refresh the list of outputs detected by xrandr?
Dnia czwartek, 19 listopada 2015 15:46:33 Łukasz Maśko pisze: > Dnia czwartek, 19 listopada 2015 14:01:26 Chris Wilson pisze: > [...] > > > > Is there a way to generate such notification using currently available > > > software tools, or am I limited to fix in the kernel to make it notify > > > dock change? > > > > Hmm, can't see a way to synthesize uevents. But still calling xrandr > > should be enough to do a forced reprobe of outputs. Without a hotplug > > event, there is a small 15s cache of the most recent probe. > > As far as I've noticed - it does not. But maybe I should wait a bit longer. > I'll check it as soon as possible. Unfortunately, in my case xrandr does not refresh its state. I left my laptop connected for more than a minute, but it was still reporting "home settings", not the ones, it really should see at work. I had to un-dock it and re-dock it while it was on, then xrandr started reporting proper outputs and modes. So I need a way to generate undock/dock event by software. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: How to refresh the list of outputs detected by xrandr?
Dnia czwartek, 19 listopada 2015 14:01:26 Chris Wilson pisze: [...] > > Is there a way to generate such notification using currently available > > software tools, or am I limited to fix in the kernel to make it notify > > dock change? > > Hmm, can't see a way to synthesize uevents. But still calling xrandr > should be enough to do a forced reprobe of outputs. Without a hotplug > event, there is a small 15s cache of the most recent probe. As far as I've noticed - it does not. But maybe I should wait a bit longer. I'll check it as soon as possible. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: How to refresh the list of outputs detected by xrandr?
Dnia czwartek, 19 listopada 2015 13:27:37 Chris Wilson pisze: [...] > The kernel is supposed to send a hotplug notification on resume that > should result in the list being updated. If I get you right, the kernel does not notify the change of a dock and therefore does not notify X about the change? Is there a way to generate such notification using currently available software tools, or am I limited to fix in the kernel to make it notify dock change? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
How to refresh the list of outputs detected by xrandr?
Hello. I have a Dell E7250 laptop. I'm using it with docking stations with external monitors connected. I have one dock at home and another one at work. The monitors connected to them differ, both in models and connectors (and therefore are recognized as different xrandr outputs). At home it looks like this: $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 276mm x 156mm 1920x1080 60.02*+ 48.03 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.3256.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP1-1 disconnected (normal left inverted right x axis y axis) DP1-2 disconnected (normal left inverted right x axis y axis) DP1-3 connected (normal left inverted right x axis y axis) 1440x900 59.89 + 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1152x720 59.97 1024x768 75.0860.00 832x624 74.55 800x600 75.0060.3256.25 848x480 60.00 640x480 75.0060.0059.94 720x400 70.08 DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) while at work like this: $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 276mm x 156mm 1920x1080 60.02*+ 48.03 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.3256.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP1-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 60.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.3256.25 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP1-2 disconnected (normal left inverted right x axis y axis) DP1-3 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) The problem is, that if I suspend my laptop while it is connected to one of the docking stations, it remembers the layout of available monitors and when I dock it onto the other station and resume, it still shows me the old list of outputs and modes. I need to undock it while running and dock it again to make it notify the change in outputs. Is there a software way to force xrandr to refresh its state and notify the change in connected devices? I'm using PLD linux with kernel 4.2.6, xserver 1.17.4, xrandr 1.4.3. Thanks. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
How do you deal with different physical DPIs on monitors?
Hello. I've recently bought a new 12.5" laptop with FullHD display, which gives a density about 176dpi. I'm also using an external 19" monitor with 1440x900 resolution (connected to a docking station), which has density almost equal to 90dpi. I have my KDE environment configured for the internal panel (dpi, font sizes and so on). It looks nice and allows for comfortable work. The problem is, that when I attach the external screen, everything rendered on it gets extremally big. It is easy to explain - pixels are almost 2 times bigger (physically). But it makes things look... bad. And the screen surface is "wasted" in a way. I tried to - in a way - emulate higher density with xrandr: $ xrandr --fb 4800x1800 --output DP1-3 --scale-from 2880x1800 --output eDP1 -- pos 2880x0 And it - in a way - does the job. Unfortunately, although sizes get adjusted, scaling does not always make things look acceptable, especially when text is considered. Do you have any ways of dealing wiht a problem of concurrently connected monitors with different physical pixel densities? What would you propose? Apart from buying another monitor, for it probably would need to be of UltraHD density ;-) -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Problems with acceleration configuration on Intel HD Graphics 5500.
Dnia sobota, 31 października 2015 17:32:13 Łukasz Maśko pisze: [...] > Now it's time for my question: is there a known way to make such > configuration work stable WITH hardware acceleration? SNA or UXA - not > important, but I want to have it working, together with KDE desktop effects. > It seems to be a waste to have such powerful hardware and not be able to > use it :-/ Maybe there are some tweaking options needed? Or shall I try > some older driver versions? It seems that all I needed was a BIOS update. My system runs fine now. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Problems with acceleration configuration on Intel HD Graphics 5500.
Hello. I've just purchased a Dell E7250 laptop equipped with Intel HD Graphics 5500 (i5-5300U). Today I've been fighting with Xorg configuration. I'm running PLD distribution (not important here) with kernel 4.2.4, xserver 1.17.4 and XOrg Intel driver 2.99.917. The problem is, that if I enable SNA acceleration, my laptop hangs very quickly after I start X - even if I use only twm as a window manager. I wouldn't even mention runnig KDE for it hangs extremally quickly. It works a bit longer if i switch off desktop effects in KDE. I've tried many tricks like switching to UXA, usinfg NoAccel option - it helps but just for a moment. Till now I've been using Dell D430 with i945MG internal card and it works very well, although not that fast. Now it's time for my question: is there a known way to make such configuration work stable WITH hardware acceleration? SNA or UXA - not important, but I want to have it working, together with KDE desktop effects. It seems to be a waste to have such powerful hardware and not be able to use it :-/ Maybe there are some tweaking options needed? Or shall I try some older driver versions? Thanks for any help. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Problems with acceleration configuration on Intel HD Graphics 5500.
Hello. I've just purchased a Dell E7250 laptop equipped with Intel HD Graphics 5500 (i5-5300U). Today I've been fighting with Xorg configuration. I'm running PLD distribution (not important here) with kernel 4.2.4, xserver 1.17.4 and XOrg Intel driver 2.99.917. The problem is, that if I enable SNA acceleration, my laptop hangs very quickly after I start X - even if I use only twm as a window manager. I wouldn't even mention runnig KDE for it hangs extremally quickly. Switching to UXA helps just a bit. Now twm-driven desktop works, but KDE has problems and I'm able to use it only if I turn off desktop effects. I have added such line in my XOrg configuration: Option "NoAccel" "true" in the card section. As a result I can find such message in XOrg log: (II) intel(0): SNA initialized with disabled backend I understand, that now I'm probably using software rendering, but at least my desktop seems to be stable (although I can see some strange artefacts, but it is less annoying than hanging environment). Till now I've been using Dell D430 with i945MG internal card and it works very well, although not that fast. Now it's time for my question: is there a known way to make such configuration work stable WITH hardware acceleration? SNA or UXA - not important, but I want to have it working. It seems to be a waste to have such powerful hardware and not be able to use it :-/ Maybe there are some tweaking options needed? Or shall I try some older driver versions? Thanks for any help. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Is there a way to force xrandr to re-read current available display modes?
Dnia piątek, 8 maja 2015 15:45:10 aiv...@latnet.lv pisze:
> Hi,
> My simple script
>
> #!/bin/bash
>
> IN="LVDS1"
> EXT="VGA1"
>
> case "$1" in
> on)
> xrandr --output $IN --off --output $EXT --auto
> ;;
> 1440)
> xrandr --output $IN --off --output $EXT --mode 1440x900
> ;;
> 1280)
> xrandr --output $IN --off --output $EXT --mode 1280x1024
> ;;
> off)
> xrandr --output $EXT --off --output $IN --auto
> ;;
> *)
> echo "Usage: $0 {on/off}\n"
> exit 2
> esac
>
>
> Said, at work display is 1280x1024
> You did:
> vga on
> You go at home where display is 1440x900
> vga 1440
> You go back to work
> vga 1280
> You go to cafee
> vga off
Thanks. I already have a similar script (even invoked in the same way), even
more automatic. It scans the list of currently available modes and selects
the highest available. I have it connected with a hot key. And the point is,
that if the list of modes is invalid, it cannot work properly. I can still
type manually vga 1280 at work, but it's not how I like it to be.
By the way - although it is not changing anything - I'm not disabling the
internal screen, I'm just attaching additional external screen.
--
Łukasz Maśko_o)
Lukasz.Masko(at)ipipan.waw.pl /\\
Registered Linux User #61028 _\_V
Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana"
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Is there a way to force xrandr to re-read current available display modes?
Hello. I have a Dell laptop, for which I have 2 docking stations (at home and at work), both with additional monitor connected. The monitors differ in resolution. I do not turn my laptop off, I only suspend it to RAM, when it is not used. Let's consider such scenario: laptop is docked at home. Xrandr shows available resolution for external screen properly. I turn off the external output (xrandr --output VGA1 --off), then I suspend it, undock and take to work, where I dock again to another docking port and wake it up. The problem is, that the laptop does not re-read the resolution configuration then. it shows resolutions from the monitor which I have at home, not at work. I think that after the machine wakes up, it gets no "display changed" message, which is pretty logical. ButThen The only way I can have the data "fixed" is to unplug the monitor physically and plug it back. And I dont like such solution, that's not what docking station is for. Can I somehow make xrandr refresh its readings? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: DPMS won't disable
Dnia 9 grudnia 2014 02:21:24 CET, Grant napisał(a): >I'm using this to disable DPMS but it isn't working: > >Section "Monitor" >Identifier "Monitor" >Option "DPMS" "false" >EndSection > >I can disable it manually with 'xset -dpms' just fine. I tried >disabling lightdm and xfce4 and using startx but DPMS is still enabled >in that case. What am I missing? Try: Option "DPMS" "no" instead of "false". -- Pozdrawiam. Łukasz Maśko Wysłane z aplikacji mobilnej ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Am I using the "ati" or "vesa" driver?
Dnia środa, 30 lipca 2014 15:58:22 YuGiOhJCJ Mailing-List pisze: > > [...] > > > > > So, I think that I am using the "vesa" Xorg driver for generic VESA > > > video > > > cards instead of the "ati" video driver. > > > > > > How to be sure about that? > > > > Have a look at Xorg logs, usually /var/log/Xorg.0.log. > > Yeah, but it seems to load both drivers (and other drivers too): > $ cat /var/log/Xorg.0.log | grep LoadModule > [...] > [ 1684.745] (II) LoadModule: "ati" > [ 1684.746] (II) LoadModule: "radeon" > [ 1684.748] (II) LoadModule: "vesa" > [ 1684.749] (II) LoadModule: "fbdev" > [...] > > I give you my full Xorg.0.log here: > http://pastebin.com/fsPBgt5P > > If you find an interesting line telling me what driver I am using please > highlight it for me. You're deffinitely using the vesa driver. The radeon driver is loaded, but then the vesa driver is initialized as first and it takes control over your card, so finally, according to line #1700, the radeon driver is unloaded: [ 1684.950] (II) UnloadModule: "radeon" I'd suggest, you should either remove the vesa driver from your system and try then. Writing a proper config file would also do the trick. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Am I using the "ati" or "vesa" driver?
Dnia środa, 30 lipca 2014 14:52:47 YuGiOhJCJ Mailing-List pisze: [...] > So, I think that I am using the "vesa" Xorg driver for generic VESA video > cards instead of the "ati" video driver. > > How to be sure about that? Have a look at Xorg logs, usually /var/log/Xorg.0.log. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Option Emulate3Buttons not working for my BT mouse
Dnia poniedziałek, 23 czerwca 2014 10:55:45 Peter Hutterer pisze: [...] > Is the mb emulation set in xinput list-props "MoGo Mouse BT"? is the > timeout too short for you? try increasing it with $ xinput list-props "MoGo Mouse BT" Device 'MoGo Mouse BT': Device Enabled (154): 1 Coordinate Transformation Matrix (156): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (287): 0 Device Accel Constant Deceleration (288): 1.00 Device Accel Adaptive Deceleration (289): 1.00 Device Accel Velocity Scaling (290):10.00 Device Product ID (275):2652, 8196 Device Node (276): "/dev/input/event13" Evdev Axis Inversion (291): 0, 0 Evdev Axes Swap (293): 0 Axis Labels (294): "Rel X" (164), "Rel Y" (165), "Rel Horiz Wheel" (284) Button Labels (295):"Button Left" (157), "Button Unknown" (278), "Button Right" (159), "Button Wheel Up" (160), "Button Wheel Down" (161), "Button Horiz Wheel Left" (162), "Button Horiz Wheel Right" (163) Evdev Scrolling Distance (296): 1, 1, 1 Evdev Middle Button Emulation (297):1 Evdev Middle Button Timeout (298): 50 Evdev Third Button Emulation (299): 0 Evdev Third Button Emulation Timeout (300): 1000 Evdev Third Button Emulation Button (301): 3 Evdev Third Button Emulation Threshold (302): 20 Evdev Wheel Emulation (303):0 Evdev Wheel Emulation Axes (304): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (305):10 Evdev Wheel Emulation Timeout (306):200 Evdev Wheel Emulation Button (307): 4 Evdev Drag Lock Buttons (308): 0 > xinput set-prop "MoGo Mouse BT" "Evdev Middle Button Timeout" 100 > (or whatever timeout is best) - does that fix it? Seems to work if I increase this value to 150-200. Although, it is not 100% reliable. But it's good that it works. Thanks. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Option Emulate3Buttons not working for my BT mouse
Dnia niedziela, 22 czerwca 2014 14:03:53 walt pisze: [...] > > Section "InputClass" > > Identifier "MoGo Mouse BT" > > Driver "evdev" > > Option "Buttons" "2" > > Option "Emulate3Buttons" "on" > > MatchProduct"MoGo" > > MatchIsPointer "On" > > MatchDevicePath "/dev/input/event*" > > > > EndSection > > Now that I think about it, I've never used the "Buttons" option and I'm not > sure why anyone would need it. Evdev should be able to get that information > from the mouse. I'd try removing that option. I had. It changed nothing. I expected it to reduce the number of buttons recognized by evdev, but it simply does nothing, as if it were not recognized (or considered) by evdev driver at all. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Option Emulate3Buttons not working for my BT mouse
Dnia sobota, 21 czerwca 2014 13:27:21 walt pisze: [...] > Okay, that's what I'd expect from a 2-button mouse. I suggest trying > > Option "EmulateWheelButton" "2" in your xorg.conf. > > That (I think) should allow you to scroll by holding down both buttons. > > Using button 1 might be more natural, but I suspect it would also break > click-and-drag. Thanks, I'll try. But I don't need scroll. I wish to have the middle button to be emulated by pressing both keys... Pasting is more desired than scrolling. Anyway, that's what I get now: [120355.111] (II) config/udev: Adding input device MoGo Mouse BT (/dev/input/event13) [120355.112] (**) MoGo Mouse BT: Applying InputClass "evdev pointer catchall" [120355.112] (**) MoGo Mouse BT: Applying InputClass "MoGo Mouse BT" [120355.112] (II) Using input driver 'evdev' for 'MoGo Mouse BT' [120355.112] (**) MoGo Mouse BT: always reports core events [120355.112] (**) evdev: MoGo Mouse BT: Device: "/dev/input/event13" [120355.112] (--) evdev: MoGo Mouse BT: Vendor 0xa5c Product 0x2004 [120355.112] (--) evdev: MoGo Mouse BT: Found 3 mouse buttons [120355.112] (--) evdev: MoGo Mouse BT: Found scroll wheel(s) [120355.112] (--) evdev: MoGo Mouse BT: Found relative axes [120355.112] (--) evdev: MoGo Mouse BT: Found x and y relative axes [120355.112] (--) evdev: MoGo Mouse BT: Found absolute axes [120355.112] (--) evdev: MoGo Mouse BT: Found absolute multitouch axes [120355.113] (II) evdev: MoGo Mouse BT: Forcing absolute x/y axes to exist. [120355.113] (II) evdev: MoGo Mouse BT: Configuring as mouse [120355.113] (II) evdev: MoGo Mouse BT: Adding scrollwheel support [120355.113] (**) Option "Emulate3Buttons" "on" [120355.113] (**) Option "EmulateWheelButton" "2" [120355.113] (**) evdev: MoGo Mouse BT: YAxisMapping: buttons 4 and 5 [120355.113] (**) evdev: MoGo Mouse BT: EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [120355.113] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1d.7/usb1/1-2/1-2.4/1-2.4:1.0/bluetooth/hci0/hci0:46/0005:0A5C:2004.0034/input/input125/event13" [120355.113] (II) XINPUT: Adding extended input device "MoGo Mouse BT" (type: MOUSE, id 15) [120355.113] (II) evdev: MoGo Mouse BT: initialized for relative axes. [120355.113] (WW) evdev: MoGo Mouse BT: ignoring absolute axes. [120355.113] (**) MoGo Mouse BT: (accel) keeping acceleration scheme 1 [120355.113] (**) MoGo Mouse BT: (accel) acceleration profile 0 [120355.113] (**) MoGo Mouse BT: (accel) acceleration factor: 2.000 [120355.113] (**) MoGo Mouse BT: (accel) acceleration threshold: 4 Emulation of the middle button (with 2 available) is still not working. It seems that the driver is simply not paying attention to Emulate3Buttons, although it can see it. So, becouse the emulated button #2 is not working, emulated scroll wheel is not working either. Is it possible, that the evdriver is simply neglecting the presence of Emulate3Buttons in a case, when it "detects" 3 buttons? But how, if the mouse has only 2? And why is it omitting the "Buttons" option? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Option Emulate3Buttons not working for my BT mouse
Dnia piątek, 20 czerwca 2014 14:52:19 walt pisze: [...] > To clarify: the mouse has *no* scrollwheel or trackball, and only *2* > physical buttons, right? Seems odd then that the logs talk about buttons 4 > and 5. That's exactly it. Only 2 physical buttons, but evdev recognizes it as 5 button mouse with a scroll wheel. I wish it had, but more buttons but no. > Have you tried xev to see what button numbers it reports? If I got it correctly - xev reports left button as button #1, right button as button #3. Pressing both buttons simultaneously generates just sequence of buttons 1 and 3 pressed one after another. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Option Emulate3Buttons not working for my BT mouse
Hello. I've recently bought a BT mouse for my laptop. I've paired it with my komputer and it works. More-less. It has only 2 physical buttons and I miss the middle button, therefore I wish to use the Emulate3Buttons option. But... it does not work. I've created the following config file: Section "InputClass" Identifier "MoGo Mouse BT" Driver "evdev" Option "Buttons" "2" Option "Emulate3Buttons" "on" MatchProduct"MoGo" MatchIsPointer "On" MatchDevicePath "/dev/input/event*" EndSection When I connect the mouse, Xorg responds like this: [ 66808.538] (II) config/udev: Adding input device MoGo Mouse BT (/dev/input/mouse3) [ 66808.538] (II) No input driver specified, ignoring this device. [ 66808.538] (II) This device may have been added with another device file. [ 66808.539] (II) config/udev: Adding input device MoGo Mouse BT (/dev/input/event13) [ 66808.539] (**) MoGo Mouse BT: Applying InputClass "evdev pointer catchall" [ 66808.539] (**) MoGo Mouse BT: Applying InputClass "MoGo Mouse BT" [ 66808.539] (II) Using input driver 'evdev' for 'MoGo Mouse BT' [ 66808.539] (**) MoGo Mouse BT: always reports core events [ 66808.539] (**) evdev: MoGo Mouse BT: Device: "/dev/input/event13" [ 66808.539] (--) evdev: MoGo Mouse BT: Vendor 0xa5c Product 0x2004 [ 66808.539] (--) evdev: MoGo Mouse BT: Found 3 mouse buttons [ 66808.539] (--) evdev: MoGo Mouse BT: Found scroll wheel(s) [ 66808.539] (--) evdev: MoGo Mouse BT: Found relative axes [ 66808.539] (--) evdev: MoGo Mouse BT: Found x and y relative axes [ 66808.539] (--) evdev: MoGo Mouse BT: Found absolute axes [ 66808.539] (--) evdev: MoGo Mouse BT: Found absolute multitouch axes [ 66808.539] (II) evdev: MoGo Mouse BT: Forcing absolute x/y axes to exist. [ 66808.539] (II) evdev: MoGo Mouse BT: Configuring as mouse [ 66808.540] (II) evdev: MoGo Mouse BT: Adding scrollwheel support [ 66808.540] (**) Option "Emulate3Buttons" "on" [ 66808.540] (**) evdev: MoGo Mouse BT: YAxisMapping: buttons 4 and 5 [ 66808.540] (**) evdev: MoGo Mouse BT: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 66808.540] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1d.7/usb1/1-2/1-2.4/1-2.4:1.0/bluetooth/hci0/hci0:46/0005:0A5C:2004.0024/input/input77/event13" [ 66808.540] (II) XINPUT: Adding extended input device "MoGo Mouse BT" (type: MOUSE, id 15) [ 66808.540] (II) evdev: MoGo Mouse BT: initialized for relative axes. [ 66808.540] (WW) evdev: MoGo Mouse BT: ignoring absolute axes. [ 66808.540] (**) MoGo Mouse BT: (accel) keeping acceleration scheme 1 [ 66808.540] (**) MoGo Mouse BT: (accel) acceleration profile 0 [ 66808.540] (**) MoGo Mouse BT: (accel) acceleration factor: 2.000 [ 66808.540] (**) MoGo Mouse BT: (accel) acceleration threshold: 4 It seems to see the Emulate3Buttons option, but it seems not to obey the Buttons option. The mouse has no scroll wheel, it has 2 physical buttons and the 3rd one must be emulated. But... it does not work. At the sime time, it works for instance for a DualPoint Stick, which I have. If it is important, I also often use an external, wired mouse, which has additional 3 buttos and a scroll wheel and it works correctly. I'm using KDE 4.13.2 right now, so quirks with gsettings don't work. I have libevdev 1.2.2 and xorg evdev driver 2.9.0. My xserver is 1.15.1. Can anyone help me solve this puzzle? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
[slightly off topic] Graphics card for X with multi-monitor support
Sorry for off-topic. A friend of mine has asked me recently the following question: which graphics card for a desktop machine to buy, such that: 1. It is not too expensive, let's say about 150-200 USD. 2. It is supported by Xorg under Linux (this is the target software architecture). 3. One can easily connect at least 4 monitors to it (FullHD resolution each) and create one big desktop out of it. 4. It supports xrandr on each output (the monitors are oriented in "portrait" mode). The 3rd point is most important. My friend has 2 cards with 2 monitors connected to each of them (4 monitors total) right now. He has all of them working, but instead of one single desktop, he has 2 separate ones (although working simultaneously - :0 and :1). It means, that each window can be maximized only using 2 monitors out of 4. He wants to have one big desktop, in which he can maximize a window so that it uses all 4 monitors. He has tried to obtain it with his current configuration, but without success. Any suggestions? It may be either ATI or NVidia card. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Problems exporting windows
Dnia niedziela, 17 listopada 2013 22:11:24 Steven Feil pisze: > I am having difficulty exporting windows between computers. I would > like to find a "how-to" like documentation so I can figure out what is > blocking windows from one computer from displaying on the other. The > main difficulty I am having in solving my problem is that I can not > find a Google-able error messages. When I try to export the display > of the program xv all I get is the message "xv: Can't open display". This is not a direct solution of your problem, but have you tried to use the X forwarding feature of ssh protocol? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: [ANNOUNCE] xf86-video-intel 2.99.904
Dnia czwartek, 10 października 2013 16:28:28 Chris Wilson pisze: > On Thu, Oct 10, 2013 at 04:27:20PM +0200, Łukasz Maśko wrote: > > Dnia środa, 9 października 2013 17:24:19 Chris Wilson pisze: > > > Snapshot 2.99.904 (2013-10-09) > > > == > > > There is one more feature planned to be completed for 3.0, so time for a > > > snapshot beforehand to push out the bug fixes from the last week. > > > > I don't know, if it is important, but I'm getting a segfault when I'm > > trying to run 2.99.904, while 2.99.903 runs without a problem. Xorg.log > > is attached. > Users! Preferred-mode strikes again, sorry about that. > > commit f0bd716425d1514b62565f9a65397cd1cb2ffb3a > Author: Chris Wilson > Date: Thu Oct 10 16:22:45 2013 +0100 > > sna: Sanitize output->crtc before falling back oto > xf86InitialConfiguration How should I understand that? Should I simply add Option "AccelMethod" "SNA" to my xorg.conf to make it work? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xf86-video-intel 2.99.904
Dnia środa, 9 października 2013 17:24:19 Chris Wilson pisze: > Snapshot 2.99.904 (2013-10-09) > == > There is one more feature planned to be completed for 3.0, so time for a > snapshot beforehand to push out the bug fixes from the last week. I don't know, if it is important, but I'm getting a segfault when I'm trying to run 2.99.904, while 2.99.903 runs without a problem. Xorg.log is attached. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" [ 120.489] X.Org X Server 1.14.3 Release Date: 2013-09-12 [ 120.489] X Protocol Version 11, Revision 0 [ 120.489] Build Operating System: PLD/Linux PLD/Team [ 120.489] Current Operating System: Linux laptok 3.10.15-1 #1 SMP Mon Oct 7 16:09:41 CEST 2013 i686 [ 120.489] Kernel command line: BOOT_IMAGE=test root=302 resume=/dev/hda7 5 [ 120.489] Build Date: 13 September 2013 08:29:35AM [ 120.489] [ 120.489] Current version of pixman: 0.30.2 [ 120.489]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 120.489] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 120.490] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 10 16:06:50 2013 [ 120.490] (==) Using config file: "/etc/X11/xorg.conf" [ 120.490] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 120.490] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 120.491] (**) Option "defaultserverlayout" "standard" [ 120.491] (**) ServerLayout "standard" [ 120.491] (**) |-->Screen "Screen" (0) [ 120.491] (**) | |-->Monitor "" [ 120.491] (**) | |-->Device "Card" [ 120.491] (==) No monitor specified for screen "Screen". Using a default monitor configuration. [ 120.491] (**) Option "DontZap" "off" [ 120.491] (==) Automatically adding devices [ 120.491] (==) Automatically enabling devices [ 120.491] (==) Automatically adding GPU devices [ 120.491] (**) FontPath set to: /usr/share/fonts/local, /usr/share/fonts/misc, /usr/share/fonts/TTF, /usr/share/fonts/OTF, /usr/share/fonts/Type1, /usr/share/fonts/100dpi, /usr/share/fonts/75dpi [ 120.491] (==) ModulePath set to "/usr/lib/xorg/modules" [ 120.491] (**) Extension "Composite" is enabled [ 120.491] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 120.491] (II) Loader magic: 0x8248620 [ 120.491] (II) Module ABI versions: [ 120.491]X.Org ANSI C Emulation: 0.4 [ 120.491]X.Org Video Driver: 14.1 [ 120.492]X.Org XInput driver : 19.1 [ 120.492]X.Org Server Extension : 7.0 [ 120.492] (II) xfree86: Adding drm device (/dev/dri/card0) [ 120.495] (--) PCI:*(0:0:2:0) 8086:27a2:1028:0201 rev 3, Mem @ 0xeff0/524288, 0xd000/268435456, 0xefec/262144, I/O @ 0xeff8/8 [ 120.495] (--) PCI: (0:0:2:1) 8086:27a6:1028:0201 rev 3, Mem @ 0xeff8/524288 [ 120.495] Initializing built-in extension Generic Event Extension [ 120.495] Initializing built-in extension SHAPE [ 120.495] Initializing built-in extension MIT-SHM [ 120.495] Initializing built-in extension XInputExtension [ 120.495] Initializing built-in extension XTEST [ 120.495] Initializing built-in extension BIG-REQUESTS [ 120.495] Initializing built-in extension SYNC [ 120.495] Initializing built-in extension XKEYBOARD [ 120.495] Initializing built-in extension XC-MISC [ 120.495] Initializing built-in extension XINERAMA [ 120.495] Initializing built-in extension XFIXES [ 120.495] Initializing built-in extension RENDER [ 120.495] Initializing built-in extension RANDR [ 120.495] Initializing built-in extension COMPOSITE [ 120.495] Initializing built-in extension DAMAGE [ 120.495] Initializing built-in extension MIT-SCREEN-SAVER [ 120.495] Initializing built-in extension DOUBLE-BUFFER [ 120.495] Initializing built-in extension RECORD [ 120.495] Initializing built-in extension DPMS [ 120.495] Initializing built-in extension X-Resource [ 120.495] Initializing built-in extension XVideo [ 120.495] Initializing built-in extension XVideo-MotionCompensation [ 120.495] Initializing built-in extension XFree86-VidModeExtension [ 120.495] Initializing built-in extension XFree86-DGA [ 120.495] Initializing built-in
Re: Strange artefacts around some objects in GTK application - is it the Intel driver to be blamed?
Dnia czwartek, 8 listopada 2012, Thomas Lübking napisał: > On Donnerstag, 8. November 2012 12:02:52 CEST, Łukasz Maśko wrote: > > But some time ago I've noticed some > > strange artefacts around menus or hint boxes (the ones that > > appear after you stop a mouse pointer on a button, for > > instance). I've made a screenshot, so you can observe it > > yourself: http://yen.ipipan.waw.pl/~ed/gtk.jpg > > It happens in applications which use GTK (here it is Iceweasel, > > but it's the same for instance in Chromium or Gimp). KDE > > applications are free of this error. > > > I wonder, who is to be blamed here: > There's been a bug report against kwin where it turned out to be the > QtCurve gtk+ style causes this (unlike the oxygen one), see > https://bugs.kde.org/show_bug.cgi?id=309477 I AM using oxygen-gtk theme and I have these problems. A guy using my distro said, that he has no such problems when using 64-bit packages (I'm using 32- bit packages). May this be a problem? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Strange artefacts around some objects in GTK application - is it the Intel driver to be blamed?
My laptop has an Intel 945GM graphics and it is working more-less correctly (I'm using kernel 3.5.7, Intel driver 2.20.12 and xserver 1.13.0). But some time ago I've noticed some strange artefacts around menus or hint boxes (the ones that appear after you stop a mouse pointer on a button, for instance). I've made a screenshot, so you can observe it yourself: http://yen.ipipan.waw.pl/~ed/gtk.jpg It happens in applications which use GTK (here it is Iceweasel, but it's the same for instance in Chromium or Gimp). KDE applications are free of this error. In the same time, I've noticed nothing like this on my workstation, which has an NVidia graphics, when using both proprietary NVidia driver or standard nv driver. The machines have exactly the same packages installed - excluding drivers, which are completly different. I wonder, who is to be blamed here: - gtk itself (although no such effets observed on NVidia card). - intel graphics driver. - anything else. I'm using PLD Linux Distribution, but I don't think it's important here. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia poniedziałek, 5 listopada 2012, Thomas Lübking napisał: [...] > Observation: > you're running 1600x1200@85Hz while basic Single Link DVI has it's > maximum at 1600x1200@60Hz > > To run higher resolutions or frequency, the entire chain has to support > reduced blanking capabilities and there's recently been a mail which > suggested this was broken in "older" versions of "something" (worked in > some recent ubuntu, but not debian) > > This would impact _everything_ but might be only notable in the > bright-on-black context of konsole. > > So you should either absolutely ensure that the entire HW chain (output, > cable, input) is Dual Link DVI (full pins, no gap the the plug) or try > the outcome of 1600x1200@60Hz (yes, 60Hz on crts suck) or try a vga > connection. > > xrandr --output DVI-I-1 --mode 1600x1200 --rate 60 So I've just checked it. And... nouveau is in fact NOT changing refresh rate AT ALL. I mean, it is not fisically changing anything. After I execute the above command, xrandr says, that the refresh rate has been changed (the '*' mark is moved to the 60Hz frequency. But my monitor, which has an ability to report its current refresh rate, still reports the same (91.2kHz, 85Hz) rates. So it seems, that --rate parameter does exactly NOTHING in the nouveau case. Isn't it strange? I can change resolutions, but I cannot change frequency... Still, since I was not able to check the above, no solution for my problem has been found. Any more ideas? Anyone? For now I'm forced to switch back to NVidia. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Blurry image with nouveau over VGA, ok with nvidia driver
Dnia wtorek, 6 listopada 2012, tino.keitel+x...@tikei.de napisał: > Hi, > > I used the nvidia binary drivers on GeForce 6150 LE graphics. They are > awfull (slow, corruption in Emacs, replace system libraries), but > nouveau didn't work at all. > > Now I tried 3.7-rc4 and nouveau seems to give an image at least. > However, the image is blurry. The computer doesn't have DVI out, so > I'm using VGA and a resolution of 1600x1200. This may be the culprit, > but the same setup worked fine with the binary driver. Are there any > options I could try? Your report is very similar to mine. I'm also using 1600x1200 resolution. My machine has DVI, but monitor does not. So I'm also using VGA connector. And I also have problems, but its font rendering in my case. What happens, if you switch to 1280x1024 or 1024x768 (if your monitor supports such resolution)? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia wtorek, 6 listopada 2012, Thomas Lübking napisał: > On Montag, 5. November 2012 23:42:21 CEST, Łukasz Maśko wrote: > > But in fact my monitor IS connected via a standard VGA > > connector. It simply has no DVI plug, only VGA. My graphics card > > has a single output connector and a splitter, which allows me to > > connect two monitors, both using VGA connector (I'm using only > > one). > > my VGA connector says "VGA-0" and the DVI one "DVI-I-1" > I suspect there's just a VGA adapter wired to the DVI link :-\ Probably. My machine is a Dell T5400 workstation, everything is possible. > > It would mean, that the only thing left for me is to use a > > proprietary NVidia driver. > > Or check a more recent version. You probably mentioned your xorg / > nouveau versions somewhere, but i deleted the mails :-) I'm using kernel 3.5.7, nouveau 1.0.3, xserver 1.13.0 and Mesa 9.0 (I don't know, what else may be important). -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia poniedziałek, 5 listopada 2012, Thomas Lübking napisał: [...] > Since there's also no relation to the compositor or the ARGB state of the > window, yet the problem is (is it?) restricted to konsole, i'm out of > ideas. I've taken a closer look and its not only console that looks bad. I think that observation, that after rescaling to 1280x1024 fonts are rendered poperly, means here something important. But I have no idea, what. > Observation: > you're running 1600x1200@85Hz while basic Single Link DVI has it's > maximum at 1600x1200@60Hz > > To run higher resolutions or frequency, the entire chain has to support > reduced blanking capabilities and there's recently been a mail which > suggested this was broken in "older" versions of "something" (worked in > some recent ubuntu, but not debian) > > This would impact _everything_ but might be only notable in the > bright-on-black context of konsole. > > So you should either absolutely ensure that the entire HW chain (output, > cable, input) is Dual Link DVI (full pins, no gap the the plug) or try > the outcome of 1600x1200@60Hz (yes, 60Hz on crts suck) or try a vga > connection. But in fact my monitor IS connected via a standard VGA connector. It simply has no DVI plug, only VGA. My graphics card has a single output connector and a splitter, which allows me to connect two monitors, both using VGA connector (I'm using only one). > xrandr --output DVI-I-1 --mode 1600x1200 --rate 60 > > If this is crisp (but flickers.. that's normal) there's your problem. I'll give it a try on Thursday and will let you know, how it behaves. > I'd nearly bet your right arm, that the nouveau driver version does > somehow fail on reduced blanking while the nvidia blob does not. It would mean, that the only thing left for me is to use a proprietary NVidia driver. Becouse if the binary driver does something and nouveau not, it means, that nouveau should be fixed/improved to obtain the same functionality (which is basic here). Otherwise it's kind of useless... Pitty... -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia środa, 31 października 2012, Thomas Lübking napisał: [...] > Back on topic: > --> Did you have a chance to check the ARGB/Compositing relation then? No relation. As I've mentioned in another post, I think it has something to do with font renderere, which works in 1280x1024 mode, while the screen is 1600x1200. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia czwartek, 1 listopada 2012, Henrik Pauli napisał: [...] > > Check "xrandr -q" for supported modes, outputs and current mode and > > use "xrandr --output DVI-I-1 --mode 1600x1200 --scale 1x1" to set it > > > > This blurring would however impact absolutely everything, every font > > in every window and every other content. > > --scale has nothing to do with the final scaling, you might be thinking > about --set "scaling mode" $mode, which is about how the HW should > behave with non-native resolutions. At least that's the case with LVDS > outputs, not sure if my DVI has such, I don't have such an output > available right this moment. $mode is as follows: > > • "Center" will not stretch at all and 1 px will be 1 px. > • "Full" will stretch the image to the full available space of the > display, with no regard for the aspect. > • "Full aspect" will stretch the image until one side is as big as the > display, aspect is retained as normal. > > The last two modes can show up very blurry or just plain odd, depending > on the smoothing done by the display. > > To list the current scaling mode, try xrandr --verbose Here it is (just a part): $ xrandr Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 8192 x 8192 DVI-I-1 connected 1600x1200+0+0 (0x64) normal (normal left inverted right x axis y axis) 352mm x 264mm Identifier: 0x61 Timestamp: 2558459 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004c2d2f0039315141 200c01036f241b5e2b0299a057499926 13484c803140455961598199a94f a959d140e145863d00c05100304040a0 13006008111e00fd0032a01e 6e1d000a20202020202000fc0053 796e634d61737465720a202000ff 00483252543830303832390a20200025 1600x1200 (0x64) 229.5MHz +HSync +VSync *current +preferred h: width 1600 start 1664 end 1856 total 2160 skew0 clock 106.2KHz v: height 1200 start 1201 end 1204 total 1250 clock 85.0Hz 1280x1024 (0x65) 157.5MHz +HSync +VSync +preferred h: width 1280 start 1344 end 1504 total 1728 skew0 clock 91.1KHz v: height 1024 start 1025 end 1028 total 1072 clock 85.0Hz [...] -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
So, I'm at my office and I'm ready to check everything which may help us
solve this problem. First, here is the output of xrandr:
$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 8192 x 8192
DVI-I-1 connected 1600x1200+0+0 (normal left inverted right x axis y axis)
352mm x 264mm
1600x1200 85.0*+ 75.0 70.0 65.0 60.0
1280x1024 85.0 + 75.0 60.0
[...]
DVI-I-2 disconnected (normal left inverted right x axis y axis)
So the card works in 1600x1200. BUT if I execute this:
xrandr --output DVI-I-1 --mode 1600x1200 --scale 0.8x0.8533, xrandr gives
this (just a part again):
$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
DVI-I-1 connected 1600x1200+0+0 (normal left inverted right x axis y axis)
352mm x 264mm
1600x1200 85.0*+ 75.0 70.0 65.0 60.0
1280x1024 85.0 + 75.0 60.0
[...]
and fonts are rendered in a much better (i.e. readable) way.
What may be even more important, if I just use 1280x1024 mode directly
(xrandr --output DVI-I-1 --mode 1280x1024), fonts are crisp and perfectly
rendered. This is why I suppose, that somehow internally, font rendering
either works with a wrong DPI, or wrong resolution. By the way, I'm using
internal font renderer of Xorg, not the external xfs.
> It's most likely about rendering ARGB visuals in the compositor.
> Fonts should be rendered in SW and make no difference. Since konsole is
> by default one of the few ARGB windows and hardly contains anything but
> fonts, it's what you see. But fonts are likely rendered in the client
> (so make no difference from anything else) and showing the picture will
> happen in a 24bit window.
>
> a) what if you suspend compositing (shift+alt+f12, given you're using
> kwin)
It is exactly the same.
> b) what if you use the xrender compositor ("kcmshell4
> kwincompositing", last tab)
Still the same, no difference, just some desktop effects are not available.
> c) what if you run konsole in RGB mode
> ("konsole --nofork --notransparency")
Same here, no difference.
> if all or any of this fixes it, you'll have to clarify whether this
> happens on kwin (GLX) or kwin_gles (guess what) and in the GLX case
> when using OpenGL 2 shaders or not (or that's irrelevant)
>
> If it was on nvidia only i'd btw. guess you've FXAA enabled, but the way
> it is, it actually will rather be a bug in either nouveau or kwin. We
> however got to figure "where".
It happens only with nouveau. With proprietary NVidia drivers there are no
problems.
I'm at office till 4pm (CET), I'm willing to answer all your questions and
check all suggestions for this topic. I hope we'll solve this puzzle
together.
--
Łukasz Maśko_o)
Lukasz.Masko(at)ipipan.waw.pl /\\
Registered Linux User #61028 _\_V
Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana"
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia środa, 31 października 2012, Thomas Lübking napisał: > On Mittwoch, 31. Oktober 2012 08:25:12 CEST, Łukasz Maśko wrote: [...] > > I think that the driver sets the resolution to 1280x1024 > > checking is better then "thinking" ;-) > > > (I wish I could change it to 1600x1200, which is the desired > > resolution). > > Check "xrandr -q" for supported modes, outputs and current mode and use > "xrandr --output DVI-I-1 --mode 1600x1200 --scale 1x1" to set it > > This blurring would however impact absolutely everything, every font in > every window and every other content. Output definitely is 1600x1200. Here are some lines from Xorg.0.log: [77.187] (II) NOUVEAU(0): Output DVI-I-1 connected [77.187] (II) NOUVEAU(0): Output DVI-I-2 disconnected [77.187] (II) NOUVEAU(0): Using user preference for initial modes [77.187] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1600x1200 [77.187] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. [77.187] (--) NOUVEAU(0): Virtual size is 1600x1200 (pitch 0) Also xrandr reports this mode as active. In one of the logs I saw something about setting virtual to 1280x1024, that's why I've mentioned the above. But now it is 1600x1200, co correct values. So probably it has nothing to do with such scaling. By the way, my monitor is a pretty good CRT capable of 1600x1200@85Hz (although not profesional one), not LCD, and it can adapt to any lower resolution in a much better way than LCD (almost no scaling noticable). -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia wtorek, 30 października 2012, Mark Wagner napisał: [...] > The driver probably thinks you're running an LCD, and is scaling the > image to what it assumes is the native resolution. Try setting the > driver to let the monitor perform scaling, or try changing your > display resolution slightly to try to find what the driver thinks is > the "native" resolution of the monitor. It may be possible. How do you do that? I mean, "setting the driver to let the monitor perform scaling". I think that the driver sets the resolution to 1280x1024 (I wish I could change it to 1600x1200, which is the desired resolution). How do you change this? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
Dnia poniedziałek, 29 października 2012, Thomas Lübking napisał: [...] > If it was on nvidia only i'd btw. guess you've FXAA enabled, but the way > it is, it actually will rather be a bug in either nouveau or kwin. We > however got to figure "where". Thanks for your reply. I suppose, i'll work on this machine next monday so I'll let you know as soon as I check the above. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Awfull rendering of fonts in KDE terminal with nouveau 1.0.3 drivers
I've given a try to latest nouveau driver on my Dell T5400 workstation with NVidia G86 (Quadro NVS 290). I'm using a Samsung SyncMaster 959NF CRT screen. Almost everything works well. Almost, becouse fonts in terminal are rendered in unacceptable way. But... it is kind of strange. To show you the difference I've made screenshots with my mobile phone camera for both NVidia and Nouveau drivers. Picture for nouveau can be downloaded from here: http://yen.ipipan.waw.pl/~ed/screenshot_nouveau.jpg Picture of the same terminal byt for NVidia can be downloaded from here: http://yen.ipipan.waw.pl/~ed/screenshot_nvidia.jpg At the first glance, one may say, that the first one is blurry becouse of hands shaking. But no, it is not. I've taken several pictures and chosen the best one. The fonts are REALLY blurry. If you have a closer look, you will see the difference on particular letters. So drawn text is very hard to read. Changing font size makes no difference, bigger letters are still blurried. Fonts under other applications like konqueror seem to look OK, at least everything is readable. Now, what is the most strange for me - the fonts are rendered in a wrong way when they are sent to the monitor! If I make a "software" screenshot with a KDE tool for making screenshots, both pictures look _exactly_ the same. You can tell no difference between them. Also kmag o xmag tools show perfectly rendered fonts. I don't understand it. Can it be fixed somehow? Right now I'm switching back to NVidia to save my eyes, though I'd prefer open drivers. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Segfault with nouveau, when acceleration is on.
5239.505] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb77c140c] [ 5239.505] (EE) 3: /lib/libc.so.6 (0x47e4c000+0x122310) [0x47f6e310] [ 5239.505] (EE) 4: /usr/lib/xorg/modules/libexa.so (0xb7643000+0x4af1) [0xb7647af1] [ 5239.505] (EE) 5: /usr/lib/xorg/modules/libexa.so (0xb7643000+0x5007) [0xb7648007] [ 5239.506] (EE) 6: /usr/lib/xorg/modules/libexa.so (0xb7643000+0x5251) [0xb7648251] [ 5239.506] (EE) 7: /usr/lib/xorg/modules/libexa.so (0xb7643000+0x7688) [0xb764a688] [ 5239.506] (EE) 8: /usr/lib/xorg/modules/libexa.so (0xb7643000+0x3fb2) [0xb7646fb2] [ 5239.506] (EE) 9: /usr/lib/xorg/modules/libexa.so (0xb7643000+0x10c95) [0xb7653c95] [ 5239.506] (EE) 10: /usr/bin/Xwrapper (miImageText8+0x96) [0x81b5e0e] [ 5239.506] (EE) 11: /usr/bin/Xwrapper (0x8047000+0x10b20a) [0x815220a] [ 5239.506] (EE) 12: /usr/bin/Xwrapper (doImageText+0x32e) [0x807b5f8] [ 5239.506] (EE) 13: /usr/bin/Xwrapper (ImageText+0x69) [0x807c97f] [ 5239.506] (EE) 14: /usr/bin/Xwrapper (0x8047000+0x2fa64) [0x8076a64] [ 5239.506] (EE) 15: /usr/bin/Xwrapper (0x8047000+0x32556) [0x8079556] [ 5239.506] (EE) 16: /usr/bin/Xwrapper (0x8047000+0x214c5) [0x80684c5] [ 5239.506] (EE) 17: /lib/libc.so.6 (__libc_start_main+0xf5) [0x47e656d1] [ 5239.506] (EE) 18: /usr/bin/Xwrapper (0x8047000+0x2186d) [0x806886d] [ 5239.506] (EE) [ 5239.506] (EE) Segmentation fault at address 0x0 [ 5239.506] Fatal server error: [ 5239.506] Caught signal 11 (Segmentation fault). Server aborting Hopefully, after such crash (which happens always), command prompt returns. I'm using a PLD distribution, kernel 3.5.7, nouveau driver 1.0.2, Mesa nouveau driver 9.0, xserver 1.13.0. I have no idea, where to look for a solution. Maybe you can give me a hint? Maybe it has something to do with the hardware and has the same origins as NVidia driver not working at all? But what should I check? -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xf86-video-intel 2.18.0
Has anyone noticed, that xrandr --scale stopped working properly with this driver version? I have a laptop with native resolution 1280x800. My TV supports only 1024x768 and 1360x768 (or higher), most of projectors I use support only 1024x768. So if I want to use the --same-as option (cloning) I'm forced to use --scale to adjust my secondary display to the primary. This is what I do: $ xrandr --output VGA1 --mode 1024x768 --scale 1.25x1.04 It worked prfectly up to 2.17.0. But if I use 2.18.0, it is not. In fact, after I execute the command above, my TV shows proper picture, but after a very short while (5 seconds?) the screen "looses" scaling and shows only 1024x768 from the upper-left part of my primary screen. I've downgraded back to 2.17.0 and it is OK now. My laptop has Intel 945GM Express Integrated Graphics Controller (rev 03). I'm using kernel 3.2.9 and xserver 1.11.4 (the driver for synaptics touchpad is not compiling wiht the latest 1.12.0, that's why I had to stay with 1.11.4). With my best regards. -- Łukasz Maśko_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
