Bug#641197: patch submitted

2012-01-04 Thread James Robertson 
It appears as though a patch has been submitted for this.

http://cgit.freedesktop.org/xorg/lib/libXft/commit/?id=6f1d7bcdd461b1f6cc64370793f52d7c170187d0



-- 
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/CAMALoy_2HyEoV=6iK=1f9eJ8EZ6oBTEzH=3uks6zrdwxgdq...@mail.gmail.com

Bug#630345: gdb trace and logs with experimental drivers

2012-01-04 Thread Craig Small 
I tried the radeon and intel drivers. The intel bit works ok but when i
make a minimal xorg.conf to use the radeon chip the X server crashes.

Attached is the gdb logs and Xorg.0.log files.  I hope these help make
sense of what is going wrong.

 - Craig
-- 
Craig Small VK2XLZ   http://enc.com.au/  csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/  csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5
SignalStop  Print   Pass to program Description
SIGPIPE   NoYes Yes Broken pipe
Starting program: /usr/bin/Xorg :0 -config /root/xorg.conf
[Thread debugging using libthread_db enabled]
[tcsetpgrp failed in terminal_inferior: Operation not permitted]

Program received signal SIGSEGV, Segmentation fault.
0x556157b4 in SetCompatOutput (config=0x55985f80)
at ../../../../hw/xfree86/modes/xf86Crtc.c:1887
1887../../../../hw/xfree86/modes/xf86Crtc.c: No such file or directory.
in ../../../../hw/xfree86/modes/xf86Crtc.c
#0  0x556157b4 in SetCompatOutput (config=0x55985f80)
at ../../../../hw/xfree86/modes/xf86Crtc.c:1887
#1  xf86SetScrnInfoModes (scrn=0x5597f810)
at ../../../../hw/xfree86/modes/xf86Crtc.c:1901
#2  0x55619054 in xf86InitialConfiguration (scrn=0x5597f810, 
canGrow=1) at ../../../../hw/xfree86/modes/xf86Crtc.c:2541
#3  0x7403d573 in drmmode_pre_init (pScrn=, 
drmmode=, cpp=)
at ../../src/drmmode_display.c:1403
#4  0x74039af7 in RADEONPreInit_KMS (pScrn=0x5597f810, 
flags=) at ../../src/radeon_kms.c:725
#5  0x555e65ec in InitOutput (pScreenInfo=0x5595e140, argc=4, 
argv=0x7fffe6d8) at ../../../../hw/xfree86/common/xf86Init.c:580
#6  0x5559581d in main (argc=4, argv=, 
envp=) at ../../dix/main.c:204
#0  0x556157b4 in SetCompatOutput (config=0x55985f80)
at ../../../../hw/xfree86/modes/xf86Crtc.c:1887
test = 
maxmode = 
o = 
compat = 
count = 
output = 
testmode = 
mode = 
mincount = 
#1  xf86SetScrnInfoModes (scrn=0x5597f810)
at ../../../../hw/xfree86/modes/xf86Crtc.c:1901
config = 0x55985f80
crtc = 
last = 
mode = 0x0
#2  0x55619054 in xf86InitialConfiguration (scrn=0x5597f810, 
canGrow=1) at ../../../../hw/xfree86/modes/xf86Crtc.c:2541
config = 
o = 
c = 
crtcs = 0x5598c990
modes = 0x5598c9b0
enabled = 
width = 1024
height = 768
i = 0
have_outputs = 0
success = 0
#3  0x7403d573 in drmmode_pre_init (pScrn=, 
drmmode=, cpp=)
at ../../src/drmmode_display.c:1403
pRADEONEnt = 0x5597fe90
info = 0x55983ec0
i = 
num_dvi = 
num_hdmi = 
#4  0x74039af7 in RADEONPreInit_KMS (pScrn=0x5597f810, 
flags=) at ../../src/radeon_kms.c:725
info = 0x55983ec0
pRADEONEnt = 0x5597fe90
pPriv = 
zeros = {red = 0, green = 0, blue = 0}
tiling = 0
cpp = 
#5  0x555e65ec in InitOutput (pScreenInfo=0x5595e140, argc=4, 
argv=0x7fffe6d8) at ../../../../hw/xfree86/common/xf86Init.c:580
i = 
j = 
k = 
scr_index = 
was_blocked = 0
modulelist = 
optionlist = 0x55976350
screenpix24 = 
pix24 = 
pix24From = X_DEFAULT
pix24Fail = 0
autoconfig = 
configured_device = 
#6  0x5559581d in main (argc=4, argv=, 
envp=) at ../../dix/main.c:204
i = 
alwaysCheckForInput = {0, 1}
A debugging session is active.

Inferior 1 [process 2160] will be killed.

Quit anyway? (y or n) [   686.869] 
X.Org X Server 1.11.99.901 (1.12.0 RC 1)
Release Date: 2011-12-27
[   686.870] X Protocol Version 11, Revision 0
[   686.870] Build Operating System: Linux 3.2.0-rc6+ x86_64 Debian
[   686.870] Current Operating System: Linux rowlf 3.1.0-1-amd64 #1 SMP Fri Dec 
23 16:37:11 UTC 2011 x86_64
[   686.870] Kernel command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 
root=/dev/mapper/rowlf-root ro quiet
[   686.870] Build Date: 29 December 2011  11:08:03PM
[   686.870] xorg-server 2:1.11.99.901-1 (Cyril Brulebois ) 
[   686.870] Current version of pixman: 0.24.0
[   686.870]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   686.870] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   686.870] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan  4 20:46:37 
2012
[   686.871] (++) Using config file: "/root/xorg.conf"
[   686.871] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   686.871]

Bug#630345: gdb trace and logs with experimental drivers

2012-01-04 Thread Michel Dänzer 
On Mit, 2012-01-04 at 20:54 +1100, Craig Small wrote: 
> I tried the radeon and intel drivers. The intel bit works ok but when i
> make a minimal xorg.conf to use the radeon chip the X server crashes.
> 
> Attached is the gdb logs and Xorg.0.log files.  I hope these help make
> sense of what is going wrong.
[...] 
> [   686.871] (++) Using config file: "/root/xorg.conf"
> [   686.871] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> [   686.871] (==) ServerLayout "aticonfig Layout"
> [   686.871] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
> [   686.871] (**) |   |-->Monitor "aticonfig-Monitor[0]-0"
> [   686.872] (**) |   |-->Device "aticonfig-Device[0]-0"

This doesn't look like /root/xorg.conf is very minimal. Please provide
it.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast |  Debian, X and DRI developer



--
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/1325671910.1807.490.camel@thor.local

Bug#652907: #652907 xterm: no UTMP/WTMP update with kfreebsd-amd64

2012-01-04 Thread Thomas Dickey 
...a little more investigation shows that utempter sees /dev/ttyp6
as owned by root.  Bypassing _that_ test lets utempter work.  I'll
investigate to see what solution is appropriate.

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature

Bug#652907: #652907 xterm: no UTMP/WTMP update with kfreebsd-amd64

2012-01-04 Thread Mats Erik Andersson 
The problem seems to be that kfreebsd-amd64 is changing ownership
of a slave device later than linux-i386 is doing. This is not
recogniced in the source of "libutempter/utempter.c".

The following output demonstrates that at the time of evaluating
ptsname(fd), the two systems differ. The call to grantpt() must
be made much earlier in Xterm for the technique to succeed.

  mats@kbsd $ ls -l $(tty)
  crw--w 1 mats tty 0, 106 jan  4 13:19 /dev/ttyp0

  mats@kbsd $ ./a.out
  master at fd 3
  slave pty at /dev/ttyp1
  crw--w 1 root root 0, 108 jan  4 13:18 /dev/ttyp1

Observe my running terminal "/dev/ttyp0" is mine, but not yet
the freshly created "/dev/ttyp1" on GNU/kFreeBSD.

  mats@linux $ ls -l $(tty)
  crw--w 1 mats tty 136, 0 jan  4 13:22 /dev/pts/0

  mats@linux $ ./a.out
  master at fd 3
  slave pty at /dev/pts/3
  crw--w 1 mats tty 136, 3 jan  4 13:21 /dev/pts/3

Here the access was adjusted on the fly with GNU/Linux.

Regards,
  Mats Erik Andersson


#define _GNU_SOURCE
#include 
#include 
#include 

int main(void) {
int f;
char *pp, cmd[40];

if ((f = getpt())< 0)
return 1;

printf("master at fd %d\n", f);
pp = ptsname(f);
printf("slave pty at %s\n", pp);

snprintf(cmd, sizeof(cmd), "ls -l %s", pp);
system(cmd);

return 0;
}



