Accessing a USB device

Accessing a USB device

[Charles Hallenbeck]

I am trying for the first time to access a USB device and having a 
problem doing so. The device is my new UPS from American Power 
Conversion, which I plan to monitor with a program called apcupsd. The 
manual describes how to configure my system for USB and how to test the 
USB interface before running the program, and that is where I am stuck.

It appears to me to be an interrupt problem. Here is why I think so. For 
the past month or two I have noticed a peculiarity that happens within 
about a minute after booting up the computer. Normally I start logging 
in various users on difference consoles, and while I am doing that, I 
get a spontaneous message saying that IRQ 5 is being disabled. The 
message says something cute like, "Nobody cares!" and then disables IRQ 
5. Examining the IRQ assignments, I see that the only device assigned to 
that IRQ shown in /proc/interrupts is the uhci-hcd driver. That has not 
been a problem until now, since until now I have not attempted to access 
a USB device, which requires the uhci-hcd driver.

When I plug the cable from my UPS into a USB slot, the device is 
correctly identified by manufacturer, serial number, etc., but then it 
says that it fails to register with usbcore. And the test program 
confirms that the device cannot be accessed.

My kernel is 2.6.11.6, and all the relevant drivers are compiled into 
the kernel. It looks to me like the uhci-hcd driver has been assigned to 
IRQ 5 but is not responding to that interrupt when it occurs. If someone 
has seen this kind of thing before, or has any suggestion how to proceed 
with troubleshooting this one, I would sure appreciate hearing about it. 
The software I plan to run to monitor the UPS is not involved here as 
yet, since I have to resolve the USB interface to the UPS before there 
is a hope in hell of that software working. If it would be of value to 
share any of the error messages or other data, I would be happy to do 
so.

Any ideas? I have run out.

Chuck


-- 
The Moon is Full
But you can still get downloads from http://www.mhcable.com/~chuckh

Re: Accessing a USB device

[Joseph C. Lininger]

Chuck,
In order to help you out, I need to see the following information. You
can send it to me privately so as not to clutter the list. We can then
post a solution to the list if people are interested. For all these
tests, do them as root after the usb device is plugged in.

1. The output from the command "dmesg"
2. The output of the command "lsusb -v"
3. A complete listing of your /dev directory, including all
subdirectories. This command will give you what I want. "find /dev"

Equal causes can produce very unequal effects.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7

And so it came to pass that on Wed, 22 Jun 2005, Charles Hallenbeck said

> I am trying for the first time to access a USB device and having a
problem
> doing so. The device is my new UPS from American Power Conversion,
which I
> plan to monitor with a program called apcupsd. The manual describes
how to
> configure my system for USB and how to test the USB interface before
running
> the program, and that is where I am stuck.
>
> It appears to me to be an interrupt problem. Here is why I think so.
For the
> past month or two I have noticed a peculiarity that happens within
about a
> minute after booting up the computer. Normally I start logging in
various
> users on difference consoles, and while I am doing that, I get a
spontaneous
> message saying that IRQ 5 is being disabled. The message says
something cute
> like, "Nobody cares!" and then disables IRQ 5. Examining the IRQ
assignments,
> I see that the only device assigned to that IRQ shown in
/proc/interrupts is
> the uhci-hcd driver. That has not been a problem until now, since
until now I
> have not attempted to access a USB device, which requires the uhci-hcd
> driver.
>
> When I plug the cable from my UPS into a USB slot, the device is
correctly
> identified by manufacturer, serial number, etc., but then it says that
it
> fails to register with usbcore. And the test program confirms that the
device
> cannot be accessed.
>
> My kernel is 2.6.11.6, and all the relevant drivers are compiled into
the
> kernel. It looks to me like the uhci-hcd driver has been assigned to
IRQ 5
> but is not responding to that interrupt when it occurs. If someone has
seen
> this kind of thing before, or has any suggestion how to proceed with
> troubleshooting this one, I would sure appreciate hearing about it.
The
> software I plan to run to monitor the UPS is not involved here as yet,
since
> I have to resolve the USB interface to the UPS before there is a hope
in hell
> of that software working. If it would be of value to share any of the
error
> messages or other data, I would be happy to do so.
>
> Any ideas? I have run out.
>
> Chuck
>
>
> --
> The Moon is Full
> But you can still get downloads from http://www.mhcable.com/~chuckh
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Accessing a USB device

