Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.6.99.903
On Thu, 2009-04-16 at 17:56 +0100, Barry Scott wrote: > Carl Worth wrote: > > On Thu, 2009-04-16 at 12:34 +0100, Jonathan Miles wrote: > > > >> Okay, understood... that is strange. I am using Compiz (0.8.2 + whatever > >> Ubuntu patches it with). > >> > >> I'm going to pull the latest git trees later and start looking into this > >> in more detail. > >> > > > > Thanks for your willingness to help, Jon. > > > > I don't know exactly how compiz interacts with xv, but you certainly > > might start by trying without compiz running to see if the tearing > > behavior changes, (my xv tests were without compiz). > > > The code you have to prevent tearing will only work without compositing. Note that for fullscreen video, you can enable the compiz option 'Unredirect Fullscreen Windows'. I think at least kwin and xfwm4 support this as well. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.6.99.903
On Fri, Apr 17, 2009 at 09:03:54 +0200, Michel Dänzer wrote: [...] > Note that for fullscreen video, you can enable the compiz option > 'Unredirect Fullscreen Windows'. I think at least kwin and xfwm4 support > this as well. At least in Xfce 4.6 an mplayer in full screen shows tearing with the option "Display fullscreen overlay windows directly" enabled in the Xfce window manager settings. Regards, Tino ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.6.99.903
On Fri, 2009-04-17 at 09:45 +0200, Tino Keitel wrote: > On Fri, Apr 17, 2009 at 09:03:54 +0200, Michel Dänzer wrote: > > [...] > > > Note that for fullscreen video, you can enable the compiz option > > 'Unredirect Fullscreen Windows'. I think at least kwin and xfwm4 support > > this as well. > > At least in Xfce 4.6 an mplayer in full screen shows tearing with the > option "Display fullscreen overlay windows directly" enabled in the > Xfce window manager settings. Assuming you get no tearing with compositing disabled, probably xfwm4 doesn't consider the mplayer window 'fullscreen'. I used to have the same problem with a few apps with compiz (though it also allows unredirecting windows manually with the 'Extra WM Actions' plugin), but it seems quite reliable now. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
On Fri, Apr 17, 2009 at 3:53 PM, Manish Jain wrote: > Dave Airlie wrote: >> >> On Thu, Apr 16, 2009 at 5:01 PM, Paul B. Mahol wrote: >> >>> >>> On 4/14/09, Manish Jain wrote: >>> Hi, I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron Coppermine 800 MHz + Intel 810 chipset-based system. The xorg documentation states that enabling DRI on this chipset just requires the colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just one screen with the depth set to 16. I am loading the agp module at boot-time via loader.conf. But xorg still disables DRI. Following are some relevant lines from xorg's log : > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > (**) intel(0): page flipping disabled > (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to > enable. > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: Open failed > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: Open failed > [drm] failed to load kernel module "i810" > >>> >>> is i915.ko loaded? >>> >>> >> >> you need to load i810.ko not i915.ko. >> >> Dave. >> >> > > Hello Dave, > > Thank you for your input. > > I myself wish things were that simple : > >> /boot/kernel # ls -l *810* >> ls: *810*: No such file or directory not sure where your kernel is come from, but you should have an i810.ko, CONFIG_DRM_I810 should create it. Dave. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
On Fri, 17 Apr 2009 21:09:36 +1000 Dave Airlie wrote: > On Fri, Apr 17, 2009 at 3:53 PM, Manish Jain > wrote: > > Dave Airlie wrote: > >> > >> On Thu, Apr 16, 2009 at 5:01 PM, Paul B. Mahol wrote: > >> > >>> > >>> On 4/14/09, Manish Jain wrote: > >>> > > Hi, > > I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron > Coppermine 800 MHz + Intel 810 chipset-based system. The xorg > documentation states that enabling DRI on this chipset just requires the > colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just one > screen with the depth set to 16. I am loading the agp module at > boot-time via loader.conf. But xorg still disables DRI. > > Following are some relevant lines from xorg's log : > > > > > X.Org X Server 1.4.2 > > Release Date: 11 June 2008 > > (**) intel(0): page flipping disabled > > (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to > > enable. > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: Open failed > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: Open failed > > [drm] failed to load kernel module "i810" > > > >>> > >>> is i915.ko loaded? > >>> > >>> > >> > >> you need to load i810.ko not i915.ko. > >> > >> Dave. > >> > >> > > > > Hello Dave, > > > > Thank you for your input. > > > > I myself wish things were that simple : > > > >> /boot/kernel # ls -l *810* > >> ls: *810*: No such file or directory > > not sure where your kernel is come from, but you should have > an i810.ko, CONFIG_DRM_I810 should create it. Not on FreeBSD :-) He is correct, though, there does not appear to be any i810 kernel module on FreeBSD. Adam ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
On Fri, Apr 17, 2009 at 9:20 PM, Adam K Kirchhoff wrote: > On Fri, 17 Apr 2009 21:09:36 +1000 > Dave Airlie wrote: > >> On Fri, Apr 17, 2009 at 3:53 PM, Manish Jain >> wrote: >> > Dave Airlie wrote: >> >> >> >> On Thu, Apr 16, 2009 at 5:01 PM, Paul B. Mahol wrote: >> >> >> >>> >> >>> On 4/14/09, Manish Jain wrote: >> >>> >> >> Hi, >> >> I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron >> Coppermine 800 MHz + Intel 810 chipset-based system. The xorg >> documentation states that enabling DRI on this chipset just requires the >> colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just one >> screen with the depth set to 16. I am loading the agp module at >> boot-time via loader.conf. But xorg still disables DRI. >> >> Following are some relevant lines from xorg's log : >> >> > >> > X.Org X Server 1.4.2 >> > Release Date: 11 June 2008 >> > (**) intel(0): page flipping disabled >> > (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to >> > enable. >> > drmOpenDevice: node name is /dev/dri/card0 >> > drmOpenDevice: open result is -1, (No such file or directory) >> > drmOpenDevice: open result is -1, (No such file or directory) >> > drmOpenDevice: Open failed >> > drmOpenDevice: node name is /dev/dri/card0 >> > drmOpenDevice: open result is -1, (No such file or directory) >> > drmOpenDevice: open result is -1, (No such file or directory) >> > drmOpenDevice: Open failed >> > [drm] failed to load kernel module "i810" >> > >> >>> >> >>> is i915.ko loaded? >> >>> >> >>> >> >> >> >> you need to load i810.ko not i915.ko. >> >> >> >> Dave. >> >> >> >> >> > >> > Hello Dave, >> > >> > Thank you for your input. >> > >> > I myself wish things were that simple : >> > >> >> /boot/kernel # ls -l *810* >> >> ls: *810*: No such file or directory >> >> not sure where your kernel is come from, but you should have >> an i810.ko, CONFIG_DRM_I810 should create it. > > Not on FreeBSD :-) He is correct, though, there does not appear to be > any i810 kernel module on FreeBSD. > Oh I missed !linux part, yes nobody has ever bothered porting i810 to FreeBSD AFAIK. Dave. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Debian Sid with NVidia card : Xorg cannot start...
Hi, Le Wed, 15 Apr 2009 12:28:56 -0500, Hugo Vanwoerkom a écrit : >David BERCOT wrote: >> Hi, >> >> I'm new on this list and this is my first message. >> I hope it's not a "classical" error but I had a (quick) look in the >> archives and I did not found any solution... >> >> First of all, I use Debian Sid with a 2.6.29 kernel. I've tried to >> install the non-free NVidia drivers but it seems that there is a >> bug with the 2.6.29 kernel. So, I have to use the free drivers >> (expecting for the bug to be resolved soon ;-))). >> > >I use Debian Sid with the 2.6.29 kernel and NVidia non-free driver >NVIDIA-Linux-x86-96.43.11-pkg1.run. > >I found the install absolutely straightforward and w/o errors. > >I use it with a multi-seat setup. > >What exactly was the problem? I've tried, yesterday evening, the same installation (except it is in amd64 and not in i386) : kernel 2.6.29 and NVidia 96.43.11-pkg1 and pkg2. The result was the same : impossible to compile... The error comes from the new organization of the headers (2 directories)... David. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
Dave Airlie wrote: > On Fri, Apr 17, 2009 at 3:53 PM, Manish Jain > wrote: > >> Dave Airlie wrote: >> >>> On Thu, Apr 16, 2009 at 5:01 PM, Paul B. Mahol wrote: >>> >>> On 4/14/09, Manish Jain wrote: > Hi, > > I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron > Coppermine 800 MHz + Intel 810 chipset-based system. The xorg > documentation states that enabling DRI on this chipset just requires the > colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just one > screen with the depth set to 16. I am loading the agp module at > boot-time via loader.conf. But xorg still disables DRI. > > Following are some relevant lines from xorg's log : > > >> X.Org X Server 1.4.2 >> Release Date: 11 June 2008 >> (**) intel(0): page flipping disabled >> (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to >> enable. >> drmOpenDevice: node name is /dev/dri/card0 >> drmOpenDevice: open result is -1, (No such file or directory) >> drmOpenDevice: open result is -1, (No such file or directory) >> drmOpenDevice: Open failed >> drmOpenDevice: node name is /dev/dri/card0 >> drmOpenDevice: open result is -1, (No such file or directory) >> drmOpenDevice: open result is -1, (No such file or directory) >> drmOpenDevice: Open failed >> [drm] failed to load kernel module "i810" >> >> is i915.ko loaded? >>> you need to load i810.ko not i915.ko. >>> >>> Dave. >>> >>> >>> >> Hello Dave, >> >> Thank you for your input. >> >> I myself wish things were that simple : >> >> >>> /boot/kernel # ls -l *810* >>> ls: *810*: No such file or directory >>> > > not sure where your kernel is come from, but you should have > an i810.ko, CONFIG_DRM_I810 should create it. > > Dave. > > Hello Dave, I am running FreeBSD's GENERIC x86 kernel without any reconfiguration with an unaltered xorg distribution : > /root # cat /var/log/Xorg.0.log | head -7 > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-PRERELEASE i386 > Current Operating System: FreeBSD unxfbsdi.local.lan 7.1-RELEASE > FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 > r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > Build Date: 08 September 2008 12:37:00PM -- Thank you and Regards Manish Jain invalid.poin...@gmail.com +91-99830-62246 NB : Laast year I kudn't spell Software Engineer. Now I are won. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
On 4/17/09, Manish Jain wrote: > Dave Airlie wrote: >> On Fri, Apr 17, 2009 at 3:53 PM, Manish Jain >> wrote: >> >>> Dave Airlie wrote: >>> On Thu, Apr 16, 2009 at 5:01 PM, Paul B. Mahol wrote: > On 4/14/09, Manish Jain wrote: > > >> Hi, >> >> I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron >> Coppermine 800 MHz + Intel 810 chipset-based system. The xorg >> documentation states that enabling DRI on this chipset just requires >> the >> colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just >> one >> screen with the depth set to 16. I am loading the agp module at >> boot-time via loader.conf. But xorg still disables DRI. >> >> Following are some relevant lines from xorg's log : >> >> >>> X.Org X Server 1.4.2 >>> Release Date: 11 June 2008 >>> (**) intel(0): page flipping disabled >>> (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to >>> enable. >>> drmOpenDevice: node name is /dev/dri/card0 >>> drmOpenDevice: open result is -1, (No such file or directory) >>> drmOpenDevice: open result is -1, (No such file or directory) >>> drmOpenDevice: Open failed >>> drmOpenDevice: node name is /dev/dri/card0 >>> drmOpenDevice: open result is -1, (No such file or directory) >>> drmOpenDevice: open result is -1, (No such file or directory) >>> drmOpenDevice: Open failed >>> [drm] failed to load kernel module "i810" >>> >>> > is i915.ko loaded? > > > you need to load i810.ko not i915.ko. Dave. >>> Hello Dave, >>> >>> Thank you for your input. >>> >>> I myself wish things were that simple : >>> >>> /boot/kernel # ls -l *810* ls: *810*: No such file or directory >> >> not sure where your kernel is come from, but you should have >> an i810.ko, CONFIG_DRM_I810 should create it. >> >> Dave. >> >> > > Hello Dave, > > I am running FreeBSD's GENERIC x86 kernel without any reconfiguration > with an unaltered xorg distribution : >> /root # cat /var/log/Xorg.0.log | head -7 >> >> X.Org X Server 1.4.2 >> Release Date: 11 June 2008 >> X Protocol Version 11, Revision 0 >> Build Operating System: FreeBSD 7.1-PRERELEASE i386 >> Current Operating System: FreeBSD unxfbsdi.local.lan 7.1-RELEASE >> FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 >> r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >> Build Date: 08 September 2008 12:37:00PM xorg list is certainly wrong place for this, post it to freebsd-x11 mailing list and/or send bug report and maybe someone will look for it. -- Paul ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
XInput2: getting window-relative coordinates?
Hello everyone, after a bit more fiddling, I now have MPX and XI2 up and running. My software is receiving the new XI2 input events fine; however, I've noticed that the valuators are always in screen coordinates. Is there a way to get them in window coordinates, or do I need to use XGetGeometry to convert them? Thanks, Yours, Florian -- 0666 - Filemode of the Beast ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Xserver function InitKeyboardDeviceStruct() does not use bell_func?
Hi, InitKeyboardDeviceStruct() does not use 'bell_func' in xserver/xkb/xkbInit.c git master. I found that this was needed to get my DDX's bell to ring :) --- ./xkb/save_xkbInit.c2009-04-17 07:41:36.0 +0100 +++ ./xkb/xkbInit.c 2009-04-17 15:00:12.0 +0100 @@ -576,6 +576,7 @@ InitKeyboardDeviceStruct(DeviceIntPtr de InitFocusClassDeviceStruct(dev); xkbi->kbdProc = ctrl_func; +dev->kbdfeed->BellProc = bell_func; dev->kbdfeed->CtrlProc = XkbDDXKeybdCtrlProc; dev->kbdfeed->ctrl = defaultKeyboardControl; A useful fix, perhaps, until I know better. Thanks, Colin Harrison ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [ANNOUNCE] xf86-video-intel 2.7.0
On Thu, 2009-04-16 at 20:24 -0700, John Ettedgui wrote: > On Thu, Apr 16, 2009 at 11:03 AM, Frederik Himpe > wrote: > On Wed, 15 Apr 2009 18:29:33 -0700, Carl Worth wrote: > > > We are pleased to announce a major 2.7.0 release of > xf86-video-intel > > (after three previous 2.6.99.90x release candidates). > This new version is not working for me: the image is > completely corrupted > (except for the mouse cursor), while 2.6.99.903 was working > without any > problem. > > I have the exact same behavior here. > 2.6.29 with KMS enabled and a x3000. Apparently, Jesse's last-minute fix that made it into xf86-video-intel 2.7.0 requires a corresponding fix in the kernel, (which as of yesterday was in Eric's tree but not quite into Linus' tree yet---but it might be there by now, I haven't checked yet.) So there are some tricky dependencies here that can be hard to get right. Hopefully everyone will have a nice, robust driver when all the dust settles. And for now, people on older kernels might need to revert something in the driver. I'm sorry we released things in such a delicate state. -Carl signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [ANNOUNCE] xf86-video-intel 2.7.0
On Thu, Apr 16, 2009 at 04:47:14AM +0200, Joerg Sonnenberger wrote: > (b) Xv doesn't crash the Xserver any more, which is good. When > xcompmgr is running, it doesn't show the video though (black window). I take that partially back. With DRI disabled, Xv still crashes the X server. Joerg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: XInput2: getting window-relative coordinates?
> after a bit more fiddling, I now have MPX and XI2 up and running. My > software is receiving the new XI2 input events fine; however, I've > noticed that the valuators are always in screen coordinates. Is there a > way to get them in window coordinates, or do I need to use XGetGeometry > to convert them? More experimentation with my code and with "xinput test-xi2" now has me totally confused. I created two master pointers, one is attached to an USB mouse, the other to a Synaptics touchpad. The first one (controlled by mouse) reports absolute screen coordinates with evtype == XI_Motion - the values range from (0,0) to (xres,yres). While window coordinates would be nice, that is about what I expect. However, the second one (controlled by touchpad) reports values in the range (1472,1408) to (5472,4448). This is also reported in the Xorg.log by the synaptics driver. How can I map these to screen coordinates? As the pointer still moves in screen coordinates, the mapping must already exist somewhere, I assume.. I know that this is quite beta still, so I'd be very grateful about some hints.. Yours, Florian -- 0666 - Filemode of the Beast ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Intel driver + KMS: logs flooded with "Xorg: freeing invalid memtype"
Hi, I've tried to use KMS (kernel vanilla 2.6.29.1) with the 2.7.0 Intel driver (Debian unstable), and the kernel logs are flooded with messages like: [ 3924.873152] Xorg:3404 freeing invalid memtype d3e58000-d3e59000 [ 3924.873229] Xorg:3404 freeing invalid memtype d3e59000-d3e5a000 [ 3924.873313] Xorg:3404 freeing invalid memtype d3e5a000-d3e5b000 [ 3924.873391] Xorg:3404 freeing invalid memtype d3e5b000-d3e5c000 [ 3924.873454] Xorg:3404 freeing invalid memtype d3e5c000-d3e5d000 [ 3924.873516] Xorg:3404 freeing invalid memtype d3e5d000-d3e5e000 [ 3924.873577] Xorg:3404 freeing invalid memtype d3e5e000-d3e5f000 The machine is up for a little more than 1 hour, and I get: # grep 'invalid memtype' /var/log/kern.log | wc -l 2652215 I got no such messages when KMS was disabled. Any ideas? Gabor # lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 10) 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 [8086:27d2] (rev 01) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01) 00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 01) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) 00:1f.2 IDE interface [0101]: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller [8086:27c0] (rev 01) 00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 01) 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02) Xorg.0.log: X.Org X Server 1.6.1 Release Date: 2009-4-14 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-1-vserver-amd64 x86_64 Debian Current Operating System: Linux boogie 2.6.29.1 #13 SMP PREEMPT Fri Apr 17 15:06:48 CEST 2009 x86_64 Build Date: 15 April 2009 12:08:18PM xorg-server 2:1.6.1-1 (bui...@excelsior.roeckx.be) 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: "/var/log/Xorg.0.log", Time: Fri Apr 17 18:04:28 2009 (II) Loader magic: 0xd40 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on linux (++) using VT number 24 (--) PCI:*(0...@0:2:0) Intel Corporation 82G33/G31 Express Integrated Graphics Controller rev 16, Mem @ 0xfea8/524288, 0xd000/268435456, 0xfe90/1048576, I/O @ 0xdc00/8 (II) Scanning /usr/share/xserver-xorg/pci directory for additional PCI ID's supported by the drivers (II) Matched intel from file name intel.ids (==) Using default built-in configuration (48 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default intel Device 0" Driver "intel" EndSection Section "Screen" Identifier "Builtin Default intel Screen 0" Device "Builtin Default intel Device 0" EndSection Section "Device" Identifier "Builtin Default intel Device 0" Driver "intel" EndSection Section "Screen" Identifier "Builtin Default intel Screen 0" Device "Builtin Default intel Device 0" EndSection Section "Device" Identifier "Builtin Default i810 Device 0" Driver "i810" EndSection Section "Screen" Identifier "Builtin Default i810 Screen 0" Device "Builtin Default i810 Device 0" EndSection Section "Device"
Re: [ANNOUNCE] xf86-video-intel 2.7.0
On Fri, 17 Apr 2009 08:32:32 -0700 Carl Worth wrote: > On Thu, 2009-04-16 at 20:24 -0700, John Ettedgui wrote: > > On Thu, Apr 16, 2009 at 11:03 AM, Frederik Himpe > > wrote: > > On Wed, 15 Apr 2009 18:29:33 -0700, Carl Worth wrote: > > > > > We are pleased to announce a major 2.7.0 release of > > xf86-video-intel > > > (after three previous 2.6.99.90x release candidates). > > > This new version is not working for me: the image is > > completely corrupted > > (except for the mouse cursor), while 2.6.99.903 was working > > without any > > problem. > > > > I have the exact same behavior here. > > 2.6.29 with KMS enabled and a x3000. > > Apparently, Jesse's last-minute fix that made it into xf86-video-intel > 2.7.0 requires a corresponding fix in the kernel, (which as of > yesterday was in Eric's tree but not quite into Linus' tree yet---but > it might be there by now, I haven't checked yet.) Is that fix queued for the -stable tree? If so, it's easier to just wait a bit rather than patch the intel driver... -RW signature.asc Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [ANNOUNCE] xf86-video-intel 2.7.0
On Friday 17 April 2009 17:32:32 Carl Worth wrote: > On Thu, 2009-04-16 at 20:24 -0700, John Ettedgui wrote: > > On Thu, Apr 16, 2009 at 11:03 AM, Frederik Himpe > > wrote: > > > > On Wed, 15 Apr 2009 18:29:33 -0700, Carl Worth wrote: > > > We are pleased to announce a major 2.7.0 release of > > > > xf86-video-intel > > > > > (after three previous 2.6.99.90x release candidates). > > > > This new version is not working for me: the image is > > completely corrupted > > (except for the mouse cursor), while 2.6.99.903 was working > > without any > > problem. > > > > I have the exact same behavior here. > > 2.6.29 with KMS enabled and a x3000. > > Apparently, Jesse's last-minute fix that made it into xf86-video-intel > 2.7.0 requires a corresponding fix in the kernel, (which as of yesterday > was in Eric's tree but not quite into Linus' tree yet---but it might be > there by now, I haven't checked yet.) I can confirm that there is no corruption with 2.6.30-rc2 with jbarnes' last- minute fix manually applied, intel driver 2.7.0 and KMS on GM965. No corruption even after a resume from suspend to disk. Great! However, I am not able to redirect output on VGA connected monitors (it works without KMS). I've opened bug #21250 on fd.o with more details. Also, you might be interested to know that with the current git master of xorg, mesa and intel driver there is an additional issue: KDE4 compositing manager cannot be enabled when using KMS. thanks > > So there are some tricky dependencies here that can be hard to get > right. Hopefully everyone will have a nice, robust driver when all the > dust settles. And for now, people on older kernels might need to revert > something in the driver. > > I'm sorry we released things in such a delicate state. > > -Carl ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
implementation of new unicode character "latin capital sharp s " = upper-case eszett = 0x1e9e
From time to time new characters are added to Unicode. Which are the processes that lead to their inclusion in Linux/GNU/X11 ? What is a typical time line ? More specifically, I am interested in the capital sharp s added as 0x1e9e in April 2008. It will serve as upper case form of the German eszett. What needs to be done to make "Ssharp" a keysym for 0x1e9e, in analogy to "ssharp" for 0x00df (lower case eszett) ? Will font designers and maintainers take care of 0x1e9e to actually produce the new letter? While waiting for the new letter to be designed and implemented, what could one do to have 0x1e9e produce a lower case eszett as a substitute for the not yet available upper case eszett? Thanks in advance - Joachim ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[Announce] X Developers' Conference 2009 (September 28-30)
The X.Org Foundation is happy to announce the X Developers' Conference for 2009. Please see the conference web page for details (some of which is copied below): http://xorg.freedesktop.org/wiki/Events/XDC2009 -Carl The 2009 X Developers' Conference[1] will be held at Portland State University (PSU) in Portland, Oregon, from Monday September 28 through Wednesday September 30. PSU is within walking distance of Portland's downtown area and a wide variety of dining, lodging, and public transportation options. The conference is scheduled to follow directly after Linux Plumbers Conference 2009[2] so that people attending both LPC and XDC can do that with a single trip. The conference will be held at the University Place[3] hotel and conference center on the edge of the PSU campus. We will run the 3-day summit as a normal conference, with presentations and also birds-of-a-feather group sessions, as well as informal 'corridor sessions', and plenty of time for after-hours social activities. Attendance is free, but you must register beforehand, by putting your name on the Attendees page. We encourage attendees to stay at the conference hotel (University Place[3]) for convenience. We have initially reserved a block of 20 rooms for the conference, (so let them know you're with the conference when making a reservation). We will attempt to increase that block size as needed, (so please make your reservation as early as possible). [1] XDC 2009: http://xorg.freedesktop.org/wiki/Events/XDC2009 [2] LPC 2009: http://linuxplumbersconf.org/2009/ [3] University Place: http://cegs.pdx.edu/stay/upl/ signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel driver + KMS: logs flooded with "Xorg: freeing invalid memtype"
On Fri, 17 Apr 2009 17:16:36 +0200 Gabor Gombas wrote: > Hi, > > I've tried to use KMS (kernel vanilla 2.6.29.1) with the 2.7.0 Intel > driver (Debian unstable), and the kernel logs are flooded with messages > like: > > [ 3924.873152] Xorg:3404 freeing invalid memtype d3e58000-d3e59000 > [ 3924.873229] Xorg:3404 freeing invalid memtype d3e59000-d3e5a000 > [ 3924.873313] Xorg:3404 freeing invalid memtype d3e5a000-d3e5b000 > [ 3924.873391] Xorg:3404 freeing invalid memtype d3e5b000-d3e5c000 > [ 3924.873454] Xorg:3404 freeing invalid memtype d3e5c000-d3e5d000 > [ 3924.873516] Xorg:3404 freeing invalid memtype d3e5d000-d3e5e000 > [ 3924.873577] Xorg:3404 freeing invalid memtype d3e5e000-d3e5f000 > > The machine is up for a little more than 1 hour, and I get: > > # grep 'invalid memtype' /var/log/kern.log | wc -l > 2652215 > > I got no such messages when KMS was disabled. Any ideas? Disable PAT in the kernel or use 2.6.30-rc2. You can add "nopat" to the kernel commandline to disable it. -- gcc-porting, by design, by neglect treecleaner, for a fact or just for effect wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 signature.asc Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: XInput2: getting window-relative coordinates?
Florian Echtler wrote: > However, the second one (controlled by touchpad) reports values in the > range (1472,1408) to (5472,4448). This is also reported in the Xorg.log > by the synaptics driver. How can I map these to screen coordinates? As > the pointer still moves in screen coordinates, the mapping must already > exist somewhere, I assume.. I'm not sure about this, but I recall it may depend on whether you listen to a master device (screen coords) or a slave device (driver coords). Anyway, make sure you're at the right set of coordinates: DeviceEvent: [...] root_x root_y The position of the pointer in screen coordinates (16.16 fixed point). event_x event_y The position of the pointer in screen coordinates relative to the event window (16.16 fixed point). (formatting broken, but I'm sure you get the idea.) Cheers, Simon ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xf86-video-savage: (2/2) Do not use XAAGetCopyROP outside of XAA-specific code
> > > Just out of curiosity, how many subscribers of this list have access to a > Savage chipset, besides myself? Is the Savage EXA code being exercised in > the wild? I do (ProSavage8 KM266/KL266). I'm using XAA with a lot of problems (performance) described in a my recent post. I'll try EXA ;) Gianni ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
On Fri, 2009-04-17 at 07:20 -0400, Adam K Kirchhoff wrote: > On Fri, 17 Apr 2009 21:09:36 +1000 > Dave Airlie wrote: > > > On Fri, Apr 17, 2009 at 3:53 PM, Manish Jain > > wrote: > > > Dave Airlie wrote: > > >> > > >> On Thu, Apr 16, 2009 at 5:01 PM, Paul B. Mahol wrote: > > >> > > >>> > > >>> On 4/14/09, Manish Jain wrote: > > >>> > > > > Hi, > > > > I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron > > Coppermine 800 MHz + Intel 810 chipset-based system. The xorg > > documentation states that enabling DRI on this chipset just requires > > the > > colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just > > one > > screen with the depth set to 16. I am loading the agp module at > > boot-time via loader.conf. But xorg still disables DRI. > > > > Following are some relevant lines from xorg's log : > > > > > > > > X.Org X Server 1.4.2 > > > Release Date: 11 June 2008 > > > (**) intel(0): page flipping disabled > > > (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to > > > enable. > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is -1, (No such file or directory) > > > drmOpenDevice: open result is -1, (No such file or directory) > > > drmOpenDevice: Open failed > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is -1, (No such file or directory) > > > drmOpenDevice: open result is -1, (No such file or directory) > > > drmOpenDevice: Open failed > > > [drm] failed to load kernel module "i810" > > > > > >>> > > >>> is i915.ko loaded? > > >>> > > >>> > > >> > > >> you need to load i810.ko not i915.ko. > > >> > > >> Dave. > > >> > > >> > > > > > > Hello Dave, > > > > > > Thank you for your input. > > > > > > I myself wish things were that simple : > > > > > >> /boot/kernel # ls -l *810* > > >> ls: *810*: No such file or directory > > > > not sure where your kernel is come from, but you should have > > an i810.ko, CONFIG_DRM_I810 should create it. > > Not on FreeBSD :-) He is correct, though, there does not appear to be > any i810 kernel module on FreeBSD. We never built it... Last word was that i915 was supposed to support all chipsets. robert. > Adam > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg -- Robert Noland FreeBSD -- Robert Noland 2 Hip Networks signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: implementation of new unicode character "latin capital sharp s " = upper-case eszett = 0x1e9e
|> What needs to be done to make "Ssharp" a keysym for 0x1e9e,
|> in analogy to "ssharp" for 0x00df (lower case eszett) ?
That is generally not needed. The symbol U1e9e works.
|> Will font designers and maintainers take care of 0x1e9e
|> to actually produce the new letter?
I would expect so. I know that it was added to DejaVu Serif and
DejaVu Sans; I expect DejaVu Sans Mono will also get it by the
next release.
|> While waiting for the new letter to be designed and implemented,
|> what could one do to have 0x1e9e produce a lower case eszett
|> as a substitute for the not yet available upper case eszett?
The easiest solution, for apps which support fallback fonts, would be to
create a family of fonts with that one glyph, using the ß glyph from your
favorite font family.
If you are using server-side bdf fonts, just edit them locally and add
a glyph for U+1E9E.
NB that, per the UCS and Unicode, uc("ß") != "ẞ"; it is still the case
that uc("ß") == "SS".
As such, support for U+1E9E may arrive a bit slower than for some other
additions to the UCS.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: XInput2: getting window-relative coordinates?
On Fri, Apr 17, 2009 at 05:45:15PM +0200, Florian Echtler wrote: > > after a bit more fiddling, I now have MPX and XI2 up and running. My > > software is receiving the new XI2 input events fine; however, I've > > noticed that the valuators are always in screen coordinates. Is there a > > way to get them in window coordinates, or do I need to use XGetGeometry > > to convert them? > More experimentation with my code and with "xinput test-xi2" now has me > totally confused. I created two master pointers, one is attached to an > USB mouse, the other to a Synaptics touchpad. > > The first one (controlled by mouse) reports absolute screen coordinates > with evtype == XI_Motion - the values range from (0,0) to (xres,yres). > While window coordinates would be nice, that is about what I expect. > > However, the second one (controlled by touchpad) reports values in the > range (1472,1408) to (5472,4448). This is also reported in the Xorg.log > by the synaptics driver. How can I map these to screen coordinates? As > the pointer still moves in screen coordinates, the mapping must already > exist somewhere, I assume.. > > I know that this is quite beta still, so I'd be very grateful about some > hints.. right, so the rule for coordinates is: event_x,event_y, root_x, root_y are in absolute screen coordinates. or should be anyway. the data in *valuators OTOH is in device-coordinates. this may be screen coordinates for relative devices, and device coordinates for absolute devices. You need to get the axis information through XIQueryDevice() first, and do the scaling on the client-side if you need it. for what you're trying to do, root_x/y should do. unless I screwed up majorly... Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Intel G45 - problem with 2D
Hi all, I've got an Intel G45/GMA4500 onboard video, and also got the following problem: after switching on 3D hardware acceleration, graphics shows pretty low perfomance in 2D (e.g. scrolling or resizing windows). 3D works quite well, glxgears shows 1100 fps. I really suspect that the trouble is in my xorg.conf .. so it would be cool if someone could show the right xorg.conf file. Thanks in advance, Jack ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
> > We never built it... Last word was that i915 was supposed to support all > chipsets. Not sure where you heard that, i915 just replaced i830 kernel module, i810/5 has always been a separate module. Dave. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problems enabling DRI on i810 chipset with xorg-server 1.4.2
On Sat, 2009-04-18 at 13:58 +1000, Dave Airlie wrote: > > > > We never built it... Last word was that i915 was supposed to support all > > chipsets. > > Not sure where you heard that, i915 just replaced i830 kernel module, > i810/5 has always been a separate module. Ok, I'll have a look, although I wouldn't have any way to test it... Surely, it wouldn't be hard to get it working though... robert. > Dave. -- Robert Noland 2 Hip Networks signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
