Pagina 1 di 2 1 2 ultimoultimo
Visualizzazione dei risultati da 1 a 10 su 12
  1. #1
    Utente di HTML.it L'avatar di chaosd
    Registrato dal
    Mar 2004
    Messaggi
    1,282

    :cry: il modulo DRI per la Ati radeon 7500 non va

    non mi va il 3D quindi ho cercato i drivers adatti, tipo con le geforce
    li avrei trovati in dri.sourceforge.net, sito in cui consigliano di usare propio quelli scaricabili da lì per attivare il 3D su scheda più vecchie della radeon 8500

    dopo averli scaricati ho lanciato l'install.sh che mi ha caompilato il nuovo modulo radeon (infatti anche la dimensione dello stesso è aumentata di 100K), ma X non parte più

    non so, l'install mi dice che mi ha rimosso il vecchio modulo e installato quello nuovo con lo stesso nome

    non è che dovrei modificare qlc nel file xorg.conf? non so, decommentare qualche voce strana... alla fine infatti c'è la sezione "DRI" ma non so come usarla, dato che nel man non viene citata

    qualcuno sa aiutarmi?
    <Girls are like Internet Domains: the ones you like are already taken, but you can still get one from a strange country!>

    Computers are like conditioned air: they stop work properly when you open windows

    Livin' on: Kubuntu + 2.6.24.2

  2. #2

    Re: :cry: il modulo DRI per la Ati radeon 7500 non va

    Originariamente inviato da chaosd
    non mi va il 3D quindi ho cercato i drivers adatti, tipo con le geforce
    Ma non e` che per le schede basate su radeon <= 9200 il driver 3D e` direttamente incluso in XFree86/X.org?
    (vedi man 4 radeon)

    dopo averli scaricati ho lanciato l'install.sh che mi ha caompilato il nuovo modulo radeon (infatti anche la dimensione dello stesso è aumentata di 100K), ma X non parte più
    errore?

    non è che dovrei modificare qlc nel file xorg.conf? non so, decommentare qualche voce strana... alla fine infatti c'è la sezione "DRI" ma non so come usarla, dato che nel man non viene citata
    Beh, posta il tuo xorg.conf e si vede
    "Qualsiasi esperto ha paura di combattere usando la katana vera. Anch'io. Ma non ignoro la mia paura, riesco ad accettarla, e a metterla da parte accanto a me".

  3. #3
    Utente di HTML.it L'avatar di Ilmalcom
    Registrato dal
    Oct 2002
    Messaggi
    1,345
    Tra le risorse del forum c'è un mio tutorial sulle ATI dove spiego per filo e per segno come far funzionare una 7500... Ti conviene leggere tutto il thread e riprovare

  4. #4
    Utente di HTML.it L'avatar di chaosd
    Registrato dal
    Mar 2004
    Messaggi
    1,282
    l'errore è che non carica il modulo "radeon"

    questo è il mio xorg.conf:

    codice:
    # File generated by xf86config.
    
    
    
    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 Type1 and FreeType 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
    
    
    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/X11R6/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)
    # 
    # If you don't have a floating point coprocessor and emacs, Mosaic or other
    # programs take long to start up, try moving the Type1 and Speedo directory
    # to the end of this list (or comment them out).
    # 
    
        FontPath   "/usr/X11R6/lib/X11/fonts/local/"
        FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
        FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
        FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
        FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
        FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
        FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
        FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"
        FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
        FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    
    # 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
    
    
    Section "InputDevice"
    
        Identifier	"Keyboard1"
        Driver	"Keyboard"
    
    # 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"    "pc102"
    # 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 X.Org
    #    Option "XkbRules"    "__XKBDEFRULES__"
    #    Option "XkbModel"    "pc101"
    #    Option "XkbLayout"   "us"
    #    Option "XkbVariant"  ""
    #    Option "XkbOptions"  ""
    
    #    Option "XkbDisable"
    
        Option "XkbRules"	"xorg"
        Option "XkbModel"	"pc105"
        Option "XkbLayout"	"it"
    
    EndSection
    
    
    # **********************************************************************
    # Core Pointer's InputDevice section
    # **********************************************************************
    
    Section "InputDevice"
    
    # Identifier and driver
    
        Identifier	"Mouse1"
        Driver	"mouse"
        Option "Protocol"    "IMPS/2"
        Option "Device"      "/dev/psaux"
        Option "ZAxisMapping" "4 5"
    
    # 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
    
    
    
    # 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  "adi"
    
    # 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 - 64.3
    
    #    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
    
    # 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 xf86config:
    
    Section "Device"
        Identifier  "ati"
        Driver      "radeon"
        #VideoRam    65536
        # Insert Clocks lines here if appropriate
    EndSection
    
    
    
    # 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      "ati"
        Monitor     "adi"
        DefaultDepth 24
    
        Subsection "Display"
            Depth       8
            Modes       "1024x768" "800x600" "640x480"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth       16
            Modes       "1024x768" "800x600" "640x480"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth       24
            Modes       "1024x768" "800x600" "640x480"
            ViewPort    0 0
        EndSubsection
    EndSection
    
    # 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
    <Girls are like Internet Domains: the ones you like are already taken, but you can still get one from a strange country!>

    Computers are like conditioned air: they stop work properly when you open windows

    Livin' on: Kubuntu + 2.6.24.2

  5. #5
    Utente di HTML.it L'avatar di chaosd
    Registrato dal
    Mar 2004
    Messaggi
    1,282
    Originariamente inviato da Ilmalcom
    Tra le risorse del forum c'è un mio tutorial sulle ATI dove spiego per filo e per segno come far funzionare una 7500... Ti conviene leggere tutto il thread e riprovare
    grazie! corro!
    <Girls are like Internet Domains: the ones you like are already taken, but you can still get one from a strange country!>

    Computers are like conditioned air: they stop work properly when you open windows

    Livin' on: Kubuntu + 2.6.24.2

  6. #6
    Utente di HTML.it L'avatar di chaosd
    Registrato dal
    Mar 2004
    Messaggi
    1,282
    Originariamente inviato da Ilmalcom
    Tra le risorse del forum c'è un mio tutorial sulle ATI dove spiego per filo e per segno come far funzionare una 7500... Ti conviene leggere tutto il thread e riprovare

    ehm... non lo trovo!
    puoi linkare per favore?
    <Girls are like Internet Domains: the ones you like are already taken, but you can still get one from a strange country!>

    Computers are like conditioned air: they stop work properly when you open windows

    Livin' on: Kubuntu + 2.6.24.2

  7. #7
    Originariamente inviato da chaosd
    ehm... non lo trovo!
    puoi linkare per favore?
    http://forum.html.it/forum/showthrea...hreadid=427653
    (acclerazione 3d mediante DRI)
    "Qualsiasi esperto ha paura di combattere usando la katana vera. Anch'io. Ma non ignoro la mia paura, riesco ad accettarla, e a metterla da parte accanto a me".

  8. #8
    Utente bannato
    Registrato dal
    Mar 2001
    Messaggi
    1,144

    Re: :cry: il modulo DRI per la Ati radeon 7500 non va

    ops

    doppio

  9. #9
    Utente bannato
    Registrato dal
    Mar 2001
    Messaggi
    1,144

    Re: :cry: il modulo DRI per la Ati radeon 7500 non va

    Originariamente inviato da chaosd
    ...

    ma perchè vai a scaricare i driver dal sito del dri? il modulo del kernel e i driver di xorg funzionano e sono recenti, lo sviluppo viene fatto nella loro CVS

  10. #10
    Utente di HTML.it L'avatar di chaosd
    Registrato dal
    Mar 2004
    Messaggi
    1,282

    Re: Re: :cry: il modulo DRI per la Ati radeon 7500 non va

    Originariamente inviato da GhePeU
    ma perchè vai a scaricare i driver dal sito del dri? il modulo del kernel e i driver di xorg funzionano e sono recenti, lo sviluppo viene fatto nella loro CVS

    semplicemente perchè va tutto benissimo A PARTE il 3D!!

    se mi dici come attivarlo con i moduli già presenti ti faccio una statua di bronzo!
    <Girls are like Internet Domains: the ones you like are already taken, but you can still get one from a strange country!>

    Computers are like conditioned air: they stop work properly when you open windows

    Livin' on: Kubuntu + 2.6.24.2

Permessi di invio

  • Non puoi inserire discussioni
  • Non puoi inserire repliche
  • Non puoi inserire allegati
  • Non puoi modificare i tuoi messaggi
  •  
Powered by vBulletin® Version 4.2.1
Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.