https://bugzilla.novell.com/show_bug.cgi?id=481569 Mark Gray changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |markgray+to-suse@puck.nac.n | |et AssignedTo|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com Severity|Major |Enhancement -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=481569 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|xorg-maintainer-bugs@forge. |libv@skynet.be |provo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=481569 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=481569#c2 --- Comment #2 from Mark Gray 2009-03-04 03:06:40 MST --- (In reply to comment #1)

Ummm... are you really, 100%, sure that fixing a crash in X server (one that prevents standardized automatic configuration) is just an *enhancement*?

It is a feature which has been broken for some time due to "bit-rot" and nobody has missed it. It is doubtful that it ever actually worked very well since DDC is only recently starting to work, and does not work on quite a lot of hardware even today. It duplicates functionality which SaX2 will always perform much better. Apart from a brief mention on the Xfree86 4.01 wiki it is undocumented ("X -help" does not list it as an option, nor does "man xserver"). While i overstepped my brief as a screener by opining that it was an ENHANCEMENT, not a major bug hampering the release of 11.2, I have to ask: Once you removed the via driver, did "X -configure" actually produce a particularly usable xorg.conf? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=481569 User libv@skynet.be added comment https://bugzilla.novell.com/show_bug.cgi?id=481569#c4 --- Comment #4 from Luc Verhaegen 2009-03-04 04:03:50 MST --- As the person who has been working on the via driver and on modesetting for more than 5years, and who has come up with quite a few of the advances in modesetting in this millenium, i can only say the following: F -configure and F sax. I'll give it a quick try on my hw, but i won't be changing my view that -configure needs to die: 3c0b77c8 (Luc Verhaegen 2005-12-14 11:37:04 +0000 957) if (flags & PROBE_DETECT) { 3c0b77c8 (Luc Verhaegen 2005-12-14 11:37:04 +0000 958) xf86DrvMsg(pScrn->scrnIndex, X_ERROR, "libv doesn't believe in " 3c0b77c8 (Luc Verhaegen 2005-12-14 11:37:04 +0000 959) "PROBE_DETECT calling PreInit.\n"); 60f73e46 (Luc Verhaegen 2004-03-01 11:36:09 +0000 960) return FALSE; 3c0b77c8 (Luc Verhaegen 2005-12-14 11:37:04 +0000 961) } We were trying to get rid of sax for ages, but were too busy changing the world with the radeonhd driver. Now, given novells new tactic, guess what we will be left with for much, much, much longer? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=481569 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481569#c7 --- Comment #7 from Stefan Dirsch 2009-03-04 09:52:26 MST --- (In reply to comment #3)

1) Changing the graphics card in the computer to a type that needs another driver. In this case, X will not start on boot, and you can either manually rewrite the SaX-generated xorg.conf (which is quite complex and difficult to read), or use the autoconfiguration to give you a start.

Or boot into failsafe for a fbdev/vesa driver base X configuration. On top of it run YaST/SaX to reconfigure your new graphics hardware.

2) When the SaX setup during the installation fails. This is almost 100% if you have more than one monitor (quite common in laptops connected to an external monitor) or more than one gfx card (increasingly common in laptops with dual powersave/performance hardware) and also with some new gfx cards; I had a laptop where SaX left the user with a black screen.

SaX2 has been improved to always only create a configuration for the primary graphics card.

I am sorry to say that, according to my experience, the reverse is true; SaX fails in many cases (see above) and the xorg.conf file produced by SaX is quite oldschool (it contains lots of stuff that gets completely ignored and only makes the conf file difficult to read) :-(

SaX2 is doing to much. This is correct. See also Bug #441404, Bug #440973, that we're aware of this. But as you might know the X team has been downsized as well. :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=481569 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481569#c9 --- Comment #9 from Stefan Dirsch 2009-03-04 10:08:01 MST --- (In reply to comment #8)

The unichrome driver is already in its seperate package. What I could do is removing the requires to xorg-x11-driver-video-unichrome from xorg-x11-driver-video and add Supplements for

0x1106#0x3122#VT3122: CLE266 0x1106#0x7205#VT7205: KM400, KM400A, KN400, P4M800 0x1106#0x3108#VT3108: K8M800, K8N800, K8N800A

to xorg-x11-driver-video-unichrome, so YaST autoselects it for installation if the appropriate hardware has been detected.

done for Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.