Bug#546588: Suggestion for slow radeon (debian bug 546588)

2010-03-27 Thread GSR
Hi:

I was reading the list of radeon reports and found yours. Time ago I
experienced a problem with similar symptoms, that got fixed by adding
Option "MigrationHeuristic" "greedy" (that go back to XAA, as other
person suggested). Maybe your case is the same.

I got the idea to test that option from:
http://lists.freedesktop.org/archives/xorg/2008-May/thread.html#35451

GSR
 



-- 
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/20100328033003.ga26...@crossbow.battleship



Bug#568236: xserver-xorg-input-wacom: Not fixed for me

2010-03-27 Thread John Sullivan
Package: xserver-xorg-input-wacom
Version: 0.10.3+20100109-1
Severity: normal


On my Thinkpad X200t running unstable, I'm still seeing this bug,
after updating today and restarting X.

I have no xorg.conf file.

xinput list:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ "PS/2 Generic Mouse"  id=11   [slave  pointer  (2)]
⎜   ↳ "Macintosh mouse button emulation"id=12   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ "Power Button"id=6[slave  keyboard (3)]
↳ "Video Bus"   id=7[slave  keyboard (3)]
↳ "Sleep Button"id=8[slave  keyboard (3)]
↳ "UVC Camera (17ef:480c)"  id=9[slave  keyboard (3)]
↳ "AT Translated Set 2 keyboard"id=10   [slave  keyboard (3)]
↳ "ACPI Virtual Keyboard Device"id=13   [slave  keyboard (3)]
↳ "ACPI Virtual Keyboard Device"id=14   [slave  keyboard (3)]
↳ "ThinkPad Extra Buttons"  id=15   [slave  keyboard (3)]

lshal|grep -i wacom:

  info.product = 'Wacom Serial Tablet PC Pen Tablet/Digitizer'  (string)
  pnp.description = 'Wacom Serial Tablet PC Pen Tablet/Digitizer'  (string)
  info.product = 'Wacom Serial Tablet PC Pen Tablet/Digitizer'  (string)

Xorg log:

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.26-2-amd64 x86_64 Debian
Current Operating System: Linux myles 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 
22:40:40 UTC 2010 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 
root=/dev/mapper/myles-root ro quiet vdso32=0
Build Date: 23 March 2010  04:00:24PM
xorg-server 2:1.7.6-1 (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: Sat Mar 27 17:01:10 2010
(II) Loader magic: 0x7c3240
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 8

(--) PCI:*(0:0:2:0) 8086:2a42:17aa:20e4 Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller rev 7, Mem @ 0xf200/4194304, 
0xd000/268435456, I/O @ 0x1800/8
(--) PCI: (0:0:2:1) 8086:2a43:17aa:20e4 Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller rev 7, Mem @ 0xf240/1048576
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier  "Builtin Default intel Device 0"
Driver  "intel"
EndSection
Section "Screen"
Identifier  "Builtin Default intel Screen 0"
Device  "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default vesa Device 0"
Driver  "vesa"
EndSection
Section "Screen"
Identifier  "Builtin Default vesa Screen 0"
Device  "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default fbdev Device 0"
Driver  "fbdev"
EndSection
Section "Screen"
Identifier  "Builtin Default fbdev Screen 0"
Device  "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier  "Builtin Default Layout"
Screen  "Builtin Default intel Screen 0"
Screen  "Builtin Default vesa Screen 0"
Screen  "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specifie

Bug#558788: add nouveau in squeeze, please

2010-03-27 Thread Adrian Glaubitz
Package: xserver-xorg-video-nouveau
Severity: normal

Hi,

there are a few problems which will probably prevent nouveau
from being added to Squeeze:

First, Squeeze is certainly going to be shipped with 2.6.32
since it is a kernel with long-term support from upstream.
Since Debian puts a strong emphasis on stability and long-term
stable support, it is very likely that it will be shipped with
2.6.32. The problem now is that nouveau modesetting and drm
support is not in 2.6.32 but it was first introduced with
2.6.33. Thus, in order to use nouveau together with Squeeze,
the nouveau drm and modesetting code will have to be backported
from 2.6.33 which Ubuntu did for their due 10.04 release.

Secondly, even if the nouveau code gets backported to 2.6.32,
there is still the problem that the nouveau xorg driver has
received significant changes in the drm API which are incompatible
to all drm code prior to 2.6.34. Thus, the current upstream
nouveau version cannot be used without a lot of efforts of
backporting or people will have to stick to the current version
of nouveau from experimental which, however, still needs the
backporting of the drm code from 2.6.32 to 2.6.33.

My suggestion therefore is to drop nouveau for Squeeze and
rather wait until 2.6.34 is released and makes it into unstable.
At this point, the kernel will provide all necessary drm and
modesetting code in a hopefully mature state.

Adrian

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20100327232354.28775.23635.report...@z6.physik.fu-berlin.de



Bug#575636: marked as done (build-depends-on-obsolete-package: xutils)

2010-03-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Mar 2010 22:34:59 +0200
with message-id <87bpe9lczw@jondo.cante.net>
and subject line Bug#575636 Close
has caused the Debian Bug report #575636,
regarding build-depends-on-obsolete-package: xutils
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
575636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xutils
Version: 1:7.5+5
Severity: important


The package depends on obsolete xutils which is going away.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xutils depends on:
ii  x11-session-utils 7.5+1  X session utilities
ii  x11-utils 7.5+3  X11 utilities
ii  x11-xfs-utils 7.4+1  X font server utilities
ii  x11-xserver-utils 7.5+1  X server utilities
ii  xfonts-utils  1:7.5+2X Window System font utility progr

xutils recommends no packages.

xutils suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Incorrect destination package for the bug. Closed by submitter.

--- End Message ---


Bug#575636: build-depends-on-obsolete-package: xutils

2010-03-27 Thread Jari Aalto
Package: xutils
Version: 1:7.5+5
Severity: important


The package depends on obsolete xutils which is going away.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xutils depends on:
ii  x11-session-utils 7.5+1  X session utilities
ii  x11-utils 7.5+3  X11 utilities
ii  x11-xfs-utils 7.4+1  X font server utilities
ii  x11-xserver-utils 7.5+1  X server utilities
ii  xfonts-utils  1:7.5+2X Window System font utility progr

xutils recommends no packages.

xutils suggests no packages.

-- no debconf information



-- 
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/20100327192543.28168.65041.report...@jondo.cante.net



Bug#575585: xserver-xorg-video-radeon: [KMS] Crashes when switching VTs

2010-03-27 Thread Michel Dänzer
On Sat, 2010-03-27 at 12:52 +0100, Josselin Mouette wrote: 
> 
> I don’t really know how to obtain a better backtrace. I haven’t managed 
> to make it dump core, and using gdb directly on it prevents me from 
> switching VTs when the server crashes.

Usually it's best to run gdb from a remote shell.


> Note that when it happens, the kernel logs something like this:
> Mar 27 12:38:42 tomoyo kernel: [  199.622777] Unpin not necessary for 
> 88007b6c2e00 !

That's harmless.


-- 
Earthling Michel Dänzer   |http://www.vmware.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/1269697180.3981.71.ca...@thor.local