Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
HOW-TO: ProSavage, SuperSavage DDR and dri-drm 3d drivers
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
Dan Forever
Tux's lil' helper
Tux's lil' helper


Joined: 13 Jun 2005
Posts: 79
Location: London, England

PostPosted: Wed Jan 18, 2006 1:20 pm    Post subject: Reply with quote

williamvergara, are you talking about using this ebuild? https://forums.gentoo.org/viewtopic-t-396898-start-0.html
I thought dmvianna meant the first post of this topic?
Back to top
View user's profile Send private message
williamvergara
n00b
n00b


Joined: 15 Sep 2004
Posts: 47
Location: Germany

PostPosted: Wed Jan 18, 2006 3:36 pm    Post subject: Reply with quote

yes, im talkin about that post. That worked great for me.
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1599
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Wed Jan 18, 2006 4:17 pm    Post subject: xorg-7 + savage = opengl apps killed/segfault Reply with quote

Has anyone been successful with opengl apps working with the savage drivers from an xorg-7 emerge?

The drivers work great for accelerated 2d but as soon as an opengl app runs it dies with a "killed" message. glx is getting loaded, it just anything that uses it not working it seems like. This has happened with glxgears and some other opengl app I tested. Just curious if anyone has a solution or knows what is causing it since the strace here didn't reveal anything very usefull.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
BonesToo
Apprentice
Apprentice


Joined: 19 Aug 2003
Posts: 153

PostPosted: Thu Jan 19, 2006 2:43 am    Post subject: Reply with quote

Sorry for late response Dan Forever. If you want to update to xorg 6.9 following that post, it will probably all just work. I'm still running xorg 6.8 with x11-drm for that, which does require the patch for 2.6.13+ kernels. If you choose to do it that way, then I'll post my overlay ebuild for x11-drm.
Back to top
View user's profile Send private message
Dan Forever
Tux's lil' helper
Tux's lil' helper


Joined: 13 Jun 2005
Posts: 79
Location: London, England

PostPosted: Thu Jan 19, 2006 11:25 pm    Post subject: Reply with quote

I'm actually considering xorg 7.0 after reading http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml since 7.0 and 6.9 are the same, essentially, to the end user...
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Sun Jan 22, 2006 7:55 pm    Post subject: Reply with quote

:?: Why would I have a stable system if I could ruin it by testing some new obscure capability? :roll:

OK, there it goes: have someone succeeded in making module savage work with a suspend2-sources kernel? I've just ruined my direct rendering *again*. Basically, after compiling the new kernel, I've lost the savage module, and neither the newest binary snapshot nor recompiling xorg 6.9 gets it working again. Damn. That's what I get:

Code:
# modprobe savage
FATAL: Error inserting savage (/lib/modules/2.6.14-suspend2-r7/kernel/drivers/char/drm/savage.ko): Unknown symbol in module, or unknown parameter (see dmesg)
# dmesg
savage: Unknown symbol drm_addmap

_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
Dan Forever
Tux's lil' helper
Tux's lil' helper


Joined: 13 Jun 2005
Posts: 79
Location: London, England

PostPosted: Wed Jan 25, 2006 2:56 pm    Post subject: Reply with quote

it's all fun :twisted:

I can't seem to get my savage module at all.
I've got x11-drivers/xf86-video-savage 'merged.

Code:
FATAL: Module savage not found.
[drm] failed to load kernel module "savage"
(EE) SAVAGE(0): [drm] DRIScreenInit failed. Disabling DRI.
(EE) SAVAGE(0): DRI isn't enabled

appears to be the useful stuff from the spew in the console.
Briefly going over /var/log/Xorg.0.log it appears to be working until...
Code:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)


looking at the directory /dev/dri it appears to be empty...

Dan
Back to top
View user's profile Send private message
Dan Forever
Tux's lil' helper
Tux's lil' helper


Joined: 13 Jun 2005
Posts: 79
Location: London, England

PostPosted: Fri Jan 27, 2006 12:00 am    Post subject: Reply with quote

OK, update, I fixed that problem by adding in the savage drivers as a module in the [2.6.15-r1] kernel->character devices. graphics devices has nothing in there. I now have a slightly different problem:

Code:
(EE) SAVAGE(0): [agp] AGP not available
:/

agpgart is loaded as a module
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Thu Feb 23, 2006 12:46 pm    Post subject: Reply with quote

