There's nothing buggy here and xorg-server 1.5 will go to extra without keeping 1.4 around.

dev status? How many stoppers are there? Any idea when it will move?

On 21:13, Sun 16 Nov 08, Jan de Groot wrote:

- xf86-input-synaptics should have better documentation about hotplugging configuration before it's thrown at our users

I'm using this driver for my touchpad, works fine so far but one finger tapping doesn't work at all. My 10-synaptics.fdi looks like this: ---snip--- <?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input.touchpad"> <match key="info.product" contains="ETPS/2 Elantech Touchpad"> <merge key="input.x11_driver" type="string">synaptics</merge> <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge> <merge key="input.x11_options.SHMConfig" type="string">true</merge> <merge key="input.x11_options.AccelFactor" type="string">0.032</merge> <merge key="input.x11_options.LeftEdge" type="string">1700</merge> <merge key="input.x11_options.RightEdge" type="string">5300</merge> <merge key="input.x11_options.TopEdge" type="string">1700</merge> <merge key="input.x11_options.BottomEdge" type="string">4200</merge> <merge key="input.x11_options.FingerLow" type="string">25</merge> <merge key="input.x11_options.FingerHigh" type="string">30</merge> <merge key="input.x11_options.MaxTapTime" type="string">180</merge> <merge key="input.x11_options.MaxTapMove" type="string">220</merge> <merge key="input.x11_options.MinSpeed" type="string">0.625</merge> <merge key="input.x11_options.MaxSpeed" type="string">1.0</merge> <merge key="input.x11_options.HorizEdgeScroll" type="string">true</merge> <merge key="input.x11_options.HorizScrollDelta" type="string">100</merge> <merge key="input.x11_options.VertEdgeScroll" type="string">true</merge> <merge key="input.x11_options.VertScrollDelta" type="string">100</merge> <!-- Restore old synaptics driver defaults removed by Fedora/RH patch --> <merge key="input.x11_options.RTCornerButton" type="string">2</merge> <merge key="input.x11_options.RBCornerButton" type="string">3</merge> <merge key="input.x11_options.TapButton1" type="string">1</merge> <merge key="input.x11_options.TapButton2" type="string">2</merge> <merge key="input.x11_options.TapButton3" type="string">3</merge> </match> </match> </device> </deviceinfo> ---snip--- Thomas

On Monday 17 November 2008 02:29:18 Amanai wrote:

nvidia-7xxx take a look here http://www.nvnews.net/vbulletin/showthread.php?t=118088

and here are the sources ftp://download.nvidia.com/XFree86/Linux-x86/180.06/ ftp://download.nvidia.com/XFree86/Linux-x86_64/180.06/

That is the 180.xx driver which does not help here. The problem is the 71xx driver for tnt and old geforce cards. But as Jan said, those are rarly used and the nv driver is a good alternative. (3d acceleration of these cards is nearly useless these days anyway) -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de

On Mon, 2008-11-17 at 21:05 +0100, José M. Prieto wrote:

2008/11/16 Jan de Groot :

...

On Sun, 2008-11-16 at 12:00 -0800, Amanai wrote:

...

dev status? How many stoppers are there? Any idea when it will move?

My stopper list: - time - xf86-input-synaptics should have better documentation about hotplugging configuration before it's thrown at our users - nvidia-7xxx

(...) Nvidia-7xxx is not a real stopper here. Cards this driver are ancient and can't keep up with todays standards, so the nv or vesa driver isn't such a big regression for these. If Nvidia provides us with a new (beta) driver with X.Org 7.4 support we're happy to package it.

I guess this applies also to nvidia-96xx, right?

Nvidia-96xx was updated to a beta release recently, the current version in testing has support for X.Org 7.4.

On Sun, 2008-11-16 at 15:00 -0500, pyther wrote:

I'm a bit confused. Can you explain to me about this Vsync thing?

When running xorg-server 1.4 I was able to get ~650fps. I have not changed my xorg.conf since switching to xorg-server 1.5 where I get a max of 60fps.

There's no such thing as a 90% performance drop, glxgears is not a benchmark. As for vsync, it means that your framerate is tied to your refreshrate. This is done by default now to avoid heavy tearing issues when using 3D on intel chips. To restore to the old behaviour, put this in your ~/.drirc: <driconf> <device screen="0" driver="i915"> <application name="Default"> <option name="vblank_mode" value="0" /> </application> </device> </driconf> Replace i915 with the driver that suits your intel chip. I would advise against using xf86-video-intel-2.5.x and libdrm-2.4.x until GEM is merged into the kernel and things start using it. We're sticking to xf86-video-intel-2.4.x and libdrm-2.3.1 now because the newer versions cause regressions. The main improvements in the 2.5 series are related to GEM, and as long as our kernel doesn't have that, there's no need for a newer driver than 2.4.x.