Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
02-02-2013, 07:37 PM
|
#1
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Rep: 
|
ATI/AMD FGLRX graphics driver is activated but not currently in use.
Hello all,
I've had problems with this(these) driver(s) since day one. Currently in the Additional Drivers utility it says that the driver is activated but not currently in use. When I look in the system settings, it says my Graphics are VESA  VST. When I look in the xorg.conf file it says load "glx". Should I just change that "glx" to "fglrx" in the text editor, save and reboot or is there somehting else I should be doing?
Thank you for your guidance.
|
|
|
|
02-03-2013, 10:20 AM
|
#2
|
|
Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 5,365
|
in xorg.conf or xorg.conf.d/* find the line that says
in the video card section, and get it changed to
amd don't trust me on the D in Driver - it could be 'driver'
|
|
|
|
02-03-2013, 01:42 PM
|
#3
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Original Poster
Rep: 
|
Thanks bu no joy. The only file that I can find a Driver line as you describe is call xorg.conf.failsafe (upper case D by the way). I backed that up then changed the driver to fglrx and rebooted but nothing has changed. I looked at all the scripts in xorg.conf.d/ as you suggested (which for anyone reading this is in /usr/share/X11/) but none includes a graphics driver line. Any other suggestions?
|
|
|
|
02-03-2013, 03:26 PM
|
#4
|
|
Moderator
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware, Debian
Posts: 12,513
|
Run, as root, the command
Code:
aticonfig --initial
This will generate a proper xorg.conf for use with the driver. Then just reboot the system.
|
|
|
|
02-03-2013, 05:16 PM
|
#5
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Original Poster
Rep: 
|
Huh! I was sure that was going to work but still no joy.
The command did in fact add a bunch of lines to my xorg.conf script (see below). But still, Graphics is still VESA  VST and Driver is "activated but not currently in use." Maybe I should not be worried about this because I'm not having any real problems (that I know about). I just find it strange that I can't see to get this driver to engage.
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
Load "glx"
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 "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:0:1:0"
EndSection
Section "Screen"
Identifier "Default Screen"
DefaultDepth 24
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
|
|
|
|
02-03-2013, 06:18 PM
|
#6
|
|
Moderator
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware, Debian
Posts: 12,513
|
Please use code-tags to post config files and output of commands.
Anyways, have you rebooted the machine?
Please show us your /var/log/Xorg.0.log, it will be a large file, so please attach it to a post instead of posting the contents.
|
|
|
|
02-04-2013, 10:18 PM
|
#7
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Original Poster
Rep: 
|
What's a code-tag?
|
|
|
|
02-04-2013, 10:30 PM
|
#8
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Original Poster
Rep: 
|
xorg.0.log
I think it's attached. Xorg.0.log
|
|
|
|
02-05-2013, 01:53 AM
|
#9
|
|
Moderator
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware, Debian
Posts: 12,513
|
Quote:
Originally Posted by CSA60
What's a code-tag?
|
See my signature.
Anyways, according to the log-file you are using the proprietary AMD driver and hardware acceleration is working, so I assume that the only problem is the Additional Drivers program showing you wrong information. If 3D acceleration is working I would just ignore that.
|
|
|
|
02-05-2013, 04:09 AM
|
#10
|
|
Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 5,365
|
Quote:
Originally Posted by CSA60
What's a code-tag?
|
If you hit "Reply" at the top of the thread, it's that symbol ' #' in the lineup. If you want to do it manually, it's CODE in [] to start and /CODE in [] to end
|
|
|
|
02-05-2013, 10:34 AM
|
#11
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Original Poster
Rep: 
|
Should I mark this as solved. There still seems to be a bug somewhere in the OS and/or driver utility.
|
|
|
|
02-06-2013, 03:18 AM
|
#12
|
|
Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 5,365
|
If you really feel there's a bug, mark this solved, and get onto phoronix forums. The ati developers feel they can contact the world from there. Get on your forum and moan, but have your facts straight and follow instructions or you'll be ignored.
|
|
|
|
02-06-2013, 04:34 AM
|
#13
|
|
Moderator
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware, Debian
Posts: 12,513
|
The AMD developers have nothing to do with the Additional Driver program, that is developed by Canonical. Since the driver seems to work correctly I would report this as bug for the Additional Drivers software, not as driver bug.
|
|
|
|
02-06-2013, 11:27 AM
|
#14
|
|
LQ Newbie
Registered: Jan 2013
Posts: 26
Original Poster
Rep: 
|
Thanks. I'll mark this as solved.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:32 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|