Nut upsdev - Mar 2006 - APC Smart-UPS 1000 RM USB problems with newhidups

Well, after our first real extended power outage, I found out that even 
though the UPS 1000 RM is recognized okay, it does not work properly.  It 
never seems to see any change in UPS status.  It looks very similar to the 
other issue I reported with the APC CyberFort 350.  I never was able to get 
to the bottom of the CyberFort issue, but I'll bet it's the same issue
as we
have with the APC 1000 RM.  Here's what I have done so far:
* Machine is a AMD Athlon, running current Debian stable, 2.4.27 stock 
Debian kernel
* Machine has been verified working with a few APC BackUPS models with 
newhidups
1)  Tested by unplugging the power, right after a fresh boot.  --  Newhidups 
didn't see any change at all
2)  Restarted the driver without rebooting.  --  Still said the UPS was 
online
3)  Stopped the driver, un/replugged the USB cable, restarted driver.  --  
Newhidups saw that it was OB
4)  Plugged in UPS power cable.  --  Newhidups saw battery level going up, 
but still saw OB

Then, I decided to try on my Toshiba Centrino laptop, running Fedora Core 4, 
stock 2.6.11 Fedora kernel.  I started just newhidups with -DD without upsd 
or upsmon.  It did notice all the UPS events and battery level changing, but 
segfaulted after a couple minutes.

Does anyone have any ideas here?  George, I'm also wondering what kernel 
you're running on the box you have attached to your SmartUPS 1000 RM.

> Does anyone have any ideas here?  George, I'm also wondering what
kernel
> you're running on the box you have attached to your SmartUPS 1000 RM.
2.6.12-1.1381_FC3 on Dell PE650 and PE750.

I don't have time to run one down right now, but I've just tried pulling
the
plug and newhidups did go "on battery" and then back "on
line" again.  Our
load graphs seem to be unbroken for at least the last couple of weeks.
-- 
Dr George D M Ross, School of Informatics, University of Edinburgh
    Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ
Mail: gdmr@inf.ed.ac.uk   Voice: +44 131 650 5147   Fax: +44 131 667 7209
 PGP: 1024D/AD758CC5  B91E D430 1E0D 5883 EF6A  426C B676 5C2B AD75 8CC5


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 239 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060315/9b976ae3/attachment.pgp

I was able to do a little more testing today.  I hooked up the UPS to 
another Linux FC4 box, running the newest stock Fedora kernel, 
2.6.14-1.1656_FC4.  I checked out the latest nut Development code from CVS; 
patched upsdrvctl.c so it will compile; and patched libusb.c to shorten 
desc->wDescriptorLength to 1040 if it is reported as 61939 (needed for 1000 
RM).
I set up the config files, and started newhidups and upsd.  I then pulled 
the power cord before running a little loop to monitor ups status using 
upsc.  Pretty soon after pulling the cord, newhidups died.  So, 2.6 behavior 
is not much better than 2.4.  Also, I did try the old hidups driver after 
newhidups died, and it worked fine except for the fact that it started 
adding an extra "0" to the end of the battery.charge line in upsc for
some
reason.  Here is output from the shell running the while loop using 
newhidups:
---  Pulled the power cord before starting typing ---
[root@FC4 clients]# while true; do ./upsc UPS@localhost|egrep 
'^battery.charge:|^battery.runtime:|^ups.status:'; sleep 10; done
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OB DISCHRG
battery.charge: 100
battery.runtime: 4800
ups.status: OB DISCHRG
Error: Driver not connected
Error: Driver not connected
Error: Driver not connected


>Well, after our first real extended power outage, I found out that even 
>though the UPS 1000 RM is recognized okay, it does not work properly.  It 
>never seems to see any change in UPS status.  It looks very similar to the 
>other issue I reported with the APC CyberFort 350.  I never was able to get 
>to the bottom of the CyberFort issue, but I'll bet it's the same
issue as
>we have with the APC 1000 RM.  Here's what I have done so far:
>* Machine is a AMD Athlon, running current Debian stable, 2.4.27 stock 
>Debian kernel
>* Machine has been verified working with a few APC BackUPS models with 
>newhidups
>1)  Tested by unplugging the power, right after a fresh boot.  --  
>Newhidups didn't see any change at all
>2)  Restarted the driver without rebooting.  --  Still said the UPS was 
>online
>3)  Stopped the driver, un/replugged the USB cable, restarted driver.  --  
>Newhidups saw that it was OB
>4)  Plugged in UPS power cable.  --  Newhidups saw battery level going up, 
>but still saw OB
>
>Then, I decided to try on my Toshiba Centrino laptop, running Fedora Core 
>4, stock 2.6.11 Fedora kernel.  I started just newhidups with -DD without 
>upsd or upsmon.  It did notice all the UPS events and battery level 
>changing, but segfaulted after a couple minutes.
>
>Does anyone have any ideas here?  George, I'm also wondering what kernel
>you're running on the box you have attached to your SmartUPS 1000 RM.
>
>
>
>_______________________________________________
>Nut-upsdev mailing list
>Nut-upsdev@lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev

I'm on vacation. The bugs you are reporting sound serious; I'll
investigate after I get back home, in late March at the earliest.

Greetings from Kerman, Iran, -- Peter

Justin Maggard wrote:
> 
> Well, after our first real extended power outage, I found out that even 
> though the UPS 1000 RM is recognized okay, it does not work properly.  It 
> never seems to see any change in UPS status.  It looks very similar to the 
> other issue I reported with the APC CyberFort 350.  I never was able to get
> to the bottom of the CyberFort issue, but I'll bet it's the same
issue as we
> have with the APC 1000 RM.  Here's what I have done so far:
> * Machine is a AMD Athlon, running current Debian stable, 2.4.27 stock 
> Debian kernel
> * Machine has been verified working with a few APC BackUPS models with 
> newhidups
> 1)  Tested by unplugging the power, right after a fresh boot.  -- 
Newhidups
> didn't see any change at all
> 2)  Restarted the driver without rebooting.  --  Still said the UPS was 
> online
> 3)  Stopped the driver, un/replugged the USB cable, restarted driver.  --  
> Newhidups saw that it was OB
> 4)  Plugged in UPS power cable.  --  Newhidups saw battery level going up, 
> but still saw OB
> 
> Then, I decided to try on my Toshiba Centrino laptop, running Fedora Core
4,
> stock 2.6.11 Fedora kernel.  I started just newhidups with -DD without upsd
> or upsmon.  It did notice all the UPS events and battery level changing,
but
> segfaulted after a couple minutes.
> 
> Does anyone have any ideas here?  George, I'm also wondering what
kernel
> you're running on the box you have attached to your SmartUPS 1000 RM.
> 
>