Firebox LCD Driver for LCDProc
-
I haven't managed this either. :( Would be nice.
See my thread for using mbmon here.
I think it needs somebody with more coding skills than me (not saying much!) to write an lcdproc client that can take the output of mbmon. I haven't found any other client that can do it.Steve
-
Sorry for the lame Q but I tried searching and cannot find an answer: How do you upload the files to PFSense? TFTP?
-
How do you upload the files to PFSense? TFTP?
Some options:
-
scp from Windows or Linux/Unix
-
From web GUI: Diagnostics -> Command, 3rd option to upload files
-
-
How do you upload the files to PFSense? TFTP?
Some options:
- From web GUI: Diagnostics -> Command, 3rd option to upload files
This was the option I used
-
hello together,
i want so start the install of the driver with die read-write problem.
the user "thewizard" posted last year:
After setting up pfsense i have loaded the web browser and gone to diag, command, and uploaded the lcdd.tar.gz
For a pc via 9 pin serial i have selected option 8 (shell)
but in the console i see the boot screen:
1. Boot pfSense [default]
2. Boot pfSense with ACPI enabled
3. Boot pfSense using USB device
4. Boot pfSense in Safe Mode
5. Boot pfSense in single user mode
6. Boot pfSense with verbose logging
7. Escape to loader prompt
8. Reboothow can i get the shell?
-
That's odd. Is that before the box has booted?
Alternatively you can access a command prompt by using ssh to connect.
Make sure it's enabled in the web interface:
\system\advanced\enable secure shell
Use putty to connect (if you're using Windows).Steve
-
at first the bootloader, then this menu. After booting "booting complete", but not the generelly menu
thx for the idea, i will test this tomorrow.
the lcdriver package "lcdproc" is not needed? only the lcdd.tar.gz?
-
You only need the lcdd tarball, it includes lcdproc along with the firebox lcd driver. However there is a problem with the install script when using 2.0Beta5 (or newer).
Here's a new set of instructions for installing the firebox lcd software that should work with Beta5
Edit: These instructions didn't work. There's a file permissions problem that needs to be fixed.
Steve
-
Edit: This only works correctly under 2.0. To use this file for 1.2.3 you need to add a sym link manually see
here.Here's something that works! ::)
At least it did with yesterdays build (pfSense-2.0-BETA5-1g-i386-20110209-1815) on a completely clean install.
Download the attachment to this message. Rename it lcdd4.tar (remove the .png).
Upload it to your firebox via Diagnostics\Command Prompt\Upload in the web interface. This will put the file in \tmp. Then open a command prompt via serial or shh and:[2.0-BETA5][root@pfSense.localdomain]/root(9): cd /tmp [2.0-BETA5][root@pfSense.localdomain]/tmp(10): tar -xvf lcdd4.tar x ./ x ./lcdd/ x ./install-embed2.lcdd.sh x ./lcdd/drivers/ x ./lcdd/LCDd.conf x ./lcdd/lcdd.sh x ./lcdd/lcdproc x ./lcdd/LCDd x ./lcdd/drivers/curses.so x ./lcdd/drivers/sdeclcd.so [2.0-BETA5][root@pfSense.localdomain]/tmp(11): ./install-embed2.lcdd.sh [2.0-BETA5][root@pfSense.localdomain]/tmp(12): /usr/local/etc/rc.d/lcdd.sh
And your lcd should be working. ;D
Changelog from lcdd3:
Reworked the install script to use rc.conf_mount_rw instead of 'mount -u -w /'.
Included the symlinking in the install script.
Changed the default lcd proc display options to C T U.
Changed the default LCDd.conf to use the front panel buttons correctly for menu access. :)Bugs:
(Xe box only) Having set it to use the buttons correctly I have found that the buttons on the Xe box are wired differently to the other fireboxes. >:( When it starts you'll be left in the menu, just press the left button to escape. The result is no different to when the buttons weren't configured correctly.Although I am using the rc.conf_mount_rw/ro commands in the script there is no need since it appears that (in this build at least) everything is mounted RW by default. Seems odd.
Steve
Edit: Changed the attachment to .png as .txt was corrupt.
-
hello steve,
that sounds good, but i can´t unpack the file.
error message on box and on windows…
-
Hmm, you're right try this.
Obviously rename it lcdd4.tar
I tested it and it untared fine.Steve
Edit: Removed the attachment as it's now on the original post.
-
ich have a problem now:
boot the hdu:
àp x xpxñý ; ñßø ùŸ Ç ˜
EDIT:
don´t forget to go back to read-only mode ::)
(/etc/rc.conf_mount_ro) -
What are you trying to boot from?
Looks like something is corrupt.3 looks like leftover stuff from the original Watchguard OS. pfSense doesn't use lilo.
Steve
-
steve the updated driver looks good im flashing a new cf card and will test it tomorrow morning
Thanks for all the work on the firebox!
-Jeff
-
i have a problem now, without doing anything…
-> still working now
AND:
the lcd-driver works! thx steve :)
-
new driver works great! and the menu looks good 2!
it would be nice to be able to switch the display screens from the menu i like that option even though it dosent work yet -
Is there a way to keep the backlight constantly on?
-
There are settings for the backlight in lcdd.conf. I can't remember off hand but there is setting for the time, you could try setting that very high or 0. Have a look through the file there's probably a setting for disabling the backlight timer. The original driver didn't have it so the light was permanently on.
Steve
-
This is the contents of lcdd.conf:
[server] Driver=pyramid Bind=127.0.0.1 Port=13666 ReportLevel=3 ReportToSyslog=yes WaitTime=5 User=nobody ServerScreen=no Foreground=no DriverPath=/usr/local/lib/lcdproc/ GoodBye="Thanks for using" GoodBye=" pfSense " ToggleRotateKey=Enter PrevScreenKey=Left NextScreenKey=Right ScrollUpKey=Up ScrollDownKey=Down [menu] MenuKey=Escape EnterKey=Enter UpKey=Up DownKey=Down [pyramid] Device=/dev/cuaU0 Size=16x2
Don't see anything related to Backlight. Or am I using an older version?
-
Hmmm, not sure what version you're using but it isn't using the firebox driver (sdeclcd).
The sdeclcd driver has parameters that appear in lcdd.conf:[sdeclcd] BackLight=yes Backlight_Timer=60
How did you install it?
Steve
Edit: I see now that you're using the lcdd2 tarball which is very old now. See my post on the previous page with the lcdd4 attachment.