I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list said I should use either the newhidups or hidups driver. I looked in the installation and I found headers and c files to create these drivers (I think), but in /usr/local/ups/bin there is no driver named, "newhidups or hidups" -- what have I messed up? thanks for your help!!! steve
Steve, use newhidups, not hidups. You should do either this: ./configure --with-drivers=newhidups make (to compile only the newhidups driver - saves a lot of time), or this: ./configure make make usb (to compile all drivers). Note that simply "make" does not compile any USB drivers by default, which is an outdated behavior and one that we should probably change. Arnaud, what is your feeling about the "make usb" target? Does it still serve a useful purpose? Also, are there any situations where the hidups driver is still preferred/needed? Perhaps we should change drivers.txt to encourage people more strongly to use newhidups. -- Peter strong.s@crwash.org wrote:> > I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list > of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list > said I should use either the newhidups or hidups driver. I looked in the > installation and I found headers and c files to create these drivers (I think), > but in /usr/local/ups/bin there is no driver named, "newhidups or hidups" -- > what have I messed up? > > thanks for your help!!! > steve > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser >
Steve,
here is another quote from the INSTALL file:
NOTE: newhidups is a special case for the "port" value. If you
only own one local UBS UPS, you can just set the "port" to
"auto".
Refer to newhidups(8) man page for more information.
The cause of your problem is not the "port" value, which is ignored
anyway. It is more likely that you forgot to follow step 13 from the
INSTALL file (to set up your startup scripts), or that you did not set
them up correctly. You should try
ps -ef | grep ups
as root, to see which ones of "upsmon", "upsd",
"newhidups", if any,
are currently running. The point is that you have to make sure these
are run each time you reboot your system.
-- Peter
Steve Strong wrote:>
> I'm sorry to be such a newbie, but...
>
> So, I issued the make install-usb command and all the drivers suddenly
> were there, and I was able to use upsc to get the status of the ups and
> all seemed okie-dokie. Then, I restarted the server and upsd couldn't
> find the driver. I discovered the problem: in etc/ups.conf my port line
> reads:
>
> port=/proc/bus/usb/005/002
>
> which (naturally) disappears after the restart. Is there some way to
> get around this?
>
> steve
>
> Peter Selinger wrote:
>
> >Steve Strong wrote:
> >
> >
> >>thanks for this reply, BUT...
> >>
> >>I chose option 2:
> >>
> >> * i removed all of the files generated by the build
> >> * i un-tared the source
> >> * i configured for the build with:
> >> o ./configure --with-user=nut
> >> o make
> >> o make usb
> >> * then i ran make install
> >>
> >>but none of the usb drivers showed up in /usr/local/ups/bin
> >>
> >>
> >
> >Sorry, I forgot to mention: If you use this option, you also have to
> >do "make install-usb". In our defense: this is mentioned in
the file
> >INSTALL. However, it is silly, and I will change it to something more
> >intuitive before the next release.
> >
> >
> >
> >>any idea what's going on?
> >>steve
> >>
> >>Peter Selinger wrote:
> >>
> >>
> >>
> >>>Steve,
> >>>
> >>>use newhidups, not hidups. You should do either this:
> >>>
> >>>./configure --with-drivers=newhidups
> >>>make
> >>>
> >>>(to compile only the newhidups driver - saves a lot of time),
or this:
> >>>
> >>>./configure
> >>>make
> >>>make usb
> >>>
> >>>(to compile all drivers). Note that simply "make"
does not compile any
> >>>USB drivers by default, which is an outdated behavior and one
that we
> >>>should probably change.
> >>>
> >>>Arnaud, what is your feeling about the "make usb"
target? Does it
> >>>still serve a useful purpose? Also, are there any situations
where the
> >>>hidups driver is still preferred/needed? Perhaps we should
change
> >>>drivers.txt to encourage people more strongly to use newhidups.
> >>>
> >>>-- Peter
> >>>
> >>>
> >>>strong.s@crwash.org wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>I just installed NUT and my UPS is an APC Back-UPS ES 500.
I looked in the list
> >>>>of drivers and found APC Back-UPS ES 350 listed in
"drivers.txt" -- that list
> >>>>said I should use either the newhidups or hidups driver. I
looked in the
> >>>>installation and I found headers and c files to create
these drivers (I think),
> >>>>but in /usr/local/ups/bin there is no driver named,
"newhidups or hidups" --
> >>>>what have I messed up?
> >>>>
> >>>>thanks for your help!!!
> >>>>steve
> >>>>
> >>>>_______________________________________________
> >>>>Nut-upsuser mailing list
> >>>>Nut-upsuser@lists.alioth.debian.org
> >>>>http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>--
> >>Steve Strong
> >>Math and Computer Science
> >>Washington High School
> >>2205 Forest Dr. SE
> >>Cedar Rapids, IA 52403
> >>http://crwash.org
> >>mailto:strong.s@crwash.org
> >>
> >>
> >>
> >
> >
> >
> >
> >
> >
>
> --
> Steve Strong
> Math and Computer Science
> Washington High School
> 2205 Forest Dr. SE
> Cedar Rapids, IA 52403
> http://crwash.org
> mailto:strong.s@crwash.org
>
P.S.: when you reply, please reply to the mailing list, not to me personally. I am not the only person on the list answering questions. Thanks! -- Peter Steve Strong wrote:> > thanks for this reply, BUT... > > I chose option 2: > > * i removed all of the files generated by the build > * i un-tared the source > * i configured for the build with: > o ./configure --with-user=nut > o make > o make usb > * then i ran make install > > but none of the usb drivers showed up in /usr/local/ups/bin > > any idea what's going on? > steve > > Peter Selinger wrote: > > >Steve, > > > >use newhidups, not hidups. You should do either this: > > > > ./configure --with-drivers=newhidups > > make > > > >(to compile only the newhidups driver - saves a lot of time), or this: > > > > ./configure > > make > > make usb > > > >(to compile all drivers). Note that simply "make" does not compile any > >USB drivers by default, which is an outdated behavior and one that we > >should probably change. > > > >Arnaud, what is your feeling about the "make usb" target? Does it > >still serve a useful purpose? Also, are there any situations where the > >hidups driver is still preferred/needed? Perhaps we should change > >drivers.txt to encourage people more strongly to use newhidups. > > > >-- Peter > > > > > >strong.s@crwash.org wrote: > > > > > >>I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list > >>of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list > >>said I should use either the newhidups or hidups driver. I looked in the > >>installation and I found headers and c files to create these drivers (I think), > >>but in /usr/local/ups/bin there is no driver named, "newhidups or hidups" -- > >>what have I messed up? > >> > >>thanks for your help!!! > >>steve > >> > >>_______________________________________________ > >>Nut-upsuser mailing list > >>Nut-upsuser@lists.alioth.debian.org > >>http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > >> > >> > >> > > > > > > > > > > > > > > -- > Steve Strong > Math and Computer Science > Washington High School > 2205 Forest Dr. SE > Cedar Rapids, IA 52403 > http://crwash.org > mailto:strong.s@crwash.org >