Hi, I’m running a fresh install of OpenSUSE 12.3 (with KDE), except I switched to the tumbleweed repos. I have a AMD Radeon HD6770 graphics, for which I’m running the default open source drivers (don’t do much gaming under linux, I keep win7 in a dual boot). My problem is the following is, in OpenSUSE, it seems like the graphics card is always loaded: it’s running very hot (73C) and the fan is always spinning at max speed, even when I’m not doing anything. In windows, when not doing anything, it runs around 56C with the fan at minimum speed.
Being relatively new to linux, I’m not sure where to start to troubleshoot this. Is there something that can tell me which process is putting load on the graphics?
AFAIK the opensource drivers do have problems with the powermanagement at least on certain cards.
So maybe you should consider trying to install the proprietary fglrx driver, even if you don’t do gaming.
On Mon, 10 Jun 2013 15:16:02 +0000, wolfi323 wrote:
> auxym;2563863 Wrote:
>> Hi, I’m running a fresh install of OpenSUSE 12.3 (with KDE), except I
>> switched to the tumbleweed repos. I have a AMD Radeon HD6770 graphics,
>> for which I’m running the default open source drivers (don’t do much
>> gaming under linux, I keep win7 in a dual boot). My problem is the
>> following is, in OpenSUSE, it seems like the graphics card is always
>> loaded: it’s running very hot (73C) and the fan is always spinning at
>> max speed, even when I’m not doing anything. In windows, when not doing
>> anything, it runs around 56C with the fan at minimum speed.
>> Being relatively new to linux, I’m not sure where to start to
>> troubleshoot this. Is there something that can tell me which process is
>> putting load on the graphics?
> AFAIK the opensource drivers do have problems with the powermanagement
> at least on certain cards.
> So maybe you should consider trying to install the proprietary fglrx
> driver, even if you don’t do gaming.
I’d concur with that, my wife’s laptop had a similar issue and
reinstalling the fglrx drivers (which had previously been installed)
fixed it for us.
Well, AFAIK the script should install all needed packages. Did you try the latest version? (13.4)
Could you post the error message please?
I don’t know what packages are needed exactly, but you also need at least kernel-desktop-devel, I would say. (provided that you use kernel-desktop, use “uname -a” to check)
And I don’t think you need kernel-source.
The automated script is intended to work against the official released kernel (3.7.whatever_dot_release)
As for the manual install attempt, is there not a 3.9.4 kernel now available? I wonder if you happened by way of chance to grab the source and related devel packages during an update window in the repo you were drawing from.
That’s likely apparently. I updated kernel-desktop and was able to successfully install fglrx. The good news is that vlsmis tells me fglrx is loaded. The bad news:
Still getting the fan and temperature problem.
X won’t start:
hostname: Name or service not known xauth: file /home/francis/.serverauth.5416 does not exist
/etc/X11/xinit/xserverrc: line 59: exec: X: not found xinit: giving up xinit: unable to connect to X server: Connection refused xinit:v server error -------------------------------------------------------------------------------------------xinit failed. /usr/bin/Xorg is not setuid, maybe that’s the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local
Thanks everyone for the help so far, much appreciated
LOL, I was going to write that I have no idea what vlsmis is
The bad news:
2. X won’t start:
did you remove the 3 from your kernel boot parameters that you added earlier? Sure sounds like you haven’t
“startx” by user has not been supported by openSUSE for a number of releases (security reasons); you’d have to alter a configuration to allow that method to work, but thats not recommended, as you can accomplish the same end result (bringing up a user’s desktop) in a secure manner via “systemctl start xdm” (to log in from a display manager) or “sudo /sbin/init 5” or …
Also: I have rebooted. Nothing gets added to /var/log/Xorg.0.log
you won’t get a log unless X starts – and, as it appears you are launching into run level 3 (or non graphical target or whatever the heck systemd calls it these days), and you (as user) are not privileged to launch X in the manner you were trying, the result was no X … no X, no X log
Hmm, I don’t really know how comprehensive the power management for the device would be when you’re not logged into a desktop/X environment … meaning I imagine that there is some base/modicum level of power management being provided by the kernel driver, but that robust power management features is perhpas contingent and interactive within an X environment
Other thoughts is perhaps the problem lay else where within the system or actual hardware itself
on second read, robust was the wrong word to use in relation to the PM features of the OSS drivers, as they (as already alluded to) are not very good in these regards.
The good news, is that there has been some improvements in recent kernels (3.8, 3.10) in relation to PM … in particular, some nice improvements related to CPU dynamic scaling (both Intell and AMD related code drops). On the graphics front, in particular to that which affects you, it is well known that the AMD developers who work on the OSS stack have already written considerable PM improvements, but are unable to yet release the code until it passes technical/legal review. Unfortunately, there is no specific timeline as to when such a code drop may happen, as well as there also being the possibility of it being upheld/veto’ed, though hopefully the later won’t come to pass. As that process has been going on for a while now, it is hopeful that it is a case of sooner, rather then later. Though, I can imagine that that news is small consolation to many who want it now!
In the meantime, the prop catalyst/fglrx drivers have much better PM support.
Posting this from OpenSUSE with working KDE and a quiet video card
In my spree to remove everything to do with radeon to get fglrx working, I think I had removed libdrm-radeon… oops >:(. Removing that (not even sure what it is) also removed kdm, kde and xorg-x11-server and I didn’t notice. Anyways, zypper in kdm and it’s all good now
Thanks again to everyone, you’ve been very helpful (and I’ve learned a bit in the process)
libdrm_radeon is the “Userspace interface for Kernel DRM services for AMD Radeon chips”, in other words it provides direct access to the graphic card (for radeon cards; there is also libdrm_nouveau2 and libdrm_intel1). I don’t think fglrx uses this, but Mesa depends on it on the rpm package level (and the radeon driver needs it for direct rendering on a radeon card).
xorg-x11-server depends on Mesa, and kdm depends on xorg-x11-server. That’s the reason why all those got removed when you removed libdrm_radeon1, and all of those got installed again when you installed kdm.