I've just started a thread for savagers who are testing the new modular xorg-7.0: https://forums.gentoo.org/viewtopic-t-436831-highlight-.html. See you there! 8)

[edit] By the way, now I have DRI enabled in the modular xorg. Just read the topic quoted above. :D
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Fri Feb 24, 2006 12:00 pm    Post subject: xorg-7 + savage = opengl apps killed/segfault Reply with quote

firephoto: did you have any luck with glxgears? I'm getting the same here. I'm running xorg-7.0-r1 too.

[edit] I wasn't using the new dri drivers that come with the 2.6.15 kernel. Using those everything works like a charm. :D
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1599
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Fri Feb 24, 2006 5:21 pm    Post subject: Reply with quote

I think I got it partially working, I know my results have changed since I last posted in this one (now that I read what I posted) but I'm pretty sure the last thing I tested resulted in the "X crashes" problem.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
RuFI0
n00b
n00b


Joined: 16 Sep 2004
Posts: 30
Location: Malaysia

PostPosted: Thu Apr 06, 2006 4:53 am    Post subject: Reply with quote

I've been at this for more than a month now and i still can't get DRI working. Here's my info:

lspci:
Code:

01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]


glxinfo:
Code:

name of display: :0.0
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
    GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,
    GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control,
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
    GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method,
    GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture,
    GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow,
    GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
    GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra,
    GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_logic_op,
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
    GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
    GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_point_parameters,
    GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color,
    GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
    GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture,
    GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
    GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object,
    GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
    GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
    GL_ATIX_texture_env_combine3, GL_IBM_texture_mirrored_repeat,
    GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
    GL_NV_blend_square, GL_NV_point_sprite, GL_NV_texgen_reflection,
    GL_NV_texture_rectangle, GL_SGIS_generate_mipmap,
    GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
    GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow,
    GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  0  0  0  0  0  0 0 None
0x24 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16  0  0 0 None
0x25 24 tc  0 32  0 r  y  .  8  8  8  8  0 16  8 16 16 16 16  0 0 None
0x26 24 tc  0 32  0 r  .  .  8  8  8  8  0 16  8 16 16 16 16  0 0 None
0x27 24 dc  0 24  0 r  y  .  8  8  8  0  0 16  0  0  0  0  0  0 0 None
0x28 24 dc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16  0  0 0 None
0x29 24 dc  0 32  0 r  y  .  8  8  8  8  0 16  8 16 16 16 16  0 0 None
0x2a 24 dc  0 32  0 r  .  .  8  8  8  8  0 16  8 16 16 16 16  0 0 None


/etc/X11/xorg.conf
Code:

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath     "/usr/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/local/"
#    FontPath   "/usr/share/fonts/Speedo/"
#    FontPath   "/usr/share/fonts/TrueType/"
#    FontPath   "/usr/share/fonts/freefont/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier  "Keyboard1"
    Driver      "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option     "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg

#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"


    Option "XkbModel"   "pc101"
    Option "XkbLayout"  "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "Auto"
    Option "Device"      "/dev/psaux"

# Mouse-speed setting for PS/2 mouse.
#    Option "Resolution"        "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"  "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"  "9600"
#    Option "SampleRate"        "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 48.5

#    HorizSync  30-64         # multisync
#    HorizSync  31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier  "Standard VGA"
    VendorName  "Unknown"
    BoardName   "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam   256

#    Clocks     25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "savage"
    Driver      "savage"
    #Option     "ForceInit"     "yes"
    #Option     "ShadowStatus"  "true"
    #VideoRam    32768
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "savage"
    Monitor     "My Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Section "DRI"
   Mode 0666
EndSection


lsmod:
Code:

via_agp                 8256  1
savage                 33984  0
drm                    66004  1 savage
agpgart                29904  2 via_agp,drm


I'm using xorg-x11-6.8.2-r6. The driver seens to load ok but i still can get DRI working. Any ideas?
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Thu Apr 06, 2006 10:19 am    Post subject: Reply with quote

RuFIO:

1) First, prepare to work on the console if xorg does not load. :wink:

2) Comment out all that:

Code:
Section "Device"
    Identifier  "Standard VGA"
    VendorName  "Unknown"
    BoardName   "Unknown"

    Driver     "vga"

EndSection


3) Cross you fingers and restart xorg. :)

