Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Firebox LCD Driver for LCDProc

    Hardware
    97
    398
    413.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fastcon68
      last edited by

      I go back over it one more time.  I removed the extra lines.  No clue how it happened.  I tookl instruction from about 4 different posts and combined them into one posting.

      I will see if I can run over see where I missed a step.
      RC

      1 Reply Last reply Reply Quote 0
      • J
        jimmy
        last edited by

        @trendchiller:

        fix it by:

        cd /lib
        ln -s libc.so.7 libc.so.6
        ln -s libkvm.so.4 libkvm.so.3

        then it works

        Did this, but I still receive:

        /usr/local/etc/rc.d/lcdd.sh

        /libexec/ld-elf.so.1: # Shared object "libkvm.so.3" not found, required by "lcdproc"

        I'm using the latest pfsense 2.0 beta, but as far as I can see that should not be the problem.
        libc.so.6 and libkvm.so.3 do exist, so making the links was not a problem:

        ls /lib
        …
        lrwxr-xr-x   1 root  wheel        9 Jun  8 10:05 libc.so.6 -> libc.so.7
        lrwxr-xr-x   1 root  wheel       11 Jun  8 10:04 libkvm.so.3 -> libkvm.so.4
        ...

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          That's because pfsense 2.0 uses libkvm.so.5 so you need to use:

          
          ln -s libkvm.so.5 libkvm.so.3
          

          However when I did this it still wouldn't work under 2.0beta and there were no useful errors given either.

          Steve

          1 Reply Last reply Reply Quote 0
          • J
            jimmy
            last edited by

            @stephenw10:

            However when I did this it still wouldn't work under 2.0beta and there were no useful errors given either.

            Steve

            Ok, I've made the link to libkvm.so.5 now and it gives no error anymore.
            Since I'm currently working remote I cannot see if the display shows anything (but I expect it to be the same as yours)… I'll check the display later today!

            EDIT: After some time, an error came up:
            sock_connect: connect failed
            Error connecting to LCD server 127.0.0.1 on port 13666.
            Check to see that the server is running and operating normally.
            ???

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              It doesn't really suprise me since everything in this thread was built against freebsd7.2 and pfsense2.0 is freebsd 8.
              It works great on 1.2.3 though!  ;D

              Steve

              1 Reply Last reply Reply Quote 0
              • J
                jjstecchino
                last edited by

                @stephenw10:

                It doesn't really suprise me since everything in this thread was built against freebsd7.2 and pfsense2.0 is freebsd 8.
                It works great on 1.2.3 though!  ;D

                Steve

                I am using the firebox lcd driver and lcdproc on 2.0 beta 2 and it works like a charm. The box is a firebox x500 with a full install, not nanobsd.
                One thing different that I have not seen mentioned is that the updated driver with key and backlit timer support is looking for LCDd.conf in /usr/local/etc and not in /usr/local/share/lcdd. Once LCDd.conf was moved to the appropriate location it worked just fine. Maybe that is the problem.

                1 Reply Last reply Reply Quote 0
                • J
                  jimmy
                  last edited by

                  @jjstecchino:

                  I am using the firebox lcd driver and lcdproc on 2.0 beta 2 and it works like a charm. The box is a firebox x500 with a full install, not nanobsd.
                  One thing different that I have not seen mentioned is that the updated driver with key and backlit timer support is looking for LCDd.conf in /usr/local/etc and not in /usr/local/share/lcdd. Once LCDd.conf was moved to the appropriate location it worked just fine. Maybe that is the problem.

                  Are you using:
                  A. the "lcdd.tar.gz" from post #7 ( http://files.pfsense.org/misc/lcdd.tar.gz ), and
                  B. the updated driver "sdeclcd.so" from post #22 ( http://goessens.dyndns.org/public )?

                  If I look at the lcdd.sh script, I see it using the LCDd.conf from /usr/local/share/lcdd.

                  
                  /usr/bin/nice -20 /usr/local/share/lcdd/LCDd -r 0 -c /usr/local/share/lcdd/LCDd.conf > /dev/null 2>&1 &
                  /usr/bin/nice -20 /usr/local/share/lcdd/lcdproc C M S &
                  
                  

                  Just to be sure, I've now also copied the conf file to /usr/local/etc.
                  But it still comes with the same error, saying that it cannot connect to the lcdd server.

                  EDIT:
                  Perhaps this would help?

                  If I just namually start:

                  /usr/local/share/lcdd/LCDd -c /usr/local/share/lcdd/LCDd.conf

                  I a receive more detailed error:
                  Could not open driver module /usr/local/share/lcdd/drivers/sdeclcd.so: Shared object "libkvm.so.4" not found, required by "sdeclcd.so"
                  Driver [sdeclcd] binding failed
                  Could not load driver sdeclcd
                  There is no output driver
                  Critical error while initializing, abort.

                  So I've done "ln -s libkvm.so.5 libkvm.so.4"
                  (I now have libkvm.so.3 and 4 linked to 5)

                  When I then start the same command, no error.

                  Then I killed the previously manually started LCDd and started the lcdd.sh script again.
                  No errors, only I cannot see the display right now, because I am working remotely…

                  EDIT AGAIN: Yes, the display is working!
                  Only the backlight is off, so it's a bit hard to see what's on the display.

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    The backlight should come on again if you press one of the buttons.
                    Confirmation of working in 2.0 is great news.  ;D

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • J
                      jimmy
                      last edited by

                      @stephenw10:

                      The backlight should come on again if you press one of the buttons.
                      Confirmation of working in 2.0 is great news.  ;D

                      Steve

                      Tried the buttons: the display changes  (shows other info) but no backlight.
                      (not even during of immediately after a reboot)

                      1 Reply Last reply Reply Quote 0
                      • C
                        CaseyBlackburn
                        last edited by

                        @jimmy:

                        Tried the buttons: the display changes  (shows other info) but no backlight.
                        (not even during of immediately after a reboot)

                        If you don't see it even right when you power on your box, your backlight is dead.

                        1 Reply Last reply Reply Quote 0
                        • J
                          jimmy
                          last edited by

                          @CaseyBlackburn:

                          @jimmy:

                          Tried the buttons: the display changes  (shows other info) but no backlight.
                          (not even during of immediately after a reboot)

                          If you don't see it even right when you power on your box, your backlight is dead.

                          Weird… I own a second box, also an x700... It doesn't have the original flashdisk inside anymore so it won't bootup, but this one also doesn't light when I turn on the box.  Do I miss something? I mean, I can't imagine having 2 boxes with a dead backlight!   ???

                          I will check a third box at the office tomorrow, that's one that's still operating with the original flashdisk, just to see what "should happen" with the backlight.

                          EDIT: Found it already. My first box does have a dead backlight. It's a bit less light here now and I can see the backlight on the second box, but not on the first box. So it's time to switch boxes.  :-[

                          1 Reply Last reply Reply Quote 0
                          • J
                            jjstecchino
                            last edited by

                            @jimmy:

                            @CaseyBlackburn:

                            @jimmy:

                            Tried the buttons: the display changes  (shows other info) but no backlight.
                            (not even during of immediately after a reboot)

                            If you don't see it even right when you power on your box, your backlight is dead.

                            Weird… I own a second box, also an x700... It doesn't have the original flashdisk inside anymore so it won't bootup, but this one also doesn't light when I turn on the box.  Do I miss something? I mean, I can't imagine having 2 boxes with a dead backlight!   ???

                            I will check a third box at the office tomorrow, that's one that's still operating with the original flashdisk, just to see what "should happen" with the backlight.

                            EDIT: Found it already. My first box does have a dead backlight. It's a bit less light here now and I can see the backlight on the second box, but not on the first box. So it's time to switch boxes.   :-[

                            [/quote]

                            The backlit comes on for several seconds just after power on with or without disk. If it doesnt it is dead.

                            If anybody is interested I may have found a solution for the watchdog errors. I posted it on a separate thread under hardware

                            1 Reply Last reply Reply Quote 0
                            • J
                              jjstecchino
                              last edited by

                              This box is getting better and better.
                              Now…. How do we display more useful and pertinent info on the LCD?
                              A network bandwidth graph
                              current throughput
                              vpn connections
                              errors
                              Boot  messages.

                              All of the above and much more would be nice.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                The default options are quite limited you have choices of:

                                screen
                                    can be one of the following: 
                                C CPU
                                    show detailed CPU usage 
                                P SMP-CPU
                                    CPU usage overview: one line per CPU, especially useful on SMP systems. 
                                G CPUGraph
                                    CPU histogram 
                                L Load
                                    Load histogram 
                                M Memory
                                    memory & swap usage 
                                S ProcSize
                                    memory usage of 5 biggest processes 
                                D Disk
                                    filling level of the mounted file systems 
                                I Iface
                                    network interface usage 
                                B Battery
                                    battery status 
                                T TimeDate
                                    time & date information 
                                O OldTime
                                    old time screen 
                                U Uptime
                                    old uptime screen 
                                K BigClock
                                    big clock 
                                N MiniClock
                                    minimal clock 
                                A About
                                    credits page
                                

                                Add the letters to where lcdproc is called in /usr/local/etc/rc.d/lcdd.sh. Not all of them work. I went with C T U.

                                Otherwise write your own client or use one someone else has written (a lot). It's supposed to be quite easy but since the  last time I coded anything was at Uni about 12 years ago it's  beyond me!  ::)

                                Steve

                                1 Reply Last reply Reply Quote 0
                                • J
                                  jjstecchino
                                  last edited by

                                  @stephenw10:

                                  The default options are quite limited you have choices of:

                                  screen
                                      can be one of the following: 
                                  C CPU
                                      show detailed CPU usage 
                                  P SMP-CPU
                                      CPU usage overview: one line per CPU, especially useful on SMP systems. 
                                  G CPUGraph
                                      CPU histogram 
                                  L Load
                                      Load histogram 
                                  M Memory
                                      memory & swap usage 
                                  S ProcSize
                                      memory usage of 5 biggest processes 
                                  D Disk
                                      filling level of the mounted file systems 
                                  I Iface
                                      network interface usage 
                                  B Battery
                                      battery status 
                                  T TimeDate
                                      time & date information 
                                  O OldTime
                                      old time screen 
                                  U Uptime
                                      old uptime screen 
                                  K BigClock
                                      big clock 
                                  N MiniClock
                                      minimal clock 
                                  A About
                                      credits page
                                  

                                  Add the letters to where lcdproc is called in /usr/local/etc/rc.d/lcdd.sh. Not all of them work. I went with C T U.

                                  Otherwise write your own client or use one someone else has written (a lot). It's supposed to be quite easy but since the  last time I coded anything was at Uni about 12 years ago it's  beyond me!  ::)

                                  Steve

                                  Steve I am away from home for a few days I can ssh to the boxbut I cannot see the lcd so I cant test.
                                  Are you able to display nework stats (letter I) on your box?

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Hmm, the screen shows up OK but no data is shown for I. Maybe with some tweaking.
                                    The only really useful things for me is how long since it last crashed and is the CPU pegged at 100% by some hideous crashed code. Anything else I'll just log in and look. To be honest none of the screens are very nice at 2X20. I should get off my arse and write something, it could easily have a single screen with cpu usage and uptime.
                                    Steve

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      jjstecchino
                                      last edited by

                                      @stephenw10:

                                      Hmm, the screen shows up OK but no data is shown for I. Maybe with some tweaking.
                                      The only really useful things for me is how long since it last crashed and is the CPU pegged at 100% by some hideous crashed code. Anything else I'll just log in and look. To be honest none of the screens are very nice at 2X20. I should get off my arse and write something, it could easily have a single screen with cpu usage and uptime.
                                      Steve

                                      I agree 2x20 is not spectacular, but it can be used to display some nice cpu/ network graphs

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        thewizard
                                        last edited by

                                        hi

                                        after following the above when i try to start lcdd.sh under usr/local/etc/rc.d

                                        i get the following

                                        /libexec/ld-elf.co.1: shared object
                                        "libkvm.so.3 not found, requirded by "lcdproc"

                                        any ideas on this one

                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          You need to add the sym links:

                                          
                                          cd /lib
                                          ln -s libc.so.7 libc.so.6
                                          ln -s libkvm.so.4 libkvm.so.3
                                          
                                          

                                          This is assuming you're running 1.2.3.

                                          Steve

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            thewizard
                                            last edited by

                                            @stephenw10:

                                            You need to add the sym links:

                                            
                                            cd /lib
                                            ln -s libc.so.7 libc.so.6
                                            ln -s libkvm.so.4 libkvm.so.3
                                            
                                            

                                            This is assuming you're running 1.2.3.

                                            Steve

                                            Hi Steve

                                            i am running 1.2.3

                                            after entering the above i get

                                            ln: libc.so.6: file exists
                                            ln: libkvm.so.3: file exists

                                            thorghts?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.