similar to: Re: unisys UPS using RD, genericups does not

Hello nut-upsuser, Hope, that its might be useful for someone: 1. Kebo UPS-600A Driver: genericups UPStype: 7 Config extras: SD = -RTS or SD = -TX (don't know why but both are suitable) 2. Kebo UPS-1200M Driver: fentonups Config extras: none Note: Looks like twin brother of Microlab UPS-1200M :) Driver ask me to report ID string: "Unknown

I have a unisys UPS, I probed the RS232 and notice that pin 2, (receive data) is going from -6v (OL) to 12v(OB), but I don't see the setting for the genericups. Seems nobody else is using the RD pin? Any driver I can use? Thanks -Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL:

Does anyone know what is the latest version of dom0-kernel, that supports fully xenpm hypercalls? I tried from 3.0 to 3.3 with xen-4.1.3, but none of them has xenpm working. On the other hand native kernel cpufreq is OK with all of them. My CPU is Xeon family 6 on PowerEdge 1950 III box. Regards, Dimitar Kazakov

Does anyone know what is the latest version of dom0-kernel, that supports fully xenpm hypercalls? I tried from 3.0 to 3.3 with xen-4.1.3, but none of them has xenpm working. On the other hand native kernel cpufreq is OK with all of them. My CPU is Xeon family 6 on PowerEdge 1950 III box. Regards, Dimitar Kazakov

The original thread on this ICE, including a link to the bug submitted to MS is here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-December/056683.html Michael From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Sergiy Migdalskiy Sent: Thursday, April 18, 2013 10:28 To: David Blaikie Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Patch to compile LLVM

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Hi, The code @ line 584 of TargetRegistry.h effectively suppresses specifying any AsmStreamer constructor function but stock createAsmStreamer one. Is it by intention or condition should be replaced with != ? Best regards, Max

Anyone know what is the problem for this? thanks Andrew freebsd 540$ /usr/local/etc/rc.d/nut restart nut not running? (check /var/db/nut/upsd.pid). Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - Generic UPS driver 1.32 (2.0.4) UPS type: APC Back-UPS (940-0023A cable) Unable to open /dev/cuad0: Device busy Current user id: uucp (66) Serial port owner: uucp (66) Serial

>From the DeveloperPolicy.html document I gathered I need to send a patch to this list (which I did); could you clarify if I misunderstood it? The second patch is really trivial and I think it's worth applying - it seems like a typo by someone who tested on MSVC 11 but not 10; or maybe my local instance of MSVC10 is somehow deficient, of course. The first patch is adding MSVC-specific

On Wed, Apr 17, 2013 at 11:36 AM, Sergiy Migdalskiy <migdalskiy at hotmail.com> wrote: > In order to get llvm to compile on Windows with MSVC 10, I have to disable > inline on utostr to avoid internal compiler failure, and disable _xgetbv > call in OsSupportsAVX because it's only defined in MSVC 2012 compiler. The > first patch (noinline) is known for many months now. I'm

Hi, Can someone tell me if my understanding is right in that post-RA scheduler currently assumes no limits on a pipeline's issue width? If so, is it by design or just overlooked? I have a case for, say, 1-issue pipeline when certain pipeline resource becomes occupied a few clocks after instruction start, but hazard evaluation is done incorrectly as scheduler advances clock not for every

2008/10/18 Sergiy Yegorov <prapor at unixzone.org.ua>: > Dear Arnaud! Hi Sergiy and Alexey, > Please, check this patch. It adds USB-attached Powercom UPS Imperial & > Black Knight series. Originaly code is writed by Kirill Burdin > (burdin at post.ru) for Imperial UPS`es. > I`m just sysadmin without enought C programming > skills, so I adapted it to nut-2.2.2-6

https://github.com/llvm-mirror/llvm/blob/652375a8cc49615de31fd9d424753795059185b6/lib/Target/NVPTX/NVPTXUtilities.h#L58 Does this solve your problem? On Wed, Dec 21, 2016 at 2:29 PM, Gurunath Kadam via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I am trying to instrument CUDA kernel functions only (llvm-3.9.0). > > Is there a way to identify cuda kernel

Hi, We are trying to convert all mbox mail on our systems to mdbox using dsync, in order to be able to use email sub-folders in Thunderbird. Everything works fine for non-inbox folders, however the inbox folders are not getting converted. We used: *dsync -v convert mbox:~/mail:INBOX=/var/mail/%u* *dovecot --version* 2.0.beta6 (3156315704ef) (shipping with RHEL6/SL6) *dovecot -n* #

Hi, I have two Gluster servers A and B. They are mirrored. I mount A. What happens when server A goes down? I would like for my applications to seamlessly use data from the Gluster storage B. Thanks, Sergiy.

In order to get llvm to compile on Windows with MSVC 10, I have to disable inline on utostr to avoid internal compiler failure, and disable _xgetbv call in OsSupportsAVX because it's only defined in MSVC 2012 compiler. The first patch (noinline) is known for many months now. I'm a casual llvm user, and don't know the proper channels to go through to submit a patch. Could someone tell

Hi! Just an idea. You randomly select the first point. Cut +/- 5 from the original space [0;100]. Select second point. Project it to the original space. Cut again. Repeat. Simplified method without cutting: every time mark +/- 5 as a bad space and select point again if it is in forbidden area. Hope it helps. Regards, Sergiy On Sat, 31 May 2025, 19:52 Brian Smith, <briansmith199312 at

Hi, I am trying to instrument CUDA kernel functions only (llvm-3.9.0). Is there a way to identify cuda kernel functions? I see that in llvm IR for CUDA has nvvm annotations section, where kernel functions are identified for NVPTX usage. I can parse the whole IR for this kernel metadata and then proceed, but this is very clumsy. Other way is to work with cuda-device-only IR. But then I am not

Can we please add this UPS? idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0005 Cyber Power UPS Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150917/0774f0a4/attachment.html>

https://bugzilla.mindrot.org/show_bug.cgi?id=3189 Bug ID: 3189 Summary: channel mux_ctx memory leak Product: Portable OpenSSH Version: 8.3p1 Hardware: ix86 OS: Linux Status: NEW Severity: critical Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org