Hide Forgot
Description of problem: The Benq 5000 scanner fails on FC6. The scanner warms up ok, and pressing "Scan" makes some noises in the scanner, but then fails with: Failed to start scanner: Error during device I/O I have tried both as root and as a plain user. I also have my firmware.bin in /usr/share/sane/snapscan/. This scanner worked perfectly under FC5. Version-Release number of selected component (if applicable): xsane-0.991-4.fc6.x86_64 sane-backends-1.0.18-5.fc6.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Press "Scan" in xsane. 2. 3. Actual results: Failed to start scanner: Error during device I/O Expected results: A scan. Additional info:
I'm a bit doubtful that it helps (it's only the frontend), but have you seen the problem with the current xsane-0.994-2.fc67 as well?
I just updated, and it makes no difference. Interestingly, the first time I run xsane now it gives me the same error as always. The second time, it can't even find the scanner device. Resetting the scanner brings it back to the usual error upon running xsane yet again. Let me know if there's anything else I can do to help.
Aldy, sorry for taking so long ;-). Please try whether you can get it to work with the old FC5 kernel (in case there have been USB changes contributing to the problem): http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/kernel-2.6.15-1.2054_FC5.i686.rpm
Hi Aldy, and thanks for your e-mail response. I found in a ubuntu forum that the problem is caused by "USB selective suspend/resume and wakeup (EXPERIMENTAL)" on the kernel code. I recompile my kernel (F7 amd_x64, Benq3300U scanner) without this option and now is working without problems... by the way, I optimize my cpu to amd 64 and ntfs RW on kernel code :)
Aldy, I suspect that this is a duplicate of bug 243953. Please try whether _one_ of the following fixes the problem: a) with a current FC6/F7 kernel, add "usbcore.autosuspend=0" without the quotes to the kernel command line, reboot b) install kernel version 2.6.21-1.3255.fc7 from updates-testing and reboot into that Thanks.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.