-- 
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/20120104123600.ga27...@mea.homelinux.org

Starting X with VGA on and LVDS off

2012-01-04 Thread Andre Majorel 
What arguments do you pass to startx to enable the VGA output
and disable the LVDS output ?

Thanks in advance.

-- 
André Majorel 
"Like a spambot on lists.debian.org."


-- 
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/20120104122500.gc28...@aym.net2.nerim.net

Re: Starting X with VGA on and LVDS off

2012-01-04 Thread Cyril Brulebois 
Andre Majorel  (04/01/2012):
> What arguments do you pass to startx to enable the VGA output
> and disable the LVDS output ?

Just call xrandr once X is started?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Starting X with VGA on and LVDS off

2012-01-04 Thread Andre Majorel 
On 2012-01-04 14:02 +0100, Cyril Brulebois wrote:
> Andre Majorel  (04/01/2012):
> > What arguments do you pass to startx to enable the VGA output
> > and disable the LVDS output ?
> 
> Just call xrandr once X is started?

Too late, must be done before the window manager starts.

-- 
André Majorel 
If the Debian project published their users' email addresses,
we'd be getting spam. So I'm glad they don't.


-- 
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/20120104143404.gd28...@aym.net2.nerim.net

Re: Starting X with VGA on and LVDS off

2012-01-04 Thread Cyril Brulebois 
Andre Majorel  (04/01/2012):
> Too late, must be done before the window manager starts.

Then your window manager needs to learn about Xrandr.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#630345: gdb trace and logs with experimental drivers

2012-01-04 Thread Alex Deucher 
On Wed, Jan 4, 2012 at 4:54 AM, Craig Small  wrote:
> I tried the radeon and intel drivers. The intel bit works ok but when i
> make a minimal xorg.conf to use the radeon chip the X server crashes.
>
> Attached is the gdb logs and Xorg.0.log files.  I hope these help make
> sense of what is going wrong.
>

Is there any chance you are using a hybrid laptop with both Intel and
AMD GPUs in it?  Based on your log this looks like it a MUX-less one
in which case the discrete AMD card is not actually connected to any
displays (or if it is, it might only be connected to an external
monitor port).  We can double check by posting your dmesg output.
MUX-less systems aren't supported yet as we need a fair amount of drm
and X infrastructure to handle buffer sharing between GPUs and
decoupled display and rendering.

Alex

>  - Craig
> --
> Craig Small VK2XLZ   http://enc.com.au/          csmall at : enc.com.au
> Debian GNU/Linux     http://www.debian.org/      csmall at : debian.org
> GPG fingerprint:     5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5
>
> ___
> xorg-driver-ati mailing list
> xorg-driver-...@lists.x.org
> http://lists.x.org/mailman/listinfo/xorg-driver-ati
>



--
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/cadnq5_mndjlwgye3ju0ey6oj-tktogffoyrhkr4fiyfjutq...@mail.gmail.com

Re: Starting X with VGA on and LVDS off

2012-01-04 Thread Andre Majorel 
On 2012-01-04 15:44 +0100, Cyril Brulebois wrote:
> Andre Majorel  (04/01/2012):
> > Too late, must be done before the window manager starts.
> 
> Then your window manager needs to learn about Xrandr.

So do the apps. Is there really no way to preventively tell X
which outputs to use ?

-- 
André Majorel 
bugs.debian.org, the spammers' favourite.


-- 
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/20120104152701.ge28...@aym.net2.nerim.net

Bug#654612: xserver-xorg-video-nouveau: dual-head DVI-I-2 disconnected GeForce 210 NVa8 (GT218)

2012-01-04 Thread oz 

Package: xserver-xorg-video-nouveau
Version: 1:0.0.15+git20100329+7858345-5
Severity: normal

*** Please type your report below this line ***
Hello,

after changing a GeForce 8600GT with a new GeForce 210 the dual-head 
monitor is
not working any longer. The secondary monitor seems to be disconnected 
now and

falls into standby-mode (no input signal). From Xorg.0.log:

(II) NOUVEAU(0): Output DVI-I-1 connected
(II) NOUVEAU(0): Output DVI-I-2 disconnected
(II) NOUVEAU(0): Using user preference for initial modes
(II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1200

But with the older 8600GT the second monitor is correctly detectable an 
works

like a charm:

(II) NOUVEAU(0): Output DVI-I-1 connected
(II) NOUVEAU(0): Output DVI-I-2 connected
(II) NOUVEAU(0): Using user preference for initial modes
(II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1200
(II) NOUVEAU(0): Output DVI-I-2 using initial mode 1280x1024

It seems like dual-head is not supported by nouveau for a nvidia GeForce 
210 in

Debian/squeeze.

cheers,
oz

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Feb 25  2009 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1733468 Feb 19  2011 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218 [GeForce
210] [10de:0a65] (rev a2)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1149 Jan  4 14:05 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# Sections ServerFlags and InputDevices can be ommitted, when rely on hal.

Section "ServerFlags"
Option  "AutoAddDevices" "false"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules""xorg"
Option  "XkbModel""pc105"
Option  "XkbLayout"   "de"
Option  "XkbVariant"  "nodeadkeys"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
EndSection

Section "Monitor"
Identifier  "Primaerer DVI"
EndSection

Section "Monitor"
Identifier  "Sekundaerer DVI"
Option "RightOf" "Primaerer DVI"
EndSection

Section "Device"
Identifier  "Configured Video Device"
Driver  "nouveau"
Option "Monitor-DVI-I-1" "Primaerer DVI"
Option "Monitor-DVI-I-2" "Sekundaerer DVI"

EndSection

Section "Screen"
Identifier  "Default Screen"
Device "Configured Video Device"
DefaultDepth24
SubSection "Display"
Depth 24
Virtual 3200 1200
EndSubSection
EndSection

Section "ServerLayout"
Identifier  "Default Layout"
Screen  "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 2.6.32-5-686 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 04:15:24 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 23172 Jan  4 14:43 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.29-dsa-ia32 i686 Debian
Current Operating System: Linux oz5 2.6.32-5-686 #1 SMP Mon Oct 3 
04:15:24 UTC

2011 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686
root=/dev/mapper/volgrp1-logvol1 ro quiet
Build Date: 19 February 2011  02:37:36PM
xorg-server 2:1.7.7-13 (Cyril Brulebois )
Current version of pixman: 0.16.4
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: Wed Jan  4 14:41:44 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor ""
(**) |   |-->Device "Configured Video Device"
(==) No monitor specified for screen "Default Screen".
Using a default monitor configuration.
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(**) Opt

Bug#654612: xserver-xorg-video-nouveau: dual-head DVI-I-2 disconnected GeForce 210 NVa8 (GT218)

2012-01-04 Thread Cyril Brulebois 
oz  (04/01/2012):
> Package: xserver-xorg-video-nouveau
> Version: 1:0.0.15+git20100329+7858345-5
> Severity: normal
> 
> […]
> 
> It seems like dual-head is not supported by nouveau for a nvidia
> GeForce 210 in
> Debian/squeeze.

You may want to try backported packages (kernel + driver):
  http://x.debian.net/reference/squeeze-backports.html

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#654612: xserver-xorg-video-nouveau: dual-head DVI-I-2 disconnected GeForce 210 NVa8 (GT218)

2012-01-04 Thread Sven Joachim 
On 2012-01-04 17:04 +0100, Cyril Brulebois wrote:

> oz  (04/01/2012):
>> Package: xserver-xorg-video-nouveau
>> Version: 1:0.0.15+git20100329+7858345-5
>> Severity: normal
>> 
>> […]
>> 
>> It seems like dual-head is not supported by nouveau for a nvidia
>> GeForce 210 in
>> Debian/squeeze.
>
> You may want to try backported packages (kernel + driver):
>   http://x.debian.net/reference/squeeze-backports.html

Since acceleration is disabled for NVA8 by the Squeeze kernel to work
around https://bugs.freedesktop.org/26980, running a kernel
>= 2.6.39 and backported X packages is very much recommended anyway.

Cheers,
   Sven



-- 
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/87ty4bwh81@turtle.gmx.de

Bug#652907: #652907 xterm: no UTMP/WTMP update with kfreebsd-amd64

2012-01-04 Thread Thomas Dickey 
yes - I could see that, and moved grantpt up above the utempter code.
(I also tested that on Solaris 10, to verify the change).

- Original Message -
From: "Mats Erik Andersson" 
To: dic...@his.com
Cc: 652...@bugs.debian.org
Sent: Wednesday, January 4, 2012 7:36:01 AM
Subject: Bug#652907: #652907 xterm: no UTMP/WTMP update with kfreebsd-amd64

The problem seems to be that kfreebsd-amd64 is changing ownership
of a slave device later than linux-i386 is doing. This is not
recogniced in the source of "libutempter/utempter.c".

The following output demonstrates that at the time of evaluating
ptsname(fd), the two systems differ. The call to grantpt() must
be made much earlier in Xterm for the technique to succeed.

  mats@kbsd $ ls -l $(tty)
  crw--w 1 mats tty 0, 106 jan  4 13:19 /dev/ttyp0

  mats@kbsd $ ./a.out
  master at fd 3
  slave pty at /dev/ttyp1
  crw--w 1 root root 0, 108 jan  4 13:18 /dev/ttyp1

Observe my running terminal "/dev/ttyp0" is mine, but not yet
the freshly created "/dev/ttyp1" on GNU/kFreeBSD.

  mats@linux $ ls -l $(tty)
  crw--w 1 mats tty 136, 0 jan  4 13:22 /dev/pts/0

  mats@linux $ ./a.out
  master at fd 3
  slave pty at /dev/pts/3
  crw--w 1 mats tty 136, 3 jan  4 13:21 /dev/pts/3

Here the access was adjusted on the fly with GNU/Linux.

Regards,
  Mats Erik Andersson


#define _GNU_SOURCE
#include 
#include 
#include 

int main(void) {
int f;
char *pp, cmd[40];

if ((f = getpt())< 0)
return 1;

printf("master at fd %d\n", f);
pp = ptsname(f);
printf("slave pty at %s\n", pp);

snprintf(cmd, sizeof(cmd), "ls -l %s", pp);
system(cmd);

return 0;
}






-- 
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/23d1423f-7a5c-4bc3-b2ec-86d8c06f2...@mail-sterling.his.com

Bug#654630: mesa: [m68k] FTBFS due to lack of GCC atomic builtins

2012-01-04 Thread Thorsten Glaser 
Source: mesa
Version: 7.11.2-1

Hi,

mesa FTBFS (with gcc-4.6) with error messages like these:

/tmp/buildd/mesa-7.11.2/build/dri/src/gallium/drivers/r600/../../../../src/gallium/auxiliary/util/u_atomic.h:151:
 undefined reference to _sync_sub_and_fetch_4'

This is due to it using GCC Atomic builtins which are not supported
on all architectures. Can it be told to use libatomic-ops-dev instead,
which implements all this stuff correctly?

Otherwise, PIPE_ATOMIC_OS_UNLOCKED might be an option, but if mesa
is used from threaded programmes, probably unsafe even on !SMP.

Any idea?

Thanks in advance,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)



--
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/alpine.deb.2.02.1201041833000.5...@tglase.lan.tarent.de

Bug#654612: xserver-xorg-video-nouveau: dual-head DVI-I-2 disconnected GeForce 210 NVa8 (GT218)

2012-01-04 Thread oz 

It seems like dual-head is not supported by nouveau for a nvidia
GeForce 210 in
Debian/squeeze.

You may want to try backported packages (kernel + driver):
  http://x.debian.net/reference/squeeze-backports.html


Since acceleration is disabled for NVA8 by the Squeeze kernel to work
around https://bugs.freedesktop.org/26980, running a kernel

= 2.6.39 and backported X packages is very much recommended anyway.


Thanks KiBi and Sven,

not an easy decision for me. If I understand it correctly, I first have 
to fetch the new kernel together with linux-base ...


apt-get -s -t squeeze-backports install linux-image-2.6.39-bpo.2-686-pae 
linux-base

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  initramfs-tools
Suggested packages:
  bash-completion linux-doc-2.6.39
The following NEW packages will be installed:
  linux-image-2.6.39-bpo.2-686-pae
The following packages will be upgraded:
  initramfs-tools linux-base
2 upgraded, 1 newly installed, 0 to remove and 75 not upgraded.
Inst initramfs-tools [0.98.8] (0.99~bpo60+1 Debian 
Backports:squeeze-backports [all])
Inst linux-base [2.6.32-38] (3.3~bpo60+1 Debian 
Backports:squeeze-backports [all])
Inst linux-image-2.6.39-bpo.2-686-pae (2.6.39-3~bpo60+1 Debian 
Backports:squeeze-backports [i386])

Conf initramfs-tools (0.99~bpo60+1 Debian Backports:squeeze-backports [all])
Conf linux-base (3.3~bpo60+1 Debian Backports:squeeze-backports [all])
Conf linux-image-2.6.39-bpo.2-686-pae (2.6.39-3~bpo60+1 Debian 
Backports:squeeze-backports [i386])


But after a reboot with this new kernel I would expect, that my current 
nouveau xserver will be unable to start (according README.Debian kernels 
>= 2.6.34 are incompatible). Having just the text-console at this point 
of time I could install the new x-system then like ...


apt-get install -t squeeze-backports xorg xserver-xorg xserver-xorg-core 
xserver-xorg-input-all xserver-xorg-video-all


If this xorg update would be successful, I can expect that the nouveau 
xserver starts after a new reboot, right?


But if the new xserver should fail for some reason I guess I will be in 
a dilemma; starting the previous kernel in grub will not match the new 
installed nouveau xserver and a downgrade of xorg will not be possible. 
I would sit there without graphical desktop ...


Are there any success-stories known to calculate the risk?

cheers,
Oz




--
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/4f04d225.10...@bluemonk.de

Bug#640464: xterm: rendering problems (pixels not erased?)

2012-01-04 Thread Thomas Dickey 
On Sat, Dec 31, 2011 at 02:26:35AM +0100, Vincent Lefevre wrote:
> On 2011-12-30 20:16:43 -0500, Thomas Dickey wrote:
> > Which window manager are you using?
> 
> fvwm

I'm baffled by this one (not able to reproduce the problem).

In my initial response, I had in mind that perhaps the optimization that I did
in #274/#275 to discard extra configure-events, and extra exposures (due to
rapid scrolling) was the problem.  If I could reproduce it, I'd do that with
the debugging traces and re-examine the changes from #274/#275.

