Hello list!
I bought a Samsung 900X3A-B01SE (also known as a Samsung Series 9 with
Intel i5 sold in Sweden) today.
It has a Synaptic touchpad, but it doesn't get recognized as a
touchpad by the synaptics input driver. I just gets recognized as a
regular mouse device.
How can I produce some kind
driver, present in the repositories,
everything works fine, but 3D acceleration vanishes.
Can you helpme?
Thank you.
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman
Hi Valter,
I had this problem long ago with a very similar configuration. It
vanished when Alex Deucher modified some details (like rounding) in the
Radeon mode setting/calculation code.
I don't know about the details, but maybe you can copy the modeline
generated by the proprietary driver
On Sun, Oct 9, 2011 at 19:35:24 -0500, Harry Putnam wrote:
I will describe what I see following this xrandr cmd:
xrandr --output DVI-I-1 --mode 1440x900 --panning 1680x1050
I see an image I have been using for background grow quite a lot.
The panel that fluxbox has put on the bottom of
Running Debian wheezy
After cloning the git repo for:
git://anongit.freedesktop.org/xorg/driver/xf86-video-nv
I got a slug of errors when running ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
configure.ac:33: error
On Sun, Oct 09, 2011 at 05:07:47PM -0500, Harry Putnam wrote:
Running Debian wheezy
After cloning the git repo for:
git://anongit.freedesktop.org/xorg/driver/xf86-video-nv
I got a slug of errors when running ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac
On Sun, Oct 9, 2011 at 3:07 PM, Harry Putnam rea...@newsguy.com wrote:
Running Debian wheezy
After cloning the git repo for:
git://anongit.freedesktop.org/xorg/driver/xf86-video-nv
I got a slug of errors when running ./autogen.sh
autoreconf: Entering directory `.'
autoreconf
On Mon, 2011-09-19 at 12:52 -0400, James Cloos wrote:
IIRC, the current server code requires that one use a compositing
manager to do backing store.
It has beena while since this last come up, though. I may be mis-
remembering.
You are. Backing store was rewritten to use the composite
depth
using the intel driver. After some assistance I was able to get 8 bit
color to show in color. However, now the backing store does not seem
to work, so the application I am attempting to run leaves blank areas
on the display whenever a menu or other window covers that area.
xdpyinfo does report
MD == Michel Dänzer mic...@daenzer.net writes:
JC It has beena while since this last come up, though. I may be
JC misremembering.
MD You are. Backing store was rewritten to use the composite layer,
MD but that doesn't require a compositing manager.
Ah. Good to know. Thanks.
-JimC
--
James
I posted to this list earlier about not getting color in 8 bit depth
using the intel driver. After some assistance I was able to get 8 bit
color to show in color. However, now the backing store does not seem
to work, so the application I am attempting to run leaves blank areas
on the display
Hi everyone, i really need help on installing the driver, all these days i
was trying it with flgrx but had just recently found out that it won't work
and i must install an open source driver. WHERE DO I BEGIN? went to X.Org
but honestly just get confused there, all this stuff about Git, dont
Hi all,
I wish to project the display of local machine onto the screen of remote
machine through network.
I wanted to know how good it would be to use mirror driver to achieve the
same?
Thanks and Regards,
Ankur
___
xorg@lists.freedesktop.org: X.Org
I don't know what you mean by mirror driver, but you could always
use VNC. x11vnc is the thing that springs to mind for this particular
scenario.
~ C.
On Mon, May 9, 2011 at 3:13 AM, ankur jain samy...@gmail.com wrote:
Hi all,
I wish to project the display of local machine onto the screen
in their build package for the intel
driver. It's time to get it upstream to avoid us all forward porting
copies (and possibly getting it wrong).
James
Index: xf86-video-intel-2.14.903/src/intel.h
===
--- xf86-video-intel-2.14.903.orig/src
Any chance of seeing a new minor version of dummy tagged?
This would help push this to users sooner rather than later.
Last question: can anyone think of a distro agnostic way of detecting if
the dummy driver has this big-screen support without starting a full
Xorg instance and seeing the result
Hi,
As suggested on this list a while back, I am trying to replace Xvfb with
the Xorg + dummy driver.
1) I can't seem to make it use resolutions higher than 2048x2048 which
is a major showstopper for me:
Virtual height (2560) is too large for the hardware (max 2048)
Virtual width (3840) is too
for the hardware (max 2048)
Seems bogus to me, I've tried giving it more ram, giving it a very wide
range of vsync and hsync, added modelines for these large modes, etc
No go.
It is bogus, the driver has an arbitrary limit. Look for the call to
xf86ValidateModelines in the source, and compare
for the hardware (max 2048)
Virtual width (3840) is too large for the hardware (max 2048)
Seems bogus to me, I've tried giving it more ram, giving it a very wide
range of vsync and hsync, added modelines for these large modes, etc
No go.
It is bogus, the driver has an arbitrary limit
On 4/6/11 6:38 PM, Aaron Plattner wrote:
On Wed, Apr 06, 2011 at 02:37:52PM -0700, Antoine Martin wrote:
diff --git a/src/dummy_driver.c b/src/dummy_driver.c
index 804e41e..05450d5 100644
--- a/src/dummy_driver.c
+++ b/src/dummy_driver.c
@@ -85,6 +85,9 @@ static Bool
for Redhat 3 Update 8. The best bet would be to use xorg driver
and compile it on
RHEL3 update 8. There is package called mga which works for matrox graphics
driver.
You must know however, that I'm not an engineer. So, customer need procedure
to install this driver.
Please help giving
high definition resolution. However, There are no VGA drivers
available for Redhat 3 Update 8. The best bet would be to use xorg driver
and compile it on
RHEL3 update 8. There is package called mga which works for matrox graphics
driver.
You must know however, that I'm not an engineer. So
Hello!
Does ati driver support OpenGL 2.0 or GL ES 2.0 for r400 chip based cards?
Cheers
Mike
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
On Sun, Feb 13, 2011 at 3:35 PM, Mike m...@0907.ru wrote:
Hello!
Does ati driver support OpenGL 2.0 or GL ES 2.0 for r400 chip based cards?
The r300 gallium driver (r300g) does.
Alex
Cheers
Mike
___
xorg@lists.freedesktop.org: X.Org support
I've got a Barco monitor that I'm using the touch screen configuration. I've
got a couple of questions concerning the configuration:
1. The xorg.conf was setup to use the evdev driver and it's working.
But I'm not sure how the startup of X is calling this driver? I do not see
On Feb 10, 2011, at 7:45 AM, Johnson, Je wrote:
I’ve got a Barco monitor that I’m using the touch screen configuration. I’ve
got a couple of questions concerning the configuration:
1. The “xorg.conf” was setup to use the “evdev” driver and it’s
working. But I’m not sure how
? driver and it?s
Je working. But I?m not sure how the startup of ?X? is calling this
Je driver? I do not see with ?lsmod? that the driver is loaded?
Don't confuse the kernel evdev interface (/dev/input/eventX) with the X
evdev input driver.
Je 2. When I disable/enable or turn off the monitor
Thanks Peter...
John
-Original Message-
From: Peter Korsgaard [mailto:jac...@gmail.com] On Behalf Of Peter Korsgaard
Sent: Thursday, February 10, 2011 2:08 PM
To: Johnson, Je
Cc: x...@freedesktop.org
Subject: EXTERNAL: Re: Driver Question - evdev
Je == Johnson, Je je.john...@lmco.com
in the device section causes the freeze (same as before,
no ping) on Xorg startup. I see there is a new ati driver soon to be
committed to the FreeBSD port system, so perhaps the problem will be
fixed.
Joey
___
xorg@lists.freedesktop.org: X.Org support
Archives
startup and a second system
(IBM R51 with an intel card) did the same. All three systems seem
stable with the vesa driver.
Thanks,
Joey
Section ServerLayout
Identifier X.org Configured
Screen 0 Screen0 0 0
InputDeviceMouse0 CorePointer
InputDevice
system had an another old ATI card and it
would lock in a similar manner on Xorg startup and a second system
(IBM R51 with an intel card) did the same. All three systems seem
stable with the vesa driver.
It's likely something freebsd specific. I'm not sure how well the
freebsd drm works
file below with either the ati or radeon
driver. If I switch to the vesa driver the problem stops, but of
course performance drops (scrolling text, windows, etc. lag).
The relevant lines ffom pciconf -lv are
[CODE]vgapci0@pci0:1:0:0: class=0x03 card=0x17721043
chip=0x4e501002 rev
I'm running the latest xorg (7,5) compiled from ports on FreeBSD 8.2
RC2 and everything is working fine, but when I shutdown X, the system
locks every time. This happens when I start X with no configuration
file or the configuration file below with either the ati or radeon
driver. If I switch
2011/1/20 Timo Jyrinki timo.jyri...@gmail.com:
Ubuntu's 2.6.37 kernel config as the basis, so CONFIG_DRM_I915=m and
CONFIG_DRM_I915_KMS=y are there.
The kernel in use is edp-fixes-2 and I also gave him drm-intel-fixes
one with the same result. Only vesa driver works for him for now.
Just
the whole file told anything else interesting in
addition to the excerpt I originally sent?
Other than the fact that the intel driver quietly fails?
Either clearly shows that the intel driver (whether 2.13 or 2.14)
just doesn't work.
The deafening silence the logs have been met with seems
On Mon, 24 Jan 2011 12:27:20 -0600 (CST), al...@verizon.net wrote:
Waiting with bated breath for us to come with a happy resolution
on the intel driver.
You need to enable kernel modesetting to use the current stable releases
of -intel.
Check you have CONFIG_DRM_I915 and CONFIG_DRM_I915_KMS
i830 driver
i915 driver
[ ] Enable modesetting on intel by default
For some reason, the boot parameter you suggested (grub excerpt):
kernel /boot
On Mon, 24 Jan 2011 19:01:57 -0600 (CST), al...@verizon.net wrote:
For some reason, the boot parameter you suggested (grub excerpt):
        kernel /boot/LFSkernel root=/dev/sda3 i915.modeset=1
does not work. Â The system remains regular (non-KMS), thus the
Original Post (problem)
Jan 24, 2011 08:14:18 PM, ch...@chris-wilson.co.uk wrote:
Then your modprobe is not parsing the command line for any relevant
module parameters and would need to put those into
'echo options i915 modeset=1 /etc/modprobe.d/i915-modeset.conf'
look at Documentation/fb/modedb.txt for a
of kms failing to initialize or so. I used
Ubuntu's 2.6.37 kernel config as the basis, so CONFIG_DRM_I915=m and
CONFIG_DRM_I915_KMS=y are there.
The kernel in use is edp-fixes-2 and I also gave him drm-intel-fixes
one with the same result. Only vesa driver works for him for now.
-Timo
---some
Jan 20, 2011 03:10:32 AM, timo.jyri...@gmail.com wrote:
alupu's attachments still didn't show the kms related line
which I assume he was initially talking about
Hi Timo,
I don't know what kms is.
Regardless, to recap my situation:
1. With intel-2.13.0 driver, Xorg-7.6 fails to start up
a need
for more information regarding the intel driver error I've been
experiencing so technical help/resolution can be forthcoming?
By bzip2 attachment (my preference)?
By pastebin (second choice)?
Thanks,
-- Alex
___
xorg@lists.freedesktop.org: X.Org
On Jan 19, 2011, at 10:07 AM, al...@verizon.net wrote:
In the reply E-mail I stated:
It's roughly a 7K file. I can bzip2 it to about 2K+ size
and attach it to my regular post to Xorg.
Would that be fine with you?
I noticed there has been no posting of my reply in the archive.
Nor any
On Jan 19, 2011, at 10:07 AM, al...@verizon.net wrote:
[the Xorg.0.log] It's roughly a 7K file. I can bzip2 it to about 2K+ size
and attach it to my regular post to Xorg.
Would that be fine with you?
Jan 19, 2011 05:57:20 PM, a...@nwnk.net wrote:
Look, do what you have to do, just show us
;X.Org Foundation"[21.874] compiled for 1.9.3, module version = 2.14.0[21.874] Module class: X.Org Video Driver[21.874] ABI class: X.Org Video Driver, version 8.0...[21.894] (II) intel: Driver for Intel Integrated Graphics Chipsets: ... G35...[21.894] (--) using VT number 7[22.243] (EE) No
)
Installed the newly released intel-2.14.0 driver.
The previous error (No modesetting) appears to have disappeared.
There's a new fatal one:
(EE) No devices detected
DETAILS
Note: Xorg-7.6 has been built entirely from sources (.tar.bz2)
xf86-video-intel-2.14.0 (1814124 intel_drv.so)
Log
On Jan 18, 2011, at 3:24 PM, al...@verizon.net wrote:
Hello,
This is a repeat mail. According to xorg archive, on
the previous one An HTML attachment was scrubbed...
Maybe better luck this time ...
You've clipped away everything from the X log that might tell us why this error
is
touchpad
MatchIsTouchpad on
Driver evdev
Option Mode absolute
EndSection
which works nicely on my DELL D430.
On my DELL E4310, however, the touchpad isn't recognized
(see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/637911)
and I have the same problem as described
Hello. I am currently writing a display driver (UMS, not framebuffer or KMS) for a very ancient card, the Oak Spitfire OTI64111. This weekend I tried this code with the Fedora 14 xorg server (I previously wrote most of the code on Fedora 12). When I run
the driver as the only card for the xorg
Hello,
SYSTEM
ASUS P5E-VM HDMI with Intel G35/ICH9R.
Intel Core2 Duo CPU E8400 @ 3.00GHz, 4GB
(B)LFS i686-pc-linux-gnu, 2.6.36.2, Udev-165
PROBLEM
I upgraded to Xorg-7.6 (from 7.5).
On bringing up X on the natural (for the board) intel driver,
X fails with No kernel modesetting driver
I need absolute rather than relative position from my touchpad. At
Peter Hutterrer's suggestion I installed the following in
/etc/X11/xorg.conf.d/99-evdev-touchpad.conf
Section InputClass
Identifier evdev touchpad
MatchIsTouchpad on
Driver evdev
Option Mode
Hi peeps.
I hope you guys don't mind the occasional newbie question :)
I have a vaguely interesting 'problem' regarding the siliconmotion
driver (the system is running Xubuntu 9.10 at the moment) and before I
start hacking around with the source code I thought I might ask if
there is someone
What I would like to do is compile a 'portrait' video driver.
Essentially, I think I just want to swap the x and y values for each
pixel, thus creating an output for a display in portrait mode.
See xrandr
I figure that there is a bit more to it than just doing a global
replace data_x
On Mon, Nov 15, 2010 at 3:33 AM, Frith Foottit frith.foot...@gmail.com wrote:
Hi peeps.
I hope you guys don't mind the occasional newbie question :)
I have a vaguely interesting 'problem' regarding the siliconmotion
driver (the system is running Xubuntu 9.10 at the moment) and before I
Hello,
is their any link or input which can give me Xorg video module driver
for PowerVR chipset (SGX535).
I would like to run on ARM11 core.
Rgds--
Vij
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives
On Thu, 2010-11-11 at 17:13 +0530, Shashi Shekar B.S. wrote:
is their any link or input which can give me Xorg video module driver
for PowerVR chipset (SGX535).
PVR driver is a closed source one. You need to contact Imagination/
your vendor for getting that driver.
If you want to write
On Thu, 11 Nov 2010 16:36:59 +0530
vijay singh testmrs@gmail.com wrote:
Hello,
is their any link or input which can give me Xorg video module driver
for PowerVR chipset (SGX535).
I believe vendors can purchase a proprietary (ie non-free in both senses)
license and access from the device
On 11/11/2010 12:56 PM, Alan Cox wrote:
On Thu, 11 Nov 2010 16:36:59 +0530
vijay singhtestmrs@gmail.com wrote:
Hello,
is their any link or input which can give me Xorg video module driver
for PowerVR chipset (SGX535).
I believe vendors can purchase a proprietary (ie non-free
On Thu, 2010-11-11 at 17:13 +0530, Shashi Shekar B.S. wrote:
is their any link or input which can give me Xorg video module driver
for PowerVR chipset (SGX535).
PVR driver is a closed source one. You need to contact Imagination/
your vendor for getting that driver.
If you want to write
to probably write an acceptable 2D
driver, maybe even to do a compositing 2D driver by staring hard at the
kernel bits that have been released (because they had to GPL them), but
not enough for 3D.
Alan
___
xorg@lists.freedesktop.org: X.Org support
Archives
Hi,
I have followed the instructions in
http://www.x.org/wiki/radeonBuildHowTo to build the latest ATI driver
and Mesa. I succeeded in build and install everything. However, with
glxinfo | grep OpenGL
I still get
OpenGL renderer string: Software Rasterizer
so 3d hardware acceleration
On Sun, Nov 7, 2010 at 5:43 PM, Stefano Facchini
stefano.facch...@gmail.com wrote:
Hi,
I have followed the instructions in
http://www.x.org/wiki/radeonBuildHowTo to build the latest ATI driver
and Mesa. I succeeded in build and install everything. However, with
glxinfo | grep OpenGL
I
Hello everybody,
I'm trying to use vmwgfx inside VmWare player 3.0.
I've a problem enabling gallium driver.
My kernel is 2.6.36 with module vmwgfx from ...
I use:
- libdrm 2.4.22 recompiled from git with --enable-vmwgfx-experimental-api=yes
- mesa 7.9 recompiled from git 7.9 branch with --enable
I wanna know if is possible to link a driver's name to a specific driver
eg:
i write in xorg.conf to use the test_driver, then I link the nvidia or
the nouveau driver to this test_driver
--
Renan Vedovato Traba
Student in Bachelor of Computer Science
Federal University of Parana, Brazil
On Thursday 21 October 2010 Peter Hutterer wrote:
xinput set-prop device name Device Enabled 0
should do the job. it relies on the driver being implemented correctly,
i.e. releasing the device on DEVICE_OFF and taking it up again on
DEVICE_ON. not sure about this driver in particular
Hello,
sorry if this has been asked before (I couldn't find an answer yet) or if it's
obviously documented somewhere (please direct me there, if so).
I would like to temporarily disable/pause the elo touchscreen input driver
(xf86Elo.c) so that I can calibrate it without competing
On Wed, Oct 20, 2010 at 11:12:25AM +0200, Bernhard Prell wrote:
sorry if this has been asked before (I couldn't find an answer yet) or if
it's
obviously documented somewhere (please direct me there, if so).
I would like to temporarily disable/pause the elo touchscreen input driver
off with
really recent 3D driver - the 7.9 RC or straight from git.
Xserver from experimental is uninstallable here (deps problem).
Yes, I recall needing to shoehorn it in. It's probably a better idea to
get up to date 3D drivers first and see if that's enough to get WebGL
working.
--
Cheers
Le vendredi 01 octobre 2010 à 08:48 -0700, ott0disk a écrit :
Hi everybody,i'm having some trouble with the xorg.conf configuration file,i
recently switched from the amd/ati proprietary driver to the radeon that
support well my graphic card.
You should try just getting rid of your xorg.conf
Hi,
I'm using a debian system rather uptodate, with:
xserver-xorg-video-ati 1:6.13.1-2
libgl1-mesa-dri 7.8.2-2
libdrm2 2.4.21-2
and I'm trying to get various WebGL examples working under Firefox 4b7
and Chromium 6.0.472.62. Lot of them don't work, and the ones that do
are quite slow.
E.g:
.
Glxinfo says also so.
How many fps do you reach ?
I think you still need an Xserver with pbuffer support (the one in
debian experimental should do) and you're probably better off with
really recent 3D driver - the 7.9 RC or straight from git.
Xserver from experimental is uninstallable here
driver - the 7.9 RC or straight from git.
(Resent since I missed to cc the list)
--
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22
signature.asc
Description: This is a digitally signed message part
___
xorg@lists.freedesktop.org
Dear Xorg developers,
As a humble Ubuntu 10.10 user I found my tablet Pc not working under 10.10.
After some googling I met the friendly kernel-developer Stéphane Chatty, who
developed a driver which I helped testing.
The driver seems to work very well (thank you Stéphane !).
Canonical decided
Hi everybody,i'm having some trouble with the xorg.conf configuration file,i
recently switched from the amd/ati proprietary driver to the radeon that
support well my graphic card.Finally i got everything working but i need
some options to be enabled in xorg,especially :
Option AGPFastWrite
Greetings all;
I have now installed ubuntu-10.04 LTS on my old box that runs my milling
machine, and its a disaster in terms of speed compared to 6.06.
One thing that is a given is that I must use the vesa driver because all
the others, including the radeon driver from the 10.04 install, do
On Friday, September 10, 2010 11:59:22 pm Alan Coopersmith did opine:
gene heskett wrote:
So, since there is not an /etc/X11/xorg.conf file now, how do I force
x to use the vesa driver at its optimum settings?
You make an xorg.conf file. We didn't get rid of xorg.conf, it's just
Greetings all;
I have now installed ubuntu-10.04 LTS on my old box that runs my milling
machine, and its a disaster in terms of speed compared to 6.06.
One thing that is a given is that I must use the vesa driver because all
the others, including the radeon driver from the 10.04 install, do
Hello,
It looks like Xorg drivers on Linux platform are NOT kernel modules.
Could someone explain, or better point some brief document - what these Xorg
drivers are and how they are implemented ?
(some call them Xorg modules)
thanks
Vilius
___
server. Where things get
confusing is that they can be written to operate in at least different ways.
Basic 2d-only drivers can directly access the hardware from userspace for both
modesetting and acceleration, and can run without a kernel driver. This was
the norm 10-15 years ago and many
2010/9/7 Timo Juhani Lindfors timo.lindf...@iki.fi
Vilius Mockūnas v.mocku...@gmail.com writes:
It looks like Xorg drivers on Linux platform are NOT kernel modules.
Could someone explain, or better point some brief document - what these
Xorg
drivers are and how they are implemented ?
Hi All,
How does the XServer handle accelerometer events, is there any
xorg-input-driver available for accelerometer support
Regards
Yogesh
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http
For the rendering work, I want to do a sum up of the work in previous several
months.
1)Based on the No icon bug fixed work from Mart, we bring all the return
FALSE condition from lx_prepare_composite to lx_check_composite
http://cgit.freedesktop.org/xorg/driver/xf86-video-geode/commit/?id
Am Friday 06 August 2010 schrieb Nikos Chantziaras:
Does that mean that it could be a bug in KDE's compositor?
.. The problem does never occur when compositing is active. ...
Doesn't make much sense, yesno? :-)
(It's rather likely that the indirect rendering works and the bug occurs on
direct fb
On 08/06/2010 01:57 PM, Thomas Lübking wrote:
Am Friday 06 August 2010 schrieb Nikos Chantziaras:
Does that mean that it could be a bug in KDE's compositor?
.. The problem does never occur when compositing is active. ...
Doesn't make much sense, yesno? :-)
Now that I read it again, it was a
with AMD's binary fglrx driver or on non-radeon cards.
The problem, as I mentioned already, is an old one. Right now, I'm at:
Radeon HD4870
kernel 2.6.35_rc6
xf86-video-ati Git master
Mesa Git master
X server Git master
I've made another observation (accidentally). The problem does never
occur
to accomplish with the
fbdev_modes_equal() check at all.
From commit f6815cb68b0f6698497348fc6e4214dacef33b95 which added it:
The fbdev API allows the driver to 'accept' modes it doesn't really
support by
modifying it to the nearest supported mode. Without this check, e.g
it back to fbmode (due to rounding error
pixclock - 260010) and then tries to set mode with pixvalue 260010 via
FBIOPUT_VSCREENINFO ioctl, but driver sets it back to 26, and xorg-server
fails to startup with this message:
(EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode.
What
, but driver sets it back to 26, and
xorg-server
fails to startup with this message:
(EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode.
What version of xserver are you using? It sounds like your problem
should be fixed by Git commit
On Mon, 2010-08-02 at 18:24 +0200, Michel Dänzer wrote:
AFAICT this will only work when using the 'built-in' mode, otherwise
mode-PrivFlags will never be set? One possible solution for that could
be
- var-pixclock = mode-Clock ? 10/mode-Clock : 0;
+ var-pixclock = mode-PrivFlags ?
Thanks Peter for your answer.
Here is the event sequence when I tap the screen:
$ evtest /dev/input/event3
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0xdfc product 0x1 version 0x305
Input device name: USB Touchscreen 0dfc:0001
Supported events:
Event type 0 (Sync)
Event
On Wed, 2010-07-28 at 05:36 +0400, sergio wrote:
Hello.
Is it possible make video driver with which subpixel rendering will not
work? Or only xrender acceleration depends on driver?
The RENDER extension is initialized when the driver calls
fbPictureInit(). All known shipping drivers do
On Thu, Jul 29, 2010 at 12:05:07PM +0200, Javi wrote:
Thanks Peter for your answer.
Here is the event sequence when I tap the screen:
$ evtest /dev/input/event3
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0xdfc product 0x1 version 0x305
Input device name: USB
Hello.
Is it possible make video driver with which subpixel rendering will not
work? Or only xrender acceleration depends on driver?
--
sergio.
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info
Hi.
I've upgraded some machines with touchscreens to latest Xorg. The ones
with USB EloGraphics touchscreens work like a charm with evdev driver
and no extra configuration. The problem is with the ones with
GeneralTouch USB touchscreens.
I managed to properly calibrate them, but now you need
On Wed, Jul 28, 2010 at 11:57:48AM +0200, Javi wrote:
I've upgraded some machines with touchscreens to latest Xorg. The ones
with USB EloGraphics touchscreens work like a charm with evdev driver
and no extra configuration. The problem is with the ones with
GeneralTouch USB touchscreens.
I
color bars at the bottom. They
always appear, but naturally, they're most visible in dark scenes. It's
not an mplayer bug it seems, since pausing the video and going out of
fullscreen and then back makes them go away temporarily. Also, they
never appear with AMD's binary fglrx driver or on non
pausing the video and going out of fullscreen and then back
makes them go away temporarily. Also, they never appear with AMD's binary
fglrx driver or on non-radeon cards.
The problem, as I mentioned already, is an old one. Right now, I'm at:
Radeon HD4870
kernel 2.6.35_rc6
xf86-video-ati Git
, they never appear with AMD's binary
fglrx driver or on non-radeon cards.
The problem, as I mentioned already, is an old one. Right now, I'm at:
Radeon HD4870
kernel 2.6.35_rc6
xf86-video-ati Git master
Mesa Git master
X server Git master
Does it happen with any other movie players (totem, vlc, etc
. They always
appear,
but naturally, they're most visible in dark scenes. It's not an mplayer
bug
it seems, since pausing the video and going out of fullscreen and then
back
makes them go away temporarily. Also, they never appear with AMD's
binary
fglrx driver or on non-radeon cards.
The problem
On 07/28/2010 03:43 AM, Pat Kane wrote:
I'm pretty sure I don't have superhuman vision :-P They're there, I can
see
them quite clearly. Maybe your monitor is too dark or too low contrast?
On my display I might be able to see the artifacts that you mention, but it
is hard to tell
1 - 100 of 575 matches
Mail list logo
