Hello,
I inserted a USB multi-cardreader to read my SD cards; I noticed this
upset nut and pptpd a bit:
Aug 27 08:27:59 epia kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 3
Aug 27 08:27:59 epia kernel: usb 3-1: configuration #1 chosen from 1 choice
Aug 27 08:27:59 epia ker
Le samedi 26 août 2006 19:45, Peter Selinger a écrit :
> Marc Collin wrote:
> > linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc
> > [EMAIL PROTECTED] driver.name: newhidups
> > driver.parameter.port: /dev/hiddev0
> > driver.version: 2.1.0
> > driver.version.data: PowerCom HID 0.1
> >
On 8/26/06, Marc Collin <[EMAIL PROTECTED]> wrote:
chmod 0600 /dev/hiddev0
chown ups:ups /dev/hiddev0
FYI, the above commands are effectively a no-op...
if i check /dev/hiddev0 seem to have disapear
...because we disable the kernel HID driver for the UPS. You may use
'auto' or anything else
On Friday 25 August 2006 19:23, Johan Pramming wrote:
> True, thanks for pointing out my shell scripting skills :D
Heh :)
> >I have ondelay = 13 and offdelay = 120 in my ups.conf (MGE Pulsar EX) so
> >the
> >system gets 2 minutes to shut down gracefully.
>
> Much better solution, I think that is
Marc Collin wrote:
>
> linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc [EMAIL
> PROTECTED]
> driver.name: newhidups
> driver.parameter.port: /dev/hiddev0
> driver.version: 2.1.0
> driver.version.data: PowerCom HID 0.1
> driver.version.internal: 0.30
> powercom.coll2.feature3: 1
> p
Le samedi 26 août 2006 09:13, Peter Selinger a écrit :
> You did "make install", right? (Else upsdrvctl might be trying to
> start an older version of the driver).
./configure --with-user=ups
make
make usb
make install
make install-usb
mkdir -p /var/state/ups
chmod 0700 /var/state/ups
chown nut
That is very odd indeed. Why should the system shut off abruptly? If
the log shows nothing, then it seems that the UPS just turned off the
power.
I recommend testing this while attaching, say, a lamp to the UPS,
instead of a computer. (You can still use your computer to monitor the
UPS, just don'
Rob wrote:
>> Did you try switching the two machines?
>
> On my system, I only have 1 UPS and I have monitored it in windows and
> in Linux. In windows, the same set of systems will properly wait until
> the designated time to shutdown (>5 minutes). When I boot into Linux,
> my Linux system perf
Udo van den Heuvel wrote:
>
> Hello,
>
> Rob wrote:
> > I've seen the same behavior when using the cpsups driver on Debian
> > Unstable, but haven't had time to try to track it down. Where are the
> > shutdown timings configured? From the manpages it looks to be
> > configured in the driver, bu
Hello,
Rob wrote:
> I've seen the same behavior when using the cpsups driver on Debian
> Unstable, but haven't had time to try to track it down. Where are the
> shutdown timings configured? From the manpages it looks to be
> configured in the driver, but the cpsups driver manpage says it doesn't
I've seen the same behavior when using the cpsups driver on Debian
Unstable, but haven't had time to try to track it down. Where are the
shutdown timings configured? From the manpages it looks to be
configured in the driver, but the cpsups driver manpage says it doesn't
support any options, s
Marc Collin wrote:
>
> changed for
>
> [myups]
>driver = newhidups
>port = /dev/hiddev0
>desc = "Ultra ULT31502"
>
> maybe some information that can be usefull
>
> drivers/newhidups -DDD -u root /dev/hiddev0
... [works]
> when i try to start the driver
>
> /usr/local/
On 8/25/06, Rob Harris <[EMAIL PROTECTED]> wrote:
Charles Lepple wrote:
> On 8/25/06, Rob Harris <[EMAIL PROTECTED]> wrote:
>> - VendorID: 09ae
>> - ProductID: 2005
>
> For Tripp-Lite product IDs other than 1, please use the newhidups
> driver instead.
>
No dice...
Sorry, I thought the Tripp-L
13 matches
Mail list logo
