From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpauth06.mail.atl.earthlink.net ([209.86.89.66]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1Dl8xp-0002Tj-00 for ; Wed, 22 Jun 2005 13:24:37 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=B+uIjmliFCP56zleuCzGcOHR5fZTpjTarNqUV6OqHC3DoU+jEC2kgwL8DP1aNw+q; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP; Received: from [67.185.140.244] (helo=home9rs6sced6q) by smtpauth06.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1Dl8xp-0002Ab-9N for speakup@braille.uwo.ca; Wed, 22 Jun 2005 13:24:37 -0400 Message-ID: <001d01c5774f$47c790f0$650fa8c0@home9rs6sced6q> From: "hank" To: "Speakup is a screen review system for Linux." References: Date: Wed, 22 Jun 2005 10:24:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-ELNK-Trace: 26c683a02984a6448aa916b1a551c5b9239a348a220c260993fbb176c2bd1ad9bb5052756bf6a31d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 67.185.140.244 Subject: Re: Accessing a USB device X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2005 17:24:38 -0000 how do you access a usb flash drive? ----- Original Message ----- From: "Joseph C. Lininger" To: "Speakup is a screen review system for Linux." Cc: "Speakup Distribution List" 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 > >