Bug 98152
Summary: | Fail to sync Palm more than once with USB in VMWare with current OS updates applied | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mitsu Hadeishi <mitsu> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:41:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mitsu Hadeishi
2003-06-27 01:02:38 UTC
Modules are loaded based on the /sbin/hotplug rules. Linux will try to claim treo etc devices. This is not a bug. You can modify hotplug to leave devices free for vmware if you need Whoa now, wait just a second here. Perhaps you can explain the following (I may not understand hotplug correctly): 1) Yes, I realize Linux normally tries to claim a Palm device. This is why I disabled the visor module to make sure that it would leave it free for VMWare. 2) VMWare does not directly access the hardware --- it relies on Linux to talk to the hardware. VMWare simply claims the device AFTER Linux detects the device. I.e., it acts like a module like visor, and claims the device. Therefore, I believe VMWare requires that hotplug be operating in order to work at all. Disabling hotplug for USB devices will also disable VMWare's access to USB devices. 3) This did not occur before. I.e., VMWare used to be able to sync just fine as many times as I liked, as long as I either removed the visor module or rmmod'd it over and over. So has something changed recently to change the behavior of hotplug? Well, I just updated to the latest kernel (2.4.20-18.9) and this bug no longer occurs in that version of the kernel. So I am re-closing the bug. This bug has reappeared with the newest kernel (2.4.20-19.9) Is there any way I can access any log files associated with the usb subsystem beyond those in /var/log/messages? Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |