Bug#523589: xserver-xorg-video-radeon: dualhead broke with upgrade

2009-05-14 Thread di dit
The last upload solved this problem with xserver-xorg-video-radeon
version 1:6.12.2-2.
I think this bug can be closed now.

Thanks for your help,

didit.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#523589: xserver-xorg-video-radeon: dualhead broke with upgrade

2009-04-11 Thread di dit
Package: xserver-xorg-video-radeon
Version: 1:6.12.2-1
Severity: normal

The dualhead setup I've been using for more than 6 months broke up with
the last upgrade. The two identical monitors work fine in clone mode but
the following command results in a black screen on DVI-1 (the monitor
goes to standby mode it seems) while the display on DVI-0 is changed as
expected.
  xrandr --output DVI-1 --left-of DVI-0
At this stage, switching to the console (CTRL+ALT+F1) behave as expected
(both monitors display the same text) but switching back to X11
(CTRL+ALT+F7) restores the same situation (i.e. DVI-1 is black and DVI-0
displays the right half of the background image).

I had no success tweaking xorg.conf to get the dualhead output either so
only the clone mode works.

-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 mar  2 11:31 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1876400 avr  9 01:45 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller: ATI Technologies Inc RV610 [Radeon
HD 2400 XT]

/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 1403 avr 10 16:06 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "fr"
Option  "XkbVariant""latin9"
Option  "XkbOptions""lv3:ralt_switch"
EndSection

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

Section "Device"
Identifier  "videocard"
Option  "monitor-DVI-0" "dvi0"
Option  "monitor-DVI-1" "dvi1"
EndSection

Section "Monitor"
Identifier "dvi0"
#   Option "Position" "1280 0"
EndSection

Section "Monitor"
Identifier "dvi1"
#   Option "LeftOf" "dvi0"
#   Option "RightOf" "dvi0"
#   Option "Position" "1280 0"
EndSection

Section "Screen"
Identifier  "screen"
Device  "videocard"
SubSection "Display"
Depth   24
Virtual 2600 1024
EndSubSection
EndSection


Xorg X server log files on system:
-rw-r--r-- 1 root root 49504 avr 10 19:00 /var/log/Xorg.0.log

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

X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-1-amd64 x86_64 Debian
Current Operating System: Linux noee 2.6.29-1-amd64 #1 SMP Sat Apr 4
16:54:07 UTC 2009 x86_64
Build Date: 08 April 2009  11:41:45PM
xorg-server 2:1.6.0-1 (jcris...@debian.org)
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: Fri Apr 10 17:30:43 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section.  Using the first Screen section.
(**) |-->Screen "screen" (0)
(**) |   |-->Monitor ""
(**) |   |-->Device "videocard"
(==) No monitor specified for screen "screen".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices be

Bug#523589: xserver-xorg-video-radeon: dualhead broke with upgrade

2009-04-15 Thread di dit
2009/4/14 Alex Deucher :
> Both heads are probably using the same crtc, but xrandr isn't smart
> enough to assign a different one.  You can see what crtc is in use by
> running xrandr --verbose.  You can assign a different crtc to the
> other head like so:
> xrandr --output DVI-1 --crtc 1 --mode 1280x1024 --left-of DVI-0


Thanks for the suggestion. Unfortunately, it doesn't solve my problem.
Here are the results of some tests obtained using the following
minimal xorg.conf file:
Section "Screen"
Identifier  "screen"
SubSection "Display"
Depth   24
Virtual 2600 1024
EndSubSection
EndSection

The output of xrandr --verbose at each step is given in the attached file.

1/ startx (window manager e16) results in monitors in clone mode as expected.
DVI-0 and DVI-1 do indeed use the same crtc (0).

2/ xrandr --output DVI-0 --crtc 0 --mode 1280x1024
nothing happens (as expected)

3/ xrandr --output DVI-1 --crtc 1 --mode 1280x1024
The monitor connected to DVI-0 enter power save mode.

4/ xrandr --output DVI-0 --off
nothing happens except that the following command wouldn't change
anything without it.

5/ xrandr --output DVI-0 --crtc 0 --mode 1280x1024
DVI-0 monitor goes on, DVI-1 monitor goes into power save mode

Another "funny" issue is that after running startx and without
"playing" with xrandr, if I switch off the
monitor connected to DVI-1 then the mouse pointer doesn't move on the
other monitor. This problem
doesn't exist when the monitor connected to DVI-1 is on and the other one off.


log.radeon
Description: Binary data


Bug#523589: xserver-xorg-video-radeon: dualhead broke with upgrade

2009-04-16 Thread di dit
2009/4/15 Alex Deucher :
> Sounds like:
> https://bugs.freedesktop.org/show_bug.cgi?id=21199

Indeed.

> Does:
> xset dpms force off
> followed by moving the mouse cause both screens to come on?

Yes it does. Thanks for the workaround!
I'm ready to test patches to solve this issue if needed.
Thank you very much for your help.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#523589: xserver-xorg-video-radeon: dualhead broke with upgrade

2009-04-16 Thread di dit
2009/4/16 Alex Deucher :
> Does reverting the commit (f8c7d6a6162196a743f6885ecaf63ba50de1722a)
> mentioned in the bug above fix the issue?

Yes it does. Congratulations, you've found the culprit!
(Sorry, I didn't notice earlier that you already suspected this commit.)



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Where to report r300 Unknown device ID ?

2006-07-11 Thread di dit

I was pleased to see that since I upgraded to debian kernel
linux-image-2.6.17-1-em64t-p4-smp,
DRI works on my system. A big "thank you" to everybody involved in
this, including the packagers
of xorg and of the linux kernel.

The graphic board (lspci):
ATI Technologies Inc RV370 5B64 [FireGL V3100 (PCIE)] (rev 80)

System: up to date debian/unstable, amd64.

When starting for example glxgears, I see this message:

Unknown device ID 5B64, please report. Assuming plain R300.
*WARN_ONCE*
File r300_state.c function r300Enable line 456
TODO - double side stencil !
***
No ctx->FragmentProgram._Current!!
*WARN_ONCE*
File r300_render.c function r300_get_num_verts line 188
user error: Need more than 2 vertices to draw primitive QS !
***

Where should I report the "unknown device ID"? Should I fill a bug in
the BTS for this?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]