Firebox LCD Driver for LCDProc
-
Yes, my fault! Sorry :-[
libkvm.so.5 is only in 2.0.
I'm late for a dinner party, I'll edit something later!
Steve
-
Ok, so as pointed out phr0zen above the file lcdd4.tar does not install properly on 1.2.3 since it sets sym links for libkvm.so.5 which doesn't exist in 1.2.3.
If you have installed it and got the error
ln /lib/libkvm.so.4: File Exists
You need to add the sym link manually with the following console commands:
/etc/rc.conf_mount_rw ln -s /lib/libkvm.so.4 /lib/libkvm.so.3 /etc/rc.conf_mount_ro
Now you can start the server and all should be well.
Steve
-
I am having an issue installing the lcdd4.tar. (firebox x700, 1.2.3 embeded installed via live cd, onto HD)
Steps:
1. uploaded the lcdd4.tar via web interface
2. opened console via serial (putty)
3. tar -xvf lcdd4.tar
4. ./install-embed2.lcdd.shI get this:
ln /lib/libkvm.so.4: File Exists
I try to run it anyway with:
/usr/local/etc/rc.d/lcdd.shI get:
/libexec/ld-elf.so.1: Shared object "libkvm.so.3" not found, required by "lcdproc"Can anyone help me?
(btw, this was a fresh install, only thing i did after interface setup was try to install this lccd4.tar)Thanks!
EDIT:
Ok… so I think I figured it out. Got it working at least.
I had to edit the install-embed.lcdd.sh. It looked like it was creating the wrong symlinks for 1.2.3 (gathered from other posts). Here is what I edited it to:#!/bin/csh /etc/rc.conf_mount_rw cp -R lcdd /usr/local/share/ cp /usr/local/share/lcdd/lcdd.sh /usr/local/etc/rc.d/ chown -R root:wheel /usr/local/share/lcdd chmod -R ugo=rX /usr/local/share/lcdd chown root:wheel /usr/local/etc/rc.d/lcdd.sh chmod ugo=rx /usr/local/etc/rc.d/lcdd.sh ln -s /lib/libc.so.7 /lib/libc.so.6 ln -s /lib/libkvm.so.4 /lib/libkvm.so.3 /etc/rc.conf_mount_ro
phr0zen & steve…
Ok - so if I run the 4.tar with the original syntax and then clean up with your (phr0zen) instructions will that get this to work? I just hate to hose my HD install of the 1.2.3 imbedded. I just finished up cleaning up the 3 fans and added a quiet coolermaster with a modded heat sync. I also fell into the perfect drive sled that works with the 2.5laptop drive. I made the decision to close the case - but this may be too soon if this next attempt at the CLI does not get the lcd working... Thanks for all your help here...
H. -
Ok, so as pointed out phr0zen above the file lcdd4.tar does not install properly on 1.2.3 since it sets sym links for libkvm.so.5 which doesn't exist in 1.2.3.
If you have installed it and got the error
ln /lib/libkvm.so.4: File Exists
You need to add the sym link manually with the following console commands:
/etc/rc.conf_mount_rw ln -s /lib/libkvm.so.4 /lib/libkvm.so.3 /etc/rc.conf_mount_ro
Now you can start the server and all should be well.
Steve
Steve - Ok - I read this twice and I am ready to jump in again on the CLI…
I will expect the error and move on with your instructions here...
Thanks for the efforts here and hoping to put this project together and start building the firewall rules. Will update tomorrow and let you know how things are going ....
Thx & Best Regards...
H.
BTW - I took off Friday and on Admin at work asked if I stayed home on Friday to watch the wedding but my reply was something like beer and fishing were the order of the day. Her reply was "In the name of the wedding I presume" :) -
Here in London it was pretty crazy! ::)
National day off was nice though. :)
Steve
-
Here in London it was pretty crazy! ::)
National day off was nice though. :)
Steve
There ya go - Niiiccce…
That crowd was huge!Well, I tried and now consider myself Linux challenged... Must have been the beer and fishing on Friday..
Tar'd the version 4 and got no error? but continued and ran rw on the system and tried the edit. I think I need to edit the install-embed.lcdd.sh following phr0zen's syntax - I can see it try and load but no joy... -
Editing the script should definitely work. But I would expect it to simply need the extra sym link. :-
What error does it give when it tries to load?When you ran the install script it didn't give an error? Weird!
Steve
-
Editing the script should definitely work. But I would expect it to simply need the extra sym link. :-
What error does it give when it tries to load?When you ran the install script it didn't give an error? Weird!
Steve
Steve…
No Error...
I am going to build out another 2 version ISO and write another drive...
I got the error the first time on the 1.2.3 and rebuilt 1.2.3 drive again as I think it changes the system boot so I started over. I think you mentioned it messes with the imbedded RO.When I build the hard drive & use my current 2 version ISO it never gets to the last menu when it boots so I am going to download 2 again and rebuild the ISO again and try that... It would be great to get the LCD going but it is not a show stopper but I am willing to try and figure out how to do this. - Like you said - It isn't that hard.... :)
-
I am going to throw this out there - (sameless lack of effort) ::)
Anyone have a .gho or acronis image??
I am burning the 2.0 RC1 now but was just wondering? -
Hi…
When you build 2.0 imbedded - it boots and does not go to the last menu nor does it allow you to setup the LAN addressing? Is that normal?
I am rebuilding my 1.2.3 and going after this again - Thanks everyone for your help...
Getting back to Linux after a few years is a challange but things are slowly coming back and I think this is a good exercise for me - If I start whining to much just give me a snickers bar and I will be ok...Regards;
H.
-
Hmm,
There seem to several people having that problem, check the x700 thread.
It seems to have started around 2.0Beta5.
One solution is to install 1.2.3 and then upgrade. Not a nice or long term solution if you ask me.
I don't actually have an x-core box so I haven't experienced it.pfSense is BSD not linux. Just different enough to catch you out! ::)
Steve
-
Wow - I started this and did not even pay attention - I thought FreeBSD was Linux - my bad….
Thanks for a eye opener Steve... After reading about FreeBSD I can see why pfsense is built on this os.... and I am glad I am on this path now.I rebuilt the drive on 1.2.3 and will try the upgrade path and go through the thread again... When I look at the syntax and try to apply it some of the paths do not exist after the upgrade attempt??! Or my input is incorrect...
H.
edit - Update - All due to a hard drive that did not work with the 2.0 version - For some reason the in-place upgrade did not like the /mbr signature on the harddrive! -
Steve…
Thanks again - the lcd setup worked like a charm on the second x700! ;D
This time I applied the correct syntax and the LCD started right up without a reboot...!Regards;
H.
-
I just purchased a Firebox X8000 from ebay. I was wondering if the LDCProc driver works on all of the LCD displays or only the X Core line?
-
It will work fine on the X8000. I installed it on my X6000 just yesterday on 2.0RC2.
Steve
-
Been piddling with my x500, and the results are promising as far as the buttons, I've used lcdexec from the LCDproc package and gotten the menus working. I've only thus far created 2 functions, 1 is to Reboot, the other is to Reset the admin passwd….(would want to be careful with the 2nd one!) :) Will keep poking around with this and post back soon :)
-Andy
Andrew Miffleton
Telecommunications Technician
DFW Business Telephones, Inc.
1260 Shiloh Rd.
Plano, TX 75074
(972)424-4242 x455 -
Sounds like good work. :)
Steve
-
Thats awesome!
Been piddling with my x500, and the results are promising as far as the buttons, I've used lcdexec from the LCDproc package and gotten the menus working. I've only thus far created 2 functions, 1 is to Reboot, the other is to Reset the admin passwd….(would want to be careful with the 2nd one!) :) Will keep poking around with this and post back soon :)
-Andy
Andrew Miffleton
Telecommunications Technician
DFW Business Telephones, Inc.
1260 Shiloh Rd.
Plano, TX 75074
(972)424-4242 x455 -
Been piddling with my x500, and the results are promising as far as the buttons, I've used lcdexec from the LCDproc package and gotten the menus working. I've only thus far created 2 functions, 1 is to Reboot, the other is to Reset the admin passwd….(would want to be careful with the 2nd one!) :) Will keep poking around with this and post back soon :)
-Andy
Andrew Miffleton
Telecommunications Technician
DFW Business Telephones, Inc.
1260 Shiloh Rd.
Plano, TX 75074
(972)424-4242 x455dfwbt…
Steve's shell script works fine for what I need. Just having it run with the domain name, uptime and processor info is enough, plus the LCD script will run once the system has started correctly so for me this is enough... The backlight turning off at first was bugging me but thinking about it the backlight only needs to run when you push the right button just to check the uptime and make sure it appears to be running correctly. I can tell you if his script does not run then you know there is an issue with the box and the FreeBSD/pfSense boot process.I am deploying my first x7000 build this Saturday and having the LCD run when running at a customers location is just one more valuable piece to modding the Watchguard boxes for small business use. Your customer can at least look at the green light (steve's script) and take a look at the uptime on the LCD while they are on the phone with you. I am not setting up remote management as I consider this a potential security issue and would like to keep everything locked down as much as possible. I have a backup drive I am leaving with the customer with the complete build in the event there is some issue which will allow a quick repair in the event something goes wrong... (FreeBSD go Wrong?? NOT ;) )
H.
-
Has anybody written a package yet that will run the LCD installation. I have done it by hand several times and it works about half the time.
I ready to see a package. I just gotten a x6000. It should be here next week.
RC -
No proper package (yet) but this will work every time on 2.0.
Steve
-
stephenw10,
I just installed the lcdd4 on x500. The LCD is working great. I can't see it. The backlight does not appear to be on or is too dimm. I did fire the x500 up with the orginal operating system and the backlight does work.
RC -
The backlight is supposed to go off after a set time to save the backlight, which has a limited life, and power.
If you press one of the buttons it should come back on.Steve
-
It does not come on at all. Any thoughts, I look at the settings on the LCD and see if I can do anything with it.
RC -
I don't remember how to change the write mode to the flash card. Can any one refresh my memory so I can install the LCD driver.
RC -
Are you installing 1.2.3 or 2.0?
The install script should take care of it but lcdd4.tar only works for 2.0 without some editing.
Here's what your looking for:
http://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-writeSteve
-
I have the LCD working no issues. The backlight is not working. I know that it works when I put the orginal boot flash card in. Any thoughts on why it is not working?
RC -
No ideas at the moment. Is it a clean install?
The backlight is controlled directly by a single bit on one of the parallel port registers. Have you changed any of the bios settings? Perhaps the way FreeBSD accesses the hardware is slightly different to Linux (the Watchguard OS).
Some body else here who's backlight had broken suggested using a usb powered internal LED. It should work but will require some modification to the panel to allow the light in.Steve
-
It is not a clean installation. It is the one I have been running. It was installed in 1.2.3 before I did the upgrade.
RC -
dfwbt,
I would be very interested in you script for the functions of the buttons. That seems to put the finishing touches on what everyone has done here. I have been very busy testing with my x500 prior to my x6000 getting here. I am really looking forward to the upgrade. I just got a ide hard drive and I am going to order a adapter adapter so I can use the carrier in the x6000 to do a full install. I been making notes so I can replicate the lcd installation and the arm light change.I love to add you reboot script to that list of things that I have got planned for the x6000. I did get my bridging working with all ports on the x500. I retired a switch I was using to eliminate the extra power used here at home. I added all the ports to the bridge and set the source to any under each port and everything just started working. I test and only see about a 5% increase in CPU utilization. My x500 runs at 2-5% utilization so 5-7% utilization is no big deal. I have a total of 12 devices on my home network right now, and that is the smallest it has been in 15 years.
RC -
I just re-read my own write up on the led and found where I referenced the backlight.
It's controlled directly by the parallel I/O registers as I said: IO address 0x379 bit 1.
You can try turning it on and off manually using this program I wrote. This program has no error/sanity checking so use it carefully! ::)
Upload it to your box. chmod it to 0755. Kill lcdd so it's not trying to write to same address then:./writeio 0x379 0x01
This should turn it on.
./writeio 0x379 0x00
Should turn it off again.
It's probably a problem with the upgrade though. You would be better to do a clean install.
Do the buttons work at all?Steve
-
I can't get the writeio to execute. I guess I need to execute the sudo command, is that right?
RC -
Did you chmod it?
chmod 0755 writeio
Are you logged in as root?
There is no sudo command.
Steve
-
Whch Driver do I need to use for the LCD on the x6000? LCDPROC or the one stephenw10 has written. I did a upgrade to the latest version last night and realized that the LCD stopped working after the upgrade was done.
I am having to use the 2GB nano version because the 4GB nano release will not fit on my flash drive.
RC
-
Use the firebox script, lcdd4. Unfortunately because it isn't a proper pfSense package, yet, it doesn't survive an update.
2GB image is fine, I'm using the 1GB image on a 4GB card.
Steve
-
Hey Steve! It's been awhile hope your well.
Got a question for you, I made the mistake of finding the lcdd3.tar file before I noticed this post with lcdd4.tar, is the file system mounting restored on reboot or should I reinstall after using lcdd3? I noticed after reboot it's writable and not sure if it should be. lcdd3.tar is what I used and on a X700
Thanks a bunch!
-
Which version of pfSense are you running?
There is a bug in current 2.0 snapshots (unless it's been fixed while I wasn't looking!) that leaves the filesystem mounted read-write. It's not really a problem or anything to worry about.
The lcdd3 script used the mount command directly which is not the correct way to do it in recent versions. This combined with the bug can leave the filesystem mounted read-only with no way to remount it RW. This means that you can't save changes, add packages etc.
If you used lcdd3 and you're running 2.0Beta5 or newer you may have a problem.
Steve
-
Which version of pfSense are you running?
There is a bug in current 2.0 snapshots (unless it's been fixed while I wasn't looking!) that leaves the filesystem mounted read-write. It's not really a problem or anything to worry about.
The lcdd3 script used the mount command directly which is not the correct way to do it in recent versions. This combined with the bug can leave the filesystem mounted read-only with no way to remount it RW. This means that you can't save changes, add packages etc.
If you used lcdd3 and you're running 2.0Beta5 or newer you may have a problem.
Steve
Thank you for the reply Steve! You're always a big help.
I installed lcdd3 on a 2.0-RC1 system and just updated yesterday with a current snapshot. It would not be a problem for this system to be reinstalled because it's not live yet and I have a backup config. I just need to make sure this system is stable so it would definetely be worth the extra work to re-do it and install the lcdd4 instead. What do you think?
This script is terrific, thank you for this and to everyone else who worked on it
-
Hmm, well that's the exact set of things that I would expect to cause a problem. Perhaps the bug has been fixed?
Anyway if it's not a problem I would reflash and use lcdd4 to be sure.Steve
Edit: Doesn't seem to have been fixed, not deliberately anyway! http://redmine.pfsense.org/issues/1279
-
Hmm, well that's the exact set of things that I would expect to cause a problem. Perhaps the bug has been fixed?
Anyway if it's not a problem I would reflash and use lcdd4 to be sure.Steve
Edit: Doesn't seem to have been fixed, not deliberately anyway! http://redmine.pfsense.org/issues/1279
After all of my config experiments yesterday, I got the reflashing process down fast! no problem at all. Thanks for the help Steve and enjoy your weekend.