[hank]

how do you access a usb flash drive?
----- Original Message ----- 
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Cc: "Speakup Distribution List" <speakup@speech.braille.uwo.ca>
Sent: Wednesday, June 22, 2005 10:07 AM
Subject: Re: Accessing a USB device


> Chuck,
> In order to help you out, I need to see the following information. You
> can send it to me privately so as not to clutter the list. We can then
> post a solution to the list if people are interested. For all these
> tests, do them as root after the usb device is plugged in.
> 
> 1. The output from the command "dmesg"
> 2. The output of the command "lsusb -v"
> 3. A complete listing of your /dev directory, including all
> subdirectories. This command will give you what I want. "find /dev"
> 
> Equal causes can produce very unequal effects.
> Joseph C. Lininger
> jbahm@pcdesk.net
> Verification: 5eab38a77ac40416e075be8f50607ff7
> 
> And so it came to pass that on Wed, 22 Jun 2005, Charles Hallenbeck said
> 
>> I am trying for the first time to access a USB device and having a
> problem
>> doing so. The device is my new UPS from American Power Conversion,
> which I
>> plan to monitor with a program called apcupsd. The manual describes
> how to
>> configure my system for USB and how to test the USB interface before
> running
>> the program, and that is where I am stuck.
>>
>> It appears to me to be an interrupt problem. Here is why I think so.
> For the
>> past month or two I have noticed a peculiarity that happens within
> about a
>> minute after booting up the computer. Normally I start logging in
> various
>> users on difference consoles, and while I am doing that, I get a
> spontaneous
>> message saying that IRQ 5 is being disabled. The message says
> something cute
>> like, "Nobody cares!" and then disables IRQ 5. Examining the IRQ
> assignments,
>> I see that the only device assigned to that IRQ shown in
> /proc/interrupts is
>> the uhci-hcd driver. That has not been a problem until now, since
> until now I
>> have not attempted to access a USB device, which requires the uhci-hcd
>> driver.
>>
>> When I plug the cable from my UPS into a USB slot, the device is
> correctly
>> identified by manufacturer, serial number, etc., but then it says that
> it
>> fails to register with usbcore. And the test program confirms that the
> device
>> cannot be accessed.
>>
>> My kernel is 2.6.11.6, and all the relevant drivers are compiled into
> the
>> kernel. It looks to me like the uhci-hcd driver has been assigned to
> IRQ 5
>> but is not responding to that interrupt when it occurs. If someone has
> seen
>> this kind of thing before, or has any suggestion how to proceed with
>> troubleshooting this one, I would sure appreciate hearing about it.
> The
>> software I plan to run to monitor the UPS is not involved here as yet,
> since
>> I have to resolve the USB interface to the UPS before there is a hope
> in hell
>> of that software working. If it would be of value to share any of the
> error
>> messages or other data, I would be happy to do so.
>>
>> Any ideas? I have run out.
>>
>> Chuck
>>
>>
>> --
>> The Moon is Full
>> But you can still get downloads from http://www.mhcable.com/~chuckh
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.7.11/26 - Release Date: 6/22/2005
> 
>

Re: Accessing a USB device

[Janina Sajka]

hank writes:
> how do you access a usb flash drive?


Mount it and access like any other file system.

If unsure where to mount, check the output of dmesg. Unless you have
other scsi devices, it's likely going to show up as /dev/sda.

Re: Accessing a USB device

[Charles Hallenbeck]

On Thu, 23 Jun 2005, Janina Sajka wrote:

