Bug 539008

Summary:	radeonhd [Mobility Radeon HD 2600 XT] Second Xserver hangs
Product:	[openSUSE] openSUSE 11.2	Reporter:	Elmar Stellnberger <estellnb>
Component:	X.Org	Assignee:	Matthias Hopf <mhopf>
Status:	RESOLVED UPSTREAM	QA Contact:	E-mail List <xorg-maintainer-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	eich, sndirsch
Version:	Milestone 7
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	sax-logs and console output

Description Elmar Stellnberger 2009-09-14 15:15:34 UTC

User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.1 (like Gecko) SUSE

 After installation I tried to start SaX2 from out of KDE4 but SaX2 had always been hanging. Nonetheless it was possible to start SaX2 from the text console (see attached logs). Moving /etc/X11/xorg.conf.install to /etc/X11/xorg.conf (no xorg.conf in place after installation!) has somehow helped SaX2 to set up an appropriate screen configuration (see attachement). The problems are most likely related to the current radeonhd-disaster (https://bugs.freedesktop.org/show_bug.cgi?id=23927).

Reproducible: Sometimes

Comment 1 Elmar Stellnberger 2009-09-14 15:20:37 UTC

Created attachment 318133 [details]
sax-logs and console output

Comment 2 Stefan Dirsch 2009-09-14 15:42:38 UTC

I don't believe this is related to SaX2. Without existing xorg.conf SaX2 creates a new xorg.conf from scratch and starts a new Xserver. I think this is the issue
here. 2 Xservers running at the same time.

Comment 3 Elmar Stellnberger 2009-09-14 17:01:06 UTC

The bug title is somehow wrong: It should be: SaX2 hangs on startup; has nothing to do with Xinerama or dual screen setup.

Comment 4 Stefan Dirsch 2009-09-14 17:56:54 UTC

1, Xinerama or dual screen setup has nothing to do with 2 Xservers running at the
   same time.
2. I explained in comment #2, why I renamed the bug title.

BTW, it doesn't make sense to run sax2 for configuring a dual head setup with
radeonhd. You can do this on-the-fly instead.

Comment 5 Elmar Stellnberger 2009-09-14 19:44:56 UTC

No, I can`t. It is not supported until a big enough virtual screen is reserved by the xorg.conf.

> xrandr -q
Screen 0: minimum 1600 x 1200, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
   1600x1200      77.0*


maximum 1600 x 1200
I need: maximum 3200x1200
- and this is only possible by an appropriate SaX2-configured xorg.conf!!!

Comment 6 Stefan Dirsch 2009-09-14 21:02:34 UTC

> maximum 1600 x 1200
> I need: maximum 3200x1200
> - and this is only possible by an appropriate SaX2-configured xorg.conf!!!

This is no longer required since today.

xorg-x11-driver-video-radeonhd:
-------------------------------------------------------------------
Fri Sep 11 15:37:16 CEST 2009 - mhopf@novell.com

- bug519261-increase-virtual.diff:
  * Increase virtual on startup if enough Gfx RAM is available.

xorg-x11-driver-video:
-------------------------------------------------------------------
Mon Sep 14 16:32:27 CEST 2009 - mhopf@novell.com

- bug519261-increase-virtual.diff for radeon and nv:
  * Increase virtual on startup if enough Gfx RAM is available.

Comment 7 Elmar Stellnberger 2009-09-15 08:57:36 UTC

  If this is not an issue then we have plenty of other issues; see https://bugs.freedesktop.org/show_bug.cgi?id=23927#c6.
The decision to drop elaborate xorg.confs is simply fatal.

Comment 8 Elmar Stellnberger 2009-09-15 12:51:01 UTC

  Have downgraded to xorg-x11 from Milestone 6 and see SaX started to work perfectly; so this is not a bug of SaX but of the radeonhd driver. Please address this issue upstreams!:  https://bugs.freedesktop.org/show_bug.cgi?id=23927#c6. - and do not drop SaX (Bug 539004) - it is radeonhd which fails here.

Comment 9 Elmar Stellnberger 2009-09-15 12:54:49 UTC