[Question]LED status control over Caps Lock key
Dear list, Under normal circumstance, the LED lights up and down whenever pressing caps lock key only or shift + caps_lock. It is my intention to make it only light up the LED when shift + caps_lock is pressed. By doing some goggling, there are pages says that setting following two options in xorg.conf would make the magic. xorg.conf ... snip ... Option XkbTypes complete Option XkbCompat complete+japan ... snip ... However, in my case, it is not the shift + caps_lock but caps_lock only to light up the caps_lock LED. Is there a way to make the behaviour fit my wish? Any comment would be greatly appreciated. By the way, $ man 4 kbd does not mention about the above two options. Is there any document describes them? -- Sincerely, Jyo ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
nvidia driver in lenny
I´m trying to install nvidia driver in lenny my kernel is this one : 2.6.26-1-686 #lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) I´ve installed the package: #dpkg -i nvidia-kernel-2.6.26-1-686_173.14.09+3_i386.deb after that I´ve takent he following steps: #ln -sf /usr/bin/gcc-4.1 /usr/bin/cc #/etc/init.d/gdm stop #m-a prepare #sh NVIDIA-Linux-x86-180.29-pkg1.run --x-module-patch=/usr/lib/xorg/modules here is my /var/log/nvidia-installer.log : Using: nvidia-installer ncurses user interface WARNING: You do not appear to have an NVIDIA GPU supported by the 180.29 NVIDIA Linux graphics driver installed in this system. For further details, please see the appendix SUPPORTED NVIDIA GRAPHICS CHIPS in the README available on the Linux driver download page at http://www.nvidia.com. - License accepted. - Installing NVIDIA driver version 180.29. - No precompiled kernel interface was found to match your kernel; would you li ke the installer to attempt to download a kernel interface for your kernel f rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: No) - No precompiled kernel interface was found to match your kernel; this means that the installer will need to compile a new kernel interface. - Performing CC sanity check with CC=cc. - Performing CC version check with CC=cc. - Kernel source path: '/lib/modules/2.6.26-1-686/build' - Kernel output path: '/lib/modules/2.6.26-1-686/build' - Performing rivafb check. - Performing nvidiafb check. - Performing Xen check. - Cleaning kernel module build directory. executing: 'cd ./usr/src/nv; make clean'... - Building kernel module: executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.26-1-686/bu ild SYSOUT=/lib/modules/2.6.26-1-686/build'... NVIDIA: calling KBUILD... make CC=cc KBUILD_VERBOSE=1 -C /lib/modules/2.6.26-1-686/build SUBDIRS=/tmp /selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/nv modules test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \ echo; \ echo ERROR: Kernel configuration is invalid.; \ echo include/linux/autoconf.h or include/config/auto.conf are mis sing.; \ echo Run 'make oldconfig make prepare' on kernel src to fix it .; \ echo; \ /bin/false) include/linux/highmem.h: In function ‘zero_user_segments’: include/linux/highmem.h:134: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:134: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:134: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:134: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:137: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:137: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:137: warning: pointer of type ‘void *’ used in a rithmetic include/linux/highmem.h:137: warning: pointer of type ‘void *’ used in a rithmetic ... In file included from include/linux/list.h:6, from include/linux/preempt.h:11, from include/linux/spinlock.h:49, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:57, from include/linux/sched.h:54, from include/linux/utsname.h:35, from /tmp/selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/ nv/nv-linux.h:19, from /tmp/selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/ nv/nv-vm.c:14: include/linux/prefetch.h: In function ‘prefetch_range’: include/linux/prefetch.h:57: warning: pointer of type ‘void *’ used in a rithmetic In file included from include/asm/dma-mapping.h:9, from include/linux/dma-mapping.h:52, from include/asm-generic/pci-dma-compat.h:7, from include/asm/pci.h:92, from include/linux/pci.h:948, from /tmp/selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/ nv/nv-linux.h:86, from /tmp/selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/ nv/nv-vm.c:14: include/linux/scatterlist.h: In function ‘sg_virt’: include/linux/scatterlist.h:199: warning: pointer of type ‘void *’ used in arithmetic In file included from /tmp/selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/ nv/nv-linux.h:113, from /tmp/selfgz15411/NVIDIA-Linux-x86-180.29-pkg1/usr/src/ nv/nv-vm.c:14: include/linux/highmem.h: In function ‘zero_user_segments’: include/linux/highmem.h:134: warning: pointer of type ‘void *’ used in a rithmetic NVIDIA: left KBUILD. - done. - Kernel module compilation complete. ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel, or if a driver such as rivafb/nvidiafb is present and prevents the NVIDIA kernel module from obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU installed in this system is not supported by this NVIDIA Linux graphics driver release. Please see the log entries 'Kernel module
Re: nvidia driver in lenny
Érico Teixeira a écrit : I´m trying to install nvidia driver in lenny [...] #lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics You have an Intel graphics card... You probably want the Intel driver instead. Rémi ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
xclock's problem
Hello, I'm using opnSuSE 11.0, whose xorg is; xorg-x11-7.4-14.1 I'm using xlock with the settings in .xinitrc; xclock -digital -update 1 -fg gray100 -bg gray25 -fn -*-*-bold-r-normal--16-* -geometry 270x33+1642+0 -strftime %Y年%m月%d日(%a) %H時%M分%S秒 With this, xclock display the date; 2009年02月26日(木) 22時22分22秒 This is same as; 2009/02/09(Thu) 22:22:22 Yes, just fine! But, I've got one problem. After 23:59:59, xclock changes to 23:00:00 or 20:00:0, not 00:00:00. What's the matter, I wonder? If I move a mouse pointer on it, xclock's display changes 20:00:0:00 to 00:00:00. How can I solve this problem? Thanks in adavance. Regards, --- Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp Bill! You married with Computers. Not with Me! No..., with money. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keyboard events and console switching
On Jan 23, 09 10:27:12 +1100, Daniel Stone wrote: On Thu, Jan 22, 2009 at 05:36:52PM +0100, Matthias Hopf wrote: On Jan 22, 09 16:55:08 +0100, Helge Bahmann wrote: Things get even more unfriendly if console switching is initiated by chvt from a background service (don't ask). I propose to change the current logic for releasing keys on VT switch -- release them before switching away from the server, instead of after switching back. Would a patch like the attached one be acceptable? I finally got around to verify this patch against our bugs. Unfortunately, no change in behavior. I had to backport the patch, though, and it wasn't exactly trivial, so there might have been errors. We have several bugs open for openSUSE because of this behavior - so I'm all for a change. I don't know the inner workings of this area in X, so I can't claim to understand the patch completely, but I will give it a try. So if it works, I really suggest taking it. It should already work: please file a bug and assign it to me, and I'll take care of it ASAP. I requested a bug to be opened upstream - I will ping you when this has been done. Thanks in advance, Daniel! Matthias -- Matthias Hopf mh...@suse.de ____ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ m...@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R D www.mshopf.de ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
correct location of evdev?
Hi, I'm keen on mpx. I've sucessfully compiled xorg git sources now. There hasn't been any big trouble, awesome! However when starting xorgserver the server fails: (EE) XKB: Couldn't open rules file /nix/store/smpg6lqc9irva4g1d918mzfwsjc925gi-xkeyboard-config-1.2/etc/X11/xkb/rules/evdev I've found an evdev file: /nix/store/smpg6lqc9irva4g1d918mzfwsjc925gi-xkeyboard-config-1.2/etc/X11/xkb/keycodes/evdev So can you tell me what's wrong here or where to lookup the information about how to tell xkb where to find the correct evdev file? Sincerly Marc Weber ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Why do I need mouse acceleration to move windows and click buttons?
Hello, Why is it impossible to permanently disable Mouse acceleration? I run xorg with KDE, Gnome and fvwm1... and use xset to disable it but the Mouse acceleration gets enabled again and again by some process... Not just on my machine... This turns Linux into a lousy choice for competetive gaming. Do I really have to compile xorg myself to make sure mouse acceleration is disabled and STAYS disabled? Why do I need Mouse acceleration to move windows and click buttons anyways? I would really like to have an option in xorg.conf that would disable this permanently(!)... Thanks, Dirk ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
On Thu, 2009-02-26 at 18:58 +0100, Dirk wrote: People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. Sorry for not being bright enough for you, but I do enjoy acceleration. Xav ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
Well, then you haven't had it re-enabling itself over and over again to interfere with your games, yet. Xavier Bestel wrote: On Thu, 2009-02-26 at 18:58 +0100, Dirk wrote: People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. Sorry for not being bright enough for you, but I do enjoy acceleration. Xav ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: compiz and xorg-server 1.6.0
On Thu, Feb 26, 2009 at 01:38:25 +, Colin Guthrie wrote: 'Twas brillig, and Colin Guthrie at 23/02/09 09:38 did gyre and gimble: In the end the fix I found was to revert: http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branchid=444127f9f408d2f517fdfab0092bd67b29073373 Before this, compiz would start but give a white screen on the cube face. More intelligent scripts would probably stop it starting in the first place. Sadly it seems the above was missed in the 1.6.0 release. Perhaps this commit can be looked at for 1.6.1? Open a bugzilla and mark it as a blocker for 1.6.1. Otherwise it doesn't exist... Cheers, Julien ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
On Thursday 26 February 2009 18:13:01 Dirk wrote: Well, then you haven't had it re-enabling itself over and over again to interfere with your games, yet. Xavier Bestel wrote: On Thu, 2009-02-26 at 18:58 +0100, Dirk wrote: People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. Sorry for not being bright enough for you, but I do enjoy acceleration. Xav a) you probably need to disable the acceleration in whatever preferences utility your window manager / desktop environment provide b) guys, there *are* cases where a hi-res mouse pretty much obviates pointer acceleration and mocking someone for wanting to turn it off is ... puerile. In fact, what's probably needed is the ability to *decelerate* the thing when you want to position something accurately ... :) ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: compiz and xorg-server 1.6.0
On Thu, 2009-02-26 at 18:38 +0100, Julien Cristau wrote: On Thu, Feb 26, 2009 at 01:38:25 +, Colin Guthrie wrote: 'Twas brillig, and Colin Guthrie at 23/02/09 09:38 did gyre and gimble: In the end the fix I found was to revert: http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branchid=444127f9f408d2f517fdfab0092bd67b29073373 Before this, compiz would start but give a white screen on the cube face. More intelligent scripts would probably stop it starting in the first place. Sadly it seems the above was missed in the 1.6.0 release. Perhaps this commit can be looked at for 1.6.1? Open a bugzilla and mark it as a blocker for 1.6.1. Otherwise it doesn't exist... The DRI1 GLX_EXT_texture_from_pixmap regression caused by the above commit was fixed for 1.6 final in commit e96921ca954ff0d3de8a69cea085aac2d43b0a2e . -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: compiz and xorg-server 1.6.0
'Twas brillig, and Michel Dänzer at 26/02/09 18:05 did gyre and gimble: On Thu, 2009-02-26 at 18:38 +0100, Julien Cristau wrote: On Thu, Feb 26, 2009 at 01:38:25 +, Colin Guthrie wrote: 'Twas brillig, and Colin Guthrie at 23/02/09 09:38 did gyre and gimble: In the end the fix I found was to revert: http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branchid=444127f9f408d2f517fdfab0092bd67b29073373 Before this, compiz would start but give a white screen on the cube face. More intelligent scripts would probably stop it starting in the first place. Sadly it seems the above was missed in the 1.6.0 release. Perhaps this commit can be looked at for 1.6.1? Open a bugzilla and mark it as a blocker for 1.6.1. Otherwise it doesn't exist... The DRI1 GLX_EXT_texture_from_pixmap regression caused by the above commit was fixed for 1.6 final in commit e96921ca954ff0d3de8a69cea085aac2d43b0a2e . Yup, so Ander just pointed out to me! Sorry, I should have checked properly :) The fix didn't jump out at me in the shortlog so it's 100% my fault for the noise :s Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
Dirk wrote: The bottom sticker of my mouse says 2000 DPI... so I want to move the pointer 2000 pixels when i move the mouse an inch... NO MATTER HOW FAST I MOVE THE MOUSE. These are device pixels, not screen pixels. I really hope you didn't need me to explain this. Well... the thing I tried to explain is that I (and other people) don't want to /have/ to give a f***... 1) I plug in 2000 dpi mouse 2) I move mouse 1 inch horizontally and/or vertically 3) pointer moves 2000 pixels horizontally and/or vertically NO MATTER HOW FAST I MOVE THE MOUSE that really is all that one cares about when he wants to use Linux for gaming. PRECISION! Not useless Desktop features that interfere and make one seriously freak out during an important match. You could completely remove mouse acceleration from the codebase and increase the quality of Linux as a gaming system. People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. I know Windows has mouse acceleration too... but just because they call it a feature it shouldn't be part of a Linux Desktop and enable itself, randomly, over and over again. Right now I run a script that calls xset 30 times a minute with sleeps as a cronjob to make sure it stays disabled. Before, I even sent my mouse back to the manufacturer because I thought it was broken before I realized it was a problem with Linux so I guess I /am/ a little annoyed. Not as much as i (e.g.) was before i uninstalled HAL to get control over my Linux back. But still... I'll check out http://www.x.org/wiki/Development/Documentation/PointerAcceleration Thanks. You wrote up this entire flame before reading the manual? http://xkcd.com/293 comes to mind. Additionally, acceleration's presence can always be made negligible by changing the rate of acceleration. (Ah, the joys of calculus.) It's definitely an enhancement, not a feature. ~ C. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
touchscreen settings
http://dpaste.com/1931/ xorg finds and uses the touchscreen - good. I need to set min/Max X/Y values - I am lost on how to do that. the #ed out parts either have 0 effect or disable it - mouse doesn't move when I touch. So how do I configure whatever driver xorg is currently using? Carl K ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
Corbin Simpson wrote: Dirk wrote: The bottom sticker of my mouse says 2000 DPI... so I want to move the pointer 2000 pixels when i move the mouse an inch... NO MATTER HOW FAST I MOVE THE MOUSE. These are device pixels, not screen pixels. I really hope you didn't need me to explain this. Well... the thing I tried to explain is that I (and other people) don't want to /have/ to give a f***... 1) I plug in 2000 dpi mouse 2) I move mouse 1 inch horizontally and/or vertically 3) pointer moves 2000 pixels horizontally and/or vertically NO MATTER HOW FAST I MOVE THE MOUSE that really is all that one cares about when he wants to use Linux for gaming. PRECISION! Not useless Desktop features that interfere and make one seriously freak out during an important match. You could completely remove mouse acceleration from the codebase and increase the quality of Linux as a gaming system. People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. I know Windows has mouse acceleration too... but just because they call it a feature it shouldn't be part of a Linux Desktop and enable itself, randomly, over and over again. Right now I run a script that calls xset 30 times a minute with sleeps as a cronjob to make sure it stays disabled. Before, I even sent my mouse back to the manufacturer because I thought it was broken before I realized it was a problem with Linux so I guess I /am/ a little annoyed. Not as much as i (e.g.) was before i uninstalled HAL to get control over my Linux back. But still... I'll check out http://www.x.org/wiki/Development/Documentation/PointerAcceleration Thanks. You wrote up this entire flame before reading the manual? http://xkcd.com/293 comes to mind. Additionally, acceleration's presence can always be made negligible by changing the rate of acceleration. (Ah, the joys of calculus.) It's definitely an enhancement, not a feature. ~ C. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg Well I had read the xset manual but it kept re-enabling itself. I didn't know I had to read /many/ manuals to permanently disable mouse acceleration in Linux... but then again I thought the nineties were over... ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
On Thu, Feb 26, 2009 at 06:58:58PM +0100, Dirk wrote: Right now I run a script that calls xset 30 times a minute with sleeps as a cronjob to make sure it stays disabled. Why not jsut disable mouse accel in desktop environment preferences to not have gnome-settings-daemon¹ reseting it? ¹ or equivalent daemon of other DEs -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. pgpvejuwP3oJX.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
On Thu, Feb 26, 2009 at 12:58 PM, Dirk noi...@gmx.net wrote: Well... the thing I tried to explain is that I (and other people) don't want to /have/ to give a f***... 1) I plug in 2000 dpi mouse 2) I move mouse 1 inch horizontally and/or vertically 3) pointer moves 2000 pixels horizontally and/or vertically NO MATTER HOW FAST I MOVE THE MOUSE that really is all that one cares about when he wants to use Linux for gaming. PRECISION! Not useless Desktop features that interfere and make one seriously freak out during an important match. I think you really hit the nail on the head here: when he wants to use Linux for gaming. I think it's great that you use Linux as a gamer but you must realize that you are a minuscule minority. Just because you might need your mouse to move exactly 2.3442 pixels per millimeter doesn't mean that the rest of the world does as well. You could completely remove mouse acceleration from the codebase and increase the quality of Linux as a gaming system. We could and it might even improve the quality of Linux as a gaming system but the overall experience for most users would suffer tremendously. Pointer acceleration is a crucial part of the input system, especially as screen sizes increase. People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. That's just not true. Try using a laptop touchpad or pointing stick with infinite acceleration. You'll quickly give up in frustration. I even find that a standard mouse is unusable without acceleration. It's simply not possible to get both fine control and move across the screen at a reasonable rate. I know Windows has mouse acceleration too... but just because they call it a feature it shouldn't be part of a Linux Desktop and enable itself, randomly, over and over again. Exactly, the problem you are experiencing is not that we implement pointer acceleration; it's that it is repeatedly enabled against your wishes. Perhaps you should investigate why. Right now I run a script that calls xset 30 times a minute with sleeps as a cronjob to make sure it stays disabled. Before, I even sent my mouse back to the manufacturer because I thought it was broken before I realized it was a problem with Linux so I guess I /am/ a little annoyed. Not as much as i (e.g.) was before i uninstalled HAL to get control over my Linux back. But still... If you have a problem with HAL, report a bug. Uninstalling isn't the answer. It is an increasingly common dependency on the desktop and for good reason. I'll check out http://www.x.org/wiki/Development/Documentation/PointerAcceleration Thanks. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: correct location of evdev?
You need a newer xkeyboard-config release that has the evdev rules. It's available in xkeyboard-config-1.4. Thanks. I just have missed that one while updating. The startup log looks like this now: (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Fatal server error: Failed to activate core devices. I'm lucky cause this recent patch seems to replace a core dump by the nice error message. http://archive.netbsd.se/?ml=xorga=2009-02t=9753387 Any suggestions where to start to find the cause? Can a messy xorg.conf cause this message? Sincerly Marc Weber ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: touchscreen settings
Carl Karsten wrote: http://dpaste.com/1931/ xorg finds and uses the touchscreen - good. I need to set min/Max X/Y values - I am lost on how to do that. the #ed out parts either have 0 effect or disable it - mouse doesn't move when I touch. #Option MinX 4100 #Option MaxX 0 #Option MinY 0 #Option MaxY 4100 I don't know the elo or how it plays with /dev/input/mice, but I'd say if you get max/min-X in the right order (min max), chances are it will work. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
Ben Gamari wrote: On Thu, Feb 26, 2009 at 12:58 PM, Dirk noi...@gmx.net wrote: Well... the thing I tried to explain is that I (and other people) don't want to /have/ to give a f***... 1) I plug in 2000 dpi mouse 2) I move mouse 1 inch horizontally and/or vertically 3) pointer moves 2000 pixels horizontally and/or vertically NO MATTER HOW FAST I MOVE THE MOUSE that really is all that one cares about when he wants to use Linux for gaming. PRECISION! Not useless Desktop features that interfere and make one seriously freak out during an important match. I think you really hit the nail on the head here: when he wants to use Linux for gaming. I think it's great that you use Linux as a gamer but you must realize that you are a minuscule minority. Just because you might need your mouse to move exactly 2.3442 pixels per millimeter doesn't mean that the rest of the world does as well. And that's it? You could completely remove mouse acceleration from the codebase and increase the quality of Linux as a gaming system. We could and it might even improve the quality of Linux as a gaming system but the overall experience for most users would suffer tremendously. Pointer acceleration is a crucial part of the input system, especially as screen sizes increase. People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. That's just not true. Try using a laptop touchpad or pointing stick with infinite acceleration. You'll quickly give up in frustration. I even find that a standard mouse is unusable without acceleration. It's simply not possible to get both fine control and move across the screen at a reasonable rate. I know Windows has mouse acceleration too... but just because they call it a feature it shouldn't be part of a Linux Desktop and enable itself, randomly, over and over again. Exactly, the problem you are experiencing is not that we implement pointer acceleration; it's that it is repeatedly enabled against your wishes. Perhaps you should investigate why. I did... I can't find the reason why it keeps getting enabled again. End of story. Right now I run a script that calls xset 30 times a minute with sleeps as a cronjob to make sure it stays disabled. Before, I even sent my mouse back to the manufacturer because I thought it was broken before I realized it was a problem with Linux so I guess I /am/ a little annoyed. Not as much as i (e.g.) was before i uninstalled HAL to get control over my Linux back. But still... If you have a problem with HAL, report a bug. Uninstalling isn't the answer. It is an increasingly common dependency on the desktop and for good reason. I don't think I'll make them stop developing HAL. Because that would be the only thinkable solution for my problem with it and it's tendencies to steal the sovereignty over the operating system from the user. Sovereignty which made me once switch to Linux. HAL did cost me quite a few CD-R before I realized to make it stop trying to mounting the media while I was burning by de-installing it. That should be all I have to say about it. As long as I can do what I want without HAL interfering, Linux remains my favourite option. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: correct location of evdev?
On Thu, Feb 26, 2009 at 11:22 AM, Marc Weber marco-owe...@gmx.de wrote: You need a newer xkeyboard-config release that has the evdev rules. It's available in xkeyboard-config-1.4. Thanks. I just have missed that one while updating. The startup log looks like this now: (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. If I had to guess, I'd say that the xserver is using the wrong location for xkbcomp. Typically it will try to use $bindir/xkbcomp. Is that the first error? Can you post the whole log? -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and click buttons?
Dirk wrote: I was referring to reading /many/ manuals as a relic of the nineties. Oh, I got that, I just used it as a starter :) I'll try this on another machine as soon as it is in debian/unstable (if not already)... It would be great it this works and can't be overriden by anything. If you set the none scheme, no acceleration will happen as long as the device stays plugged. (you can't switch schemes live, only profiles). For gaming, you might want to check out adaptive deceleration. Though then you'd first need to kill whatever tweaks your acceleration. I know of no such bug in xorg. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: 3D slowness after suspend/resume cycle
There was actually a bug that was filed quite recently about a similar issue: http://bugzilla.kernel.org/show_bug.cgi?id=12769. Unfortunately, there hasn't been any progress yet. Good luck, - Ben On Tue, Feb 24, 2009 at 8:54 AM, Kalman KHIRALY khiraly...@gmx.net wrote: Dear list, I have a laptop (Toshiba L300-19J) with an intel 4500MHD video card. I use ubuntu 9.04-alpha5 but upgraded the kernel from 2.6.28 to 2.6.29-rc5. With this update I have at least double 3D performance, compiz works without glitch, and Enemy Terrority I have double fps (from 9-14fps (2.6.28) to 19-30fps (2.6.29)). My problem, that after a suspend/resume cycle the 3D slow down, and compiz works as in 2.6.28 kernel (it stops when switching workspace or using the Expose effect) I suspended with the following command: echo -n mem/sys/power/state My intel driver version is: 2:2.6.1-1ubuntu1 My logs after a suspend: The /var/log/Xorg.log: http://pastebin.com/f4140cc09 The dmesg output: http://pastebin.com/f5b30ac6b The /proc/cpuinfo: http://pastebin.com/f6822b085 The lspci -vvvnnnxxx output: http://pastebin.com/f7eb8bd83 The /var/log/kern.log output: http://khiraly.googlepages.com/kern.log.gz The dpkg -l output: http://pastebin.com/f5497dfd4 The uname -a : Linux lamagep 2.6.29-020629rc5-generic #020629rc5 SMP Sun Feb 15 18:53:03 UTC 2009 i686 GNU/Linux Do you have any idea what can it cause? Best regards, Khiraly ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Not able to start X as normal user
Hi I am getting following error when starting X as normal user : Build Operating System: Linux 2.6.27.10 i686 Current Operating System: Linux host.webofunni.com 2.6.27.10 #1 SMP PREEMPT Wed Dec 24 21:37:14 CET 2008 i686 (WW) xf86ReadBIOS: Failed to open /dev/mem (Operation not permitted) (WW) xf86OpenConsole: chown /dev/tty7 failed: Operation not permitted (WW) xf86OpenConsole: chown /dev/tty0 failed: Operation not permitted xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) I am able to start X as root and using xfce as desktop interface. Please help. -- - With regards, Unnikrishnan.A A candle loses nothing by lighting another candle ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Not able to start X as normal user
On 26 Feb 2009, at 23:51, unni krishnan wrote: I am able to start X as root and using xfce as desktop interface. Please help. Are you running with selinux enabled? -- Torgeir Veimo torg...@pobox.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Not able to start X as normal user
On Thu, Feb 26, 2009 at 2:51 PM, unni krishnan unnikrishna...@gmail.com wrote: Hi I am getting following error when starting X as normal user : Build Operating System: Linux 2.6.27.10 i686 Current Operating System: Linux host.webofunni.com 2.6.27.10 #1 SMP PREEMPT Wed Dec 24 21:37:14 CET 2008 i686 (WW) xf86ReadBIOS: Failed to open /dev/mem (Operation not permitted) (WW) xf86OpenConsole: chown /dev/tty7 failed: Operation not permitted (WW) xf86OpenConsole: chown /dev/tty0 failed: Operation not permitted xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) I am able to start X as root and using xfce as desktop interface. Please help. Is Xorg setuid to root? sudo chown root $prefix/Xorg sudo chmod u+s $prefix/Xorg -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xf86-input-synaptics 1.0.99.1
First snapshot for synaptics 1.1 Most exciting change: synclient uses device properties now. SHM is still available, but you have to specify -s to use it, and of course enable it through Option SHMConfig on. Please give this one a test, I expect to release 1.1 on Monday. Cheers, Peter Ben Gamari (1): Add comma after version number in configure.ac Marcel Dejean (2): two-finger emulation through fingerWidth change magic numbers to fractions Peter Hutterer (7): Remove synSetFloatOption, use xf86SetRealOption instead. Remove commented-out sections from configure.ac. synclient: clean up a bit, namespace shm functions. synclient: split shm_set_value into a parse_cmd. synclient: add support for device properties. Remove randr requirement from configure.ac Bump to 1.0.99.1 git tag: xf86-input-synaptics-1.0.99.1 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.0.99.1.tar.bz2 MD5: eaac925946c5f7bbf379b6b63dd7e8d7 xf86-input-synaptics-1.0.99.1.tar.bz2 SHA1: 2e075d2f9c89304ad11ecf87bf6835e5cc38eafb xf86-input-synaptics-1.0.99.1.tar.bz2 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.0.99.1.tar.gz MD5: 88338c9928d7df97cca7dcbb01f4af96 xf86-input-synaptics-1.0.99.1.tar.gz SHA1: 7401b276ba386f0ee757433e526c61eb87536b5d xf86-input-synaptics-1.0.99.1.tar.gz pgpKHChrGTSui.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [EDIT] Why do I need mouse acceleration to move windows and?click buttons?
On Thu, Feb 26, 2009 at 05:56:33PM +, Bill Crawford wrote: On Thursday 26 February 2009 18:13:01 Dirk wrote: Well, then you haven't had it re-enabling itself over and over again to interfere with your games, yet. Xavier Bestel wrote: On Thu, 2009-02-26 at 18:58 +0100, Dirk wrote: People who believe they need an accelerated pointer to click buttons or move windows are not bright enough to realize the absence of acceleration anyways. Sorry for not being bright enough for you, but I do enjoy acceleration. Xav a) you probably need to disable the acceleration in whatever preferences utility your window manager / desktop environment provide b) guys, there *are* cases where a hi-res mouse pretty much obviates pointer acceleration and mocking someone for wanting to turn it off is ... puerile. In fact, what's probably needed is the ability to *decelerate* the thing when you want to position something accurately ... :) see AdaptiveDeceleration (or ConstantDeceleration), added in server 1.6 http://wiki.x.org/wiki/Development/Documentation/PointerAcceleration Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xf86-input-hyperpen 1.3.0
hyperpen 1.3.0, fixes build for server 1.6 Note that the only fix this driver has ever seen dates back to 12/2007. If you are using this driver, please make sure we are aware of it by contacting me or xorg-de...@lists.freedesktop.org. Cheers, Peter Alan Coopersmith (1): Add README with pointers to mailing list, bugzilla git repos Peter Hutterer (3): Check for XINPUT ABI 3. Remove XFREE86_V4 cruft. hyperpen 1.3.0 git tag: xf86-input-hyperpen-1.3.0 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-hyperpen-1.3.0.tar.bz2 MD5: c50d0da3206d18d9d94f720e3688eca5 xf86-input-hyperpen-1.3.0.tar.bz2 SHA1: c508f7d713d9127b6ad906f347c4760825a612e5 xf86-input-hyperpen-1.3.0.tar.bz2 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-hyperpen-1.3.0.tar.gz MD5: 60004453cc65159be6ae8557a029b4fc xf86-input-hyperpen-1.3.0.tar.gz SHA1: 5a67db0e6887d9743ea0d9fd9e2dc92090f7fa3e xf86-input-hyperpen-1.3.0.tar.gz pgpiLJkTVr2ep.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
X crash on multi screen set-up
Thought I'd submit to the mailinglist before filing a bug report. System: Fedora 10 x86_64. 3 * 1680x1050 displays. 2.6.27.12-170.2.5.fc10.x86_64 #1 SMP. nvidia nvs 440 graphics card, has two GPUs and 2x2 DVI connections. What happens?: Reoccurring crash, involves mouse click triggering some sort of event which makes further mouse clicks unavailable. Can still move mouse cursor, but as mentioned after the event no more clicks are registered. Short time later X crashes. Keyboard can be used throughout, just mouse is affected before crash. Notes: Never happened with Twinview on dual screen set-up. Seems to happen only with Xinerama. -Is it true that with a 3 screen set-up you can only use separate X screens? Xorg.log looks error free. Files: xorg.conf config - http://pastebin.com/m3b98d45b Xorg.0.log.old - http://pastebin.com/mc4f715f /var/log/message: Feb 27 01:34:26 localhost kernel: Xorg[9274]: segfault at 4 ip 00509371 sp 7fffe9aa0390 error 4 in Xorg[40+1aa000] Hope this information helps. Thanks, -Ben ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xclock's problem
Masaru Nomiya wrote: I'm using opnSuSE 11.0, whose xorg is; xorg-x11-7.4-14.1 I'm using xlock with the settings in .xinitrc; xclock -digital -update 1 -fg gray100 -bg gray25 -fn -*-*-bold-r-normal--16-* -geometry 270x33+1642+0 -strftime %Y年%m月%d日(%a) %H時%M分%S秒 I don't know if it's related to your problem, but you should probably be using e.g.: -xrm *fontSet: -*-*-bold-r-normal--16-* instead of -fn. Also, try using the -norender option. -- Glynn Clements gl...@gclements.plus.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xf86-input-synaptics 1.0.99.2
Brown paperbag release. Fix two build errors on server 1.6 systems. Peter Hutterer (3): synclient: Fix build errors - BOOL isn't always available. synclient: define XATOM_FLOAT if missing from xserver-properties. Bump to 1.0.99.2 git tag: xf86-input-synaptics-1.0.99.2 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.0.99.2.tar.bz2 MD5: baac9f27665b91958fb5fca270591316 xf86-input-synaptics-1.0.99.2.tar.bz2 SHA1: 48abf6c8cdf2978a66d4347d2135a6aa00d71bd0 xf86-input-synaptics-1.0.99.2.tar.bz2 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.0.99.2.tar.gz MD5: 7834ef7e44d5d0f649368b3bcae2d557 xf86-input-synaptics-1.0.99.2.tar.gz SHA1: d5d1003f609e4f08cac3decd5425b26a6ab43ad8 xf86-input-synaptics-1.0.99.2.tar.gz pgp1LFBNh0Wrr.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Not able to start X as normal user
Dan, setuid was not set. I have set that and X is working now. bash-3.2$ ls -l /usr/bin/Xorg -rwsrwxrwx 1 root root 1563180 Feb 19 15:31 /usr/bin/Xorg bash-3.2$ Thanks for the solution :-) -- - With regards, Unnikrishnan.A A candle loses nothing by lighting another candle On Fri, Feb 27, 2009 at 4:43 AM, Dan Nicholson dbn.li...@gmail.com wrote: On Thu, Feb 26, 2009 at 2:51 PM, unni krishnan unnikrishna...@gmail.com wrote: Hi I am getting following error when starting X as normal user : Build Operating System: Linux 2.6.27.10 i686 Current Operating System: Linux host.webofunni.com 2.6.27.10 #1 SMP PREEMPT Wed Dec 24 21:37:14 CET 2008 i686 (WW) xf86ReadBIOS: Failed to open /dev/mem (Operation not permitted) (WW) xf86OpenConsole: chown /dev/tty7 failed: Operation not permitted (WW) xf86OpenConsole: chown /dev/tty0 failed: Operation not permitted xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) I am able to start X as root and using xfce as desktop interface. Please help. Is Xorg setuid to root? sudo chown root $prefix/Xorg sudo chmod u+s $prefix/Xorg -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
