I have a xinerama setup with an ati r128 and a s3: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF 02:08.0 VGA compatible controller: S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] (rev 16) Yesterday I update to xorg-server 1.3, up to that moment every configuration file works perfectly, now if I start the X system without xinerama (only with the r128) all it's perfect, but If I start with the xinerama setup the X system spend 2 o 3 minutes and don't show anything in the screen. When I look the logs I see that the X system hangs in the s3 part but they don't do any errors. I can't see the cursor and the system don't respond to a ctr+alt+sup or ctr+alt+ret. I recompiled xf86-video-ati xf86-video-s3 xf86-input-keyboard xf86-input-mouse and I have the same behaviour. No I went back to xorg-server-1.2.0-r3 and it's working. Reproducible: Always Steps to Reproduce: 1. update to xorg-server 1.3 2. try to startx with a s3 videocard 3. system hangs and don't respond to anything Expected Results: work with a s3 videocard
Created attachment 117738 [details] Xorg log when hangs
Created attachment 117739 [details] emerge --info
Created attachment 117741 [details] xorg.conf with the xinerama config I use a symbolic link to change between xorg-config. Here is the xorg-config with the xinerama option enable.
Donnie, it was my understanding that Xinerama was only broken for the Intel driver. Is it actually broken for everything in 1.3?
(In reply to comment #4) > Donnie, it was my understanding that Xinerama was only broken for the Intel > driver. Is it actually broken for everything in 1.3? Shouldn't be. I haven't tested lately. I didn't even realize it was broken on intel.
Err no, the problem does not in the xinerama setup. If I try to start ONLY with the s3 card I get the same behaviour.
(In reply to comment #6) > Err no, the problem does not in the xinerama setup. If I try to start ONLY with > the s3 card I get the same behaviour. Perhaps next time, you don't even need to mention Xinerama if it's irrelevant to the problem. It's a little confusing, as you can see. =)
*** This bug has been marked as a duplicate of bug 176938 ***