> hank writes:
>> how do you access a usb flash drive?
>
>
> Mount it and access like any other file system.
>
> If unsure where to mount, check the output of dmesg. Unless you have
> other scsi devices, it's likely going to show up as /dev/sda.

I think he was asking about a USB device. Would they use a SCSI device 
name? I have all this to look forward to once I get my UPS interface to 
work.

Chuck


-- 
The Moon is Waning Gibbous (95% of Full)
But you can still get downloads from http://www.mhcable.com/~chuckh

Re: Accessing a USB device

[hank]

I am wanting to mount my usb flash drive
----- Original Message ----- 
From: "Charles Hallenbeck" <chuckh@hhs48.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, June 23, 2005 4:36 PM
Subject: Re: Accessing a USB device


> On Thu, 23 Jun 2005, Janina Sajka wrote:
> 
>> hank writes:
>>> how do you access a usb flash drive?
>>
>>
>> Mount it and access like any other file system.
>>
>> If unsure where to mount, check the output of dmesg. Unless you have
>> other scsi devices, it's likely going to show up as /dev/sda.
> 
> I think he was asking about a USB device. Would they use a SCSI device 
> name? I have all this to look forward to once I get my UPS interface to 
> work.
> 
> Chuck
> 
> 
> -- 
> The Moon is Waning Gibbous (95% of Full)
> But you can still get downloads from http://www.mhcable.com/~chuckh
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.8.0/27 - Release Date: 6/23/2005
> 
>

Re: Accessing a USB device

[Doug Sutherland]

Yes, USB flash disks appear as a SCSI drive. But the USB mass storage
driver must be loaded. Check if it's loaded like this:
lsmod | grep -i usb

usb-storage  52236   0  (unused)
scsi_mod     92488   3  [usb-storage sr_mod ide-scsi]

If the usb-storage is not listed, load it:
modprobe usb-storage

Make a mount point for the flash disk:
mkdir /mnt/flash

And then mount the disk
mount /dev/sda1 /mnt/flash

This assumes you don't have any other SCSI disks, if you do
then the flash disk will not be /dev/sda1.

Also note that you may need msdos and/or vfat kernel support
if the flash disk has a FAT file system.


hank wrote:
 >>I am wanting to mount my usb flash drive

Chuck wrote:
 > I think he was asking about a USB device. Would they use a SCSI 
device name?

Re: Accessing a USB device

[Janina Sajka]

Yes, usb uses scsi names.

Actually works very well, in my experience. You can put a statement in
/etc/fstab and get automounts, e.g.:

/dev/sda /jetflash auto noauto,users,rw

Chuck Hallenbeck writes:
> On Thu, 23 Jun 2005, Janina Sajka wrote:
> 
> >hank writes:
> >>how do you access a usb flash drive?
> >
> >
> >Mount it and access like any other file system.
> >
> >If unsure where to mount, check the output of dmesg. Unless you have
> >other scsi devices, it's likely going to show up as /dev/sda.
> 
> I think he was asking about a USB device. Would they use a SCSI device 
> name? I have all this to look forward to once I get my UPS interface to 
> work.
> 
> Chuck
> 
> 
> -- 
> The Moon is Waning Gibbous (95% of Full)
> But you can still get downloads from http://www.mhcable.com/~chuckh
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more.

Re: Accessing a USB device

[Janina Sajka]

Do you have an uhci-hcd module loaded? I have the following statement in my
(Fedora) /etc/modprobe.conf:

alias usb-controller uhci-hcd

I found the following web site helpful, by the way:

http://www.linux-usb.org/USB-guide/book1.html

