Baldrick1 wrote:I'd have to guess that it's because visudo isn't working for some reason.
Can you type "sudo visudo"
Then scroll to the bottom of the file and on the last line add: www-data ALL=(ALL) NOPASSWD: ALL
All the reboot button is, is a fancy interface for the command "sudo reboot" so it's nothing complex which makes me think that it's a problem with sudo. I am of course assuming that when you manually type "sudo reboot" into your bash session then it acts as expected?
Hi I just checked the file and it already has the exact entry..
Sorry, I can't imagine what else is wrong then. Still learning this stuff myself. Hopefully someone more knowledgeable will be along before too long
P4d0uch wrote:Hi. i just got my Raspcontrol running and i have one question. It shows that my cpu is running at 697.95 MHz but in config i have 900mhz and i dont know if the config file is wrong or your program is not showing the correct way.
But it is superb program
Thanks for any answer.
Can you run the command "cat /proc/cpuinfo | grep BogoMIPS" and share the results?
I actually have the same issue on mine although I've not taken the time to look into it until now. I *believe* although I have nothing to back this up right now, that it is caused by the new firmware and the CPU scaling that has been implemented.
I need to look into this a lot more, but what leads me to this conclusion is the contents of the files
In my case, the current frequency is being reported as 700000 (default out of the box speed) and
850000 (I chose 850Mhz as my overclock).
This is what makes me think that it is (or at least has the potential) to overclock but will always report 700Mhz in /proc/cpuinfo for some reason.
I need to go back and read more about the CPU scaling before I'm confidant that's where the problem is, but this issue started for me after a firmware upgrade so I think it's likely to be the Pi itself rather than Raspcontrol that's caused it