| View previous topic :: View next topic |
| Author |
Message |
stustill
Guru
Joined: 25 Feb 2003
Posts: 333
Location: Aberdeen, Scotland
|
 Posted: Tue May 27, 2003 5:42 pm Post subject: |
 |
|
No, I get that too, doesn't effect the running of X. What are your USE flags and CFLAGS?
Stu |
|
| Back to top |
|
 |
ricril
n00b
Joined: 05 Mar 2003
Posts: 26
Location: New York
|
| Posted: Tue May 27, 2003 6:09 pm Post subject: |
|
|
stustill,
USE="apm avi emacs gif gnome gphoto2 cups slp X opengl xv -kde -arts gtk bonobo evo gtkhtml libwww tcltk jpeg png tiff mpeg xmms oggvorbis imap mozilla spell xml2 pdflib java truetype radeon -sis -rage128 -matrox -3dfx -gamma -i8x0"
and
CFLAGS="-march=pentium4 -03 -pipe -fomit-frame-pointer"
and by the way:
MAKEOPTS="-j3"
Yeah, I get myself a nice dual Xeon.... 
_________________
Ricril |
|
| Back to top |
|
|
guy
Apprentice
Joined: 31 Mar 2003
Posts: 286
Location: USA
|
| Posted: Tue May 27, 2003 10:33 pm Post subject: |
|
|
| ricril wrote: | Crowbert,
nothing happend when "xterm -display :0." is typed (it hangs without giving the prompt back).
guy,
here is one line of /var/log/XFree86.0.log:
| Quote: | | (WW) Open APM failed (/dev/apm_bios) (No such a file or directory) |
Is it a possible clue? |
is there any mention of radeon or other drivers being loaded or failing to load?
_________________
www.manatee.servemp3.com
www.seas.upenn.edu/~bdodson/gina
www.goatse.cx [it will rise again!] |
|
| Back to top |
|
|
ricril
n00b
Joined: 05 Mar 2003
Posts: 26
Location: New York
|
| Posted: Wed May 28, 2003 11:37 am Post subject: |
|
|
When runnig startx I get a black screen with the mouse pointer in the middle. when Ctrl-Alt-Backspace, it says:
Symbol drmGetClient from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved!
When I uncomment the following:
Load "glx"
Load "dri"
Section "DRI"
Mode 0666
EndSection
It doesn't make a difference (black screen with the mouse pointer in the middle), but it doesn't give me the error message anymore (Symbol drmGetClient from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! is not displayed anymore when X is killed
Again, radeon_drv.o IS present in /usr/X11R6/lib/modules/drivers/
I really don't know what to do anymore.... 
_________________
Ricril |
|
| Back to top |
|
|
crowbert
Tux's lil' helper
Joined: 28 Apr 2003
Posts: 140
|
| Posted: Wed May 28, 2003 2:29 pm Post subject: |
|
|
| If you're getting a working mouse pointer, then it's probably working. When you ran "xterm -display :0" from the console, you said it didn't die--did you check to see if it showed up on the X display? |
|
| Back to top |
|
|
ricril
n00b
Joined: 05 Mar 2003
Posts: 26
Location: New York
|
| Posted: Wed May 28, 2003 2:39 pm Post subject: |
|
|
Sorry crowbert, I don't understand what you mean by "showed up on the X display?"
When "xterm -display :0" is typed, nothing happend (but I don't get the prompt back)
_________________
Ricril |
|
| Back to top |
|
|
crowbert
Tux's lil' helper
Joined: 28 Apr 2003
Posts: 140
|
| Posted: Wed May 28, 2003 2:41 pm Post subject: |
|
|
| Yes, you won't have anything come back, because the xterm is running, but it is on the X display, which in normally virtual terminal 7. Switch back to it (where you have the black screen with the mouse pointer) and see if you have an xterm there now. |
|
| Back to top |
|
|
ricril
n00b
Joined: 05 Mar 2003
Posts: 26
Location: New York
|
| Posted: Wed May 28, 2003 3:47 pm Post subject: |
|
|
Thank youy all, it works!
_________________
Ricril |
|
| Back to top |
|
|
Erinye
n00b
Joined: 29 Apr 2003
Posts: 10
Location: The Netherlands
|
| Posted: Wed May 28, 2003 5:54 pm Post subject: |
|
|
I have the problem that my screen turns black BSOD (Nice of linux not to go blue but for a change going black e.g. different color, same result though less '...fatal'  then the usual winnieXP driver problems)and that i get an error message that i'm having a third party board and thus it's not supported? can't be. Though it's a sticky, it's not giving me an answer still that worked for me. Hoping that the 'guy' approach would work but ofcourse not 
[emerge xfree-drm; emerge ati-drivers; MTRR +;Kernel DRI -]
For a few nights i tried to figure out how i can get this thing working. Are people having good results with the fglrxconfig? ow yeah why can't root see this file and a normal user do? locatedb thingy perhaps?
anyone posting a nice edited XF86Config file that works for a r300?
Thanks in advance
Arnoud |
|
| Back to top |
|
|
spamsk8r
n00b
Joined: 07 Apr 2003
Posts: 27
|
| Posted: Wed May 28, 2003 7:52 pm Post subject: |
|
|
| My problem is that after i emerge ati-drivers with my radeon 9700 pro on my kt400 board it says cannot load agpgart, and refuses to run any 3d applications. I have tried compiling agpgart into the kernel, and I have also tried compiling it as a module, but it gives me an error when i modprobe agpgart, and it wont insmod it. Has anyone else had this problem using the KT400 chipset? |
|
| Back to top |
|
|
crowbert
Tux's lil' helper
Joined: 28 Apr 2003
Posts: 140
|
| Posted: Wed May 28, 2003 8:03 pm Post subject: |
|
|
It's simplest to compile AGPGART into the kernel, unless you're obsessive about modules. Keep in mind, though, that selecting that option by itself does nothing useful. What matters are the options immediately below that that that option enables. You have to select support for your motherboard's chipset. If you're not sure what chipset your motherboard has, select all of them. If your chipset isn't listed, then you're probably completely out of luck, but try selecting all of them just on the off chance that one of them is compatible with yours with respect to AGP.
I think that AGPGART will refuse to load as a module if there is no support for your chipset built with it.
[This is all based on my experiences getting my card to work, following the advice on the first few pages of this thread.] |
|
| Back to top |
|
|
BadGuy
n00b
Joined: 13 May 2003
Posts: 44
|
| Posted: Fri May 30, 2003 10:31 am Post subject: |
|
|
For me everything loads. I can modprobe everything but I'm not getting results from it. It just gives low-fps as the direct rendering just keeps getting disabled.... Frustrating to say the least...
stu:
I figured that out going to emerge them though coz I'd like to use my s-video out support... Also there is a reference to the gatos site in the xfree86 log so it might still get loaded?
edit:
I'm also getting that APM_bios stuff donno why it is and what it does yet my battery indicator won't work eitherway. Doesn't affect the video performance though |
|
| Back to top |
|
|
borker
n00b
Joined: 05 Oct 2002
Posts: 25
Location: Perth, WA
|
| Posted: Fri May 30, 2003 12:21 pm Post subject: |
|
|
spamsk8r, your problem is probably that your kt400 board's 8x agp is not supported. If you can dumb it down to 4x in the bios then do that, otherwise you may want to follow the steps here
That thread talks about patching the agp drivers to work with the kt400.. it's a bit of a pain, but it did work for me. |
|
| Back to top |
|
|
Infra
Tux's lil' helper
Joined: 12 Jul 2002
Posts: 131
Location: Vantaa, Finland
|
| Posted: Sat May 31, 2003 7:16 am Post subject: |
|
|
Hi,
I have same card as Stu and I did everything like he told but when I uncomment the load "glx" and "dri" and type startx X starts to load but then my monitor goes to power safe mode (u know the led starts to blink orange -> green)
I have to press the reboot switch on my comp. And when Gentoo loads it gives an error when trying to load module radeon.
Please help!
_________________
If it works don't mess with it |
|
| Back to top |
|
|
stustill
Guru
Joined: 25 Feb 2003
Posts: 333
Location: Aberdeen, Scotland
|
| Posted: Sat May 31, 2003 2:33 pm Post subject: |
|
|
Badguy:
You had any success with ati-gatos?
Infra:
What error message are you receiving when you modprobe radeon? Can you paste the /var/log/XFree86.0.log so that we can have a look at why x won't start
Stu |
|
| Back to top |
|
|
Infra
Tux's lil' helper
Joined: 12 Jul 2002
Posts: 131
Location: Vantaa, Finland
|
| Posted: Sat May 31, 2003 2:57 pm Post subject: |
|
|
| stustill wrote: |
What error message are you receiving when you modprobe radeon? Can you paste the /var/log/XFree86.0.log so that we can have a look at why x won't start
Stu |
| Code: | root@ascension .fluxbox # modprobe radeon
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: unresolved symbol mtrr_del_Rsmp_272d394e
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: unresolved symbol mtrr_add_Rsmp_56179c5f
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: insmod /lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o failed
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: insmod radeon failed |
I couldn't find any errors from Xfree86.0.log
_________________
If it works don't mess with it |
|
| Back to top |
|
|
stustill
Guru
Joined: 25 Feb 2003
Posts: 333
Location: Aberdeen, Scotland
|
| Posted: Sat May 31, 2003 3:27 pm Post subject: |
|
|
Infra: You don't have MTRR support enabled as I PM'ed you. The PM includes details of where to enable MTRR
Stu |
|
| Back to top |
|
|
Sarlok
Tux's lil' helper
Joined: 03 Jan 2003
Posts: 98
|
| Posted: Sat May 31, 2003 4:10 pm Post subject: |
|
|
Hey folks. thought I'd add my experiences to this thread, we'll get installing Radeon drivers down to a fine art eventually.
My system specs:
Duron 1ghz
ECS K7SEM mainboard
Radeon 8500 128 meg DDR
Vanilla 2.4.20 kernel
Fluxbox 0.1.14-r1
XFree 4.3.0-r2
I got it working to around 2200 fps, still not great, but a lot better than 180!
I just wish I knew how I got it up to 4000+ fps before. I got it working a week ago just in time to re-format everything. In case somone's feeling more adventurous, I was using the driver 'fglrx' at the time with exactly the same system setup, and version of Xfree (Allthough I was using KDE 3.1).
Anyway, these are the steps I took to get it to work today:
| Code: |
su -
emerge -C ati-drivers xfree-drm xfree
--- (Caution: That will remove the listed ebuilds)
Compile kernel *Without* dri/drm support at all. IE, not even as a module.
(In menuconfig it's "Characther Devices -> Direct Rendering Manager (XFree DRI Support)")
Copy kernel to /boot/ (after mounting boot partition), reboot.
cd /usr/portage/x11-base/xfree/
emerge xfree-4.3.0-r2.ebuild
--- If that doesn't start compiling, try again without .ebuild
|
I'll break at this point to explain a little prblem I encountered.
This is where I emerged ati-drivers, or tried to. Every time I got some error "libGL.o: Could not recognize Is a directory"
And the compile would exit with an error ("no error code"). To get around this problem, I did this:
| Code: |
rpm -i --force --nodeps fglrx-glc22-4.2.0-2.5.1.i586.rpm
|
That's the driver RPM from ATI's site, link can be found here:
http://www.ati.com/support/drivers/linux/radeon-linux.html?cboOS=LinuxXFree86&cboProducts=RADEON+8500+128&eula=&choice=agree&cmdNext=Next.
The drivers in that RPM are exactly the same as the ones in the ati-drivers ebuild. Or seem to be at any rate.
I did try X after just using the RPM, no dice ("error loading module 'fglrx' module version missmatch").
Moving onto the next step (Do not run fglrxconfig after installing the rpm)
| Code: |
cd /usr/portage/media-video/ati-drivers/
emerge ati-drivers-2.9.12.ebuild
--- If that doesn't start compiling, try again without .ebuild
opengl-update ati
fglrxconfig
|
After installing the RPM, the ati-drivers installed fine.
And so you know (if you don't, I didn't at the time) you have to go into the /usr/portage/x11-base/ and ati-drivers folders i order to emerge 'specific' versions of ebuilds.
Good luck!
edit: In case anyone wants it, my XF86Config:
| Code: |
Section "dri"
Mode 0666
EndSection
Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
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/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# ModulePath "/usr/X11R6/lib/modules"
EndSection
Section "ServerFlags" #Leave in just in case something needs it later.
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2" #PS2 Optical Wheel mouse
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/mouse"
EndSection
Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5 - 64.3
VertRefresh 50 - 160
EndSection
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection
# === ATI device section ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
Option "no_accel" "no"
Option "no_dri" "no"
Option "DesktopSetup" "0x00000000"
Option "Display2" "0"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
Option "Capabilities" "0x00000000"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
BusID "PCI:1:0:0" # vendor=1002, device=514c
Screen 0
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Server Layout"
Screen "Screen0"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
|
[/code]
_________________
Four-thousand, six-hundred and ninety-one Irradiated haggis. |
|
| Back to top |
|
|
Infra
Tux's lil' helper
Joined: 12 Jul 2002
Posts: 131
Location: Vantaa, Finland
|
| Posted: Sat May 31, 2003 4:24 pm Post subject: |
|
|
| stustill wrote: | Infra: You don't have MTRR support enabled as I PM'ed you. The PM includes details of where to enable MTRR
Stu |
Well still doesn't work
From kernel-config
and when i'm loading radeon module:
| Code: |
root@ascension linux # modprobe radeon
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: unresolved symbol mtrr_del_Rsmp_272d394e
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: unresolved symbol mtrr_add_Rsmp_56179c5f
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: insmod /lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o failed
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/drm/radeon.o: insmod radeon failed |
and if i try to modprobe agpgart:
| Code: |
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o: insmod /lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o failed
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed |
I
_________________
If it works don't mess with it |
|
| Back to top |
|
|
stustill
Guru
Joined: 25 Feb 2003
Posts: 333
Location: Aberdeen, Scotland
|
| Posted: Sat May 31, 2003 5:02 pm Post subject: |
|
|
Infra:
Are you sure that you have compiled the correct chipset support for your AGP? For example, I have compiled VIA chipset support. Also, did you remember to re-emerge xfree-drm after you recompiled your kernel?
Stu |
|
| Back to top |
|
|
Infra
Tux's lil' helper
Joined: 12 Jul 2002
Posts: 131
Location: Vantaa, Finland
|
| Posted: Sat May 31, 2003 5:17 pm Post subject: |
|
|
| stustill wrote: | Infra:
Are you sure that you have compiled the correct chipset support for your AGP? For example, I have compiled VIA chipset support. Also, did you remember to re-emerge xfree-drm after you recompiled your kernel?
Stu |
If I remember right I have Epox 8k7a+ motherboard, so do I compile Via support? Or AMD support?
It's a VIA KT board but I think it has AMD Chipset because it says in the manual:
AMD IGD4 761 AGP set
Do I compile both?
_________________
If it works don't mess with it |
|
| Back to top |
|
|
stustill
Guru
Joined: 25 Feb 2003
Posts: 333
Location: Aberdeen, Scotland
|
| Posted: Sat May 31, 2003 5:22 pm Post subject: |
|
|
I don't think it would do any harm to compile both, but obviouslly one of them will be redundant
Stu |
|
| Back to top |
|
|
Infra
Tux's lil' helper
Joined: 12 Jul 2002
Posts: 131
Location: Vantaa, Finland
|
| Posted: Sun Jun 01, 2003 8:05 am Post subject: |
|
|
Okey I got it working, I think
My card is: ATI Technologies Inc Radeon R100 QD [Radeon 64 DDR]
glxinfo says:
| 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_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
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 1 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x24 24 tc 1 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x25 24 tc 1 24 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 1 24 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 1 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x28 24 dc 1 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x29 24 dc 1 24 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 1 24 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
|
glxgears:
| Code: | infra@ascension infra $ glxgears
1008 frames in 5.0 seconds = 201.600 FPS
1237 frames in 5.0 seconds = 247.400 FPS
1155 frames in 5.0 seconds = 231.000 FPS
1238 frames in 5.0 seconds = 247.600 FPS
1237 frames in 5.0 seconds = 247.400 FPS
1155 frames in 5.0 seconds = 231.000 FPS
1238 frames in 5.0 seconds = 247.600 FPS
1237 frames in 5.0 seconds = 247.400 FPS
1155 frames in 5.0 seconds = 231.000 FPS
1238 frames in 5.0 seconds = 247.600 FPS
1155 frames in 5.0 seconds = 231.000 FPS
1237 frames in 5.0 seconds = 247.400 FPS
1238 frames in 5.0 seconds = 247.600 FPS
|
Should I get more ?
If there's still something wrong heres my XF86Config:
| 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 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
# **********************************************************************
# 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/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/TrueType/"
FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
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
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "fi"
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
# **********************************************************************
# 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 XF86Config 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 "96P"
# 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 30-96
# 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-160
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 xf86config:
Section "Device"
Identifier "** ATI Radeon (generic) [radeon]"
Driver "radeon"
Option "AGPMode" "4"
Option "EnablePageFlip" "True"
#VideoRam 65536
# 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 "** ATI Radeon (generic) [radeon]"
Monitor "96P"
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 |
How do I check is my card using agp 4x?
_________________
If it works don't mess with it |
|
| Back to top |
|
|
neuron
Advocate
Joined: 28 May 2002
Posts: 2371
|
| Posted: Sun Jun 01, 2003 4:22 pm Post subject: |
|
|
| Infra, your not running accelerated 3d, you would get more glxgears fps. |
|
| Back to top |
|
|
stustill
Guru
Joined: 25 Feb 2003
Posts: 333
Location: Aberdeen, Scotland
|
| Posted: Sun Jun 01, 2003 4:27 pm Post subject: |
|
|
| Code: |
OpenGL renderer string: Mesa GLX Indirect
|
That says that it can't find any hardware accelerated drivers, so it uses software rendering. Post the contents of /var/log/XFree86.0.log, that will contain more details as to why it is not working.
Stu |
|
| Back to top |
|
|
|
|
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
|
|
Desktop Environments