Chuck Hallenbeck writes:
> I am trying for the first time to access a USB device and having a 
> problem doing so. The device is my new UPS from American Power 
> Conversion, which I plan to monitor with a program called apcupsd. The 
> manual describes how to configure my system for USB and how to test the 
> USB interface before running the program, and that is where I am stuck.
> 
> It appears to me to be an interrupt problem. Here is why I think so. For 
> the past month or two I have noticed a peculiarity that happens within 
> about a minute after booting up the computer. Normally I start logging 
> in various users on difference consoles, and while I am doing that, I 
> get a spontaneous message saying that IRQ 5 is being disabled. The 
> message says something cute like, "Nobody cares!" and then disables IRQ 
> 5. Examining the IRQ assignments, I see that the only device assigned to 
> that IRQ shown in /proc/interrupts is the uhci-hcd driver. That has not 
> been a problem until now, since until now I have not attempted to access 
> a USB device, which requires the uhci-hcd driver.
> 
> When I plug the cable from my UPS into a USB slot, the device is 
> correctly identified by manufacturer, serial number, etc., but then it 
> says that it fails to register with usbcore. And the test program 
> confirms that the device cannot be accessed.
> 
> My kernel is 2.6.11.6, and all the relevant drivers are compiled into 
> the kernel. It looks to me like the uhci-hcd driver has been assigned to 
> IRQ 5 but is not responding to that interrupt when it occurs. If someone 
> has seen this kind of thing before, or has any suggestion how to proceed 
> with troubleshooting this one, I would sure appreciate hearing about it. 
> The software I plan to run to monitor the UPS is not involved here as 
> yet, since I have to resolve the USB interface to the UPS before there 
> is a hope in hell of that software working. If it would be of value to 
> share any of the error messages or other data, I would be happy to do 
> so.
> 
> Any ideas? I have run out.
> 
> Chuck
> 
> 
> -- 
> The Moon is Full
> But you can still get downloads from http://www.mhcable.com/~chuckh
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more.

Re: Accessing a USB device

[Charles Hallenbeck]

Hi Janina,

Thanks for the URL. I have built the uhci_hcd driver into the kernel, 
and have selected usb_hid, usb_hiddev, usb_devicefs, and so on, and the 
software components seem to be in place. But something very strange is 
going on with my hardware. I cannot figure out why IRQ 5 is misbehaving 
and becoming disabled shortly after bootup. The uhci_hcd driver wants to 
use IRQ 5, but when it fails, communication with the UPS fails. I can 
still "see" the device. Unplugging it produces a disconnect message, and 
plugging it back in produces a recognition message with make and model 
of the UPS displayed, followed by a "failed to register" message.

I have been relying on the very extensive manual accompanying the 
software I want to use, "apcupsd," but will give the web site a look 
that you mentioned.

Joseph L. thinks it is a kernel configuration problem, but I'm damned if 
I can figure out what. I am running 2.6.11.11 on this Debian system, 
although the kernel is not a Debian package and I have configured and 
compiled it the old fashioned (Slackware) way! Some old dogs just cannot 
be taught new tricks.

One other anomaly that makes me think Joseph might be correct: My bootup 
messages end with a complaint about an "unknown_bootoption" followed by 
an offset of some sort, but I have only specified the usual 
"speakup_synth=ltlk" option explicitly. If that is what it is 
complaining about, it is a benign message. But if it is something else, 
I cannot imagine what it might be.

Chuck


On Thu, 23 Jun 2005, Janina Sajka wrote:

> Do you have an uhci-hcd module loaded? I have the following statement in my
> (Fedora) /etc/modprobe.conf:
>
> alias usb-controller uhci-hcd
>
> I found the following web site helpful, by the way:
>
> http://www.linux-usb.org/USB-guide/book1.html
>

-- 
The Moon is Waning Gibbous (95% of Full)
But you can still get downloads from http://www.mhcable.com/~chuckh

Re: Accessing a USB device

[Janina Sajka]

Sounds like you've covered the basic points correctly, Chuck. At this
point, it's a search and repair mission, I guess. Sorry I have no wisdom
to add.

