Displaying 20 results from an estimated 3000 matches similar to: "APC Back-UPS ES 700 under FreeBSD"
2008 Dec 19
2
Kernel not mounting root
Hi all,
I did cvsup to 7-STABLE yesterday, build, installed and booted a new
kernel then buildworld.
Then I noticed that my PS/2 keyboard is not working at the loader menu
so I booted multiuser and did the make installworld part from there.
Then I tried to reboot but now it hangs after the line
Trying to mount root from ufs:/dev/ad4s1a
It sits there for at least 10min. I tried so far:
-
2007 Jan 03
1
Curitel PC5740 Wireless Modem (EVDO)
Dear Sir,
I am attempting to get a Broad Band Modem working on:
sony# uname -a
FreeBSD sony.family.hom 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2:
Tue Dec 19 16:55:50 EST 2006
root@sony.family.hom:/usr/obj/usr/src/sys/SONY01 i386
The device is a Sprint PC5740 pc card. When I perform a "man umodem"
the card is listed (vendor = Curitel)
UMODEM(4)
2009 Oct 06
1
NUT UPS monitor & APC Back UPS CS-350 (nut-2.2.2p1) on OpenBSD
Hallo,
Following the tips found at https://calomel.org/nut_ups.html I was trying to
make NUT operate "APC Back UPS CS-350". The device introduces itself as:
#v+
ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I
USB FW:q7" rev 1.10/0.06 addr 2
#v-
My config:
#v+
[apc]
driver = usbhid-ups
port = /dev/ugen0.00
pollfreq =
2009 Oct 06
1
NUT UPS monitor & APC Back UPS CS-350 (nut-2.2.2p1) on OpenBSD
Hallo,
Following the tips found at https://calomel.org/nut_ups.html I was trying to
make NUT operate "APC Back UPS CS-350". The device introduces itself as:
#v+
ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I
USB FW:q7" rev 1.10/0.06 addr 2
#v-
My config:
#v+
[apc]
driver = usbhid-ups
port = /dev/ugen0.00
pollfreq =
2009 Jan 02
2
powerware 5110 and openbsd
Hello all!
I've been trying to get my UPS working with my OpenBSD stable box and I haven't had any luck yet.
dmesg shows that I have something from Powerware
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
biomask f5fd netmask fffd ttymask ffff
ugen0 at uhub0 port 1 "Powerware Powerware UPS" rev 0.20/0.50 addr 2
nut version
2010 Jan 10
1
Eaton PW5110 + nut-2.4.1 + OpenBSD
Hello,
I 'm trying to set up an Eaton PW5110 using nut-2.4.1 in OpenBSD, my
ups.conf follows :
[myups]
driver = bcmxcp_usb
port = auto
desc = "Eaton PW 5110 (1500VA)"
My first attempt to run upsdrvctl ended up complaining about unimplemented
usb_clear_halt() in libusb. I patched libusb-0.1.12 with the following
patch :
2010 Sep 26
3
Cannot connect to APC Smart via USB under FreeBSD
Hi, folks!
There is FreeBSD 7.1, NUT 2.4.1, UPS APC Smart 2200 XL.
NUT is compiled from ports with following options:
---------------------------------------
_OPTIONS_READ=nut-2.4.1_5
WITH_SERIAL=true
WITH_USB=true
WITH_SNMP=true
WITHOUT_NEON=true
WITHOUT_PDU=true
WITHOUT_HAL=true
WITHOUT_IPV6=true
WITHOUT_CGI=true
---------------------------------------
UPS is successfully recognized by OS
2009 Jul 26
1
Problems connecting via USB to APC Back-UPS ES 700 (Model BE700-GR)
hi list,
im running debian/testing(act. squeeze) with 2.6.26-2-amd64 kernel. first
tried apcupsd what flawlessly worked but because i run nagios (needs nut
running for 'check_ups'), im trying to run nut.
dmesg and syslog show the device:
Jul 27 00:08:06 kate kernel: [16001.477941] hiddev96hidraw0: USB HID v1.10
Device [APC Back-UPS ES 700 FW:829.D3 .I USB FW:D3 ] on usb-0000:00:1d.1-1
2011 Dec 22
1
[HCL] MGE Pulsar Evolution 1100 - not recognized by USB driver
(Sorry, I accidentally discarded the wrong message in the moderation queue - please subscribe to the list to avoid this in the future.)
> From: <onyx at netfusion.fr>
> Subject: [HCL] MGE Pulsar Evolution 1100 - not recognized by USB driver
> Date: December 22, 2011 12:15:16 AM EST
> To: <nut-upsuser at lists.alioth.debian.org>
>
>
> Hi everybody,
>
> It
2012 Nov 08
1
APC Back UPS ES 700
Hello!
I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have
got some news.
This device is detected by nut-scanner as:
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 "
serial =
2009 Jul 19
1
Problem with nut 2.4.1 & Ippon 2000 Smart power on FreeBSD
Hi all!
Maybe possible adds something in megatec_usb driver for normal working
with ippon 2000?
This is output for drivers megatec_usb and blazer_usb:
===========================================================
gate# /usr/local/libexec/nut/megatec_usb -DDDD -a IPPON
Network UPS Tools - Megatec protocol driver 1.6 (2.4.1)
Serial-over-USB transport layer 0.10
debug level is '4'
Checking
2007 Mar 04
1
OMNIVS1500XL and FreeBSD
I'm running FreeBSD 6.2 with Nut 2.0.5 installed from ports...
I have a TrippLite OmniVS1500XL plugged in, but I'm having little luck with the
tripplite_usb module. I have already built and booted a new kernel with UHID
disabled so that libusb can grab /dev/ugen0.
At first I was able to get the following out of the driver:
# USB_DEBUG=5 /usr/local/libexec/nut/tripplite_usb -u root
2004 Dec 18
4
Free World Dialup and Asterisk
Hi forum,
I have been fighting days and days configuring FWD and asterisk with NO success
I have the following scenario.
My sister in Spain with FWD dialup client
My question is if she can dial my FWD dialup number, which is registered in Asterisk and the call being forwarded to ring my IP Phone.
Spain LAN
FWD
2009 Sep 05
1
FreeBSD, NUT OmniVS1500
Howdy,
I had this working with lots of help for a developer before (Charles Lepple),
but after upgrading to a somewhat more current version of FreeBSD the
patched-up version stopped working. Seeing as this was more than a few years
ago, I thought I'd give a new libusb and NUT a try to see if it might work out
of the box. So far, no luck.
Some info:
FreeBSD 6.3
libusb 0.1.12
NUT 2.4.1
2006 May 22
3
USB UPS and FreeBSD
I am looking at the newhid driver for this Pulsar EXtreme here but it gives
odd results, for example there is no status variable :)
eg
debug level is '2'
Checking device (0463/FFFF) (/dev/usb0//dev/ugen0)
- VendorID: 0463
- ProductID: ffff
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: /dev/usb0
Trying to match device
Device matches
HID descriptor retrieved
2007 Feb 16
5
MGE Nova AVR 600 USB on FreeBSD
Hi,
I've seen a few emails in the archives about problems polling MGE UPSs
via USB under FreeBSD, but unfortunately I didn't find a solution in
them that works for me.
A few details about my setup.. The UPS is a MGE Nova AVR 600 connected
via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5)
and the svn trunk but have had no success yet. I am running nut as
root to
2007 Feb 16
5
MGE Nova AVR 600 USB on FreeBSD
Hi,
I've seen a few emails in the archives about problems polling MGE UPSs
via USB under FreeBSD, but unfortunately I didn't find a solution in
them that works for me.
A few details about my setup.. The UPS is a MGE Nova AVR 600 connected
via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5)
and the svn trunk but have had no success yet. I am running nut as
root to
2008 Aug 20
1
FreeBSD usbhid-ups problem
Hi,
I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works
OK
to begin with but after an hour or so it dies, eg..
Starts out OK..
debug level is '2'
upsdrv_initups...
Checking device (0463/FFFF) (/dev/usb2//dev/ugen0)
- VendorID: 0463
- ProductID: ffff
- Manufacturer: MGE UPS SYSTEMS
- Product: ELLIPSE
- Serial Number: 000000000
- Bus: /dev/usb2
Trying to match device
2003 Jun 11
1
Palm m50x & the USB stack
[It seems the last time this came up was in march, under the heading of "Sony
Cybershot should be in hardware notes". This message is intended mainly to
document what I've managed to track down.]
The m500s still will not sync with pilot-link 0.11.7 in -STABLE. An easily
triggerable panic is another issue [1]. The pilot-link code first opens
/dev/ugenX and then switches to
2013 Aug 07
3
Documentation error: wrong permissions given in FAQ
Hi,
I discovered yesterday that the instructions given at http://www.openssh.org/faq.html#3.14 regarding the correct permissions for the authorized_keys file mistakenly recommend chmod'ing the file to 600 when it should be 644. The requirement for public key authentication to work is in fact that ~/.ssh/authorized_keys is readable (but not writable) by group and other, not just owner. Someone