Errors with fbdev and nvidia. Cannot run in framebuffer mode.
Hello there, I want to use DisplayLink devices with fbdev and my two monitors connected to the internal Nvidia card of my laptop. But I get an error Cannot run in framebuffer mode Attached are my Xorg.0.log.old and the xorg.conf. Section ServerLayout Identifier Layout0 Screen 0 DLScreenLeft 0 0 Screen 1 TopScreen RightOf DLScreenLeft Screen 2 DLScreenRight RightOf TopScreen Screen 3 MacbookScreen Below TopScreen InputDeviceKeyboard0 CoreKeyboard InputDeviceMouse0 CorePointer Option Xinerama off EndSection Section Module #Disableglx #Disable nvidia EndSection Section Files ModulePath /usr/lib/xorg/modules ModulePath /usr/local/lib/xorg/modules EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/psaux Option Emulate3Buttons no Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section Monitor Identifier Monitor0 VendorName Unknown ModelName Apple Color LCD HorizSync 30.0 - 75.0 VertRefresh 60.0 Option DPMS EndSection Section Device Identifier Device0 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce 9600M GT BusID PCI:2:0:0 Screen 0 Option NoLogo EndSection Section Screen Identifier MacbookScreen Device Device0 MonitorMonitor0 DefaultDepth24 Option TwinView 0 SubSection Display Depth 24 Modes 1920x1200_60.00 EndSubSection EndSection Section Monitor Identifier Monitor1 VendorName Unknown ModelName SyncMaster 2443 HorizSync 30.0 - 75.0 VertRefresh 60.0 Option DPMS EndSection Section Device Identifier Device1 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce 9600M GT BusID PCI:2:0:0 Screen 1 Option NoLogo EndSection Section Screen Identifier TopScreen Device Device1 MonitorMonitor1 DefaultDepth24 Option TwinView 0 SubSection Display Depth 24 Modes 1920x1200_60.00 EndSubSection EndSection DisplayLink Stuff ### Section Device Identifier DLDeviceLeft Driver fbdev BusID USB Option fbdev /dev/fb1 #OptionReportDamage true Option rotate CCW EndSection Section Monitor Identifier DLMonitorLeft EndSection Section Screen Identifier DLScreenLeft Device DLDeviceLeft Monitor DLMonitorLeft DefaultDepth16 EndSection Section Device Identifier DLDeviceRight Driver fbdev BusID USB Option fbdev /dev/fb2 #OptionReportDamage true Option rotate CCW EndSection Section Monitor Identifier DLMonitorRight EndSection Section Screen Identifier DLScreenRight Device DLDeviceRight Monitor DLMonitorRight DefaultDepth16 EndSection [ 4906.211] X.Org X Server 1.11.1 Release Date: 2011-09-24 [ 4906.212] X Protocol Version 11, Revision 0 [ 4906.212] Build Operating System: Linux 3.0-ARCH x86_64 [ 4906.212] Current Operating System: Linux caffeine 3.0-ARCH #1 SMP PREEMPT Fri Oct 7 11:35:34 CEST 2011 x86_64 [ 4906.212] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/sda3 ro nomodeset quiet reboot=pci [ 4906.213] Build Date: 10 October 2011 08:55:30AM [ 4906.213] [ 4906.214] Current version of pixman: 0.22.2 [ 4906.214]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 4906.215] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4906.217] (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 2 11:25:40 2011 [ 4906.218] (==) Using config file: /etc/X11/xorg.conf [ 4906.218] (==) Using config directory: /etc/X11/xorg.conf.d [ 4906.218] (==) ServerLayout Layout0 [ 4906.218] (**) |--Screen DLScreenLeft (0) [ 4906.218] (**) | |--Monitor DLMonitorLeft [ 4906.219] (**) | |--Device DLDeviceLeft [ 4906.219] (**) |--Screen TopScreen (1) [ 4906.219] (**) | |--Monitor Monitor1 [ 4906.219] (**) | |--Device Device1 [ 4906.219] (**) |--Screen DLScreenRight (2) [ 4906.219] (**) | |--Monitor DLMonitorRight [ 4906.219] (**) | |--Device DLDeviceRight [ 4906.219] (**) |--Screen MacbookScreen (3) [ 4906.219] (**) | |--Monitor Monitor0 [ 4906.219] (**) | |--Device Device0 [
[ANNOUNCE] xf86-video-ati 6.14.3
I'm pleased to announce the 6.14.3 release of the xf86-video-ati (radeon) driver. Thanks to everybody who contributed! Highlights: * Support for more cards, in particular Llano APUs. * KMS page flipping fixes. * vdpau/XvMC support (currently only available for = R3xx via Gallium3D). * Tiling fixes, enable it on more cards by default. Changes since 6.14.2: Alex Deucher (14): radeon: add support for llano APUs radeon: add llano pci ids kms: enable ColorTiling by default on r6xx-cayman asics kms/man: update ColorTiling info dri2/eg+: fix size and alignment of depth/stencil buffers dri2: missing bit from a6154c00c64932332e8f6e334661ffd579cfd894 dri2: fix copy pasto in a6154c00c64932332e8f6e334661ffd579cfd894 evergreen: fix num_banks for 2D tiling config radeon: add some new NI pci ids kms: fix possible leak in pageflip code r5xx+: Fix vline setup with crtc offsets update man page with new marking names man: note that the list of marketing names is non-exhaustive UMS: fix DDIA enable on some rs690 systems Christian König (1): Register XvMC video decoding acceleration Dave Airlie (2): bump version after release evergreen: Emit SQ_LDS_RESOURCE_MGMT Jeremy Huddleston (2): Use malloc/calloc/realloc/free directly Build fix for -Werror=int-to-pointer-cast Jerome Glisse (1): radeon/kms: fallback to vesa if GPU is not supported by UMS Maarten Lankhorst (1): dri2: Add vdpau driver name entry Michel Dänzer (12): Prefer the CRTC of the primary output for synchronization. Change my e-mail address to something that still works, and always will, I hope. video: Don't round up bottom/right edge for clipping source width/height. Bail if we're trying to start up in UMS mode on KMS. Convert register ranges for = r6xx from enums to defines. KMS Color Tiling requires xserver which supports EXA_MIXED_PIXMAPS. Remove dead variable remain_size_bytes. Only call radeon_dri2_close_screen() if DRI2 was enabled. Make radeon_dri2_create_buffer(s) more robust. (Bug #30047) EXA R6xx: Make sure 2D state is re-emitted after running out of CS space. EXA = R6xx / KMS: Avoid running out of CS space at inconvenient times. Bump version for 6.14.3 release. Tormod Volden (1): radeon: do not include xf86PciInfo.h Ville Syrjala (2): dri2: Update front buffer pixmap and name before exchanging buffers kms: Move flip_count and co. to a per swap structure git tag: xf86-video-ati-6.14.3 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-6.14.3.tar.bz2 MD5: 19126c8421a05d9605883dcf7498d876 xf86-video-ati-6.14.3.tar.bz2 SHA1: db635e2e2858d5db90362f546ac0adad85474bad xf86-video-ati-6.14.3.tar.bz2 SHA256: 844a2649eff6a3e92aff3e1837ea864f1561b4822b3e5d5ccb27b3b7fb8137b4 xf86-video-ati-6.14.3.tar.bz2 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-6.14.3.tar.gz MD5: c5e9ebdf3f68349eb68d72c170888325 xf86-video-ati-6.14.3.tar.gz SHA1: 9d13845e192108f41cb536d03e9e9bf8685ec7a2 xf86-video-ati-6.14.3.tar.gz SHA256: 12be0ec960f2d700fd259ab5eec2a1c7a0564ec7fa057502a3457ca4e97ad334 xf86-video-ati-6.14.3.tar.gz -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer 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
Simulating a mouse click
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. 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: arch...@mail-archive.com
XRandR EDID missed with Cedar on LVDS
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. 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 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 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
