Summary: | S3 VT8375 [ProSavage8 KM266/KL266] - Screen Corrupted with FC3 | ||
---|---|---|---|
Product: | xorg | Reporter: | Rob Rosenthal <robrose7> |
Component: | Driver/savage | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | critical | ||
Priority: | high | CC: | bugzi11.fdo.tormod |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Rob Rosenthal
2005-03-26 13:28:29 UTC
correctness problems aren't blockers. it's unclear what version of Xorg you are using. it would be helpful if you could confirm that the problem still occurs with CVS or a 6.8.99 snapshot. reporter: need more information on you before we can resolve this bug. suspect this was a symptom of gcc miscompiling libvgahw on some fedora versions. Similar problem here. Linux kernel 2.6.15, GCC 3.3.4, Glibc 2.3.4 KM2M motherboard (Athlon XP) ProSavage8 card. In Xorg 6.8.2, most resolutions work OK. However, 1024x768 @ 44.9 has a 4-pixel missing column at the right edge (the problem seems to be corrected with "UseBIOS" "True", but not supported well by my old monitor). In 6.9.0, 1024x768 @ 44.9 the screen appears totally scrambled (independently of any modules I load). Other modes seem to work ok, but are unsupported by old monitors. Whats the status using a current version of xorg (7.1)? I have about same problem running gentoo's latest xorg-7 and 7.1 and latest savage drivers from gentoo portage. see: http://bugs.gentoo.org/show_bug.cgi?id=147234 Is this still a problem? The gentoo bug was closed as WORKSFORME. We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. |
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.