Here is the order of troubleshooting I would follow:
Verify you are on NOOBS 2.4.0, it is the latest install which you
Plug the HDMI into the Pi and the monitor, plug the power into the
Pi. Now confirm you can see picture and get input from the Pi, along
with lights on the Pi after plugging in the power.
- Plug in the mouse, are you able to see the mouse move around on the
- If not, try all four USB plugs with the mouse. If it still does not
work, you should try to plug the mouse into another computer to
confirm the mouse is working.
- You should also grab one more wired basic mouse to connect to the USB
of the Pi to confirm it's not the mouse.
- If the issue still persists, my last resort would be to download
Raspbian and mount the system image on the SD card after
formatting it, and seeing if the mouse will work with Raspbian vs
The rest of the steps come from this article and should be tried next.
Are you up to date?
Work on the USB driver and kernel happens frequently. You should use sudo apt-get update && sudo apt-get upgrade to get the latest firmware and kernel that will contain many patches not present in the default installs of Raspbian. If you are using a different distro on the Pi, then you should check around the distro's website or guides to see how to update it.
Does it enumerate?
If a device doesn't work, then the first step is to see if it is detected at all. There are two commands that can be entered into a terminal for this: lsusb and dmesg. The first will print out all devices attached to USB, whether they are actually recognised or not, and the second will print out the kernel message buffer (which can be quite big after booting: try doing sudo dmesg -C then plug in your device and retype dmesg to see new messages).
If there are errors with enumeration, then there are a few usual suspects:
The Raspberry Pi's USB ports cannot provide enough current for high-power 500mA devices. You should use a good-quality powered hub when using these devices: some devices may advertise that they use lower power than they actually do, especially things like wireless LAN dongles and USB HDDs. Also, some hub power supplies advertise that they give out much more power than they actually can. Be sure to check your USB device with an alternative source of power: if you continue to receive the same result, you can rule power out as a cause of the issue.
Number of hubs
There is a limit to the number of cascaded hubs you can use with the Raspberry Pi. If your device refuses to work when used with a multi-port hub, then use lsusb -t to display a "tree" of which devices physically connect to what. There is always at least 1 hub in a model B: the ethernet chip is actually a 3-port hub and a USB ethernet device.
If a device enumerates without any errors, but doesn't appear to do anything, then it is likely there are no drivers installed for it. Search around based on the manufacturer's name for the device or the USB IDs that are displayed in lsusb (e.g. 05dc:a781). The device may not be supported with default Linux drivers, and you may need to download or compile your own third-party software.
Poor performance, but no errors in dmesg
First, be sure that it is actually the USB device itself which is causing the problem. Doing other activity such as other wireless devices using the same network, other devices using the USB bus may impact performance. Try to replicate the problem with a minimum number of other devices plugged in.
Some devices can become flakey after a while because they heat up. For example, wireless LAN dongles can become quite warm if in constant use: try unplugging the device, leave it for a few minutes and plug back in. Does it still exhibit the same behaviour?
Device disconnects or continually reconnects
This again is usually caused by problems with power, so double-check your supply. If it's not power, then it can also be a symptom of getting too many errors from the device which causes Linux to reset the device. Try moving the device to a different hub port as described above.