similar to: Tripp Lite G1000U (0x2007)

On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > 0.016485 Trying megatec protocol... > 0.017411 send: Q1 > 0.252545 read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001 > 0.252589 Status read in 1 tries > 0.252602 Supported UPS detected with megatec protocol > 1.288032 send: Unknown error > 1.288085 Permissions problem: Input/output error

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

Thx Charles, So since this is a new type of UPSonic UPS, do you think the vendor screwed up or is it just some quirk on Freebsd? Yes, if you can look into this I would appreciate it. I do not see anyone else on the Web attempting to use this new device yet.....but....... Regards chris On 2/6/14, 8:24 AM, Charles Lepple wrote: > On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > >>

Hi, Have anybody tried Cyberpower Value 600E (USB) under FreeBSD? usbhid-ups from nut 2.4.1 does not recognize (find) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance

Hello all, I just wanted to dump some info here for the archives. Here's the original thread for reference: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-March/002403.html Charles Lepple did a tremendous amount of work to get my TrippLite USB working on FreeBSD 6.2. I'm running an svn version (nut-2.1.0-r879) to pick up his changes to tripplite_usb. So far, it is

Hi all, I’m new to NUT and have some trouble getting my new UPS to work. Since the HCL listed Powercom UHID models as „green“ I thought buying a Roline (German rebranded Powercom) model would be a good idea. The OS is FreeBSD: FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are

Hello ! Anybody have expirience with Powercom Imperial 1500 VAC (USB interface) ? Under FreeBSD 6.2 it's shown as uhid device: uhid0: POWERCOM CO., LTD. USB to Serial, rev 1.00/0.00, addr 2, iclass 3/0 usbhid-ups doesn't recognize it, and powercom driver doesn't work with uhid device. It seems for me that FreeBSD doesn't support it, so it doesn't create serial device for

On Jul 16, 2019, at 3:52 AM, Patrick M. Hausen wrote: > The OS is FreeBSD: > > FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64 > > This is the device: > > ugen0.6: <POWERCOM Co.,LTD HID UPS

Hi! I'm having problems connecting Ippon Smart power pro 1000 UPS to nut via usb under FreeBSD 7-stable The UPS uses megatec protocol and works fine via RS232 (UPS has RS232 and USB connectors) When I connect USB /dev/uhid0 is created. Tried port=/dev/uhid0 - doesn't work. Kernel rebuild w/o option uhid. On connect I get 2 devices /dev/ugen1, /dev/ugen1.1. Tried both of them.

I have setup a few Asterisk systems for customers using Digium TDM400 cards and Aastra phones. No problems with sound quality at all except at this one site. Every time I try their system I don't hear any problems but they tell me that it is really bad. They describe it a a loud scratching sound. Are there any tests that can be done to pinpoint the problem? Has anyone seen this before? Are

We are new to R and evaluating if we can use it for a project we need to do. We have read that R is not well suited to handle very large data sets. Assuming we have the data prepped and stored in an RDBMS (Oracle, Teradata, SQL Server), what can R reasonably handle from a volume perspective? Are there some guidelines on memory/machine sizing based on data volume? We need to be able to handle

I believe auth-rhosts.c, function check_rhosts_file(), contains a bug that shows up when doing host-based authentication where the client_user name is not the same as the server_user name. Line 76 reads: strlcpy(userbuf, server_user, sizeof(userbuf)); I believe it should read: strlcpy(userbuf, client_user, sizeof(userbuf)); Otherwise later in the function this test will fail: /* Verify that

Hi all, > Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at gmail.com>: > There may be an issue with the uhid driver binding to the device. I can't remember which versions of FreeBSD this affects, though. Unloaded the kmod - did not change anything. But I will configure devd not to load uhid.ko ever, just to be sure. You are implying Ithe uhid driver should not be

I have a network of offices using Asterisk that are connected via IAX2 trunks. The trunks work great for a day or two then for no reason at all one end of the trunk will become UNREACHABLE while the other end is still connected. The only way to fix the problem is to shutdown Asterisk completly then start it backup again. The end that dies is not always the same, some times it is server A and some

2007/3/8, Charles Lepple <clepple-guest@alioth.debian.org>: > Author: clepple-guest > Date: Thu Mar 8 04:15:51 2007 > New Revision: 848 > > Modified: > branches/tl_usb_fbsd/drivers/Makefile.am > branches/tl_usb_fbsd/drivers/libhid-uhid.c > Log: > Work-in-progress... maybe I need to look at how the SHUT subdriver works. > ... simply use the same interface

The purpose of this posting is to summarize the FreeBSD installation procedure from the beginning till the very end. 1. Follow the instructions provided in the How-To prepared by Thierry Thomas (http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt). Please note the following: a) if you are using an USB device, as of NUT 2.2 usbhid-ups completely replaces the legacy hidups driver and provides

The nice folks at work have just provided me with a new, really spiffy, ThinkPad. So, I''m trying to get wireless working under CentOS4 and I''m having trouble. First, I can''t seem to find any rpms to just install (this would be really nice). And, second, when I try to build it from the src.rpm that I pulled from the atrpms repository with "rpmbuild --recompile

My UPS has a usb interface with USB-to-Serial chip. But ucycom driver doesn't recognize it. uhid driver does, but it doesn't help me, I need a virtual com port. (output below is without uhid loaded) What can I do to get it working? udi = '/org/freedesktop/Hal/devices/usb_device_665_5161_noserial' freebsd.device_file = '/dev/ugen1' (string) freebsd.driver =

Hi, I was wondering if anyone was using freebsd-update to manage deployment of custom FreeBSD builds to there systems. Here is the scenario, I have 2 binary build servers at the moment (one for i386 and one for amd64) and currently we stage the deployments of updates on NFS servers at each site. We use make installworld/kernel to update the servers from read only src and obj NFS mounts.