03-09-2012 06:05 AM
I have a new W520. I have a Logitech wireless mouse connected to the USB/SATA port (I also tried the powered USB port). The mouse works fine. If I plug a USB 3.0 Disk drive into one of the USB 3.0 ports, the mouse becomes very erratic. The pointer will "freeze" on the screen and will stop and start as it is moved.
My assumption is that this is some sort of interference in USB processing or the disk is somehow overwhelming the USB infrastructure. Interestingly all it takes is for the disk to be plugged it, not as if I'm transferring large amounts of data at the time.
Has anyone else experienced this problem? Any recommendations on solutions? One of the reasons I got the W520 was to use it for photo processing. I keep the photos on a USB 3.0 portable disk and so loosing mouse control will be a real problem.
03-09-2012 07:32 AM - edited 03-09-2012 07:34 AM
I actually have this exact problem.
External USB 3.0 disk, and a Logitech Wireless M905.
It's an issue that I first experienced on the W510, but now also on my new W520.
There's something strange about USB 3.0 disk sharing the same host controller with the Logitech Wireless (Unified) receiver.
If I then relocate the receiver to some other non-USB 3.0 ports, then the mouse works again.
03-09-2012 07:55 AM
Hmmm... I have the receiver in the combined USB / SATA port. I tried it in the yellow powered USB port as well and seemed to have the same problem. I haven't tried it in the other USB 3.0 port.
I guess I will try a wired mouse tonight but I would hate to loose my nice wireless mouse.
03-11-2012 09:56 PM
Had some time to figure this one out.
It is indeed EMI/RFI related. And is dependent on the proximity of the wireless mouse reciever to the USB 3 plug.
Proximity of the wireless mouse reciever to the USB 3 cable itself does not affect the mouse functionality. (I have the wireless mouse reciever connected to a USB cable extension...so that I can use it like an electrical wiring detector. Moving the mouse, and ensuring USB 3 is transferring data at the same time).
So this turns out to be not USB 3 or USB 2 related, or bus related.
Question now is, does it mean the USB 3 plug is not shielded properly?
03-12-2012 07:29 AM