Chuck Hallenbeck writes:
> Hi Janina,
> 
> Thanks for the URL. I have built the uhci_hcd driver into the kernel, 
> and have selected usb_hid, usb_hiddev, usb_devicefs, and so on, and the 
> software components seem to be in place. But something very strange is 
> going on with my hardware. I cannot figure out why IRQ 5 is misbehaving 
> and becoming disabled shortly after bootup. The uhci_hcd driver wants to 
> use IRQ 5, but when it fails, communication with the UPS fails. I can 
> still "see" the device. Unplugging it produces a disconnect message, and 
> plugging it back in produces a recognition message with make and model 
> of the UPS displayed, followed by a "failed to register" message.
> 
> I have been relying on the very extensive manual accompanying the 
> software I want to use, "apcupsd," but will give the web site a look 
> that you mentioned.
> 
> Joseph L. thinks it is a kernel configuration problem, but I'm damned if 
> I can figure out what. I am running 2.6.11.11 on this Debian system, 
> although the kernel is not a Debian package and I have configured and 
> compiled it the old fashioned (Slackware) way! Some old dogs just cannot 
> be taught new tricks.
> 
> One other anomaly that makes me think Joseph might be correct: My bootup 
> messages end with a complaint about an "unknown_bootoption" followed by 
> an offset of some sort, but I have only specified the usual 
> "speakup_synth=ltlk" option explicitly. If that is what it is 
> complaining about, it is a benign message. But if it is something else, 
> I cannot imagine what it might be.
> 
> Chuck
> 
> 
> On Thu, 23 Jun 2005, Janina Sajka wrote:
> 
> >Do you have an uhci-hcd module loaded? I have the following statement in my
> >(Fedora) /etc/modprobe.conf:
> >
> >alias usb-controller uhci-hcd
> >
> >I found the following web site helpful, by the way:
> >
> >http://www.linux-usb.org/USB-guide/book1.html
> >
> 
> -- 
> The Moon is Waning Gibbous (95% of Full)
> But you can still get downloads from http://www.mhcable.com/~chuckh
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more.

Re: Accessing a USB device

[Ralph W. Reid]

I am not largely familiar with your setup, but I notice that you are
trying to use IRQ 5, which is often used by sound cards.  Could you
possibly have an IRQ conflict with a sound card in your system?  HTH,
and have a _great_ weekend.

On Thu, Jun 23, 2005 at 07:33:42PM -0400, Charles Hallenbeck wrote:
> Hi Janina,
> 
> Thanks for the URL. I have built the uhci_hcd driver into the kernel, 
> and have selected usb_hid, usb_hiddev, usb_devicefs, and so on, and the 
> software components seem to be in place. But something very strange is 
> going on with my hardware. I cannot figure out why IRQ 5 is misbehaving 
> and becoming disabled shortly after bootup. The uhci_hcd driver wants to 
> use IRQ 5, but when it fails, communication with the UPS fails. I can 
> still "see" the device. Unplugging it produces a disconnect message, and 
> plugging it back in produces a recognition message with make and model 
> of the UPS displayed, followed by a "failed to register" message.
> 
> I have been relying on the very extensive manual accompanying the 
> software I want to use, "apcupsd," but will give the web site a look 
> that you mentioned.
> 
> Joseph L. thinks it is a kernel configuration problem, but I'm damned if 
> I can figure out what. I am running 2.6.11.11 on this Debian system, 
> although the kernel is not a Debian package and I have configured and 
> compiled it the old fashioned (Slackware) way! Some old dogs just cannot 
> be taught new tricks.
> 
> One other anomaly that makes me think Joseph might be correct: My bootup 
> messages end with a complaint about an "unknown_bootoption" followed by 
> an offset of some sort, but I have only specified the usual 
> "speakup_synth=ltlk" option explicitly. If that is what it is 
> complaining about, it is a benign message. But if it is something else, 
> I cannot imagine what it might be.
> 
> Chuck
> 
> 
> On Thu, 23 Jun 2005, Janina Sajka wrote:
> 
> >Do you have an uhci-hcd module loaded? I have the following statement in my
> >(Fedora) /etc/modprobe.conf:
> >
> >alias usb-controller uhci-hcd
> >
> >I found the following web site helpful, by the way:
> >
> >http://www.linux-usb.org/USB-guide/book1.html
> >
> 
> -- 
> The Moon is Waning Gibbous (95% of Full)
> But you can still get downloads from http://www.mhcable.com/~chuckh
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
Ralph.  N6BNO.  Wisdom comes from central processing, not from I/O.
rreid@sunset.net  http://personalweb.sunset.net/~rreid
...passing through The City of Internet at the speed of light!
CIRCLE AREA = _pi * r ^ 2

