I have a Manzanita program, MP2TSA, that requires a USB key to run. You
insert the key in a USB port and run the program. Without the key the
program will not run. When I boot directly into Windows XP and run the
program, all is well.
However, I normally run Windows XP as a guest operating system under Linux
using VMWare Workstation 4.0. This also works fine in general.
However, if I have XP running as a guest and insert the USB key, XP will
lockup solid (no mouse cursor movement, no keyboard, nothing) for about five
minutes. After which, everything works fine, the USB key is recognized, and
I can run MP2TSA.
My USB mouse works fine. A USB hotsync cable for my Palm works fine also,
without any lockups (though I added visor to the usb blacklist file so it
wouldn't compete with the Palm Windows software).
So--what is going on and what can I do to fix it?
There are a few other anomalies that might be clues. If you boot Linux (Redhat
7.2, kernel 2.4.18-3) with the key installed, Linux will hang for a while
(say 30 seconds) after the first two lines below and before the third:
Initializing USB controller (USB-uhci): [OK]
Initializing USB controller (ehci-hcd): [OK]
--hangs for a while--
Initializing USB HID interface: [OK]
So there's something going on with Linux trying to figure out what the device
is. If I boot first, then plug in the key and run lsusb here's the (partial)
output:
Bus 002 Device 002: ID 07f2:0001
cannot get string descriptor 1, error = Connection timed out(110)
cannot get string descriptor 2, error = Connection timed out(110)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.01
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x07f2
idProduct 0x0001
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
MaxPower 10mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 0 Interface
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 5 EndPoint1 10ms Interrupt Pipe
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 8
bInterval 10
Language IDs: (length=4)
0109 (null)((null))
When you watch this, what happens is that it pauses for a few seconds before
each of the timeout messages. There's something non-compliant about the key.
Which may be what is causing the problem. Perhaps VMWare forces a rescan of
the USB chain and causes a longer timeout as well?
Anyway, there's no module/driver for this key under Linux, so as long as
hotplug notices it is present, everything should be fine. I'm wondering if
there is some hack I can do to hotplug to make it ignore the device, or just
to change the timeout?
Anybody have any suggestions?
Thanks,
Glenn
-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
