Dear All,
Is it an application to check the 3d acceleration of a graphic card ?
many thanks in advance
new user x
This is a good question. I wish there was some decent graphics benchmarking software available for linux. Anyway, have a look at:
3D Graphics hardware performance using Free Software drivers (X.Org DRI) [Free3D]
They mention
…a simple shell script was proposed Henrik Carlqvist in a comp.os.linux.hardware discussion and subsequently revised by Michael Mauch and others. This script uses glxgears to get a frame rate for 3D rendering. We are aware this isn’t a particularly good benchmark. It’s been compared to bogomips for graphics cards. But it is readily available on almost every computer running Xorg and provides a handy baseline for comparing hardware.
They offer this script:
cat /proc/pci | grep VGA || lspci | grep VGA | colrm 1 4 ; cat /proc/cpuinfo |
egrep “model name|MHz” ; xdpyinfo | egrep “version:|dimensions|depth of” ; glxinfo |
egrep -A2 “direct rendering|OpenGL vendor” ; uname -sr; glxgears & sleep 30 ;
killall glxgears
Cut and paste it into your favorite terminal, and see what results you get. 
Dear Sir,
Find hereunder the result :
linux-jei6:/home/tringaf # cat /proc/pci | grep VGA || lspci | grep VGA | colrm 1 4 ; cat /proc/cpuinfo |
> egrep “model name|MHz” ; xdpyinfo | egrep “version:|dimensions|depth of” ; glxinfo |
> egrep -A2 “direct rendering|OpenGL vendor” ; uname -sr; glxgears & sleep 30 ;
> killall glxgears
cat: /proc/pci: Aucun fichier ou dossier de ce type
0.0 VGA compatible controller: ATI Technologies Inc RV630 PRO AGP [Radeon HD 2600 PRO AGP]
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
cpu MHz : 2040.325
X.Org version: 1.5.2
dimensions: 1024x768 pixels (304x228 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.2
Linux 2.6.27.23-0.1-pae
[1] 6467
486 frames in 5.0 seconds = 97.109 FPS
502 frames in 5.0 seconds = 100.352 FPS
503 frames in 5.0 seconds = 100.522 FPS
503 frames in 5.0 seconds = 100.428 FPS
503 frames in 5.0 seconds = 100.450 FPS
Is it something we can change/add ?
Bye
new user x
Easiest way? Install Urban Terror and run it, then you’ll reliably know if you have full acceleration. Do not depend on glxgears as it isn’t meant to show if you have or don’t have acceleration. It also is not a benchmark. So just get a real OpenGL game and test with it
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.2
Linux 2.6.27.23-0.1-pae
[1] 6467
486 frames in 5.0 seconds = 97.109 FPS
502 frames in 5.0 seconds = 100.352 FPS
503 frames in 5.0 seconds = 100.522 FPS
503 frames in 5.0 seconds = 100.428 FPS
503 frames in 5.0 seconds = 100.450 FPS
Your results suggest you are using the open source driver. You can improve this performance by installing the proprietary driver:
Dear Sir,
As I got already a problem trying to use ati drivers, is a way a safe way to recover “old” configuration ?
I got a black screen and re-install the whole system.
Thank You
new user x
Try starting in failsafe mode. That should get your desktop back with basic vesa driver. You may need to uninstall the driver via yast software manager. Search for ‘fglrx’. You should have something like
x11-video-fglrxG01
ati-fglrxG01-kmp
With your HD card, it may be necessary to use a later version directly from amd:
Dear Sir,
After install the proprietary driver, I ran the config command and got the following message :
/usr/bin/aticonfig --initial
Found fglrx primary device section
Using /etc/X11/xorg.conf
Saved back-up to /etc/X11/xorg.conf.fglrx-1
What should I do now ?
Many thanks in advance
new user x
Hello again,
It seems that the driver were not started :
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 1.4 (2.1 Mesa 7.2)
Should I reboot before to be able to configure the driver ?
If it is something wrong with the configuration, I will maybe not be able to configure after reboot (black screen for instance ) ?
I appreciate Your advice
new user x
New User X adjusted his/her AFDB on Friday 24 Jul 2009 09:56 to write:
>
> Dear Sir,
> After install the proprietary driver, I ran the config command and got
> the following message :
> /usr/bin/aticonfig --initial
> Found fglrx primary device section
> Using /etc/X11/xorg.conf
> Saved back-up to /etc/X11/xorg.conf.fglrx-1
>
> What should I do now ?
> Many thanks in advance
> new user x
>
>
If you are at the command line in runlevel 3 then run :
init 5
this should bring you up to the graphical login, when back in KDE/Gnome open
a terminal/console and run as a normal user:
amdcccle
this will bring up the ATI Catalyst GUI to configure the graphics card.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Hello,
I ran the command amdcccle and I get an error message:
“There is no driver installed”
Should I reboot ?
Thanks
new user x
New User X adjusted his/her AFDB on Friday 24 Jul 2009 10:16 to write:
>
> Hello again,
> It seems that the driver were not started :
> fglrxinfo
> display: :0.0 screen: 0
> OpenGL vendor string: Mesa Project
> OpenGL renderer string: Software Rasterizer
> OpenGL version string: 1.4 (2.1 Mesa 7.2)
> Should I reboot before to be able to configure the driver ?
> If it is something wrong with the configuration, I will maybe not be
> able to configure after reboot (black screen for instance ) ?
> I appreciate Your advice
>
> new user x
>
>
You can try a reboot, if you get a black screen try pressing Ctrl+Alt+F1 and
see if that gets you to a commanline.
It may be that the drivers have not taken or you still have some old libs
hanging about that a reboot will get rid of.
If you can then have a look in the fglrx-install.log in /usr/share/ati
It could be a problem with the other drivers you have tried leaving stuff on
your system that is conflicting with the propriety drivers, if that is the
case then you will need to ( on the commandline as root ) run the uninstall
script in the ATI directory and also run yast and uninstall the drivers that
were put on from the repository. like the other poster said search for fglrx
and uninstall the 2 files.
Also have a look in /etc/X11/ to see if there is a file called:
xorg.conf.install
after you have removed all those files then rename this file as xorg.conf,
let it overwrite the xorg.conf that is in there.
The reason for this is that the SuSE provided drivers and the ATI ones will
configure the xorg.conf in their own little ways and this can lead to all
sorts of problems when you install different drivers from different sources.
This should at least get you to a GUI even if it is rather ugly.
If so then you will need to drop to runlevel 3 and install the ATI propriety
drivers again but first let us know if you get to a GUI with no errors then
we can help you get a fully working 3D setup.
See if that helps
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Dear Sir,
I rebooted.
Ran amdcccle and configured the display.
It seems that everythings were ok but:
the display of a document seems to sticky. If I use the mouse to moove the cursor or roll the scroll, everything moves very slowly, like step by step, pixel after pixel if you see what I mean.
Is it something additional to be adjusted ?
Command indicated in the gui of amd still aborts :
/usr/bin/aticonfig --initial
Found fglrx primary device section
Using /etc/X11/xorg.conf
Saved back-up to /etc/X11/xorg.conf.fglrx-3
/usr/bin/aticonfig: Writing to ‘/etc/X11/xorg.conf’ failed. Bad file descriptor.
Any good idea?
Many thanks in advance
new user x
New User X adjusted his/her AFDB on Friday 24 Jul 2009 11:56 to write:
>
> Dear Sir,
> I rebooted.
> Ran amdcccle and configured the display.
> It seems that everythings were ok but:
> the display of a document seems to sticky. If I use the mouse to moove
> the cursor or roll the scroll, everything moves very slowly, like step
> by step, pixel after pixel if you see what I mean.
> Is it something additional to be adjusted ?
> Command indicated in the gui of amd still aborts :
> /usr/bin/aticonfig --initial
> Found fglrx primary device section
> Using /etc/X11/xorg.conf
> Saved back-up to /etc/X11/xorg.conf.fglrx-3
> /usr/bin/aticonfig: Writing to ‘/etc/X11/xorg.conf’ failed. Bad file
> descriptor.
> Any good idea?
> Many thanks in advance
> new user x
>
>
Can you please cut and paste the contents of the /etc/x11/xorg.conf here.
also the results of glxinfo
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Dear Mark,
*For xorg.conf:
/…/
SaX generated X11 config file
Created on: 2009-07-21T13:17:06+0200.
Version: 8.1
Contact: Marcus Schaefer <sax@suse.de>, 2005
Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
Automatically generated by [ISaX] (8.1)
PLEASE DO NOT EDIT THIS FILE!
Section “ServerLayout”
Identifier “Layout[all]”
Screen 0 “aticonfig-Screen[0]-0” 0 0
InputDevice “Keyboard[0]” “CoreKeyboard”
InputDevice “Mouse[1]” “CorePointer”
Option “Clone” “off”
Option “Xinerama” “off”
EndSection
Section “Files”
InputDevices “/dev/gpmdata”
InputDevices “/dev/input/mice”
FontPath “/usr/share/fonts/misc:unscaled”
FontPath “/usr/share/fonts/local”
FontPath “/usr/share/fonts/75dpi:unscaled”
FontPath “/usr/share/fonts/100dpi:unscaled”
FontPath “/usr/share/fonts/Type1”
FontPath “/usr/share/fonts/URW”
FontPath “/usr/share/fonts/Speedo”
FontPath “/usr/share/fonts/PEX”
FontPath “/usr/share/fonts/cyrillic”
FontPath “/usr/share/fonts/latin2/misc:unscaled”
FontPath “/usr/share/fonts/latin2/75dpi:unscaled”
FontPath “/usr/share/fonts/latin2/100dpi:unscaled”
FontPath “/usr/share/fonts/latin2/Type1”
FontPath “/usr/share/fonts/latin7/75dpi:unscaled”
FontPath “/usr/share/fonts/baekmuk:unscaled”
FontPath “/usr/share/fonts/japanese:unscaled”
FontPath “/usr/share/fonts/kwintv”
FontPath “/usr/share/fonts/truetype”
FontPath “/usr/share/fonts/uni:unscaled”
FontPath “/usr/share/fonts/CID”
FontPath “/usr/share/fonts/ucs/misc:unscaled”
FontPath “/usr/share/fonts/ucs/75dpi:unscaled”
FontPath “/usr/share/fonts/ucs/100dpi:unscaled”
FontPath “/usr/share/fonts/hellas/misc:unscaled”
FontPath “/usr/share/fonts/hellas/75dpi:unscaled”
FontPath “/usr/share/fonts/hellas/100dpi:unscaled”
FontPath “/usr/share/fonts/hellas/Type1”
FontPath “/usr/share/fonts/misc/sgi:unscaled”
FontPath “/usr/share/fonts/xtest”
FontPath “/opt/kde3/share/fonts”
EndSection
Section “Module”
Load “dri”
Load “dbe”
Load “freetype”
Load “extmod”
Load “glx”
EndSection
Section “ServerFlags”
Option “AllowMouseOpenFail” “on”
Option “ZapWarning” “on”
EndSection
Section “InputDevice”
Identifier “Keyboard[0]”
Driver “kbd”
Option “Protocol” “Standard”
Option “XkbLayout” “ch”
Option “XkbModel” “microsoftpro”
Option “XkbRules” “xfree86”
Option “XkbVariant” “fr”
EndSection
Section “InputDevice”
Identifier “Mouse[1]”
Driver “mouse”
Option “Buttons” “9”
Option “Device” “/dev/input/mice”
Option “Name” “ImExPS/2 Logitech Explorer Mouse”
Option “Protocol” “explorerps/2”
Option “Vendor” “Sysp”
Option “ZAxisMapping” “4 5”
EndSection
Section “Modes”
Identifier “Modes[0]”
ModeLine “1024x768” 81.8 1024 1080 1192 1360 768 769 772 802
ModeLine “1024x768” 76.2 1024 1080 1192 1360 768 769 772 800
ModeLine “1024x768” 69.7 1024 1080 1184 1344 768 769 772 798
ModeLine “1024x768” 64.1 1024 1080 1184 1344 768 769 772 795
ModeLine “800x600” 48.9 800 840 920 1040 600 601 604 627
ModeLine “800x600” 45.5 800 840 920 1040 600 601 604 625
ModeLine “800x600” 42.1 800 840 920 1040 600 601 604 623
ModeLine “800x600” 38.2 800 832 912 1024 600 601 604 622
EndSection
Section “Monitor”
Identifier “Monitor[0]”
VendorName “GSM”
ModelName “LG ELECTRONICS FLATRON L1510 S”
UseModes “Modes[0]”
DisplaySize 304 228
HorizSync 30.0 - 61.0
VertRefresh 43.0 - 75.0
Option “DPMS”
Option “PreferredMode” “1024x768”
EndSection
Section “Monitor”
Identifier “aticonfig-Monitor[0]-0”
Option “VendorName” “ATI Proprietary Driver”
Option “ModelName” “Generic Autodetecting Monitor”
Option “DPMS” “true”
EndSection
Section “Device”
Identifier “Device[0]”
Driver “radeonhd”
VendorName “ATI”
BoardName “ATI Radeon HD 2600 Pro AGP”
Option “monitor-VGA_1” “Monitor[0]”
EndSection
Section “Device”
Identifier “aticonfig-Device[0]-0”
Driver “fglrx”
BusID “PCI:1:0:0”
EndSection
Section “Screen”
Identifier “Screen[0]”
Device “Device[0]”
Monitor “Monitor[0]”
DefaultDepth 24
SubSection “Display”
Virtual 3840 1200
Depth 15
Modes “1024x768” “800x600”
EndSubSection
SubSection “Display”
Virtual 3840 1200
Depth 16
Modes “1024x768” “800x600”
EndSubSection
SubSection “Display”
Virtual 3840 1200
Depth 24
Modes “1024x768” “800x600”
EndSubSection
SubSection “Display”
Virtual 3840 1200
Depth 8
Modes “1024x768” “800x600”
EndSubSection
EndSection
Section “Screen”
Identifier “aticonfig-Screen[0]-0”
Device “aticonfig-Device[0]-0”
Monitor “aticonfig-Monitor[0]-0”
DefaultDepth 24
SubSection “Display”
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section “DRI”
Group “video”
Mode 0660
EndSection
*And glxinfo gives:
tringaf@linux-jei6:~> glxinfo
name of display: :0.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 12
Current serial number in output stream: 12
Thank You for Your support
new user x
New User X adjusted his/her AFDB on Friday 24 Jul 2009 13:56 to write:
> Section “Monitor”
> Identifier “aticonfig-Monitor[0]-0”
> Option “VendorName” “ATI Proprietary Driver”
> Option “ModelName” “Generic Autodetecting Monitor”
> Option “DPMS” “true”
> EndSection
>
> Section “Device”
> Identifier “Device[0]”
> Driver “radeonhd”
> VendorName “ATI”
> BoardName “ATI Radeon HD 2600 Pro AGP”
> Option “monitor-VGA_1” “Monitor[0]”
> EndSection
>
> Section “Device”
> Identifier “aticonfig-Device[0]-0”
> Driver “fglrx”
> BusID “PCI:1:0:0”
> EndSection
As I thought your xorg is not configured correctly, there are a couple of
ways to do this.
One way is to drop to runlevel 3 and create a new xorg.conf with sax telling
it to use the vesa driver then use the aticonfig to generate a completely
new one specifically for your new drivers, so what you need to do is from
KDE/Gnome press Ctrl+Alt+F1 this will drop you to a console, then login as
root enter password and in this order:
sax2 -r -m 0=vesa
That will ignore the xorg.conf and start with a fresh blank one (-r) using
the module (-m) vesa, let it start and make sure you test before you save
then when that has set up then save the configuration, next when you get
back to the commandline issue:
aticonfig --initial
you should see the message about the xorg.conf again but this time it should
alter the xorg.conf specifically for the flgrx module.
Now issue:
init 5
and if the GUI starts use amdcccle to configure the graphics.
Hope that works
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Hello,
The 1st command opens the sax2 window but the test aborts and write to check file xorg.99.log :
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/linux-jei6:99
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
Find the 3 first lines.
and now ?
New User X adjusted his/her AFDB on Friday 24 Jul 2009 15:56 to write:
>
> Hello,
> The 1st command opens the sax2 window but the test aborts and write to
> check file xorg.99.log :
You want the Xorg.o.log, the 99 version is an old one just have a look at
the date on them.
> _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
> _XSERVTransOpen: transport open failed for inet6/linux-jei6:99
> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for
> inet6
> Find the 3 first lines.
> and now ?
>
>
This error however indicates that you have not got ipv6 support in the
kernel ( I could be wrong there though ).
Are you sure that you have not got an xserver running, sometimes if there is
a crash or there is something wrong then X can still be running even if you
are in runlevel 3, run top and see if X is still going if so kill it.
If X is not running then have a look in /tmp/X11-unix and see if there is a
file called X0 if there is then delete it and the X11-unix dir also delete
the X0-lock file in /tmp if it exists.
See if that helps.
just to get my mind straight on this you are using a root login and not
sudo?
Your command prompt does end in a # yes?
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Dear Mark,
Sorry for that but I don’t know what a xserver is…
Then of course, don’t know either when it is running.
I log like this :
tringaf@linux-jei6:~> su
Mot de passe :
linux-jei6:/home/tringaf #
Never mind if you think my knowledge is too low for a successfull result.
If you mind go further, just let run the system with linux drivers.
Thank You so far
new user x
New User X adjusted his/her AFDB on Friday 24 Jul 2009 16:36 to write:
>
> Dear Mark,
> Sorry for that but I don’t know what a xserver is…
> Then of course, don’t know either when it is running.
>
> I log like this :
> tringaf@linux-jei6:~> su
> Mot de passe :
> linux-jei6:/home/tringaf #
>
> Never mind if you think my knowledge is too low for a successfull
> result.
> If you mind go further, just let run the system with linux drivers.
>
> Thank You so far
> new user x
>
>
Hey no problems,
the “X” is the server which runs the graphic engine for linux.
Here is a quick and not very specific explanation:
You have the linux kernel and all the commands and applications that can run
with no graphics which is what you use when you are in runlevel 3 ( and some
other runlevels ) this is great if you just want to run on a machine that
does not need graphics such as servers and headless machines that are
remotely controlled and do not have monitors, keyboards, mouse.
If you want graphics then you have the X server which puts a layer on top of
the base system to handle drawing stuff to the screen in a pretty way, X on
its own does not really do much more than enable the software to talk to the
graphical hardware and put the display on the screen.
Now you need a desktop/window manager (
KDE/Gnome/xfce/wm/afterstep/enlightenment etc… etc… ) these are the bits
that we see and can use to move things about and give us all the eye-candy.
Sometimes if things are not quite right or things are not configured good
then when you go back to runlevel 3 (init 3) then the X server does not get
stopped or is locked open and still runs, in that case the configuration
with sax2 and others will not work correctly because they need exclusive use
of the X server and cannot start one as there is already one running.
To see if there is an instance of one running while in runlevel 3 you can
run the command top this will show what processes are running and give you
option to kill them by entering there pid number.or you can use the command:
killall -9 X
When you run an application like X it will create a lock file ( the one in
tmp ) that tells other applications that it is running and so they will not
start, however if the X server crashes and therefore the lock file is not
removed then any application that starts and needs exclusive rights to the X
server will look in tmp find the lock file and think X is running so will
not start and throw errors.
So you need to delete those orphan lock files for the program to run.
I hope that helps a bit with your understanding
it is not an exact description there is far far more to it than that but it
should give you an idea.
As to your problem I think it is just that some of you config files got a
little confused after you tried one set of the drivers and then another and
so had 2 sets of drivers trying to load in the xorg.file ( there was the
vesa and the fglrx sections ) and so when you tried to run amdcccle it did
not find the fglrx driver as X had loaded the vesa one first.
If you still want to give it a go though I will be here just give me a
shout, however will be away all weekend after tomorrow morning so do not
expect an answer till next week after tomorrow.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum