You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(6) |
Feb
(2) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(9) |
Oct
(2) |
Nov
(3) |
Dec
|
2002 |
Jan
|
Feb
(4) |
Mar
(5) |
Apr
(1) |
May
(12) |
Jun
(3) |
Jul
(7) |
Aug
(10) |
Sep
(5) |
Oct
(6) |
Nov
(2) |
Dec
|
2003 |
Jan
(3) |
Feb
(11) |
Mar
(9) |
Apr
(6) |
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
(36) |
Sep
(19) |
Oct
(54) |
Nov
(14) |
Dec
(23) |
2004 |
Jan
(30) |
Feb
(49) |
Mar
(35) |
Apr
(9) |
May
(18) |
Jun
(3) |
Jul
(8) |
Aug
(1) |
Sep
(15) |
Oct
(6) |
Nov
(5) |
Dec
(21) |
2005 |
Jan
(32) |
Feb
(14) |
Mar
(2) |
Apr
(13) |
May
(7) |
Jun
(31) |
Jul
(14) |
Aug
(27) |
Sep
(9) |
Oct
(19) |
Nov
(9) |
Dec
(13) |
2006 |
Jan
(35) |
Feb
(8) |
Mar
(27) |
Apr
(16) |
May
(4) |
Jun
(5) |
Jul
(20) |
Aug
(53) |
Sep
(58) |
Oct
(19) |
Nov
(21) |
Dec
(11) |
2007 |
Jan
(42) |
Feb
(20) |
Mar
(5) |
Apr
(14) |
May
(18) |
Jun
(11) |
Jul
(22) |
Aug
(17) |
Sep
(2) |
Oct
(8) |
Nov
|
Dec
(2) |
2008 |
Jan
(25) |
Feb
(1) |
Mar
(4) |
Apr
(5) |
May
(5) |
Jun
|
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(6) |
Nov
|
Dec
|
2009 |
Jan
(2) |
Feb
(4) |
Mar
|
Apr
|
May
(10) |
Jun
|
Jul
(7) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
2010 |
Jan
(17) |
Feb
(2) |
Mar
(2) |
Apr
(6) |
May
(4) |
Jun
(2) |
Jul
(1) |
Aug
(5) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(5) |
Jun
|
Jul
(11) |
Aug
(2) |
Sep
(2) |
Oct
(5) |
Nov
(5) |
Dec
(18) |
2012 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(2) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(2) |
Dec
|
2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
(5) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
(4) |
Mar
|
Apr
(12) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Michael R. <mi...@re...> - 2011-10-15 02:36:46
|
Hi Kaya, Could you provide a copy of your lcd4linux.conf? signal 2 is SIGINT, did you stop it with Ctrl-C or something? regards, Michael Am 2011-10-12 21:01, schrieb Kaya Saman: > Ok managed to get the display recognized as it was on the wrong USB header! > > However, when running: lcd4linux -Fvv > > I get: > > # cat lcd > Version 0.10.1-RC1-768 starting > plugin_cfg.c: Variable n = '0' (0) > plugin_cfg.c: Variable nkey = '0' (0) > [KVV] Using station 89 > [KVV] Using default port 80 > [KVV] Using default refresh interval of 60 seconds > [KVV] Default abbreviation setting: off > lcd4linux.c: initializing driver picoLCD > picoLCD: $Rev: 759 $ > picoLCD: scanning for picoLCD... > picoLCD: found picoLCD on bus 004 device 002 > picoLCD: Manufacturer='ITUNER INC' Product='USB-LCD-20x2' SerialNumber='1.57rel.' > Setting contrast to 0 > Setting backlight to 1 > picoLCD: reserving 6 of 8 user-defined characters for icons > picoLCD: using 0 GPI's and 8 GPO's > initializing layout 'L20x2' > lcd4linux.c: starting main loop > lcd4linux.c: got signal 2 > lcd4linux.c: leaving main loop > picoLCD: shutting down. > > > with a whole bunch of these errors: > > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > picoLCD::GPI(1): GPI out of range (1..0) > > > and additionally this error too: > > Starting lcd4linux: error evaluating variable 'button_text' from /etc/lcd4linux.conf > > > Can anyone help me with that? > > > Thanks, > > > Kaya > > > > -------- Original Message -------- > Subject: PicoLCD from Mini-Box M300 not detecting? > Date: Wed, 12 Oct 2011 21:17:31 +0300 > From: Kaya Saman <kay...@gm...> > To: lcd...@li... > > > > Hi, > > I'm totally new to working with LCD's and linux. I purchased a Mini-Box > Mini-ITX case with 20x2 PicoLCD module embedded to run on a Trixbox > based Asterisk server. > > The display lights up and information is displayed on the panel and the > keyboard works at least for the power key. > > I hooked it up via the on-board USB connector to the internal USB header > on the system board. > > > I have the wiring diagram for it at hand even though came pre-wired but > still I think all that was needed was to attach the USB cable to the > system board..... > > > Anyway, when I run the lcd4linux command I get this output: > > # lcd4linux -Fvv > Version 0.10.1-RC1-768 starting > error evaluating variable 'button_text' from /etc/lcd4linux.conf > plugin_cfg.c: Variable n = '0' (0) > plugin_cfg.c: Variable nkey = '0' (0) > [KVV] Using station 89 > [KVV] Using default port 80 > [KVV] Using default refresh interval of 60 seconds > [KVV] Default abbreviation setting: off > lcd4linux.c: initializing driver picoLCD > picoLCD: $Rev: 759 $ > picoLCD: scanning for picoLCD... > picoLCD: could not find a picoLCD > > How come that it isn't finding the picoLCD device? > > > I took the sample configuration from here: > > http://ssl.bulix.org/projects/lcd4linux/wiki/picoLCD > > > and also checked out this as well: > > http://ssl.bulix.org/projects/lcd4linux/ticket/265 > > but am a bit confused? > > > Can anyone give me a hand as to what is going on? > > > > > This is the output of uname -a: > > 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 > GNU/Linux > > > > lsusb doesn't actually show anything either? > > > # lsusb > Bus 005 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 002 Device 002: ID 0b38:0003 Gear Head Keyboard > Bus 003 Device 001: ID 0000:0000 > Bus 004 Device 001: ID 0000:0000 > > > > Many thanks!! > > > Kaya > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > > > > _______________________________________________ > Lcd4linux-users mailing list > Lcd...@li... > https://lists.sourceforge.net/lists/listinfo/lcd4linux-users -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Kaya S. <kay...@gm...> - 2011-10-12 19:02:10
|
Ok managed to get the display recognized as it was on the wrong USB header! However, when running: lcd4linux -Fvv I get: # cat lcd Version 0.10.1-RC1-768 starting plugin_cfg.c: Variable n = '0' (0) plugin_cfg.c: Variable nkey = '0' (0) [KVV] Using station 89 [KVV] Using default port 80 [KVV] Using default refresh interval of 60 seconds [KVV] Default abbreviation setting: off lcd4linux.c: initializing driver picoLCD picoLCD: $Rev: 759 $ picoLCD: scanning for picoLCD... picoLCD: found picoLCD on bus 004 device 002 picoLCD: Manufacturer='ITUNER INC' Product='USB-LCD-20x2' SerialNumber='1.57rel.' Setting contrast to 0 Setting backlight to 1 picoLCD: reserving 6 of 8 user-defined characters for icons picoLCD: using 0 GPI's and 8 GPO's initializing layout 'L20x2' lcd4linux.c: starting main loop lcd4linux.c: got signal 2 lcd4linux.c: leaving main loop picoLCD: shutting down. with a whole bunch of these errors: picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) picoLCD::GPI(1): GPI out of range (1..0) and additionally this error too: Starting lcd4linux: error evaluating variable 'button_text' from /etc/lcd4linux.conf Can anyone help me with that? Thanks, Kaya -------- Original Message -------- Subject: PicoLCD from Mini-Box M300 not detecting? Date: Wed, 12 Oct 2011 21:17:31 +0300 From: Kaya Saman <kay...@gm...> To: lcd...@li... Hi, I'm totally new to working with LCD's and linux. I purchased a Mini-Box Mini-ITX case with 20x2 PicoLCD module embedded to run on a Trixbox based Asterisk server. The display lights up and information is displayed on the panel and the keyboard works at least for the power key. I hooked it up via the on-board USB connector to the internal USB header on the system board. I have the wiring diagram for it at hand even though came pre-wired but still I think all that was needed was to attach the USB cable to the system board..... Anyway, when I run the lcd4linux command I get this output: # lcd4linux -Fvv Version 0.10.1-RC1-768 starting error evaluating variable 'button_text' from /etc/lcd4linux.conf plugin_cfg.c: Variable n = '0' (0) plugin_cfg.c: Variable nkey = '0' (0) [KVV] Using station 89 [KVV] Using default port 80 [KVV] Using default refresh interval of 60 seconds [KVV] Default abbreviation setting: off lcd4linux.c: initializing driver picoLCD picoLCD: $Rev: 759 $ picoLCD: scanning for picoLCD... picoLCD: could not find a picoLCD How come that it isn't finding the picoLCD device? I took the sample configuration from here: http://ssl.bulix.org/projects/lcd4linux/wiki/picoLCD and also checked out this as well: http://ssl.bulix.org/projects/lcd4linux/ticket/265 but am a bit confused? Can anyone give me a hand as to what is going on? This is the output of uname -a: 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 GNU/Linux lsusb doesn't actually show anything either? # lsusb Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 002 Device 002: ID 0b38:0003 Gear Head Keyboard Bus 003 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Many thanks!! Kaya |
From: Kaya S. <kay...@gm...> - 2011-10-12 18:17:42
|
Hi, I'm totally new to working with LCD's and linux. I purchased a Mini-Box Mini-ITX case with 20x2 PicoLCD module embedded to run on a Trixbox based Asterisk server. The display lights up and information is displayed on the panel and the keyboard works at least for the power key. I hooked it up via the on-board USB connector to the internal USB header on the system board. I have the wiring diagram for it at hand even though came pre-wired but still I think all that was needed was to attach the USB cable to the system board..... Anyway, when I run the lcd4linux command I get this output: # lcd4linux -Fvv Version 0.10.1-RC1-768 starting error evaluating variable 'button_text' from /etc/lcd4linux.conf plugin_cfg.c: Variable n = '0' (0) plugin_cfg.c: Variable nkey = '0' (0) [KVV] Using station 89 [KVV] Using default port 80 [KVV] Using default refresh interval of 60 seconds [KVV] Default abbreviation setting: off lcd4linux.c: initializing driver picoLCD picoLCD: $Rev: 759 $ picoLCD: scanning for picoLCD... picoLCD: could not find a picoLCD How come that it isn't finding the picoLCD device? I took the sample configuration from here: http://ssl.bulix.org/projects/lcd4linux/wiki/picoLCD and also checked out this as well: http://ssl.bulix.org/projects/lcd4linux/ticket/265 but am a bit confused? Can anyone give me a hand as to what is going on? This is the output of uname -a: 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 GNU/Linux lsusb doesn't actually show anything either? # lsusb Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 002 Device 002: ID 0b38:0003 Gear Head Keyboard Bus 003 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Many thanks!! Kaya |
From: Rob M. <rob...@gm...> - 2011-09-14 19:28:26
|
On Wed, Sep 14, 2011 at 19:41, Janis Tupulis <jtu...@gm...> wrote: > Hi, > > Just got my picoLCD 256x64 and stuck in the very beginning, just can't > start the thing. Help would be very much appreciated. > > First of all, seem that hw is not an issue: lcd lights at startup and > is found by lsusb. > > Then, tried an easy way - installing manufacturer provided drivers+sw: > http://www.picolcd.com/drivers/?ck=V...p&cktime=96661 Initially - most > simple thing - installer. Doesn't work - software just doesn't fire > up, nothing happen. Tried to run script in a terminal, got messages I > wasn't able to google out: > > jtupulis@STRAZDS:~/picolcd-256x64/picoLCDGraphic$ ./start-picolcd256x64.sh > Installation path: /home/jtupulis/picolcd-256x64 > Running gksu wrapper > /home/jtupulis/picolcd-256x64/picoLCDGraphic/gksu: error while loading > shared libraries: libstartup-notification-1.so.0: wrong ELF class: > ELFCLASS64 A quick Google found me lots of answers, http://stackoverflow.com/questions/216000/gcc-error-wrong-elf-class-elfclass64 for a start > But there is display entry in conf file: > > # The display settings > > Display picoLCD { > Driver 'picoLCDGraphic' > Size '256x64' > Contrast 230 > Backlight 1 > Inverted 1 > Icons 1 > } Is there a matching line of: Display 'picoLCD' later in the configuration file? -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
From: Janis T. <jtu...@gm...> - 2011-09-14 18:42:00
|
Hi, Just got my picoLCD 256x64 and stuck in the very beginning, just can't start the thing. Help would be very much appreciated. First of all, seem that hw is not an issue: lcd lights at startup and is found by lsusb. Then, tried an easy way - installing manufacturer provided drivers+sw: http://www.picolcd.com/drivers/?ck=V...p&cktime=96661 Initially - most simple thing - installer. Doesn't work - software just doesn't fire up, nothing happen. Tried to run script in a terminal, got messages I wasn't able to google out: jtupulis@STRAZDS:~/picolcd-256x64/picoLCDGraphic$ ./start-picolcd256x64.sh Installation path: /home/jtupulis/picolcd-256x64 Running gksu wrapper /home/jtupulis/picolcd-256x64/picoLCDGraphic/gksu: error while loading shared libraries: libstartup-notification-1.so.0: wrong ELF class: ELFCLASS64 /home/jtupulis/picolcd-256x64/picoLCDGraphic/gksu: error while loading shared libraries: libstartup-notification-1.so.0: wrong ELF class: ELFCLASS64 Then decided to go a bit harder way: installed lcd4linux from svn and to to be sure (?) compiled picoLCD driver from manufacturer source. But, trying to launch lcd4linux: missing 'Display' entry in /etc/lcd4linux.conf! But there is display entry in conf file: # The display settings Display picoLCD { Driver 'picoLCDGraphic' Size '256x64' Contrast 230 Backlight 1 Inverted 1 Icons 1 } I was not able to google out next step in order to proceed, please help, maybe somebody has similar experience? -- Veiksmi, Jānis |
From: Michael R. <mi...@re...> - 2011-08-09 04:13:12
|
Hi there, did you try to run ./bootstrap ? Maybe some files are missing in the distribution? I never know which files that are created by the autotool chain should be checkd in into subversion... mybe someone with deeper knowledge can give me some advices? regards, Michael Am 2011-08-02 17:03, schrieb Mattias Tengblad: > Rupert Plumridge<r.plumridge@...> writes: > >> >> HiNew user here. I am having problems compiling the latest version from > SVN.Here is the output of the ./configure command: > http://pastebin.com/fXYfFPb7And then, when I try to make (using sudo for both as > I am in /usr/local/src) I get this:CDPATH="${ZSH_VERSION+.}:"&& cd .&& > /bin/bash /usr/local/src/lcd4linux/missing --run aclocal-1.11 -I m4aclocal-1.11: > couldn't open directory `m4': No such file or directorymake: *** [aclocal.m4] > Error 1After mkdir m4I now get this error:rupert<at> > noah:/usr/local/src/lcd4linux$ sudo make cd .&& /bin/bash > /usr/local/src/lcd4linux/missing --run automake-1.11 --gnuMakefile.am:16: > required file `./ltmain.sh' not found >> make: *** [Makefile.in] Error 1Something clearly not right here....As I have > already successfully built ffmpeg and x264 from source, I am pretty sure I have > all the required build tools (automake is already up-to-date).A google search > doesn't show anything.Any pointers what is wrong?Rupert >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev > > Hi, > > Did you find a solution? Got the exact same problem. > > //Matt > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos& much more. Register early& save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Lcd4linux-users mailing list > Lcd...@li... > https://lists.sourceforge.net/lists/listinfo/lcd4linux-users -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Mattias T. <ms...@ey...> - 2011-08-02 15:05:22
|
Rupert Plumridge <r.plumridge@...> writes: > > HiNew user here. I am having problems compiling the latest version from SVN.Here is the output of the ./configure command: http://pastebin.com/fXYfFPb7And then, when I try to make (using sudo for both as I am in /usr/local/src) I get this:CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /usr/local/src/lcd4linux/missing --run aclocal-1.11 -I m4aclocal-1.11: couldn't open directory `m4': No such file or directorymake: *** [aclocal.m4] Error 1After mkdir m4I now get this error:rupert <at> noah:/usr/local/src/lcd4linux$ sudo make cd . && /bin/bash /usr/local/src/lcd4linux/missing --run automake-1.11 --gnuMakefile.am:16: required file `./ltmain.sh' not found > make: *** [Makefile.in] Error 1Something clearly not right here....As I have already successfully built ffmpeg and x264 from source, I am pretty sure I have all the required build tools (automake is already up-to-date).A google search doesn't show anything.Any pointers what is wrong?Rupert > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev Hi, Did you find a solution? Got the exact same problem. //Matt |
From: Hans de G. <hde...@re...> - 2011-07-27 08:51:28
|
Hi, On 07/27/2011 09:55 AM, Michael Reinelt wrote: > Hi Hans, > > in your email you wrote: >> Note that I'm an active contributor to lm_sensors upstream too, >> and a such I must say that it would be better if there would be >> a plugin using libsensors rather then accessing sysfs directly. >> The advantages are that libsensors takes care of the details >> of sysfs parsing, and more importantly that it offers one >> central configuration file for things like scaling and offsets >> of sensors, as often some conversion is needed to go from raw >> sysfs value to a "real" value. > > Using libsensors sounds like a good idea. > > The i2c_sensors plugin is quite old (it was contributed by Xavier Vello back in 2004). maybe at that time libsensors was not available, or in a bad quality, or... > > Another question comes to my mind: I always try to keep "embedded systems" in mind. Do you see a problem with libsensors there? No libsensors is quite small, written in plain C and has no external dependencies. > OTOH, is there a possible performance penalty when using libsensors? See above, quite small written in C. > anyway, because of me lacking experience with libsensors, and because of -ENOTIME, any volunteers for a new plugin? (I'd prefer having a seperate plugin for that, keeping the old one at least for some time) I think doing a libsensors plugin is a good idea and a fun little project, but I'm afraid -ENOTIME applies to me too. But if others are interested I'll gladly help with answering any questions people may have about libsensors. Regards, Hans |
From: Hans de G. <hde...@re...> - 2011-07-27 08:49:51
|
Hi, On 07/27/2011 10:25 AM, Be...@da... wrote: > Hello, > I'm reading the lcd4linux mailing list. > > I want to check your LCD-FRAME thingi, but the Link inside your article > won't work: > http://picframe.spritesserver.nl/wiki/index.php/UsingAsPicframe > I'm afraid that that website is not hosted by my, so there is nothing I can do to fix it. > Would you please take a look to it? Regards, Hans |
From: <Be...@da...> - 2011-07-27 08:43:50
|
Hello, I'm reading the lcd4linux mailing list. I want to check your LCD-FRAME thingi, but the Link inside your article won't work: http://picframe.spritesserver.nl/wiki/index.php/UsingAsPicframe > http://article.gmane.org/gmane.comp.sysutils.lcd4linux.devel/396/ > > Regards, > > Hans > Would you please take a look to it? Thank you Bernd |
From: Michael R. <mi...@re...> - 2011-07-27 07:56:05
|
Hi Hans, in your email you wrote: > Note that I'm an active contributor to lm_sensors upstream too, > and a such I must say that it would be better if there would be > a plugin using libsensors rather then accessing sysfs directly. > The advantages are that libsensors takes care of the details > of sysfs parsing, and more importantly that it offers one > central configuration file for things like scaling and offsets > of sensors, as often some conversion is needed to go from raw > sysfs value to a "real" value. Using libsensors sounds like a good idea. The i2c_sensors plugin is quite old (it was contributed by Xavier Vello back in 2004). maybe at that time libsensors was not available, or in a bad quality, or... Another question comes to my mind: I always try to keep "embedded systems" in mind. Do you see a problem with libsensors there? OTOH, is there a possible performance penalty when using libsensors? anyway, because of me lacking experience with libsensors, and because of -ENOTIME, any volunteers for a new plugin? (I'd prefer having a seperate plugin for that, keeping the old one at least for some time) regards, Michael -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Michael R. <mi...@re...> - 2011-07-27 07:44:14
|
Hi Hans, >> Could you please resend that Mail? I don't have an explanation :-) > > That is why I put a link to that mail in my previous mail, I guess you missed it, so here it is again: > http://article.gmane.org/gmane.comp.sysutils.lcd4linux.devel/396/ Oh, silly me... thanks. -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Hans de G. <hde...@re...> - 2011-07-27 07:38:49
|
Hi, On 07/27/2011 04:24 AM, Michael Reinelt wrote: > Hi Hans, > >> The patches which I've can be found here: >> >> http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-hwmon.patch;hb=master >> http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-st2205-width-height-swap.patch;hb=master >> http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-wireless.patch;hb=master > > Thanks a lot, Looks like I really missed some emails here. > > Anyway, patches have been applied and committed. > >> See my initial post for an explanation of them. Esp. the hwmon one. I think it would be good to document >> how to use the i2c_sensors plugin with multiple sensor devices, feel free to copy paste any or all text >> from my initial mail for that. > > Could you please resend that Mail? I don't have an explanation :-) That is why I put a link to that mail in my previous mail, I guess you missed it, so here it is again: http://article.gmane.org/gmane.comp.sysutils.lcd4linux.devel/396/ Regards, Hans |
From: Michael R. <mi...@re...> - 2011-07-27 02:24:41
|
Hi Hans, > The patches which I've can be found here: > > http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-hwmon.patch;hb=master > http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-st2205-width-height-swap.patch;hb=master > http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-wireless.patch;hb=master Thanks a lot, Looks like I really missed some emails here. Anyway, patches have been applied and committed. > See my initial post for an explanation of them. Esp. the hwmon one. I think it would be good to document > how to use the i2c_sensors plugin with multiple sensor devices, feel free to copy paste any or all text > from my initial mail for that. Could you please resend that Mail? I don't have an explanation :-) Or, even better, change the Wiki yourselves? regards, Michael -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Michael R. <mi...@re...> - 2011-07-27 02:15:29
|
Hi Matt, > Anyway, my contribution, attached. > I'm not familiar with C so if there are daft mistakes, then apologies. > Happy to be shown. committed to trunk. -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Matt J. <mat...@gm...> - 2011-07-25 11:15:11
|
That's a tough time to get up in the morning. Must play havoc with your social life. Anyway, my contribution, attached. I'm not familiar with C so if there are daft mistakes, then apologies. Happy to be shown. Best regards Matt On Mon, Jul 25, 2011 at 17:38, Michael Reinelt <mi...@re...> wrote: > Hi all, > > sorry for replying late, I've been offline due to business journey for a few days... > > first, LCD4Linux is not dead, it's just in a kind of C6 state, or deep sleep, or.. > > the reason is simple and sad: I am still extremely busy with my real-life job, getting up every day at around 3 o'clock > in the morning, working at least for 12 hours, even on weekends. > > What we could really need is a Co-maintainer, at least for answering mails and integrating patches. Write access to the > repository should be no problem (as Sam aka Maxime already wrote) > > Anyway, i feel very sorry for disappointing some or all of you. I will try to find some spare time in the future, do do > at least the most important tasks. > > unfortunately I lost some emails in the last months (ya know, SSDs are the hell fast, but not as reliable as I expected > them to be). So if there are important patches that haven't been integrated 8or will be integrated in the next days) > please resend them. > > I will go to my mail archive, and integrate all patches that I can find. After that, i will create a new release (this > time really!) > > for this specific MPD problem, what is the problem (or better: the solution)? > > > kind regards, Michael > > > > Am 2011-07-23 12:40, schrieb Hans de Goede: >> Hi, >> >> On 07/23/2011 01:44 AM, Matt Joyce wrote: >>> I posted a patch to this list last September. Nearly a year ago. >>> I didn't hear anything back at all, not even a 'no thank you'. >>> >>> That lack of engagement is quite demotivating. >>> To suggest not to fork is fine (I agree), but if I have to manually >>> add my own patch, technically it has forked. >>> >>> I'm all for simply leaving this project where it is, but for the team >>> to be more responsive, and/or enable others to take action. >> >> Yes, so I'm writing this down for one more vote as someone needs to >> pick up lcd4linux, merge submitted patches and do a new release, preferably >> while working together with Michael / the sf.net project, iow without >> forking. >> >> So we need someone to step forward and volunteer to actually do this, >> and then we should contact Michael about this. So any volunteers? >> >> Note I'm explicitly not nominating myself, because of -ENOTIME. Next >> to my $dayjob I still have a coulple of webcams which need reverse >> engineering and then writing a Linux driver for them ... >> >> Regards, >> >> Hans >> >> ------------------------------------------------------------------------------ >> Storage Efficiency Calculator >> This modeling tool is based on patent-pending intellectual property that >> has been used successfully in hundreds of IBM storage optimization engage- >> ments, worldwide. Store less, Store more with what you own, Move data to >> the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ >> _______________________________________________ >> Lcd4linux-devel mailing list >> Lcd...@li... >> https://lists.sourceforge.net/lists/listinfo/lcd4linux-devel >> >> > > -- > Michael Reinelt <mi...@re...> > http://home.pages.at/reinelt > GPG-Key 0xDF13BA50 > ICQ #288386781 > > ------------------------------------------------------------------------------ > Storage Efficiency Calculator > This modeling tool is based on patent-pending intellectual property that > has been used successfully in hundreds of IBM storage optimization engage- > ments, worldwide. Store less, Store more with what you own, Move data to > the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ > _______________________________________________ > Lcd4linux-devel mailing list > Lcd...@li... > https://lists.sourceforge.net/lists/listinfo/lcd4linux-devel > -- http://about.me/mattjoyce |
From: Hans de G. <hde...@re...> - 2011-07-25 08:27:32
|
Hi, On 07/25/2011 09:38 AM, Michael Reinelt wrote: > Hi all, > > sorry for replying late, I've been offline due to business journey for a few days... > > first, LCD4Linux is not dead, it's just in a kind of C6 state, or deep sleep, or.. > That is very good to hear, and apologies for using the word dead. I've done enough FOSS work to know that a project like this feels like it is your baby and you don't want to hear that someone saying your baby is dead. I guess this is also a good moment to (re-)explain my interest in lcd4linux. I've reverse engineered and written a libgphoto2 based driver for st2205 based miniature digital photo frames (keychain photoframes). Naturally I encountered the picframe project which has a hack for these devices to use them as external lcd displays. I've given this a try together with lcd4linux. As a result of this I've also ended up packaging lcd4linux (and libst2205 and some other deps) for Fedora. Also see my initial mail to this list: http://article.gmane.org/gmane.comp.sysutils.lcd4linux.devel/396/ > the reason is simple and sad: I am still extremely busy with my real-life job, getting up every day at around 3 o'clock > in the morning, working at least for 12 hours, even on weekends. > Wow, those are heavy heavy workdays. > What we could really need is a Co-maintainer, at least for answering mails and integrating patches. Write access to the > repository should be no problem (as Sam aka Maxime already wrote) > > Anyway, i feel very sorry for disappointing some or all of you. I will try to find some spare time in the future, do do > at least the most important tasks. > > unfortunately I lost some emails in the last months (ya know, SSDs are the hell fast, but not as reliable as I expected > them to be). So if there are important patches that haven't been integrated 8or will be integrated in the next days) > please resend them. The patches which I've can be found here: http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-hwmon.patch;hb=master http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-st2205-width-height-swap.patch;hb=master http://pkgs.fedoraproject.org/gitweb/?p=lcd4linux.git;a=blob_plain;f=lcd4linux-wireless.patch;hb=master See my initial post for an explanation of them. Esp. the hwmon one. I think it would be good to document how to use the i2c_sensors plugin with multiple sensor devices, feel free to copy paste any or all text from my initial mail for that. Regards, Hans |
From: Michael R. <mi...@re...> - 2011-07-25 08:01:08
|
Hi all, sorry for replying late, I've been offline due to business journey for a few days... first, LCD4Linux is not dead, it's just in a kind of C6 state, or deep sleep, or.. the reason is simple and sad: I am still extremely busy with my real-life job, getting up every day at around 3 o'clock in the morning, working at least for 12 hours, even on weekends. What we could really need is a Co-maintainer, at least for answering mails and integrating patches. Write access to the repository should be no problem (as Sam aka Maxime already wrote) Anyway, i feel very sorry for disappointing some or all of you. I will try to find some spare time in the future, do do at least the most important tasks. unfortunately I lost some emails in the last months (ya know, SSDs are the hell fast, but not as reliable as I expected them to be). So if there are important patches that haven't been integrated 8or will be integrated in the next days) please resend them. I will go to my mail archive, and integrate all patches that I can find. After that, i will create a new release (this time really!) for this specific MPD problem, what is the problem (or better: the solution)? kind regards, Michael Am 2011-07-23 12:40, schrieb Hans de Goede: > Hi, > > On 07/23/2011 01:44 AM, Matt Joyce wrote: >> I posted a patch to this list last September. Nearly a year ago. >> I didn't hear anything back at all, not even a 'no thank you'. >> >> That lack of engagement is quite demotivating. >> To suggest not to fork is fine (I agree), but if I have to manually >> add my own patch, technically it has forked. >> >> I'm all for simply leaving this project where it is, but for the team >> to be more responsive, and/or enable others to take action. > > Yes, so I'm writing this down for one more vote as someone needs to > pick up lcd4linux, merge submitted patches and do a new release, preferably > while working together with Michael / the sf.net project, iow without > forking. > > So we need someone to step forward and volunteer to actually do this, > and then we should contact Michael about this. So any volunteers? > > Note I'm explicitly not nominating myself, because of -ENOTIME. Next > to my $dayjob I still have a coulple of webcams which need reverse > engineering and then writing a Linux driver for them ... > > Regards, > > Hans > > ------------------------------------------------------------------------------ > Storage Efficiency Calculator > This modeling tool is based on patent-pending intellectual property that > has been used successfully in hundreds of IBM storage optimization engage- > ments, worldwide. Store less, Store more with what you own, Move data to > the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ > _______________________________________________ > Lcd4linux-devel mailing list > Lcd...@li... > https://lists.sourceforge.net/lists/listinfo/lcd4linux-devel > > -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Nathan L. <nt...@po...> - 2011-05-15 02:51:50
|
Greetings, I have a QNAP TS-439 Pro II+ NAS appliance[1] which sports a white-on-blue 16x2 character LCD with two buttons ("enter" and "select"). I haven't been able to determine the manufacturer or model, but it can be manipulated by writing strings to /dev/ttyS1. QNAP ships with their firmware some proprietary utilities that drive the LCD, but I'm running a stock Linux distribution on the system, and I'm hoping that lcd4linux either supports it or could be made to support it. Any suggestions for drivers/settings to try? I've attempted several drivers (MilfordInstruments MI216, CrystalFontz 626/632/633) without success. Clues: * Running strings(1) on the QNAP binaries shows references to "A78" e.g. A78_Send_Command(%d) A78_Turn_Off_Back_Light() A78_Turn_On_Back_Light() * It's attached to ttyS1 (second serial port) and folks on the QNAP forums[2] have reported that the port must be set to 1200 baud and it accepts the following commands: * Turn on: echo -e "M^\x1" > /dev/ttyS1 * Turn off: echo -e "M^\x0" > /dev/ttyS1 * Write a message to the first line: echo -e "M\f\x0 HELLO WORLD 1234" > /dev/ttyS1 * Write a message to the second line: echo -e "M\f\x1 HELLO WORLD 1234" > /dev/ttyS1 * I took a photo of the back of the LCD and posted it here: http://i.imgur.com/5lmbl.jpg * Here is a large (3.5MB) photo of the front of the unit: http://files.qnap.com/news/pressresource/product/TS-439ProII+09.png Thanks in advance for any guidance! Nathan [1] http://qnap.com/pro_detail_feature.asp?p_id=179 [2] http://forum.qnap.com/viewtopic.php?f=147&t=41752 |
From: Andreas W. <an...@t-...> - 2011-05-02 16:39:46
|
Hi, maybe there is an Option in Bios Setup to keep the usb ports on power or not? Regards, Andreas -----Ursprüngliche Nachricht----- Von: Till Harbaum / Lists [mailto:li...@ha...] Gesendet: Montag, 2. Mai 2011 17:13 An: lcd...@li... Betreff: Re: [lcd4linux] lcd4linux clean shutdown Hi, that's unintended. The glcd2usb should be painting some simple "splash screen" while not being used. This sounds like your board is switching USB power on and off on driver load/unload. Till On Monday, May 02, 2011 08:16:50 Stefan Krister wrote: > Hi Jonathan, > > Jonathan McCrohan schrieb am 02.05.2011 01:02: > > I am wondering what the easiest method of making lcd4linux clear the > > screen and dim the backlight on a Matrix Orbital LCD display upon > > shutdown. > > I was very surprised with my GLCD2USB plugged into my PC Engines Alix > board. 1st the display was off. During boot as the USB driver loads the > display came to life and the display screensaver [1] ran. When lcd4linux > started, normal content was shown [2]. > > On shutdown the same in opposit happened. At the end, all was dark and off. (...) |
From: Till H. / L. <li...@ha...> - 2011-05-02 15:39:30
|
Hi, that's unintended. The glcd2usb should be painting some simple "splash screen" while not being used. This sounds like your board is switching USB power on and off on driver load/unload. Till On Monday, May 02, 2011 08:16:50 Stefan Krister wrote: > Hi Jonathan, > > Jonathan McCrohan schrieb am 02.05.2011 01:02: > > I am wondering what the easiest method of making lcd4linux clear the > > screen and dim the backlight on a Matrix Orbital LCD display upon > > shutdown. > > I was very surprised with my GLCD2USB plugged into my PC Engines Alix > board. 1st the display was off. During boot as the USB driver loads the > display came to life and the display screensaver [1] ran. When lcd4linux > started, normal content was shown [2]. > > On shutdown the same in opposit happened. At the end, all was dark and off. > > > My current thinking is to create an script in /etc/rc0.d/ to run a > > second lcd4linux instance with a modified config file to simply clear > > the screen and dim the backlight and exit, however this seems wasteful. > > I would do it this way. However I wish to have a way to alter the > brightness during run without changching the config file and restart > lcd4linux. > > [1] http://gallery.port23.de/v/bastard/lcd/GLCD2USB/glcd2usb+061.JPG.html > [2] http://gallery.port23.de/v/bastard/lcd/GLCD2USB/glcd2usb+066.png.html > > Bye > > Stefan > > --------------------------------------------------------------------------- > --- WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Lcd4linux-users mailing list > Lcd...@li... > https://lists.sourceforge.net/lists/listinfo/lcd4linux-users |
From: Stefan K. <ste...@cr...> - 2011-05-02 06:48:12
|
Hi Jonathan, Jonathan McCrohan schrieb am 02.05.2011 01:02: > > I am wondering what the easiest method of making lcd4linux clear the > screen and dim the backlight on a Matrix Orbital LCD display upon shutdown. I was very surprised with my GLCD2USB plugged into my PC Engines Alix board. 1st the display was off. During boot as the USB driver loads the display came to life and the display screensaver [1] ran. When lcd4linux started, normal content was shown [2]. On shutdown the same in opposit happened. At the end, all was dark and off. > My current thinking is to create an script in /etc/rc0.d/ to run a > second lcd4linux instance with a modified config file to simply clear > the screen and dim the backlight and exit, however this seems wasteful. I would do it this way. However I wish to have a way to alter the brightness during run without changching the config file and restart lcd4linux. [1] http://gallery.port23.de/v/bastard/lcd/GLCD2USB/glcd2usb+061.JPG.html [2] http://gallery.port23.de/v/bastard/lcd/GLCD2USB/glcd2usb+066.png.html Bye Stefan |
From: Jonathan M. <jmc...@gm...> - 2011-05-01 23:02:53
|
Hi, I am wondering what the easiest method of making lcd4linux clear the screen and dim the backlight on a Matrix Orbital LCD display upon shutdown. My current thinking is to create an script in /etc/rc0.d/ to run a second lcd4linux instance with a modified config file to simply clear the screen and dim the backlight and exit, however this seems wasteful. Other ideas involve using eval() check for the existence of /etc/nologin and use a widget with no graphic to set the contrast of the LCD. This has the advantage of only using one lcd4linux instance. However it has now has to poll for the existence of /etc/nologin now. Does anyone know of any nicer methods? Thanks, Jon |
From: Michelle D. <md...@oc...> - 2011-04-06 15:41:35
|
Ok - well I'll stick with it then since it's 90% of what I want... If I were a programmer I'd definitely kick in to this project. Great functionality and design.... Thanks Michelle ________________________________________ From: Michael Reinelt [mi...@re...] Sent: Tuesday, April 05, 2011 9:17 PM To: Michelle Dupuis Cc: lcd...@li... Subject: Re: [lcd4linux] Is this list alive? Hi Michelle, > I haven't gotten a single email...and no reply to my last one. I just noticed that the lcd4linux software was last updated 2 years ago. Yes, bothe this list and project progress is very "low traffic" > Is this project dead? Should I move on to lcdproc or something else? I don't consider it dead. At least not completely. But at least for myself I am extremely busy with my real-life job for two years now, trying to get a really big project up and running.... thats why I get up between 2 and 3 am every morning.... therefore there is no time left for other things at the moment. sorry, Michael -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: Michael R. <mi...@re...> - 2011-04-06 01:30:55
|
Hi Michelle, > I haven't gotten a single email...and no reply to my last one. I just noticed that the lcd4linux software was last updated 2 years ago. Yes, bothe this list and project progress is very "low traffic" > Is this project dead? Should I move on to lcdproc or something else? I don't consider it dead. At least not completely. But at least for myself I am extremely busy with my real-life job for two years now, trying to get a really big project up and running.... thats why I get up between 2 and 3 am every morning.... therefore there is no time left for other things at the moment. sorry, Michael -- Michael Reinelt <mi...@re...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |