Ahojte chcem si zahrat quake 3.Mam slackware.A chcem spojazdnit 3D ovladace.Nie fglrx.Pod Ubuntu som mal open source ovladace ATI.Vsetko islo.Ale neviem ako pod slackware 11.0.S tejto stranky https://help.ubuntu.com/community/RadeonDriver
.Vypis lspic
# lspci
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
02:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
02:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary)
root
Slack a ati.
Pre pridávanie komentárov sa musíte prihlásiť.
# 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 "freetype"
#Load "speedo"
# This loads the GLX module
Load "glx"
EndSection
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 50.0 - 80.0
# 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 40-75
EndSection
Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection
Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"
# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32
# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubsection
EndSection
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
root:~# glxinfo |grep vendor
server glx vendor string: SGI
client glx vendor string: SGI
OpenGL vendor string: Mesa project: www.mesa3d.org
root@:~#
root:~# glxinfo | grep "direct rendering"
direct rendering: No
root:~#
sudo apt-get remove xorg-driver-fglrx; sudo apt-get install libgl1-mesa-glx libgl1-mesa-dri
Pridat do xorgu:
Driver "ati"
Section "DRI"
Mode 0666
EndSection
A uz to slo.V slackware som nenasiel balicky glx a dri..Neviem ci pouzit xorgconfig.Alebo nieco take.
mimochodom, riesil si to pre debian alebo slack?
load dri
Load glx
A premenujem driver na "ati"
Prihodim aby to mohol spustat ja.Nejde. :(....
# DRI devices
KERNEL=="card*", NAME="dri/card%n", GROUP="video"
KERNEL=="nvidia*", NAME="%k", GROUP="video"
KERNEL=="3dfx*", NAME="%k", GROUP="video"
..Napadlo ma ci mam prava..Ako vystupujem stale pod rootom.
Meno je foxii
heslo je pheonix
No nic :(
ked mas nahodeny system tak aby mal nakopnut aj 3d akceleraciu tak pri jej zlychani aspon vypise "vypinam tu 3d akceleraciu pretoze...". Neviem ci ocakavas nejake okienko co sa ma nakreslit aj s vykricnikom na obrazovku, ale logy su v /var/log.
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 6.9.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.2
(II) LoadModule: "dri"
(II) Loading /usr/X11R6/lib/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 6.9.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.2
Aj "ati"
(II) LoadModule: "ati"
(II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
compiled for 6.9.0, module version = 6.5.7
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.8
Toto ma zaujalo (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled ..Ja som zapojeny na DVI teda secondary monitor
Tu je ten log cely ftp.foxii.ic.cz/Xorg.0.log
Meno:foxii
Heslo pheonix
mozem z toho logu vybrat to podstatne o chybe a dat to sem aby bolo toto vlakno napomocne aj pre ostatnych ? alebo zarucis ze dany subor bude dostupny aj o rok, dva alebo viac na danej adrese a aj s tymi autorizacnymi udajmi.
mimochodom, ani by som sa nedivil keby to heslo uz bolo zmenene.
takze sem daj chyby z logu xorg (xorg.N.log) ktore maju na riadku EE, typnem si ze ak sa ti este niekto nedostal na to konto, tak ten log za chvilu zmazes a cele vlakno bude mat nulovy prinos.
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
(EE) Failed to load module "speedo" (module does not exist, 0)
(EE) Failed to load module "xtt" (module does not exist, 0)
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
a teraz nam povedz ako si to instaloval ze tie ovladace nespolupracuju z tvojou distribuciou ... ovladace su inej verzie ako zwindows, preto to nejde.
odstranil som vsetko fglrx..
dal som load dri
load glx
..Potom som zmenil ovladac s vesa na radeon.
A to je tak vsetko
bud si kompletne neodinstaloval flrgx alebo si nainstaloval nieco z inej distribucie a to vyzera byt jadrom problemu ...
takze cesty su teda tri:
1) spustit spominanu konttrolu konzistencie systemu pomocou balickovacieho nastroja - ak to slack umoznuje
2) spustit kontrolu konzistencie systemu k bodu pred instalaciou - ak pouzivas doplnkovy nastroj ktory to za teba riesi hoci aj sudo find / -type f -exec md5sum {} \; | tee ~/kontrola.md5 # a spetne overenie cez md5sum -c ~/kontrola.md5
3) reinstalovat zodpovedajuce baliky
k jednotke sa nevyjadrujem, slack nie je moja srdcova zalezitost. dvojka vyzaduje spustit checksum na system pred instalaciou hovadin ktore ignoruju balickovaci system a trojka je najschodnejsie riesenie, zial nakolko nevies ake to boli baliky a zistit je to dost tazke, tak asi cely stroj ...