Parkard Bell Easynote TS – touchpad not working

Topic

New Reply

As the title says. An attached mouse works as expected, but the touchpad is defunct. I’ve had a good old look round for any settings that might have gone awry, but haven’t found anything to fix it. Is the next step to uninstall then reinstall? It says it’s working and plugged into PS/2 mouse port, but I assume that’s normal.

Any suggestions will be welcome. Note that this isn’t mine – it’s been lent to me by our local U3A – and it was already defunct when lent.

OS is Win 10

Eliminate spare time: start programming PowerShell

Reply | Quote

Replies

If it works when the mouse is disconnected then look at Settings | Devices | Touchpad. Make sure “Leave Touchpad on when mouse*is connected” is selected.

--Joe

Reply | Quote

Sorry Joe, I may have been less than clear. it doesn’t work with or without the mouse attached. Dead, defunct, moribund.

Eliminate spare time: start programming PowerShell

Reply | Quote

Do you have a Win10 driver for the touchpad?
Have*you checked the BIOS to see if it is disabled there?

--Joe

Reply | Quote

After trying hard to get into the BIOS, I finally succeeded (F2 had to be pressed very quickly). However, I couldn’t see anything in the BIOS about the touchpad.

I’ve asked the system to check the driver and it’s the latest (I’m sure that it was working after being upgraded to 10) .

I’ve stopped and started the touchpad from Device manager, but it’s still on strike.

I strongly suspect it’s a hardware problem but I thought I would ensure I’ve tried the easier solutions first (start simple, then gradually go to more complex!)

Eliminate spare time: start programming PowerShell

Reply | Quote

As Joe suggested, it could be the driver. Go to the Packard Bell websiteand see if there is a driver for the touchpad. If not, then there may be a chipset driver; try that one.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote

Thanks both of you, I will have to speak to the owners of the laptop to make sure they’re happy going down that path of a new driver. It’s not likely to make things worse (and I would do an image first anyway), but as it’s not mine…..

Eliminate spare time: start programming PowerShell

Reply | Quote