Bug 3904

Summary: Problems with Xinerama: Trident 975Im�ge (PCI) and SiS520 (AGP)
Product: xorg Reporter: Piter PUNK <piterpk>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high    
Version: 6.8.1   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Piter PUNK 2005-07-29 02:38:08 UTC
Hi,

I am running X11R6-6.8.1 in a 598MLR motherboard, with on-board AGP video
(SiS520), i put one Trident 975Imàge in PCI slot and try to use Xinerama.
But a few things happens:

1. In first time, all got ok, only a little flickering in screen.
2. If i Ctrl+Alt+BS, and start X again, the SiS video works OK, but the
   Trident video looses the correct frequency and i lose the image (sometimes
   the screen goes to 800x600 instead 1280x1024).
3. If i Crtl+Alt+BS again, and start X again, both screens loose their video.
   Ctrl+Alt+BS don't works (ok, it works, but i don't got console back!).

This things all happens in 16bit mode. In 24bit mode, the Trident screen
got very confused and flickering. I try many times, only one time i got an
real "error" message talking about vm86 error on trident module.

If i put the primarly display on PCI and second on AGP, the system goes to
3. in the first time. If i disable vesa framebuffer, the things are more
stable but the 1. flickering continues.
Comment 1 Erik Andren 2006-05-31 01:24:11 UTC
Any improvements using the 7.1 xorg release?
Comment 2 Timo Jyrinki 2007-02-22 14:27:29 UTC
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status.

Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.