Firebox LCD Driver for LCDProc

thewizard

Hmmm,
Had you already made the sym links when you installed the driver?
What exactly have you done so far?

Steve

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)

I have navigated to the tmp dir and typed
tar -xvf lcdd.tar
chmod 700 install-embed.lcdd.sh
./install-embed.lcdd.sh
Mount

Navigated to
cd /usr/local/etc/rc.d
type
./lcdd.sh
error
/libexec/ld-elf.co.1: shared object
"libkvm.so.3 not found, requirded by "lcdproc"

Navigate to lib
ln -s libc.so.7 libc.so.6
ln -s libkvm.so.4 libkvm.so.3
error
ln: libkvm.so.3 read-only file system
same for libc

any help would be appreciated

stephenw10

The embedded version of pfsense is mounted read only so to make any changes, like adding sym links, you need to first mount it read-write. Remember to put it back to read only afterwards to preserve your cf card.
This is all detailed on page 2 of this thread and in the docs here:

http://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-write

Steve

thewizard

@stephenw10:

The embedded version of pfsense is mounted read only so to make any changes, like adding sym links, you need to first mount it read-write. Remember to put it back to read only afterwards to preserve your cf card.
This is all detailed on page 2 of this thread and in the docs here:

http://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-write

Steve

thank you for your help Steve - led is now working great

quick question i have set the file system back to read only, when installing apps from the gui will i have to change the card to read / write?

stephenw10

No problem! :D
You shouldn't have to if you're using the gui. From, I think, 1.2.3 onwards the embedded install has switched to bsd nano and can support packages, however not all of them. Only supported packages show up in the gui though as I understand it.

StuartW

Hi,

I have followed all the instrcutions on the various threads and now happily have a working pfsense system running on a firebox x500, complete with working ath0 interface and LCD. Happy days :)

The last thing that would really make this perfect would be if the LCD could display tempurature details from the motherboard. I know this inof is available in the bios, but havent yet seen a way of getting this info out, either on the LCD or on the webGUI.

Any ideas?

Stuart

P.s. At this stage I am yet to see any of the fabeled Wacthdog timeout errors that seem to plague this device, and I've spent a long time configuring to get it how I want it. Not sure why….

stephenw10

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

JeffD

Sorry for the lame Q but I tried searching and cannot find an answer: How do you upload the files to PFSense? TFTP?

wallabybob

@JeffD:

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

StuartW

@wallabybob:

@JeffD:

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

slider_nww

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

how can i get the shell?

stephenw10

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

slider_nww

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?

stephenw10

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

stephenw10

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.

lcdd4.tar.png

slider_nww

hello steve,

that sounds good, but i can´t unpack the file.

error message on box and on windows…

stephenw10

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.

slider_nww

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)

stephenw10

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

jdetmold

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

slider_nww

i have a problem now, without doing anything…

-> still working now

AND:

the lcd-driver works! thx steve :)