4) If it does start normally, your savage driver is working OK. Great! :D You can forget standard VGA for the centuries of the centuries now.

5) Try that configuration for the savage driver:

Code:
Section "Device"
   Identifier  "Videocard0"
   Driver      "savage"
#   Driver      "vesa"
#   Driver   "vga"
   Option "SWCursor" "True"
   Option "ShadowStatus" "off"
   Option "UseBIOS" "True"
   Option "AGPSize" "16"
   Option "AGPMode" "4"
   Option "DmaMode" "Vertex"
   Option "DmaType" "AGP"
   Option "BusType" "AGP"
EndSection


If anything goes wrong, you can always switch back to VGA or VESA (better than VGA) by quoting out "savage" and unquoting the desired one.

6) No dice? Read the savage man page, change your device settings accordingly. You might have to test different ones until everything works at its best.

Code:
$ man savage


7) Be sure you're reading this as well; it is very informative:

Code:
# ls -l /var/log/Xorg.*.log

(choose the more recent one, of course)
Code:
# cat /var/log/Xorg.<?>.log | grep SAVAGE
# cat /var/log/Xorg.<?>.log | grep direct
# cat /var/log/Xorg.<?>.log | grep dri
# cat /var/log/Xorg.<?>.log | grep drm


and good luck! 8)
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
RuFI0
n00b
n00b


Joined: 16 Sep 2004
Posts: 30
Location: Malaysia

PostPosted: Thu Apr 06, 2006 12:27 pm    Post subject: Reply with quote

Thanks for the reply dmvianna.
Well, i've commented the lines you suggested and X loads just fine so i'm sure that the savage driver is working. However, i still can't get DRI.

cat /var/log/Xorg.0.log | grep SAVAGE
Code:

(II) SAVAGE: driver (version 1.1.27) for S3 Savage chipsets: Savage4,
(**) SAVAGE(0): Depth 24, (--) framebuffer bpp 32
(==) SAVAGE(0): RGB weight 888
(==) SAVAGE(0): Default visual is TrueColor
(II) SAVAGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(**) SAVAGE(0): Option "SWCursor" "True"
(**) SAVAGE(0): Option "UseBIOS" "True"
(**) SAVAGE(0): Option "ShadowStatus" "off"
(**) SAVAGE(0): Using SW cursor
(**) SAVAGE(0): Using video BIOS to set modes
(**) SAVAGE(0): Option: ShadowStatus enabled
(II) SAVAGE(0): initializing int10
(II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 31680 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Graphics ProSavage DDR Family BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Garphics Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 3.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 0.0
(--) SAVAGE(0): Chip: id 8d04, "ProSavage DDR-K"
(--) SAVAGE(0): Engine: "ProSavage"
(--) SAVAGE(0): mapping MMIO @ 0xdfe80000 with size 0x80000
(==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
(--) SAVAGE(0): probed videoram:  32768k
(II) SAVAGE(0): VESA VBE DDC supported
(II) SAVAGE(0): VESA VBE DDC Level none
(II) SAVAGE(0): VESA VBE DDC transfer in appr. 0 sec.
(II) SAVAGE(0): VESA VBE DDC read failed
(--) SAVAGE(0): Detected current MCLK value of 14.318 MHz
(II) SAVAGE(0): My Monitor: Using hsync range of 31.50-48.50 kHz
(II) SAVAGE(0): My Monitor: Using vrefresh range of 50.00-90.00 Hz
(II) SAVAGE(0): Clock range:  10.00 to 220.00 MHz
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "400x300" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1152x864" (hsync out of range)
(II) SAVAGE(0): Not using default mode "576x432" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x960" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640x480" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x960" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640x480" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x1024" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x1024" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x1024" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (hsync out of range)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (hsync out of range)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (hsync out of range)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (hsync out of range)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1792x1344" (hsync out of range)
(II) SAVAGE(0): Not using default mode "896x672" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "896x672" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1856x1392" (hsync out of range)
(II) SAVAGE(0): Not using default mode "928x696" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "928x696" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "960x720" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "960x720" (hsync out of range)
(II) SAVAGE(0): Not using default mode "832x624" (hsync out of range)
(II) SAVAGE(0): Not using default mode "416x312" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1400x1050" (hsync out of range)
(II) SAVAGE(0): Not using default mode "700x525" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1400x1050" (hsync out of range)
(II) SAVAGE(0): Not using default mode "700x525" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1024" (hsync out of range)
(II) SAVAGE(0): Not using default mode "800x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "960x720" (hsync out of range)
(II) SAVAGE(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using mode "1280x1024" (no mode of this name)
(II) SAVAGE(0): Not using default mode "1152x768" (width too large for virtual size)
(--) SAVAGE(0): Found 13 modes at this depth:
(--) SAVAGE(0): Virtual size is 1024x768 (pitch 1024)
(**) SAVAGE(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) SAVAGE(0): Modeline "1024x768"   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync
(**) SAVAGE(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) SAVAGE(0): Modeline "800x600"   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync
(**) SAVAGE(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
(II) SAVAGE(0): Modeline "640x480"   36.00  640 696 752 832  480 481 484 509 -hsync -vsync
(**) SAVAGE(0):  Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.1 Hz (I)
(II) SAVAGE(0): Modeline "1024x768"   44.90  1024 1032 1208 1264  768 768 776 817 interlace +hsync +vsync
(**) SAVAGE(0):  Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) SAVAGE(0): Modeline "800x600"   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync
(**) SAVAGE(0):  Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) SAVAGE(0): Modeline "800x600"   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync
(**) SAVAGE(0):  Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) SAVAGE(0): Modeline "800x600"   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync
(**) SAVAGE(0):  Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) SAVAGE(0): Modeline "640x480"   31.50  640 656 720 840  480 481 484 500 -hsync -vsync
(**) SAVAGE(0):  Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) SAVAGE(0): Modeline "640x480"   31.50  640 664 704 832  480 489 491 520 -hsync -vsync
(**) SAVAGE(0):  Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) SAVAGE(0): Modeline "640x480"   25.20  640 656 752 800  480 490 492 525 -hsync -vsync
(**) SAVAGE(0):  Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
(II) SAVAGE(0): Modeline "720x400"   35.50  720 756 828 936  400 401 404 446 -hsync +vsync
(**) SAVAGE(0):  Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) SAVAGE(0): Modeline "640x400"   31.50  640 672 736 832  400 401 404 445 -hsync +vsync
(**) SAVAGE(0):  Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) SAVAGE(0): Modeline "640x350"   31.50  640 672 736 832  350 382 385 445 +hsync -vsync
(**) SAVAGE(0):  Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D)
(II) SAVAGE(0): Modeline "576x384"   32.50  576 589 657 736  384 385 388 403 doublescan +hsync +vsync
(**) SAVAGE(0):  Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(II) SAVAGE(0): Modeline "512x384"   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync
(**) SAVAGE(0):  Default mode "512x384": 22.4 MHz, 35.5 kHz, 87.1 Hz (D)
(II) SAVAGE(0): Modeline "512x384"   22.45  512 516 604 632  384 384 388 409 interlace doublescan +hsync +vsync
(**) SAVAGE(0):  Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
(II) SAVAGE(0): Modeline "400x300"   24.75  400 408 448 528  300 300 302 312 doublescan +hsync +vsync
(**) SAVAGE(0):  Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
(II) SAVAGE(0): Modeline "400x300"   25.00  400 428 488 520  300 318 321 333 doublescan +hsync +vsync
(**) SAVAGE(0):  Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(II) SAVAGE(0): Modeline "400x300"   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync
(**) SAVAGE(0):  Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) SAVAGE(0): Modeline "400x300"   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync
(**) SAVAGE(0):  Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D)
(II) SAVAGE(0): Modeline "320x240"   18.00  320 348 376 416  240 240 242 254 doublescan -hsync -vsync
(**) SAVAGE(0):  Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
(II) SAVAGE(0): Modeline "320x240"   15.75  320 328 360 420  240 240 242 250 doublescan -hsync -vsync
(**) SAVAGE(0):  Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
(II) SAVAGE(0): Modeline "320x240"   15.75  320 332 352 416  240 244 245 260 doublescan -hsync -vsync
(**) SAVAGE(0):  Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) SAVAGE(0): Modeline "320x240"   12.60  320 328 376 400  240 245 246 262 doublescan -hsync -vsync
(**) SAVAGE(0):  Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D)
(II) SAVAGE(0): Modeline "360x200"   17.75  360 378 414 468  200 200 202 223 doublescan -hsync +vsync
(**) SAVAGE(0):  Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) SAVAGE(0): Modeline "320x200"   15.75  320 336 368 416  200 200 202 222 doublescan -hsync +vsync
(**) SAVAGE(0):  Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) SAVAGE(0): Modeline "320x175"   15.75  320 336 368 416  175 191 192 222 doublescan +hsync -vsync
(==) SAVAGE(0): DPI set to (75, 75)
(II) SAVAGE(0): initializing int10
(II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 31680 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Graphics ProSavage DDR Family BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Garphics Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 3.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 0.0
(--) SAVAGE(0): mapping framebuffer @ 0xd0000000 with size 0x2000000
(==) SAVAGE(0): Write-combining range (0xd0000000,0x2000000)
(--) SAVAGE(0): Chose mode 118 at 60Hz.
(II) SAVAGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) SAVAGE(0): Using 1279 lines for offscreen memory.
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)
(==) SAVAGE(0): Backing store disabled
(WW) SAVAGE(0): Option "AGPSize" is not used
(WW) SAVAGE(0): Option "AGPMode" is not used
(WW) SAVAGE(0): Option "DmaMode" is not used
(WW) SAVAGE(0): Option "DmaType" is not used
(WW) SAVAGE(0): Option "BusType" is not used


