search for: 0x0004

On Nov 11, 2014, at 3:30 PM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Dear Charles and Artem, > > I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. > At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds for indefinite time (the same problem described by Vincenzo Colonnella here: http://lists.alioth.debian.org/pipermail/nut-upsdev/...

Hi Charles, > Sigh, I wish the vendors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached by Alexey Morozov: "(VGD, VRT, RPT, .. and new UPS etc.) - 0X04.". According to this doc we...

...Lines, but i am receiving a lot of times this message . Is a software issue or is a hardware issue ? Regards. Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: Unicall/5 event Alarm Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event: Unicall/5 Alarm masks 0x0000 0x0004 Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event: Unicall/5 Alarm No Alarm raised, Yellow Alarm cleared Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: Unicall/6 event Alarm Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event: Unicall/6 Alarm mas...

...2, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors wouldn't change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. You're right, I jumped to the wrong conclusion on that one. There was another thread about this, where it seems there are other mism...

Dear Charles and Artem, I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds for indefinite time (the same problem described by Vincenzo Colonnella here: http://lists.alioth.debian.org/pipermail/nut-upsdev/2...

On Sep 11, 2014, at 2:50 AM, Khokhlov Artem <khokhlov.a at pcm.ru> wrote: > Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Confused. This commit was added in 2011:

...DW_TAG_base_type [24] DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000051] = "int") DW_AT_encoding [DW_FORM_data1] (0x05) DW_AT_byte_size [DW_FORM_data1] (0x04) 0x00000058: NULL 0x000001ec: Compile Unit: length = 0x0000002b version = 0x0004 abbr_offset = 0x0000 addr_size = 0x08 (next unit at 0x0000021b) 0x0000000b: DW_TAG_type_unit [25] * DW_AT_language [DW_FORM_data2] (0x0004) 0x0000000e: DW_TAG_namespace [9] * It is a bit weird using the same syntax to print the section relative offest for the unit header, then...

...he default settings > > ---------------------------------------------------------------------- > File: out.o (x86_64) > ---------------------------------------------------------------------- > .debug_info contents: > > 0x00000000: Compile Unit: length = 0x0000005b version = 0x0004 abbr_offset = 0x00000000 addr_size = 0x08 (next CU at 0x0000005f) > > 0x0000000b: TAG_compile_unit [1] * > AT_producer( "clang version 3.5.0 (209308)" ) > AT_language( DW_LANG_C_plus_plus ) > AT_name( "test.cc <http://test....

Hey guys, Frederic is introducing the expression dumping support and in the interests of tersity is skipping the "DW_" in every "DW_OP" (heck, we could even skip the "OP" given the context - nothing else textual can appear there, right?) Any thoughts on skipping the "DW_" (maybe even the AT/TAG/FORM too) in the rest of dwarfdump? (skipping the AT/TAG (FORM

...>> ---------------------------------------------------------------------- >> File: out.o (x86_64) >> ---------------------------------------------------------------------- >> .debug_info contents: >> >> 0x00000000: Compile Unit: length = 0x0000005b version = 0x0004 abbr_offset = 0x00000000 addr_size = 0x08 (next CU at 0x0000005f) >> >> 0x0000000b: TAG_compile_unit [1] * >> AT_producer( "clang version 3.5.0 (209308)" ) >> AT_language( DW_LANG_C_plus_plus ) >> AT_name( "test...

...Info (0x2029b0,0x32f37c) trace:dinput:JoystickAImpl_SetProperty (0x2029b0,<guid-0x0005>,0x32f 0b0) trace:dinput:JoystickAImpl_SetProperty deadzone(0) obj=0 trace:dinput:JoystickAImpl_SetProperty (0x2029b0,<guid-0x000a>,0x32f 0b0) trace:dinput:JoystickAImpl_GetProperty (0x2029b0,<guid-0x0004>,0x32f 0c4) trace:dinput:JoystickAImpl_GetProperty range(0, 65535) obj=0 trace:dinput:JoystickAImpl_SetProperty (0x2029b0,<guid-0x0005>,0x32f 0b0) trace:dinput:JoystickAImpl_SetProperty deadzone(0) obj=1 trace:dinput:JoystickAImpl_SetProperty (0x2029b0,<guid-0x000a>,0x32f 0b0) trace:...

...arwin's dwarfdump output with the default settings ---------------------------------------------------------------------- File: out.o (x86_64) ---------------------------------------------------------------------- .debug_info contents: 0x00000000: Compile Unit: length = 0x0000005b version = 0x0004 abbr_offset = 0x00000000 addr_size = 0x08 (next CU at 0x0000005f) 0x0000000b: TAG_compile_unit [1] * AT_producer( "clang version 3.5.0 (209308)" ) AT_language( DW_LANG_C_plus_plus ) AT_name( "test.cc<http://test.cc/>" )...

Hi Attached, patches to implement ListItem. This class, in wxruby 0.6.0, allows styling of individual items in a ListCtrl, via a particularly clunky API. In disambiguating the overloaded ListCtrl#set_item method it introduces one non backwards-compatible change. I''ve followed the WxPython convention as described in the Wx class ref, renaming set_item(index, col, string, imageid) to

...; this message . > Is a software issue or is a hardware issue ? > > Regards. > > Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: > Unicall/5 event Alarm > Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event: > Unicall/5 Alarm masks 0x0000 0x0004 > Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event: > Unicall/5 Alarm No Alarm raised, Yellow Alarm cleared > Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: > Unicall/6 event Alarm > Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_e...

...;max at stro.at> diff --git a/usr/kinit/fstype/ext3_fs.h b/usr/kinit/fstype/ext3_fs.h index 12d64fe..f958e5c 100644 --- a/usr/kinit/fstype/ext3_fs.h +++ b/usr/kinit/fstype/ext3_fs.h @@ -6,12 +6,31 @@ */ #define EXT3_SUPER_MAGIC 0xEF53 +#define EXT2_FLAGS_TEST_FILESYS 0x0004 +#define EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER 0x0001 +#define EXT2_FEATURE_RO_COMPAT_LARGE_FILE 0x0002 +#define EXT2_FEATURE_RO_COMPAT_BTREE_DIR 0x0004 +#define EXT2_FEATURE_INCOMPAT_FILETYPE 0x0002 +#define EXT2_FEATURE_INCOMPAT_META_BG 0x0010 #define EXT3_FEATU...

If wxRuby-SWIG is as usable as wxRuby 0.6.0, maybe it should be given a version number and packaged up for download. Given the nature of SWIG, having a lot more people use it would probably result in more code contributions to this project. Seems most of the changes are 2+ months old, so I''m guessing wxRuby-SWIG is fairly stable right now in terms of frequency of changes...

...vironment: Solaris 8/Sparc, Compiler: Forte 6 Update 2 suggested fix: --- modules/CP437.c Fri Aug 29 17:11:23 2003 +++ modules/CP437.c.orig Fri Aug 29 17:27:09 2003 @@ -24,261 +24,261 @@ #include "includes.h" static const uint16 to_ucs2[256] = { - 0x0001, - 0x0002, - 0x0003, - 0x0004, - 0x0005, - 0x0006, - 0x0007, - 0x0008, - 0x0009, - 0x000A, - 0x000B, - 0x000C, - 0x000D, - 0x000E, - 0x000F, - 0x0010, - 0x0011, - 0x0012, - 0x0013, - 0x0014, - 0x0015, - 0x0016, - 0x0017, - 0x0018, - 0x0019, - 0x001A, - 0x001B, - 0x001C, - 0x001D, - 0x001E, - 0x001F, -...

...39;t access gnome keyring socket: /tmp/keyring-4jRNoE/socket: Permission denied Jun 24 15:30:11 history-20 passwd: gkr-pam: couldn't change password for 'login' keyring: 255 Jun 24 15:30:13 history-20 sshd[4656]: pam_winbind(sshd:setcred): [pamh: 0x1f06f48] ENTER: pam_sm_setcred (flags: 0x0004) Jun 24 15:30:13 history-20 sshd[4656]: pam_winbind(sshd:setcred): [pamh: 0x1f06f48] ENTER: _pam_delete_cred (flags: 0x0004) However, if I set my computer back two days, the timestamps work out. The time on the Windows server is set correctly, and the box even has it's ntpdate set to use the W...

...9;m trying to unify some of the administrative interfaces via mmc, specifically the group policy stuff. When I try to use the Group Policy snap-in to connect to my samba 2.2.1 servers, I see the windows box do a Tree Connect Andx to ADMIN$\System32\GroupPolicy, and then the samba box responds with 0x0004, permission denied. Then the windows box goes and tries to create ADMIN$\System32, which also fails. I have sniffer dumps of the exchange here (libpcap format, use Ethereal to open): http://lightconsulting.com/~thalakan/gpdump.cap Poking around in the samba source code, it looks like ADMIN$ is...

...39;t access gnome keyring socket: /tmp/keyring-4jRNoE/socket: Permission denied Jun 24 15:30:11 history-20 passwd: gkr-pam: couldn't change password for 'login' keyring: 255 Jun 24 15:30:13 history-20 sshd[4656]: pam_winbind(sshd:setcred): [pamh: 0x1f06f48] ENTER: pam_sm_setcred (flags: 0x0004) Jun 24 15:30:13 history-20 sshd[4656]: pam_winbind(sshd:setcred): [pamh: 0x1f06f48] ENTER: _pam_delete_cred (flags: 0x0004) However, if I set my computer back two days, the timestamps work out. The time on the Windows server is set correctly, and the box even has it's ntpdate set to use the W...