2.3 LCDPROC
-
The fix is here - they haven't merged it into pfsense yet.
The two versions are the same with the exception of those three '+' symbols that got inserted into the previous pull request.
i.e. 2.3.3 includes the extra matrix orbital stuff, you just have to delete those + symbols.
-
The fix is here - they haven't merged it into pfsense yet.
The two versions are the same with the exception of those three '+' symbols that got inserted into the previous pull request.
i.e. 2.3.3 includes the extra matrix orbital stuff, you just have to delete those + symbols.
Great thanks. The MatrixOrbital fix was the important one, I can handle the + symbols.
-
The MatrixOrbital fix was the important one, I can handle the + symbols.
For what it's worth, they've now merged that + symbol fix in.
-
LCDproc 0.10.4 is in the Package Manager/Available Packages
but i get this error
LCD display driver.Package Dependencies:
lcdproc-0.5.7_2New packages to be INSTALLED:
pfSense-pkg-LCDproc: 0.10.4 [pfSense]
lcdproc: 0.5.7_2 [pfSense]
freetype2: 2.6.3 [pfSense]Number of packages to be installed: 3
The process will require 3 MiB more space.
787 KiB to be downloaded.
pkg: https://pkg.pfsense.org/pfSense_v2_3_3_i386-pfSense_v2_3_3/All/pfSense-pkg-LCDproc-0.10.4.txz: Not Found
Failedthere anyway to change the location its looking for the files or are they fixing it
-
It looks like the version number needs to be bumped to 0.10.5.
-
to treer, or whomever else may know:
I manually installed lcdproc on 2.3.1 (and since upgraded to 2.3.2). if i upgrade to 2.3.3 with lcdproc available as a package, should i uninstall (and how would i do this?) the manually installed version and then install the official package, or will there be no issues with upgrading and installing over the manually installed version?
I just don't want two versions running at the same time, or some other silly issue.
i could use the uninstallation part of the instructions here: https://github.com/Treer/FreeBSD-ports/blob/devel/README.md#update
edit: hmmm… it's already showing up in my installed packages list even on 2.3.2 with an available upgrade from 0.10.1 to 0.10.5
-
The package is effectively the same thing, it was this that was accepted into our repo.
You would not get two versions running as both would try to use the same config file and hence the same port and would fail.
I wouldn't anticipate any problems
Steve
-
I originally installed the package manually on 2.3.2. Today it showed up in the official package list in yellow indicating there was an update. I did the update to 0.10.5 through the GUI. Everything went fine and there is no duplication of menus. I don't anticipate any issue when upgrading to 2.3.3 next weekend.
-
cool, i upgraded LCDproc and then installed 2.3.3. everything worked fine!
-
What's the correct way to file a feature request against LCDproc?
I have a CrystalFontz 631 display and I need to frequently edit the .inc file and edit the model number from 635 to 631. There should be a dropdown in the GUI to specify what model CrystalFontz display is attached.
-
The best way would be to add that code and file a pull request.
But otherwise you can open a feature request in redmine: https://redmine.pfsense.org/projects/pfsense-packages
You might get more traction bribing Treer here though. ;)
Steve
-
I was worried about spamming the pfsense maintainers with pull requests, so there's already a change I haven't sent them yet, I could add the CrystalFontz model as well.
These sorts of problems will be ongoing unless someone comprehensively implements all lcdproc's config options in the GUI, and then you have a messy GUI. Many pfsense screens facing similar problems have a "Custom options" field, so perhaps the LCDProc GUI ought to have a custom options textbox where users can extend or somehow smartly override any options set by the GUI?
What would be desirable behaviour for a custom options textbox? Normally they are for appending extra config lines, and often that's all the LCDProc webgui will need, but for overriding settings (like joako would have had to) I think lcdproc usually uses the first setting it finds (skip=0) so it might be better to have any custom text inserted between the [drivername] and the lines produced by the GUI.
-
I used to use this form thread https://forum.pfsense.org/index.php?topic=83747.15 to fix the required port speed to 38400 required to make my lcd work. However since the latest update I can no longer edit this parameter using this method because they don't exist. If someone could point me in the right direction it would be much appreciated.
-
Which particular post in that thread? I don't see anything on that page you linked to concerning baud rate.
Steve
