Bug#697932: init script for single application appliances
lightdm-autologin-greeter provides the functionality, thus closing.
Bug#697932: init script for single application appliances
s/incube\.tk/zincube.net/ Please read above : [1] http://sousmonlit.zincube.net/~niol/repositories/deejayd/file/d52a42471c0a/debian/deejayd.deejayd-xserver.init [2] http://sousmonlit.zincube.net/~niol/repositories/deejayd/file/d52a42471c0a/debian/deejayd.default -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cam79t8gjvumoxodcuokohbooyfti803ttps6jsa4kkq098i...@mail.gmail.com
Bug#453754: Fixed for me
Hi, For me, this has been fixed by migrating to squeeze. I was using Option XvPreferOverlay with a patched version of the lenny driver, but now I do not need to anymore. I use the standard squeeze binary packages. xserver-xorg-video-intel 2:2.9.1-4 linux-image-2.6.32-5-amd64 2.6.32-21 $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) $ xvinfo | grep Adaptor Adaptor #0: Intel(R) Textured Video = this is the one that I exprienced the bug with Adaptor #1: Intel(R) Video Overlay But if I use Xine to play a video, the output show that it is using the Textured Video XV adaptor and I do not experience the tearing. -- Xine 1.1.19 video_out_dxr3: Failed to open control device /dev/em8300-0 (No such file or directory) video_out_xv: using Xv port 89 from adaptor Intel(R) Textured Video for hardware colour space conversion and scaling. video_out_xv: this adaptor supports the yuy2 format. video_out_xv: this adaptor supports the yv12 format. -- So this is fixed for me. Alex -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimafx23vjf8g7476ghnb8z-znxax8zb+oksn...@mail.gmail.com
Bug#564549: Possible documentation
Please find a possible patch for this that works for me.
Information was found there : http://sidux.com/PNphpBB2-viewtopic-t-19491.html
Cheers,
Alex
diff -Nru xserver-xorg-input-synaptics-1.2.1/debian/65-xorg-synaptics-custom.rules xserver-xorg-input-synaptics-1.2.1.new/debian/65-xorg-synaptics-custom.rules
--- xserver-xorg-input-synaptics-1.2.1/debian/65-xorg-synaptics-custom.rules 1970-01-01 01:00:00.0 +0100
+++ xserver-xorg-input-synaptics-1.2.1.new/debian/65-xorg-synaptics-custom.rules 2010-02-08 20:15:15.0 +0100
@@ -0,0 +1,20 @@
+ACTION!=add|change, GOTO=xorg_synaptics_custom_end
+KERNEL!=event*, GOTO=xorg_synaptics_custom_end
+
+ENV{ID_INPUT_TOUCHPAD}!=1, GOTO=xorg_synaptics_custom_end
+
+ENV{x11_driver}=synaptics
+
+# Example parameters, uncomment to activate
+#ENV{x11_options.VertEdgeScroll}=true
+#ENV{x11_options.TapButton1}=1
+
+# model specific quirks
+ATTR{[dmi/id]product_name}==Inspiron 1011|Inspiron 1012, \
+ ENV{x11_options.JumpyCursorThreshold}=90, \
+ ENV{x11_options.AreaBottomEdge}=4100
+
+ATTR{[dmi/id]product_name}==HP MiniNote 1000, \
+ ENV{x11_options.JumpyCursorThreshold}=20
+
+LABEL=xorg_synaptics_custom_end
diff -Nru xserver-xorg-input-synaptics-1.2.1/debian/xserver-xorg-input-synaptics.docs xserver-xorg-input-synaptics-1.2.1.new/debian/xserver-xorg-input-synaptics.docs
--- xserver-xorg-input-synaptics-1.2.1/debian/xserver-xorg-input-synaptics.docs 2010-02-08 20:07:34.0 +0100
+++ xserver-xorg-input-synaptics-1.2.1.new/debian/xserver-xorg-input-synaptics.docs 2010-02-08 20:19:21.0 +0100
@@ -2,3 +2,4 @@
docs/README.alps
TODO
docs/trouble-shooting.txt
+debian/65-xorg-synaptics-custom.rules
diff -Nru xserver-xorg-input-synaptics-1.2.1/debian/xserver-xorg-input-synaptics.README.Debian xserver-xorg-input-synaptics-1.2.1.new/debian/xserver-xorg-input-synaptics.README.Debian
--- xserver-xorg-input-synaptics-1.2.1/debian/xserver-xorg-input-synaptics.README.Debian 2010-02-08 20:07:34.0 +0100
+++ xserver-xorg-input-synaptics-1.2.1.new/debian/xserver-xorg-input-synaptics.README.Debian 2010-02-08 20:17:05.0 +0100
@@ -3,7 +3,7 @@
This package contains the Synaptics TouchPad driver for X.Org X server.
See also the README file for details on configuration options.
-The following notes are reported from the INSTALL instructions of upstream
+The following notes are reported from the INSTALL instructions of upstream
package (by Stefan Gmeiner riddle...@freesurf.ch), but first of all a
security notice about SHMConfig:
@@ -11,7 +11,7 @@
restarting the X server, one option is to enable the SHMConfig option in
the X configuration file. You can then use the synclient program to
query and modify driver parameters on the fly.
- SECURITY NOTE! This is not secure if you are in an untrusted
+ SECURITY NOTE! This is not secure if you are in an untrusted
multiuser environment. All local users can change the parameters at any
time.
@@ -23,12 +23,12 @@
Xorg auto-configuration
---
Recent X.Org has support for automatic configuration. The synaptics driver does
-not support automatic configuration yet but the information required is
-supplied by a third party fdi script through HAL.
-The file is /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi,
-if you need to customize it, you can first copy it to
-/etc/hal/fdi/policy and the edit it to match your requirements.
-
+not support automatic configuration yet but the information required can be
+supplied as an udev rule.
+If you need to customize Synaptics configuration parameters, a customized rules
+template and edit it to match your needs.
+$ sudo cp /usr/share/doc/xserver-xor-input-synaptics/66-xorg-synaptics.rules \
+ /etc/udev/rules.d/65-xorg-synaptics-custom.rules
Manual configuration
@@ -105,7 +105,7 @@
Running 'syndaemon' automatically
-
-The easiest way to run the syndaemon binary each time you startup X you can
+The easiest way to run the syndaemon binary each time you startup X you can
simply add the following line to your ~/.xinitrc file:
/usr/bin/syndaemon -i 1 -d
Bug#523946: xserver-xorg-input-synaptics: VertScrolling stops working after update to version 1.1.0
This does not seem to be the issue for me, as I successfully re-enabled Tapping and SHMConfig (for syndaemon) but vertical scrolling does not work even though the option is modified : $ synclient -l | grep Vert VertScrollDelta = 25 VertEdgeScroll = 1 VertTwoFingerScroll = 0 Can you also check the values of the various *Edge options? $ synclient -l | grep Edge LeftEdge= 40 RightEdge = 983 TopEdge = 42 BottomEdge = 725 VertEdgeScroll = 1 HorizEdgeScroll = 1 EdgeMotionMinZ = 14 EdgeMotionMaxZ = 79 EdgeMotionMinSpeed = 1 EdgeMotionMaxSpeed = 102 EdgeMotionUseAlways = 0 You were right, calibrating as explained in the manual page (using synclient -m 1), I managed to get back vertical scrolling using : $ synclient RightEdge=930 No issue for me anymore, thanks! As a side note, all options in hal fdi files must have a string type, otherwise, it does not work. Also note that SHMConfig is not required anymore and is not even used by synclient if you don't specify the -s option. syndaemon used to complain when SHMConfig is disabled... But this is not the case anymore. Thanks. By the way, the syndaemon manual page still lists a -s option (to use the SHMConfig area), but it is not accepted by syndaemon. Cheers, Alex -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523946: xserver-xorg-input-synaptics: VertScrolling stops working after update to version 1.1.0
I have the same issue as Mirko. Vertical Scrolling does not work after upgrading xserver-xorg-input-synaptics from 0.14.7~git20070706-3 (lenny) to 1.1.0-1 (sid). Downgrading fixes the problem. It's a configuration issue, with version 1.1.0 most of the default values have changed so you will need to explicitly enable some features in your xorg.conf or hal fdi files. See bugs 523581, 513875, 523528 for more. This does not seem to be the issue for me, as I successfully re-enabled Tapping and SHMConfig (for syndaemon) but vertical scrolling does not work even though the option is modified : $ synclient -l | grep Vert VertScrollDelta = 25 VertEdgeScroll = 1 VertTwoFingerScroll = 0 Alex -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#497523: patch for documentation about hal stuff
Hi, A patch for that would certainly be appreciated. Note that there's already a NEWS entry about this in git, for which suggestions are also welcome. A quick patch I could come up with. Alex diff --git a/debian/NEWS b/debian/NEWS index dfa879b..c11f47d 100644 --- a/debian/NEWS +++ b/debian/NEWS @@ -3,7 +3,7 @@ xserver-xorg-input-synaptics (1.1.0-2) unstable; urgency=low * Tapping has been disabled by default on many touchpads by upstream. If you want to re-enable it, you can do so explicitly by adding the following to your xorg.conf: - + Section InputDevice Identifier synaptics Driver synaptics @@ -16,4 +16,35 @@ xserver-xorg-input-synaptics (1.1.0-2) unstable; urgency=low configuration. For more details see synaptics(4) and http://who-t.blogspot.com/2009/04/synaptics-11-and-what-your-touchpad-can.html + Another option is to configure it through hal. An exemple hal policy file is + available : /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi + In order to re-enable tapping, you can put the following contents in + /etc/hal/fdi/policy/11-x11-synaptics.fdi : + +?xml version=1.0 encoding=ISO-8859-1? +deviceinfo version=0.2 + device +match key=info.capabilities contains=input.touchpad + match key=input.x11_driver contains=synaptics +merge key=input.x11_options.TapButton1 + type=string1/merge +merge key=input.x11_options.TapButton2 + type=string2/merge +merge key=input.x11_options.TapButton3 + type=string3/merge + /match +/match + /device +/deviceinfo + +For the changes to be taken into account, restart hal : + +# /etc/init.d/hal restart + + * On a more general note, the defaults have changed in this version. To +restore the defaults to the old ones, just drop +/usr/share/doc/xserver-xorg-input-synaptics/examples/prehal-defaults.fdi +into +/etc/hal/fdi/policy/11-x11-synaptics.fdi + -- David Nusinow dnusi...@debian.org Sat, 11 Apr 2009 16:23:11 -0400 diff --git a/debian/examples/prehal-defaults.fdi b/debian/examples/prehal-defaults.fdi new file mode 100644 index 000..bc401f1 --- /dev/null +++ b/debian/examples/prehal-defaults.fdi @@ -0,0 +1,13 @@ +?xml version=1.0 encoding=ISO-8859-1? +deviceinfo version=0.2 + device +match key=info.capabilities contains=input.touchpad + merge key=input.x11_driver type=stringsynaptics/merge + merge key=input.x11_options.VertEdgeScroll type=stringtrue/merge + merge key=input.x11_options.HorizEdgeScroll type=stringtrue/merge + merge key=input.x11_options.TapButton1 type=string1/merge + merge key=input.x11_options.TapButton2 type=string2/merge + merge key=input.x11_options.TapButton3 type=string3/merge +/match + /device +/deviceinfo diff --git a/debian/xserver-xorg-input-synaptics.docs b/debian/xserver-xorg-input-synaptics.docs index 07e6c68..64cb5a5 100644 --- a/debian/xserver-xorg-input-synaptics.docs +++ b/debian/xserver-xorg-input-synaptics.docs @@ -3,3 +3,4 @@ docs/README.alps TODO NEWS docs/trouble-shooting.txt +debian/examples/
Bug#523415: Same here
severity 523415 important retitle 523415 [855GM] corrupted rendering except for the cursor thanks Hi, Same thing for me here, same hardware. I also think severity should be grave, because it renders the package unusable. Please feel free to ask me for more input, debugging info or testing potential fixes. If this is relevant for some reason, the cursor is displayed properly, everything else is scrambled. Cheers, Alex -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493030: Already reported
merge 480919 493030 thanks This is the same as #480919. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453754: Problem really comes from Texturized video
Hi,
The above patch works around the tearing for me (and my Intel 945G).
So : rebuild, and add the following line to the Device section of
/etc/X11/xorg.conf
Option XvPreferOverlay true
Thanks!
(I had to trivially adapt it because it overlaps with the second patch
in the series... so here it is attached)
diff -rN -u old-xserver-xorg-video-intel-2.3.2/man/intel.man
new-xserver-xorg-video-intel-2.3.2/man/intel.man
--- old-xserver-xorg-video-intel-2.3.2/man/intel.man2008-09-21
20:46:31.0 +
+++ new-xserver-xorg-video-intel-2.3.2/man/intel.man2008-09-21
20:46:31.0 +
@@ -128,6 +128,11 @@
Disable or enable XVideo support.
Default: XVideo is enabled for configurations where it is supported.
.TP
+.BI Option \*qXvPreferOverlay\*q \*q boolean \*q
+Make hardware overlay be first XV adapter.
+Some applications assume only one XV adapter present thus use first one.
+Default: Textured video adapter is first and overlay second.
+.TP
.BI Option \*qLegacy3D\*q \*q boolean \*q
Enable support for the legacy i915_dri.so 3D driver.
This will, among other things, make the 2D driver tell libGL to
diff -rN -u old-xserver-xorg-video-intel-2.3.2/src/i830_driver.c
new-xserver-xorg-video-intel-2.3.2/src/i830_driver.c
--- old-xserver-xorg-video-intel-2.3.2/src/i830_driver.c2008-09-21
20:46:31.0 +
+++ new-xserver-xorg-video-intel-2.3.2/src/i830_driver.c2008-09-21
20:46:31.0 +
@@ -318,6 +318,7 @@
OPTION_XVMC,
#endif
OPTION_RENDERACCEL,
+ OPTION_PREFER_OVERLAY,
} I830Opts;
static OptionInfoRec I830Options[] = {
@@ -346,6 +347,7 @@
#ifdef INTEL_XVMC
{OPTION_XVMC, XvMC, OPTV_BOOLEAN, {0},TRUE},
#endif
+ {OPTION_PREFER_OVERLAY, XvPreferOverlay, OPTV_BOOLEAN, {0}, TRUE},
{OPTION_RENDERACCEL, RenderAccel, OPTV_BOOLEAN, {0},TRUE},
{-1,NULL, OPTV_NONE, {0},FALSE}
};
@@ -1682,6 +1684,8 @@
pI830-XvDisabled =
!xf86ReturnOptValBool(pI830-Options, OPTION_XVIDEO, TRUE);
+ pI830-XvPreferOverlay = xf86ReturnOptValBool(pI830-Options,
OPTION_PREFER_OVERLAY, FALSE);
+
#ifdef I830_XV
if (xf86GetOptValInteger(pI830-Options, OPTION_VIDEO_KEY,
(pI830-colorKey))) {
diff -rN -u old-xserver-xorg-video-intel-2.3.2/src/i830.h
new-xserver-xorg-video-intel-2.3.2/src/i830.h
--- old-xserver-xorg-video-intel-2.3.2/src/i830.h 2008-09-21
20:46:31.0 +
+++ new-xserver-xorg-video-intel-2.3.2/src/i830.h 2008-09-21
20:46:31.0 +
@@ -516,6 +516,7 @@
Bool XvDisabled;/* Xv disabled in PreInit. */
Bool XvEnabled; /* Xv enabled for this generation. */
+ Bool XvPreferOverlay;
#ifdef I830_XV
int colorKey;
diff -rN -u old-xserver-xorg-video-intel-2.3.2/src/i830_video.c
new-xserver-xorg-video-intel-2.3.2/src/i830_video.c
--- old-xserver-xorg-video-intel-2.3.2/src/i830_video.c 2008-09-21
20:46:31.0 +
+++ new-xserver-xorg-video-intel-2.3.2/src/i830_video.c 2008-09-21
20:46:31.0 +
@@ -611,7 +611,6 @@
{
texturedAdaptor = I830SetupImageVideoTextured(pScreen);
if (texturedAdaptor != NULL) {
- adaptors[num_adaptors++] = texturedAdaptor;
xf86DrvMsg(pScrn-scrnIndex, X_INFO, Set up textured video\n);
} else {
xf86DrvMsg(pScrn-scrnIndex, X_ERROR,
@@ -625,7 +624,6 @@
{
overlayAdaptor = I830SetupImageVideoOverlay(pScreen);
if (overlayAdaptor != NULL) {
- adaptors[num_adaptors++] = overlayAdaptor;
xf86DrvMsg(pScrn-scrnIndex, X_INFO, Set up overlay video\n);
} else {
xf86DrvMsg(pScrn-scrnIndex, X_ERROR,
@@ -633,6 +631,16 @@
}
I830InitOffscreenImages(pScreen);
}
+
+if (overlayAdaptor pI830-XvPreferOverlay)
+ adaptors[num_adaptors++] = overlayAdaptor;
+
+if (texturedAdaptor)
+ adaptors[num_adaptors++] = texturedAdaptor;
+
+if (overlayAdaptor !pI830-XvPreferOverlay)
+ adaptors[num_adaptors++] = overlayAdaptor;
+
#ifdef INTEL_XVMC
if (intel_xvmc_probe(pScrn)) {
if (texturedAdaptor)
Bug#469295: xserver-xorg-video-i810: do not fail to set XV_PIPE if not in clone mode
Package: xserver-xorg-video-i810
Version: 2:1.7.2-4
Severity: normal
Tags: patch
While working with xine-lib, I encountered an issue only in etch with i810 :
Calling xine_close_video_driver while using an XV output raises a BadMatch
error.
This is easily shown using the muxine reference implementation[1] and playing
a video till the end.
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (XVideo)
Minor opcode of failed request: 13 ()
Serial number of failed request: 88
Current serial number in output stream: 95
[1] http://xinehq.de/index.php/samplecode
Minor opcode 13 is XvSetPortAttribute :
$ grep 13 /usr/include/X11/extensions/Xvproto.h
#define xv_SetPortAttribute 13
Playing a bit with gdb, using XSynchronize() and a breakpoint on
XvSetPortAttribute, I found out that the offending port attribute was XV_PIPE.
Xine, upon closing the video driver, restores all the port attributes value to
the state in which they were before Xine video driver was started. But
setting XV_PIPE to its default value '0' does not work if clone mode is
disabled in i810. Here is a simple program that shows the issue. The program
simply tries to restore the XV_PIPE attribute to 0.
--
#include stdio.h
#include X11/Xlib.h
#include X11/extensions/Xvlib.h
// Compile with :
// $ gcc -lXv -o test_spa test_spa.c
int main(int argc, char **argv){
Display *display;
XvPortID port = 57; // Find this in the output of xvinfo | grep 'port base'
char *attr_name = XV_PIPE;
Atom attr;
int p_value;
display = XOpenDisplay(:0.0);
XSynchronize(display, True);
attr = XInternAtom(display, attr_name, False);
printf(%s is %d\n, attr_name, (int)attr);
XvGetPortAttribute(display, port, attr, p_value);
printf(%s has value %d\n, attr_name, p_value);
printf(Trying to set %s to %d...\n, attr_name, p_value);
if( XvSetPortAttribute(display, port, attr, p_value) == Success ){
printf( success.\n);
}else{
printf( failed!\n);
}
XCloseDisplay(display);
return 0;
}
--
Output is :
$ ./test_spa
XV_PIPE is 77
XV_PIPE has value 0
Trying to set XV_PIPE to 0...
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (XVideo)
Minor opcode of failed request: 13 ()
Serial number of failed request: 13
Current serial number in output stream: 14
I really do not understand all this video driver stuff, but here is a simple
patch that fixes the problem for me.
diff -rN -u old/debian/patches/12-set_xv_pipe.patch
new/debian/patches/12-set_xv_pipe.patch
--- old/debian/patches/12-set_xv_pipe.patch 1970-01-01 01:00:00.0
+0100
+++ new/debian/patches/12-set_xv_pipe.patch 2008-03-04 14:19:02.0
+0100
@@ -0,0 +1,21 @@
+Tue Mar 4 13:42:17 CET 2008 Alexandre Rossi [EMAIL PROTECTED]
+ * success if setting XV_PIPE to same value
+diff -rN -u old/src/i830_video.c new/src/i830_video.c
+--- old/src/i830_video.c 2008-03-04 13:44:52.0 +0100
new/src/i830_video.c 2008-03-04 13:44:52.0 +0100
+@@ -945,7 +945,13 @@
+ ErrorF(CONTRAST\n);
+ if (*pI830-overlayOn)
+ OVERLAY_UPDATE;
+- } else if (pI830-Clone attribute == xvPipe) {
++ } else if (attribute == xvPipe) {
++ if (!pI830-Clone) {
++ if (value == pPriv-pipe)
++return Success;
++ else
++return BadMatch;
++ }
+ if ((value 0) || (value 1))
+ return BadValue;
+ pPriv-pipe = value;
+
diff -rN -u old/debian/patches/series
new-xserver-xorg-video-i810-1.7.2-4+xvpipebadmatch/debian/patches/series
--- old/debian/patches/series 2008-03-04 14:19:01.0 +0100
+++ new/debian/patches/series 2008-03-04 14:19:02.0 +0100
@@ -1,3 +1,4 @@
10-overlay_fix_lockup.patch
11-xv_lockup.patch
+12-set_xv_pipe.patch
20-i915_bios.patch
(it's crappy because the patch overlaps 10-overlay_fix_lockup.patch)
Upstream should not be interested because it seems that clone mode has
completely been rewritten since. The new implementation is not affected by this
issue (i.e. no problem in lenny or sid).
Anyway, I do not know if this should be fixed or not, but I wanted to share
what I had found out, and I do not have a blog ;)
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-vserver-amd64
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Versions of packages xserver-xorg-video-i810 depends on:
ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries
ii xserver-xorg-core 2:1.1.1-21etch4 X.Org X server -- core server
xserver-xorg-video-i810 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438619: Fixed for me
Hi, This is fixed for me in version 2:2.2.0-1 Cheers, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438619: xserver-xorg-video-intel: resets brightness to maximum upon chvt
Could you try reverting the following commit in 2.1.1? http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commitdiff;h=a85dd7adc35601a988b1001e8b3c8aa4d53de0c0;hp=c989cb4897e2e2d395c52df4822290a767cdc866 I reverted the commit in the git trunk (git revert 0da4f2b0cd7203377ad10407928a367b8c6d310e seems to have done the trick) and it fixes the problem. Also, testing the latest git code might be nice anyway. There's an howto at http://bgoglin.livejournal.com/10936.html I can reproduce the bug using the git trunk. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438619: xserver-xorg-video-intel: resets brightness to maximum upon chvt
Package: xserver-xorg-video-intel Version: 2:2.1.1-1 Severity: normal Since the upgrade to 2:2.1.1-1, LCD brightness is set to the maximum when switching to a virtual console or from a virtual console back to X. I use the sony-laptop module on vanilla kernel 2.6.22 to set the brightness on my laptop. # cat /sys/class/backlight/sony/actual_brightness 0 # chvt 1 (coming back using CTRL+ALT+F7) # cat /sys/class/backlight/sony/actual_brightness 50 (and screen is very bright) Same behavior when playing a video (mplayer -vo xv or -vo x11) : $ cat /sys/class/backlight/sony/actual_brightness 0 $ mplayer some_video.mpeg $ cat /sys/class/backlight/sony/actual_brightness 50 (and screen is very bright) Fixing the problem until the next chvt or the next video playback : # echo 1 /sys/class/backlight/sony/brightness Downgrading to xserver-xorg-video-intel (2:2.1.0-2) fixes the problem. Cheers, Alex -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-12-09 17:47 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1736632 2007-08-09 19:39 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 4402 2007-06-27 19:46 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # Configuration file for Debian X.org and Vaio VGN-B1VP Section Files FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID FontPath/usr/share/fonts/truetype FontPath/usr/local/share/fonts/truetype FontPath/usr/lib/X11/fonts/CID FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi:unscaled FontPath/usr/lib/X11/fonts/75dpi:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/misc FontPath/usr/share/fonts/X11/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/share/fonts/X11/75dpi EndSection Section Module # LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord # Loadspeedo Loadsynaptics Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout fr EndSection Section InputDevice Driversynaptics IdentifierAlps Touchpad OptionDevice/dev/psaux OptionProtocol auto-dev OptionLeftEdge 120 OptionRightEdge 830 OptionTopEdge 120 OptionBottomEdge650 OptionFingerLow 14 OptionFingerHigh15 OptionMaxTapTime180 # Option FastTaps True OptionMaxTapMove110 OptionEmulateMidButtonTime 75 OptionVertScrollDelta 20 OptionHorizScrollDelta 20 OptionMinSpeed 0.3 OptionMaxSpeed 0.75 OptionAccelFactor 0.015 OptionEdgeMotionMinSpeed200 OptionEdgeMotionMaxSpeed200 OptionUpDownScrolling 1 OptionCircularScrolling 1 OptionCircScrollDelta 0.1 OptionCircScrollTrigger 2 # SHMConfig is needed by syndaemon Option SHMConfig on # Option Repeater /dev/ps2mouse EndSection Section InputDevice Identifier Configured Mouse Driver mouse # Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section Device Identifier Carte vido gnrique Driver intel Option DRI Option EnablePageFliptrue Option
Bug#421418: No XV here too
Does this also happen if you don't use Option SWcursor or enable the DRI? Disabling SWcursor partially fixes the problem : XV is enabled but I get the blue screen upon xv input. Upgrading to xserver-xorg-video-intel 2.0.0.0-2 fixes the problem. Thanks! I had SWCursor enabled because of suspend to RAM problems (cursor did not show upon resuming) but this is not an issue anymore with the -intel driver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
Please post a full log file from starting the X server without the VideoRam directive. Here it is (attached). An extract that I find relevant : (II) intel(0): I830CheckAvailableMemory: 440316 kB available (==) intel(0): VideoRam: 131072 KB (II) intel(0): Allocating 5472 scanlines for pixmap cache (II) intel(0): Memory allocation layout: (II) intel(0): 0x-0x0001: ring buffer (128 kB) (II) intel(0): 0x0002-0x00027fff: logical 3D context (32 kB) (II) intel(0): 0x0003-0x02127fff: front buffer (33760 kB) (II) intel(0): 0x007df000:end of stolen memory (II) intel(0): 0x02128000-0x02137fff: xaa scratch (64 kB) (II) intel(0): 0x0800:end of aperture (II) intel(0): front buffer is not tiled (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. Xorg.0.log.gz Description: GNU Zip compressed data
Bug#421418: No XV here too
Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? Nothing like that in the BIOS menus. Note that some BIOSes obfuscate it as DVMT (Dynamic Video Memory Technology) or some other fancy marketing term. The BIOS of my VAIO VGN-B1VP does not have more than Date, Password, IDE devices and Boot device settings. Anyway this used to work perfectly with xserver-xorg-video-i810, so this seems to be a problem with the new driver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? Nothing like that in the BIOS menus. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
Hi, (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. If I explicitely use VideoRam 32768 in xorg.conf, xorg does not start and fails with the following message : (II) intel(0): Kernel reported 110080 total, 1 used (II) intel(0): I830CheckAvailableMemory: 440316 kB available (**) intel(0): VideoRam: 32768 KB (II) intel(0): Allocating 5273 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? As indicated here, try commenting out the VideoRam directive in xorg.conf. If I do, X.org starts but no XV, which is deactivated due to failing overlay register allocation . Alexandre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
Hi, Same behavior here. As this has not been said, I add my comments. It is in fact XV that does not work. I have no external screen connected. $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) $ xvinfo X-Video Extension version 2.2 screen #0 no adaptors present $ grep -i xv /var/log/Xorg.0.log (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. If I explicitely use VideoRam 32768 in xorg.conf, xorg does not start and fails with the following message : (II) intel(0): Kernel reported 110080 total, 1 used (II) intel(0): I830CheckAvailableMemory: 440316 kB available (**) intel(0): VideoRam: 32768 KB (II) intel(0): Allocating 5273 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 Everything works well with the older i810 driver, Hoping to help, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#285818: xserver-xfree86: Display corruption for i855GM with external monitor
Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding a display corruption on the i855GM chipset with an external monitor. A follow-up seems to claim that the bug could be closed. Did any of you guys reproduce this problem recently? If not, I will close this bug in the next weeks. For all I know, you can close the bug, I haven't encountered it for years now. Cheers, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#285818: External CRT clone with i810 driver
Hi all, This is an answer for a fairly old conversation, but I could not have left it unanswered. On 9/1/05, Zsolt Rizsanyi [EMAIL PROTECTED] wrote: What worked for me is to add this to my xorg.conf: Section Device Identifier Generic Video Card Driver i810 Option MonitorLayout CRT,LFP Option Clone true EndSection Works perfectly. Thanks a lot for the directions. This works giving me cloned output on the laptop and CRT. Overlay only works outputs to the laptop, but it can be changed using xv_attr utility (so you can watch films from a projector ;) Works perfectly. Wrote a little script to swap overlay pipes (sorry for the poor scripting, but it works...) : attached. Is i855crt deprecated since the inclusion of X.org in Debian? I am not sure since switching with Fn+F5 does not work it would be nice to make i855crt work with it. With the new driver, it appears there is no need for i855crt. Should bug #285818 be closed? It definitely needs some updating :) Bug CC'd Cheers, swap_overlay_pipe Description: Binary data
