Re: Exclusive Fullscreen Mode
Roland Plüss wrote: I tried searching on the Internet for informations on how to take over the screen using Xlib. I think here about fullscreen exclusive access like for example SDLMAME does it. I stumbled so far though only on one single mentioning of an Xlib call which should allow switching a window into a FullscreenExclusiveMode. I could though find nothing about such a call nor this FullscreenExclusiveMode. Has anybody an idea what this FullscreenExclusiveMode could be or in general how one can make a window take over the entire screen? Not sure if this is what you're looking for, but I use wmctrl to set the window size and then to nail it on top. It's a window manager function to manage the size and location of windows. --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ 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
Manipulate x windows
OK, I know this is more of a WM question... I'm looking for a CLI utility that would let me manipulate (resize and relocate) windows based on WM_NAME or WM_CLASS. Is anyone aware of any such thing? I need to open a window and position it - but the app does not fully support the -geometry option. It only allows me to set the size and not the location (in other words, it ignores the +X+Y portion of the HxW+X+Y string.) Thanks, --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ 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, h264 and XvMC
Terry Barnaby wrote: On 04/04/10 05:23, Nikos Chantziaras wrote: On 04/04/2010 06:30 AM, Yan Seiner wrote: I'm trying to understand if Intel XvMC can be used with h264 material. If not, is there any way to use Intel hardware acceleration with h264 source? VA-API does h264 bitstream decoding on the GPU, not XvMC. XvMC is only for motion compensation (which is what MC stands for.) There are extensions to XvMC however, for Via and other chipsets that allow at least MPEG2 streams to be sent to the GPU for higher level hardware decode. XvMC isn't really suited to this though, hence the newer schemes. Actually Intel developers, is there any news of providing hardware H264/MPEG2 decoding via an API for Linux on the G45 graphics chipset ? I've heard unsubstantiated rumours of possible VDPAU support.. That would be sweet! It would make intel chipsets competitive with nvidia ion for video playback. Any truth to those rumours? --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Error building intel driver
I'm getting the following error building the intel driver. I've cleaned out all of the old code, cloned the git repositories, and started fresh to make sure it's not some old cruft. Does anyone have any idea what I'm missing? libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -fvisibility=hidden -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/libdrm -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -Wold-style-definition -Wdeclaration-after-statement -fvisibility=hidden -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/libdrm -I/usr/local/include/X11/dri -I/usr/local/include -I/usr/local/include -I../uxa -I../src/render_program -g -O2 -MT i830_video.lo -MD -MP -MF .deps/i830_video.Tpo -c i830_video.c -fPIC -DPIC -o .libs/i830_video.o i830_video.c: In function ‘drmmode_has_overlay’: i830_video.c:219: error: ‘I915_PARAM_HAS_OVERLAY’ undeclared (first use in this function) i830_video.c:219: error: (Each undeclared identifier is reported only once i830_video.c:219: error: for each function it appears in.) i830_video.c: In function ‘drmmode_overlay_update_attrs’: i830_video.c:230: error: storage size of ‘attrs’ isn’t known i830_video.c:233: error: ‘I915_OVERLAY_UPDATE_ATTRS’ undeclared (first use in this function) i830_video.c:245: error: ‘DRM_I915_OVERLAY_ATTRS’ undeclared (first use in this function) i830_video.c:230: warning: unused variable ‘attrs’ i830_video.c: In function ‘drmmode_overlay_off’: i830_video.c:255: error: storage size of ‘request’ isn’t known i830_video.c:260: error: ‘DRM_I915_OVERLAY_PUT_IMAGE’ undeclared (first use in this function) i830_video.c:255: warning: unused variable ‘request’ i830_video.c: In function ‘drmmode_overlay_put_image’: i830_video.c:276: error: storage size of ‘request’ isn’t known i830_video.c:281: error: ‘I915_OVERLAY_ENABLE’ undeclared (first use in this function) i830_video.c:319: error: ‘I915_OVERLAY_YUV_PLANAR’ undeclared (first use in this function) i830_video.c:319: error: ‘I915_OVERLAY_YUV420’ undeclared (first use in this function) i830_video.c:321: error: ‘I915_OVERLAY_YUV_PACKED’ undeclared (first use in this function) i830_video.c:321: error: ‘I915_OVERLAY_YUV422’ undeclared (first use in this function) i830_video.c:323: error: ‘I915_OVERLAY_Y_SWAP’ undeclared (first use in this function) i830_video.c:326: error: ‘DRM_I915_OVERLAY_PUT_IMAGE’ undeclared (first use in this function) i830_video.c:276: warning: unused variable ‘request’ make[3]: *** [i830_video.lo] Error 1 make[3]: Leaving directory `/home/src/xorg/xorg/driver/xf86-video-intel/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/src/xorg/xorg/driver/xf86-video-intel/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/src/xorg/xorg/driver/xf86-video-intel' make: *** [all] Error 2 -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Error building intel driver
Julien Cristau wrote: On Sat, Apr 3, 2010 at 07:22:48 -0700, Yan Seiner wrote: I'm getting the following error building the intel driver. I've cleaned out all of the old code, cloned the git repositories, and started fresh to make sure it's not some old cruft. Does anyone have any idea what I'm missing? You need newer drm headers (i915_drm.h), either from a recent libdrm or from linux 2.6.33. HAH! Thanks. I had conflicting headers, in drm/i915_drm.h and libdrm/i915_drm.h . Deleted the older headers in drm and all is well. --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Intel, h264 and XvMC
I'm trying to understand if Intel XvMC can be used with h264 material. If not, is there any way to use Intel hardware acceleration with h264 source? Thanks. --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Building intel driver: where's xcb-aux?
OK, dumb question perhaps... I'm trying to build the intel driver, and it's failing to build with XvMC support because it can't find xcb-aux: configure:14233: checking for XVMCLIB configure:14241: $PKG_CONFIG --exists --print-errors xvmc xext xfixes dri2proto x11-xcb xcb-dri2 xcb-aux Package xcb-aux was not found in the pkg-config search path. Perhaps you should add the directory containing `xcb-aux.pc' to the PKG_CONFIG_PATH environment variable No package 'xcb-aux' found configure:14244: $? = 1 configure:14259: $PKG_CONFIG --exists --print-errors xvmc xext xfixes dri2proto x11-xcb xcb-dri2 xcb-aux Package xcb-aux was not found in the pkg-config search path. Perhaps you should add the directory containing `xcb-aux.pc' to the PKG_CONFIG_PATH environment variable No package 'xcb-aux' found configure:14262: $? = 1 No package 'xcb-aux' found configure:14290: result: no configure:14303: checking whether to include XvMC support configure:14305: result: no However, git.freedisktop.git doesn't seem to know anything about xcb-aux How do I build the latest intel driver with XvMC support? -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Xephyr + wacom
Anyone know how I'd go about setting up Xephyr with a wacom tablet? I have a tablet that's recognized by the system, I have a pretty recent wacom driver, and I can't figure out how to get Xephyr to do anything with it. I run dual-head, and I need the wacom tablet attached to one head. I'm also having an issue with Xephyr logging. I get no logs at all (Xorg.N.log is never created). Of course, this is on the machine that I need wacom support. The other machine that runs the same setup logs Xephyr stuff just fine. -- If you have eight hours to chop down a tree spend six sharpening your axe. --Abraham Lincoln ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Xephyr problems
I just built the latest xorg from git. I'm having a problem with xkblayout; all of the keys show up as one off - 'a' produces 's', 'tab' produces 'enter', and so on. Also, I can't get Xephyr to produce a log file. How do I get Xephyr to create a log file? I have another, similar machine with a slightly older installation of Xorg where the keyboard works and the the log file is produced and I can't figure out why it's not working here. root 3542 0.1 0.8 77160 17204 tty7 SLs+ 07:36 0:03 /usr/local/bin/X :0 -config /etc/mdm/xorg.conf.mdm -noreset -ignoreABI -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 root 3690 0.4 1.1 96144 23888 ?S07:37 0:12 /usr/local/bin/Xephyr :1 -br :1 -parent 0x22 -mouse evdev,,device=/dev/input/event7 -keybd evdev,,device=/dev/input/event1,xkbmodel=evdev,xkblayout=us -auth /var/lib/gdm/:1.Xauth -nolisten tcp vt9 -verbosity 255 root 4133 0.0 1.1 96996 24720 ?S07:45 0:02 /usr/local/bin/Xephyr :2 -br :2 -parent 0x42 -mouse evdev,,device=/dev/input/event4 -keybd evdev,,device=/dev/input/event3,xkbmodel=evdev,xkblayout=us -auth /var/lib/gdm/:2.Xauth -nolisten tcp vt8 -verbosity 255 [61.425] X.Org X Server 1.7.99.3 Release Date: (unreleased) [61.425] X Protocol Version 11, Revision 0 [61.425] Build Operating System: Linux 2.6.26-1-amd64 x86_64 [61.425] Current Operating System: Linux athena 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64 [61.425] Kernel command line: root=/dev/sda1 ro quiet [61.425] Build Date: 07 February 2010 06:18:52AM [61.425] [61.425] Current version of pixman: 0.17.5 [61.425] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xephyr problems
Yan Seiner wrote: I just built the latest xorg from git. I'm having a problem with xkblayout; all of the keys show up as one off - 'a' produces 's', 'tab' produces 'enter', and so on. Never mind Turns out I was not installing the xkb database in the right place. Problem solved. (Xephyr expects it at /opt/gfx-test rather than$PREFIX.) --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
git repostory for font-utils
I apologize for my mental weakness today I embarked on building the latest and greatest xorg, and I can't find the git repository for font-util. I'm not an xorg developer, so I don't know my way around http://cgit.freedesktop.org/ as well as I should. All I've found is this announcement: http://lwn.net/Articles/356547/ but I can't figure out where the git repo is. Thanks, --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: CT ct65545 problem
Egbert Eich wrote: On Tue, Oct 27, 2009 at 10:33:42AM -0400, Adam Jackson wrote: That's not how the ISA bus support works (well, worked). Since ISA is not an enumerable bus, we would assume that if no PCI device was claimed by any driver then the video card must be out on ISA somewhere. So, there's a cascade of failures here. The PCI probe support was broken, so the driver would (brokenly) not claim any PCI devices. Then the server would assume ISA, and the driver would (rightly) not find any ISA devices. Again: update your chips driver, the 65545 really is a PCI device as far as I know, and newer chips drivers should have fixed the detection bug. The 65545 was a transition chipset which could be used on ISA, VL and PCI systems. This particular laptop is ISA with a couple of PCMCIA 1 (16 bit) slots. The video is on the ISA bus. The chips driver (1.2.1 and 1.2.2) doesn't work in this configuration at all, exiting with the error given previously. However, the VESA driver works just fine. It assumes a 24 bit depth and fails as the hardware only supports 8 bits. Once it's told to use defaultdepth of 8, it correctly sees the CT chipset and initializes the screen just fine. --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: CT ct65545 problem
David Gerard wrote: 2009/10/27 Yan Seiner y...@seiner.com: This particular laptop is ISA with a couple of PCMCIA 1 (16 bit) slots. The video is on the ISA bus. The chips driver (1.2.1 and 1.2.2) doesn't work in this configuration at all, exiting with the error given previously. However, the VESA driver works just fine. It assumes a 24 bit depth and fails as the hardware only supports 8 bits. Once it's told to use defaultdepth of 8, it correctly sees the CT chipset and initializes the screen just fine. Can this sort of thing be detected and special-cased? (Should it? Would this be an appropriate method of supporting ye crusty olde chips?) Not sure if the effort is worth it for 15 year old hardware Wouldn't surprise me if I'm one of less than a dozen who still has this stuff in working order. OTOH, X is being used more and more on embedded platforms, so it wouldn't hurt to have a DefaultDepth fallback - if 24 doesn't work, try 16, if that doesn't work, try 8. --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: CT ct65545 problem
Adam Jackson wrote: On Tue, 2009-10-27 at 11:40 -0700, Yan Seiner wrote: Not sure if the effort is worth it for 15 year old hardware Wouldn't surprise me if I'm one of less than a dozen who still has this stuff in working order. OTOH, X is being used more and more on embedded platforms, so it wouldn't hurt to have a DefaultDepth fallback - if 24 doesn't work, try 16, if that doesn't work, try 8. The vesa driver has that already, in a sense: depths = VBEFindSupportedDepths(pVesa-pVbe, pVesa-vbeInfo, flags24, V_MODETYPE_VBE); /* Preferred order for default depth selection. */ if (depths V_DEPTH_24) defaultDepth = 24; else if (depths V_DEPTH_16) defaultDepth = 16; else if (depths V_DEPTH_15) defaultDepth = 15; /* ... */ So we should do the right thing, if the BIOS is polite enough to not lie to us. Of course, it could be lying. Having the _server_ retry successively smaller depths is a fair idea, but really hard to implement given the way driver setup works right now, and fixing it sort of requires fixing all the drivers in the same pass. - ajax fwiw, here's the log file. The auto fallback doesn't work on this hardware (not surprising, the bios is very, very weird.) --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! (WW) Failed to open protocol names file /usr/lib/xorg/protocol.txt X.Org X Server 1.5.1 Release Date: 23 September 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30 x86_64 Current Operating System: Linux OpenWrt 2.6.31.5 #3 Tue Oct 27 09:54:25 PDT 2009 i486 Build Date: 26 October 2009 07:22:40PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Sat Dec 4 22:06:53 1943 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard0 (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (==) FontPath set to: built-ins (==) ModulePath set to /usr/lib/xorg/modules (WW) Duplicate core pointer devices. Removing core pointer attribute from Mouse1 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Loader magic: 0x81a16a4 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (--) using VT number 2 (II) System resource ranges: (II) extmod will be loaded. This was enabled by default and also specified in the config file. (II) dbe will be loaded. This was enabled by default and also specified in the config file. (II) glx will be loaded by default. (II) freetype will be loaded. This was enabled by default and also specified in the config file. (II) dri will be loaded by default. (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.5.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.1 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.5.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.1 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension XC-MISC (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: fbdevhw (II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so (II) Module fbdevhw: vendor=X.Org Foundation compiled for 1.5.1, module version = 0.0.2 ABI class: X.Org Video Driver, version 4.1 (II) LoadModule: record (WW) Warning, couldn't open module record (II) UnloadModule: record (EE) Failed to load module record (module does not exist, 0) (II) LoadModule: freetype (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so (II) Module freetype: vendor=X.Org Foundation the After X-TT Project compiled for 1.5.1, module
More old hardware weirdness....
I'm trying to resurrect this laptop, and I'm running into all sorts of issues... Now that I have X running, but I can't get the keyboard to work in X. If I configure things the way I always do,I get nothing. (see below for xorg.conf snippet.) /dev/input/event? stuff works AFAICT - I can cat the devices and when I type junk appears. No errors in the log files. To eliminate WM weirdness, I am running X DISPLAY :0 xterm Not ideal, but the results are the same if I run a WM. I get a slew of warnings from xkbcomp: expected keysym, got XF86Forward: line 45 of inet expected keysym, got XF86Back: line 46 of inet expected keysym, got XF86MyComputer: line 47 of inet expected keysym, got XF86Mail: line 48 of inet expected keysym, got XF86AudioMedia: line 49 of inet expected keysym, got XF86PowerOff: line 55 of inet expected keysym, got XF86Standby: line 56 of inet expected keysym, got XF86WakeUp: line 57 of inet expected keysym, got XF86AudioMute: line 89 of inet expected keysym, got XF86AudioLowerVolume: line 90 of inet expected keysym, got XF86AudioRaiseVolume: line 91 of inet But all of them appear to be non-standard key definitions. and then I get the only indication of something wrong: Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default Warning: Cannot convert string nil2 to type FontStruct Failed to open input method I've googled the Failed to open input method and get absolutely nothing that could shed any light on this. Here's my keyboard: Section InputDevice Identifier Keyboard0 Driver evdev OptionDevice /dev/input/event0 EndSection If I use evdev, I get nothing at all from the keyboard. If I use the keyboard driver with the evdev device, I get slews of garbage. Here's dmesg: r...@openwrt:/etc/X11# dmesg | grep input input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input1 So the keyboard is definitely a normal keyboard. It works fine in text mode. vt switch doesn't work; zapping does. -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: More old hardware weirdness....
Yan Seiner wrote: I'm trying to resurrect this laptop, and I'm running into all sorts of issues... Now that I have X running, but I can't get the keyboard to work in X. If I configure things the way I always do,I get nothing. (see below for xorg.conf snippet.) /dev/input/event? stuff works AFAICT - I can cat the devices and when I type junk appears. No errors in the log files. To eliminate WM weirdness, I am running X DISPLAY :0 xterm Not ideal, but the results are the same if I run a WM. I get a slew of warnings from xkbcomp: expected keysym, got XF86Forward: line 45 of inet expected keysym, got XF86Back: line 46 of inet expected keysym, got XF86MyComputer: line 47 of inet expected keysym, got XF86Mail: line 48 of inet expected keysym, got XF86AudioMedia: line 49 of inet expected keysym, got XF86PowerOff: line 55 of inet expected keysym, got XF86Standby: line 56 of inet expected keysym, got XF86WakeUp: line 57 of inet expected keysym, got XF86AudioMute: line 89 of inet expected keysym, got XF86AudioLowerVolume: line 90 of inet expected keysym, got XF86AudioRaiseVolume: line 91 of inet But all of them appear to be non-standard key definitions. and then I get the only indication of something wrong: Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default Warning: Cannot convert string nil2 to type FontStruct Failed to open input method I've googled the Failed to open input method and get absolutely nothing that could shed any light on this. Here's my keyboard: Section InputDevice Identifier Keyboard0 Driver evdev OptionDevice /dev/input/event0 EndSection If I use evdev, I get nothing at all from the keyboard. If I use the keyboard driver with the evdev device, I get slews of garbage. Here's dmesg: r...@openwrt:/etc/X11# dmesg | grep input input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input1 So the keyboard is definitely a normal keyboard. It works fine in text mode. vt switch doesn't work; zapping does. Forgot to add: Here's what the log file says about the input devices: (**) Option Protocol PS/2 (**) Mouse0: Device: /dev/psaux (**) Mouse0: Protocol: PS/2 (**) Option CorePointer (**) Mouse0: always reports core events (**) Option Device /dev/psaux (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 9 (**) Mouse0: Sensitivity: 1 (**) Option CoreKeyboard (**) Keyboard0: always reports core events (**) Keyboard0: Device: /dev/input/event0 (II) Keyboard0: Found keys (II) Keyboard0: Configuring as keyboard (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD) (**) Option xkb_rules base (**) Keyboard0: xkb_rules: base (**) Option xkb_model evdev (**) Keyboard0: xkb_model: evdev (**) Option xkb_layout us (**) Keyboard0: xkb_layout: us (**) Option Device /dev/psaux (II) Mouse0: ps2EnableDataReporting: succeeded -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: More old hardware weirdness....
David Gerard wrote: 2009/10/27 Yan Seiner y...@seiner.com: Now that I have X running, but I can't get the keyboard to work in X. If I configure things the way I always do,I get nothing. (see below for xorg.conf snippet.) Does it work with an external keyboard? Just tested. No joy. But I suspect that the external keyboard is slaved to the internal keyboard; both keyboards work but no new device shows up in dmesg or /dev/input --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: CT ct65545 problem
Tiago Vignatti wrote: Yan Seiner wrote: I have a very, very old laptop - 1995 vintage - that I want to repurpose for a net-terminal. It has a Chips and Technologies 65545 video chipset. This works with X as I've run it in the past with both freeBSD and an older version of linux (something with a 2.4 kernel and an old version of xfree.) I decided to upgrade this to a current version to get some net tools. Now I can't get X to recognize the CT chipset. I am using xorg 7.4, with the chips driver. X fails with: (II) Primary Device is: ISA (EE) No devices detected Unfortunately I don't have pcmcia working either so I can't copy and paste quite yet. I suspect that the driver cannot auto-probe the ISA bus and it's looking for some sort of IRQ or base address. But how do I go about finding this? I don't recall having to do anything special in the past, but who knows recently versions of the server don't support ISA anymore. Well, after some trial and error, I got vesa to work for X and framebuffer to work for text screens. (For some reason, X Frame buffer won't work, but as the hardware is 15 years old, it's not worth fixing.) --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
CT ct65545 problem
I have a very, very old laptop - 1995 vintage - that I want to repurpose for a net-terminal. It has a Chips and Technologies 65545 video chipset. This works with X as I've run it in the past with both freeBSD and an older version of linux (something with a 2.4 kernel and an old version of xfree.) I decided to upgrade this to a current version to get some net tools. Now I can't get X to recognize the CT chipset. I am using xorg 7.4, with the chips driver. X fails with: (II) Primary Device is: ISA (EE) No devices detected Unfortunately I don't have pcmcia working either so I can't copy and paste quite yet. I suspect that the driver cannot auto-probe the ISA bus and it's looking for some sort of IRQ or base address. But how do I go about finding this? I don't recall having to do anything special in the past, but who knows --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Intel Option TV_Connector ignored
I'm having trouble getting TV out working reliably. It will sometimes work and sometimes not; depends on the monitor attached. If I connect a video amplifier/splitter, it the TV-Out will show up as disconnected. If I connect a monitor, it will show us as connected. If I start X with the monitor, and change the plugs around and plug in the amplifier, it will work just fine. I built the lastet xorg from trunk, as the intel driver has been under heavy development. In particular, this item on the intel manpage caught my eye: TV_Connector - connector type This config option should be added to xorg.conf TV monitor’s section, it allows you to force the TV output connector type, which bypass load detect and TV will always be taken as connected. You can select between S-Video, Composite and Components Alas, it's being ignored. I've tried every combination of TV_Connector, TV-connector, TV-1_connector, and so on; nothing turns on the TV out unless the monitor is plugged in. I'm attaching various bits of log files, as well as a diff of the disconnected and connected Xorg log files. I'm willing to test and do what I can; but I really need this working if at all possible. Thanks! r...@mythtvrt:/usr/local/var/log# Xorg -version This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.7.99.1 Release Date: (unreleased) X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31.1 i686 Current Operating System: Linux mythtvrt 2.6.31.1 #2 SMP Thu Oct 1 19:45:02 PDT 2009 i686 Kernel command line: root=UUID=85c7c288-b547-4634-8e1d-6c1f677555f7 ro quiet splash Build Date: 02 October 2009 01:56:11PM Current version of pixman: 0.17.1 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) **Section Monitor Identifier TV VendorName Monitor Vendor ModelName Monitor Model Option TV-FORMAT NTSC-M Option TV_Connector S-Video HorizSync 30.0 - 60.0 VertRefresh 60 EndSection r...@mythtvrt:/usr/local/var/log# ls Xorg.0.log Xorg.0.log.conn Xorg.0.log.disc Xorg.0.log.old r...@mythtvrt:/usr/local/var/log# diff *disc *conn 24c24 (==) Log file: /usr/local/var/log/Xorg.0.log, Time: Fri Oct 2 18:18:10 2009 --- (==) Log file: /usr/local/var/log/Xorg.0.log, Time: Fri Oct 2 18:19:30 2009 226a227 (II) intel(0): Output TV-1 using monitor section TV 228,230c229,232 (II) intel(0): Output TV-1 disconnected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output VGA using initial mode 1680x1050 --- (II) intel(0): Output TV-1 connected (II) intel(0): Using fuzzy aspect match for initial modes (II) intel(0): Output VGA using initial mode 1280x960 (II) intel(0): Output TV-1 using initial mode 1280x960 236c238 (**) intel(0): DPI set to (104, 102) --- (**) intel(0): DPI set to (79, 93) 245c247 (WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x to 0x0303 --- (WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x to 0x8303 247c249 (WW) intel(0): PIPEASTAT after: status: VSYNC_INT_STATUS DLINE_COMPARE_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS --- (WW) intel(0): PIPEASTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS DLINE_COMPARE_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS 277c279 (II) intel(0): 0x0100-0x01ff: front buffer (16384 kB) X tiled --- (II) intel(0): 0x0080-0x00ff: front buffer (8192 kB) X tiled 280a283,287 output modeline: (II) intel(0): Modeline 1280x960x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz) input modeline: (II) intel(0): Modeline 1280x960x60.0 119.47 1280 1389 1421 1716 960 1023 1025 1170 +hsync +vsync (69.6 kHz) (II) intel(0): SDVOB: Choosing default TV format of NTSC-M 284,285c291,292 (II) intel(0): Pipe B is off (II) intel(0): Display plane B is now disabled and connected to pipe B. --- (II) intel(0): Pipe B is on (II) intel(0): Display plane B is now enabled and connected to pipe B. 287c294 (II) intel(0): Output TV-1 is connected to pipe none --- (II) intel(0): Output TV-1 is connected to pipe B 318c325 (II) intel(0): Setting screen physical size to 444 x 277 --- (II) intel(0): Setting screen physical size to 338 x 253 -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride!
GMA945 TV-1 disconnected
I've been trying to bring up a machine that's driving an analog tv. The machine is using the GMA 945 chipset. X sees the TV out, but the log file says TV-1 disconnected and the TV shows No Signal. I can get a signal all the way through the boot sequence up until X starts. Unfortunately this machine is not networked ATM so I'm not able to reproduce log files. (Long story; backordered on wifi antennas) Is there a sample xorg.conf file that shows me how to force X to use the TV out, and tell it to use NTSC? Thanks, --Yan -- o__ ,/'_ o__ (_)\(_) ,/'_ o__ A day may come (_)\(_) ,/'_ o__ when the courage of men fails, (_)\(_) ,/'_ when we forsake our friends and break all (_)\(_) bonds of fellowship, but it is not this day. It is not this day! This day we ride! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Only use part of display..?
On Fri, April 24, 2009 3:39 pm, Danny Ayers wrote: Slightly odd request - the display on my EeePC got damaged (left it in the car in winter - literally frozen I believe) so now the pixels in the top RH corner are screwed (lovely snowflake pattern). So I was wondering if I could tell X to use only the LH 7/8 of the display. Run Xephyr on top of a blank X server? -- Yan Seiner, PE Support my bid for the 4J School Board http://www.seiner.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Multiple keyboards with Xephyr
Is there any documentation for Xephyr? It doesn't seem to have a manpage... I'm trying to find out if I can use multiple keyboards with Xephyr. I'd like to be able to connect a standard keyboard and a usb remote control. The remote looks like a keyboard to the system and sends ordinary keystrokes. --Yan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Weird corruption with Xephyr
I'm seeing this rather weird corruption with Xephyr. The system is running Debian Lenny with a custom 2.6.27.4 kernel. I am running Xephyr 1.5.3. I've captured an image of this here: http://seiner.com/images/imga0018.jpg This happens after some time - can be minutes, hours or days. The screen just flickers and then wraps right a lot and down very slightly. You can see it in the poor quality image above (sorry for the poor quality image. That was shot with a handheld video camera). This has happened on 2 of the 3 Xephyr servers so far. It doesn't appear to be video driver related; I've been running various versions of nvidia binary blob driver for a while now. I have updated Xephyr from 1.5.1, and the problem appears since then. A second machine, which has the same video hardware, and still runs 1.5.1, doesn't exhibit the problem. I've been through all the logs I can find, and there is nothing at all out of the ordinary in any of them. I've considered hardware failure, but the problem occurs on both video cards in the system, so it's unlikely that both would fail at the same time in the same way. Is there some way to get Xephyr to generate verbose logs to try and capture this? Any other suggestions? --Yan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Weird corruption with Xephyr
Aaron Plattner wrote: On Thu, Dec 11, 2008 at 07:50:41AM -0800, Yan Seiner wrote: I'm seeing this rather weird corruption with Xephyr. The system is running Debian Lenny with a custom 2.6.27.4 kernel. I am running Xephyr 1.5.3. I've captured an image of this here: http://seiner.com/images/imga0018.jpg This happens after some time - can be minutes, hours or days. The screen just flickers and then wraps right a lot and down very slightly. You can see it in the poor quality image above (sorry for the poor quality image. That was shot with a handheld video camera). This has happened on 2 of the 3 Xephyr servers so far. This actually does sound like a bug in the driver to me. Please run nvidia-bug-report.sh after reproducing the problem and send the resulting nvidia-bug-report.log file to linux-b...@nvidia.com. OK, the issue appeared with 180.11, 177.82, and 177.67. I've downgraded to Xephyr 1.5.0 which doesn't appear to have the problem (yet). If it's stable, I'll switch back to 1.5.3 and 177.82 and see if I can reproduce it. It may be a while as I am about to go on vacation and be away from all this until after New Year. :-) The reason I suspect Xephyr is that it doesn't appear to happen on screens adjacent to the broken one. In other words, on a dual DVI, single GPU card, I'd expect both outputs to be corrupt. Not so. It happens independently on each head, regardless of whether they share the GPU or not. --Yan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xephyr + DRI
On Thu, December 4, 2008 8:39 am, Julien Cristau wrote: On Thu, Dec 4, 2008 at 07:44:40 -0800, Yan Seiner wrote: Before I go off on a wild goose chase, is DRI possible with Xephyr? I am using 1.5.3 from Debian experimental. I disabled it in our 1.5.1 packages, because it didn't seem to work when I tried it anyway (bug#16955). If it works for other people it's easy to reenable... After reading that bug, is there some runtime setting that I can use as a workaround (provided, of course, that DRI is enabled in the first place?) I'd like to do some experimenting with DRI/GLX/VDPAU --Yan -- o__ ,/'_ o__ (_)\(_),/'_o__ Yan Seiner (_)\(_) ,/'_ o__ Personal Trainer (_)\(_),/'_o__ Professional Engineer (_)\(_) ,/'_ Who says engineers have to be pencil necked geeks? (_)\(_) You are an adult when you realize that everyone's an idiot sometimes. You are wise when you include yourself. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
xset dpms force off
I am running a multi-head setup. I'd like to be able to turn off each head individually. I'm using the evil binary nvidia drivers to set up 4 screens as DISPLAY 0.0, 0.1, 0.2, and 0.3 I'm not using Xinerama or Twinview. xset -display :0.0 dpms force off turns off all 4 displays, as does xset -display :0.1 dpms force off and so on. Any way to reach in and turn off a particular display? Anyone know if this is possible with nouveau? Thanks, --Yan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Xephyr, DRI, and compiz
? -- o__ ,/'_ o__ (_)\(_),/'_o__ Yan Seiner (_)\(_) ,/'_ o__ Personal Trainer (_)\(_),/'_o__ Professional Engineer (_)\(_) ,/'_ Who says engineers have to be pencil necked geeks? (_)\(_) As long as nobody gets hurt, a decent explosion livens up any experiment. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Building X
Keith Packard wrote: Yes, I'm cool with the black root background; nicer looking, conforming to the spec and everything. As a X user and occasional embedded programmer, might I suggest something with a pattern? Even if it's a X logo in the center, or just a shapeless blob, or a row and column of white pixels. Anything that is recognizable as the X root window. I've displayed random areas of memory before because my hardware framebuffer wasn't where I thought it was, and a black background was my clue that something was really wrong. Just my $0.01, what with the recession here in the US. --Yan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
