2.1 on Watchguard x500e problem - sysctl: unknown oid 'dev.cpu.0.freq_levels'
-
Hello,
First of all sorry for my english, I hope you understand me. I read the doc about installing pfsense on a watchguard system. I used the Watchguard x700 for a long time with pfsense. Because I want to use gigabit i changed to x500e. I've done everything as described in the docs and it's running now.
On the first start i configured LAN und WAN (PPPoE but no cable connected at the moment). Then I installed LCDProc-dev and Shellcmd for the LCD and the Armed-LED. After rebooting the firewall stops after "Configuring firewall…...done." and throws the following error in a loop:
sysctl: unknown oid 'dev.cpu.0.freq_levels' sysctl: unknown oid 'dev.cpu.0.freq'
I can access SSH but not the WebGUI (Internal Server error)
I have 2x 1GB RAM installed and the default CPU (SL6N7 1.3GHz Banias Celeron-M).
I found a article in the freebsd forum that i should append
cpufreq_load="YES"
in the loader.conf. Now I can access the webGUI but the firewall also stops after "Configuring firewall…...done."
Has anybody an idea?
Greetings
BJ
-
Okay, I found the reason why this happens:
Under LCDproc -> Screens i checked "Enable CPU Frequency". And with Shellcmd i restart the lcdproc. At the moment where shellcmd restarts lcdproc I get this error messages from above. After unchecking "Enable CPU Frequency" the error is away. But it also hangs after configuring firewall.
I think the problem is that i restart lcdproc with shellcmd. But this is no Problem on my Watchguard x700 (2.1-RELEASE). The reaseon why i want to restart lcdproc is, that there was an problem on starting lcdproc sometimes and i read a article where this fix is described. It works on my x700.
So the problem is the new hardware x500e OR the newer Version 2.1.4-RELEASE.
I deleted the shellcmd command and until now the LCD starts without errors. But how can i get the cpu frequency working?
-
I assume you mean X550e?
Are you running the Nano image from a compact flash card?
Are you seeing that output via the serial console?
Did yoy enable powerd? The original Celeron CPU does not support speedstep so you can't vary the frequency.
I have an x750e (identical hardware) running 2.1.4, it should not be a problem running on your x550e.Steve
-
Yes, sorry I mean x550e.
I updated BIOS and use a 4GB CF-Card. I see this error via the serial console.
No I didn't use powerd.
The problem only appears if I checked "Enable CPU Frequency" in LCDProc. I use LCDProc-dev.
As I wrote on the X700 is everything working fine. Does your LCD show CPU Frequency oder did you change the cpu?
Greetings
BJ
-
No, I have never used the CPU frequency screen in lcdproc. In fact I don't use the lcdproc php client written for pfSense at all because it doesn't really work well with the sdeclcd driver. I use the original lcdproc client which doesn't have a cpu frequency screen. See:
http://forum.pfsense.org/index.php/topic,7920.msg344513.html#msg344513However that still doesn't really explain why your box isn't booting. Did it boot up OK initially?
Steve
-
Hello,
I can reproduce the following.
Bootup stops after "Configuring firewall…...done.":
Reason: I insert the command "/usr/local/etc/rc.d/lcdproc.sh restart" via shellcmd (see https://forum.pfsense.org/index.php?topic=7920.msg410248#msg410248)
Solution: Delete this CommandSecond Problem: A loop of this two lines:
sysctl: unknown oid 'dev.cpu.0.freq_levels' sysctl: unknown oid 'dev.cpu.0.freq'
Reason: I've cheked "Enable CPU Frequency" in LCDProc-dev
Solution: Unchek.Both is no Problem on my X700 (pfsense 2.1-RELEASE). But it is a problem on my x550e (2.1.4-RELEASE).
If nobody has an idea why this two probleam appear, I should try your link.
Thank you.
-
You won't have those OIDs unless you load the cpufreq driver which normally only gets loaded when you enable powerd. You can load it manually as you did before.
Why do you want to see the CPU frequency when it can't change?Steve
-
I tried it with enabling powerd but the problem is the same.
I don't need this function so i disabled this.
-
So everything else is working correctly?
Steve
-
yes.