radeon-profile icon indicating copy to clipboard operation
radeon-profile copied to clipboard

All buttons unclickable in Ubuntu 18.04

Open JC-S opened this issue 5 years ago • 27 comments

I installed using:

sudo add-apt-repository ppa:trebelnik-stefina/radeon-profile
sudo apt-get install radeon-profile

And then when I run radeon-profile, the GUI popped up without problem, and shows the correct information about my GPU, but all buttons are grey and unclickable: Screenshot from 2019-06-03 19-01-39

JC-S avatar Jun 03 '19 11:06 JC-S

This bug also affects me, able to provide information about system and config if desired.

Dantali0n avatar Jun 03 '19 11:06 Dantali0n

Do you have daemon installed? Also, this seem to be very old version, that could be the cause.

marazmista avatar Jun 03 '19 18:06 marazmista

Do you have daemon installed? Also, this seem to be very old version, that could be the cause.

Thanks for your reply. Yes, I do have a daemon installed. It is installed as a dependency by apt.

Also, is there any way to install a newer version other than compile from scratch? Is there any deb packages?

JC-S avatar Jun 04 '19 02:06 JC-S

No, I don't think so. The only place I've found is this that you've mentioned in first post.

marazmista avatar Jun 04 '19 19:06 marazmista

@JC-S You can use this script to compile & install latest:

https://github.com/Enigma0/build-scripts/blob/master/build_radeon_profile.sh

Not a .deb but next best thing.

Snowman3456 avatar Jun 04 '19 19:06 Snowman3456

Actually I fixed this issue on my system by starting radeon-profile with root privileges

sudo radeon-profile

Marco-MP avatar Jun 05 '19 12:06 Marco-MP

Actually I fixed this issue on my system by starting radeon-profile with root privileges

sudo radeon-profile

I still experience the issue even when running with root privileges.

Dantali0n avatar Jun 05 '19 21:06 Dantali0n

I got it working on 18.04 while having the daemon. Really makes it easy as it goes by the daemon to control the card rather than root. Just be sure you got the daemon installed. If it doesn't work still, I don't know, I guess you're unlucky

Shijikori avatar Jul 13 '19 05:07 Shijikori

I have a similar issue on 18.04. Some of the buttons and tabs work, some don't. Also, only the Connections tab has information, everything else is blank. Edit: After further testing I realise that the same thing happens when I run radeon-profile without the daemon. It seems I might be doing something wrong trying to run the daemon, but I don't know what.

Thisisaline avatar Jul 21 '19 17:07 Thisisaline

I have a similar issue on 18.04. Some of the buttons and tabs work, some don't. Also, only the Connections tab has information, everything else is blank. Edit: After further testing I realise that the same thing happens when I run radeon-profile without the daemon. It seems I might be doing something wrong trying to run the daemon, but I don't know what.

I just realized that I compiled radeon-profile and it's daemon, I didn't install it through a ppa. Maybe try that. For both, you just got to do 'sudo make install' at the end.

Shijikori avatar Jul 23 '19 19:07 Shijikori

I have a similar issue on 18.04. Some of the buttons and tabs work, some don't. Also, only the Connections tab has information, everything else is blank. Edit: After further testing I realise that the same thing happens when I run radeon-profile without the daemon. It seems I might be doing something wrong trying to run the daemon, but I don't know what.

I just realized that I compiled radeon-profile and it's daemon, I didn't install it through a ppa. Maybe try that. For both, you just got to do 'sudo make install' at the end.

I compiled them as well cos as far as I know there is only one ppa available for radeon-profile that is quite outdated. Also it is my understanding that sudo should not be necessary. I compiled both as per the instructions, with 'qmake && make'. What could be the issue for me is that I have not moved the systemd service file to /etc/systemd/system/. I don't know this for sure though as I have not yet got around to doing it, and being new to linux, I first have to figure out how to do it.

Thisisaline avatar Jul 26 '19 15:07 Thisisaline

