Overclocking my Processor with TurionPowerControl. Issue with OpenSuse

English Applications
1

Hello everyone! The problem I am having is something I did not have on a debian based Distro so this might be a easy fix that i just cant see :P. Anyways I have finished Installing the program but it requires some things to be enabled before I can actually go ahead and overclock with it.
Here is my problem I cant seem to get these commands to work on Opensuse.

sudo modprobe cpuid

sudo modprobe msr

If anyone could help me that would be great! Thanks in advance!

2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How, exactly, do they not work? Throw an error? Crash the box?
Nothing at all?

I presume ‘sudo’ works, and ‘modprobe’ is a standard package too so
worst case you may just want to specify its absolute path
(/sbin/modprobe) instead of just the executable name. After that, do
you have the ‘cpuid’ or ‘msr’ modules installed?

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJQvO0qAAoJEF+XTK08PnB51wkQALMcAujFKsdbtztdTD73H2X6
DViBVJL/nROKsr/oTzHL1tbWVlEMNhz7mKkzpuKySIGBYXbUxbe6yvOXk80cdzRt
xGLspjEq5Tgcc5P3j/Eu9VYdmO8y0MMFjvGKPNWLGn9VAHxgtnRa8dFU0FY3a2wN
kWziv4HNocMvZFk00ygxb1028ZaKVxIpv4PXEbpObqe9MhelQD6iFPlYCB22c0Vb
lbMO6RQCgMfi91ijGgVGDc1KH4OcHSkbj49o2ZDYbqP84pFCtQ29zY2u7p0FIrIO
fuAn3bLcwEeLeYZgbLuvNk11a4oAJy2H5XjSIb9UVKBS00J4M4+e6Wcy4C0TVmia
Eji+WQ5pULdy7rm0epX9rs1BwcF1t/DLuah/eNe+iD0goHyJ793YEUJbdD9si0rw
rXiWrmhNrkVdheMhIE6FFX1k5fpz5nRhSevevXzF5TcAdPD8oI7gVRuLUbtsHSqW
YLRrFNUuHpK+iWr4OcKo1chH9P8eyCV0nlmg+W7tqbS/BioLU0A6KcyqkyhYaRAI
hjtEdNiSUfGAnvvlJGXy736tSpuWK26HcVZGOlnXASd1qBb32TU+CHL6PUHfC0u8
ksCXZ5ambHn5gT6uoeYC+gq9LCiu24X44IQDLpE2b4lvTUusowdHhso19nKX7VBB
vWBvLag4LONvLswIOa1E
=/+hc
-----END PGP SIGNATURE-----

3

i went to software.opensuse.org: to get CPUID
I did

sudo zypper in msr-tools

for the msr
But when i run the command i get.

sudo: modprobe: command not foundjerry@linux-jtjz:~> sudo modprobe cpuid
sudo: modprobe: command not found
jerry@linux-jtjz:~> sudo modprobe msr
sudo: modprobe: command not found
4

Oh wait you are something else with that /sbin/modprobe that actually did it thank you for the help!

5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Oh wait you are something else with that /sbin/modprobe that
> actually did it thank you for the help!

Yes, and it may be useful if you understand why. ‘modprobe’ is in /sbin
which is usually for things (these days) that are usable as ‘root’,
which of course is why you are calling ‘sudo’ before it (well done).
‘sudo’ does not change the user’s PATH, though, so even though ‘root’
can access modprobe without specifying the absolute path sudo is running
with your non-root environment. Putting in the full path helps with that.

On a personal note, anytime I use ‘sudo’ I put in the full path just in
case somebody is tricky/malicious and gives my user a different version
of the command with the intention of causing me harm. For example, if I
convinced you to drop a script in /home/jseymour/bin and make it
executable, and if that script had ‘rm -rf /’ in it, your attempt to add
modules to the kernel would end up wiping your computer. Specifying
absolute paths when making calls out as root like that makes me feel
warmer and fuzzier, and prevents my own stupidity as well.

Thank-you for posting back your results.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJQvPxbAAoJEF+XTK08PnB5no0P/2yJDmfAVE/Dq4+7AauF7oWN
j+WKOUT2D8EtgBIGW3dnJFUHCUY0p2uNWr7COg15P99dD98vpBWJAA4sfTGokhmk
vWfMXrwG2ZqKGBOOd1THiWJAsvd1tbpnVcTTlTW52hEUmbAoTP1Mr63qOlTx/QEP
WINe3U8LyFvVb+0PEPOBWxnC2PYqTllwatzj0JDl5gurRjN4bW0fR17P1AvLdZmb
RdFjsLO6pUlkjONg0CoKLB6hqXbO+uVKhFehiPTbM7FGdjnvEvWMXfb2c6mxKAVq
hG3BjouEyCZtfGziPO+ggNyVHC9x4eMe3N3Ef5ddRuKZkyiioEOS5vXnkIEZlQnZ
WZ+QGLrhxwoe6lleSRefR8ML5WeBHaYUdTbVRaHJNk8OrBlfHZoSiXHUH9hoyWF5
Tys3eU0PAlzL90b4fxMwBqveOlcQzp/kfhczXItV1tMIAzVqrZCQo2xYxN+5Aga9
eJwQU6VInDA4/GH+aXeBeCgT+xkPXAzBFQNgcsXBq/vLNSJO/uEnTIb1/o51wOwX
IwJNP77iY8kzmlxHwfbsAGHkbF3wsLgWXM5lb9i/m0yTo0q0lz4UAWS1rZjC5yVr
ktDl0Ld1F6dkZ9D/mucB23eqtXUMh0HnfPPcgHvnuYi3bBpJch3QOyGMg2Ux4Obt
uHxNpH6C83M/8hlfyT5Y
=2lWu
-----END PGP SIGNATURE-----

6

On 12/03/2012 07:06 PM, JSeymour421 wrote:
> debian based Distro-
> sudo modprobe cpuid

forget sudo for now…that is what Ubuntu and their spins uses to keep
its users from actually becoming root… (as far as i know there is no
such effort in actual Debian.)

so, try this combo


su -
modprobe cpuid

in which “su -” (do not forget the dash) lets you become root, the real
and only root…where you will then see that root can find the
executable modprobe, which sudo cannot.

read more:
http://tinyurl.com/593e4c
http://tinyurl.com/ydbwssh

and, to help you in your transition from “Debian based”, some other
differences between ubuntu and openSUSE, here:
http://tinyurl.com/ubuntu-to-openSUSE
http://tinyurl.com/Ubuntu-Differences

–
dd http://goo.gl/PUjnL
http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software

7

Once again on my pelgrimage against being root: Don’t use “su” or “su -”, use

su -c ' *command ' *

This means that only command is invoked with superuser permissions.

8

On 12/03/2012 11:06 PM, Knurpht wrote:
>
> Once again on my pelgrimage against being root: Don’t use “su” or “su
> -”, use
>
> Code:
> --------------------
> su -c ’ -command ’ -
> --------------------

perhaps you should write a how-to, as did Carl
<http://tinyurl.com/ydbwssh> with your opinion on the ‘best’ way to
exercise administrator/superuser powers…

if you do, i will link to it (as i did both Carl’s and the SDB in my
#6)…that way you won’t have to follow me around and offer your
differing opinion.

in fact, maybe you want to comment in Carl’s thread since


su -c [command]

is mentioned…

–
dd