From: Kaya S. <kay...@gm...> - 2011-10-15 04:39:41
|
The actual SEGFAULT from the config provided in the previous email is this: lcd4linux -Fvv: Version 0.11.0-SVN-965 starting plugin_cfg.c: Variable tack = '100' (100) plugin_cfg.c: Variable tick = '500' (500) lcd4linux.c: initializing driver picoLCD picoLCD: $Rev: 947 $ 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 1 GPI's and 8 GPO's initializing layout 'L20x2' widget 'GPO_kf1': Class 'gpo', Parent '<root>', Layer 0, Row 1, Col 0 Segmentation fault ???? Regards, Kaya On 10/15/2011 05:22 AM, Michael Reinelt wrote: > 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 > |