LCDProc package update



  • Hello,
      as I understood LCDProc in Freebsd is still version 0.5.3, while I would need 0.5.4 to get my LCD panel to work (http://www.sureelectronics.net/goods.php?id=964)…

    To bypass the problem I compiled the driver myself and I add it to every update I do on my routers... also I was modifying the package in order to add a lot of new features (corrected bugs, added support for 4 lines panels, added more "screens", and so on). The changes have been tested for months until now.

    I was asking the commit of my git clone in order to implement the changes I did in the main project, but the mantainer of the package is unreachable (the email address does not exist anymore), and I got no other reference for this...

    I know that until now there was a lot of more important things to fix on pfSense 2.0, but can someone help me please?

    Thanks a lot,
    Michele



  • I can't help but I hope cmb and jimp can. I noticed the updates you did a few months and manually edited them to my files. I can confirm they do work. I do like the MBUF Usage screen. If they are able help, do you think you could add a driver, lib (i386 and amd64) and some code so this driver can work? Its for a picolcd display. I dont know how to create a patch file but can upload them on my dropbox for you to look at if you have time.

    Thanks,

    Stephen



  • @Cino:

    I can't help but I hope cmb and jimp can. I noticed the updates you did a few months and manually edited them to my files. I can confirm they do work. I do like the MBUF Usage screen. If they are able help, do you think you could add a driver, lib (i386 and amd64) and some code so this driver can work? Its for a picolcd display. I dont know how to create a patch file but can upload them on my dropbox for you to look at if you have time.

    Thanks,

    Stephen

    hehe, thanks Stephen, I am glad someone used it…

    Unfortunately I can only add x86 drivers, I am a very newbye in FreeBSD and I was only able to set up a x86 virtual machine in order to compile LCDProc... I was already adding the SureElec.so driver in the package xml and uploading next to another driver that has been distributed in the same way...
    If you want I can recompile including also the picolcd driver and include it in the package or send it to you, but only for x86 unfortunately...



  • Yeah,if you can add the piclocd driver, that would be great!! Include it in the package. I currently have both the i386(i use this) and the amd64 driver(compiled myself). I was going to use amd64 but found some bugs of another package I use so i went back to i386.. I feel I will probably stay with i386 for a while.

    For the past year, every time I would do a firmware update; I would copy over my hacked copies of php/xml to get lcdproc to work with lcdproc.. The driver at least never gets removed :-) It did once when i manually add 0.5.4 to the system but I created a quick update script to copy the files back.

    I don't know much about the the backend of the pfsense packaging system but once you update the xmls, does it compile everything on their servers or do you have update pre-compile binaries?



  • Hi,
    well, I don't know that too, I was adding my "already compiled" driver, so I don't know exactly how the pfSense compiling procedure works…

    Tomorrow I will compile the driver at the office for the x86 architecture (where I have the vm) and I will update the xml, then I will post it on a reply on this message. I can't test if the driver works because I don't have that lcd panel, so I will wait for your feedback before posting them to the git archive, ok?

    Have a nice evening,
    Michele



  • @mdima:

    Hi,
    well, I don't know that too, I was adding my "already compiled" driver, so I don't know exactly how the pfSense compiling procedure works…

    Tomorrow I will compile the driver at the office for the x86 architecture (where I have the vm) and I will update the xml, then I will post it on a reply on this message. I can't test if the driver works because I don't have that lcd panel, so I will wait for your feedback before posting them to the git archive, ok?

    Have a nice evening,
    Michele

    Works for me :-) I check the git archive almost everyday when i'm at work. Oh, btw, are you using the new site? github? I remember coping your code from the old git site. You have a nice evening also.



  • i was checking my notes and there is another file that needs to be uploaded for the display to work. After it compiles the picolcd.so driver, can you also upload /usr/local/lib/libusb.so.2? This lib is needed for picolcd.so to work.

    I also had to add references so i can pick the Com Port. I added this to lcdproc.xml, lcdproc.inc:
    ugen0.2(/dev/ugen0.2)
    ugen1.2(/dev/ugen1.2)
    ugen2.2(/dec/ugen2.2)

    and added after "case "bayrad":" in lcdproc.inc

    
    				case "picolcd":
    					$config_text .= "[{$lcdproc_config['driver']}]\n";
    					$config_text .= "driverpath=/usr/local/lib/lcdproc/\n";
    					$config_text .= "Device={$realport}\n";
    					$config_text .= "Size={$lcdproc_config['size']}\n";
    					$config_text .= "KeyTimeout=500\n";
    					$config_text .= "Brightness=1000\n";
    					$config_text .= "Blacklight_Timer=60\n";
    					$config_text .= "Contrast=1000\n";
    					$config_text .= "Keylights=on\n";
    					$config_text .= "Key0Light=on\n";
    					$config_text .= "Key1Light=off\n";
    					$config_text .= "Key2Light=off\n";
    					$config_text .= "Key3Light=off\n";
    					$config_text .= "Key4Light=off\n";
    					$config_text .= "Key5Light=off\n";
    					break;
    
    

    I just checked my box and I have it configured to use ugen2.2. When I ran usbconfig on the box, its on ugen0.2. Doesn't make sense but it works.

    Here is a copy of all the files that i copy over after installing the lcdproc package if you want to reference:

    http://dl.dropbox.com/u/11597356/pfSense/lcdpro files/lcdproc-picolcd.tar.gz


  • Netgate Administrator

    @Cino:

    I don't know much about the the backend of the pfsense packaging system but once you update the xmls, does it compile everything on their servers or do you have update pre-compile binaries?

    That's not how the package system works. It's independent of the pfSense build system. It's up to the package maintainer to keep it working if something big is changed in pfSense. There's quite a lot of good infomation over in the dev wiki but it's a bit spread out. I've been trying to assimilate it over the past few months!  ::)
    Mostly the package system gives you an easy way to have a nice GUI for your package that's all tied in with the main pfSense GUI. It also handles installing and uninstalling the package and reinstalling after a firmware update.

    @mdima, I'm interested in the exact syntax you have used for compiling the driver for lcdproc as I've been struggling to do the same for some time.  :-\

    Steve



  • Thanks Steve! I've done some reading also and not there yet to create my own.

    @mdima Take a look here, looks like you need to open a ticket http://forum.pfsense.org/index.php/topic,25519.msg132491.html#msg132491



  • @stephenw10:

    @mdima, I'm interested in the exact syntax you have used for compiling the driver for lcdproc as I've been struggling to do the same for some time.  :-\

    Steve

    Hi, I was using the syntax I got from the instructions, with the parameter –enable-drivers=all
    I just run:

    ./configure --enable-drivers=all
    make
    

    and it made the job…


  • Netgate Administrator

    Thanks for that.  :)
    I managed to get it to compile in the end. My biggest problem was a typo I made in the config files while adding the driver.  :-[

    Actually I might take this opportunity to document the process if you don't mind me hi-jacking your thread.

    Steve



  • @Cino:

    Thanks Steve! I've done some reading also and not there yet to create my own.

    @mdima Take a look here, looks like you need to open a ticket http://forum.pfsense.org/index.php/topic,25519.msg132491.html#msg132491

    OK! Sorry for the delay but I just got back from my "summer break" and the urgent stuff was stucking me…

    Also, it took a lot of time because I wanted to compile also the picolcd driver, but it's really hard, at least for me, since I should install also the libusb library that is needed but I don't know where to install them... btw, in the end I was using the drivers from your dropbox, and I used the x86 version...

    At this address (http://staff.nt2.it/lcdproc.zip) you can download the files to install on the pfSense box. The files in the /bin directory should be copied on the box in the directory /usr/local/lib/lcdproc, the others in the directory /usr/local/pkg.

    This files are the "merge" of the files I changed + your changes (serial ports, parameters of the picolcd, and so on) + the driver binary files for picolcd... on my system the package works, if it works on your system also I update my git branch and will ask again to update the main repository with the files from my branch in order to install the updated package directly from the webconfigurator... ok?

    Thanks,
    Michele



  • @stephenw10:

    Thanks for that.  :)
    I managed to get it to compile in the end. My biggest problem was a typo I made in the config files while adding the driver.  :-[

    Actually I might take this opportunity to document the process if you don't mind me hi-jacking your thread.

    Steve
    [/quote]

    no, it's fine! I really thought that the LCDProc package was kind of dead, because it was not updated since a lot of time, and the mantainer's email is not reachable anymore… but as I see everyone is implementing his own changes by himself and this can lead to a mess...

    Now I was "merging" the changes that Cino and I did to the package, if you want we can merge also yours, in order to update the package in the repository... what do you think about that?



  • Michele, I wont be able to see my display until later this evening but I'll let you know how it turns out… And thank you very much!!



  • @Cino:

    Michele, I wont be able to see my display until later this evening but I'll let you know how it turns out… And thank you very much!!

    Don't worry, it's fine! I look forward to hearing a feedback from you!



  • @mdima:

    Also, it took a lot of time because I wanted to compile also the picolcd driver, but it's really hard, at least for me, since I should install also the libusb library that is needed but I don't know where to install them… btw, in the end I was using the drivers from your dropbox, and I used the x86 version...

    the libusb library, a full install of FreeBSD includes this lib. Don't know if it makes a difference, but I've put libusb.so.5 in the /usr/local/lib directory. We don't need libkvm.so.5 lib anymore. This is included with the current snapshots of pfsense.

    I had problems trying to compile all the drivers for lcdproc from source-code using ./configure –enable-drivers=all. I signed up for the lcdproc mailing list and was told instead of compiling from SC, use the Port from the package system and tell that to configure all the drivers... Doing this, I was able to get all the drivers for with no errors since the package knew where all the libs that were needed.


  • Netgate Administrator

    Mostly to remind myself how I did it here are the steps I took to compile a new driver for LCDproc for the package under 2.0.

    I started with an install of FreeBSD 8.1_release.
    First install the FreeBSD port of LCDproc. Goto /usr/ports/sysutils/lcdproc and type make. This will download all the sources and dependencies for LCDproc 0.5.3 and build them.
    Then follow the instructions from the LCDproc site, here, to add your new driver. There are some parts of these that are unclear.  ;)
    The driver I'm adding is specific to the Watchguard Firebox, which causes problems later, named sdeclcd.
    Editing acinclude.m4 is as per the instructions, as long as you don't make a typo! Editing Makefile.am was more involved.
    For step 2 I needed:```
    sdeclcd_LDADD =      libLCD.a libbignum.a

    And for step 3 I needed:```
     sdeclcd_SOURCES =    lcd.h lcd_lib.h sdeclcd.c sdeclcd.h report.h 
    

    Next you need to run autogen.sh but that's not included in the FreeBSD port so download it from here to  /usr/ports/sysutils/lcdproc/work/lcdproc-0.5.3.
    Then you can run ./configure –enable-drivers=sdeclcd (or whatever your driver is or all to build every driver) and then make to build the driver. sdeclcd.ko in my case.

    You then need to edit the files from the lcdproc package to allow the new driver to be selected and loaded. This is still a work in progress for me as the driver is a special case.

    Steve



  • i copied the package files over and it worked for me. I did leave the libusb in the /usr/local/lib directory tho.

    reading steve's post, i believe that was the same thing i did when i trying to get the driver i needed.



  • @Cino:

    i copied the package files over and it worked for me. I did leave the libusb in the /usr/local/lib directory tho.

    ok, I updated the files in my git clone… today I will mail Jim and ask how to do that... I keep you updated!

    Ciao,
    Michele



  • Thanks Michele!


  • Netgate Administrator

    Assides from having to add your driver are either of having problems with the lcdproc package?

    Because I intended to modify the package I first setup my own local repo as detailed here.
    I have had a lot of trouble getting the package up and running. A lot of my problems were caused by the fact that, despite putting the .htaccess file in every directory I could, the php files from the package are being executed by my server rather than served.   >:(
    However even having moved the php file manually I am getting errors. The lcdproc_client.php file will not run such that I just see the output of LCDd on the LCD. Running /tmp/lcdclient.sh manually gives:

    Fatal error: Cannot redeclare array_combine() in /usr/local/pkg/lcdproc_client.php on line 84
    

    Commenting out the array_combine function and the CPU usage function which depends on it allows it to run.
    I have no idea why this won't run for me yet other people aren't complaining.  ???

    Steve



  • @stephenw10: this is a bug I fixed on my version of LCDProc… you can use my version of LCDProc (in this thread in a previous post there's the link) or wait that I try to merge the changes I made in the main repository...


  • Netgate Administrator

    Ok thanks, not just me then!  ::)

    Solved the php parsing problem. By default Apache ignores .htaccess files unless you allow it. I added the following to httpd.conf:

    
     <directory "="" usr="" local="" www="" apache22="" data="" packages"="">AllowOverride All</directory> 
    
    

    Allowing 'all' is more than what is required but solves the problem.

    Steve

    Edit: I see you commented out the function but left it in CPU Usage. Do you have a list of changes?

    Edit: If you're merging stuff then there should be a description line in the service section of lcdproc.xml like so:

    
     <service><name>lcdproc</name>
    		<description>LCD Driver</description>
    		<rcfile>lcdproc.sh</rcfile>
    		<executable>LCDd</executable></service> 
    

    This fills in the empty box on Status: Services:



  • @Cino:

    Thanks Michele!

    ok, I committed all the changed in the new repository… I hope that soon all this changed will be torned in production, in the real distributed package!

    Ciao,
    Michele



  • @stephenw10: well, I made so many changes from may that I lost the track… the most important I remember are: added mbuf screen, added support for panels 4x20 and 4x16, also now the screen size is considered by the application (before was anyway fixed 16x2), added some comports, added a parameter for the refresh frequency, added the states screen (think I did, not sure about that), added the cpu frequency screen. After 1 month I made also some optimizations to all the above code.

    I committed my changed with my clone on rcs.pfsense.org only a couple of times, but I think that if you need to make some changes it worths to start from my files...

    I just added the description to the LCDProc service and I committed it... ;)


  • Netgate Administrator

    Com 1 seems to have vanished from lcdproc.xml  ;)

    Steve

    Edit: Ah so com1 is default if you don't select anything?



  • @stephenw10:

    Com 1 seems to have vanished from lcdproc.xml  ;)

    Steve

    Edit: Ah so com1 is default if you don't select anything?

    mmmhhhh… I didn't change that, but it's not so nice if "none" means com1... :S

    btw, if you reinstall the package now you download the last version!! :) Thanks to Jim and Luiz!!



  • looks like the merge request when thru, https://github.com/bsdperimeter/pfsense-packages/commit/c587fd97b5baaec9358b50f303326350d1c23088.

    A couple of things tho:
    1: Please remove libkvm.so.5 from the package, pfsense has it built-in already
    2: libusb.so.2 should be located at /usr/local/lib
    3: This maybe your next step, are your going to update to 0.5.4?

    I removed everything including manual files… installed the package and it started after clicking start under services. I have to verify that the screen is working but that will be later tonight... Swamp at work to prepare for the Hurricane and I'm on stand-by with the army national guard. Should be a fun weekend in NYC... Glad I live an hour+ away from the city.

    If the screen is displaying correctly, then issue 2 wouldn't be an issue :-)

    On another note, have either of you messed around with using lcdproc client that comes with LCDproc? I've enabled it on my build because I like the load graphical screen. Works pretty good. You have to copy lcdproc.conf.sample to lcdproc.conf and edit some of the settings. then you can run lcdproc from the command line or within a start-up script.



  • Hi Cino,
    about your points:

    @Cino:

    1: Please remove libkvm.so.5 from the package, pfsense has it built-in already

    I did it. For this:

    @Cino:

    2: libusb.so.2 should be located at /usr/local/lib

    I am a bit afraid to mess up some other package or part that use that file… it should be better to leave the file in his own directory, so if someone uninstalls LCDProc does not remove a lib from a "common directory" that maybe is needed by some other package or similar, what do you think about that? Tell me when you're back home, if it works I would leave this file where it is, if it does not work I move it, ok? Just let me know...

    About the update of LCDProc to 5.4, the changelog reports only a couple of drivers more and a small bugfix, I am not sure it worths it... anyway, now I am trying to manage a x64 virtual machine, + I have your files for both versions, let me think about it...

    As for the graphical screens, no I didn't try anything... but consider that this package is done for a lot of different devices and panels, I am a bit scared about introducing features that could not be compatible with this devices...

    It is very honorable of you being ready to serve your Country in case of need... I wish you the best for the Hurricane in NY...



  • @mdima:

    About the update of LCDProc to 5.4, the changelog reports only a couple of drivers more and a small bugfix, I am not sure it worths it… anyway, now I am trying to manage a x64 virtual machine, + I have your files for both versions, let me think about it...

    Actually, for this, I was investigating a bit and I found out that LCDProc 0.5.4 is already present in http://files.pfsense.org/packages/8/All/ and http://files.pfsense.org/packages/amd64/8/All/ and in both files "lcdproc-0.5.4.tbz" there is both the Surelect then the picolcd driver… the only missing file would be libusb.so.2 that I can't find in the package...

    So the update to 0.5.4 looks less painful than I thought...


  • Netgate Administrator

    @Cino:

    Please remove libkvm.so.5 from the package, pfsense has it built-in already

    But only on 2.0. As far as I can see this package will still appear under 1.2.3 and won't work. Need to change pkg_config.7.xml? Or fork?
    @Cino:

    2: libusb.so.2 should be located at /usr/local/lib

    You've confirmed that you definitely need this?

    @Cino:

    Swamp at work to prepare for the Hurricane and I'm on stand-by with the army national guard

    :o I was nailing some plastic over a window I didn't finish painting before it started raining earlier. I was cursing the weather. Then I watched the news and it put it into perspective! Good luck.

    @Cino:

    On another note, have either of you messed around with using lcdproc client that comes with LCDproc?

    Until now that's the only client I had used. A forum user had written the driver for LCDproc 0.52 sometime ago and released a tarball with LCDd and lcdproc included. The lcdproc package client is far more flexible it's relatively easy to add extra screens but it doesn't look anywhere near as good as the standard lcdproc client. I think my screen has a slow update time. It's hard to read a lot of the scrolling info, especially as it goes in both directions. See the thread here. The second post is about making a package. Three and half years later it still hasn't happened!  ::)

    Maybe we should include the Watchguard driver in this package to give people more choice?

    Steve


  • Netgate Administrator

    @lcdproc:

    TitleSpeed = SPEED
    Set the speed how fast over-long title lines shall scroll. Legal values are 0 to 10, where 0 means that no scrolling takes place and 10 stands for fastest scrolling. Default is 10, where no artificial delay is inserted.

    Hmm, defaults to the highest speed. Room for adjustment there then.

    Steve



  • @stephenw10:

    @Cino:

    Please remove libkvm.so.5 from the package, pfsense has it built-in already

    But only on 2.0. As far as I can see this package will still appear under 1.2.3 and won't work. Need to change pkg_config.7.xml? Or fork?

    The picolcd.so driver wont work on 1.2.3. There is some usb hack that needs to be applied. I dont have the link but it was covered under the freebsd.org board somewhere. http://forum.pfsense.org/index.php/topic,13697.msg123473.html#msg123473

    @stephenw10:

    @Cino:

    2: libusb.so.2 should be located at /usr/local/lib

    You've confirmed that you definitely need this?

    Don't need it seems :-) It's already located '/usr/lib'

    I really need to learn the program.. I wanted to create a tab to the lcdproc package to add the different screens from lcdproc.

    @mdima thank you so much for adding updating the package. When you get a chance, please remove libusb.so.2 from the package. It doesn't need to be part of since its built-in into the pfsense snapshot. Never noticed it before back when i first added the driver to 2.0-Beta4

    i made a mistake saying that it adding a graphical screen, its really just a character based screen that looks like a bar graph… Its already part of the LCDproc package..



  • @Cino:

    @mdima thank you so much for adding updating the package. When you get a chance, please remove libusb.so.2 from the package. It doesn't need to be part of since its built-in into the pfsense snapshot. Never noticed it before back when i first added the driver to 2.0-Beta4

    you are welcome, it was the 1st time I dealed with pfSense packages, for me it is still all new…
    now I am thinking about the update to version 0.5.4, which will solve the problem of "binaries in the package repository"...

    @Cino:

    i made a mistake saying that it adding a graphical screen, its really just a character based screen that looks like a bar graph… Its already part of the LCDproc package..

    what you mean with this?


  • Netgate Administrator

    The standard lcdproc client, confusingly called lcdproc, uses custom characters to display either vertical or horisontal bars to indicate values. Like this:


    That picture doesn't really show it to full effect though. All idle!

    Because of the way lcdproc works you can have more than one client program running so it should be possible to use both lcdproc_client.php and the standard lcdproc and have them both displayed.

    Steve

    Edit: This thread should be in packages don't you think?



  • @stephenw10:

    The standard lcdproc client, confusingly called lcdproc, uses custom characters to display either vertical or horisontal bars to indicate values. Like this:


    That picture doesn't really show it full effect though. All idle!

    Because of the way lcdproc works you can have more than one client program running so it should be possible to use both lcdproc_client.php and the standard lcdproc and have them both displayed.

    Steve

    Edit: This thread should be in packages don't you think?

    that's great! I was also finding this one: http://www.youtube.com/watch?v=Vqo7ZTxlxyE
    How do you do that?

    anyway, now yes, we start to be a little ot in this forum… or this changes apply only to the version 2.0?
    I don't know, I don't have a pfsense 1.2.3 anymore...


  • Netgate Administrator

    That video shows it much better.  :)

    To use the lcproc client you just call it with your selection of screens as command line options.
    As described here: http://lcdproc.sourceforge.net/docs/current-user.html#running-lcdproc

    Currently users of Watchguard hardware have a tarball with an install script that puts the files in the correct locations etc. Because it's not a real pfSense package you have to re-install it after each firmware update and it doesn't integrate with the GUI at all. Hence my effort.

    In the script it is called from /usr/local/etc/rc.d with:

    
    /usr/bin/nice -20 /usr/local/share/lcdd/lcdproc C T U &
    
    

    Steve



  • Here is photo of the load screen:

    http://forum.pfsense.org/index.php/topic,39362.0.html



  • Any new progress? I was released from state active duty for the hurricane so i've been playing catch-up…



  • Hi Cino,
    I was asking to update the package to version 0.5.4… I don't know what is better between updating the current package or create a new package (LCDProc-dev) until it is stable to replace the current package... anyway, let's see what the guys will answer me...

    I will update this post when I have news about that!

    Ciao,
    Michele


Log in to reply