On 08/03/2007 01:48 PM, Matthew Garrett wrote:
> On Fri, Aug 03, 2007 at 10:44:35AM -0700, Greg KH wrote:
>> On Fri, Aug 03, 2007 at 01:32:53PM +0100, Matthew Garrett wrote:
>>> But while this is still a likely probability, the chances are no
>>> distribution is going to ship with CONFIG_USB_SUSPE
On 07/11/2007 08:59 AM, Ville Herva wrote:
> [98790.134315] sd 17:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [98790.134319] sd 17:0:0:0: [sdb] Assuming drive cache: write through
> [98790.134323] sdb:<6>usb 6-1: USB disconnect, address 27
> [98790.366609] BUG: unable to handle kernel NULL pointer dere
On 07/11/2007 04:30 AM, Piotr Muszynski wrote:
[cc: linux-usb, linux-ide]
> I am adding transparent ATAPI capability to USB gadget Mass Storage
> driver. The idea is to pass USB traffic to block device queue as packet
> requests. At the end of the queue, the requests are handled by ide-cd.c
> dri
On 07/08/2007 05:45 PM, Daniel J Blueman wrote:
> When plugging in a USB 2 mass-storage device which I've been seeing
> problems with, I caught a khubd oops [1]. Kernel is 2.6.22-rc7 on ia32
> built with Ubuntu's 2.6.22 .config.
> [ 4769.252000] sd 6:0:0:0: [sdb] Assuming drive cache: write throug
On 06/26/2007 10:20 AM, Keith Chew wrote:
[cc: linux-usb-devel]
> We have been using a Zydas based WIFI drivers under kernel 2.6.16.18
> with great success. Recently, when we upgraded to 2.6.20.1 (also
> tested on 2.6.21.5), we found that during initialisation, these calls
> works with USB2.0 but
On 06/20/2007 10:06 AM, Alan Stern wrote:
>> In my dmesg today, I see this:
>> usb 1-1: can't set config #1, error -71
>
> That error is more serious.
>
>> When I remove and input (again) my Mouse, I see this in /var/log/messages:
>>
>> kernel: usb 1-1: USB disconnect, address 3
>> kernel: usb 1-
On 06/19/2007 10:45 AM, Renato S. Yamane wrote:
> Hi,
> I see this in dmesg:
> usb 1-1: device descriptor read/all, error -71
>
> Using 2.6.21.1
>
> Someone know what it is?
>
Try disabling CONFIG_USB_SUSPEND
[usb developers: what are the drawbacks of doing this?]
We just found a file with this name in 2.6.21:
Directory name: /sys/module/nousb/parameters
File name: ""
IOW the file has an empty name. Is this intentional?
It sure confuses updatedb...
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242715
--
Alan Stern wrote:
> On Sun, 1 Apr 2007, Pavel Machek wrote:
>
>> Hi!
>>
>> The GNOME hath spoken?
> I also thought about that,
>
> I think that the best solution is still to hide connect/disconnect of
> usb devices from userspace (now it also causes corruption)
>
David Brownell wrote:
> On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
>> On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
>>> _Something_ is generating those overcurrent
>>> warnings, and it sure looks like a hardware malfunction.
>> But it works with 2.6.20.
>
> So can yo
Daniel Barkalow wrote:
> On Tue, 13 Feb 2007, Chuck Ebbert wrote:
>
>> drivers/usb/net/usbnet.c:
>>
>> int
>> usbnet_probe (struct usb_interface *udev, const struct usb_device_id *prod)
>> {
>> struct usbnet *dev;
>&
I can't send a break signal using my Belkin PDA Adapter. It uses
the mct_u232 USB serial driver. Looking deeper, I found I can't
change data bits, stop bits or parity either. All of these
functions depend on writing to the LCR (Line Control Register).
This is with 2.6.16-rc5.
I tried:
1) Con
In-Reply-To: <[EMAIL PROTECTED]>
On Sat, 24 Sep 2005 at 10:59:14 -0400, Alan Stern wrote:
> Have you tried building these things as modules instead of compiling them
> into the kernel? Then you could test what happens when you simply rmmod
> ohci_hcd.
I don't like modules because of the extr
In-Reply-To: <[EMAIL PROTECTED]>
On Fri, 23 Sep 2005 at 22:12:54 -0400, Alan Stern wrote:
> The presence of the OHCI driver shouldn't make any difference to how the
> EHCI controller behaves. You could try re-enabling OHCI in your .config
> and recompiling again. Maybe everything will continu
In-Reply-To: <[EMAIL PROTECTED]>
On Fri, 23 Sep 2005 at 11:05:39 -0700, David Brownell wrote:
> > OHCI is claiming my USB 2.0 hub, connected to the built-in USB port
> > on my x86-64 notebook.
>
> Or to say it more correctly: "ehci is NOT claiming it".
> If it's not doing that, there's some sor
OHCI is claiming my USB 2.0 hub, connected to the built-in USB port
on my x86-64 notebook.
This happens on both 2.6.13.2 and 2.6.14-rc2:
ehci_hcd :00:13.2: new USB bus registered, assigned bus number 1
ehci_hcd :00:13.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB
I just added some usb-storage devices to my system and got the below.
Why do the first four lines repeat for each device? (Not sure if
this is a SCSI or USB problem.)
[ 23.433725] SCSI device sda: 63424 512-byte hdwr sectors (32 MB)
[ 23.560564] sda: Write Protect is off
[ 23.560581] sda:
17 matches
Mail list logo