@Thisisaline sudo make install should do on both, it will install the app system wide and it should install the daemon correctly then, with sudo service --status-all you can see if the daemon is started (if it has a plus, it's running). If it's not, just do sudo service <service> start you may want to reboot after installing the daemon, to be sure it's installed correctly, but it's not necessary

Shijikori avatar Jul 26 '19 15:07 Shijikori

ok thanks, but isn't the tool supposed to be able to run without root access?

Thisisaline avatar Jul 26 '19 17:07 Thisisaline

you're giving it root access so it can be installed on the system @Thisisaline . You will have to do it to install the daemon. For the software though, you can just run the compiled code like you were already doing. It wont run as root, even when installed on the system. Though, if your daemon is not installed, it cannot access the card. It's because it is going by the daemon to access what's not accessible without root.

Shijikori avatar Jul 26 '19 17:07 Shijikori

ok, so even though I have already run make with the daemon I can just go into radeon-profile-daemon/radeon-profile-daemon folder and run sudo make install? Do I need to copy the systemd service file to /etc/systemd/system/ like it mentions on the daemon git page? If yes, how do I do it?

Thisisaline avatar Jul 26 '19 18:07 Thisisaline

@Thisisaline the sudo make install is for the daemon. Though, you can do it for radeon-profile if you want it to appear with it's icon like all of your other programs in the launch menu. I honestly don't know how to setup a service. I did it once for a TeamSpeak server but that's about it.

Edit: I'll rephrase what I said, maybe it'll clear confusion. sudo make install will just rebuild the radeon-profile-daemon and install it for you. You wont have to do anything, the daemon will be in place. You can check if it's setup correctly with the commands I talked about above.

Shijikori avatar Jul 26 '19 19:07 Shijikori

Hi. To install systemd service (after you've executed make install on deamon) you need to copy radeon-profile-daemon.service to usr/lib/systemd/system/ and later execute systemctl enable radeon-profile-deamon --now. That should start the daemon.

marazmista avatar Jul 27 '19 17:07 marazmista

I guess I was the only one that it installed automatically... the service commands should do too.

Shijikori avatar Jul 27 '19 19:07 Shijikori

I have installed radeon-profile by building it from source but no matter how I run it I can still not press any buttons

Dantali0n avatar Jul 28 '19 13:07 Dantali0n

@Dantali0n did you install the daemon?

Shijikori avatar Jul 28 '19 16:07 Shijikori

@Dantali0n did you install the daemon?

No and I like not to, the documentation states it should work without 'Otherwise app need to be run with root privilages for changing power profiles (and clocks readings sometimes)'

Dantali0n avatar Jul 28 '19 20:07 Dantali0n

@Dantali0n your phrasing suggests you're looking at it backwards.. you need the daemon to run radeon-profile without root privileges, not the other way round.

@Mikasu-X14 @marazmista Thanks. I only ran make and not make install, that's probably contributed to my situation. So I can run make install without sudo, or is sudo necessary? Also, sorry for a noob question, but I assume I can copy radeon-profile-daemon.service to usr/lib/systemd/system/ by running sudo cp radeon-profile-daemon.service usr/lib/systemd/system/radeon-profile-daemon.service from within the extra folder, is this correct? Also, can I enable and start the service file straight after doing the above, or do I have to somehow navigate to the usr/lib/systemd/system/ folder first? And if I may lastly ask for my own knowledge, since apparently running systemctl enable radeon-profile-daemon.service AND systemctl start radeon-profile-daemon.service vs running only systemctl enable radeon-profile-deamon --now both start the daemon, what is the difference between both methods? Is the --now command like a sort of alternative short cut for the start command?

Thanks a lot!

Thisisaline avatar Jul 28 '19 21:07 Thisisaline

@Thisisaline Sudo is necessary because it installs on the system where only root can modify anything. It's /usr . Always from root. Else, it wont work. For the command, I guess it's just to keep the legacy way of doing things. I think most people use service nowadays as opposed to systemctl.

Shijikori avatar Jul 28 '19 23:07 Shijikori

@Dantali0n you will have to run with root then. If it's not working, maybe you are not on an up-to-date version or it didn't compile correctly, I can't tell

Shijikori avatar Jul 28 '19 23:07 Shijikori

@Mikasu-X14 @Thisisaline I already stated I run radeon-profile as root on the 5th of June, further emphasized by 'no matter how I run it'. I think saying its not up-to-date or diden't compile correctly is something we should not immediately assume, especially since it was working for me before (and I did not reinstall).

I think it is likely there is a bug that is causing this problem and we should attempt to investigate.

Dantali0n avatar Jul 29 '19 06:07 Dantali0n

@Dantali0n could also have to do with your kernel version but that's unlikely. Maybe communicate with the developper to see what can be done about your case.

Note : AMD cards have their Driver in the kernel, I think you know that. Just thinking perhaps a patch could do something but as I said, very unlikely.

Edit: Also unlikely but possible, your mesa version. If you're using a mesa-git or something that isn't a kind of stable release as they are libraries to the driver and, as I understood, radeon-profile deals with them too.

Edit 2: if none of this makes sense, feel free to ignore. I am just trying to help better knowledged out there by giving my ideas.

Shijikori avatar Jul 29 '19 07:07 Shijikori

I've got the tool mostly working now, except for the part I need the most, the overclock tab (since I need to underclock my gpu). I've already enabled overdrive bit on grub when I installed wattmangtk, and as far as I understand, I did it correctly. What should I do to get the overclock tab to work? Edit: Maybe I'm a bit slow and should have realised this sooner, but I think it's finally dawned on me that the tool absolutely requires the amdgpu driver to fully function, as opposed to the ubuntu open source driver. Can someone confirm that this is correct?

Thisisaline avatar Aug 07 '19 16:08 Thisisaline