similar to: Question regarding Tripp-Lite omnismart 1050 and Nut

Hey all, I have a triplite 1050 and when I did a test today I saw that the battery bounce from 100 to 80 to 90 to 91 percent before UPSD lost its connection to the UPS. The server then decided that it was time to shut off. The UPS sat at 91% for about 5 min before UPSD lost its connection, so I'm not sure if it wasn't updating its battery.charge... I wasn't sure if this is

I've having trouble understanding the NUT compatibility page. Is it compatible with the OMNISMART300? Or the OMNI900LCD? The compatibility page said for instance SMART550 -- tripplite_usb SmartUPS -- tripplite OMNI650LCD -- usbhid_ups so I'm not sure if an OMNISMART300 is like a Smart, or a SMART, or an OMNI, or even if it's supported at all. Thanks in advance for any help!

2003-06-28 Bandwidth Study - John Todd (jtodd @loligo.com) Purpose: ------------- To obtain a better chart of actual bandwidth usage per codec as seen "on-the-wire" when using IAX2 trunking between two Asterisk telephony servers. Discussion: ------------- Past threads on the asterisk-dev and asterisk-users lists have indicated that the optimal way to save bandwidth on

https://bugzilla.netfilter.org/show_bug.cgi?id=1050 Jozsef Kadlecsik <kadlec at netfilter.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |kadlec at netfilter.org Resolution|---

http://bugzilla.mindrot.org/show_bug.cgi?id=1050 Summary: getrrsetbyname compat broken Product: Portable OpenSSH Version: 4.1p1 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: jakob at rfc.se it

CentOS Errata and Bugfix Advisory 2011:1050 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1050.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: f96bb552de15de498e77c1aa5453ab17 libtdb-1.2.1-6.el5.i386.rpm 49dbfd5b5f175961ae755dcef7f16af1 libtdb-1.2.1-6.el5.x86_64.rpm 79021cb3cf85ca7706c668150026909c

CentOS Errata and Bugfix Advisory 2011:1050 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1050.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: c427ede335c12508a19587405f88a995 libtdb-1.2.1-6.el5.i386.rpm 49690a13221e84a4a1437647a52bd645 libtdb-devel-1.2.1-6.el5.i386.rpm afbe6e54c58e7746ca28f5fc5d8c4594

Hello everyone, I would like to submit a simple patch to let nouveau able to detect GTX 1050 / 1050ti cards. TESTED and WORKING on my computer with my GPU (Gigabyte GTX 1050ti OC edition). drivers/gpu/drm/nouveau/nvkm/engine/device/ base.c gpu_nouveau_gp107.patch 2272a2273,2301 > static const struct nvkm_device_chip > nv137_chipset = { > .name = "GP107", > .bar =

Hello, Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the Mesa-side, you will need >=17.0. Pierre On 02:04 am - May 04 2017, Karl Schmidt wrote: > This is probably the problem > May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 > May

Hi, I am slightly stuck in a corner case I don't know how to debug. I have an optimus setup in a dell xps 9560 with a discrete gpu nvidia geforce 1050 (Pascal - NV130). I installed Fedora and if I do not boot with nouveau.modeset=0, then the computer crashes as soon as I try to start Xorg (I have disabled wayland). So, gdm starts but then as soon as I get into i3 or gnome, the computer

CentOS Errata and Bugfix Advisory 2016:1050 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1050.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a1aa81ebe31aaf61659272f9008b4c25f7ed6c84db4e440564a18e8efd5ebcb5 gnome-terminal-3.14.3-3.el7_2.1.x86_64.rpm

Hi Rowland, Thanks for the advice. I've tried your suggestions, but the problem persists. It's strange that it only happens with Macs. I know this is a Samba list, but have encountered anything like this pertaining to Macs in the past? Many thanks, Louis

Yes, I've tried all of them at this point. I spent some time focusing on SMB2 due to various sources indicating they target it for stability (example: Configure Samba to Work Better with Mac OS X [ https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X] ). Thanks for the suggestion though. I've now been trying out the various Apple specific flags in vfs_fruit (

I notice the Configure Samba to Work Better with Mac OS X has been radically shortened?not sure why, but you may want to look at my original 22 Apr 2019 version in the history. You may want to put vfs objects in Global. Note in the vfs_fruit man page: Be careful when mixing shares with and without vfs_fruit. OS X clients negotiate SMB2 AAPL protocol extensions on the first tcon, so mixing shares

Louis - have you run testparm -s on your server? You don?t show it in your smb.conf, but I assume you have vfs objects = catia fruit streams_xattr there as well as in your [data] share. If you don?t, you should since you have various fruit: parameters in the [global]. The SMB conversation in your Wireshark pcap would be easier to read if you filter on ?smb2? :-) Todd

Dear Todd, Thanks for all of the suggestions, yes testparm comes back fine. It used to complain but, Rowlands original suggestion silenced the complaints, except for one: rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) But that's been around for years before the issue at hand. Wilfred Smith's Wireshark suggestion on Stack Exchange eventually took the focus away

CentOS Errata and Security Advisory 2013:1050 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1050.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c4f2c36592c8829f781741194176da1f12f9404b0b673eac5f7ba2bff9dc8275 php53-5.3.3-13.el5_9.1.i386.rpm

First things first -- I've alluded to this before, but let me be clear -- there is no global database that contains monitor-specific information which is used by any linux drivers. Please forget any notions you had of such a thing existing or being used. The information comes from the EDID blob supplied by the monitor. Presumably hwinfo has a primitive EDID parser, which is where that

On 05/06/2017 12:38 PM, Ilia Mirkin wrote: > The information comes from the EDID blob supplied by the monitor. > Presumably hwinfo has a primitive EDID parser, which is where that > information comes from. A more complete EDID parser is available at > > https://cgit.freedesktop.org/xorg/app/edid-decode/ > > For example, > > $ ./src/edid-decode/edid-decode

This is probably the problem May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 May 3 16:44:45 kernel: [ 7.068401] nouveau E[ DRM] failed to create 0x80000080, -22 May 3 16:44:45 kernel: [ 7.068723] nouveau: probe of 0000:08:00.0 failed with error -22 I can make this card available - if you can tell me an older card that can do the