LCDProc 0.5.4-dev

mdima

… and we are with 0.9.2.

I didn't realize that there were some clients pending, that with the new error counter management could work behind. So now all the lcdproc_client.php processes are killed during the package resync.

Sorry for the people that was already upgrading do 0.9.1...

stephenw10

Looks good. :)

Now the error counter is in the php script (much better) why bother having lcdclient.sh at all?
Just call the php client from the rc file directly.

Also I have been running fmertz's driver he removed real time priority from with Nice level 20. Doing this allows the box to remain responsive even when some error event occours. Since the LCD is really of no importance compared to the firewall functions it seems better to run it at minimum priority. E.g.


$start .= "\t/usr/bin/nice -20 /usr/local/sbin/LCDd -c ". LCDPROC_CONFIG ."\n";
$start .= "\t/usr/bin/nice -20 ". LCDPROC_CLIENT ." &\n";

Steve

mdima

@stephenw10:

Looks good. :)

Thanks!

@stephenw10:

Now the error counter is in the php script (much better) why bother having lcdclient.sh at all?
Just call the php client from the rc file directly.

makes sense…

@stephenw10:

Also I have been running fmertz's driver he removed real time priority from with Nice level 20. Doing this allows the box to remain responsive even when some error event occours. Since the LCD is really of no importance compared to the firewall functions it seems better to run it at minimum priority. E.g.
$start .= "\t/usr/bin/nice -20 /usr/local/sbin/LCDd -c ". LCDPROC_CONFIG ."\n";
$start .= "\t/usr/bin/nice -20 ". LCDPROC_CLIENT ." &\n";

also this makes sense. Just we have to consider if this influences negatively the client or LCDd to refresh the data or communicate with the panel, but it's just a matter of tuning…

fmertz

Folks, the SDEC driver for Fireboxes is now officially part of the upstream lcdproc project! I received confirmation this morning that my code submission was committed. I guess it should come to pfSense as part of the package when the project leaders decide the current development branch is stable enough for release.

Now, on to support for the LEDs…

mdima

That's great! So the next version of LCDproc will have the SDEC driver… fmerz, consider that the compiling option in pfSense is "WITH_USB=true" only, I don't know if with this option the SDEC driver will be compiled...

BTW, how's going with the new package version? I found out it's more stable, but anyway still give some problems... what do you think?

Thanks,
Michele

stephenw10

Excellent work! ;D

Steve

fmertz

@stephenw10:

X-Peak:


[2.0.1-RELEASE][root@pfsense.fire.box]/root(7): pciconf -r pci0:31:0 0:256
25a18086

Device ID 25a1 is a 6300ESB, data sheet: http://ark.intel.com/products/27663/Intel-6300ESB-IO-Controller

For the X-Peak, the LEDs are on GPIO pins 40 and 41. This is part of the second set of pins, so there no blink support in hardware. We already knew this…

Anyone with an X-Core?

tix

@fmertz:

I would like the output of the command, for the X-Core and X-Peak models. The key is the first 8 digits, the last 4 being 8086, Intel's vendor ID. Thanks.

X-Core (x700)


/root(1): pciconf -r pci0:31:0 0:256
24408086 0280000f 06010005 00800000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00004001 00000010 00000000 00000000
00000000 00000000 00004081 00000010
09060b0c 000000d0 0a058003 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00005475 00000000 00000000 00000000
00000200 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00004004 00000000 00000000
00002002 00001f02 00000004 00000000
c0000010 14050000 00112233 45670291
017c000f 00000000 00000f47 00000200
ffffffff

I'm using the WGXepc script and it works flawlessly!

fmertz

@tix:

X-Core (x700)


/root(1): pciconf -r pci0:31:0 0:256
24408086

2440 is an 82801BA, Intel ICH2, datasheet here: http://www.intel.com/content/dam/doc/datasheet/82801ba-i-o-controller-hub-2-82801bam-i-o-controller-hub-2-mobile-datasheet.pdf

Somehow the existing WGXepc code does not seem to line up with the spec…

mdima

Hi,
how's going with the latest (0.9.2) package?

Right now I am working on this:

I divided / 2 the number of commands sent to LCDproc every cycle. So if before were sent 10 commands, now only 5
I wrote a little better code for error handling
I slowed down a bit the scrolling (just a little bit)
Simplified the script to launch. There's no more lcdproc_client.sh.

Then I will:
4) add and test the "nice" command to the programs running
5) I will add a "top value" for waiting to the next cycle of 10 seconds. So it will be sure that the communication won't timeout

What else?

Ciao,
Michele

stephenw10

@fmertz:

Somehow the existing WGXepc code does not seem to line up with the spec…

Hmm, in what way?
There was a problem because the GPIO base is set to a non-standard value on the X-core.
On the other boxes it is at 0x480, which I believe is the standard value where as the X-Core is at 0x4080.

Steve

fmertz

@stephenw10:

@fmertz:

Somehow the existing WGXepc code does not seem to line up with the spec…

Hmm, in what way?
There was a problem because the GPIO base is set to a non-standard value on the X-core.
On the other boxes it is at 0x480, which I believe is the standard value where as the X-Core is at 0x4080.

Steve

The way I read it, this particular device ID is an ICH2, and has the GPIO base port stored at offset 0x58 (page 9-1). Fine. The value at that offset happens to be 4081, which, masked off is 4080 (this was listed in the pciconf command, and is already in your code). Fine. In your code, you use port 4080 + 0x0f. Offset 15 in the GPIO area is for GPIO level, and bits control pins. Fine. The blink register is at offset 0x18 (32 bit), so I am not sure how it can blink with just the level register, or how it is not possible to turn the LEDs off…

For the X-Core-e, the Level port controls on/off, the Blink port controls the, well, blinking, and it all can be turned off with putting the bit to zero.

stephenw10

I had to re-read the thread to remind myself what happened. I agree with you it doesn't make any sense! In fact you can see, here, where I was expecting the registers to work as you describe above but the experimental results show otherwise.

One thing that is different about the X-core is that you can set the LED state in the BIOS (though I've never tried it myself). And you have a choice of red or green and fast or slow flash. There is no fast/slow blink described in the documentation yet it is clearly available. :-\

Steve

tix

Hello

I've tried the latest .92 package and my x-core will still become unresponsive at the 10 hour mark.

I'm out of ideas on what the issue could be… :(

mdima

@tix:

Hello

I've tried the latest .92 package and my x-core will still become unresponsive at the 10 hour mark.

I'm out of ideas on what the issue could be… :(

Hi Tix,
Thank you for the feedback. I am trying a new version with a lot of changes, if it passes my tests I will publish it… Cross your fingers...

Ciao,
Michele

fmertz

@mdima:

@tix:

Hello

I've tried the latest .92 package and my x-core will still become unresponsive at the 10 hour mark.

I'm out of ideas on what the issue could be… :(

Hi Tix,
Thank you for the feedback. I am trying a new version with a lot of changes, if it passes my tests I will publish it… Cross your fingers...

Ciao,
Michele

Shot in the dark: is the client reading the responses back from LCDd? The release notes mentioned something about ignoring them causing unpleasant behavior …

Cino

I'm noticing a bug that I haven't seen since before the re-write of the package. If my second WAN does down (3G wireless), and comes back up; lcdclient seems to lose the connection to LCDd. In the past I would have pages of errors in the system log. but i dont have any this time. I do want to say this started with the last changes.

Still want to see if I can reproduce this on the fly (maybe tin cup around the 3G Wireless USB stick) but wanted to report it

Edit: I think this may have been a fluke… my 3g went down a couple of times last night and no issues with lcdproc

mdima

@fmertz:

@mdima:

@tix:

Hello
I've tried the latest .92 package and my x-core will still become unresponsive at the 10 hour mark.
I'm out of ideas on what the issue could be… :(

Hi Tix,
Thank you for the feedback. I am trying a new version with a lot of changes, if it passes my tests I will publish it… Cross your fingers...

Ciao,
Michele

Shot in the dark: is the client reading the responses back from LCDd? The release notes mentioned something about ignoring them causing unpleasant behavior …

Fmertz,
what do you mean? I just read the entire changelog and the release notes but I didn't find anything about that. Can you give me some references?

EDIT: Btw, yes, the client is reading the responses and log on pfSense if there is some error reported (messages with huh?)

Now I am running the binary 0.5.3 and the package 0.9.2 to see what changes. With 0.5.5 it looks like there are some problems having more than one screen, like there are problems for LCDd to "switch" during the screen rotation.

If you all set only one screen with 0.5.3 and pkg 0.9.2 do you have this problem?

Thanks,
Michele

mdima

@Cino:

I'm noticing a bug that I haven't seen since before the re-write of the package. If my second WAN does down (3G wireless), and comes back up; lcdclient seems to lose the connection to LCDd. In the past I would have pages of errors in the system log. but i dont have any this time. I do want to say this started with the last changes.

Still want to see if I can reproduce this on the fly (maybe tin cup around the 3G Wireless USB stick) but wanted to report it

Edit: I think this may have been a fluke… my 3g went down a couple of times last night and no issues with lcdproc

Hi Cino,
well, this should have start with the last version of the package.

Before the LCDclient was trying to connect to LCDd forever (which caused endless lists of log entries and high CPU usage), now if it fails for 3 times straight it will end. In the while if LCDd restart to respond, it connects and resets the error counter.

I can understand that a gateway failture may cause a reset of the routes and the states, but if the client gets disconnected it starts other 2 times to reconnect (about 10 seconds between each attempt). Maybe we should increase it to 4… what do you think about it?

Thanks,
Michele

fmertz

@mdima:

@fmertz:

Shot in the dark: is the client reading the responses back from LCDd? The release notes mentioned something about ignoring them causing unpleasant behavior …

Fmertz,
what do you mean? I just read the entire changelog and the release notes but I didn't find anything about that. Can you give me some references?

EDIT: Btw, yes, the client is reading the responses and log on pfSense if there is some error reported (messages with huh?)

https://github.com/fmertz/sdeclcd/blob/master/BUGS

The documentation for responses is here: http://lcdproc.sourceforge.net/docs/lcdproc-0-5-5-dev.html#language-messages

It says: LCDd can send messages back to the client. These messages can be directly related to the last command, or generated for some other reason. Because messages can be generated at any moment, the client should read from the connection at regular intervals. A very simple client could simply ignore all received messages. Not reading the messages will cause trouble !

I read this to mean that LCDd could generate more than one response to a command, or even send text outside of typical responses to commands. Does the PHP code accommodate for this? Reading the code, there seems to be the assumption that only 1 response comes back, maybe leaving responses hanging, and slowly filling the buffer. Just a thought.