[ANNOUNCE] Deprecation of xf86-video-nv
Historically, NVIDIA developed and maintained the xf86-video-nv X driver, primarily as a very minimal driver that works well enough to give users accelerated X rendering from the time they install their Linux distribution until the time they install the NVIDIA driver available from nvidia.com [1]. The xf86-video-nv driver intentionally has a very small feature set, both to minimize the maintenance cost of this driver, and to minimize exposure of any IP NVIDIA might consider sensitive. However, the rendering needs of a modern X Window System desktop have changed drastically in recent years to rely heavily on the X Render extension, which is not well accelerated in the nv driver. At this point, on a modern X desktop the nv driver does not offer much beyond what is provided by the stock VESA X driver. Providing proper Render acceleration in the nv driver would be a substantial task, and would require diverting significant engineering resources away from NVIDIA's nvidia.com driver. For this reason, NVIDIA is dropping support, on new GPUs, for the xf86-video-nv driver. Details: - NVIDIA will continue to support the existing functionality and existing level of acceleration in the nv driver for existing GPUs, on existing, and (within reason) future, X server versions. - NVIDIA will not support the xf86-video-nv driver on Fermi or later GPUs. - NVIDIA will not support DisplayPort, on any GPU, in the xf86-video-nv driver. Our advice to owners of NVIDIA GPUs running Linux is to use the VESA X driver from the time of Linux distribution installation until they can download and install the NVIDIA Linux driver from their distribution repositories or from nvidia.com. We believe that focusing our Linux driver engineering efforts exclusively on the NVIDIA driver, in order to leverage NVIDIA's cross-platform graphics driver code base, is the optimal route for the best possible user experience for NVIDIA Linux users. Thanks, Andy Ritger [1] http://www.nvidia.com/object/unix.html ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
Re: Xorg - Buildroot distribution - chip XGI Volari z9s
Hi, I found a patch here that could resolve one of my problem : http://lists.freedesktop.org/archives/xorg/2008-January/032346.html Its name : Ensure XGI DriverRec and xgiModuleData XF86ModuleData are public symbols. Could it be the cause of the error xgiModuleData object when using driver XGI? It only add a keyword *_X_EXPORT *before two variables in xgi_driver.c. I applied it and try but now I got a Segmentation fault. And the problem is I don't know if this segmentation fault comes from the _X_EXPORT key word (is this a macro of Xorg or something?) or if the patch really works and this is another error which came after. The segmentation fault trace in Xorg.0.log : (II) LoadModule: xgi (II) Loading /usr/lib/xorg/modules/drivers/xgi_drv.so (II) Module xgi: vendor=X.Org Foundation compiled for 1.7.1, module version = 1.1.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 Backtrace: 0: X (xorg_backtrace+0x34) [0x80c6994] 1: X (0x8048000+0x4d711) [0x8095711] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb7741410] Segmentation fault at address 0x6 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting At my level, I can't see something interesting in that message. So if anybody has an idea... Thanks! Damien Borie TERAWATT / AENERGIA S.A.S. ZA DUBOSCOA 64990 Villefranque FRANCE tel : +33 (0)5 59 44 26 08 fax : +33 (0)5 59 31 15 11 Damien Borie a écrit : Hello everybody. This is my first message in this list, so forgive me if I'm not quite clear. First, the situation. We work on a panel PC, the Icop PDX-089T, which contains a graphic chipset XGI Volari Z9S, a screen of size 8'9, a touch screen, and some other things. We have installed a Linux distribution, a customized one created with Buildroot. The aim is to execute three applications, and one of them is a graphic application (made with QT). So we need a nice displaying, with mode 1024x600x16. Before that, we used a PDX-057T, which is exactly the same device but with a smaller screen (5'7). We used Framebuffer with Vesa driver and succeed to obtain the good resolution (640x480x16). But the same Linux distribution on the PDX-089T doesn't offer a good resolution. The best is 800x600x8, and there is no mode with depth 16. We have concluded that there is a memory limit in Framebuffer which not allow depth of 16 with the same chip on a larger screen. So we had to active Xorg in our distribution. After some epic battles, we succeeded in creating a new distribution with Buildroot with Xorg and the drivers XGI and SiS installed. Then we tried to set up and launch a X server, but for now without success. The first try was with Xorg 1.5.3, XGI drivers 1.5.0, SiS drivers 0.10.0, which were all include in Buildroot last release (2010.02). The issues : *Framebuffer + Vesa* : Max resolution : 800x600x8. No depth 16 *Xorg + XGI* : No apparent error, but black screen. Interrupt doesn't return to the console. *Xorg + SiS* : No apparent error, but black screen. Interrupt allow to return to the console. *Xorg + XGIZ* : We try to install several version on the XGIZ driver, which is provided by XGI (and some other providers like Icop). No one seems to correspond to Xorg version 1.5.3, and no one works. After some search, we decided to try with the last snapshot of Buildroot, as a lot of X update have been made. Second try : Xorg 1.7.1, XGI driver 1.5.1, SiS driver 0.10.2, included in the snapshot, and XGIZ driver 2.70.1201 provided by Icop support service. *Framebuffer + Vesa *: Max resolution : 800x600x8. No depth 16 *Framebuffer + sisfb *: No display, black screen. Option problems? We didn't search any further... *Xorg + XGI* : Load module failed with this error : LoadModule: Module xgi does not have a xgiModuleData data object. I don't know where this error comes from. *Xorg + SiS* : No apparent error, but black screen. Interrupt allow to return on the console. *Xorg + XGIZ* : Load module failed with this error : dlopen: /usr/lib/xorg/modules/drivers/xgiz_drv.so: undefined symbol: resVgaMemShared We are searching for long days now, for no result. All these drivers should works and be compatible with the chip. But, as we're not at all specialist of Xorg, we must have missed something. What I search here is : - any suggestion about the errors when loading module for XGI and XGIZ drivers. - any idea about why SiS driver doesn't seems to fail but do not display anything - any others suggestion from anybody who has already use this chip and encounters some problems. - any explanation about the apparent Framebuffer limit, as the provider confirm that 1024x600 resolution should be supported. - any suggestion about the options to set in xorg.conf, as I tried many things but with no results, and without understand everything. I have all the Xorg.0.log files saved if it's needed. I'll try to debug the source code of the driver, but I don't know if
GSOC idea: USB Multiseat Refinement
Hello, I'm really interested to participate in GSOC program this year. I have worked with multiseats over the last 3 years in MDM project ( http://wiki.c3sl.ufpr.br/multiseat/index.php/Mdm) and I would like to work in the USB Multiseat Refinement idea because I think is very important that linux distributions have a easy way to configure a multiseat enviroment. It is because here in Brazil multiseats are becomming very commom on public schools and I have saw that they are having many problens with it. I have read what the Plugable have done about USB multiseats and I already had studied the problems that they are having, so I think I can help and try to resolve it. Best regards, -- Lucas Nascimento Ferreira C3SL - Centro de Computação Científica e Software Livre UFPR - Universidade Federal do Paraná ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [ANNOUNCE] xf86-input-synaptics 1.2.2
2010/3/25 Peter Hutterer peter.hutte...@who-t.net: Only two minor fixes for the stable 1.2 series. This version will work with the upcoming 1.8 X server release though you _must_ recompile, the ABI has been bumped. If you plan to use synaptics 1.2.2 with server 1.8, the following config snippet is recommended in /etc/xorg.conf.d/10-synaptics.conf: Section InputClass Identifier touchpad catchall Driver synaptics MatchIsTouchpad on MatchDevicePath /dev/input/event* EndSection Maybe we should ship this in the tarball and/or install it like evdev on xserver-1.8+. Also, do we need to limit to /dev/input/event* devices? Unlike evdev, synaptics is used on multiple platforms that probably don't have the same device layout. I think it's safe to just have MatchIsTouchpad and let later rules sort out when that should not be synaptics. -- Dan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] Deprecation of xf86-video-nv
Historically, NVIDIA developed and maintained the xf86-video-nv X driver, primarily as a very minimal driver that works well enough to give users accelerated X rendering from the time they install their Linux distribution until the time they install the NVIDIA driver available from nvidia.com [1]. The xf86-video-nv driver intentionally has a very small feature set, both to minimize the maintenance cost of this driver, and to minimize exposure of any IP NVIDIA might consider sensitive. However, the rendering needs of a modern X Window System desktop have changed drastically in recent years to rely heavily on the X Render extension, which is not well accelerated in the nv driver. At this point, on a modern X desktop the nv driver does not offer much beyond what is provided by the stock VESA X driver. Providing proper Render acceleration in the nv driver would be a substantial task, and would require diverting significant engineering resources away from NVIDIA's nvidia.com driver. For this reason, NVIDIA is dropping support, on new GPUs, for the xf86-video-nv driver. Details: - NVIDIA will continue to support the existing functionality and existing level of acceleration in the nv driver for existing GPUs, on existing, and (within reason) future, X server versions. - NVIDIA will not support the xf86-video-nv driver on Fermi or later GPUs. - NVIDIA will not support DisplayPort, on any GPU, in the xf86-video-nv driver. Our advice to owners of NVIDIA GPUs running Linux is to use the VESA X driver from the time of Linux distribution installation until they can download and install the NVIDIA Linux driver from their distribution repositories or from nvidia.com. We believe that focusing our Linux driver engineering efforts exclusively on the NVIDIA driver, in order to leverage NVIDIA's cross-platform graphics driver code base, is the optimal route for the best possible user experience for NVIDIA Linux users. Thanks, Andy Ritger [1] http://www.nvidia.com/object/unix.html ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Re: GSOC idea: USB Multiseat Refinement
Hello again, I have some questions about the USB Multiseat Refinement idea. Configure USB multiseats may be very dependent of distributions and I have seen that Bernie Thompson has worked on Ubuntu 9.04 and Xubuntu 8.10. In this project, Ther is one specific distribution to work on? If not, What version of Xorg and Linux kernel will be used to it? Thanks for any reply, 2010/3/26 Lucas Ferreira ln...@c3sl.ufpr.br Hello, I'm really interested to participate in GSOC program this year. I have worked with multiseats over the last 3 years in MDM project ( http://wiki.c3sl.ufpr.br/multiseat/index.php/Mdm) and I would like to work in the USB Multiseat Refinement idea because I think is very important that linux distributions have a easy way to configure a multiseat enviroment. It is because here in Brazil multiseats are becomming very commom on public schools and I have saw that they are having many problens with it. I have read what the Plugable have done about USB multiseats and I already had studied the problems that they are having, so I think I can help and try to resolve it. Best regards, -- Lucas Nascimento Ferreira C3SL - Centro de Computação Científica e Software Livre UFPR - Universidade Federal do Paraná -- Lucas Nascimento Ferreira C3SL - Centro de Computação Científica e Software Livre UFPR - Universidade Federal do Paraná ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
