Re: how exactly does X11 work with virtual terminals?
Awesome. That is exactly what I needed. Thanks! On Mon, Dec 19, 2011 at 6:01 PM, Alan Coopersmith alan.coopersm...@oracle.com wrote: On 12/19/11 14:20, James Strother wrote: Quite honestly, I have only a basic understanding for what the virtual terminals are and how they work, so I am baffled as to how I would resolve this issue. Does Xorg really need a virtual terminal, or can I start it without one? Is there another way to sort this out? Sounds like you need the flag that was originally added for the multiseat support in Xorg: -sharevts Share virtual terminals with another X server, if supported by the OS. Google finds pages such as https://help.ubuntu.com/community/MultiseatX that should have more information. -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Looking for **PAID** help with calling XSendEvent correctly
On Thu, Dec 22, 2011 at 9:20 AM, Aryeh Friedman
aryeh.fried...@gmail.com wrote:
I have a Java program that calls the following code but somehow the
events are not rebroadcasted... from my very limited knowledge of X (I
have known C for years but never used it for GUI work) I highly
suspect I some how got the second arg wrong (it seems that the JAWT
window ID is not the same as the Xorg one)... since this is a high
priority project my client is willing to pay for 1 to 2 hours of
consulting on how to adjust the code to make it work... the final goal
is we want to block all keystrokes not meant for the actual app
(alt-f1:f9, ctl-alt-del, etc.)... namely the client is making a
application to apply standardized tests to distance learning students
and we need to enable a kiosk like mode (the user can not break out
the app [or as much as is possible]... the reason is we want to
prevent the test taker of using this as a work around the closed
book restriction on a closed book test)... I can either have no
event filtering (all events go their intended targets) or filtering
and no forwarding (namely if a invert the test of which process to
terminate on fork(2)).
Note: I tried both InputFocus and PointerFocus for the target win of
the event but that doesn't work nor does key-win. Also I can handle
all the coding except the actual XLib/XCB calls.
// src/c/KioskJNI.c
/**
* Any C needed to make Kiosk Mode work as expected
*
* Copyright (C) 2010-2011. Friedman-Nixon-Wong Enterprises, LLC.
*
* @author aryeh
* @version Mon Dec 5 03:47:46 2011
*/
#include signal.h
#include X11/Xlib.h
#include jawt_md.h
#include client_kiosk_core_KioskJNI.h
/**
* Block all OS signals (param's ignored)
*/
JNIEXPORT void JNICALL
Java_client_kiosk_core_KioskJNI_blockSigs(JNIEnv *env, jclass cls,
jobject comp)
{
Display *dpy=XOpenDisplay(0);
int i=0;
for(i=0;i256;i++)
signal(i,SIG_IGN);
JAWT awt;
printf(fart\n);
// Get the AWT
awt.version = JAWT_VERSION_1_4;
jboolean result = JAWT_GetAWT(env, awt);
JAWT_DrawingSurface* ds=awt.GetDrawingSurface(env, comp);
ds-Lock(ds);
JAWT_DrawingSurfaceInfo* dsi=ds-GetDrawingSurfaceInfo(ds);
JAWT_X11DrawingSurfaceInfo* dsi_win =
(JAWT_X11DrawingSurfaceInfo*)dsi-platformInfo;
printf(dsi %p\n,dsi);
printf(ds %p\n,ds);
jlong win=dsi_win-visualID;
I don't know AWT very well, but I would assume that if it were using
similar naming terminology to the rest of xlib, then I think that
dsi_win-visualID; is probably not the correct
printf(dsi_win %p\n,win);
Have you tried using the result of this in xwininfo -id ?
// Free the drawing surface info
ds-FreeDrawingSurfaceInfo(dsi);
// Unlock the drawing surface
ds-Unlock(ds);
// Free the drawing surface
awt.FreeDrawingSurface(ds);
XGrabKeyboard(dpy, DefaultRootWindow(dpy), True, GrabModeAsync,
GrabModeAsync, CurrentTime);
int pid=fork();
if(!pid) {
return;
}
printf(%d\n,pid);
XEvent ev;
while(1) {
XNextEvent(dpy,ev);
XKeyEvent *key=(XKeyEvent *) ev;
printf(You typed a %d\n,key-keycode);
XSendEvent(dpy,win, True, (KeyPressMask | KeyReleaseMask),
ev);
Have you ensured that the receiving client has selected for
KeyPressMask and KeyReleaseMask ?
Check with xwininfo -id client_id -all
XFlush(dpy);
}
XCloseDisplay(dpy);
}
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: smspil...@gmail.com
--
Sam Spilsbury
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: Looking for **PAID** help with calling XSendEvent correctly
Thanks for the clue it was not exactly what you said but it gave me
the right idea (namely instead of rebroadcasting I use normal method
calling to make a callback in Java for the keystroke)
On Fri, Dec 23, 2011 at 4:58 AM, Sam Spilsbury smspil...@gmail.com wrote:
On Thu, Dec 22, 2011 at 9:20 AM, Aryeh Friedman
aryeh.fried...@gmail.com wrote:
I have a Java program that calls the following code but somehow the
events are not rebroadcasted... from my very limited knowledge of X (I
have known C for years but never used it for GUI work) I highly
suspect I some how got the second arg wrong (it seems that the JAWT
window ID is not the same as the Xorg one)... since this is a high
priority project my client is willing to pay for 1 to 2 hours of
consulting on how to adjust the code to make it work... the final goal
is we want to block all keystrokes not meant for the actual app
(alt-f1:f9, ctl-alt-del, etc.)... namely the client is making a
application to apply standardized tests to distance learning students
and we need to enable a kiosk like mode (the user can not break out
the app [or as much as is possible]... the reason is we want to
prevent the test taker of using this as a work around the closed
book restriction on a closed book test)... I can either have no
event filtering (all events go their intended targets) or filtering
and no forwarding (namely if a invert the test of which process to
terminate on fork(2)).
Note: I tried both InputFocus and PointerFocus for the target win of
the event but that doesn't work nor does key-win. Also I can handle
all the coding except the actual XLib/XCB calls.
// src/c/KioskJNI.c
/**
* Any C needed to make Kiosk Mode work as expected
*
* Copyright (C) 2010-2011. Friedman-Nixon-Wong Enterprises, LLC.
*
* @author aryeh
* @version Mon Dec 5 03:47:46 2011
*/
#include signal.h
#include X11/Xlib.h
#include jawt_md.h
#include client_kiosk_core_KioskJNI.h
/**
* Block all OS signals (param's ignored)
*/
JNIEXPORT void JNICALL
Java_client_kiosk_core_KioskJNI_blockSigs(JNIEnv *env, jclass cls,
jobject comp)
{
Display *dpy=XOpenDisplay(0);
int i=0;
for(i=0;i256;i++)
signal(i,SIG_IGN);
JAWT awt;
printf(fart\n);
// Get the AWT
awt.version = JAWT_VERSION_1_4;
jboolean result = JAWT_GetAWT(env, awt);
JAWT_DrawingSurface* ds=awt.GetDrawingSurface(env, comp);
ds-Lock(ds);
JAWT_DrawingSurfaceInfo* dsi=ds-GetDrawingSurfaceInfo(ds);
JAWT_X11DrawingSurfaceInfo* dsi_win =
(JAWT_X11DrawingSurfaceInfo*)dsi-platformInfo;
printf(dsi %p\n,dsi);
printf(ds %p\n,ds);
jlong win=dsi_win-visualID;
I don't know AWT very well, but I would assume that if it were using
similar naming terminology to the rest of xlib, then I think that
dsi_win-visualID; is probably not the correct
printf(dsi_win %p\n,win);
Have you tried using the result of this in xwininfo -id ?
// Free the drawing surface info
ds-FreeDrawingSurfaceInfo(dsi);
// Unlock the drawing surface
ds-Unlock(ds);
// Free the drawing surface
awt.FreeDrawingSurface(ds);
XGrabKeyboard(dpy, DefaultRootWindow(dpy), True, GrabModeAsync,
GrabModeAsync, CurrentTime);
int pid=fork();
if(!pid) {
return;
}
printf(%d\n,pid);
XEvent ev;
while(1) {
XNextEvent(dpy,ev);
XKeyEvent *key=(XKeyEvent *) ev;
printf(You typed a %d\n,key-keycode);
XSendEvent(dpy,win, True, (KeyPressMask | KeyReleaseMask),
ev);
Have you ensured that the receiving client has selected for
KeyPressMask and KeyReleaseMask ?
Check with xwininfo -id client_id -all
XFlush(dpy);
}
XCloseDisplay(dpy);
}
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: smspil...@gmail.com
--
Sam Spilsbury
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: XInput: Atmel maXTouch Digitizer touch screen
On 22.12.2011 07:41, Chase Douglas wrote: You can fiddle with the input class like you have been to resolve this. Add these lines to your input class: Driver evdev Option Mode Absolute I did this, but then the clicks by tapping don't work at all anymore. I.e. mouse cursor follows my finger, but I cannot activate anything. Or, fix your driver so it works properly. Simply removing the registration of the BTN_TOOL_EVENT should work. It doesn't even use BTN_TOOL_FINGER. I've seen this exact issue on almost every driver of Android origin, like they're all copy pasted. Do you think I should still proceed this way, given above? You may know this already as well, but your driver/device is only operating as a single-touch capable device. maXTouch chips all support at least some multitouch, IIRC. There is an upstream Linux driver for these chips, and it supports multitouch. Yes, I know. For a start, I'd be quite happy to get a single finger and a nice onscreen keyboard working properly. You mean hid-multitouch or some other one? The hid-multitouch didn't work, because the USD IDs are not registered and apparently the udev rules trich failed as well. I'll try adding the IDs and recompile the kernel, if you think that will make it work properly. Ben ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: XInput: Atmel maXTouch Digitizer touch screen
On 12/22/2011 04:48 AM, Ben Bucksch wrote: On 22.12.2011 07:41, Chase Douglas wrote: You can fiddle with the input class like you have been to resolve this. Add these lines to your input class: Driver evdev Option Mode Absolute I did this, but then the clicks by tapping don't work at all anymore. I.e. mouse cursor follows my finger, but I cannot activate anything. If I had to guess, BTN_TOOL_FINGER is likely still getting in the way of things in the evdev driver. Or, fix your driver so it works properly. Simply removing the registration of the BTN_TOOL_EVENT should work. It doesn't even use BTN_TOOL_FINGER. I've seen this exact issue on almost every driver of Android origin, like they're all copy pasted. Do you think I should still proceed this way, given above? It looks like you need to fix your kernel driver. You could hack up xserver-xorg-input-evdev to disregard the BTN_TOOL_FINGER event, but I would only do that if you can't fix the kernel driver. You may know this already as well, but your driver/device is only operating as a single-touch capable device. maXTouch chips all support at least some multitouch, IIRC. There is an upstream Linux driver for these chips, and it supports multitouch. Yes, I know. For a start, I'd be quite happy to get a single finger and a nice onscreen keyboard working properly. You mean hid-multitouch or some other one? The hid-multitouch didn't work, because the USD IDs are not registered and apparently the udev rules trich failed as well. I'll try adding the IDs and recompile the kernel, if you think that will make it work properly. No, the maXTouch chips are handled by atmel_mx_ts in drivers/input/touchscreen/atmel_mx_ts.c. -- Chase ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: XInput: Atmel maXTouch Digitizer touch screen
On Wed, Dec 21, 2011 at 11:52:39PM +0100, Ben Bucksch wrote: I have unsuccessfully tried the whole day to configure the Atmel maXTouch Digitizer with USB ID 03eb:211c . This is a touch screen and does appear in X.org as input device. It is working rudimentary, but bad enough to be unusable. The machine is a Samsung Series 7 Slate XE700T1A, a tablet with standard notebook hardware. I am using Ubuntu 11.10 with Ubuntu kernel 3.0.0-14-generic and xorg-server 1.10.4-1ubuntu4.2. Problems: 1. ABSOLUTE By default, it's configured in Mode RELATIVE, but it's ABSOLUTE. When I do xinput --set-mode Atmel Atmel maXTouch Digitizer ABSOLUTE it works. But I need it at the login screen already. I do not understand how to just change certain config options about an input device without changing the whole config. When I put in /etc/X11/x.org.conf.d/atmel.conf : Section InputClass Identifier Atmel touchscreen MatchProduct Atmel Atmel maXTouch Digitizer MatchIsTouchpad on Option Mode Absolute EndSection then I get a complaint in the X.org log that the Driver is missing (yes, I shouldn't get that and I don't understand why I do). If I use Driver synaptics, X.org log complains that it's not a synaptics device. If I use Driver evdev, the clicking (mouse button, tapping) doesn't at all work anymore. Either way, this should work OOTB. Can somebody please fix the driver to make it know that this device is ABSOLUTE? please attach your log, it's too hard to guess which configuration doesn't apply correctly. 2. Button not released Sometimes, it generates only button 1 pressed, but not button 1 released. as Chase said, probably broken kernel driver or device. Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: XInput: Atmel maXTouch Digitizer touch screen
Hey Chase, thanks for your answer. On 22.12.2011 01:41, Chase Douglas wrote: A capture of the evdev events would be necessary to debug the issue. You can use evtest to do this. Done http://www.bucksch.org/xfer/1.evtest The beginning of the log is my finger moving across the screen, in all 4 corners. The end is me tapping on the screen, double-clicking/-tapping, and clicking/tapping long. xinput --list-props 15 gives http://www.bucksch.org/xfer/1.props Xorg.0.log extract http://www.bucksch.org/xfer/Xorg.0.log It needs to conform to what is stated at: Sorry, but I can't judge that. Ben ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: XInput: Atmel maXTouch Digitizer touch screen
On 12/21/2011 09:25 PM, Ben Bucksch wrote: Hey Chase, thanks for your answer. On 22.12.2011 01:41, Chase Douglas wrote: A capture of the evdev events would be necessary to debug the issue. You can use evtest to do this. Done http://www.bucksch.org/xfer/1.evtest Your driver is reporting the availability of BTN_TOOL_FINGER. This is only valid for touchpads. That's why the synaptics driver is loading instead of the evdev driver. You can fiddle with the input class like you have been to resolve this. Add these lines to your input class: Driver evdev Option Mode Absolute Or, fix your driver so it works properly. Simply removing the registration of the BTN_TOOL_EVENT should work. It doesn't even use BTN_TOOL_FINGER. I've seen this exact issue on almost every driver of Android origin, like they're all copy pasted. Hopefully, with either of these two resolutions things will work right. I don't see anything else wrong. You may know this already as well, but your driver/device is only operating as a single-touch capable device. maXTouch chips all support at least some multitouch, IIRC. There is an upstream Linux driver for these chips, and it supports multitouch. I've heard that at least nVidia has switched over to using it, though their previous driver supported multitouch too. -- Chase ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: how exactly does X11 work with virtual terminals?
On 12/19/11 14:20, James Strother wrote: Quite honestly, I have only a basic understanding for what the virtual terminals are and how they work, so I am baffled as to how I would resolve this issue. Does Xorg really need a virtual terminal, or can I start it without one? Is there another way to sort this out? Sounds like you need the flag that was originally added for the multiseat support in Xorg: -sharevts Share virtual terminals with another X server, if supported by the OS. Google finds pages such as https://help.ubuntu.com/community/MultiseatX that should have more information. -- -Alan Coopersmith-alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: xorg Digest, Vol 77, Issue 8
Hi everybody How can I find best resolution for L1752S LG monitor and make changes in xorg.conf. Is there any other solution? My fedora14 does not recognize the monitor. Thanks ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: help with xorg.conf
Hi Alan, Thanks for the info, that fixed the first problem. I had assumed that Xorg was looking in the config dir listed in the Xorg log, which was obviously a poor assumption. Thanks again, James On Wed, Dec 14, 2011 at 8:11 PM, Alan Coopersmith alan.coopersm...@oracle.com wrote: On 12/14/11 14:08, James Strother wrote: Problem 1: Unable to access config file at non-default location as non-root - This seems like an extremely simple problem, but I'm stumped. I have written an alt.conf file, and place it into /etc/X11/xorg.conf.d. The file exists, is owned by root, and has permissions of 644. It shows up on ls just fine: $ ls /etc/X11/xorg.conf.d alt.conf But I can't actually get Xorg to find or use that file: $ Xorg :1 -config alt.conf /etc/X11/xorg.conf.d is not the location for alternate configuration files - it's used for config file fragments to be used by *ALL* Xorg instances run on the system. The xorg.conf man page lists the directories you can put alternate configuration files in (I just noticed that Xorg(1) man page does not, though it does point you off to the xorg.conf man page for the full list). For instance, for testing, I have a /etc/X11/xorg.conf.dummy config file that loads the dummy driver, which I can run with Xorg -config xorg.conf.dummy, and in our OS packages, we ship /usr/lib/X11/xorg.conf.vesa so that the OS installer can run Xorg -config xorg.conf.vesa when the normal drivers fail on the LiveCD and the user chooses the VESA mode option from the grub menu instead. I expected this to connect to the graphics card at PCI:12:0:0 in order to create a one monitor screen. However, Xorg actually connects to both cards and then only displays on the graphics card at PCI:8:0:0. I have tried setting AutoAddDevices/AutoEnableDevices to false in ServerFlags without success. The AutoAddDevices/AutoEnableDevices flags only apply to input devices not video cards. (I can't explain the rest of your issue here, just that bit.) -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: help with xorg.conf
On 12/14/11 14:08, James Strother wrote: Problem 1: Unable to access config file at non-default location as non-root - This seems like an extremely simple problem, but I'm stumped. I have written an alt.conf file, and place it into /etc/X11/xorg.conf.d. The file exists, is owned by root, and has permissions of 644. It shows up on ls just fine: $ ls /etc/X11/xorg.conf.d alt.conf But I can't actually get Xorg to find or use that file: $ Xorg :1 -config alt.conf /etc/X11/xorg.conf.d is not the location for alternate configuration files - it's used for config file fragments to be used by *ALL* Xorg instances run on the system. The xorg.conf man page lists the directories you can put alternate configuration files in (I just noticed that Xorg(1) man page does not, though it does point you off to the xorg.conf man page for the full list). For instance, for testing, I have a /etc/X11/xorg.conf.dummy config file that loads the dummy driver, which I can run with Xorg -config xorg.conf.dummy, and in our OS packages, we ship /usr/lib/X11/xorg.conf.vesa so that the OS installer can run Xorg -config xorg.conf.vesa when the normal drivers fail on the LiveCD and the user chooses the VESA mode option from the grub menu instead. I expected this to connect to the graphics card at PCI:12:0:0 in order to create a one monitor screen. However, Xorg actually connects to both cards and then only displays on the graphics card at PCI:8:0:0. I have tried setting AutoAddDevices/AutoEnableDevices to false in ServerFlags without success. The AutoAddDevices/AutoEnableDevices flags only apply to input devices not video cards. (I can't explain the rest of your issue here, just that bit.) -- -Alan Coopersmith-alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev input module and multiple X screen support
Peter, I have been looking at this for a while and have not been able to get my system setup correctly as it is a rather complex setup. I have 4 monitors on this system. The first one is NOT a touch screen and is at 800X600, the other 3 are touch screens at 1280X1024, with the center of those 3 rotated to portrait mode. I am not quite sure how to proceed looking at the examples provided since none of them really give me any idea of what to do about my first monitor which is not a touch device. I am assuming that I still need to account for it in the equations, is that a valid assumption? #xinput list â¡ Virtual core pointer id=2[master pointer (3)] â â³ Virtual core XTEST pointer id=4[slave pointer (2)] â â³ TouchScreenLeft id=6[slave pointer (2)] â â³ TouchScreenCenterid=7[slave pointer (2)] â â³ TouchScreenRight id=8[slave pointer (2)] ⣠Virtual core keyboardid=3[master keyboard (2)] â³ Virtual core XTEST keyboard id=5[slave keyboard (3)] â³ Power Button id=9[slave keyboard (3)] â³ Power Button id=10 [slave keyboard (3)] â³ Logitech USB Keyboardid=11 [slave keyboard (3)] â³ Logitech USB Keyboardid=12 [slave keyboard (3)] #xinput list-props TouchScreenLeft Device 'TouchScreenLeft': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenCenter Device 'TouchScreenCenter': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenRight Device 'TouchScreenRight': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 So first to make it a little easier no rotation for now on #2: 0: 800/(800 + (3*1280) ) 00 0 600/1024 0 0 0 1 1: 1280/(800 + (3*1280) ) 0 800/(800 + (3*1280) ) 0 1024/10240 0 01 2: 1280/(800 + (3*1280) ) 0 800+1280/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 3: 1280/(800 + (3*1280) ) 0 800 + (2*1280)/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 Does that look about correct, because the math on the 3rd number or c2 from the equation examples does not seem to add up properly to equal a total of 1. Regards, Curtis On 09.12.2011 23:37, Peter Hutterer wrote: On Fri, Dec 09, 2011 at 12:47:10PM -0500, Curtis Rubel wrote: Hello xorg... Can someone tell me if multiple X screen support is planned for the evdev input module? We have a number of multiple X screen systems here running Xorg using the older evtouch input library and from what I can see it appears this module is no longer supported and being replaced by the evdev module. Is this the case or has the evtouch input library just not been updated yet?? Any help in this matter would be greatly appreciated...as the touch screen vendor ELO does not support multiple USB touchscreens on a single system... input drivers don't do multi-screen handling (anymore), it's all handled by the server now. See the documentation here: http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage Cheers, Peter -- Curtis Rubel Senior Development Engineer Compro Computer Services, Inc. 105 East Drive - Melbourne, Florida, 32904 Phone: 321-727-2211 email: cru...@compro.net Web: http://www.compro.net An ISO 9001:2008 Registered Company --- CONFIDENTIALITY NOTICE: This email transmission, and any documents, files or previous email messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by email or call 321-727-2211. Please destroy the original transmission and its attachments without reading or saving it in any manner. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info:
Re: evdev input module and multiple X screen support
Peter, I did attempt to try setting the values to those I sent you below and when I touch any of the touch screens, my cursor still remains in the first monitor screen and I never see it move to any of the other 3 touch monitors. Is there something else I need to do other than set the xinput settings to get the new settings to take effect? Regards, Curtis On 12.12.2011 09:02, Curtis Rubel wrote: Peter, I have been looking at this for a while and have not been able to get my system setup correctly as it is a rather complex setup. I have 4 monitors on this system. The first one is NOT a touch screen and is at 800X600, the other 3 are touch screens at 1280X1024, with the center of those 3 rotated to portrait mode. I am not quite sure how to proceed looking at the examples provided since none of them really give me any idea of what to do about my first monitor which is not a touch device. I am assuming that I still need to account for it in the equations, is that a valid assumption? #xinput list â¡ Virtual core pointer id=2[master pointer (3)] â â³ Virtual core XTEST pointer id=4[slave pointer (2)] â â³ TouchScreenLeft id=6[slave pointer (2)] â â³ TouchScreenCenterid=7[slave pointer (2)] â â³ TouchScreenRight id=8[slave pointer (2)] ⣠Virtual core keyboardid=3[master keyboard (2)] â³ Virtual core XTEST keyboard id=5[slave keyboard (3)] â³ Power Button id=9[slave keyboard (3)] â³ Power Button id=10 [slave keyboard (3)] â³ Logitech USB Keyboardid=11 [slave keyboard (3)] â³ Logitech USB Keyboardid=12 [slave keyboard (3)] #xinput list-props TouchScreenLeft Device 'TouchScreenLeft': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenCenter Device 'TouchScreenCenter': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenRight Device 'TouchScreenRight': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 So first to make it a little easier no rotation for now on #2: 0: 800/(800 + (3*1280) ) 00 0 600/1024 0 0 0 1 1: 1280/(800 + (3*1280) ) 0 800/(800 + (3*1280) ) 0 1024/10240 0 01 2: 1280/(800 + (3*1280) ) 0 800+1280/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 3: 1280/(800 + (3*1280) ) 0 800 + (2*1280)/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 Does that look about correct, because the math on the 3rd number or c2 from the equation examples does not seem to add up properly to equal a total of 1. Regards, Curtis On 09.12.2011 23:37, Peter Hutterer wrote: On Fri, Dec 09, 2011 at 12:47:10PM -0500, Curtis Rubel wrote: Hello xorg... Can someone tell me if multiple X screen support is planned for the evdev input module? We have a number of multiple X screen systems here running Xorg using the older evtouch input library and from what I can see it appears this module is no longer supported and being replaced by the evdev module. Is this the case or has the evtouch input library just not been updated yet?? Any help in this matter would be greatly appreciated...as the touch screen vendor ELO does not support multiple USB touchscreens on a single system... input drivers don't do multi-screen handling (anymore), it's all handled by the server now. See the documentation here: http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage Cheers, Peter -- Curtis Rubel Senior Development Engineer Compro Computer Services, Inc. 105 East Drive - Melbourne, Florida, 32904 Phone: 321-727-2211 email: cru...@compro.net Web: http://www.compro.net An ISO 9001:2008 Registered Company --- CONFIDENTIALITY NOTICE: This email transmission, and any documents, files or previous email messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of any of the information contained in or attached to this transmission is STRICTLY
Re: evdev input module and multiple X screen support
On Mon, Dec 12, 2011 at 09:02:29AM -0500, Curtis Rubel wrote: Peter, I have been looking at this for a while and have not been able to get my system setup correctly as it is a rather complex setup. I have 4 monitors on this system. The first one is NOT a touch screen and is at 800X600, the other 3 are touch screens at 1280X1024, with the center of those 3 rotated to portrait mode. I am not quite sure how to proceed looking at the examples provided since none of them really give me any idea of what to do about my first monitor which is not a touch device. you only set the matrix if you want a input device bound to an _area_ on the screen. so don't think of it in terms of monitors, think of it in terms of touchscreens - the first touchscreen should be mapped to area of the the second monitor from the left, etc. I am assuming that I still need to account for it in the equations, is that a valid assumption? #xinput list â¡ Virtual core pointer id=2[master pointer (3)] â â³ Virtual core XTEST pointer id=4[slave pointer (2)] â â³ TouchScreenLeft id=6[slave pointer (2)] â â³ TouchScreenCenterid=7[slave pointer (2)] â â³ TouchScreenRight id=8[slave pointer (2)] ⣠Virtual core keyboardid=3[master keyboard (2)] â³ Virtual core XTEST keyboard id=5[slave keyboard (3)] â³ Power Button id=9[slave keyboard (3)] â³ Power Button id=10 [slave keyboard (3)] â³ Logitech USB Keyboardid=11 [slave keyboard (3)] â³ Logitech USB Keyboardid=12 [slave keyboard (3)] #xinput list-props TouchScreenLeft Device 'TouchScreenLeft': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenCenter Device 'TouchScreenCenter': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenRight Device 'TouchScreenRight': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 So first to make it a little easier no rotation for now on #2: 0: 800/(800 + (3*1280) ) 00 0 600/1024 0 0 0 1 1: 1280/(800 + (3*1280) ) 0 800/(800 + (3*1280) ) 0 1024/10240 0 01 2: 1280/(800 + (3*1280) ) 0 800+1280/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 3: 1280/(800 + (3*1280) ) 0 800 + (2*1280)/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 Does that look about correct, because the math on the 3rd number or c2 from the equation examples does not seem to add up properly to equal a total of 1. I can't see anything wrong at a quick glance, though I suggest just trying with simple values (e.g. 0.5) first to make sure the mapping works at all (see below). c2 shouldn't usually add up to 1 since that'd be an offset of the display width - i don't think there's a use-case for that :) for the right-most screen, usually you'd want c0 + c2 to add up to 1. also, something I forgot in the first email: the matrix only works properly for RandR displays if you're using a released server version, only the git version supports this for traditional multihead. Cheers, Peter On 09.12.2011 23:37, Peter Hutterer wrote: On Fri, Dec 09, 2011 at 12:47:10PM -0500, Curtis Rubel wrote: Hello xorg... Can someone tell me if multiple X screen support is planned for the evdev input module? We have a number of multiple X screen systems here running Xorg using the older evtouch input library and from what I can see it appears this module is no longer supported and being replaced by the evdev module. Is this the case or has the evtouch input library just not been updated yet?? Any help in this matter would be greatly appreciated...as the touch screen vendor ELO does not support multiple USB touchscreens on a single system... input drivers don't do multi-screen handling (anymore), it's all handled by the server now. See the documentation here: http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage Cheers, Peter -- Curtis Rubel Senior Development Engineer Compro Computer Services, Inc. 105 East Drive - Melbourne, Florida, 32904 Phone: 321-727-2211 email: cru...@compro.net Web: http://www.compro.net An ISO
Re: evdev input module and multiple X screen support
Peter, What I am seeing when I run with the settings I sent you below, is that the cursor actually stays in the first monitor. However it appear to be scaled so that as I touch the other 3 touch screens the cursor will move further and further right until I am finally on my last touch screen and the cursor arrow finally can reach the rightmost side of the first monitor. My release of Xorg shows as: X.Org X Server 1.10.4 Release Date: 2011-08-19 from the Xorg.0.log file... So I guess from that information can you determine if I can actually do what I need to do with the version I have installed from the OpenSuSE 12.1 release? Will I need to download from git, build and install that version? Or will it even support separate X screens at all and will I need to switch into a Xinerama type setup? I really appreciate all your help and insight into this.having to switch from an easy method where the input driver would do this for us to this new way is a little bit confusing for me. Best Regards, Curtis On 12.12.2011 16:23, Peter Hutterer wrote: On Mon, Dec 12, 2011 at 09:02:29AM -0500, Curtis Rubel wrote: Peter, I have been looking at this for a while and have not been able to get my system setup correctly as it is a rather complex setup. I have 4 monitors on this system. The first one is NOT a touch screen and is at 800X600, the other 3 are touch screens at 1280X1024, with the center of those 3 rotated to portrait mode. I am not quite sure how to proceed looking at the examples provided since none of them really give me any idea of what to do about my first monitor which is not a touch device. you only set the matrix if you want a input device bound to an _area_ on the screen. so don't think of it in terms of monitors, think of it in terms of touchscreens - the first touchscreen should be mapped to area of the the second monitor from the left, etc. I am assuming that I still need to account for it in the equations, is that a valid assumption? #xinput list â¡ Virtual core pointer id=2[master pointer (3)] â â³ Virtual core XTEST pointer id=4[slave pointer (2)] â â³ TouchScreenLeft id=6[slave pointer (2)] â â³ TouchScreenCenterid=7[slave pointer (2)] â â³ TouchScreenRight id=8[slave pointer (2)] ⣠Virtual core keyboardid=3[master keyboard (2)] â³ Virtual core XTEST keyboard id=5[slave keyboard (3)] â³ Power Button id=9[slave keyboard (3)] â³ Power Button id=10 [slave keyboard (3)] â³ Logitech USB Keyboardid=11 [slave keyboard (3)] â³ Logitech USB Keyboardid=12 [slave keyboard (3)] #xinput list-props TouchScreenLeft Device 'TouchScreenLeft': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenCenter Device 'TouchScreenCenter': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 #xinput list-props TouchScreenRight Device 'TouchScreenRight': Device Enabled (117): 1 Coordinate Transformation Matrix (119): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 So first to make it a little easier no rotation for now on #2: 0: 800/(800 + (3*1280) ) 00 0 600/1024 0 0 0 1 1: 1280/(800 + (3*1280) ) 0 800/(800 + (3*1280) ) 0 1024/10240 0 01 2: 1280/(800 + (3*1280) ) 0 800+1280/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 3: 1280/(800 + (3*1280) ) 0 800 + (2*1280)/(800 + (3*1280) ) 0 1024/1024 0 0 0 1 Does that look about correct, because the math on the 3rd number or c2 from the equation examples does not seem to add up properly to equal a total of 1. I can't see anything wrong at a quick glance, though I suggest just trying with simple values (e.g. 0.5) first to make sure the mapping works at all (see below). c2 shouldn't usually add up to 1 since that'd be an offset of the display width - i don't think there's a use-case for that :) for the right-most screen, usually you'd want c0 + c2 to add up to 1. also, something I forgot in the first email: the matrix only works properly for RandR displays if you're using a released server version, only the git version supports this for traditional multihead. Cheers, Peter On 09.12.2011 23:37, Peter Hutterer wrote: On Fri, Dec 09, 2011 at 12:47:10PM -0500,
Re: evdev input module and multiple X screen support
Thank you... I will take a look at the new info Regards Curtis Rubel Sent from my iPhone On Dec 9, 2011, at 23:37, Peter Hutterer peter.hutte...@who-t.net wrote: On Fri, Dec 09, 2011 at 12:47:10PM -0500, Curtis Rubel wrote: Hello xorg... Can someone tell me if multiple X screen support is planned for the evdev input module? We have a number of multiple X screen systems here running Xorg using the older evtouch input library and from what I can see it appears this module is no longer supported and being replaced by the evdev module. Is this the case or has the evtouch input library just not been updated yet?? Any help in this matter would be greatly appreciated...as the touch screen vendor ELO does not support multiple USB touchscreens on a single system... input drivers don't do multi-screen handling (anymore), it's all handled by the server now. See the documentation here: http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Good afternoon
hi Samuel, i have never heard about virtual gl and it seems that this is more a problem of VirtualGL. i used google to found the mail below may be it can help you. http://www.mail-archive.com/virtualgl-users@lists.sourceforge.net/msg00023.html re, wh Am 09.12.2011 08:48, schrieb Samuel Boateng: Hello, I just installed VirtualGL-2.2.90 on my machine which runs on Centos5.7. After installation I had to test to see if everything was successful but unfortunately I encountered this error: Xlib: Extension GLX missing on display 0:0, Error: Couldn't get an RGB Double Buffered visual. I have not found a way out as at now. Could your team please give me some support? Urgently needed. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev input module and multiple X screen support
On Fri, Dec 09, 2011 at 12:47:10PM -0500, Curtis Rubel wrote: Hello xorg... Can someone tell me if multiple X screen support is planned for the evdev input module? We have a number of multiple X screen systems here running Xorg using the older evtouch input library and from what I can see it appears this module is no longer supported and being replaced by the evdev module. Is this the case or has the evtouch input library just not been updated yet?? Any help in this matter would be greatly appreciated...as the touch screen vendor ELO does not support multiple USB touchscreens on a single system... input drivers don't do multi-screen handling (anymore), it's all handled by the server now. See the documentation here: http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: rRadeon 9000 + X.Org 1.11.2 + EnablePageFlip + opengl = crash
On Die, 2011-12-06 at 17:44 -0500, Alex Deucher wrote: On Tue, Dec 6, 2011 at 5:04 PM, Giuliano Pochini poch...@shiny.it wrote: I also tried KMS. When EnablePageFlip is enabled glxgears renders nothing and X freezes immediately except the mouse pointer. After a few second the screen blanks and a reboot is the only cure. W/o EnablePageFlip it works better. glxgears looks OK, but it runs at 60fps. xterm colours are wrong. Wrong xterm colours would be an xf86-video-ati issue. Everything else seems fine. Running other 3D apps (Nexuiz, Scorched3D) works fine at first, but seconds or minutes later it locks up the same way without any symptom before that moment. With KMS apps are synced the refresh rate by default, you can override that by setting the env var vblank_mode=0, e.g., vblank_mode=0 glxgears Pageflipping with KMS works fine here, so it may be something mac specific. It works fine on this PowerBook with an RV350, but glxgears can't really use page flipping anyway with KMS, unless you run it in fullscreen mode maybe. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Question about pixman,x11perf and xserver
On 12/5/11 6:39 AM, 杨帅 wrote: 1.I recompile the pixman with enable-neon,but when I use the x11perf for testing ,I can‘t see the significant difference between the pixman with neon and pixman without neon.That's why? Presumably because you're not hitting a neon-accelerated path. You've not said which x11perf tests you are measuring with. Be aware that many of them are not at all relevant for real world performance. 2.xserver use which drawing library to resizing the window,scroll the text window ,and so on? 3.which library excepts pixman could I optimize using neon to improve the performance of xserver? The X server has an internal library called 'fb' for this. fb is a layer around pixman that implements X core rendering, either by calling down to pixman or directly. - ajax ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: rRadeon 9000 + X.Org 1.11.2 + EnablePageFlip + opengl = crash
On Tue, 6 Dec 2011 08:46:41 + Dave Airlie airl...@gmail.com wrote: On Mon, Dec 5, 2011 at 8:41 PM, Giuliano Pochini poch...@shiny.it wrote: First, my config: :00:10.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev 01) Linux Jay 3.1.0 #3 SMP Tue Nov 1 17:58:39 CET 2011 ppc 7455, altivec supported PowerMac3,6 GNU/Linux When EnablePageFlip is enabled the machine crashes as soon as another window hides any part of the glxgears window. The screen turns off and a hard reset is needed (Rsys+B does not work). I'm not using KMS. Thats probably the problem then. Supporting UMS is not on anyones list that cares anymore. Well, I think EnablePageFlip was just ignored in older versions of Xorg or kernel. Now, when EnablePageFlip is enabled, glxgears runs about 15% faster, while it made no difference before. I also tried KMS. When EnablePageFlip is enabled glxgears renders nothing and X freezes immediately except the mouse pointer. After a few second the screen blanks and a reboot is the only cure. W/o EnablePageFlip it works better. glxgears looks OK, but it runs at 60fps. xterm colours are wrong. Everything else seems fine. Running other 3D apps (Nexuiz, Scorched3D) works fine at first, but seconds or minutes later it locks up the same way without any symptom before that moment. So unless its a regression in the kernel and you can bisect it I'm not sure you'll see much help. Plus I have pretty old hardware and hard lock ups are hard to debug... -- Giuliano. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: 8k resolution video causes X Error
On 05/12/2011 2:03 AM, Maarten Maathuis wrote: On Sun, Dec 4, 2011 at 6:11 PM, Donald McLachlan donald.mclach...@crc.ca wrote: Hi, I don't know where to start to resolve this problem and guessed maybe this is a good place to start. If not, please point me in the right direction. Our ultimate goal is to stream 8k resolution video using sage (see www.sagecommons.org). - We first used ffmpeg to convert a 4k resolution video file to yuv format, and we were able to view it with ffplay, mplayer, and crcview (an in house program). - We then used ffmpeg to convert/resample the same 4k resolution video file to yuv/8k resolution; the conversion completed without error. - When trying to view the resulting yuv/8k resolution file all three viewer programs failed with the same X Error. For example, here is the output from ffplay: ffplay -i Lupe.8k.yuv -s 8192x4320 -pix_fmt yuv420p -x 1920 -y 1080 ffplay version 0.8, Copyright (c) 2003-2011 the FFmpeg developers built on Nov 30 2011 13:01:22 with gcc 4.5.1 20101208 [gcc-4_5-branch revision 167585] configuration: libavutil51. 9. 1 / 51. 9. 1 libavcodec 53. 7. 0 / 53. 7. 0 libavformat 53. 4. 0 / 53. 4. 0 libavdevice 53. 1. 1 / 53. 1. 1 libavfilter 2. 23. 0 / 2. 23. 0 libswscale2. 0. 0 / 2. 0. 0 [rawvideo @ 0x129d740] Estimating duration from bitrate, this may be inaccurate Input #0, rawvideo, from 'Lupe.8k.yuv': Duration: N/A, start: 0.00, bitrate: N/A Stream #0.0: Video: rawvideo, yuv420p, 8192x4320, 25 tbr, 25 tbn, 25 tbc X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 132 (XVideo) Minor opcode of failed request: 18 () Serial number of failed request: 23 Current serial number in output stream: 24 In case it matters, we are using openSuse 11.4 64 bit linux, on an ASUS P6T7 WS Supercomputer motherboard, with 12 G RAM, and a ASUS GTX590 video card. My guess is the 8k resolution video format is exceeding a buffer size limit somewhere, either in software, or maybe on the video card. Is there a way to find out what buffers are affected and is there a way to overcome these limits? Thanks for any assistance you can provide, Don ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: If this is using the nouveau driver (check lsmod or xorg log), i see that for some reason that it's limited to 4096x4096 for xvideo. See this line: http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nouveau_xv.c#n2031 And then check the contents of DummyEncodingTex and you'll find it refers to the maximum sizes. The command xvinfo confirms this. NV50 and higher (everything starting geforce 8) are able to do 8192x8192, it should just be a matter of making a NV50 specific DummyEncodingTex structure. Hi Maaten, I believe we replaced the nouveau driver with the nvidia driver, but I will double check. I will run the xvinfo command to see what it says limits are. - If need be I guess we could revert to the nouveau driver and modify the DummyEncodingTex structure. - Does anyone know if there something similar we can do with the nvidia driver to enable 8k? (I guess maybe Nvidia are the ones to ask. :-) ) Thanks, and I'll let you know how it goes, Don ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: 8k resolution video causes X Error
On 05/12/2011 9:38 AM, Donald McLachlan wrote: On 05/12/2011 2:03 AM, Maarten Maathuis wrote: On Sun, Dec 4, 2011 at 6:11 PM, Donald McLachlan donald.mclach...@crc.ca wrote: Hi, I don't know where to start to resolve this problem and guessed maybe this is a good place to start. If not, please point me in the right direction. Our ultimate goal is to stream 8k resolution video using sage (see www.sagecommons.org). - We first used ffmpeg to convert a 4k resolution video file to yuv format, and we were able to view it with ffplay, mplayer, and crcview (an in house program). - We then used ffmpeg to convert/resample the same 4k resolution video file to yuv/8k resolution; the conversion completed without error. - When trying to view the resulting yuv/8k resolution file all three viewer programs failed with the same X Error. For example, here is the output from ffplay: ffplay -i Lupe.8k.yuv -s 8192x4320 -pix_fmt yuv420p -x 1920 -y 1080 ffplay version 0.8, Copyright (c) 2003-2011 the FFmpeg developers built on Nov 30 2011 13:01:22 with gcc 4.5.1 20101208 [gcc-4_5-branch revision 167585] configuration: libavutil51. 9. 1 / 51. 9. 1 libavcodec 53. 7. 0 / 53. 7. 0 libavformat 53. 4. 0 / 53. 4. 0 libavdevice 53. 1. 1 / 53. 1. 1 libavfilter 2. 23. 0 / 2. 23. 0 libswscale2. 0. 0 / 2. 0. 0 [rawvideo @ 0x129d740] Estimating duration from bitrate, this may be inaccurate Input #0, rawvideo, from 'Lupe.8k.yuv': Duration: N/A, start: 0.00, bitrate: N/A Stream #0.0: Video: rawvideo, yuv420p, 8192x4320, 25 tbr, 25 tbn, 25 tbc X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 132 (XVideo) Minor opcode of failed request: 18 () Serial number of failed request: 23 Current serial number in output stream: 24 In case it matters, we are using openSuse 11.4 64 bit linux, on an ASUS P6T7 WS Supercomputer motherboard, with 12 G RAM, and a ASUS GTX590 video card. My guess is the 8k resolution video format is exceeding a buffer size limit somewhere, either in software, or maybe on the video card. Is there a way to find out what buffers are affected and is there a way to overcome these limits? Thanks for any assistance you can provide, Don ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: If this is using the nouveau driver (check lsmod or xorg log), i see that for some reason that it's limited to 4096x4096 for xvideo. See this line: http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nouveau_xv.c#n2031 And then check the contents of DummyEncodingTex and you'll find it refers to the maximum sizes. The command xvinfo confirms this. NV50 and higher (everything starting geforce 8) are able to do 8192x8192, it should just be a matter of making a NV50 specific DummyEncodingTex structure. Hi Maaten, I believe we replaced the nouveau driver with the nvidia driver, but I will double check. I will run the xvinfo command to see what it says limits are. - If need be I guess we could revert to the nouveau driver and modify the DummyEncodingTex structure. - Does anyone know if there something similar we can do with the nvidia driver to enable 8k? (I guess maybe Nvidia are the ones to ask. :-) ) Thanks, and I'll let you know how it goes, Don Hi Maarten, (sorry for the typo on your name last time.) lsmod shows: nvidia 11909611 44 and Xorg.0.log shows: /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 180.902] (II) Module nvidia: vendor=NVIDIA Corporation [ 180.902] compiled for 4.0.2, module version = 1.0.0 [ 180.902] Module class: X.Org Video Driver [ 180.902] (II) NVIDIA dlloader X Driver 285.05.09 Fri Sep 23 17:33:35 PDT 2011 [ 180.902] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs So I take it we are running the nvidia driver, not the nouveau driver. Also, xvinfo shows maximum XvImage size: 16384 x 16384 Does that cover video, or just static images? In case it helps, I've attached a file with the text output of the 3 commands. Thanks, Don Script started on Mon 05 Dec 2011 10:00:57 AM EST ]2;crc@crc-fsmanager:~]1;crc-fsmanagercrc@crc-fsmanager:~ lsmod ; xvinfo ; cat /var/log/Xorg.0.log Module Size Used by nls_iso8859_1 4633 0 nls_cp437 6319 0 vfat 10387 0 fat52270 1 vfat iptable_filter 1722 0 ip_tables 18968 1 iptable_filter ip6table_filter 1695 0 ip6_tables 19130 1 ip6table_filter x_tables 24840 4 iptable_filter,ip_tables,ip6table_filter,ip6_tables fuse 69275 3 mpt2sas 129590 2
Re: Question about pixman,x11perf and xserver
On 2011-12-05 06:39, 杨帅 wrote: 1.I recompile the pixman with enable-neon,but when I use the x11perf for testing ,I can‘t see the significant difference between the pixman with neon and pixman without neon.That's why? x11perf is an older test suite, and mostly only tests core graphics. Only x11perf -compwinwin and -comppixwin will make heavy use of pixman (along with the new-style text tests, a*text, aa*text and rgb*text to some extent). The good news is, most modern applications draw using those requests. 2.xserver use which drawing library to resizing the window,scroll the text window ,and so on? Depends on the application. Either pixman, or the fb directory of the server. 3.which library excepts pixman could I optimize using neon to improve the performance of xserver? xserver/fb But first, make sure you're working on something that matters to your application. In particular, cairo-perf-trace is probably more relevant these days than x11perf. See http://cgit.freedesktop.org/cairo-traces/tree/README Peter Harris -- Open Text Connectivity Solutions Group Peter Harrishttp://connectivity.opentext.com/ Research and DevelopmentPhone: +1 905 762 6001 phar...@opentext.comToll Free: 1 877 359 4866 ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: 8k resolution video causes X Error
/usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 180.902] (II) Module nvidia: vendor=NVIDIA Corporation [ 180.902] compiled for 4.0.2, module version = 1.0.0 [ 180.902] Module class: X.Org Video Driver [ 180.902] (II) NVIDIA dlloader X Driver 285.05.09 Fri Sep 23 17:33:35 PDT 2011 [ 180.902] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs So I take it we are running the nvidia driver, not the nouveau driver. You are - so you need to discuss that case with Nvidia not Xorg if you want to make much progress on that driver. Alan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: 8k resolution video causes X Error
On Sun, Dec 4, 2011 at 6:11 PM, Donald McLachlan donald.mclach...@crc.ca wrote: Hi, I don't know where to start to resolve this problem and guessed maybe this is a good place to start. If not, please point me in the right direction. Our ultimate goal is to stream 8k resolution video using sage (see www.sagecommons.org). - We first used ffmpeg to convert a 4k resolution video file to yuv format, and we were able to view it with ffplay, mplayer, and crcview (an in house program). - We then used ffmpeg to convert/resample the same 4k resolution video file to yuv/8k resolution; the conversion completed without error. - When trying to view the resulting yuv/8k resolution file all three viewer programs failed with the same X Error. For example, here is the output from ffplay: ffplay -i Lupe.8k.yuv -s 8192x4320 -pix_fmt yuv420p -x 1920 -y 1080 ffplay version 0.8, Copyright (c) 2003-2011 the FFmpeg developers built on Nov 30 2011 13:01:22 with gcc 4.5.1 20101208 [gcc-4_5-branch revision 167585] configuration: libavutil 51. 9. 1 / 51. 9. 1 libavcodec 53. 7. 0 / 53. 7. 0 libavformat 53. 4. 0 / 53. 4. 0 libavdevice 53. 1. 1 / 53. 1. 1 libavfilter 2. 23. 0 / 2. 23. 0 libswscale 2. 0. 0 / 2. 0. 0 [rawvideo @ 0x129d740] Estimating duration from bitrate, this may be inaccurate Input #0, rawvideo, from 'Lupe.8k.yuv': Duration: N/A, start: 0.00, bitrate: N/A Stream #0.0: Video: rawvideo, yuv420p, 8192x4320, 25 tbr, 25 tbn, 25 tbc X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 132 (XVideo) Minor opcode of failed request: 18 () Serial number of failed request: 23 Current serial number in output stream: 24 In case it matters, we are using openSuse 11.4 64 bit linux, on an ASUS P6T7 WS Supercomputer motherboard, with 12 G RAM, and a ASUS GTX590 video card. My guess is the 8k resolution video format is exceeding a buffer size limit somewhere, either in software, or maybe on the video card. Is there a way to find out what buffers are affected and is there a way to overcome these limits? Thanks for any assistance you can provide, Don ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com If this is using the nouveau driver (check lsmod or xorg log), i see that for some reason that it's limited to 4096x4096 for xvideo. See this line: http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nouveau_xv.c#n2031 And then check the contents of DummyEncodingTex and you'll find it refers to the maximum sizes. The command xvinfo confirms this. NV50 and higher (everything starting geforce 8) are able to do 8192x8192, it should just be a matter of making a NV50 specific DummyEncodingTex structure. -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [Xcb] [admin] X.Org list configuration change
[Dropping the CCs to announce and commit lists.] On Fri, Dec 02, 2011 at 06:19:44PM +, Daniel Stone wrote: Hi all, To clean things up a bit, we will be moving the following lists from lists.freedesktop.org to lists.x.org on Tuesday afternoon European time: xorg@lists.freedesktop.org xorg-annou...@lists.freedesktop.org xorg-com...@lists.freedesktop.org x...@lists.freedesktop.org xcb-comm...@lists.freedesktop.org Will the existing email addresses for those lists continue to work? Some of those list addresses have various references scattered about, and it would help if they forwarded to the new location. - Josh Triplett ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [Xcb] [admin] X.Org list configuration change
Hi, On 2 December 2011 18:34, Josh Triplett j...@joshtriplett.org wrote: On Fri, Dec 02, 2011 at 06:19:44PM +, Daniel Stone wrote: Hi all, To clean things up a bit, we will be moving the following lists from lists.freedesktop.org to lists.x.org on Tuesday afternoon European time: [...] Will the existing email addresses for those lists continue to work? Some of those list addresses have various references scattered about, and it would help if they forwarded to the new location. Sorry, I should've clarified: yes, they will both now and always. Cheers, Daniel ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
Am 28.11.2011 07:43, schrieb Maarten Maathuis: ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com No, damage is an extention, it is called by EXA, it's probably adding all you rectangles to a damage region used to determine how much data is actually valid (needed for ram--vram migrations for example). One thing that just comes to mind, if you are rendering a million rectangles, how many of those do you actually see on your screen? Most of them are only 1x1 pixel wide. And lots of rectangles share the same pixel. I assue that one can optimize the application. But I did not write it and do not know how it works. I only know that it was able to show vector pictures consisting of millions of rectangles within seconds (VLSI design data) when run on XFree86. With Xorg it takes minutes. I only see the problem because we recently upgraded our X11 thin clients to better hardware. But they turned out to be much slower than the older ones. My quest to find the problem has led me to the damage extension now. First I thought it was a network problem. But Xorg was also slow on my notebook when the program was started locally. The contrast is striking: The old XFree86 thin clients were able to draw all the rectangles that were sent over a 100 MBit ethernet network in seconds. While my more powerful Xorg server needs minutes although the software runs on the same machine. However, I was able to improve the runtime of the first operation in damagePolyRectangle. The runtime of my benchmark went down from 90 seconds to 64 seconds. Now one has to look at (*pGC-ops-PolyRectangle)(pDrawable, pGC, nRects, pRects); Thanks Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Disabling EXA
On Sat, Nov 26, 2011 at 10:33 AM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: Hi, how can I disable EXA and use XAA? I am on opensuse and added the following section to /etc/X11/xorg.conf.d/50-device.conf: Section Device Option AccelMethod xaa Identifier Default Device EndSection Xorg reads the file because it says in its logfile: [ 21.481] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 21.481] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 21.481] (==) RADEON(0): Default visual is TrueColor [ 21.481] (**) RADEON(0): Option AccelMethod xaa [ 21.481] (==) RADEON(0): RGB weight 888 [ 21.481] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 21.481] (--) RADEON(0): Chipset: ATI Radeon Mobility X300 (M22) 5460 (PCIE) (ChipID = 0x5460) [ 21.481] (II) RADEON(0): PCIE card detected But EXA is still used: [ 21.481] (II) Loading sub module exa [ 21.481] (II) LoadModule: exa [ 21.482] (II) Loading /usr/lib/xorg/modules/libexa.so [ 21.488] (II) Module exa: vendor=X.Org Foundation [ 21.488] compiled for 1.10.4, module version = 2.5.0 ... [ 21.575] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM ... [ 21.635] (II) RADEON(0): Setting EXA maxPitchBytes [ 21.635] (II) EXA(0): Driver allocated offscreen pixmaps [ 21.635] (II) EXA(0): Driver registered support for the following operations: [ 21.635] (II) Solid [ 21.635] (II) Copy [ 21.635] (II) Composite (RENDER acceleration) [ 21.635] (II) UploadToScreen [ 21.635] (II) DownloadFromScreen How can I disable EXA and use XAA?. I suspect EXA to be responsible for a huge performance regression. XAA is not compatible with KMS. Alex ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: hdmi output not detected by xrandr
On Tue Nov 29 00:00:34 2011, sashan wrote: On Sun Nov 27 18:51:03 2011, sashan wrote: On Sat Nov 26 22:13:49 2011, Keith Packard wrote: On Sun, 27 Nov 2011 16:01:52 +1100, sashan sas...@zenskg.net wrote: Hi I'm trying to figure out why the external hdmi output on my laptop doesn't work but am not sure where the problem is or if this is the right mailing list. I'd bet money that the hdmi connector is only hooked up to the nVidia device, which means you'd have to use that one to display anything over that connector. Yeah that might be the case but the document http://www.nvidia.com/object/LO_optimus_whitepapers.html about nvidia optimus basically says that the datapath to the physical monitor is always through the Intel IGP and then the IGP is responsible for writing to the display. The nVidia chip is between the application and the IGP, therefore I expected that the IGP would be connected to the HDMI port. However I'm probably wrong and would appreciate if you or someone could clarify my understanding about how this is meant to work. The laptop is a Dell XPS 15z (http://reviews.cnet.com/laptops/dell-xps-15z/4507-3121_7-34714594.html) I've been able to get output from the HDMI port onto the monitor by adding the ModulePath to the nvidia driver to xorg.conf, so it looks like you're right about the fact that it's connected to the nVidia gpu. The problem now is that the higher resolutions aren't detected. The highest it goes is 640x480. I've tried to manually add a modeline but this is ignored. The xorg log shows this when it encounteres the modeline it can't validate: (WW) NVIDIA(0): No valid modes for 1920x1080; removing. Is there anyway I can fix this? I've attached the xorg.conf and xorg log file. Never mind I've got this working. ReadEDID was set to false in the xorg.conf I posted. I deleted that and X is able to correctly detect modelines. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
Am 28.11.2011 10:35, schrieb Christoph Bartoschek:
Now one has to look at
(*pGC-ops-PolyRectangle)(pDrawable, pGC, nRects, pRects);
Here is what I see so far:
- damagePolyRectangle is called for 2044 rectangles.
- the damage region is computed it consists of about 1000 rectangles
each time.
- miPolyRectangle is called.
- the function iterates over all rectangles and calls exaPolylines for
each of them because most have only a width and height of 0
- exaPolylines calls ExaCheckPolylines.
We see that for each rectanlge ExaCheckPolylines is called. I have added
timers to this function to see what costs time:
void
ExaCheckPolylines (DrawablePtr pDrawable, GCPtr pGC,
int mode, int npt, DDXPointPtr ppt)
{
EXA_PRE_FALLBACK_GC(pGC);
EXA_FALLBACK((to %p (%c), width %d, mode %d, count %d\n,
pDrawable, exaDrawableLocation(pDrawable),
pGC-lineWidth, mode, npt));
exaPrepareAccess (pDrawable, EXA_PREPARE_DEST); // Step1: 55 s
exaPrepareAccessGC (pGC); // Step2: 2.4 s
pGC-ops-Polylines (pDrawable, pGC, mode, npt, ppt); // Step3: 2.4 s
exaFinishAccessGC (pGC); // Step4: 2.2 s
exaFinishAccess (pDrawable, EXA_PREPARE_DEST);// Step5: 2.2 s
EXA_POST_FALLBACK_GC(pGC);
}
We see that exaPrepareAccess needs most of the time. Is that expected?
Inside we see that there are some region operations on the damage region
in exaCopyDirty. As said before the damage region contains about 1000
rectangles. So we have 2000 times several operations on 1000 rectangeles.
I think this explains the runtime.
Isn't it somehow possible to batch the rectangle drawing such that the
region operations are not neccessary for each rectangle?
Isn't is possible to expand the damage region such that it contains less
rectangles?
Is this still the correct list, or should I ask the EXA questions elsewhere?
Christoph
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xf86-video-ati 6.14.3
snip * vdpau/XvMC support (currently only available for = R3xx via Gallium3D). /snip How can i test this? Do I need to configure something? Is there a way to check if this works? Hardware: fusion e350 in lenovo x121e ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
On Mon, Nov 28, 2011 at 4:49 PM, Christoph Bartoschek
bartosc...@or.uni-bonn.de wrote:
Am 28.11.2011 10:35, schrieb Christoph Bartoschek:
Now one has to look at
(*pGC-ops-PolyRectangle)(pDrawable, pGC, nRects, pRects);
Here is what I see so far:
- damagePolyRectangle is called for 2044 rectangles.
- the damage region is computed it consists of about 1000 rectangles each
time.
- miPolyRectangle is called.
- the function iterates over all rectangles and calls exaPolylines for each
of them because most have only a width and height of 0
- exaPolylines calls ExaCheckPolylines.
We see that for each rectanlge ExaCheckPolylines is called. I have added
timers to this function to see what costs time:
void
ExaCheckPolylines (DrawablePtr pDrawable, GCPtr pGC,
int mode, int npt, DDXPointPtr ppt)
{
EXA_PRE_FALLBACK_GC(pGC);
EXA_FALLBACK((to %p (%c), width %d, mode %d, count %d\n,
pDrawable, exaDrawableLocation(pDrawable),
pGC-lineWidth, mode, npt));
exaPrepareAccess (pDrawable, EXA_PREPARE_DEST); // Step1: 55 s
exaPrepareAccessGC (pGC); // Step2: 2.4 s
pGC-ops-Polylines (pDrawable, pGC, mode, npt, ppt); // Step3: 2.4 s
exaFinishAccessGC (pGC); // Step4: 2.2 s
exaFinishAccess (pDrawable, EXA_PREPARE_DEST); // Step5: 2.2 s
EXA_POST_FALLBACK_GC(pGC);
}
We see that exaPrepareAccess needs most of the time. Is that expected?
Inside we see that there are some region operations on the damage region in
exaCopyDirty. As said before the damage region contains about 1000
rectangles. So we have 2000 times several operations on 1000 rectangeles.
I think this explains the runtime.
Isn't it somehow possible to batch the rectangle drawing such that the
region operations are not neccessary for each rectangle?
Isn't is possible to expand the damage region such that it contains less
rectangles?
Is this still the correct list, or should I ask the EXA questions elsewhere?
Christoph
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: madman2...@gmail.com
EXA doesn't have a seperate list, but now that you ask, you should
probably move to the xorg-devel mailinglist :-)
I don't have any answers right now, but i'll think about it.
--
Far away from the primal instinct, the song seems to fade away, the
river get wider between your thoughts and the things we do and say.
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xorg-server 1.11.99.1
On Sun, Nov 20, 2011 at 03:20:11PM -0800, Keith Packard wrote: We discussed doing regular releases from master, and Jeremy suggested (sensibly) that we just do them whenever there's a stable release. I completely spaced that plan, nor was I looking at the Google X.org calendar. In any case, here's the current state of master. It's missing a pull request from alanc -- there were a couple of build failures in that which I've replied back about and I expect that'll be fixed shortly. For those interested in helping out, here's the 1.12 release tracker. https://bugs.freedesktop.org/show_bug.cgi?id=40982 Anyone interested in helping clean up the release is encouraged to take a look at the outstanding bugs there. There's a slight snag about the 1.12 release schedule. I'm going biking in New Zealand next February, leaving on the 9th and not getting back until March 1st. So, we can either have the release done before I leave, or wait until I get back. It seems like the former might work a bit better, but it would mean pulling the release in to Feb 8th or so. Anyone have an opinion on the matter? We probably won't get X Input 2.2 done if the release is moved forward to Feb 8th. What's the date for the merge window end? Cheers, Peter ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
Re: [ANNOUNCE] xorg-server 1.11.99.1
On Sun, Nov 27, 2011 at 07:29:53PM -0800, Keith Packard wrote: On Mon, 28 Nov 2011 11:39:31 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: We probably won't get X Input 2.2 done if the release is moved forward to Feb 8th. What's the date for the merge window end? If we followed the 1.11 schedule, the non-critical bug window would close three weeks earlier (Jan 18), and the merge window two months before that (Nov 18), which is now nine days past... If you think X Input 2.2 is nearly ready for merging , I'd say we should go for it and get that merged by Christmas, then plan on closing the non-critical bug window in the first week of February and then finish the release in the first week of March. If you don't think X Input 2.2 will be ready by then, we should probably just close out the merge window earlier, and plan on getting the release out the door by the time I go biking. I think Christmas is realistic for the merge. We're quite some way there, but pointer emulation and the resulting grab hilarity is still missing (Chase has worked on this while I was away but I haven't looked at the current state yet) Cheers, Peter ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
Re: [ANNOUNCE] xorg-server 1.11.99.1
On Mon, 28 Nov 2011 13:36:35 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: On Sun, Nov 27, 2011 at 07:29:53PM -0800, Keith Packard wrote: On Mon, 28 Nov 2011 11:39:31 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: We probably won't get X Input 2.2 done if the release is moved forward to Feb 8th. What's the date for the merge window end? If we followed the 1.11 schedule, the non-critical bug window would close three weeks earlier (Jan 18), and the merge window two months before that (Nov 18), which is now nine days past... If you think X Input 2.2 is nearly ready for merging , I'd say we should go for it and get that merged by Christmas, then plan on closing the non-critical bug window in the first week of February and then finish the release in the first week of March. If you don't think X Input 2.2 will be ready by then, we should probably just close out the merge window earlier, and plan on getting the release out the door by the time I go biking. I think Christmas is realistic for the merge. We're quite some way there, but pointer emulation and the resulting grab hilarity is still missing (Chase has worked on this while I was away but I haven't looked at the current state yet) I'd say we should go for it then. I'll plan on checking my inbox for critical patches while I'm on my bike trip, but we haven't had a lot of patches in that window in the past, so I don't expect things to back up much. -- keith.pack...@intel.com pgpdxJNZCUWBM.pgp Description: PGP signature ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
Re: EXA performance problem
On Sun, Nov 27, 2011 at 3:55 PM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: Hi, I still have a huge performance problem with Xorg. One application that painted 2 Mio rectangles on the screen within a second or so with XFree86 needs about a minute with Xorg. Most of the time is spent in libpixman. I've added some debug statements and see that pixman_raster_op is called about 7.2 mio times during my testcase. I do not think that pixman itself is the problem. It is just used too often by EXA. Is there anything I can do about this? Is there a better list where I can ask? Or do you know a person that might be interested in solving such a problem? Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com As far as i know it basically boils down to this, rendering rectangles is done in a software library as you observed. If your pixmap happens to be outside normal ram then a lot of reads will kill performance. These days the aim should be to use as little core rendering as possible. A modern toolkit or a rendering library like cairo should handle this far better. -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
On Sun, 27 Nov 2011 15:55:12 +0100, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: Hi, I still have a huge performance problem with Xorg. One application that painted 2 Mio rectangles on the screen within a second or so with XFree86 needs about a minute with Xorg. The easiest way for anyone else to reproduce this issue would be if you were to identify the most common slow op and translate that into the appropriate x11perf command line. -Chris -- Chris Wilson, Intel Open Source Technology Centre ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
Am 27.11.2011 16:13, schrieb Maarten Maathuis: On Sun, Nov 27, 2011 at 3:55 PM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: Hi, I still have a huge performance problem with Xorg. One application that painted 2 Mio rectangles on the screen within a second or so with XFree86 needs about a minute with Xorg. Most of the time is spent in libpixman. I've added some debug statements and see that pixman_raster_op is called about 7.2 mio times during my testcase. I do not think that pixman itself is the problem. It is just used too often by EXA. Is there anything I can do about this? Is there a better list where I can ask? Or do you know a person that might be interested in solving such a problem? Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com As far as i know it basically boils down to this, rendering rectangles is done in a software library as you observed. If your pixmap happens to be outside normal ram then a lot of reads will kill performance. These days the aim should be to use as little core rendering as possible. A modern toolkit or a rendering library like cairo should handle this far better. How can I check whether the pixmap is outside the normal ram? For me it does not look as if pixman is used for rendering the image. It looks as if EXA is managing the region that needs updates with pixman routines. But I could be wrong here. Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
On Sun, Nov 27, 2011 at 9:40 PM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: Am 27.11.2011 16:13, schrieb Maarten Maathuis: On Sun, Nov 27, 2011 at 3:55 PM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: Hi, I still have a huge performance problem with Xorg. One application that painted 2 Mio rectangles on the screen within a second or so with XFree86 needs about a minute with Xorg. Most of the time is spent in libpixman. I've added some debug statements and see that pixman_raster_op is called about 7.2 mio times during my testcase. I do not think that pixman itself is the problem. It is just used too often by EXA. Is there anything I can do about this? Is there a better list where I can ask? Or do you know a person that might be interested in solving such a problem? Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com As far as i know it basically boils down to this, rendering rectangles is done in a software library as you observed. If your pixmap happens to be outside normal ram then a lot of reads will kill performance. These days the aim should be to use as little core rendering as possible. A modern toolkit or a rendering library like cairo should handle this far better. How can I check whether the pixmap is outside the normal ram? For me it does not look as if pixman is used for rendering the image. It looks as if EXA is managing the region that needs updates with pixman routines. But I could be wrong here. Christoph Only the driver knows that. If you know what driver it is, you can also figure out if the driver handles pixmap allocation themselves. Then you can see if they (are likely) to use dedicated video ram, which is the only uncached memory (=slow read) i can think of right now. I don't know off the top of my head how to determine if a pixmap is offscreen (for a driver that allocates pixmaps this means that the pixmap is under driver control, the alternative is that it's a malloc private to exa). -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: What will happen when the X server doesn't support XKB(XKEYBOARD)
On Mon, Nov 21, 2011 at 07:35:21PM +0800, Adam Q wrote: There is a X server for win32 which doesn't support XKB extension(I know it's unbelievable). There is something strange when I try to use the gnome-keyboard-properties and system-config-keyboard to change the X server's keyboard layout. When using gnome-keyboard-properties,the input of keyboard goes crazy and can't be used. When using system-config-keyboard the CLI just prints something like XKB extension unsupported and nothing changed including the keyboard layout. I tested serveral X server from the latest Xorg server in Arch and some old Xorg server in RHEL5.6/5.5 also with latest cygwin/X. All the servers I tested above can change the keyboard using these 2 GUI. I assume the problem is the lack of XKB extension but without XKB extension,the client should just send a lot of ChangeKeyboardLayout requests (and wireshark shows it really sends) to X server,and the layout should change even without the XKB extension and no crazy keyboard. How can I determine where the problem really is? possibly with xmodmap to get the keyboard mapping before/after and maybe xscope or something to snoop the protocol traffic. though a server without XKB support is not really high on the priority list for server or client developers and I expect this to be a rather untested scenario. Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
I have new information. I am no longer sure whether it is a problem with EXA. I have a testcase that currently takes 90 seconds to draw all rectangles. I see that in damage.c two functions are mainly used: damagePolyRectangle damagePolyFillRectangle The first function calls for each given rectangle up to four times damageDamageBox (pDrawable, box, pGC-subWindowMode); which adds the box to a region. The function then calls damageRegionAppend. This part takes in sum 30 seconds of my testcase. I think the code has quadratic behaviour here becuase it adds rectangle by rectangle instead of first adding them to a region and then calling damageRegionAppend. I think removing the quadratic behaviour can reduce the runtime significantly. About 60 seconds are spent in the calls (*pGC-ops-PolyRectangle)(pDrawable, pGC, nRects, pRects); (*pGC-ops-PolyFillRect)(pDrawable, pGC, nRects, pRects); However I do not yet know why they are so slow. Is damage.c part of EXA? Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xorg-server 1.11.99.1
On Mon, 28 Nov 2011 11:39:31 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: We probably won't get X Input 2.2 done if the release is moved forward to Feb 8th. What's the date for the merge window end? If we followed the 1.11 schedule, the non-critical bug window would close three weeks earlier (Jan 18), and the merge window two months before that (Nov 18), which is now nine days past... If you think X Input 2.2 is nearly ready for merging , I'd say we should go for it and get that merged by Christmas, then plan on closing the non-critical bug window in the first week of February and then finish the release in the first week of March. If you don't think X Input 2.2 will be ready by then, we should probably just close out the merge window earlier, and plan on getting the release out the door by the time I go biking. -- keith.pack...@intel.com pgpbqiHoUCd8C.pgp Description: PGP signature ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xorg-server 1.11.99.1
On Sun, Nov 27, 2011 at 07:29:53PM -0800, Keith Packard wrote: On Mon, 28 Nov 2011 11:39:31 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: We probably won't get X Input 2.2 done if the release is moved forward to Feb 8th. What's the date for the merge window end? If we followed the 1.11 schedule, the non-critical bug window would close three weeks earlier (Jan 18), and the merge window two months before that (Nov 18), which is now nine days past... If you think X Input 2.2 is nearly ready for merging , I'd say we should go for it and get that merged by Christmas, then plan on closing the non-critical bug window in the first week of February and then finish the release in the first week of March. If you don't think X Input 2.2 will be ready by then, we should probably just close out the merge window earlier, and plan on getting the release out the door by the time I go biking. I think Christmas is realistic for the merge. We're quite some way there, but pointer emulation and the resulting grab hilarity is still missing (Chase has worked on this while I was away but I haven't looked at the current state yet) Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xorg-server 1.11.99.1
On Mon, 28 Nov 2011 13:36:35 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: On Sun, Nov 27, 2011 at 07:29:53PM -0800, Keith Packard wrote: On Mon, 28 Nov 2011 11:39:31 +1000, Peter Hutterer peter.hutte...@who-t.net wrote: We probably won't get X Input 2.2 done if the release is moved forward to Feb 8th. What's the date for the merge window end? If we followed the 1.11 schedule, the non-critical bug window would close three weeks earlier (Jan 18), and the merge window two months before that (Nov 18), which is now nine days past... If you think X Input 2.2 is nearly ready for merging , I'd say we should go for it and get that merged by Christmas, then plan on closing the non-critical bug window in the first week of February and then finish the release in the first week of March. If you don't think X Input 2.2 will be ready by then, we should probably just close out the merge window earlier, and plan on getting the release out the door by the time I go biking. I think Christmas is realistic for the merge. We're quite some way there, but pointer emulation and the resulting grab hilarity is still missing (Chase has worked on this while I was away but I haven't looked at the current state yet) I'd say we should go for it then. I'll plan on checking my inbox for critical patches while I'm on my bike trip, but we haven't had a lot of patches in that window in the past, so I don't expect things to back up much. -- keith.pack...@intel.com pgp5iObDYmU22.pgp Description: PGP signature ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
On Mon, Nov 28, 2011 at 2:41 AM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: I have new information. I am no longer sure whether it is a problem with EXA. I have a testcase that currently takes 90 seconds to draw all rectangles. I see that in damage.c two functions are mainly used: damagePolyRectangle damagePolyFillRectangle The first function calls for each given rectangle up to four times damageDamageBox (pDrawable, box, pGC-subWindowMode); which adds the box to a region. The function then calls damageRegionAppend. This part takes in sum 30 seconds of my testcase. I think the code has quadratic behaviour here becuase it adds rectangle by rectangle instead of first adding them to a region and then calling damageRegionAppend. I think removing the quadratic behaviour can reduce the runtime significantly. About 60 seconds are spent in the calls (*pGC-ops-PolyRectangle)(pDrawable, pGC, nRects, pRects); (*pGC-ops-PolyFillRect)(pDrawable, pGC, nRects, pRects); However I do not yet know why they are so slow. Is damage.c part of EXA? Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com No, damage is an extention, it is called by EXA, it's probably adding all you rectangles to a damage region used to determine how much data is actually valid (needed for ram--vram migrations for example). One thing that just comes to mind, if you are rendering a million rectangles, how many of those do you actually see on your screen? Anyway, you can try optimizing damaga, exa and either fb or mi (for PolyRectangle PolyFillRect software ops). I don't know how efficient the region code is at reducing the number of rectangles if they overlap, a region is built up out of rectangles as well. -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: EXA performance problem
On Mon, Nov 28, 2011 at 7:43 AM, Maarten Maathuis madman2...@gmail.com wrote: On Mon, Nov 28, 2011 at 2:41 AM, Christoph Bartoschek bartosc...@or.uni-bonn.de wrote: I have new information. I am no longer sure whether it is a problem with EXA. I have a testcase that currently takes 90 seconds to draw all rectangles. I see that in damage.c two functions are mainly used: damagePolyRectangle damagePolyFillRectangle The first function calls for each given rectangle up to four times damageDamageBox (pDrawable, box, pGC-subWindowMode); which adds the box to a region. The function then calls damageRegionAppend. This part takes in sum 30 seconds of my testcase. I think the code has quadratic behaviour here becuase it adds rectangle by rectangle instead of first adding them to a region and then calling damageRegionAppend. I think removing the quadratic behaviour can reduce the runtime significantly. About 60 seconds are spent in the calls (*pGC-ops-PolyRectangle)(pDrawable, pGC, nRects, pRects); (*pGC-ops-PolyFillRect)(pDrawable, pGC, nRects, pRects); However I do not yet know why they are so slow. Is damage.c part of EXA? Christoph ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: madman2...@gmail.com No, damage is an extention, it is called by EXA, it's probably adding all you rectangles to a damage region used to determine how much data is actually valid (needed for ram--vram migrations for example). One thing that just comes to mind, if you are rendering a million rectangles, how many of those do you actually see on your screen? Anyway, you can try optimizing damaga, exa and either fb or mi (for PolyRectangle PolyFillRect software ops). I don't know how efficient the region code is at reducing the number of rectangles if they overlap, a region is built up out of rectangles as well. -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. s/damaga/damage and s/extention/extension and s/you rectangles/your rectangles It was too early in the morning :-) -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: hdmi output not detected by xrandr
On Sun, 27 Nov 2011 16:01:52 +1100, sashan sas...@zenskg.net wrote: Hi I'm trying to figure out why the external hdmi output on my laptop doesn't work but am not sure where the problem is or if this is the right mailing list. I'd bet money that the hdmi connector is only hooked up to the nVidia device, which means you'd have to use that one to display anything over that connector. -- keith.pack...@intel.com pgpO0ePXw16ja.pgp Description: PGP signature ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: hdmi output not detected by xrandr
On Sat Nov 26 22:13:49 2011, Keith Packard wrote: On Sun, 27 Nov 2011 16:01:52 +1100, sashan sas...@zenskg.net wrote: Hi I'm trying to figure out why the external hdmi output on my laptop doesn't work but am not sure where the problem is or if this is the right mailing list. I'd bet money that the hdmi connector is only hooked up to the nVidia device, which means you'd have to use that one to display anything over that connector. Yeah that might be the case but the document http://www.nvidia.com/object/LO_optimus_whitepapers.html about nvidia optimus basically says that the datapath to the physical monitor is always through the Intel IGP and then the IGP is responsible for writing to the display. The nVidia chip is between the application and the IGP, therefore I expected that the IGP would be connected to the HDMI port. However I'm probably wrong and would appreciate if you or someone could clarify my understanding about how this is meant to work. The laptop is a Dell XPS 15z (http://reviews.cnet.com/laptops/dell-xps-15z/4507-3121_7-34714594.html) ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Cannot setup dual monitors
Sorry! I got that to work. I had not installed mesa-utils. This seemed to solve this problem. However, my graphics is quite slow. Text scrolls slowly in Iceweasel. I checked glxgears and got only 400fps in windowed view and about 50fps in full screen. All this time, my processor utilzation is only 20%. So, Its not a processor problem. I tried removing xorg.conf, - I get the same performance. Can I edit xorg.conf and add in special statements to help speedup my graphics? Thanks Githin On 11/23/11, Githin Alapatt git...@gmail.com wrote: Hello, I recently upgraded from lenny to squeeze and I no longer can get my external monitor working correctly on my laptop. lspci gives these 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) lsmod gives: githin@debian-githin:~$ lsmod Module Size Used by parport_pc 15799 0 ppdev 4058 0 lp 5570 0 parport22554 3 parport_pc,ppdev,lp acpi_cpufreq4951 1 cpufreq_conservative 4018 0 cpufreq_powersave602 0 cpufreq_stats 1997 0 cpufreq_userspace 1480 0 rfcomm 25199 0 sco 5885 2 bridge 33031 0 stp 996 1 bridge bnep7452 2 l2cap 21721 6 rfcomm,bnep crc16 1027 1 l2cap bluetooth 36319 6 rfcomm,sco,bnep,l2cap uinput 4796 1 fuse 44268 3 arc4 974 2 ecb 1405 2 b43 132615 0 ssb33714 1 b43 pcmcia 16194 2 b43,ssb rng_core2178 1 b43 mac80211 123586 1 b43 cfg80211 87637 2 b43,mac80211 pcmcia_core20450 3 b43,ssb,pcmcia firewire_sbp2 9647 0 loop9769 0 joydev 6739 0 snd_hda_codec_idt 35329 1 snd_hda_codec_intelhdmi 9027 1 snd_hda_intel 16823 1 snd_hda_codec 46002 3 snd_hda_codec_idt,snd_hda_codec_intelhdmi,snd_hda_intel snd_hwdep 4054 1 snd_hda_codec snd_pcm_oss28671 0 snd_mixer_oss 10461 1 snd_pcm_oss snd_pcm47226 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi3576 0 snd_rawmidi12513 1 snd_seq_midi snd_seq_midi_event 3684 1 snd_seq_midi snd_seq35463 2 snd_seq_midi,snd_seq_midi_event snd_timer 12270 2 snd_pcm,snd_seq snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq i915 223022 0 drm_kms_helper 18569 1 i915 uvcvideo 45554 0 drm 111992 2 i915,drm_kms_helper i2c_algo_bit3497 1 i915 videodev 25605 1 uvcvideo dell_laptop 1557 0 rfkill 10264 4 bluetooth,cfg80211,dell_laptop i2c_i8016462 0 dcdbas 3892 1 dell_laptop v4l1_compat10250 2 uvcvideo,videodev snd34423 14 snd_hda_codec_idt,snd_hda_codec_intelhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device wmi 3575 0 button 3598 1 i915 i2c_core 12787 6 i915,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801 pcspkr 1207 0 psmouse44809 0 evdev 5609 17 serio_raw 2916 0 battery 3782 0 video 14605 1 i915 output 1204 1 video soundcore 3450 1 snd ac 1640 0 snd_page_alloc 5045 2 snd_hda_intel,snd_pcm processor 26327 3 acpi_cpufreq ext3 94396 2 jbd32317 1 ext3 mbcache 3762 1 ext3 sg 19937 0 sr_mod 10770 0 cdrom 26487 1 sr_mod sd_mod 26005 5 crc_t10dif 1012 1 sd_mod ata_generic 2247 0 uhci_hcd 16057 0 ahci 27410 4 sdhci_pci 4581 0 sdhci 12171 1 sdhci_pci mmc_core 38685 3 b43,ssb,sdhci ricoh_mmc 2561 0 led_class 1757 2 b43,sdhci firewire_ohci 16725 0 firewire_core 31243 2 firewire_sbp2,firewire_ohci crc_itu_t 1035 1 firewire_core ata_piix 17736 0 ehci_hcd 28693 0 sky2 34040 0 libata115869 3 ata_generic,ahci,ata_piix scsi_mod 104853 5
RE: The PCI device 0x10de087d (ION) at 02@00:00:0 has a kernel module claiming it.
Thanks for reply, as you told there is nouveau driver block my driver. Is this possible to unload it? All the best, Anatolii Ivashyna -Original Message- From: Aaron Plattner [mailto:aplatt...@nvidia.com] Sent: Tuesday, November 22, 2011 6:43 PM To: Anatolii Ivashyna Cc: x...@freedesktop.org Subject: Re: The PCI device 0x10de087d (ION) at 02@00:00:0 has a kernel module claiming it. Check the output of lsmod for modules that can claim that device. It's probably either nvidia or nouveau. I think you can find out for sure by running readlink /sys/bus/pci/devices/:02:00.0/driver Unload the conflicting driver and try again. On 11/22/2011 02:58 AM, Anatolii Ivashyna wrote: Hi all, I use ION nettop, and have this message in boot.log when using xorg7-nv driver. Linux: Thinstation, kernel ver: 3.0.9TS Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 22 12:48:34 2011 (++) Using config file: /etc/X11/x.config-0 (==) Using config directory: /etc/X11/xorg.conf.d (EE) NV: The PCI device 0x10de087d (ION) at 02@00:00:0 has a kernel module claiming it. (EE) NV: This driver cannot operate until it has been unloaded. (EE) No devices detected. Please help! *All the best,* *Anatolii Ivashyna* ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: The PCI device 0x10de087d (ION) at 02@00:00:0 has a kernel module claiming it.
On Wed, Nov 23, 2011 at 4:48 AM, Anatolii Ivashyna t...@aurora.com.ua wrote: Thanks for reply, as you told there is nouveau driver block my driver. Is this possible to unload it? All the best, Anatolii Ivashyna Is it not possible to just use the nouveau driver instead of nv? nv is pretty much unmaintained at this point, but nouveau is supported by the nouveau team, and more importantly, your distro apparently supports nouveau too. ~ C. -- When the facts change, I change my mind. What do you do, sir? ~ Keynes Corbin Simpson mostawesomed...@gmail.com ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Failed to compile keymap using ptxdist
thing is i cant find xkbcomp in menuconfig or kernelconfig.. i searched through.. is there an easy way to identify where the packages menu entry would be? [Wilson Wingston Sharon] On Mon, Nov 21, 2011 at 1:30 PM, Dirk Wallenstein hals...@t-online.de wrote: On Fri, Nov 18, 2011 at 02:09:17PM +0530, Wingston Sharon wrote: I'm using the pengutronix ptxdist BSP for the mini2440 and i wanted to set up an xwindow system. but got this error.. when trying to start Xorg.. i have enabled anxkeymap entry in menuconfig but i cant find a keymap entry in eithermenuconfig or kernelconfig.doing a ptxdist clean xorg and then ptxdist go doesnt help either.. asin ptxdist says that theres nothing to be done for world. (==) Logfile: /var/log/Xorg.0.log, Time: Thu Oct 2 23:41:35 2008(==) Using config file: /etc/X11/xorg.conf(==) Using system config directory/usr/lib/X11/xorg.conf.dsh: /usr/bin/xkbcomp: not found(EE) Error compiling keymap (server-0)(EE) XKB: Couldn't compile Sounds like you need to install xkbcomp. keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be amissing or incorrect setup of x. Fatal server error: Failed to activate core devices.-doing a little more digging around i came across the xorg -configureoption.. this though gives me this little gem of knowledge.. root@mini2440:~ Xorg -configure X.Org X Server 1.9.3Release Date: 2010-12-13X Protocol Version 11, Revision 0Build Operating System:Linux- PtxdistCurrent Operating System: Linux mini2440 3.1.1-ptx-2011.11.0 #0 PREEMPT Fri NovlKernel command line: console=ttySAC0,115200 mini2440=6tbc ip=192.168.1.2:192.16)Build Date: 18 November 2011 11:37:52AM Current version of pixman: 0.21.2 Before reporting problems, check http://www.pengutronix.de/software/ptxl to make sure that you have the latest version.Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown.(==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 2 23:53:52 2008List ofvideo drivers: dummy v4l fbdev No devices to configure. Configuration failed. ---i gues my device is fbdev.. but i'm stumped how i would be able to getit to configure the xorg.config file.[Wilson Wingston Sharon] -- Cheers, Dirk ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: The PCI device 0x10de087d (ION) at 02@00:00:0 has a kernel module claiming it.
Check the output of lsmod for modules that can claim that device. It's probably either nvidia or nouveau. I think you can find out for sure by running readlink /sys/bus/pci/devices/:02:00.0/driver Unload the conflicting driver and try again. On 11/22/2011 02:58 AM, Anatolii Ivashyna wrote: Hi all, I use ION nettop, and have this message in boot.log when using xorg7-nv driver. Linux: Thinstation, kernel ver: 3.0.9TS Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 22 12:48:34 2011 (++) Using config file: /etc/X11/x.config-0 (==) Using config directory: /etc/X11/xorg.conf.d (EE) NV: The PCI device 0x10de087d (ION) at 02@00:00:0 has a kernel module claiming it. (EE) NV: This driver cannot operate until it has been unloaded. (EE) No devices detected. Please help! *All the best,* *Anatolii Ivashyna* ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Failed to compile keymap using ptxdist
On Fri, Nov 18, 2011 at 02:09:17PM +0530, Wingston Sharon wrote: I'm using the pengutronix ptxdist BSP for the mini2440 and i wanted to set up an xwindow system. but got this error.. when trying to start Xorg.. i have enabled anxkeymap entry in menuconfig but i cant find a keymap entry in eithermenuconfig or kernelconfig.doing a ptxdist clean xorg and then ptxdist go doesnt help either.. asin ptxdist says that theres nothing to be done for world. (==) Logfile: /var/log/Xorg.0.log, Time: Thu Oct 2 23:41:35 2008(==) Using config file: /etc/X11/xorg.conf(==) Using system config directory/usr/lib/X11/xorg.conf.dsh: /usr/bin/xkbcomp: not found(EE) Error compiling keymap (server-0)(EE) XKB: Couldn't compile Sounds like you need to install xkbcomp. keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be amissing or incorrect setup of x. Fatal server error: Failed to activate core devices.-doing a little more digging around i came across the xorg -configureoption.. this though gives me this little gem of knowledge.. root@mini2440:~ Xorg -configure X.Org X Server 1.9.3Release Date: 2010-12-13X Protocol Version 11, Revision 0Build Operating System:Linux- PtxdistCurrent Operating System: Linux mini2440 3.1.1-ptx-2011.11.0 #0 PREEMPT Fri NovlKernel command line: console=ttySAC0,115200 mini2440=6tbc ip=192.168.1.2:192.16)Build Date: 18 November 2011 11:37:52AM Current version of pixman: 0.21.2 Before reporting problems, check http://www.pengutronix.de/software/ptxl to make sure that you have the latest version.Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown.(==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 2 23:53:52 2008List ofvideo drivers: dummy v4l fbdev No devices to configure. Configuration failed. ---i gues my device is fbdev.. but i'm stumped how i would be able to getit to configure the xorg.config file.[Wilson Wingston Sharon] -- Cheers, Dirk ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Failed to compile keymap using ptxdist
On Mon, Nov 21, 2011 at 01:43:05PM +0530, Wingston Sharon wrote: thing is i cant find xkbcomp in menuconfig or kernelconfig.. i searched through.. is there an easy way to identify where the packages menu entry would be? [Wilson Wingston Sharon] Sorry, I don't know pengutronix ptxdist BSP. Best ask at ptxdist.org. On Mon, Nov 21, 2011 at 1:30 PM, Dirk Wallenstein hals...@t-online.de wrote: On Fri, Nov 18, 2011 at 02:09:17PM +0530, Wingston Sharon wrote: I'm using the pengutronix ptxdist BSP for the mini2440 and i wanted to set up an xwindow system. but got this error.. when trying to start Xorg.. i have enabled anxkeymap entry in menuconfig but i cant find a keymap entry in eithermenuconfig or kernelconfig.doing a ptxdist clean xorg and then ptxdist go doesnt help either.. asin ptxdist says that theres nothing to be done for world. (==) Logfile: /var/log/Xorg.0.log, Time: Thu Oct 2 23:41:35 2008(==) Using config file: /etc/X11/xorg.conf(==) Using system config directory/usr/lib/X11/xorg.conf.dsh: /usr/bin/xkbcomp: not found(EE) Error compiling keymap (server-0)(EE) XKB: Couldn't compile Sounds like you need to install xkbcomp. keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be amissing or incorrect setup of x. Fatal server error: Failed to activate core devices.-doing a little more digging around i came across the xorg -configureoption.. this though gives me this little gem of knowledge.. root@mini2440:~ Xorg -configure X.Org X Server 1.9.3Release Date: 2010-12-13X Protocol Version 11, Revision 0Build Operating System:Linux- PtxdistCurrent Operating System: Linux mini2440 3.1.1-ptx-2011.11.0 #0 PREEMPT Fri NovlKernel command line: console=ttySAC0,115200 mini2440=6tbc ip=192.168.1.2:192.16)Build Date: 18 November 2011 11:37:52AM Current version of pixman: 0.21.2 Before reporting problems, check http://www.pengutronix.de/software/ptxl to make sure that you have the latest version.Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown.(==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 2 23:53:52 2008List ofvideo drivers: dummy v4l fbdev No devices to configure. Configuration failed. ---i gues my device is fbdev.. but i'm stumped how i would be able to getit to configure the xorg.config file.[Wilson Wingston Sharon] -- Cheers, Dirk -- Cheers, Dirk ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Problem: After exiting X-intel, console command line wraps around
On Nov 19, 2011 9:45 PM, al...@verizon.net wrote: Hello, System: (B)LFS, i686-pc-linux-gnu, kernel-3.1.0, Udev-173, Xorg-7.6 xorg-server-1.11.2 xf86-video-intel-2.17.0 xf86-input-keyboard-1.6.0 (not used - for reference) xf86-input-mouse-1.7.1(not used - for reference) xf86-input-evdev-2.6.0 xf86-video-vesa-2.3.0 xterm-276 Board: ASUS P5E-VM HDMI with Intel G35/ICH9R Monitor: Samsung SM2494, Wide (16:9), DVI input (HDMI-DVI cable) SEQUENCE OF STEPS LEADING TO THE PROBLEM 1. Reboot to command line (as opposed to graphics) 2. startx ~/xterm # go to X using the intel driver 3. exit # Exit X to command line 4. PROBLEM: command line wraps around now (i.e., doesn't go to next line if text reaches end, as would normally happen) COMMENTS A. Unlike the (default) intel driver above, the vesa driver doesn't exhibit problem (4) B. The wrap-around problem doesn't change back to normal unless/until B1. At (4) one logouts and logs back in B2. At (4) one types TERM=linux # Strange (see C below) C. echo $TERM - linux at _all_ times (in command/text mode) D. echo $TERM - xterm-color (in X) E. 'setterm -linewrap on|off' doesn't have any effect (like B above, i.e., doesn't restore system to normal) What does $COLUMNS say afterwards? Does stty columns 80 fix it? Dan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Is there any client program which can test what extension the server support?
On Thu, Nov 17, 2011 at 1:36 PM, Adam Q wrote: Sorry for disturbing everyone. May someone tell me is there any client program that can test what extension the X server supports? xdpyinfo Regards, Tormod ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Third level chooser dysfunct in untrusted clients
* Message by -Andreas Wettstein- from Mon 2011-11-14: When I try to load the layout via setxkbmap from the untrusted client, it says that the XKB extension is not available. You could try the pre-XKB way and use an additional group instead of an additional level. xmodmap is easier to use for this than setxkbmap: keysym q = q Q slash keysym space = Mode_switch and so on. Note that even xmodmap must be run from a trusted client. Unfortunately, it's the same with xmodmap. The third-level chooser stops working in untrusted clients. The modmap is loaded from a trusted client and works well then for any trusted client. For untrusted clients, all modifications done by the modmap -- save the third-level chooser! -- also work. I feel that this classifies as a bug. I'll file a formal report soon. pgpfMT8EYNQPW.pgp Description: PGP signature ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: No action for keyboard on YOCTO
On 2011年11月17日 13:07, Xiaofeng Yan wrote: Hi all, I had a trouble with no action for keyboard when running command Xfbdev on qemuarm and OS is yocto, the version is 1.4.4 The version of xserver is 1.11.1, not 1.4.4 The detailed steps are follow: $Xfbdev :0 -keybd keyboard -mouse tslib When I type keys on keyboard, the information on screen are follow: driver Linux console keyboard wanted to post scancode 78 outside of [0, 0]! driver Linux console keyboard wanted to post scancode 55 outside of [0, 0]! .. My configuration for compiling xorg-kdrive is as follow: --enable-composite --enable-kdrive \ --disable-dga --disable-dri --disable-xinerama \ --disable-xf86misc --disable-xf86vidmode \ --disable-xorg --disable-xorgcfg \ --disable-xnest --disable-xvfb \ --disable-xevie --disable-xprint --disable-xtrap \ --disable-dmx --with-xkb-output=/var/lib/xkb\ --with-default-font-path=built-ins \ --enable-tslib --enable-xcalibrate \ --disable-glx \ ac_cv_file__usr_share_X11_sgml_defs_ent=no Who can tell me how to solve this problem? Thanks Yan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Third level chooser dysfunct in untrusted clients
When I try to load the layout via setxkbmap from the untrusted client, it says that the XKB extension is not available. You could try the pre-XKB way and use an additional group instead of an additional level. xmodmap is easier to use for this than setxkbmap: keysym q = q Q slash keysym space = Mode_switch and so on. Note that even xmodmap must be run from a trusted client. Andreas ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Strange problem that might be a hardware malfunction.[Follow up]
On 11/10/2011 09:34 PM, James Richard Tyrer wrote: I had a Radeon 9200 video card which I used for some time. For apparently no reason, it started showing vertical Magenta stripes that are in the frame buffer since they also showed up in a screen shot: http://on.fb.me/sGUVX3 I have a lot of parts sitting around so I tried a Radeon 9250 and things improved. But still similar problems. http://on.fb.me/sGUVX3 Look closely at the icons and the scroll bar. I have the similar Magenta vertical stripes that flicker on when the screen redraws. Also I have green vertical stripes in photographs and dark colors. Any suggestions would be greatly appreciated. I am presuming that it is hardware but it would be a coincidence if two graphics cards had similar issues. I tried another mother board and it made no significant difference. I am using the radeon driver: xf86-video-ati-6.12.4 and Linux 3.0.4 with X.Org 1.7.1. All 32 bit. Thank you for the assistance. I tried the X1650 and it has problems too. I am not facing a simple quandary. Either I have three defective video cards or there is something wrong with the AGP socket on my motherboard. I am going to explore the possibility that the AGP socket is the problem. -- James Tyrer Linux (mostly) From Scratch ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Strange problem that might be a hardware malfunction.
On Fre, 2011-11-11 at 04:00 -0700, James Richard Tyrer wrote: On 11/11/2011 03:07 AM, Michel Dänzer wrote: On Don, 2011-11-10 at 21:34 -0700, James Richard Tyrer wrote: I am using the radeon driver: xf86-video-ati-6.12.4 and Linux 3.0.4 with X.Org 1.7.1. All 32 bit. Please provide the Xorg.0.log file and dmesg output. Files are attached. Thanks, but please always follow up to the mailing list. I'm doing so now. Anyway, I can see a few problems: * X uses the generic vesa driver. Try the radeon driver instead. * The kernel is configured to use radeonfb, which precludes the radeon driver from enabling KMS. This may work, but it's generally recommended to disable radeonfb and enable KMS. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: your mail
On Thu, Nov 10, 2011 at 09:06:10AM -0800, Sebastian Glita wrote:
Hello,
Had 48 hours with no mouse movement since commit
b450efdf95999cad08de23ce069f04a66bdae24b to xorg/driver/xf86-input-evdev
Seems below #endif went one line too far:
@@ -1136,10 +1141,12 @@ EvdevAddRelValuatorClass(DeviceIntPtr device)
for (axis = REL_X; i MAX_VALUATORS axis = REL_MAX; axis++)
{
pEvdev-axis_map[axis] = -1;
+#ifndef HAVE_SMOOTH_SCROLLING
/* We don't post wheel events, so ignore them here too */
if (axis == REL_WHEEL || axis == REL_HWHEEL || axis == REL_DIAL)
continue;
if (!EvdevBitIsSet(pEvdev-rel_bitmask, axis))
+#endif
continue;
pEvdev-axis_map[axis] = i;
i++;
@@ -1168,6 +1175,14 @@ EvdevAddRelValuatorClass(DeviceIntPtr device)
Should be:
+#endif
if (!EvdevBitIsSet(pEvdev-rel_bitmask, axis))
thanks,
s.
Ooops, thanks, I pushed the fix to master,
a9cdb6590cdf72917cdfeb17e2fcc6a110b2c7d1
Cheers,
Peter
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] libXi 1.4.99.1
On 09/11/11 12:16, Peter Hutterer wrote: A month late but I just noticed that I never sent an announcement out for this. libXi is the first snapshot for XI 2.1 support. At this point I consider it unlikely that any major protocol changes will happen to the smooth scrolling support. If you're working on a toolkit or similar, I highly recommend to start using the new stuff while we can still change it to fit your expectations better. Hi, I posted this message 4-Nov-2010: quote In XInput2, when i get a XI_HierarchyChanged event after plugging in another mouse, is there a way to get a unique identifier for each device such as a brand and model number? When i start my program that uses two mice for different functions (one in each hand), it would be useful for them both to be assigned the correct role whenever the program is started, regardless of whatever other devices have been plugged in since the last session. unquote I'm not currently working on mouse stuff, but i will again sometime, and will use more than one pointer device simultaneously for CAD programs. Brand and model number and also the port the pointer is plugged into would be useful, in case both devices are the same model. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] libXi 1.4.99.1
On Wed, Nov 09, 2011 at 07:24:08PM +1100, Russell Shaw wrote: On 09/11/11 12:16, Peter Hutterer wrote: A month late but I just noticed that I never sent an announcement out for this. libXi is the first snapshot for XI 2.1 support. At this point I consider it unlikely that any major protocol changes will happen to the smooth scrolling support. If you're working on a toolkit or similar, I highly recommend to start using the new stuff while we can still change it to fit your expectations better. Hi, I posted this message 4-Nov-2010: quote In XInput2, when i get a XI_HierarchyChanged event after plugging in another mouse, is there a way to get a unique identifier for each device such as a brand and model number? The Device Product ID property contain vendor and product ID (if those are set by the driver). Cheers, Peter When i start my program that uses two mice for different functions (one in each hand), it would be useful for them both to be assigned the correct role whenever the program is started, regardless of whatever other devices have been plugged in since the last session. unquote I'm not currently working on mouse stuff, but i will again sometime, and will use more than one pointer device simultaneously for CAD programs. Brand and model number and also the port the pointer is plugged into would be useful, in case both devices are the same model. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: peter.hutte...@who-t.net ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: savage2 with free radeon drivers on AMD Radeon 6850
On Sat, 2011-11-05 at 19:30 -0500, Alexey I Korepanov wrote: Hello. I found Savage2 in Supported Program List for Free Radeon Drivers ( http://www.x.org/wiki/RadeonProgram ), it has with platinum rating on Northern Islands. I wonder how I make it run on my Radeon 6850. My attempts fail: khu@globalhost ~ $ /opt/Savage2/savage2.bin warning: The VAD has been replaced by a hack pending a complete rewrite Savage2 - Fatal Error: OpenGL 2.0 not available. Segmentation fault Hi, Most likely you need to move the libraries shipped with the game (libgcc, libstdc++ etc) out of the way to make sure it uses the system libraries. You can use the environment variable LIBGL_DEBUG=verbose to get more information in cases like these. I'm not really sure WHY this is necessary though, even new Linux games ships broken like this. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: rotate display
This has been a major thorn in my side with Nvidia. Their driver does not support rotating a single display, it is all or nothing. The work-around is to use Xinerama. I have included the related parts of my config file, monitor 0 is normal and monitors 1 and 2 are rotated. As far as I can tell, both Damage and Composite extensions are not working with Xinerama, but I left the related configuration in the config file, so that if this ever changes, the configuration may be valid. If you wish to use rotation that differs between monitors along with Damage and Composite, you are likely out of luck with the Nvidia driver, and my talks with Nvidia revealed that they are not likely to fix this any time in the near future. -Neil- Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 500 Screen 1 Screen1 1920 0 Screen 2 Screen2 3120 120 Option Xinerama 1 EndSection Section Device Identifier Device0 VendorName NVIDIA Corporation BoardName GeForce GT 440 Driver nvidia BusID PCI:1:0:0 Option backingstore true Option DamageEvents True Option TripleBuffer True Option AllowGLXWithComposite true Option RenderAccel true Screen 0 EndSection Section Device Identifier Device1 VendorName NVIDIA Corporation BoardName GeForce GT 440 Driver nvidia BusID PCI:1:0:0 Option backingstore true Option DamageEvents True Option TripleBuffer True Option AllowGLXWithComposite true Option RenderAccel true Option Rotate left Screen 1 EndSection Section Device Identifier Device2 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce 9500 GT BusID PCI:2:0:0 Option backingstore true Option DamageEvents True Option TripleBuffer True Option AllowGLXWithComposite true Option RenderAccel true Option Rotate left Screen 0 EndSection On Thursday, November 03, 2011 16:45:11 Gergely Buday wrote: Hi, I have my X display as 2560x1024, two monitors in one, so I cannot rotate one of them. How I should modify my xorg.conf so that I can rotate the left one? - Gergely # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 270.41.06 (mockbuild@) Sun May 1 14:42:45 EDT 2011 Section ServerLayout #Screen1 at the right of Screen0 Identifier DualSreen Screen 0 Screen0 0 0 Screen 1 Screen1 RightOf Screen0 InputDeviceKeyboard0 CoreKeyboard InputDeviceMouse0 CorePointer Option TwinView 1 #To move windows between screens EndSection Section InputDevice # generated from data in /etc/sysconfig/keyboard Identifier Keyboard0 Driver keyboard Option XkbLayout us Option XkbModel pc105 EndSection Section InputDevice # generated from default Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/input/mice Option Emulate3Buttons no Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor0 VendorName Unknown ModelName Unknown HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option DPMS EndSection Section Monitor Identifier Monitor1 HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option Enable true EndSection Section Device Identifier Videocard0 Driver nvidia EndSection Section Screen Identifier Screen0 Device Videocard0 MonitorMonitor0 DefaultDepth24 Option TwinView True SubSection Display Depth 24 Modes 1280x800_75.00 EndSubSection EndSection Section Screen Identifier Screen1 Device Videocard0 MonitorMonitor1 DefaultDepth24 Option TwinView True SubSection Display Depth 24 EndSubSection EndSection ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: neil.whelc...@gmail.com ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Simulating a mouse click
Thanks for the help. I was able to fix this now by setting the time member correctly. I had it set to CurrentTime before, but that didn't fix it. Cheers, Markus On 03.11.2011 00:34, Peter Hutterer wrote: On Wed, Nov 02, 2011 at 03:27:42PM +0100, Markus Kramer wrote: Hi, I'm attempting to use xlib to simulate a series of mouse clicks in an application (gedit). I found some posts that describe how to do this and it essentially works. I can do left clicks on buttons and so on. But if I generate a click on the menu bar, a menu opens and something breaks and no further ButtonPress/ButtonRelease events that I send will be processed by the application. When debugging it with xtrace I noticed that my events look slightly different than real left click events. Real: ButtonPress(4) [1]button=left button(0x01) [4]time=0x03752355 [8]root=0x0102 [12]event=0x01a3 [16]child=None(0x) [20]root-x=428 [22]root-y=33 [24]event-x=295 [26]event-y=10 state=0 [30]same-screen=true(0x01) My simulated event: SendEvent [1]propagate=true(0x01) [4]destination=PointerWindow(0x) event-mask=ButtonPress ButtonPress(4) [1]button=left button(0x01) [4]time=0x [8]root=0x0102 [12]event=0x012000a3 [16]child=None(0x) [20]root-x=407 [22]root-y=40 [24]event-x=274 [26]event-y=19 state=0 [30]same-screen=true(0x01) The field event of the real event says 0x01a3 mine is 0x012000a3. What is this event field about? It is not part of the ButtonPress struct. event is the window the event happens on. once you send a button down on a menu, the client usually grabs the device that sent the event and the event window from then on is the grab window, not necessarily the window underneath the cursor. If you're tyring to emulate click events, I recommend to use the XTest extension instead, it's much simpler to handle. Cheers, Peter This is the code that I use to simulate a left click: --- XEvent event; memset(event, 0, sizeof(XEvent)); XWindowAttributes attr; XGetWindowAttributes(dpy, windowId,attr); event.type = ButtonPress; event.xbutton.same_screen = TRUE; event.xbutton.root = root; event.xbutton.window = windowId; event.xbutton.subwindow = None; event.xbutton.x = x; event.xbutton.y = y; event.xbutton.x_root = attr.x + x; event.xbutton.y_root = attr.y + y; event.xbutton.state = 0; event.xbutton.button = Button1; XSendEvent(dpy, PointerWindow, True, ButtonPressMask,event); XFlush(dpy); // the same for ButtonRelease, with modified state and mask -- Thanks in advance. Markus ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: peter.hutte...@who-t.net ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: xrender issue
On Fri, 04 Nov 2011 11:26:07 +0100, Hans-Peter Budek peter.bu...@gmx.de wrote: Hi, if I set an alpha-map to a destination picture via XRenderChangePicture(s-Dpy, Dest, CPAlphaMap, Att) ; the following XRenderComposite() call crash my X-server: Backtrace: [ 9911.289] 0: /usr/X11R6/bin/X (xorg_backtrace+0x37) [0x80e8997] [ 9911.289] Segmentation fault at address (nil) [ 9911.289] Fatal server error: [ 9911.289] Caught signal 11 (Segmentation fault). Server aborting [ 9911.289] [ 9911.289] Please consult the The X.Org Foundation support X.Org X Server 1.9.5 [ 9887.642] (II) Module intel: vendor=X.Org Foundation [ 9887.642] compiled for 1.9.5, module version = 2.14.0 is this a known bug? It is now. I'll have a fix shortly, though you will still be triggering CPU fallbacks. Do you mind describing you use-case for alphamaps and could you create a little benchmark for your workload? -Chris -- Chris Wilson, Intel Open Source Technology Centre ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: xrender issue
On Fri, 04 Nov 2011 15:11:28 +0100, Hans-Peter Budek peter.bu...@gmx.de wrote:
Chris Wilson wrote:
Do you mind describing you use-case for alphamaps and could you create a
little benchmark for your workload?
-Chris
I´am programming a animated crossfade from one window to another.
Both windows are not created by my application. The content
of both windows is previously stored in a ARGB32 picture
(without a usable alpha channel). To apply an alpha channel, I use:
So what I think you want to achieve is:
dst = a * srcA + (1-a) * srcB
which can be acheived (and hitting the accelerated paths) with:
Picture a = XRenderCreateSolidFill(dpy, (XRenderColor){.alpha = 0x *
Fade});
Picture ia = XRenderCreateSolidFill(dpy, (XRenderColor){.alpha = 0x *
(1-Fade)});
XRenderComposite(dpy, PictOpSrc, srcA, a, dst, 0, 0, 0, 0, 0, 0, width,
height);
XRenderComposite(dpy, PictOpAdd, srcB, ia, dst, 0, 0, 0, 0, 0, 0, width,
height);
XRenderFreePicture(dpy, ia);
XRenderFreePicture(dpy, a);
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: xrender issue
Chris Wilson wrote:
Do you mind describing you use-case for alphamaps and could you create a
little benchmark for your workload?
-Chris
I´am programming a animated crossfade from one window to another.
Both windows are not created by my application. The content
of both windows is previously stored in a ARGB32 picture
(without a usable alpha channel). To apply an alpha channel, I use:
uint16_t v = a-Fade * 600 ;
XRenderColor Fade = {.red = v, .green = v, .blue = v, .alpha = v} ;
PixmapMap = XCreatePixmap(s-Dpy, f-Win, 1, 1, 8) ;
XRenderPictFormat *Format8 = XRenderFindStandardFormat(s-Dpy, PictStandardA8) ;
XRenderPictureAttributes Rep = {.repeat = RepeatNormal,
.subwindow_mode = IncludeInferiors} ;
Picture Alpha = XRenderCreatePicture(s-Dpy, Map, Format8,
CPRepeat, Rep) ;
Picture Dest = XRenderCreatePicture(s-Dpy, f-Win,
s-RenderFormat,
CPSubwindowMode, Rep) ;
XRenderPictureAttributes Att = {.alpha_map = Alpha} ;
XRenderFillRectangle(s-Dpy, PictOpSrc, Alpha, Fade, 0, 0, 1, 1) ;
XRenderChangePicture(s-Dpy, a-OldPic, CPAlphaMap, Att) ;
XRenderChangePicture(s-Dpy, a-NewPic, CPAlphaMap, Att) ;
XRenderChangePicture(s-Dpy, Dest, CPAlphaMap, Att) ;
Rendering to 'Dest' cause the described crash (even PictOpClear).
I tried out 'PictStandardARGB32' alpha maps and maps with the same size
as the windows (no 'RepeatNormal'). But that makes no difference.
Unfortunately a copy of a 'PictStandardA8' picture to a 'PictStandardARGB32'
(via PictOpSrc) does not only modifies the alpha values (it also clears the RGB
values).
Peter
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: xrender issue
Hi,
So what I think you want to achieve is:
dst = a * srcA + (1-a) * srcB
yes, that's my intension
which can be acheived (and hitting the accelerated paths) with:
Picture a = XRenderCreateSolidFill(dpy, (XRenderColor){.alpha = 0x *
Fade});
Picture ia = XRenderCreateSolidFill(dpy, (XRenderColor){.alpha = 0x *
(1-Fade)});
XRenderComposite(dpy, PictOpSrc, srcA, a, dst, 0, 0, 0, 0, 0, 0, width,
height);
XRenderComposite(dpy, PictOpAdd, srcB, ia, dst, 0, 0, 0, 0, 0, 0, width,
height);
XRenderFreePicture(dpy, ia);
XRenderFreePicture(dpy, a);
-Chris
That work's much better (and avoids the crash). I thought the third parameter
of XRenderComposite() is something like a clipmask (after reading
http://www.x.org/releases/current/doc/renderproto/renderproto.txt), but it is
the missing multiplier.
I will use your approach.
Thank you very much.
Peter
Anyway, I wrote a little programm to reproduce the bug.
/**/
/**/
#include stdint.h
#include stdlib.h
#include X11/Xlib.h
#include X11/extensions/Xrender.h
/**/
/**/
int main(int argc, char *argv[])
{
const char *Host = (argc == 2) ? argv[1] : getenv(DISPLAY) ;
if(Host != NULL) {
Display *Dpy = XOpenDisplay(Host) ;
if(Dpy != NULL) {
Window Root = RootWindowOfScreen(DefaultScreenOfDisplay(Dpy)) ;
Pixmap s = XCreatePixmap(Dpy, Root, 100, 100, 32) ;
Pixmap d = XCreatePixmap(Dpy, Root, 100, 100, 32) ;
Pixmap Map = XCreatePixmap(Dpy, Root, 1, 1, 8) ;
XRenderPictFormat *Format32 = XRenderFindStandardFormat(Dpy,
PictStandardARGB32) ;
XRenderPictFormat *Format8 = XRenderFindStandardFormat(Dpy,
PictStandardA8) ;
uint16_t v = 0x8000 ;
XRenderColor c = {.red = v, .green = v, .blue = v, .alpha = v} ;
XRenderPictureAttributes Rep = {.repeat = RepeatNormal} ;
Picture Alpha = XRenderCreatePicture(Dpy, Map, Format8,
CPRepeat, Rep) ;
Picture Src = XRenderCreatePicture(Dpy, s, Format32, 0, NULL) ;
Picture Dest = XRenderCreatePicture(Dpy, d, Format32, 0, NULL) ;
XRenderPictureAttributes Att = {.alpha_map = Alpha} ;
XRenderFillRectangle(Dpy, PictOpSrc, Alpha, c, 0, 0, 1, 1) ;
XRenderChangePicture(Dpy, Src, CPAlphaMap, Att) ;
XRenderChangePicture(Dpy, Dest, CPAlphaMap, Att) ;
XRenderComposite(Dpy, PictOpClear, Src, None, Dest,
0, 0, 0, 0, 0, 0, 100, 100) ;
XSync(Dpy, False) ;
XRenderFreePicture(Dpy, Dest) ;
XRenderFreePicture(Dpy, Src) ;
XRenderFreePicture(Dpy, Alpha) ;
XFreePixmap(Dpy, s) ;
XFreePixmap(Dpy, d) ;
XCloseDisplay(Dpy) ;
}
}
return(0) ;
}
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: XRandR EDID missed with Cedar on LVDS
On Wed, Nov 2, 2011 at 5:03 PM, Kai-Uwe Behrmann k...@gmx.de wrote: While testing a ATI Cedar equiped laptop I could not get the EDID for the interal LVDS in user space. I tried xrandr and xcmddc with no results. But the /var/log/Xorg.0.log showed that EDID was detected and hwinfo gives the monitor manufacturer. Still user space applications needs the complete data block to configure the monitor. Can you post your xorg log and dmesg output? There are several possibilities: 1. Your panel does not provide an EDID. The driver is still able to determine the native mode timings from tables in the vbios. 2. Your EDID has a bad checksum/etc. and the kernel drm EDID validator rejects it: https://bugs.freedesktop.org/show_bug.cgi?id=31943 You can try the patch on that bug and see if it helps. The driver is Radeon-1.3.0 build from git master 80ba041a . Here some more details: https://bugzilla.novell.com/show_bug.cgi?id=615740#c21 That bug just looks like a random collection of things vaguely to EDIDs. Alex ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: XRandR EDID missed with Cedar on LVDS
Am 02.11.11, 17:41 -0400 schrieb Alex Deucher: On Wed, Nov 2, 2011 at 5:03 PM, Kai-Uwe Behrmann k...@gmx.de wrote: While testing a ATI Cedar equiped laptop I could not get the EDID for the interal LVDS in user space. I tried xrandr and xcmddc with no results. But the /var/log/Xorg.0.log showed that EDID was detected and hwinfo gives the monitor manufacturer. Still user space applications needs the complete data block to configure the monitor. Can you post your xorg log and dmesg output? There are several possibilities: They are here: https://bugs.freedesktop.org/show_bug.cgi?id=32343#c7 1. Your panel does not provide an EDID. The driver is still able to determine the native mode timings from tables in the vbios. This LVDS' EDID looks like being detected by frglx. It might be broken. On the other side xcmddc shows an external monitors EDID but does not listen the this LVDS one. xcmddc uses i2c communication. Not sure what frglx does to see the discussed LVDS EDID. 2. Your EDID has a bad checksum/etc. and the kernel drm EDID validator rejects it: https://bugs.freedesktop.org/show_bug.cgi?id=31943 You can try the patch on that bug and see if it helps. kind regards Kai-Uwe ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: XRandR EDID missed with Cedar on LVDS
On Wed, Nov 2, 2011 at 6:34 PM, Kai-Uwe Behrmann k...@gmx.de wrote: Am 02.11.11, 17:41 -0400 schrieb Alex Deucher: On Wed, Nov 2, 2011 at 5:03 PM, Kai-Uwe Behrmann k...@gmx.de wrote: While testing a ATI Cedar equiped laptop I could not get the EDID for the interal LVDS in user space. I tried xrandr and xcmddc with no results. But the /var/log/Xorg.0.log showed that EDID was detected and hwinfo gives the monitor manufacturer. Still user space applications needs the complete data block to configure the monitor. Can you post your xorg log and dmesg output? There are several possibilities: They are here: https://bugs.freedesktop.org/show_bug.cgi?id=32343#c7 1. Your panel does not provide an EDID. The driver is still able to determine the native mode timings from tables in the vbios. This LVDS' EDID looks like being detected by frglx. It might be broken. On the other side xcmddc shows an external monitors EDID but does not listen the this LVDS one. xcmddc uses i2c communication. Not sure what frglx does to see the discussed LVDS EDID. We may need a machine specific quirk for your laptop, or it's possible the closed driver is generating a fake edid using the modeline and vendor info from the vbios tables. Please attach your vbios to the bug above and I'll see what I can find out. Alex ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Simulating a mouse click
On Wed, Nov 02, 2011 at 03:27:42PM +0100, Markus Kramer wrote: Hi, I'm attempting to use xlib to simulate a series of mouse clicks in an application (gedit). I found some posts that describe how to do this and it essentially works. I can do left clicks on buttons and so on. But if I generate a click on the menu bar, a menu opens and something breaks and no further ButtonPress/ButtonRelease events that I send will be processed by the application. When debugging it with xtrace I noticed that my events look slightly different than real left click events. Real: ButtonPress(4) [1]button=left button(0x01) [4]time=0x03752355 [8]root=0x0102 [12]event=0x01a3 [16]child=None(0x) [20]root-x=428 [22]root-y=33 [24]event-x=295 [26]event-y=10 state=0 [30]same-screen=true(0x01) My simulated event: SendEvent [1]propagate=true(0x01) [4]destination=PointerWindow(0x) event-mask=ButtonPress ButtonPress(4) [1]button=left button(0x01) [4]time=0x [8]root=0x0102 [12]event=0x012000a3 [16]child=None(0x) [20]root-x=407 [22]root-y=40 [24]event-x=274 [26]event-y=19 state=0 [30]same-screen=true(0x01) The field event of the real event says 0x01a3 mine is 0x012000a3. What is this event field about? It is not part of the ButtonPress struct. event is the window the event happens on. once you send a button down on a menu, the client usually grabs the device that sent the event and the event window from then on is the grab window, not necessarily the window underneath the cursor. If you're tyring to emulate click events, I recommend to use the XTest extension instead, it's much simpler to handle. Cheers, Peter This is the code that I use to simulate a left click: --- XEvent event; memset(event, 0, sizeof(XEvent)); XWindowAttributes attr; XGetWindowAttributes(dpy, windowId, attr); event.type = ButtonPress; event.xbutton.same_screen = TRUE; event.xbutton.root = root; event.xbutton.window = windowId; event.xbutton.subwindow = None; event.xbutton.x = x; event.xbutton.y = y; event.xbutton.x_root = attr.x + x; event.xbutton.y_root = attr.y + y; event.xbutton.state = 0; event.xbutton.button = Button1; XSendEvent(dpy, PointerWindow, True, ButtonPressMask, event); XFlush(dpy); // the same for ButtonRelease, with modified state and mask -- Thanks in advance. Markus ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: peter.hutte...@who-t.net ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: x crash and auto log me out
Hi Di Zhang, thx for the report but please be more verbose with your bugreport and give the developer a chance to recreate the circumstances where the bug shows up. E.g. What version of xserver are you running ? (F16=Fedora 16 Beta ?) What graphiccard you are using ? When exactly does it happen ? (e.g. at start, or after login, ...) Are interactions needed ? (like starting a certain program, ... ) hope that helps, wh Am 01.11.2011 02:17, schrieb Di Zhang: Hello everyone: X crash and automatic log me out always happen in my F16 beta, can you give me some help to solve this problem, because this problem makes me lose a lot of work. Below is the error log in the Xorg.o.log.old file: 518 [ 37.346] (II) intel(0): Printing DDC gathered Modelines: 519 [ 37.346] (II) intel(0): Modeline 1600x900x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz) 520 [ 37.346] (II) intel(0): Modeline 1600x900x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz) 521 [ 155.044] 522 Backtrace: 523 [ 155.044] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x462d8f] 524 [ 155.045] 1: /usr/bin/Xorg (0x40+0x67b56) [0x467b56] 525 [ 155.045] 2: /lib64/libpthread.so.0 (0x7f9102d05000+0xf4f0) [0x7f9102d144f0] 526 [ 155.045] 3: /usr/lib64/xorg/modules/extensions/librecord.so (0x7f9101555000+0x26c3) [0x7f91015576c3] 527 [ 155.045] 4: /usr/bin/Xorg (_CallCallbacks+0x3c) [0x43820c] 528 [ 155.045] 5: /usr/bin/Xorg (WriteToClient+0x1f5) [0x466315] 529 [ 155.045] 6: /usr/lib64/xorg/modules/extensions/libdri2.so (ProcDRI2WaitMSCReply+0x4f) [0x7f9100f3beef] 530 [ 155.045] 7: /usr/lib64/xorg/modules/extensions/libdri2.so (DRI2WaitMSCComplete+0x52) [0x7f9100f3a6d2] 531 [ 155.045] 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f9100ce7000+0x25ae4) [0x7f9100d0cae4] 532 [ 155.045] 9: /usr/lib64/libdrm.so.2 (drmHandleEvent+0xa3) [0x7f9101145523] 533 [ 155.045] 10: /usr/bin/Xorg (WakeupHandler+0x6b) [0x4379db] 534 [ 155.045] 11: /usr/bin/Xorg (WaitForSomething+0x1a9) [0x460289] 535 [ 155.045] 12: /usr/bin/Xorg (0x40+0x3379a) [0x43379a] 536 [ 155.045] 13: /usr/bin/Xorg (0x40+0x22dc5) [0x422dc5] 537 [ 155.045] 14: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f91024e569d] 538 [ 155.045] 15: /usr/bin/Xorg (0x40+0x230b1) [0x4230b1] 539 [ 155.045] Segmentation fault at address 0x7f90fe161010 540 [ 155.045] 541 Fatal server error: 542 [ 155.045] Caught signal 11 (Segmentation fault). Server aborting 543 [ 155.045] 544 [ 155.045] 545 Please consult the Fedora Project support 546 at http://wiki.x.org 547 for help. 548 [ 155.045] Please also check the log file at /var/log/Xorg.0.log for additional information. 549 [ 155.045] 550 [ 155.051] (II) evdev: Power Button: Close ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: x crash and auto log me out
On Tue, Nov 1, 2011 at 09:17:58 +0800, Di Zhang wrote: Hello everyone: X crash and automatic log me out always happen in my F16 beta, can you give me some help to solve this problem, because this problem makes me lose a lot of work. Below is the error log in the Xorg.o.log.old file: This is https://bugs.freedesktop.org/show_bug.cgi?id=36930 Cheers, Julien ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: keyboard mapping error
Hi
All
I have downgraded xorg 1.7.99.2 to 1.7.7 and the first
warning about kbd driver has gone
(WW) module ABI major version (7) doesn't match the server's
version (8)
and xorg log is now
.
.
(**) Option CoreKeyboard
(**) Keyboard0: always reports core events
(**) Option Protocol standard
(**) Keyboard0: Protocol: standard
(**) Option XkbRules base
(**) Keyboard0: XkbRules: base
(**) Option XkbModel pc105
(**) Keyboard0: XkbModel: pc105
(**) Option XkbLayout us
(**) Keyboard0: XkbLayout: us
(**) Option CustomKeycodes off
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD)
(EE) Error loading keymap
/usr/local/xkeyboard-config-2.0/share/X11/xkb/compiled/server-0.xkm
so i manually created the file server-0.xkm
[root@localhost log] setxkbmap -rules base -model pc104 -layout us
-print server-0
and then compiled it by
[root@localhost log] xkbcomp server-0
[root@localhost ~]# cat server-0
xkb_keymap {
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc+us };
xkb_geometry { include pc(pc104) };
};
and then copied the file server-0.xkm
cp -f server-0.xkm /usr/local/xkeyboard-config-2.0/share/X11/xkb/compiled
Now when i start X xorg log file says
(EE) Error loading keymap
/usr/local/xkeyboard-config-2.0/share/X11/xkb/compiled/server-0.xkm
if i do ls -l on the directory
/usr/local/xkeyboard-config-2.0/share/X11/xkb/compiled then i find
that server-0.xkm is not there.
Any valueable inputs will be appreciated
Thanks
On 10/29/11, Dwijadas Dey dwi...@gmail.com wrote:
Hi i have compiled and installed xorg 1.7.7 with all the xkb options.
Now the keyboard is detected but i have to press twice to get that
character with some peculiar behaviour say typing 's' will give me an
option for saving etc. I have checked with setxkboption with the
command
[root@localhost ~]# setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Applied rules from xorg:
model: pc105
layout: us
Trying to build keymap using the following components:
keycodes: xfree86+aliases(qwerty)
types: complete
compat: complete
symbols:pc+us+inet(pc105)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc+us+inet(pc105) };
xkb_geometry { include pc(pc105) };
};
and the xorg config section has following part in the keyboard section
Section InputDevice
Identifier Keyboard0
Driver kbd
Option XkbModel pc105
Option XkbLayout us
EndSection
and the xorg log contains the following part for keyboard section
(II) LoadModule: kbd
(II) Loading
/usr/local/xf86-input-keyboard-1.4.0/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor=X.Org Foundation
compiled for 1.7.7, module version = 1.4.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(WW) module ABI major version (7) doesn't match the server's version (8)
..
.
..
(**) Option CoreKeyboard
(**) Keyboard0: always reports core events
(**) Option Protocol standard
(**) Keyboard0: Protocol: standard
(**) Option XkbRules base
(**) Keyboard0: XkbRules: base
(**) Option XkbModel pc105
(**) Keyboard0: XkbModel: pc105
(**) Option XkbLayout us
(**) Keyboard0: XkbLayout: us
(**) Option CustomKeycodes off
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD)
Am i missing something ?
Dwdy
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-274.3.1.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.39 #9 SMP Tue Oct 25 19:41:13 IST 2011 i686
Kernel command line: ro root=/dev/VolGroup00/LogVol00
Build Date: 30 October 2011 09:25:28AM
Current version of pixman: 0.22.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /opt/xorg/var/log/Xorg.0.log, Time: Sun Oct 30 13:45:45 2011
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout single head configuration
(**) |--Screen Screen0 (0)
(**) | |--Monitor Monitor0
(**) | |--Device Videocard0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(**) Option DontZap off
(**) Option AllowMouseOpenFail on
(**) Option AIGLX off
(**) Option AllowEmptyInput false
(**) Option IgnoreABI on
Re: xorg open driver and ati card Radeon 9200 agp
Hi Valter, I had this problem long ago with a very similar configuration. It vanished when Alex Deucher modified some details (like rounding) in the Radeon mode setting/calculation code. I don't know about the details, but maybe you can copy the modeline generated by the proprietary driver and force the open-source radeon to use it. But I'm not sure it's possible, and even if I don't know how to do it ;) In my case, the problem also did depend on the LCD - perhaps you can check other models. Cheers, Simon On 10/29/2011 06:52 PM, Valter Giovannetti wrote: Hi. Excuse me for my bad english! I am a newcomer to Ubuntu and Italian! On my computer I have an ATI Radeon 9200 AGP- RV280 chip. The Operating Systems are: Windows XP and Ubuntu 11.04. In WindowsXP all work ok. Everything works fine with Ubuntu, 3D acceleration, if I use the VGA output. Apart from the top rows in windows, when I move. But the DVI output does not work well, if I try to move, enlarge a window, the monitor turns off and on again. As if the video signal disappear. I searched various forums how to fix the problem, but nobody could help me. By installing the proprietary driver, present in the repositories, everything works fine, but 3D acceleration vanishes. Can you helpme? Thank you. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: simon.t...@gmx.de ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: No screens found on intel sandy bridge / centos 5.7 / kernel 2.6.39
Hi Solved the problem, i had compiled kernel 2.6.39 without drm support earlier, now compiled again with drm intel support i got the screen. Thanks On 10/27/11, Tino Keitel tino.keitel+x...@tikei.de wrote: On Tue, Oct 25, 2011 at 13:56:56 +0530, Dwijadas Dey wrote: Hi After successfully compiling and installing xorg-server-1.7.7, xf86-video-intel-2.13.903 when i run startx -- /opt/xorg/bin/Xorg -verbose i got Fatal server error: no screens found. [...] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge (II) Primary Device is: PCI 00@00:02:0 (EE) No devices detected. What is the output of lspci -nn ? Regards, Tino ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: dwi...@gmail.com ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
RE: Intel 845GME with newer xorg
Hi all! I'm now trying Running xorg-server on arm6(S3C6410), my xorg.log is attached, why can't find /dev/fb0 ? BR -Original Message- From: xorg-bounces+anf=siso.edu...@lists.freedesktop.org on behalf of jarek Sent: Thu 10/27/2011 10:36 PM To: xorg@lists.freedesktop.org Subject: Intel 845GME with newer xorg Hi all! I've device with xorg 1.6.5, and I want to upgrade it to 1.10.4. I tried to find IEGD driver but failed. After some tweeks I have installed Intel driver from http://intellinuxgraphics.org (xf86-video-intel-2.15.0.tar.bz2). which almost works. The problem I'have is that I'm unable to configure resolution for this display. In original xorg.conf I have: Section Screen SubSection Display Depth 24 Modes 1920x480 EndSubSection IdentifierScreen0 DeviceIntel_IEGD-0 EndSection Section Device Identifier Intel_IEGD-0 Driver iegd VendorName Intel(R) DEG BoardName Embedded Graphics BusID 0:2:0 Screen 0 Option PcfVersion1792 Option ConfigId 1 Option ALL/1/name test4 Option PortDrivers sdvo lvds Option ALL/1/General/PortOrder 24000 Option ALL/1/General/DisplayConfig 2 Option ALL/1/General/DisplayDetect 0 Option ALL/1/Port/4/General/name lvds Option ALL/1/Port/4/General/EdidAvail 0 Option ALL/1/Port/4/General/EdidNotAvail 4 Option ALL/1/Port/4/General/Rotation 0 Option ALL/1/Port/4/General/Edid 0 Option ALL/1/Port/4/Attr/271 Option ALL/1/Port/4/Attr/491 Option ALL/1/Port/4/Attr/2618 Option ALL/1/Port/4/Attr/437 Option ALL/1/Port/4/Dtd/1/PixelClock 114000 Option ALL/1/Port/4/Dtd/1/HorzActive 1920 Option ALL/1/Port/4/Dtd/1/HorzSync 55 Option ALL/1/Port/4/Dtd/1/HorzSyncPulse88 Option ALL/1/Port/4/Dtd/1/HorzBlank800 Option ALL/1/Port/4/Dtd/1/VertActive 480 Option ALL/1/Port/4/Dtd/1/VertSync 3 Option ALL/1/Port/4/Dtd/1/VertSyncPulse5 Option ALL/1/Port/4/Dtd/1/VertBlank200 Option ALL/1/Port/4/Dtd/1/Flags0x802 Option ALL/1/Port/2/General/name sdvo Option ALL/1/Port/2/General/EdidAvail 0 Option ALL/1/Port/2/General/EdidNotAvail 4 Option ALL/1/Port/2/General/Rotation 0 Option ALL/1/Port/2/General/Edid 0 Option ALL/1/Port/2/Attr/271 Option ALL/1/Port/2/Attr/491 Option ALL/1/Port/2/Attr/2618 Option ALL/1/Port/2/Dtd/1/PixelClock 114000 Option ALL/1/Port/2/Dtd/1/HorzActive 1920 Option ALL/1/Port/2/Dtd/1/HorzSync 55 Option ALL/1/Port/2/Dtd/1/HorzSyncPulse88 Option ALL/1/Port/2/Dtd/1/HorzBlank800 Option ALL/1/Port/2/Dtd/1/VertActive 480 Option ALL/1/Port/2/Dtd/1/VertSync 3 Option ALL/1/Port/2/Dtd/1/VertSyncPulse5 Option ALL/1/Port/2/Dtd/1/VertBlank200 Option ALL/1/Port/2/Dtd/1/Flags0x802 EndSection I'tried a lot of different settings but I'm unable to get it working with intel driver. Usually I get: 4956.938] (II) intel(0): Not using mode 1920x480 (exceeds panel dimensions) Can someone help ? best regards Jarek [23.341] X.Org X Server 1.10.4 Release Date: 2011-08-19 [23.342] X Protocol Version 11, Revision 0 [23.342] Build Operating System: Linux 2.6.32-34-generic i686 OpenBricks [23.342] Current Operating System: Linux 192.168.1.20 2.6.28.6 #721 PREEMPT Thu Jan 13 17:51:35 CST 2011 armv6l [23.343] Build Date: 18 October 2011 03:21:22PM [23.343] [23.344] Current version of pixman: 0.23.4 [23.344] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [23.344] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [23.346] (==) Log file: /var/log/Xorg.0.log, Time: Thu Jan 1 00:00:23 1970 [23.399] (==) Using config file: /etc/X11/xorg.conf [23.400] (==) Using config directory: /etc/X11/xorg.conf.d [23.400] (==) Using system config directory /usr/share/X11/xorg.conf.d [23.498] (==) No Layout section. Using the first Screen section. [23.498] (**) |--Screen Screen0 (0) [23.498] (**) | |--Monitor Monitor0 [23.526] (**) | |--Device Card0 [23.526] (==) Automatically adding devices [23.526] (==) Automatically enabling devices [23.592] (==) FontPath set to: /usr/share/X11/fonts/misc, built-ins [23.592] (==)
Re: Missing events sometimes
Hi Peter, On Fri, Oct 28, 2011 at 12:44 AM, Peter Hutterer peter.hutte...@who-t.net wrote: [...] I'm not sure on the actual code but there's a race condition for both - if the release event happens before the server receives/processes the GrabKey/Pointer request you may drop the event on the floor. This shouldn't happen since you should get it delivered based on the passive grab either way but there's a chance the client drops it. Try swapping the passive grab to sync and see if that avoids it. Yeap it works, this plus an XAllowEvents(dpy, SyncKeyboard, ev-time) that nails it! [...] put a delay in before XGrabPointer in the client and click fast (so that the release happens before the request). this way you can easily verify if it is that race condition or something else. Many thanks! Cheers, Olivier ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: No screens found on intel sandy bridge / centos 5.7 / kernel 2.6.39
On Tue, Oct 25, 2011 at 13:56:56 +0530, Dwijadas Dey wrote: Hi After successfully compiling and installing xorg-server-1.7.7, xf86-video-intel-2.13.903 when i run startx -- /opt/xorg/bin/Xorg -verbose i got Fatal server error: no screens found. [...] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge (II) Primary Device is: PCI 00@00:02:0 (EE) No devices detected. What is the output of lspci -nn ? Regards, Tino ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Missing events sometimes
On Tue, Oct 25, 2011 at 10:16:17AM +0200, Olivier Fourdan wrote: I have been facing a bug in the xfce [1] window manager xfwm4 [2], for a very long time, no doubt the fault is with my code yet I fail to find the fix. Sometimes, when the system is heavily loaded and/or swapping intensively, the event loop does not get the ButtonReleasse or KeyRelease events it's waiting to exit the event loop. The logic used in the code is the following: 1. For keyboard, it installs a passive grab in sync mode on keyboard, ie: XGrabKey (dpy, keycode, modifier, w, TRUE, GrabModeAsync, GrabModeSync); 2. For buttons, same with Sync mode on pointer XGrabButton (dpy, button, modifier, w, FALSE, ButtonPressMask|ButtonReleaseMask, GrabModeSync, GrabModeAsync, None, None); 3. Then when the user activates a keyboard shortcut or moves a window usign the mouse, the window manager installs an active grab on the keyboard / pointer using the timestamp of the event: XGrabKeyboard (dpy, root, TRUE, GrabModeAsync, GrabModeAsync, timestamp) or XGrabPointer (dpy, root, FALSE, PointerMotionMask | ButtonMotionMask | ButtonReleaseMask | LeaveWindowMask, GrabModeAsync, GrabModeAsync, root, cursor, timestamp); 4. Then enters an event loop processing events, until a KeyRelease event (in the case of a keyboard shortcut) or a ButtonRelease is received (in the case of a mouse op). Using this logic, the code sometimes (when the system is loaded or swapping) remains in the event loop because the ButtonRelease or KeyRelease event is not received in the event loop, so I guess it's consumed somehow before the code enters the event loop, but how? I'm not sure on the actual code but there's a race condition for both - if the release event happens before the server receives/processes the GrabKey/Pointer request you may drop the event on the floor. This shouldn't happen since you should get it delivered based on the passive grab either way but there's a chance the client drops it. Try swapping the passive grab to sync and see if that avoids it. As I said, there's probably a flaw somewhere in the logic, but I fail to find it (also because of the nature of the probl;em it's quite hard to reproduce and therefore investigate and test), so I am open to any suggestion... put a delay in before XGrabPointer in the client and click fast (so that the release happens before the request). this way you can easily verify if it is that race condition or something else. Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [v2 PATCH] libpciaccess: close mtrr fd on pci_cleanup
Thanks,
I reviewed and pushed this with a small modification.
--Jeremy
On Oct 24, 2011, at 12:15 PM, Nithin Nayak Sujir wrote:
Since the fd is not closed, calling pci_system_init and
pci_system_cleanup more than 1024 times results in too many files open
error.
v2: Modified the patch to use the destroy hook function instead of
calling close in the common code based on Jeremy Huddleston's comments. It
seemed appropriate to use the destroy hook since other implementations are
doing clean ups here.
Signed-off-by: Nithin Nayak Sujir nsu...@broadcom.com
---
src/linux_sysfs.c | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/src/linux_sysfs.c b/src/linux_sysfs.c
index d5ba66a..09e7138 100644
--- a/src/linux_sysfs.c
+++ b/src/linux_sysfs.c
@@ -889,8 +889,18 @@ pci_device_linux_sysfs_unmap_legacy(struct pci_device
*dev, void *addr, pciaddr_
return munmap(addr, size);
}
+
+static void
+pci_system_linux_destroy(void)
+{
+#ifdef HAVE_MTRR
+ if (pci_sys-mtrr_fd 0)
+ close(pci_sys-mtrr_fd);
+#endif
+}
+
static const struct pci_system_methods linux_sysfs_methods = {
-.destroy = NULL,
+.destroy = pci_system_linux_destroy,
.destroy_device = NULL,
.read_rom = pci_device_linux_sysfs_read_rom,
.probe = pci_device_linux_sysfs_probe,
--
1.7.1
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: libpciaccess
Hi WH Yes, i was missing -lpciaccesss parameter in the configure option though lib path was there. When i did pkg-config --cflags --libs libpciaccess i find out that missing part. Now xorg has been installed, but startx is not working, i will post it separately. Many thanks for you suggestion/time Dwdy On 10/22/11, walter harms wha...@bfs.de wrote: undefined reference to means there is an object file or library missing in the final stage of linking. re, wh Am 22.10.2011 16:13, schrieb Dwijadas Dey: Hi list Able to solve the problem ( http://lists.freedesktop.org/archives/xorg/2011-October/053700.html )related to drmsetserverinfo , the problem was in xorg compilation where i set the location of LIBDRM_CFLAGS and LIBS to an old version of libdrm (2.0.4), correcting these LIBDRM_CFLAGS and LIBDRM_LIBS location solves the problem. Now i am trying to recompile xorg with libpciaccess but at the last stage of make command I got the errors which are given below. * ./.libs/libxorg.a(xf86Helper.o): In function `xf86MatchPciInstances': xf86Helper.c:(.text+0x3583): undefined reference to `pci_slot_match_iterator_create' xf86Helper.c:(.text+0x3597): undefined reference to `pci_device_next' xf86Helper.c:(.text+0x35ab): undefined reference to `pci_iterator_destroy' xf86Helper.c:(.text+0x35ce): undefined reference to `pci_slot_match_iterator_create' xf86Helper.c:(.text+0x3805): undefined reference to `pci_device_next' xf86Helper.c:(.text+0x381d): undefined reference to `pci_iterator_destroy' ./.libs/libxorg.a(xf86Init.o): In function `probe_devices_from_device_sections': xf86Init.c:(.text+0x693): undefined reference to `pci_id_match_iterator_create' xf86Init.c:(.text+0x74c): undefined reference to `pci_device_next' xf86Init.c:(.text+0x764): undefined reference to `pci_iterator_destroy' ./.libs/libxorg.a(xf86Init.o): In function `add_matching_devices_to_configure_list': xf86Init.c:(.text+0xaae): undefined reference to `pci_id_match_iterator_create' xf86Init.c:(.text+0xc64): undefined reference to `pci_device_next' xf86Init.c:(.text+0xc7c): undefined reference to `pci_iterator_destroy' ./.libs/libxorg.a(xf86Configure.o): In function `bus_pci_newdev_configure': xf86Configure.c:(.text+0x169): undefined reference to `pci_device_get_vendor_name' xf86Configure.c:(.text+0x177): undefined reference to `pci_device_get_device_name' ./.libs/libxorg.a(xf86pciBus.o): In function `xf86PciProbe': xf86pciBus.c:(.text+0xae): undefined reference to `pci_slot_match_iterator_create' xf86pciBus.c:(.text+0x147): undefined reference to `pci_device_probe' xf86pciBus.c:(.text+0x15f): undefined reference to `pci_device_next' xf86pciBus.c:(.text+0x1cd): undefined reference to `pci_device_cfg_read_u16' xf86pciBus.c:(.text+0x29d): undefined reference to `pci_device_get_vendor_name' xf86pciBus.c:(.text+0x2ab): undefined reference to `pci_device_get_device_name' ./.libs/libxorg.a(xf86AutoConfig.o): In function `listPossibleVideoDrivers': xf86AutoConfig.c:(.text+0xf66): undefined reference to `pci_slot_match_iterator_create' xf86AutoConfig.c:(.text+0xf85): undefined reference to `pci_device_next' xf86AutoConfig.c:(.text+0xf99): undefined reference to `pci_iterator_destroy' ./.libs/libxorg.a(linuxPci.o): In function `get_parent_bridge': linuxPci.c:(.text+0x410): undefined reference to `pci_id_match_iterator_create' linuxPci.c:(.text+0x43e): undefined reference to `pci_device_get_bridge_info' linuxPci.c:(.text+0x464): undefined reference to `pci_device_next' linuxPci.c:(.text+0x478): undefined reference to `pci_iterator_destroy' ./.libs/libxorg.a(Pci.o): In function `xf86scanpci': ** I checked pciaccess.h where each of these definitions are there and it is included in the include path. I want to know from the list, is it a bug related to libpciaccess(0.10.9) ? Thanks Dwdy ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: wha...@bfs.de ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: remapping XInput axes
On Mon, 24 Oct 2011, Peter Hutterer wrote: On Fri, Oct 21, 2011 at 02:45:06PM +0200, Tamas Papp wrote: Hi, I just purchased an Intellipen Pro digital pen. It shows up fine in xinput list: [...] and button events are detected, but the cursor doesn't move. xinput test reveals that the X and Y axes are a[2] and a[3]: [...] Device 'EPOS EPOS Pen Digitizer.': Device Enabled (132): 1 Coordinate Transformation Matrix (134): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (257): 0 Device Accel Constant Deceleration (258): 1.00 Device Accel Adaptive Deceleration (259): 1.00 Device Accel Velocity Scaling (260):10.00 Evdev Axis Inversion (261): 0, 0 Evdev Axis Calibration (262): no items Evdev Axes Swap (263): 0 Axis Labels (264): Abs X (254), Abs Y (255), Abs Z (275), Abs Rotary X (276), Abs Pressure (485), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285) Fairly common issue. The kernel needs a fix to enable HID_QUIRK_MULTI_INPUT for this device. Hi Peter, Thanks, that put me on the right track. I just had to create /etc/hal/fdi/policy/90-intellipen-pro.fdi with the contents ?xml version=1.0 encoding=UTF-8? deviceinfo version=0.2 device !-- Intellipen Pro -- match key=usb_device.vendor_id int=0x188c match key=usb_device.product_id int=0x221 merge key=input.x11_driver type=stringevdev/merge /match /match /device /deviceinfo and /etc/modprobe.d/intellipen.conf with options usbhid quirks=0x188c:0x0221:0x0040 and the device works perfectly. Where should I submit this information so that it gets incorporated to future updates so that others can just plug it in and have it work automatically? Thanks, Tamas ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [PATCH] libpciaccess: close mtrr fd on pci_cleanup
While possibly safe in practice, this doesn't look like the correct fix. It is possible that this will result in a close(0) if HAVE_MTRR is defined and mtrr_fd was just never set. HAVE_MTRR is defined if asm/mtrr.h exists. mtrr_fd is set if HAVE_MTRR is defined and linux_sysfs is used. Probably a trivial example of this would be to sudo touch /usr/include/asm/mtrr.h on FreeBSD. On Oct 21, 2011, at 11:49, Nithin Nayak Sujir wrote: Since the fd is not closed, calling pci_system_init and pci_system_cleanup more than 1024 times results in too many files open error. Signed-off-by: Nithin Nayak Sujir nsu...@broadcom.com --- src/common_init.c |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/src/common_init.c b/src/common_init.c index 5e91c27..d7ade3f 100644 --- a/src/common_init.c +++ b/src/common_init.c @@ -31,7 +31,9 @@ #include stdlib.h #include errno.h +#include unistd.h +#include config.h #include pciaccess.h #include pciaccess_private.h @@ -122,6 +124,10 @@ pci_system_cleanup( void ) (*pci_sys-methods-destroy)(); } +#ifdef HAVE_MTRR +if (pci_sys-mtrr_fd != -1) + close(pci_sys-mtrr_fd); +#endif free( pci_sys ); pci_sys = NULL; } -- 1.7.1 ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: jerem...@freedesktop.org ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [PATCH] libpciaccess: close mtrr fd on pci_cleanup
The module which opens the fd should be the same module that closes it. Letting that cross between the common/specific boundary seems problematic. I'd prefer to see a new hook added for implementation-specific cleanup, and the close() live in linux_sysfs.c itself. That will allow for better abstraction down the road as other implementations might want to do something similar. On Oct 24, 2011, at 10:18, Nithin Sujir wrote: On 10/24/2011 09:51 AM, Jeremy Huddleston wrote: While possibly safe in practice, this doesn't look like the correct fix. It is possible that this will result in a close(0) if HAVE_MTRR is defined and mtrr_fd was just never set. HAVE_MTRR is defined ifasm/mtrr.h exists. mtrr_fd is set if HAVE_MTRR is defined and linux_sysfs is used. Probably a trivial example of this would be to sudo touch /usr/include/asm/mtrr.h on FreeBSD. That is a valid point. I don't have a freebsd system to test it but based on code review I agree that what you say will happen. Would you suggest adding an #ifdef linux around the close or since the pci_sys structure is allocated with a calloc either directly or indirectly, I can change the condition to check for 0. Thanks, Nithin. On Oct 21, 2011, at 11:49, Nithin Nayak Sujir wrote: Since the fd is not closed, calling pci_system_init and pci_system_cleanup more than 1024 times results in too many files open error. Signed-off-by: Nithin Nayak Sujirnsu...@broadcom.com --- src/common_init.c |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/src/common_init.c b/src/common_init.c index 5e91c27..d7ade3f 100644 --- a/src/common_init.c +++ b/src/common_init.c @@ -31,7 +31,9 @@ #includestdlib.h #includeerrno.h +#includeunistd.h +#include config.h #include pciaccess.h #include pciaccess_private.h @@ -122,6 +124,10 @@ pci_system_cleanup( void ) (*pci_sys-methods-destroy)(); } +#ifdef HAVE_MTRR +if (pci_sys-mtrr_fd != -1) + close(pci_sys-mtrr_fd); +#endif free( pci_sys ); pci_sys = NULL; } -- 1.7.1 ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: jerem...@freedesktop.org ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Monitor doesn't display anything. EDID trouble ?
On Mon, Oct 24, 2011 at 3:01 PM, Xavier Bestel xavier.bes...@free.fr wrote: Hi, I know it may be off-topic, but the experience is there. I've just bought a used 30 monitor (HP ZR30w), and it doesn't display anything, even at BIOS time. The backlight is on, but I see nothing except a faint flickering at mode change times. Screen blanking works (the backlight switches off). I'm using a Radeon HD 5700 via DVI, debian/sid with kernel 3.1.0-rc7, Xorg 2:1.11.1.901-2 and radeon 1:6.14.2-2. After googling a bit, some people talk about a possible EDID problem (apparently it's possible to have the EDID somehow erased from the EEPROM ?). But Xorg.0.log does seem indicate that there's an EDID: [ 21.829] (II) RADEON(0): Monitor name: HP ZR30w [ 21.829] (II) RADEON(0): Serial No: CN4048041Z [ 21.829] (II) RADEON(0): EDID (in hex): [ 21.829] (II) RADEON(0): 000022f06e2801010101 [ 21.829] (II) RADEON(0): 3014010380402878ea8d85ad4f35b125 [ 21.829] (II) RADEON(0): 0e50540001010101010101010101 [ 21.829] (II) RADEON(0): 010101010101e26800a0a0402e603020 [ 21.829] (II) RADEON(0): 36008190211abc1b00a050201730 [ 21.829] (II) RADEON(0): 302036008190211a00fc0048 [ 21.829] (II) RADEON(0): 50205a523330770a2020202000ff [ 21.829] (II) RADEON(0): 00434e343034383034315a0a20200066 [ 21.829] (II) RADEON(0): Printing probed modes for output DVI-0 [ 21.829] (II) RADEON(0): Modeline 2560x1600x60.0 268.50 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.7 kHz) [ 21.829] (II) RADEON(0): Modeline 1280x800x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz) ... and then: [ 21.854] (II) RADEON(0): Output DVI-0 using initial mode 2560x1600 Does anyone have an idea how I could pinpoint the problem ? The EDID looks ok to me. Do any other modes work? Try 1280x800. Try the other DVI port. If the neither port lights up the monitor (especially if the bios produces no display), it's probably a bad monitor. Alex Thanks a lot, Xav dmesg | grep drm [ 0.998537] [drm] Initialized drm 1.1.0 20060810 [ 1.009248] [drm] radeon kernel modesetting enabled. [ 1.009276] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver [ 1.009877] [drm] initializing kernel modesetting (JUNIPER 0x1002:0x68B8 0x1682:0x2994). [ 1.009914] [drm] register mmio base: 0xFE7C [ 1.009915] [drm] register mmio size: 131072 [ 1.010062] [drm] Detected VRAM RAM=1024M, BAR=256M [ 1.010064] [drm] RAM width 128bits DDR [ 1.010128] [drm] radeon: 1024M of VRAM memory ready [ 1.010130] [drm] radeon: 512M of GTT memory ready. [ 1.010139] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 1.010140] [drm] Driver supports precise vblank timestamp query. [ 1.010189] [drm] radeon: irq initialized. [ 1.010192] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1.010720] [drm] Loading JUNIPER Microcode [ 1.034007] [drm] ring test succeeded in 1 usecs [ 1.034086] [drm] radeon: ib pool ready. [ 1.034146] [drm] ib test succeeded in 0 usecs [ 1.034517] [drm] Radeon Display Connectors [ 1.034518] [drm] Connector 0: [ 1.034519] [drm] DisplayPort [ 1.034520] [drm] HPD4 [ 1.034521] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [ 1.034523] [drm] Encoders: [ 1.034524] [drm] DFP1: INTERNAL_UNIPHY2 [ 1.034525] [drm] Connector 1: [ 1.034526] [drm] DVI-I [ 1.034527] [drm] HPD1 [ 1.034528] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c [ 1.034529] [drm] Encoders: [ 1.034530] [drm] DFP2: INTERNAL_UNIPHY1 [ 1.034531] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 1.034533] [drm] Connector 2: [ 1.034533] [drm] DVI-I [ 1.034534] [drm] HPD6 [ 1.034536] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c [ 1.034537] [drm] Encoders: [ 1.034538] [drm] DFP3: INTERNAL_UNIPHY [ 1.034539] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 1.512032] [drm] Radeon display connector DP-1: No monitor connected or invalid EDID [ 1.563505] [drm] Radeon display connector DVI-I-1: Found valid EDID [ 1.573120] [drm] Radeon display connector DVI-I-2: No monitor connected or invalid EDID [ 1.573135] [drm] Internal thermal controller with fan control [ 1.573174] [drm] radeon: power management initialized [ 1.665202] [drm] fb mappable at 0xD0141000 [ 1.665203] [drm] vram apper at 0xD000 [ 1.665204] [drm] size 16384000 [ 1.665205] [drm] fb depth is 24 [ 1.665206] [drm] pitch is 10240 [ 1.665288] fbcon: radeondrmfb (fb0) is primary device [ 2.124952] fb0: radeondrmfb frame buffer device [ 2.124954] drm: registered panic notifier [ 2.124962] [drm] Initialized radeon 2.11.0 20080528 for :01:00.0 on minor 0
Re: Monitor doesn't display anything. EDID trouble ?
On Mon, Oct 24, 2011 at 4:49 PM, Xavier Bestel xavier.bes...@free.fr wrote: Le lundi 24 octobre 2011 à 15:16 -0400, Alex Deucher a écrit : On Mon, Oct 24, 2011 at 3:01 PM, Xavier Bestel xavier.bes...@free.fr wrote: Hi, I know it may be off-topic, but the experience is there. I've just bought a used 30 monitor (HP ZR30w), and it doesn't display anything, even at BIOS time. The backlight is on, but I see nothing except a faint flickering at mode change times. Screen blanking works (the backlight switches off). I'm using a Radeon HD 5700 via DVI, debian/sid with kernel 3.1.0-rc7, Xorg 2:1.11.1.901-2 and radeon 1:6.14.2-2. After googling a bit, some people talk about a possible EDID problem (apparently it's possible to have the EDID somehow erased from the EEPROM ?). But Xorg.0.log does seem indicate that there's an EDID: [ 21.829] (II) RADEON(0): Monitor name: HP ZR30w [ 21.829] (II) RADEON(0): Serial No: CN4048041Z [ 21.829] (II) RADEON(0): EDID (in hex): [ 21.829] (II) RADEON(0): 000022f06e2801010101 [ 21.829] (II) RADEON(0): 3014010380402878ea8d85ad4f35b125 [ 21.829] (II) RADEON(0): 0e50540001010101010101010101 [ 21.829] (II) RADEON(0): 010101010101e26800a0a0402e603020 [ 21.829] (II) RADEON(0): 36008190211abc1b00a050201730 [ 21.829] (II) RADEON(0): 302036008190211a00fc0048 [ 21.829] (II) RADEON(0): 50205a523330770a2020202000ff [ 21.829] (II) RADEON(0): 00434e343034383034315a0a20200066 [ 21.829] (II) RADEON(0): Printing probed modes for output DVI-0 [ 21.829] (II) RADEON(0): Modeline 2560x1600x60.0 268.50 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.7 kHz) [ 21.829] (II) RADEON(0): Modeline 1280x800x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz) ... and then: [ 21.854] (II) RADEON(0): Output DVI-0 using initial mode 2560x1600 Does anyone have an idea how I could pinpoint the problem ? The EDID looks ok to me. Do any other modes work? Try 1280x800. Try the other DVI port. If the neither port lights up the monitor (especially if the bios produces no display), it's probably a bad monitor. OK, thanks to you I've found the problems: 1) this monitor is apparently unable to display anything but 1280x800 or 2560x1600, so no BIOS nor GRUB for me. You should still get a BIOS image. The vbios takes the preferred mode from the monitor's EDID and uses the scaler to fake the legacy modes. It's probably trying to use 2560x1600 mode which requires a dual link cable. Alex 2) my cable is single-link, so Xorg's default guess doesn't work. After hooking a second monitor, and choosing 1280x800 for the big one, everything's working (sort-of). I'll hunt for a dual-link or displayport cable, whichever is cheapest. Can Xorg/radeon detect that the DVI cable is single-link ? Thanks, Xav ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Monitor doesn't display anything. EDID trouble ?
Le lundi 24 octobre 2011 à 16:53 -0400, Alex Deucher a écrit : On Mon, Oct 24, 2011 at 4:49 PM, Xavier Bestel xavier.bes...@free.fr wrote: Le lundi 24 octobre 2011 à 15:16 -0400, Alex Deucher a écrit : On Mon, Oct 24, 2011 at 3:01 PM, Xavier Bestel xavier.bes...@free.fr wrote: Hi, I know it may be off-topic, but the experience is there. I've just bought a used 30 monitor (HP ZR30w), and it doesn't display anything, even at BIOS time. The backlight is on, but I see nothing except a faint flickering at mode change times. Screen blanking works (the backlight switches off). I'm using a Radeon HD 5700 via DVI, debian/sid with kernel 3.1.0-rc7, Xorg 2:1.11.1.901-2 and radeon 1:6.14.2-2. After googling a bit, some people talk about a possible EDID problem (apparently it's possible to have the EDID somehow erased from the EEPROM ?). But Xorg.0.log does seem indicate that there's an EDID: [21.829] (II) RADEON(0): Monitor name: HP ZR30w [21.829] (II) RADEON(0): Serial No: CN4048041Z [21.829] (II) RADEON(0): EDID (in hex): [21.829] (II) RADEON(0):000022f06e2801010101 [21.829] (II) RADEON(0):3014010380402878ea8d85ad4f35b125 [21.829] (II) RADEON(0):0e50540001010101010101010101 [21.829] (II) RADEON(0):010101010101e26800a0a0402e603020 [21.829] (II) RADEON(0):36008190211abc1b00a050201730 [21.829] (II) RADEON(0):302036008190211a00fc0048 [21.829] (II) RADEON(0):50205a523330770a2020202000ff [21.829] (II) RADEON(0):00434e343034383034315a0a20200066 [21.829] (II) RADEON(0): Printing probed modes for output DVI-0 [21.829] (II) RADEON(0): Modeline 2560x1600x60.0 268.50 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.7 kHz) [21.829] (II) RADEON(0): Modeline 1280x800x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz) ... and then: [21.854] (II) RADEON(0): Output DVI-0 using initial mode 2560x1600 Does anyone have an idea how I could pinpoint the problem ? The EDID looks ok to me. Do any other modes work? Try 1280x800. Try the other DVI port. If the neither port lights up the monitor (especially if the bios produces no display), it's probably a bad monitor. OK, thanks to you I've found the problems: 1) this monitor is apparently unable to display anything but 1280x800 or 2560x1600, so no BIOS nor GRUB for me. You should still get a BIOS image. The vbios takes the preferred mode from the monitor's EDID and uses the scaler to fake the legacy modes. It's probably trying to use 2560x1600 mode which requires a dual link cable. OK, I'll see that with the good cable. Thanks Alex, Xav ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Monitor doesn't display anything. EDID trouble ?
On Mon, Oct 24, 2011 at 5:03 PM, Xavier Bestel xavier.bes...@free.fr wrote: Le lundi 24 octobre 2011 à 15:16 -0400, Alex Deucher a écrit : On Mon, Oct 24, 2011 at 3:01 PM, Xavier Bestel xavier.bes...@free.fr wrote: Hi, I know it may be off-topic, but the experience is there. I've just bought a used 30 monitor (HP ZR30w), and it doesn't display anything, even at BIOS time. The backlight is on, but I see nothing except a faint flickering at mode change times. Screen blanking works (the backlight switches off). I'm using a Radeon HD 5700 via DVI, debian/sid with kernel 3.1.0-rc7, Xorg 2:1.11.1.901-2 and radeon 1:6.14.2-2. After googling a bit, some people talk about a possible EDID problem (apparently it's possible to have the EDID somehow erased from the EEPROM ?). But Xorg.0.log does seem indicate that there's an EDID: [ 21.829] (II) RADEON(0): Monitor name: HP ZR30w [ 21.829] (II) RADEON(0): Serial No: CN4048041Z [ 21.829] (II) RADEON(0): EDID (in hex): [ 21.829] (II) RADEON(0): 000022f06e2801010101 [ 21.829] (II) RADEON(0): 3014010380402878ea8d85ad4f35b125 [ 21.829] (II) RADEON(0): 0e50540001010101010101010101 [ 21.829] (II) RADEON(0): 010101010101e26800a0a0402e603020 [ 21.829] (II) RADEON(0): 36008190211abc1b00a050201730 [ 21.829] (II) RADEON(0): 302036008190211a00fc0048 [ 21.829] (II) RADEON(0): 50205a523330770a2020202000ff [ 21.829] (II) RADEON(0): 00434e343034383034315a0a20200066 [ 21.829] (II) RADEON(0): Printing probed modes for output DVI-0 [ 21.829] (II) RADEON(0): Modeline 2560x1600x60.0 268.50 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.7 kHz) [ 21.829] (II) RADEON(0): Modeline 1280x800x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz) ... and then: [ 21.854] (II) RADEON(0): Output DVI-0 using initial mode 2560x1600 Does anyone have an idea how I could pinpoint the problem ? The EDID looks ok to me. Do any other modes work? Try 1280x800. Try the other DVI port. If the neither port lights up the monitor (especially if the bios produces no display), it's probably a bad monitor. OK, thanks to you I've found the problem 1) this monitor is apparently unable to display anything but 1280x800 or 2560x1600, so no BIOS nor GRUB for me. 2) my cable is single-link, so Xorg's default guess doesn't work. After hooking a second monitor, and choosing 1280x800 for the big one, everything's working (sort-of). I'll hunt for a dual-link or displayport cable, whichever is cheapest. Can Xorg detect if the cable is single-link ? No. Alex ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: remapping XInput axes
On Mon, Oct 24, 2011 at 01:59:50PM +0200, Tamas Papp wrote: On Mon, 24 Oct 2011, Peter Hutterer wrote: On Fri, Oct 21, 2011 at 02:45:06PM +0200, Tamas Papp wrote: Hi, I just purchased an Intellipen Pro digital pen. It shows up fine in xinput list: [...] and button events are detected, but the cursor doesn't move. xinput test reveals that the X and Y axes are a[2] and a[3]: [...] Device 'EPOS EPOS Pen Digitizer.': Device Enabled (132): 1 Coordinate Transformation Matrix (134): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (257): 0 Device Accel Constant Deceleration (258): 1.00 Device Accel Adaptive Deceleration (259): 1.00 Device Accel Velocity Scaling (260):10.00 Evdev Axis Inversion (261): 0, 0 Evdev Axis Calibration (262): no items Evdev Axes Swap (263): 0 Axis Labels (264): Abs X (254), Abs Y (255), Abs Z (275), Abs Rotary X (276), Abs Pressure (485), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285), Abs Misc (285) Fairly common issue. The kernel needs a fix to enable HID_QUIRK_MULTI_INPUT for this device. Hi Peter, Thanks, that put me on the right track. I just had to create /etc/hal/fdi/policy/90-intellipen-pro.fdi with the contents ?xml version=1.0 encoding=UTF-8? deviceinfo version=0.2 device !-- Intellipen Pro -- match key=usb_device.vendor_id int=0x188c match key=usb_device.product_id int=0x221 merge key=input.x11_driver type=stringevdev/merge /match /match /device /deviceinfo and /etc/modprobe.d/intellipen.conf with options usbhid quirks=0x188c:0x0221:0x0040 and the device works perfectly. Where should I submit this information so that it gets incorporated to future updates so that others can just plug it in and have it work automatically? kernel bugzilla. I'd be easy enough to knock up a kernel patch that adds the quirk for this particular device, so if you can find the time to do that you're most likely to see the change happen. Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: xf86-video-intel-2.14.0 compilation error
On Mon, 2011-10-24 at 22:23 +0530, Dwijadas Dey wrote: Hi I have compiled and installed xorg-server-1.7.99.2 and now i am trying to compile xf86-video-intel-2.14.0 on centos 5.7 [kernel 2.6.39] using the following configure command Most of time what you have in system should be good enough. So why you want update centos 5.7 ? and what versions of x and intel-drv have 5.7? but if you want upgrade and do it right, you have to pack xorg-server-1.7.99.2 as rpm and replace the original that you have in system, you may grab a xorg-server.src.rpm and recompile for your system with rpmbuild --rebuild . compile xf86-video-intel-2.14.0 with /usr/local/x, is not a good idea. and why 1.7.99.2 , this is a release candidate ? Dwdy ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: ser...@serjux.com -- Sérgio M. B. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [PATCH] libpciaccess: close mtrr fd on pci_cleanup
On 10/24/2011 09:51 AM, Jeremy Huddleston wrote: While possibly safe in practice, this doesn't look like the correct fix. It is possible that this will result in a close(0) if HAVE_MTRR is defined and mtrr_fd was just never set. HAVE_MTRR is defined ifasm/mtrr.h exists. mtrr_fd is set if HAVE_MTRR is defined and linux_sysfs is used. Probably a trivial example of this would be to sudo touch /usr/include/asm/mtrr.h on FreeBSD. That is a valid point. I don't have a freebsd system to test it but based on code review I agree that what you say will happen. Would you suggest adding an #ifdef linux around the close or since the pci_sys structure is allocated with a calloc either directly or indirectly, I can change the condition to check for 0. Thanks, Nithin. On Oct 21, 2011, at 11:49, Nithin Nayak Sujir wrote: Since the fd is not closed, calling pci_system_init and pci_system_cleanup more than 1024 times results in too many files open error. Signed-off-by: Nithin Nayak Sujirnsu...@broadcom.com --- src/common_init.c |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/src/common_init.c b/src/common_init.c index 5e91c27..d7ade3f 100644 --- a/src/common_init.c +++ b/src/common_init.c @@ -31,7 +31,9 @@ #includestdlib.h #includeerrno.h +#includeunistd.h +#include config.h #include pciaccess.h #include pciaccess_private.h @@ -122,6 +124,10 @@ pci_system_cleanup( void ) (*pci_sys-methods-destroy)(); } +#ifdef HAVE_MTRR +if (pci_sys-mtrr_fd != -1) + close(pci_sys-mtrr_fd); +#endif free( pci_sys ); pci_sys = NULL; } -- 1.7.1 ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: jerem...@freedesktop.org ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
