Firebox LCD Driver for LCDProc

fmertz

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?

stephenw10

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

vizi0n

–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 executable

Feel 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

dhoffman98

@vizi0n:

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.

stephenw10

On 32bit? ;)

networkBob

@vizi0n:

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.

stephenw10

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

vizi0n

Yes this driver is for 32 bit, I can recompile it for 64 bit later tonight for you fancy 64 bit folks :P

vizi0n

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.zip

Please 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

networkBob

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

vizi0n

@networkBob:

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

whitexp

hi guys ,
offtopic :

any lcd recomend for work with pfsense ?

thanks .

StlCardsFanJR

@vizi0n:

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.zip

Please 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.

vizi0n

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

maksimred

@networkBob:

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.

stephenw10

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

networkBob

@vizi0n:

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.zip

Please 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

vizi0n

@networkBob:

@vizi0n:

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.zip

Please 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 :(

networkBob

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. rebooting

Maybe I missed something, or maybe 2.4.1 added a file signing feature for security? I'll keep trying…

vizi0n

Aaah 2.4 is using FreeBSD 11, mine were compiled on 10.3

I will create new ones