The most likely devices to fail upon suspension are those that are least
likely attached to laptops. Scanners and printers come foremost to my
mind. To test printers you'll have to unload the usblp module, wait 4
seconds and reload it. Usually you see a disconnect event in the syslog
when the
** Changed in: linux (upstream)
Status: Invalid = Fix Released
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I have verified that the Epson Perfection 1260 Photo (ID 04b8:011d) is
not working in feisty and that this can be solved by using the
scanbuttond workaround (but there are still problems with the TPA
adapter, which doesn't work as well).
However I don't own an Epson Perfection 1250, I only
additional quirks
** Attachment added: quirk3.diff
http://launchpadlibrarian.net/8533186/quirk3.diff
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
another for the list
ID 04b8:0122 Seiko Epson Corp.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ok, echo -1 /sys/module/usbcore/parameters/autosuspend did the trick
for my Benq 3300 S2W scanner.
It's a good idea creating a quirks list. But what makes me worry is,
that in my opinion too less people will come to this bug page and post
their problematic USB hardware ID. And I think that
I like this idea, but (IMO, at least) it would be important for such a
dialog to also automatically capture the USB IDs of the devices in
question and post them to some place where the quirks list could be
updated, perhaps similar to or as a part of the automated bug reporting
system now in
I tried today's daily build so I could report on trying out the echo -1
. . . test on the USB scanner I have.
The problem is, while I can boot other ISO Linux CDROMs, this one boos
so far and then stops at a light earth-tone (light orange-tan?) screen.
The screen is blank, so I can't do anything.
@t2000kw Same problem I had with Tribe 2 and later. Try to get Tribe 1
ISO, worked for me.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Any further IDs? Everything posted so far is on the way into the
standard kernel.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I picked a hell of a bug to triage in my first month at work :)
I now have a list (see below) of all the USB IDs listed on this bug
along with Oliver's list, that break with USB autosuspend. This list
will go into drivers/usb/core/quirks.c in the next kernel release of
gutsy (in the next week).
Adding USB devices to blacklist
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Amit Kucheria
Status: New = In Progress
Target: None = tribe-4
--
some usb_devices fault if usb_suspend enabled
In my opinion there is also a problem with usb_suspend and the palm
m505. If it is suspended you got to start the sync twice. The first sync
will always fail because of usb_suspend.
Bus 002 Device 002: ID 0830:0002 Palm, Inc. Palm M505
--
some usb_devices fault if usb_suspend enabled
Hi Amit,
I already posted here on 2007-07-16 !
Anyway, here again is the output of 'lsusb' on my computer :
Bus 001 Device 005: ID 04b8:0114 Seiko Epson Corp. Perfection 660
Do not forget my scanner on the blacklist, please !!!
Thanks !
Amit Kucheria a écrit :
I picked a hell of a bug to
My scanner also needs to be added to the blacklist:
Bus 002 Device 003: ID 04a5:207e Acer Peripherals Inc. (now BenQ Corp.)
Prisa 640BU
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
@Philipp: I am loathe to add Palm M505 since atleast it works (wakes up)
on a second sync. Could you report this upstream at bugzilla.kernel.org?
I will take it if they accept it.
@Jean: This is a *huge* thread. Sorry I missed it the first time. I have
it now.
@Luca: Added.
--
some usb_devices
Same problem (and solution) with EPSON Perfection 2480:
ID 04b8:0121 Seiko Epson Corp.
Thanks for the work to all involved! I think we affected users should nicely
inform the vendors about this issue, maybe they can provide firmware updates
or at least fix this in newer models.
Gregor
--
I thought I posted this before, but I don't see my post, so here's my
info:
[EMAIL PROTECTED]:~$ lsusb
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002 Device 001: ID :
Bus 001 Device 004: ID 04a9:1072 Canon, Inc. I850 Printer
Bus 001 Device 003: ID
Epson Perfection 1260 Photo is affected (it is the same as Epson Perfection
1260 with a TPA adapter):
ID 04b8:011d Seiko Epson Corp.
I suppose that Epson Perfection 1250 / Photo (ID 04b8:010f) are also
affected, since they are similar and from SANE page they use the same
plustek backend
I installed the kernal that fishor posted on rapidshare on 2007-05-01
and now I can use my scanner (Epson Perfection 1670) again.
I am amazed that this problem has not been fixed in the official
release.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You
Also affected:
Bus 002 Device 003: ID 04a9:2207 Canon, Inc. CanoScan 1220U
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
The kernel freeze is October 4th.
There is still time to move the new kernel into Gutsy.
The fact that Mark Shuttleworth showed up in this forum to comment
probably means that this will get fixed. I understand that when he feels
strongly about something, it gets done, and that is the mark of a
Can others confirm this bug is closed now?
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Amit, are you serious? With the number of posts and the unsolved
problems remaining, I don't think this bug is going to be closed without
any update in Ubuntu repositories.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification
@Lionel: I asked because Clay mentioned three posts above yours that the
problem was fixed. And it was a new 2.6.22-8 kernel.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Tuesday July 17 2007 10:47:37 am Amit Kucheria wrote:
@Lionel: I asked because Clay mentioned three posts above yours that the
problem was fixed. And it was a new 2.6.22-8 kernel.
no, I confirmed that after setting /sys/module/usbcore/parameters/autosuspend
to -1, it works in the current
I've been bouncing around to a few threads on this exact issue for two
days. I've only been using Ubuntu on my HP Pavillion dv2116wm laptop
for a few weeks now, but I was really trying to fix this issue. I'm not
really good at the coding and understanding some of the technical jargon
on the
With my Canon Canoscan N650U, I've just given a try with the Gutsy Tribe
2 burned as a live CD.
I first booted on the live CD, plugged in the scanner, then started xsane from
the Applications menu.
The scanner was recognized, but trying a preview scan hunged xsane.
Same behavior as in Feisty (I
Nicolas M:
Given that using
sudo echo -1 /sys/module/usbcore/parameters/autosuspend
works for you in Gutsy can you include the output of
lsusb
here so your scanner can be added to the list of devices that need workarounds?
That way it will be added to the blacklist of devices that can't cope
Here is the output of lsusb for this scanner:
$ lsusb
Bus 002 Device 002: ID 04a9:2206 Canon, Inc. CanoScan N650U/N656U
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Hello everybody,
I have been using fishor's kernel since the beginning of may 2007 and it works
perfectly !
Thank you again, fishor !
I have just tried the latest Gutsy Gibbon LiveCD : my scanner did not work at
all...
Then I have tried what fishor proposed on 2007-07-13 :
... You should
I had a problem with scanner Agfa snapscan 1212u_2. XSane gived me an error
message: Failed to start scanner : Error during device I/O after clicking on
the preview button.
I try the Fischors kernel and it solved my problem. Thank you very much Fischor.
--
some usb_devices fault if
ok, there is:
USB scanner (vendor=0x06bd [AGFA], product=0x2061 [ Snapscan1212u_2]) at
libusb:001:002
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
fishor:
I don't tihnk you realise the enormity of what you are asking. We are talking
about well over 50 different devices (many of which are owned by people's whose
time is very expensive) some of which are very big and very heavy. I happen to
know that support for autosupending usb mass
dmesg reports:
Bus 004 Device 004: ID 1606:0060 Umax [hex] Astra 3400U
This device needs to be on the 'quirks' list. Thanks!
UMax
Astra Net e3420.
Post vendor:product id
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug
This works for me in Gutsy
2.6.22-8-generic, for my Lide 25 canon scanner
plustek:libusb:001:003' is a Canon CanoScan LiDE25 flatbed scanner
Clay Weber
On Friday July 13 2007 4:31:34 pm fishor wrote:
to disable autosuspend you should do:
echo -1 /sys/module/usbcore/parameters/autosuspend
Disabling autosuspend on usbcore on 2.6.22-8-generic on a Gutsy install just
resulted in the following warnings within dmesg and no resolution of the black
scan problem with a Canoscan LiDE 20:
Bus 004 Device 003: ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20
[ 23.178531] usb 2-1:
Despite the above problem I have some good news: the sysfs interface for usb
seems to work. On a Gutsy LiveCD (http://cdimage.ubuntu.com/daily-live/current/
) from a few days ago with a 2.6.22-7-generic kernel I was able to do the
following after finding xsane was producing black scans:
sudo -s
Just grabbed another scanner. autosuspend issues do not seem to affect the
CanoScan LiDE 60:
Bus 005 Device 006: ID 04a9:221c Canon, Inc.
So I guess my original idea of blacklisting all CanoScans would be
unwise...
What devices are worth testing at the moment? Is it just scanners or is
it worth
in the quirk file here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/usb/core/quirks.c;hb=HEAD
you can find the newest blacklist of the known devices, there are some
scanners, modem, audio and blackberry.
You should test every usb-device you have.
to disable
do not know what happened. i clicked on xsane image scanner today.
and my epson perfection 1200 worked. scanned a photo.
my mem48 made a grinding sound. which is more than it ever did before.
yea, i have a working scanner.
thanks
--
some usb_devices fault if usb_suspend enabled
UMax
Astra Net e3420.
Post vendor:product id
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
In case this particular USB Canon scanner has not been reported, here
are the details:
Bus 001 Device 004: ID 04a9:2220 Canon, Inc.
Kernel is 2.6.20.16
The USB Canon printer does work:
Bus 001 Device 005: ID 04a9:1072 Canon, Inc. I850 Printer
--
some usb_devices fault if usb_suspend enabled
On Tue, 2007-07-10 at 04:14 +, das wrote:
quote
1. Open Applications, then Terminal.
2. A box should appear. In the box, type sudo gedit /boot/grub/menu.lst
(without quotes) and hit enter.
3. Look about halfway down for a line that starts # defoptions= (without
quotes; NOTE: use the
Try the autosuspend parameter in /etc/modprobe.conf.local
The IDs so far reported have been added to the USB development tree.
** Attachment added: new_quirks_1.patch
http://launchpadlibrarian.net/8410141/new_quirks_1.patch
--
some usb_devices fault if usb_suspend enabled
@Ben. I tried that (used nano, not vi - I couldn't understand vi!).
After reboot, I tried Xsane and it warned that it couldn't find a
scanner attached; so I tried lsusb and drew a blank - NO usb devices
were detected (despite several being attached as well as the scanner).
@Oliver. Please can
How do I identify my scanner to add to this quirks list? It is a UMax
Astra Net e3420.
Try the autosuspend parameter in /etc/modprobe.conf.local
The IDs so far reported have been added to the USB development tree.
** Attachment added: new_quirks_1.patch
Ben,
Your suggestion to:
This would be more proper by doing:
- sudo vi /etc/modprobe.d/usb-core-options
- Add a line with options usbcore autosuspend=0, without quotes
- sudo update-initramfs -u
Reboot, and hopefully things will work as expected.
did not work. It actually made the USB
And please, no more fixes that don't work. Spend your time making the
new kernel part of Gutsy instead of trying to make the problem go away.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of
autosuspend=0 in newer kernel releases means as soon as possible.
A negative value prevents autosuspend.
Can someone with a newer kernel possibly test and confirm this?
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification
I'm running Gutsy Gibbon in VirtualBox (native system is Feisty Fawn),
where Xsane works fine with my Canon LiDE 30. Does that mean that this
problem is solved in Gutsy?
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification
I'm running Gutsy Gibbon in VirtualBox (native system is Feisty Fawn), where
Xsane works fine with my Canon LiDE 30. Does that mean that this problem is
solved in Gutsy?
2007/7/10, jengel [EMAIL PROTECTED]:
autosuspend=0 in newer kernel releases means as soon as possible.
A negative value
I totally agree with comment 300. Why not just compile a kernel for us
ubuntu users which allows us to switch autosuspend off, if we want to? I
don't understand this.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because
USB suspend has recently been disabled by default in Fedora kernels -
see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243038#c19
(although it has been turned on and off a few times). The
usbcore.autosuspend=0 parameter was added in 2.6.21 (see
( http://marc.info/?l=linux-usb-develw=2r=1s=quirks.cq=b gives a
list emails some of which contain patches that are against
drivers/usb/core/quirks.c that haven't hit git yet)
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug
@jengel: What constitutes a newer kernel? Does the 2.6.20-16.29 in Feisty
count? And do negative values have special meaning, or can we assume -1 for
the time being?
@cank1090: IIRC, Herd CDs are also live-install combo CDs, like any other --
would it be possible for you to burn the ISO to e.g.
OK, Michael. I've just tried the usbcore.autosuspend_delay=-1
workaround and can confirm that it _doesn't_ work for me (so I'll
continue to use the Scanbuttond workaround until this is fixed properly)
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You
Sorry, I should more explicitly have said that neither
usbcore.autosuspend=0, usbcore.autosuspend=-1 nor
usbcore.autosuspend_delay=-1 worked.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of
someone asked:
t2000kw: Do you have the USB id for that USB braille device that was
showing this issue?
No. I read about it earlier in this or some other thread. It was a
problem for someone. If you want to follow up on that one, you can try
following back on this thread. I think it was
I think for the sake of sanity we should include kernel versions if
possible when we make comments if something work or not.
It seems the autosuspend went through 3 iterations.
1. No disable possible, unless you recompile with USB_SUSPEND disabled
2. autosuspend can be set, with 0 = disable
@Jengel. uname -r reports 2.6.20-16-generic
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
@jengel: Well if the code _appears_ to do that, then we can probably
work with that until the fix comes out and/or people tell us to do
differently.
@SilverLoz: Thank you very much for trying our suggestions.
As stated above, I wasn't expecting the boot-time flag to work in 2.6.20
(a.k.a. Feisty
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Part of the Ubuntu manifesto is that every computer user should be
given every opportunity to use software, even if they work under a
disability.
Not having the USB thing working goes against this manifesto, which
Shuttleworth created and endorsed himself.
On the one part, any software that
t2000kw raises a good point, though I think even if scanners aren't
involved, full and flawless support for devices whose function is
specifically enabling disabled users to use their computer (i.e. USB
braille devices) should be of *paramount* priority. I haven't read the
SABDFL's statement but
Can someone point to the existing blacklist of known devices that can't
handle USB suspend? I have access to a couple of scanners and will test
them if they are not already known. Further can someone (t2000kw?) post
the USB ids of the teletypes that don't work with USB suspend? It would
be awful
I can't believe the importance is still low (kernel) and medium (sane-
backends). A lot of people can't use their USB devices and therefore
can't use feisty the way it should be. What information do the
developers need to solve this bug? how can we help? I love the idea of
ubuntu, but I need to be
Unfortunately, I think the problem here is twofold:
Firstly, the problem doesn't seem to affect *all* USB devices -- simply
those who don't conform to usb_suspend, and violate the USB
specification*.
Secondly, I think the issue is that there is a workaround -- but both
enabling the workaround
FWIW my affected device's ID is: 04a9:220e Canon, Inc. CanoScan
N1240U/LiDE 30, if some sort of exclude list is being compiled, as was
intimated a few posts ago.
Also, on a different note: I think it might be a little hard to compile
yourself a kernel to get your USB braille device working... if
Maybe this isn't being fixed because the developers think that this fix
actually works consistently on all Ubuntu systems?
I tried it, the menu.lst file is changed, GRUB was updated, and I can
not use Kooka or Xsane.
Why not assume that all of this chatter is because the solutions
either don't
@ Michael Chang
Unfortunately, the fix you posted doesn't work for me at all. No
changes, still the same problem.
I've got a Canon LiDE 30, running Ubuntu Feisty Fawn.
How is it possible that such a bug still exists since the release of
Feisty, where Launchpad is such a great infrastructure
Michael Chang - that's too much ratiocination. Please stop dismissing
user reports like that.
Ubuntu can fix this problem *now*. Compile a Feisty kernel with
CONFIG_USB_SUSPEND unset, then make that available as a standard Ubuntu
repository item.
Again, this puts choice in user hands. They
My apologies, I am simply a user like you guys -- attempting to be
helpful.
Nobody (until now) _denied_ that the solution worked -- which is why I
reiterated the comment. Now that we know that option doesn't work means
that the fix probably involves some RH-specific patch, or RH systems are
quote
1. Open Applications, then Terminal.
2. A box should appear. In the box, type sudo gedit /boot/grub/menu.lst
(without quotes) and hit enter.
3. Look about halfway down for a line that starts # defoptions= (without
quotes; NOTE: use the line with ONE # symbol)
4. At the end of this line,
My Benq S2W 3300U ID:
Bus 001 Device 002: ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W
3300U/4300U
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255
I believe that 2.6.21 adds the ability to disable autosuspend on a per-
device basis under /sys, e.g.
/sys/bus/usb/devices/$USB_ID/power/autosuspend
This advice is from a person I know who is having problems with his USB
Braille device under the stock kernel. :-(
Preventing people with sight
Regarding the Braille device I am sorry. Please get me the
vendor:product ids. Or is there a device class?
For the other devices, please post the vendor:product pairs on this page
and I'll include them in 2.6.23
--
some usb_devices fault if usb_suspend enabled
Here's the vendor:product pair for my scanner:
ID 1606:0060 Umax [hex] Astra 3400U
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
feisty has not recognized my scanner: canoscan 4400F :-( :-( :-(
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
i had 2 working scanners
Bus 002 Device 002: ID 05d8:4005 Ultima Electronics Corp.
found USB scanner (vendor=0x05d8, product=0x4005, chip=GT-6816) at
libusb:002:004
and this one.
Bus 002 Device 003: ID 04b8:0104 Seiko Epson Corp. Perfection 1200
found USB scanner (vendor=0x04b8 [EPSON],
Hi Oliver,
Thanks for your offer, I contacted the person with the Braille display
and he responded with:
As of the latest svn revision, the BRLTTY braille software
(http://www.mielke.cc/brltty/) turns off autosuspend
for this device before accessing it. This solves the problem.
Can anyone here check and see if they have any other symptoms from bug
102659? There is suspicion that these are related.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think that another issue has to do something with this USB thingy:
My USB mouse does not work when I send the laptop into suspend mode and wake it
up again. Plugging it out and in in ANOTHER port makes it work again.
Maybe that's a separate bug, but for me that looks like it has
something to
Canon Lide 30 is also not working with Gutsy Tribe 2 (LiveCD)
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Thanks for the links I can see now that this really has been thought
out. I still wonder how rare the problem actually is, and if
manufacturers are likely to continue making broken devices, but maybe
suspend really does save enough power to be worth the grief.
--
some usb_devices fault if
Most problems are thought out at least once before people start curtly
responding well it's an incompatibility with XYZ and we can't do
anything unless they fix XYZ and this is what we think is the best way
of fixing it -- summing things up elegantly does take some work.
(Performing Google
Oliver:
It probably would have been easier to ask folks to do
sudo dmesg -c
(start scanner)
dmesg dmesg.txt
then have them upload dmesg.txt
but it's neither here nor there really...
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug
It really seems like this should be fixed in libusb rather than the
kernel. To fix it in the kernel apparently the approach is to blacklist
specific scanners, which obviously leaves newer scanners still broken.
Another possible kernel fix is to lengthen the timeout for sleep, but
this obviously
The kernel does wake up the devices if they are opened through usbfs.
But that exactly is the point the buggy devices crash. Either you never
suspend the scanners at all, or you need a work around.
As for the placement, it must be in kernel space. Some devices that have
kernel drivers have the
Just curious, but is there a difference between suspending a USB device
and turning it off entirely and turning it on later, and if so, what is
it? Maybe one could actually somehow shut off the devices which crash on
suspend and turn them back on when the PC comes back? Can we selectively
suspend
It didn't seem to me that my device (canoscan lide 25, plustek) was
crashing. Being able to run scanimage multiple times in sequence
suggests that suspend works fine as long as the device is resumed
properly. If I'm wrong about that I'd like to know in more detail
what's really happening. The
The following seem somewhat relevant:
http://lkml.org/lkml/2006/9/14/252
http://lkml.org/lkml/2007/1/14/98
http://lkml.org/lkml/2007/1/15/92
Someone seems to have known about this even in January, but there
doesn't seem to be a good way of fixing this, apart from perhaps having
a separate kernel
@Oliver Neukum (#266)
Gutsy Tribe-1 + updates 2007-06-21; Kernel: Linux thinkubuntuz29
2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
Scanner: S2W 3300u
Ouput of /var/log/messages:
Jun 21 12:13:35 thinkubuntuz29 kernel: [ 265.564000] usb 1-2: new full speed
USB device
The increment of the number is consistent with the scanner disconnecting
upon suspension, but the part of your log you posted doesn't show it. Is
it complete?
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are
For the CX7800, this bug report fixed the problem I was having:
https://launchpad.net/ubuntu/+source/sane-backends/+bug/72506;
This fixed scanning for my CX7800 under Kubuntu 7.04 with the current
kernel.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You
** Also affects: linux-source-2.6.20 (Baltix)
Importance: Undecided
Status: Unconfirmed
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Yes, I need the syslog, but I need it for the actual failure case. If
the scanner works I can't fix bugs.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Hi Oliver,
I've posted mine to the link in silentb's post - is that what you want and is
that the right place to put it?
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, if you want to capture debug info.
1. Boot with your scanner switched off
2. Notice the state of /var/log/messages
3. Switch on your scanner
4. Wait half a minute
5. Do scanimage -L (or anything that will fail)
6. Send me everything added to /var/log/messages after step 2
--
some
I've been happily using feisty for a while, then I tried to use my canon
lide20 (purchased because it was known to work with Linux). Scanbuttond
works for me, thanks. I'm concerned about the above reports of the
problem persisting in gutsy. Funny thing is I've got dapper on my
laptop, where the
101 - 200 of 298 matches
Mail list logo
