Firebox LCD Driver for LCDProc
-
I manage a ton of XTMs with actual watchguard software I assure you the backlight stays on 24/7
it's lcdproc that turns it off in the driver
That's true, it's the driver that turns off the back light and not the BIOS.
It would not be that hard to recompile the driver with the timer edited out if you really need that. I personally prefer it going out. If I see the LCD is lit that means the driver has crashed out for some reason.
Steve
You guys where 100% right.
I never used these boxes with the Watchguard software, only for a powerup test after receiving it for verifying
if the listed modelnr corresponds with the seller information.
Besides that, these boxes where immediately converted to pfSense, and that's why i never saw the LCD screens keeps on. ::)Grtz
DeLorean -
OK, so… if it's the driver... is there a way to include a command to NOT turn it off or to change the timer value? Perhaps being able to set it to zero to keep it on, or to a number of seconds before it shuts off.
-
It would be nice if the option to keep on the LCD screen under settings was working.
So that you can decide if the LCD screen backlight must be kept on or off.Grtz
DeLorean -
That's true. Since there are options set in the settings interface for LCDProc, I wonder if there isn't some way for the file to disregard it's internal clock for killing the backlight and just allow the settings to override it.
Where is the latest code source for the program? I don't know if I can properly write the changes, but I'll try.
-
Go to the source! ;D
http://lcdproc.cvs.sourceforge.net/viewvc/lcdproc/lcdproc/server/drivers/sdeclcd.c?view=markup
But yeah a code revision to enable or disable the backlight timer from the driver config would be appreciated by many. There can;t be that many people running the original X-Core models now.
Steve
-
It's here, now: https://github.com/lcdproc/lcdproc
So, this backlight timeout is only useful for the old X-Core boxes? What about the X-Core-e (x550e, x750e)? X-Peak?
-
The X-Peak may have a limited life but the display is different hardware. My X-Peak died of bad caps a while back anyway.
The X-e and newer models are all led backlight I believe so no problems.
I would not want to have it on all the time personally but a choice to do so seems reasonable.
Steve
-
–EDITED POST--
This might be the wrong way to disable the backlight off toggle because I am not a driver coder, but I have edited/compiled a sdeclcd.so that has "no timeout" on FreeBSD 10.3 (32 bit and 64 bit) and FreeBSD 11.1 (64 bit) virtual machines
So far the 32 bit works great on my X750e and the 64 bit works on XTM5 according to networkBob
Here's how I proceeded (from scratch on a new install of FreeBSD)
pkg install automake autoconf gcc git nano cd ~ git clone http://github.com/lcdproc/lcdproc cd lcdproc nano server/drivers/sdeclcd.c ----- change BACKLIGHT_OFF to BACKLIGHT_ON on lines 650 and 676 then save CTRL-X, Y, ENTER sh ./autogen.sh ./configure --enable-drivers=sdeclcd make server
This will generate ~/lcdproc/server/drivers/sdeclcd.so which you can copy somewhere in order to download it to your pfSense box by FTP or whatever method you prefer.
If you don't want to compile it yourself, you can grab the ones I have compiled at the following links or as an attachment to this post
pfSense 2.3 (FreeBSD 10.3)
- 32 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.32bit.zip
- 64 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.64bit.zip
pfSense 2.4 (FreeBSD 11.1)
- 64 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.freebsd11.zip
- 32 bit version : none, pfSense has no 32 bit release since 2.4
You need to extract the zip file's content and move it it /usr/local/lib/lcdproc/
Then make sure that you run "chmod +x sdeclcd.so" to make it executableFeel free to edit my post if the method I haved used is not the proper way to bypass that timeout in the driver.
sdeclcd.so.64bit.zip
sdeclcd.so.32bit.zip
sdeclcd.so.64bit.freebsd11.zip -
I am not a driver coder, this might be the wrong way, but I have compiled a sdeclcd.so that has "no timeout" on a i386 FreeBSD 10.3 virtual machine.
So far it works great on my x750e.
All I did was edit "sdeclcd.c" and replace "BACKLIGHT_OFF" to "BACKLIGHT_ON" on lines 650 and 676
Hope this works for you
You can grab it here : http://www.vizi0n.com/watchguard/sdeclcd.so or as an attachment to this post
Feel free to edit my post if the method I haved used is not the proper way to remove that timeout.
That made LCDProc fail on startup. If I went into the services status, it showed LCDproc not started, and when I tried to start, it just failed.
Error in the system log: Could not open driver module /usr/local/lib/lcdproc/sdeclcd.so: /usr/local/lib/lcdproc/sdeclcd.so: unsupported file layout
But I'm happy that you tried! Thank you for that.
-
On 32bit? ;)
-
I am not a driver coder, this might be the wrong way, but I have compiled a sdeclcd.so that has "no timeout" on a i386 FreeBSD 10.3 virtual machine.
So far it works great on my x750e.
All I did was edit "sdeclcd.c" and replace "BACKLIGHT_OFF" to "BACKLIGHT_ON" on lines 650 and 676
Hope this works for you
You can grab it here : http://www.vizi0n.com/watchguard/sdeclcd.so or as an attachment to this post
Feel free to edit my post if the method I haved used is not the proper way to remove that timeout.
Thank you so much for the effort, vizi0n. However, this did not work on my 64-bit XTM515 box.
As noted by dhoffman98, LCDproc failed to start after replacing the release sdeclcd.so file with your modified version. Maybe it has to do with the 64-bit architecture vs 32-bit. I do not possess the required knowledge to know.
I tried messing around with online C compilers but got super frustrated trying to find a way to compile to a .so file. It seems to me that eliminating the timeout would be more complicated than, say, increasing the timeout from 30 seconds to 300,000 seconds, although that would add a tiny amount of processor overhead.
-
Yes, you need a 64bit driver to run in 64bit. That error is what you see when you try to load a 32bit driver.
Steve
-
Yes this driver is for 32 bit, I can recompile it for 64 bit later tonight for you fancy 64 bit folks :P
-
I have updated my previous post with both drivers as separate attachments
32 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.32bit.zip
64 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.64bit.zipPlease confirm if the 64 bit works as I have no way to test it. Also make sure that you run "chmod +x sdeclcd.so" to make it executable
-
Thank you, vizi0n. That worked on my XTM515 box (running 2.3.4 amd64)! Now the backlight stays on! I am happy and frankly kinda giddy. I appreciate your help.
Cheers
-
Thank you, vizi0n. That worked on my XTM515 box (running 2.3.4 amd64)! Now the backlight stays on! I am happy and frankly kinda giddy. I appreciate your help.
Cheers
You're welcome
-
hi guys ,
offtopic :any lcd recomend for work with pfsense ?
thanks .
-
I have updated my previous post with both drivers as separate attachments
32 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.32bit.zip
64 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.64bit.zipPlease confirm if the 64 bit works as I have no way to test it. Also make sure that you run "chmod +x sdeclcd.so" to make it executable
I apologize in advance if this is a stupid question. I opened the file "sdeclcd.so.64bit.zip" and noticed the "__MACOSX" folder. I don't have a Mac.
-
I don't have a Mac.
I do haha. Sorry, I did not notice that it had added this folder. I thought I had zipped it on my VM. You only need the .so file inside the zip
EDIT: I have updated both zip files to remove the __MACOSX folder
-
Thank you, vizi0n. That worked on my XTM515 box (running 2.3.4 amd64)! Now the backlight stays on! I am happy and frankly kinda giddy. I appreciate your help.
Cheers
Hi, How did you manage to get pfsense loaded on your XTM 515? I have a XTM 535 and want to load pfsense, but no write up is available. From what I understand 515 and 535 have the same internals, only software locked by watchguard.
-
Replied in the XTM 5 thread.
Please don't double post. This thread is specifically for questions about the LCD driver. And it's included upstream in LCDproc now anyway.
Steve
-
I have updated my previous post with both drivers as separate attachments
32 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.32bit.zip
64 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.64bit.zipPlease confirm if the 64 bit works as I have no way to test it. Also make sure that you run "chmod +x sdeclcd.so" to make it executable
Oh dang the backlight turns off now after pfSense 2.4.1 update. Any ideas? Could this be a file signing issue?
Cheers
-
I have updated my previous post with both drivers as separate attachments
32 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.32bit.zip
64 bit version : http://www.vizi0n.com/watchguard/sdeclcd.so.64bit.zipPlease confirm if the 64 bit works as I have no way to test it. Also make sure that you run "chmod +x sdeclcd.so" to make it executable
Oh dang the backlight turns off now after pfSense 2.4.1 update. Any ideas? Could this be a file signing issue?
Cheers
Even after reuploading the file?
32-bit support has been deprecated and removed – There are no images available for 32-bit (x86/i386) Intel architecture systems
Awww its the end for the updates on my x750e :(
-
Yes, I tried that. I also tried:
1. deleting the sdeclcd.so file and replacing with fresh downloaded copy
2. uninstalling LCDProc package and reinstalling
3. rebootingMaybe I missed something, or maybe 2.4.1 added a file signing feature for security? I'll keep trying…
-
Aaah 2.4 is using FreeBSD 11, mine were compiled on 10.3
I will create new ones
-
Can you try this one ?
http://vizi0n.com/watchguard/sdeclcd.so.freebsd11.zip
-
Thank you so much, Vizi0n. I can confirm that your new file works on pfSense 2.4.1. This new modified LCDproc sdecled.so file keeps the LCD backlight powered on forever. These are the steps I used:
1) stop the LCDproc service
2) open console shell
3) mv /usr/local/lib/lcdproc/sdeclcd.so /usr/local/lib/lcdproc/sdeclcd.so.bak
4) fetch http://vizi0n.com/watchguard/sdeclcd.so.freebsd11.zip
5) unzip sdeclcd.so.freebsd11.zip
6) cp sdeclcd.so /usr/local/lib/lcdproc
7) chmod +x sdeclcd.soCheers
-
Thank you so much, Vizi0n. I can confirm that your new file works on pfSense 2.4.1. This new modified LCDproc sdecled.so file keeps the LCD backlight powered on forever.
You're welcome!
I have updated my previous post with the download links and attachments
-
Hi,
ich have a little Problem.
I'm not able to install LCD Proc.
Any time i tryed to install it on the WebGUI there are some fails:>>> Installing pfSense-pkg-LCDproc... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: pfSense-pkg-LCDproc: 0.10.5 [pfSense] lcdproc: 0.5.7_2 [pfSense] Number of packages to be installed: 2 The process will require 1 MiB more space. [1/2] Installing lcdproc-0.5.7_2... [1/2] Extracting lcdproc-0.5.7_2: . pkg-static: Fail to create temporary file: /usr/local/lib/lcdproc/.CFontz.so.70EQSoDb3VPJ:Not a directory [1/2] Extracting lcdproc-0.5.7_2... done Failed
My System is a XTM 510
with 2.4.3-RELEASE (amd64)Anybody able to help me?
Thanks in advance
-
Hmm, not seeing that here.
>>> Installing pfSense-pkg-LCDproc... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: pfSense-pkg-LCDproc: 0.10.5 [pfSense] lcdproc: 0.5.7_2 [pfSense] Number of packages to be installed: 2 The process will require 1 MiB more space. 253 KiB to be downloaded. [1/1] Fetching lcdproc-0.5.7_2.txz: .......... done Checking integrity... done (0 conflicting) [1/2] Installing lcdproc-0.5.7_2... [1/2] Extracting lcdproc-0.5.7_2: .......... done [2/2] Installing pfSense-pkg-LCDproc-0.10.5... [2/2] Extracting pfSense-pkg-LCDproc-0.10.5: ......... done Saving updated package information... done. Loading package configuration... done. Configuring package components... Loading package instructions... Custom commands... Executing custom_php_resync_config_command()...done. Menu items... done. Services... done. Writing configuration... done. Message from lcdproc-0.5.7_2: ============================================================== The default configuration files have been installed as /usr/local/etc/LCDd.conf.sample /usr/local/etc/lcdproc.conf.sample /usr/local/etc/lcdexec.conf.sample Copy and edit them as needed. ============================================================== >>> Cleaning up cache... done. Success
You have any other packages installed? Low drive space?
That looks like a general LCDproc issue though. Better to ask here:
https://forum.pfsense.org/index.php?topic=44034.0Or maybe in the packages section generally.
Steve
-
Hi, I have newly installed pfsense to my watchguard xtm5 series hardware via cf, installed to 500gb HDD. I have downloaded the lcdproc package from the package manager however I cannot get the display to work. The service won't start and if it does it reverts to defaults and the display just shows the bios version and nothing more,as it did before lcdproc package was installed. My understanding is you need to manually configure files. I am happy to do this but am not sure where to go, what files to modify and how to modify them.
Any assistance appreciated -
You should be able to use the package settings directly. The previous issues have mostly been eliminated with a recent round of bug fixes. Be sure to set some screens on the second tab or it won't start. So:
And then something like:
Steve
-
@stephenw10 hi, I have done this exactly but the settings revert back to defaults and the service won't start
-
Hmm, the package actually reverts to the default settings immediately?
If you check the config file directly (/conf/confg.xml) so you see the correct settings there?
<lcdproc> <config> <enable>yes</enable> <comport>lpt1</comport> <size>20x2</size> <driver>sdeclcd</driver> <connection_type>lcd2usb</connection_type> <refresh_frequency>5</refresh_frequency> <port_speed>0</port_speed> <brightness>-1</brightness> <offbrightness>-1</offbrightness> <contrast>-1</contrast> <backlight>default</backlight> <outputleds>yes</outputleds> <mtxorb_type>lcd</mtxorb_type> <mtxorb_adjustable_backlight>yes</mtxorb_adjustable_backlight> </config> </lcdproc> <lcdprocscreens> <config> <scr_version></scr_version> <scr_time>yes</scr_time> <scr_uptime>yes</scr_uptime> <scr_hostname></scr_hostname> <scr_system></scr_system> <scr_disk></scr_disk> <scr_load>yes</scr_load> <scr_states></scr_states> <scr_carp></scr_carp> <scr_ipsec></scr_ipsec> <scr_slbd></scr_slbd> <scr_interfaces></scr_interfaces> <scr_mbuf></scr_mbuf> <scr_cpufrequency>yes</scr_cpufrequency> <scr_traffic></scr_traffic> <scr_traffic_interface>wan</scr_traffic_interface> <scr_top_interfaces_by_bps></scr_top_interfaces_by_bps> <scr_top_interfaces_by_total_bytes></scr_top_interfaces_by_total_bytes> <scr_top_interfaces_by_bytes_today></scr_top_interfaces_by_bytes_today> <scr_traffic_by_address></scr_traffic_by_address> <scr_traffic_by_address_if>wan</scr_traffic_by_address_if> <scr_traffic_by_address_sort>in</scr_traffic_by_address_sort> <scr_traffic_by_address_filter>local</scr_traffic_by_address_filter> <scr_traffic_by_address_hostipformat>descr</scr_traffic_by_address_hostipformat> </config> </lcdprocscreens>
The SDEC driver ignores a lot of those settings, some of them look incorrect there but are just not set.
Steve
-
@stephenw10 hi I can't show you what mine says as I don't know how to copy the text in. It's unable to post it as thinks it's spam.
Mine doesn't show what yours shows. -
-
Hmm, so simply not saving the config. Are you able to make other changes there? Is it possible the user you're using has 'config deny write' set? Try using the admin user if you're not.
Do you see any errors in the system log when you try to enable the LCD?
Steve
-
I am logged in as admin. I'll check the logs..
-
@stephenw10 im sorry, where are the logs? still very new to this.
-
In Status > System Logs > System / General tab.
If there is some issue saving the package settings I would expect to see something logged there when you try.
Steve