Re: Accessing a USB device

[Charles Hallenbeck]

Hi Ralph,

Nope, not this time. IRQ 5 is used only by three instances of uhci_hcd, 
and although it becomes disabled shortly after bootup, the USB interface 
continues to work anyway. My IRQ assignments look like this:

            CPU0
   0:    2094923    IO-APIC-edge  timer
   1:       2832    IO-APIC-edge  i8042
   2:          0          XT-PIC  cascade
   5:     100000   IO-APIC-level  uhci_hcd, uhci_hcd, uhci_hcd
   8:          4    IO-APIC-edge  rtc
  14:      10277    IO-APIC-edge  ide0
  15:      18332    IO-APIC-edge  ide1
  16:     258202   IO-APIC-level  ohci_hcd, hsfpcibasic2
  17:        329   IO-APIC-level  ohci_hcd, EMU10K1
  18:       1183   IO-APIC-level  ehci_hcd, eth0
  19:    2049001   IO-APIC-level  wctdm
NMI:          0 
LOC:    2094638 
ERR:          0
MIS:          0

I'm not sure why there should be three instances of uhci_hcd, but 
otherwise this layout looks okay to me. The important thing for me is 
that the Digium wctdm card does not have to share an interrupt with 
anybody. That seems critical to asterisk.

Chuck



-- 
The Moon is Waning Gibbous (89% of Full)
But you can still get downloads from http://www.mhcable.com/~chuckh

Re: Accessing a USB device

[Charles Hallenbeck]

Well I'll be dipped!

Suddenly it's working. After writing about my woes I thought I'd try it 
one more time, and at least generate that "failure to register" error. 
When I unplugged the USB cable and plugged it in again, I got this:

usb 2-1: USB disconnect, address 3

usb 2-1: new low speed USB device using ohci_hcd and address 4
hiddev96: USB HID v1.10 Device [APC Back-UPS ES 350 FW:800.e5.D USB 
FW:e5] on usb-0000:00:0b.0-1
*** There used to be an error message appearing right here, but this 
time none. ***

So then I ran the test program, which said I might still have a problem, 
but I went ahead anyway and ran the monitoring daemon, which ran without 
complaint. Next, I ran the "access" program to display the status of my 
UPS, and here is my proud outcome:

APC      : 001,033,0813
DATE     : Thu Jun 23 20:15:27 EDT 2005
HOSTNAME : hhs48
RELEASE  : 3.10.17
VERSION  : 3.10.17 (18 March 2005) debian
UPSNAME  : hhs48
CABLE    : USB Cable
MODEL    : Back-UPS ES 350
UPSMODE  : Stand Alone
STARTTIME: Thu Jun 23 19:58:30 EDT 2005
STATUS   : ONLINE
LINEV    : 118.0 Volts
LOADPCT  :   9.0 Percent Load Capacity
BCHARGE  : 100.0 Percent
TIMELEFT :  42.1 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
LOTRANS  : 088.0 Volts
HITRANS  : 138.0 Volts
ALARMDEL : Always
BATTV    : 13.5 Volts
NUMXFERS : 0
TONBATT  : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
STATFLAG : 0x02000008 Status Flag
MANDATE  : 2005-04-17
SERIALNO : AB0516149651
BATTDATE : 2000-00-00
NOMBATTV :  12.0
FIRMWARE : 00.e5.D USB FW:e5
APCMODEL : Back-UPS ES 350
END APC  : Thu Jun 23 20:15:53 EDT 2005


*** Theoretically I know what all that stuff means. That is, I know 
where to look it up! <smile> ***


