> 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
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
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
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
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
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
> >
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 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
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
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 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
> >
On Sun, 14 Jan 2007, Alan Stern wrote:
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
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:
On Sun, 14 Jan 2007, Alan Stern wrote:
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
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
22 matches
Mail list logo