Your xtrace output is showing only a few exposure events:

5.711 000:>:010b: Event Expose(12) window=0x02c00018 x=9 y=0 width=484 
height=784 count=0x
5.711 000:>:010b: Event Expose(12) window=0x02c00019 x=0 y=0 width=8 height=784 
count=0x
11.726 000:>:0242: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=108 
width=275 height=3329 minor-opcode=0x000d count=0x major-opcode=0x3e
11.729 000:>:024d: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=108 
width=275 height=3329 minor-opcode=0x000d count=0x major-opcode=0x3e
11.731 000:>:025e: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=82 
width=275 height=9985 minor-opcode=0x0027 count=0x major-opcode=0x3e
26.349 000:>:0396: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=108 
width=275 height=3329 minor-opcode=0x000d count=0x major-opcode=0x3e
26.351 000:>:03a5: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=108 
width=275 height=3329 minor-opcode=0x000d count=0x major-opcode=0x3e
26.353 000:>:03c2: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=17 
width=275 height=26625 minor-opcode=0x0068 count=0x major-opcode=0x3e
27.995 000:>:0455: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=43 
width=275 height=19969 minor-opcode=0x004e count=0x major-opcode=0x3e
34.750 000:>:053f: Event GraphicsExposure(13) drawable=0x02c00018 x=216 y=2 
width=275 height=30465 minor-opcode=0x0077 count=0x major-opcode=0x3e
45.532 000:>:0560: Event Expose(12) window=0x02c00018 x=9 y=0 width=484 
height=121 count=0x0002
45.532 000:>:0560: Event Expose(12) window=0x02c00018 x=9 y=121 width=207 
height=503 count=0x0001
45.532 000:>:0560: Event Expose(12) window=0x02c00018 x=9 y=624 width=484 
height=160 count=0x
45.532 000:>:0560: Event Expose(12) window=0x02c00019 x=0 y=0 width=8 
height=784 count=0x

Some of the heights look too large to me, those at 26.353 and 27.995,
and the GraphicsExposure widths all look too small (perhaps those are
the highlighting - but still, I'd expect more than just that).

This type of problem is also possible in the X server - usually for
specific drivers.

(My display here is just vesa - mostly am using Parallels on Mac OS X -
so the X server tends to be more stable than some of the drivers).

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature