similar to: Fwd: "Ever" Company UPS drivers

Dear NUT Developers, First of all I would like to introduce myself, my name is Simon Iwi?ski and for some time right now I'm working in Ever Company that design and builds UPSes from scratch. I'm responsible mostly for proper functionality of "Evers" IT sector but lately also for our dedicated application (called PowerSoft) testing and development. Recently I've heard

After reading that someone had problems with 802.11i/WPA2, I tested my iwi device, too. 802.11i (as client) works, but disconnects about every five minutes briefly, which is nothing new -- I had the same issue with 6.2-RELEASE. In contrast to 6.2-RELEASE, monitor does not work. Kismet does not receive anything, while it does with ath or ural (even at the same time). dmesg with debug.iwi=2 is

Hi, My guess is this: RSAT reads policy definitions either from central store (first) or from local (if first not found). It might be the case, that one of the policies templates was changed between windows 7 and windows 10 and now windows 7 runs into errors. Your error shows that it's trying to look for policy definition in the local store (c:\windows\PolicyDefinitions). You can google

A file creation and corruption bug in XConsole included in procps-X11 versions 1.2.6 and earlier has been found. To fix it, you can either remove the XConsole program or upgrade to procps-1.2.7, available from ftp://tsx-11.mit.edu/pub/linux/sources/usr.bin/procps-1.2.7.tar.gz Thanks to Alan Iwi for finding the bug. A few other bugs have been fixed in this version. Read the NEWS file if you

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 2GB of transfer, files stop being written by Samba. I keep getting Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(656) Jun 12 11:29:37 nasserver smbd[8715]: posix_fcntl_lock: WARNING: lock request at offset 558761983, length 1 returned Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37,

?Order watches, bags here- http://goo.gl/tFhuvb tkhlc xd anmw f plmi tcul o e xuz on rq nbkbs bhcv zkkwb b ozhkp h b givcc jm birjv bbdvf ek wgo bgyt buf yw e g qzby wbexd vevwm pnb c p azugj hlk ieyan pj rc yzcx drqxe mcrcj xlo bnkpt in pw wzurk n ycct tz kt hwsjt nkg jln wocia rh vkt lzn co sjhnr ic c crdz ssh cs vz ddpl hwgmh adtcn trf iv as asbp xmcp moho yo jegpk bj bui x c ddz

Hello, I am trying to get a Wildcard TE110P to work in a relatively modern HP Proliant DL385p Gen8 server. Being a potent 12 core Opteron server I expected no problems. Much to my dismay the dahdi_test results are constantly terrible: # dahdi_test Opened pseudo dahdi interface, measuring accuracy... 89.101% 89.195% 89.142% 88.957% 88.953% 89.115% 89.089% 89.134% 89.066% 89.021% 88.933% 89.044%

Hello all- I have a Digium TE410P in an HP DL145 G2 dual processor server that generates well over 100,000 interrupts per second (sometimes I?ve counted 160,000+ per second) generally resulting in either the system becoming swamped and unusable or the kernel disabling the IRQ the TE410P is on resulting in the spans on that card being unusable. I have confirmed that the card is good by placing it

Hi, after some time without FreeBSD I installed 7.1 on an IBM Thinkpad T30 (with ZFS root on encrypted geli, works great). Config is: FreeBSD hasking.alashan.nongo 7.1-STABLE FreeBSD 7.1-STABLE #3: Thu Feb 5 21:10:45 CET 2009 root@hasking.alashan.nongo:/usr/obj/usr/src/sys/HASKING i386 I tried using my ath based D-Link DWL G650, which still seems to have some issues in regard to interrupt

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

Hi, I have a problem with GPO editing. I have some GPO first created with RSAT and GPO editor on Win 7 x64. I have modified recently this object with RSAT and GPO editor on Win 10 x64 . If I try to edit the GPO back to Win7 I got the following error (in french): La ressource ? $(string.SiteDiscoveryEnableWMI) ? r?f?renc?e dans l?attribut displayName est introuvable. Fichier

Hello, I seem to be having an issue with the configuration of my PRI on a new asterisk server I've created to replace an old install that I have. The card is Digium Wildcard TE133. I continually get messages like "Primary D-Channel on span 1 down", rather irregularly: [2013-07-29 17:31:39] VERBOSE[3621] sig_pri.c: == Primary D-Channel on span 1 up [2013-07-29 17:31:39]

Hello, I almost always get a panic when running kismet on my ipw-Interface under 6.1-PRERELEASE. This has been the case ever since ipw hit the tree. Sometimes kismet works, sometimes it doesn't. A sure way to trigger the panic is to switch between bss/ibss/monitor mode prior to running kismet. Perhaps there is a bug in the re-initialization when loading a different firmware? Is this panic

Dear syslinux list members, I'm a newbie on this list. I hope I don't offend anyone by being slightly off-topic. I had the problem of wanting multiple Linux distros (i.c. Debian, Ubuntu, OpenSuSE, SuSE, RedHat, CentOS, Fedora) installable from a single PXELinux menu, so I wrote a couple of scripts that do what is described below. The question is whether anyone would be interested in

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Author: Darren Moffat <Darren.Moffat at Sun.COM> Repository: /hg/zfs-crypto/gate Latest revision: 957d30a3607ed9f3cbe490da5894d1e1b2104033 Total changesets: 28 Log message: resync onnv_105 partial for 6713916 Files: usr/src/Makefile.lint usr/src/Targetdirs usr/src/cmd/Makefile usr/src/cmd/Makefile.cmd usr/src/cmd/acctadm/Makefile usr/src/cmd/acctadm/acctadm.xcl

" Message from syslogd at localhost at Aug 27 08:57:53 ... kernel:Disabling IRQ #17" is the message I got on all my terminal windows at the time indicated. What is it complaining about? What should I do about it? I got some information from dmesg. It mentions IRQ 17, but the only error is from before the most recent hibernation. Here are some excerpts, in order from dmesg: SELinux:

https://bugs.freedesktop.org/show_bug.cgi?id=87983 Bug ID: 87983 Summary: nouveau E[Xorg.bin[1119]] failed to idle channel 0xcccc0001 on G86 [GeForce 8500 GT] (rev a1) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

https://bugs.freedesktop.org/show_bug.cgi?id=112070 Bug ID: 112070 Summary: H/W Acceleration sufficiently buggy on Debian to hard lock machine GeForce 7600 GO Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: other Status: NEW Severity: critical Priority: not

Hey, I have a nighly build/test system that boots various machines with upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable. After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'') has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'') the PVHVM