2007
Date: Tue, 24 Apr 2007 06:44:17 +0300
From: Zune-Online.com [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken
I don't know if this is the right place to mention it but after
upgrading from 2.6.17 to 2.6.20 linux kernel, Microsoft Zune
On Sat, 20 Jan 2007, Prakash Punnoor wrote:
Am Freitag 19 Januar 2007 17:11 schrieb Alan Stern:
[Removed LKML from the CC: list]
On Fri, 19 Jan 2007, Prakash Punnoor wrote:
Hi,
I found quickly booted into a 2.6.19-rc5 kjernel which was lying around
here and here
Am Freitag 19 Januar 2007 17:11 schrieb Alan Stern:
[Removed LKML from the CC: list]
On Fri, 19 Jan 2007, Prakash Punnoor wrote:
Hi,
I found quickly booted into a 2.6.19-rc5 kjernel which was lying around
here and here CONFIG_USB_SUSPEND doesn't make any problems with my
scanner...
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this
are the messages I get (w/o touching the device/usb cable except pluggin it
in for the first time):
Hi,
I need lsusb -v for your device.
Am Freitag 19 Januar 2007 12:29 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the messages I get (w/o touching the device/usb cable except
pluggin it in for the
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the messages I get (w/o touching the device/usb cable except
pluggin it in for the first time):
Hi,
I found quickly booted into a
[Removed LKML from the CC: list]
On Fri, 19 Jan 2007, Prakash Punnoor wrote:
Hi,
I found quickly booted into a 2.6.19-rc5 kjernel which was lying around here
and here CONFIG_USB_SUSPEND doesn't make any problems with my scanner...
Do you want me to try out kernels until I find one rc
Am Sonntag, 14. Januar 2007 20:47 schrieb [EMAIL PROTECTED]:
Can anyone suggest another approach?
Alan Stern
Just a thought, you could use both a blacklist approach, and a module
paramater, or something in sysfs, to allow specifying devices that won't
be suspend and resume compatible.
On Mon, 15 Jan 2007, Oliver Neukum wrote:
Am Sonntag, 14. Januar 2007 20:47 schrieb [EMAIL PROTECTED]:
Can anyone suggest another approach?
Alan Stern
Just a thought, you could use both a blacklist approach, and a module
paramater, or something in sysfs, to allow specifying
Am Montag, 15. Januar 2007 17:03 schrieb Alan Stern:
On Mon, 15 Jan 2007, Oliver Neukum wrote:
Upon further thought, a module parameter won't do as the problem
will arise without a driver loaded. A sysfs parameter turns the whole
affair into a race condition. Will you set the guard
On Mon, 15 Jan 2007, Oliver Neukum wrote:
Am Montag, 15. Januar 2007 17:03 schrieb Alan Stern:
On Mon, 15 Jan 2007, Oliver Neukum wrote:
Upon further thought, a module parameter won't do as the problem
will arise without a driver loaded. A sysfs parameter turns the whole
affair into
On Mon, Jan 15, 2007 at 11:03:35AM -0500, Alan Stern wrote:
On Mon, 15 Jan 2007, Oliver Neukum wrote:
Am Sonntag, 14. Januar 2007 20:47 schrieb [EMAIL PROTECTED]:
Can anyone suggest another approach?
Alan Stern
Just a thought, you could use both a blacklist approach, and a
Am Donnerstag 11 Januar 2007 18:28 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the messages I get (w/o touching the device/usb cable except
pluggin it in for
Am Sonntag, 14. Januar 2007 10:08 schrieb Prakash Punnoor:
Am Donnerstag 11 Januar 2007 18:28 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the messages I
Am Sonntag 14 Januar 2007 10:28 schrieb Oliver Neukum:
Am Sonntag, 14. Januar 2007 10:08 schrieb Prakash Punnoor:
Am Donnerstag 11 Januar 2007 18:28 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know
Am Sonntag 14 Januar 2007 10:28 schrieb Oliver Neukum:
Have you confirmed that by using a kernel without CONFIG_USB_SUSPEND ?
BTW, these are my USB config options, which don't seem to make problems
anymore as long as USB_SUSPEND isn't activated:
CONFIG_USB_ARCH_HAS_HCD=y
On Sun, Jan 14, 2007 at 10:08:37AM +0100, Prakash Punnoor wrote:
Am Donnerstag 11 Januar 2007 18:28 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the
On Sun, 14 Jan 2007, Prakash Punnoor wrote:
Am Sonntag 14 Januar 2007 10:28 schrieb Oliver Neukum:
Am Sonntag, 14. Januar 2007 10:08 schrieb Prakash Punnoor:
Am Donnerstag 11 Januar 2007 18:28 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
Am Sonntag, 14. Januar 2007 20:47 schrieb [EMAIL PROTECTED]:
When the scanner is not in use, the system automatically suspends it after
two seconds. When you use sane the scanner is resumed, but it then
disconnects itself and reconnects. Sane is left trying to control the
disconnected
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but this
are the messages I get (w/o touching the device/usb cable except pluggin it
in for the first time):
usb 1-1.2: new full speed USB device using ehci_hcd and address 4
ehci_hcd :00:0b.1: qh 81007bc6c280
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this
are the messages I get (w/o touching the device/usb cable except pluggin it
in for the first time):
usb 1-1.2: new full speed USB device
21 matches
Mail list logo