cat /var/log/Xorg.0.log | grep DRI
Code:

(II) Loading extension XFree86-DRI


cat /var/log/Xorg.0.log | grep drm
Code:

(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/modules/linux/libdrm.a
(II) Module drm: vendor="X.Org Foundation"
Back to top
View user's profile Send private message
dmvianna
l33t
l33t


Joined: 22 Mar 2004
Posts: 742
Location: Down Underland

PostPosted: Thu Apr 06, 2006 1:37 pm    Post subject: Reply with quote

How's your kernel set? did you choose
Code:
device drivers -> graphics support -> S3 savage support [X]
device drivers -> character devices -> direct rendering manager -> savage video cards [M]

I suppose the first option is chosen, as you are able to load the driver. As about the second, please check.

From there, I might not be able to help you. Try reading the log files and see when/why dri fails. You might try stuff like
Code:
cat /var/log/Xorg.0.log | grep [EE]
(for errors)
Code:
cat /var/log/Xorg.0.log | grep [WW]
(for warnings)

or plain
Code:
nano -w /var/log/Xorg.0.log
(for freakin' everything)

It might take some time, reading and insight. Setting DRI up is often an adventure. Good luck!
_________________
Proprietary is theft. Pierre-Joseph Proudhon, if he had a chance
Powered by a MacBook Pro
Back to top
View user's profile Send private message
hoyanf
Tux's lil' helper
Tux's lil' helper


Joined: 27 Aug 2005
Posts: 80
Location: Malaysia

PostPosted: Mon Apr 10, 2006 7:21 pm    Post subject: Reply with quote

Maybe this might helped some you... from my post on another thread https://forums.gentoo.org/viewtopic-t-436831-highlight-.html

Quote:

my glxinfo :-
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2

my glxgears:-
1035 frames in 5.0 seconds = 206.990 FPS
1020 frames in 5.0 seconds = 203.927 FPS
1019 frames in 5.0 seconds = 203.534 FPS
1018 frames in 5.0 seconds = 203.449 FPS
1016 frames in 5.0 seconds = 203.020 FPS

my xorg.conf :-
Option "BusType" "AGP"
Option "HWCursor" "True"
# Option "NoAccel" "False"
# Option "LCDClock" "14.318mhz"
Option "UseBIOS" "False"
Option "AGPMode" "4"
Option "AGPSize" "16"
Option "DmaMode" "Any"
Option "DmaType" "AGP"

Identifier "Card0"
Driver "savage"
VendorName "S3 Inc."
BoardName "VT8375 [ProSavage8 KM266/KL266]"
BusID "PCI:1:0:0"

Laptop : -
Twinhead efio! 125A
Athlon-M 1400+
512MB DDR


btw am using modular X..
_________________
WorkPC -> Xeon x3440 | Gigabyte P55-UD6 | 16GB DDR3 | HDD1 - 600GB | HDD2 - 500 GB | HDD3 - 1TB
HomePC -> Xeon x3320 | Gigabyte GA-EP45-UD3P | 8GB DDR2 | HDD1 - 500GB | HDD2 - 1TB
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Page 10 of 10

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum