search for: update_status

...normally then will randomly >> stop working at stop "send: QS". The debug logs show values successfully >> retrieved repeatedly until something like: >> .... >> Quick update... >> send: QS >> read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 >> update_status: OL >> update_status: !LB >> update_status: !CAL >> update_status: !FSD >> upsdrv_updateinfo... >> Quick update... >> send: QS >> (driver hangs here) >> >> I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB >> communication d...

...indicates the driver works normally then will randomly stop > working at stop "send: QS". The debug logs show values successfully > retrieved repeatedly until something like: > .... > Quick update... > send: QS > read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 > update_status: OL > update_status: !LB > update_status: !CAL > update_status: !FSD > upsdrv_updateinfo... > Quick update... > send: QS > (driver hangs here) > > I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB communication > driver 0.32. Playing with pollinterval di...

...;240.0" 20.075543 send_to_all: SETINFO ups.load "6" 20.075569 send_to_all: SETINFO input.frequency "50.0" 20.075596 send_to_all: SETINFO battery.voltage "40.50" 20.075632 send_to_all: SETINFO ups.temperature "29.0" 20.075652 update_status: OL 20.075667 update_status: !LB 20.075704 send_to_all: SETINFO ups.type "offline / line interactive" 20.075724 update_status: !CAL 20.075752 update_status: !FSD 20.075776 send_to_all: SETINFO ups.beeper.status "enabled" 20.075799 command: (8...

...nutdrv_qx -u root -a MY_UPS -DDDDDD indicates the driver works normally then will randomly stop working at stop "send: QS". The debug logs show values successfully retrieved repeatedly until something like: .... Quick update... send: QS read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 update_status: OL update_status: !LB update_status: !CAL update_status: !FSD upsdrv_updateinfo... Quick update... send: QS (driver hangs here) I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB communication driver 0.32. Playing with pollinterval didn't help - Is there anything further I can d...

On Mar 5, 2015, at 2:34 AM, Jakub <jakub.scepka at gmail.com> wrote: > Come on, it started to be interesting! Do you have one of these UPSes? If so, here was Dan's email about a branch to test: > If you still can't get it to work with nutdrv_atcl_usb, another > approach could be worth considering. > > Since this UPS seems to be supported by UPSmart2000I, it could

...an action on my controller for updating this value. I just tried the ''remote_function'', ah, function. It invokes the action on the controller but the the value of the select that it is connected to is not sent. I hope I am missing something simple. The controller action is: def update_status goal = Goal.find(params[:id]) goal.status = params[:goal][:status] goal.save end The relevant form part looks like this <%= select_tag(''goal[status]'', options_for_select(GoalStatus::STATES, goal.status), :onfiltered=> remote_function(:url => :update_st...

...87 command index: 0x03 12.249983 read: (47 bytes) => 28 30 30 30 2e 30 20 30 30 30 2e 30 20 30 30 30 2e 30 12.250037 20 30 30 30 20 30 30 2e 30 20 30 2e 30 30 20 30 30 2e 30 20 30 30 30 30 30 12.250055 30 30 30 0d 12.250069 read: (000.0 000.0 000.0 000 00.0 0.00 00.0 00000000 12.250091 update_status: OL 12.250112 update_status: !LB 12.250136 update_status: !CAL 12.250158 update_status: !FSD On 2 October 2016 at 23:26, hyouko at gmail.com <hyouko at gmail.com> wrote: > Matthew, I've looked briefly at the files you uploaded to GitHub and > it seems to me that the device i...

...PS -DDDDDD indicates the driver works normally then will randomly stop working at stop "send: QS". The debug logs show values successfully retrieved repeatedly until something like: > .... > Quick update... > send: QS > read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 > update_status: OL > update_status: !LB > update_status: !CAL > update_status: !FSD > upsdrv_updateinfo... > Quick update... > send: QS > (driver hangs here) > > I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB communication driver 0.32. Playing with pollinterval didn...

Matthew, I've looked briefly at the files you uploaded to GitHub and it seems to me that the device is like something that should work with the 'fabula' USB subdriver (and 'megatec' protocol): what are the issues you are experiencing and that prevent the driver to work?

...aux] poll_data: ups.firmware.aux UPS supports variable [ambient.humidity.alarm.maximum] poll_data: ambient.humidity.alarm.maximum UPS supports variable [ambient.humidity.alarm.minimum] poll_data: ambient.humidity.alarm.minimum APC - UPS capabilities determined Detected (null) [(null)] on /dev/ttyS0 update_status update_info_all: starting poll_data: ups.firmware.aux poll_data: ups.contacts poll_data: ambient.humidity poll_data: ambient.humidity.alarm.maximum poll_data: ambient.humidity.alarm.minimum poll_data: ambient.temperature poll_data: ambient.temperature.alarm.maximum poll_data: ambient.temperature.al...

...t;props.brightness; + int reg = NV_READ(NV40_PMC_BACKLIGHT); + + NV_WRITE(NV40_PMC_BACKLIGHT, + (val << 16) | (reg & ~NV40_PMC_BACKLIGHT_MASK)); + + return 0; +} + +static struct backlight_ops nv40_bl_ops = { + .options = BL_CORE_SUSPENDRESUME, + .get_brightness = nv40_get_intensity, + .update_status = nv40_set_intensity, +}; + +static int nv50_get_intensity(struct backlight_device *bd) +{ + struct drm_device *dev = bl_get_data(bd); + struct drm_nouveau_private *dev_priv = dev->dev_private; + + return NV_READ(NV50_PDISPLAY_BACKLIGHT); +} + +static int nv50_set_intensity(struct backlight_devi...

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

Forward declare struct backlight_device and remove the include statement. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> Reviewed-by: Jani Nikula <jani.nikula at intel.com> --- include/linux/fb.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/fb.h b/include/linux/fb.h index 2ce2f5c2fca9a..7380d959c5d53 100644 --- a/include/linux/fb.h +++

Does anyone know how to update a Facebook Status with Facebooker?

...-D -D -D -D -D -D -D -D -D -a smartups1250 Network UPS Tools (version 2.2.2) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '9' Attempting firmware lookup Attempting to contact older Smart-UPS version APC - Attempting to find command set update_status Detected Smart-UPS [07025563] on /dev/ttyS0 here is the apcsmart debug output for the 1400: # apcsmart -D -D -D -D -D -D -D -D -D -a smartups1400 Network UPS Tools (version 2.0.3) - APC Smart protocol driver Driver version 1.99.7, command table version 2.0 debug level is '9' Att...

...git a/drivers/gpu/drm/nouveau/nouveau_backlight.c b/drivers/gpu/drm/nouveau/nouveau_backlight.c index 2ffad21..63f3f26 100644 --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c +++ b/drivers/gpu/drm/nouveau/nouveau_backlight.c @@ -174,6 +174,23 @@ static const struct backlight_ops nva3_bl_ops = { .update_status = nva3_set_intensity, }; +int +nouveau_backlight_config(struct nouveau_drm *drm) +{ + struct backlight_device *bd = drm->backlight; + struct nouveau_encoder *nv_encoder = bl_get_data(bd); + struct nouveau_device *device = nv_device(drm->device); + int or = nv_encoder->or; + + if (device...

Hi folks, Today I installed nut on my Dell Poweredge 1800 server running Ubuntu 8.04 Server, with an APC Smart-UPS 1500 connected to it with the black APC cable. I used apt to install nut, upsd -v gives me "Network UPS Tools upsd 2.2.1-" I then copied and configured the config files. Most of the setup seems OK; I get console messages for line power fail / good, and I can do instant

Hello, Quick question on caching based on time based expiration. Is this something that rails supports? Is there a way to instruct rails to refetch the new page after a time period or do we actually have to spawn a background process and have it expire the pages. Thanks, Sam. -- Posted via http://www.ruby-forum.com/.

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

...drivers/apcsmart.h: comsetics - adjust tabs and add basic modeline drivers/apcsmart.h: add compat hardware, add commands apcsmart: remove APC_IGNORE drivers/apcsmart.c: cosmetics drivers/apcsmart: adjust ignored chars and handle over/~over drivers/apcsmart.c: remove status_commit() from update_status() drivers/apcsmart: adjust how firmware_table_lookup() handles 'b' and 'V' drivers/dstate: add dstate_getflags() drivers/apcsmart: add APC_USERCTRL and APC_CRUCIAL drivers/apcsmart.c: add sdcmd_*() sdok() drivers/apcsmart.c: add upsdrv_shutdown_advanced() and upsdrv_shutdo...