Bug 8901 - vesa no longer works with S3 Trio's
Summary: vesa no longer works with S3 Trio's
Status: RESOLVED DUPLICATE of bug 7112
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Vesa (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL: http://bugs.gentoo.org/show_bug.cgi?i...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-05 12:44 UTC by VinnieNZ
Modified: 2007-03-11 18:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description VinnieNZ 2006-11-05 12:44:58 UTC
I've been asked to post this bug here with reference to the site above.

Copy and paste of non-gentoo specific info from above link:



Using any version of xf86-video-vesa greater than 1.0.1.3 results in not being
able to startx on a S3 Trio card.  Using v1.0.1.3 works fine.

Result:
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.15-gentoo-r7 i686
Current Operating System: Linux hope-st 2.6.15-gentoo-r7 #1 SMP Wed Mar 29
12:01:30 NZST 2006 i686
Build Date: 27 October 2006
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 27 21:51:38 2006
(==) Using config file: "/etc/X11/xorg.conf"


Fri Oct 27 21:51:38 2006
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5900
 vncext:      created VNC server for screen 0
    xkb_keycodes             { include "xfree86+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+us" };
    xkb_geometry             { include "pc(pc105)" };

Backtrace:
0: X(xf86SigHandler+0x9d) [0x80c718d]

Fatal server error:
Caught signal 11.  Server aborting

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.




lspci:
00:05.0 VGA compatible controller: S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX]
(rev 16)
Comment 1 Evgeny Zubok 2006-11-24 03:01:49 UTC
Try this little patch against /driver/xf86-video-s3/configure.ac. Generate new
configure script with autogen.sh and recompile driver. After that you will be
able to replace "vesa" to "s3" and get full 2d acceleration for your
trio64V2/DX/GX. This patch works well for me now on this card.

https://bugs.freedesktop.org/show_bug.cgi?id=7112#c7

xorg.conf sample:

Section "Device"
    Identifier  "s3_trio64v2"
#    Driver "vesa"
    Driver      "s3" 
#    Option     "noaccel"
    Option      "DPMS"
EndSection

Section "Screen"
    Identifier  "Screen 1"
    Device      "s3_trio64v2"
    Monitor     "your_monitor_id"
    DefaultDepth 16

    Subsection "Display"
        Depth       8
        Modes       "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

Note that I could get only 800x600 @ 85Hz only with 16bpp depth. See the bug
https://bugs.freedesktop.org/show_bug.cgi?id=5527.
Comment 2 Daniel Stone 2007-02-27 01:34:25 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 Adam Jackson 2007-03-11 18:53:12 UTC

*** This bug has been marked as a duplicate of bug 7112 ***


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.