Bug 867068
Summary: | kernel 3.6.1-1 breaks Epson V500 USB scanner initialization | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joel C Ewing <jcewing> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-10-16 21:53:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joel C Ewing
2012-10-16 17:10:07 UTC
See if you can get things working with the machine directly, and open a bug if not, but if 3.6 broke Virtual Box passthrough, you will have to get support from them to fix that. We cannot do anything with it. Tried installing several additional different packages on f17: From Fedora: iscan-firmware-2.26.4 From Epson: iscan-2.29.1-5.usb0.ltd7.x86_64.rpm iscan-data-1.18.0-1.noarch.rpm iscan-plugin-gt-x770-2.1.2-1.x86_64.rpm Not sure which resolved most of problem, but for sure the last plugin-gt pkg was needed. Now both SimpleScan and Epson Imagescan recognize and properly initialize Epson V500 scanner after scanner power-up with both 3.5.4-2 kernel and 3.6.1-1 kernel. Once scanner has been initialized, can start Win2K virtual machine under VirtualBox 4.1.22 and successfully use the scanner; but if scanner has not yet been initialized after scanner power-on and virtual machine is started, then with kernel 3.6.1-1 the scanner fails and is unable to initialize from the virtual machine. It appears that kernel 3.6.1-1 introduced some incompatibility with VirtualBox 4.1.22 that is adversely affecting USB support in this case. Just as a follow-up, this issue appears to have been fixed with kernel 3.6.6-1 install, which strongly suggests the problem was with the kernel and not VirtualBox. Hopefully someone has some idea what questionable thing was done with USB support in 3.6.1-1 that was fixed by 3.6.6-1 so it doesn't get unfixed again. I updated to VirtualBox 4.2.4 at the same time as the latest kernel, but under VirtualBox 4.2.4 my Win2K virtual machine still sees the failure with kernel 3.6.1-1, and does not see any failure with kernel 3.6.6-1, which I would take to indicate the fix was not part of VirtualBox 4.2.4 but part of the kernel. Also the problem was more subtle than previously thought: even when the the scanner appeared to be functioning under VirtualBox after initialization outside VirtualBox with kernel 3.6.1-1, there was some subtle data corruption occurring in the USB image data from the scanner. |