Now for my obsessive self flagellation: I don't know why the damn thing 
did not work before, and I don['t know why it is working now. But this 
is looking pretty good to me right now. A prolonged power outage will 
shut my system down gracefully, and will also turn off the UPS itself. I 
will have to do some more configuring to get it to restart unattended 
when power is restored, but the book says I can do that if I want to.

Pretty soon this computer will not need me at all, for anything, and I 
will be FREE!

Chuck



The Moon is Waning Gibbous (95% of Full)
But you can still get downloads from http://www.mhcable.com/~chuckh

Re: Accessing a USB device

[Janina Sajka]

Very cool! All's well that ends well!

I've seen this before, Chuck, where you have to restart once or twice to
get it all working. I've seen it on usb, and elsewhere, too. For the
longest time, my high end audio device worked that way. Had to restart
alsa twice--then everything was fine.

Chuck Hallenbeck writes:
> 
> Well I'll be dipped!
> 
> Suddenly it's working. After writing about my woes I thought I'd try it 
> one more time, and at least generate that "failure to register" error. 
> When I unplugged the USB cable and plugged it in again, I got this:
> 
> usb 2-1: USB disconnect, address 3
> 
> usb 2-1: new low speed USB device using ohci_hcd and address 4
> hiddev96: USB HID v1.10 Device [APC Back-UPS ES 350 FW:800.e5.D USB 
> FW:e5] on usb-0000:00:0b.0-1
> *** There used to be an error message appearing right here, but this 
> time none. ***
> 
> So then I ran the test program, which said I might still have a problem, 
> but I went ahead anyway and ran the monitoring daemon, which ran without 
> complaint. Next, I ran the "access" program to display the status of my 
> UPS, and here is my proud outcome:
> 
> APC      : 001,033,0813
> DATE     : Thu Jun 23 20:15:27 EDT 2005
> HOSTNAME : hhs48
> RELEASE  : 3.10.17
> VERSION  : 3.10.17 (18 March 2005) debian
> UPSNAME  : hhs48
> CABLE    : USB Cable
> MODEL    : Back-UPS ES 350
> UPSMODE  : Stand Alone
> STARTTIME: Thu Jun 23 19:58:30 EDT 2005
> STATUS   : ONLINE
> LINEV    : 118.0 Volts
> LOADPCT  :   9.0 Percent Load Capacity
> BCHARGE  : 100.0 Percent
> TIMELEFT :  42.1 Minutes
> MBATTCHG : 5 Percent
> MINTIMEL : 3 Minutes
> MAXTIME  : 0 Seconds
> LOTRANS  : 088.0 Volts
> HITRANS  : 138.0 Volts
> ALARMDEL : Always
> BATTV    : 13.5 Volts
> NUMXFERS : 0
> TONBATT  : 0 seconds
> CUMONBATT: 0 seconds
> XOFFBATT : N/A
> STATFLAG : 0x02000008 Status Flag
> MANDATE  : 2005-04-17
> SERIALNO : AB0516149651
> BATTDATE : 2000-00-00
> NOMBATTV :  12.0
> FIRMWARE : 00.e5.D USB FW:e5
> APCMODEL : Back-UPS ES 350
> END APC  : Thu Jun 23 20:15:53 EDT 2005
> 
> 
> *** Theoretically I know what all that stuff means. That is, I know 
> where to look it up! <smile> ***
> 
> 
> Now for my obsessive self flagellation: I don't know why the damn thing 
> did not work before, and I don['t know why it is working now. But this 
> is looking pretty good to me right now. A prolonged power outage will 
> shut my system down gracefully, and will also turn off the UPS itself. I 
> will have to do some more configuring to get it to restart unattended 
> when power is restored, but the book says I can do that if I want to.
> 
> Pretty soon this computer will not need me at all, for anything, and I 
> will be FREE!
> 
> Chuck
> 
> 
> 
> The Moon is Waning Gibbous (95% of Full)
> But you can still get downloads from http://www.mhcable.com/~chuckh
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more.