I answerd the first question in a prior post - tha answer was No it did not work after VMware is shutdown.
I am not sure about the modprobe command if you can give the exact syntax it would confirm my tests. modprobe usbcore usbfs_snoop=y Here is the syslog: Jul 2 08:56:00 bluelinux kernel: usbcore: deregistering driver usbserial_generic Jul 2 08:56:00 bluelinux kernel: drivers/usb/serial/usb-serial.c: USB Serial deregistering driver Generic Jul 2 08:56:00 bluelinux kernel: usbcore: deregistering driver usbserial Jul 2 08:56:12 bluelinux kernel: usbcore: deregistering driver Xaxero_SkyEye Jul 2 08:56:31 bluelinux kernel: usbcore: deregistering driver usb-storage Jul 2 08:56:31 bluelinux hal-subfs-mount[10711]: Mount point /media/usbdisk got removed. Jul 2 08:56:51 bluelinux kernel: uhci_hcd 0000:00:1d.0: remove, state 1 Jul 2 08:56:51 bluelinux kernel: usb usb2: USB disconnect, address 1 Jul 2 08:56:51 bluelinux kernel: uhci_hcd 0000:00:1d.0: USB bus 2 deregistered Jul 2 08:56:51 bluelinux kernel: uhci_hcd 0000:00:1d.1: remove, state 1 Jul 2 08:56:51 bluelinux kernel: usb usb3: USB disconnect, address 1 Jul 2 08:56:51 bluelinux kernel: uhci_hcd 0000:00:1d.1: USB bus 3 deregistered Jul 2 08:56:51 bluelinux kernel: uhci_hcd 0000:00:1d.2: remove, state 1 Jul 2 08:56:51 bluelinux kernel: usb usb4: USB disconnect, address 1 Jul 2 08:56:51 bluelinux kernel: uhci_hcd 0000:00:1d.2: USB bus 4 deregistered Jul 2 08:57:02 bluelinux syslog-ng[3604]: STATS: dropped 0 Jul 2 08:57:12 bluelinux kernel: ehci_hcd 0000:00:1d.7: remove, state 1 Jul 2 08:57:12 bluelinux kernel: usb usb1: USB disconnect, address 1 Jul 2 08:57:12 bluelinux kernel: usb 1-3: USB disconnect, address 3 Jul 2 08:57:12 bluelinux kernel: ehci_hcd 0000:00:1d.7: USB bus 1 deregistered Jul 2 08:58:30 bluelinux kernel: /dev/vmnet: open called by PID 10969 (vmware-vmx) Jul 2 08:58:30 bluelinux kernel: device eth0 entered promiscuous mode Jul 2 08:58:30 bluelinux kernel: bridge-eth0: enabled promiscuous mode Jul 2 08:58:30 bluelinux kernel: /dev/vmnet: port on hub 0 successfully opened Jul 2 08:58:31 bluelinux kernel: /dev/vmmon[10977]: host clock rate change request 0 -> 19 Jul 2 08:58:42 bluelinux kernel: /dev/vmmon[10977]: host clock rate change request 19 -> 83 Jul 2 08:58:52 bluelinux kernel: device eth0 left promiscuous mode Jul 2 08:58:52 bluelinux kernel: bridge-eth0: disabled promiscuous mode Jul 2 08:58:52 bluelinux kernel: /dev/vmnet: open called by PID 10977 (vmware-vmx) Jul 2 08:58:52 bluelinux kernel: device eth0 entered promiscuous mode Jul 2 08:58:52 bluelinux kernel: bridge-eth0: enabled promiscuous mode Jul 2 08:58:52 bluelinux kernel: /dev/vmnet: port on hub 0 successfully opened Alan Stern wrote: > On Thu, 30 Jun 2005, jon wrote: > > >>Thank you for your response: >> >> >>the data you requested is enclosed > > > The files didn't show any difference as far as I could see. > > You didn't answer my last question. If you run and exit from VMware, and > then unplug and replug the device, does the driver work? Better yet, if > you leave the device unplugged while running and exiting from VMware and > then plug the device in afterward, does the driver work? > > Here's another experiment you can try. Unload all the USB drivers and > then modprobe usbcore.ko with the "usbfs_snoop=y" parameter. Then see > what shows up in the debugging log while VMware runs > > Alan Stern > > > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
