Ethernet Causes Mouse Problems

Hi Reeve,

I'm not familiar with the RPI much, but your question got me thinking. Is the other end of the cable plugged into a switch/router when this occurs? Or are you plugged in an old hub?

If you have many devices connected to your network, just as a test maybe try disconnecting all and just having your RPI connected into the router?

@shabaz Thanks for the response I was going to try it, however now the same problem happens even without the Ethernet cable plugged in.

If you can help with this, it would be greatly appreciated

Hi Reeve,

I'm afraid I'm not very useful on RPI knowledge, but reply #5 at this link appears to have very similar symptoms regarding keys repeating, and the resolution seemed to be a software upgrade. Hopefully this may help you.

@shabaz I just downloaded the latest verion of NOOBZ from the Raspberry Pi website as of about a week ago but they may have come out with a new one since then. I will try this and let you know how it worked.

As I understand, there is a compatibility list (apparently some k/b and mice may not work), so it's also worth double-checking that list. I think this is the list. There are quite a few keyboards in that list in the 'problem USB keyboard' section marked as 'sticky keys' unfortunately. I don't see GE on that list, although the working section does have one GE model (but this is not an exhaustive list). It may be worth eliminating the keyboard by trying a different one if you can, since sticky keys seems to be a popular symptom for the keyboards reported as incompatible.

j reeve wrote:

 

I have no idea why this is happening and still need help.

I'm afraid this will be of no comfort to you, but Pi USB operation will forever be in the lap of the gods because of the limitations of the USB controller hardware built into the Pi's BCM2835 SoC.  It's well documented in many places on the RPF site, there are huge threads about the issue there, and RPF developers have acknowledged it many times.  The Pi's Ethernet is implemented over USB, so it's entangled in the USB problems.

The advice given by others above is your only good way of moving forward, ie. stick to recommended USB devices and don't expect things to continue working when you introduce another USB device into the system.  That's just how it is.

USB has always been a weakness with RasPi, basically because it has a very rudimentary USB host controller on the SoC.  There's constant work in progress to improve things -- for example, this discussion -- but obviously we're not there yet.  Updating the operating system often helps, unless you get an update where something regressed.

Wired keyboards/mice tend to work better than wireless.  This is possibly a power issue, so try using an external hub if you have a wireless keyboard/mouse.

It's also possible that there's something wrong with your LAN9512 chip or crystal X1.  There may be other ideas at the RasPi Troubleshooting Wiki, such an inadequate power which causes all sorts of ills.

@ John Beetem I am pretty sure that this is not a power issue as I am using a USB wall plug outputing 5V 1A. Could this be too much power?

Also, you mentioned that one of my chips or crystals could be bad. Would getting a new Pi help solve this problem?

Hi Reeve,

It sounds like the symptom could be caused by one of several things. The problem is, replacing the board (i.e. if you think the crystal or chip is faulty) still won't help if the keyboard is not supported.

Maybe try the easiest things first, such as trying a new keyboard if you have access to one, use a hub if it is wireless, and trying a different power supply (5V 1A is fine, but some high quality one is needed).

j reeve wrote:

 

@ John Beetem I am pretty sure that this is not a power issue as I am using a USB wall plug outputing 5V 1A. Could this be too much power?

Also, you mentioned that one of my chips or crystals could be bad. Would getting a new Pi help solve this problem?

1A is not too much power.  5V at 1A means that the power supply can deliver up to 1A and is happy to deliver less current while maintaining 5V.

The problem with RasPi power is that it has to go through a Micro USB cable and then through polyfuse F3 before it can be measured at TP1 and TP2.  Some micro USB cables have very thin conductors and you get a sizeable voltage drop.  Some F3 polyfuses are out of spec and cause an excessive voltage drop.  So if you have a multimeter or voltmeter, it's pretty easy to check that the voltage between TP1 and TP2 is 4.8V to 5.2V.  Iffy power can cause so many different symptoms that it's good to rule it out.

If the LAN9512 chip or crystal is bad it's time for an RMA IMO.  Usually it's not the chip itself, but rather a bad solder joint, so some people who enjoy doing this sort of thing have reheated the X1 connections and made X1 work.  Everyone else should have the board replaced so that RasPi can improve the process.  I don't know how common the X1 problem is nowadays -- it was pretty rare even when RasPi was first being shipped.