Touchpad button problem
Hi all,
A few weeks ago my MacBook (original Core Duo model) started detecting clicks on the touchpad button as double-clicks in the OS. This doesn't happen all the time, and seems much more likely to occur when I press on the left side of the button than the right, so I'm assuming it's a hardware issue.
Does anyone have a rough idea of how much it'd cost to get repaired at a UK Apple store? It's been out of warranty for a while unfortunately.
Thanks
J
I have two MB's one has a crisp trackpad button while the other had a mushy button. I fixed the mushy button quite easily. Take out the battery and look at the metal panel directly underneath the trackpad button. You'll see a circular indention in the metal. If you press lightly on the indention and at the same time press on the trackpad button you'll notice that the trackpad button's response is more crisp (at least mine was). I just pressed on the spot a few times to force the metal to bow every so slightly (not perceptible to the eye). Now my button clicks quite nicely across the entire button.
Similar Messages
-
DV5-1000 touchpad buttons, premature wear
After about a year of using my DV5-1000, the silver coated left touchpad button began to wear through to the black plastic underneath. Also, the button became noticeably loose, especially when compared to the right touchpad button. It eventually got to the point where the button would click unreliably.
I managed to buy a replacement palmrest part for the DV5, which contains the touchpad assembly (you cannot buy the assembly separately). Unfortunately, the palmrest is an integral part of the laptop, requiring 75% of it to be disassembled to remove the original part. I downloaded a service manual and went to work... and I got it done after 2 long hours. The new part fit properly and the laptop appeared as new.
A year later, I'm faced with the same problem yet again! I am not abusive to the touchpad buttons. This kind of wear should not be happening. I dread having to take apart the laptop again... but I am worried that the button will start developing click problems as the previous one did. I wonder if some kind of protective coating added to the button would help it. Anybody else here suffer premature wear to the left touchpad button?
"If you keep an open mind, life will give you more possibilities."I had a look at some of the newer DV5 models and... I'm rather taken aback with how HP solved the touchpad button problem. They no longer have tactile keys. Instead, there's a soft touch membrane. This makes it very difficult to control sustained pressing of the button, as the travel from on to off is so short. It was a real cop-out in my mind, that HP didn't stick with tactile buttons. Sure, there were some problems with how they were intially implemented, but c'mon--so many other laptop makers have tactile buttons that don't wear out. Why couldn't HP have gone that route of just improving the button?
Also, what's with all of the wacky patterns that HP is now slathering over their laptop casings? It makes the laptop look a lot less professional. If they want to appeal to kids, make it so that there's an optional shell you can get with the laptop with whatever zany pattern you wish. Or instead, just opt for something conservative and wear resistant.
"If you keep an open mind, life will give you more possibilities." -
How to deal with those pesky touchpad buttons
The Pavilion series laptops are really well made in a lot of respects. I have owned my DV5t for almost 4 years now and I've been quite happy with it (except for rather anemic battery life). There is one thing that became a nasty problem for me, that being the left touchpad button. It is the most commonly used touchpad button and unfortunately these buttons were not well designed. They can easily break after a certain number of hits, whereby there's no longer any spring to it. Pressing the button ends up getting double-taps like mad. Also, the silver coating on them tends to wear away, looking rather unsightly over time. Once you start seeing the black plastic beneath, it won't be long before the button breaks. It's really a shame, because these tactile feel buttons work well--they just don't last. The newer HP laptops have those "lite touch" buttons which I do not like. The tactile feel is so much better. Unfortunately, it seems like most laptop makers are going with those solid state buttons to avoid another component that might go wrong. It's a shame, because with just a little more effort they could have been designed to last a very long time.
As of this writing, I have now gone through TWO of these touchpads. How did I manage to get another two chances? Well, they can be replaced but unfortunately they require you to disassemble more than half of the laptop. You see, the touchpad is integrated into the palm bezel, and the palm bezel is a piece of plastic coated metal that runs all the way to the back of the laptop. To get at it requires about an hour of taking the laptop apart. It's not for the faint of heart either. However, there is a service manual available that shows you what to do and I was able to follow it... thrice. Yes, the first button wore out after just under 2 years. The second one held up about as long. I use the touchpad buttons frequently, so... well, needless to say, now that I've got the 3rd bezel in place, I am going to rely mostly on an external mouse. And when I have to use the touchpad, I am going to use it very carefully, not exerting too much pressure (note that you can also tap the touchpad itself for a single click, something good to get into the habit of doing). Additionally, I'm going to put a sheet of protector plastic on the left mouse button to help avoid wearing out the surface.
So... one hour to disassemble it and a little more than an hour to reassemble it. It looked daunting to do at first, but believe me if you're patient and can follow instructions it is definitely doable. You don't need to be an HP tech to do it.
As for the parts, I obtained them from eBay. Apparently there are a lot of excellent condition used parts available from a variety of sources. I got the bezel for just under $30 shipped. Also, the speaker grille part is metal and tends to dent, so this time around I replaced it as well as the keyboard (the original was fine, but just a little touchy on one or two keys). With all 3 of these parts replaced, my laptop feels like new all over again. As for obtaining parts, you'll need to do your homework with the HP parts finder. There are many variants of the Pavilion laptop models with many parts in common, so the part you need can vary by number. The parts catalog can help you find them.
Anyway, that's about it. After having done this for the 3rd time, I figured there might be others out there with this problem on the brink of tossing out the laptop or selling it for parts on the cheap. It's salvageable!
"If you keep an open mind, life will give you more possibilities."Thank you for your information and support. I may have to replace my touch pad and keyboard and you have given me hope and confidence. Thank you again,
Jackson Gal -
Left touchpad button delay in web browsers
I'm at a loss to figure out what could be causing my left button on my touchpad to delay intermittently. On both Google Chrome (whether stable, beta or dev) and Firefox, the left button when pressed may not respond for up to a few seconds. This is most noticeable when using Google Street View and Google Maps, which refuse to change viewpoint when holding down the left button. It isn't a Flash fault because there is also a delay when highlighting text.
I can rule out the possibility of any hardware fault as the left button on the touchpad works fine elsewhere, within KDE (ie. drag and dropping works without delay or fault) and other applications.
Output of my X log:
[ 5.365]
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 5.365] X Protocol Version 11, Revision 0
[ 5.365] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 5.365] Current Operating System: Linux TGHE 3.8.10-1-ARCH #1 SMP PREEMPT Sat Apr 27 12:36:59 CEST 2013 x86_64
[ 5.365] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=99d5896f-0144-4c5c-8c54-c11229ef01eb ro quiet
[ 5.365] Build Date: 17 April 2013 02:37:06PM
[ 5.365]
[ 5.365] Current version of pixman: 0.28.2
[ 5.365] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 5.365] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 5.365] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 28 21:34:03 2013
[ 5.367] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 5.368] (==) No Layout section. Using the first Screen section.
[ 5.368] (==) No screen section available. Using defaults.
[ 5.368] (**) |-->Screen "Default Screen Section" (0)
[ 5.368] (**) | |-->Monitor "<default monitor>"
[ 5.368] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 5.368] (==) Automatically adding devices
[ 5.368] (==) Automatically enabling devices
[ 5.368] (==) Automatically adding GPU devices
[ 5.369] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 5.369] Entry deleted from font path.
[ 5.370] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 5.371] Entry deleted from font path.
[ 5.371] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 5.371] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 5.371] Entry deleted from font path.
[ 5.371] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 5.371] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 5.371] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 5.371] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 5.371] (II) Loader magic: 0x7fcc20
[ 5.371] (II) Module ABI versions:
[ 5.371] X.Org ANSI C Emulation: 0.4
[ 5.371] X.Org Video Driver: 14.1
[ 5.371] X.Org XInput driver : 19.1
[ 5.371] X.Org Server Extension : 7.0
[ 5.373] (--) PCI:*(0:1:0:0) 10de:0dcd:1028:04b7 rev 161, Mem @ 0xd4000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[ 5.498] Initializing built-in extension Generic Event Extension
[ 5.498] Initializing built-in extension SHAPE
[ 5.498] Initializing built-in extension MIT-SHM
[ 5.498] Initializing built-in extension XInputExtension
[ 5.498] Initializing built-in extension XTEST
[ 5.498] Initializing built-in extension BIG-REQUESTS
[ 5.498] Initializing built-in extension SYNC
[ 5.498] Initializing built-in extension XKEYBOARD
[ 5.498] Initializing built-in extension XC-MISC
[ 5.498] Initializing built-in extension SECURITY
[ 5.498] Initializing built-in extension XINERAMA
[ 5.498] Initializing built-in extension XFIXES
[ 5.498] Initializing built-in extension RENDER
[ 5.498] Initializing built-in extension RANDR
[ 5.498] Initializing built-in extension COMPOSITE
[ 5.498] Initializing built-in extension DAMAGE
[ 5.498] Initializing built-in extension MIT-SCREEN-SAVER
[ 5.498] Initializing built-in extension DOUBLE-BUFFER
[ 5.498] Initializing built-in extension RECORD
[ 5.498] Initializing built-in extension DPMS
[ 5.498] Initializing built-in extension X-Resource
[ 5.498] Initializing built-in extension XVideo
[ 5.498] Initializing built-in extension XVideo-MotionCompensation
[ 5.498] Initializing built-in extension XFree86-VidModeExtension
[ 5.498] Initializing built-in extension XFree86-DGA
[ 5.498] Initializing built-in extension XFree86-DRI
[ 5.498] Initializing built-in extension DRI2
[ 5.498] (II) LoadModule: "glx"
[ 5.499] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 5.560] (II) Module glx: vendor="NVIDIA Corporation"
[ 5.560] compiled for 4.0.2, module version = 1.0.0
[ 5.560] Module class: X.Org Server Extension
[ 5.560] (II) NVIDIA GLX Module 313.30 Wed Mar 27 15:51:21 PDT 2013
[ 5.560] Loading extension GLX
[ 5.560] (==) Matched nouveau as autoconfigured driver 0
[ 5.560] (==) Matched nvidia as autoconfigured driver 1
[ 5.560] (==) Matched nv as autoconfigured driver 2
[ 5.560] (==) Matched vesa as autoconfigured driver 3
[ 5.560] (==) Matched modesetting as autoconfigured driver 4
[ 5.560] (==) Matched fbdev as autoconfigured driver 5
[ 5.560] (==) Assigned the driver to the xf86ConfigLayout
[ 5.560] (II) LoadModule: "nouveau"
[ 5.562] (WW) Warning, couldn't open module nouveau
[ 5.562] (II) UnloadModule: "nouveau"
[ 5.562] (II) Unloading nouveau
[ 5.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 5.562] (II) LoadModule: "nvidia"
[ 5.563] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 5.569] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 5.569] compiled for 4.0.2, module version = 1.0.0
[ 5.569] Module class: X.Org Video Driver
[ 5.570] (II) LoadModule: "nv"
[ 5.571] (WW) Warning, couldn't open module nv
[ 5.571] (II) UnloadModule: "nv"
[ 5.571] (II) Unloading nv
[ 5.571] (EE) Failed to load module "nv" (module does not exist, 0)
[ 5.571] (II) LoadModule: "vesa"
[ 5.571] (WW) Warning, couldn't open module vesa
[ 5.571] (II) UnloadModule: "vesa"
[ 5.571] (II) Unloading vesa
[ 5.571] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 5.571] (II) LoadModule: "modesetting"
[ 5.571] (WW) Warning, couldn't open module modesetting
[ 5.571] (II) UnloadModule: "modesetting"
[ 5.571] (II) Unloading modesetting
[ 5.571] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 5.571] (II) LoadModule: "fbdev"
[ 5.571] (WW) Warning, couldn't open module fbdev
[ 5.571] (II) UnloadModule: "fbdev"
[ 5.571] (II) Unloading fbdev
[ 5.571] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 5.571] (II) NVIDIA dlloader X Driver 313.30 Wed Mar 27 15:33:21 PDT 2013
[ 5.571] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 5.572] (++) using VT number 7
[ 5.596] (II) Loading sub module "wfb"
[ 5.596] (II) LoadModule: "wfb"
[ 5.596] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 5.597] (II) Module wfb: vendor="X.Org Foundation"
[ 5.597] compiled for 1.14.1, module version = 1.0.0
[ 5.597] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.597] (II) Loading sub module "ramdac"
[ 5.597] (II) LoadModule: "ramdac"
[ 5.597] (II) Module "ramdac" already built-in
[ 5.598] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 5.598] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 5.598] (==) NVIDIA(0): RGB weight 888
[ 5.598] (==) NVIDIA(0): Default visual is TrueColor
[ 5.598] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 5.599] (**) NVIDIA(0): Enabling 2D acceleration
[ 6.276] (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-2
[ 6.283] (II) NVIDIA(0): NVIDIA GPU GeForce GT 555M (GF106) at PCI:1:0:0 (GPU-0)
[ 6.283] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 6.283] (--) NVIDIA(0): VideoBIOS: 70.06.32.00.03
[ 6.283] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 6.521] (--) NVIDIA(0): Valid display device(s) on GeForce GT 555M at PCI:1:0:0
[ 6.521] (--) NVIDIA(0): DFP-0
[ 6.521] (--) NVIDIA(0): DFP-1
[ 6.521] (--) NVIDIA(0): LGD (DFP-2) (connected)
[ 6.521] (--) NVIDIA(0): DFP-3
[ 6.521] (--) NVIDIA(0): DFP-0: 165.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 6.521] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 6.521] (--) NVIDIA(0): LGD (DFP-2): 480.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): LGD (DFP-2): Internal DisplayPort
[ 6.521] (--) NVIDIA(0): DFP-3: 480.0 MHz maximum pixel clock
[ 6.521] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 6.521] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 6.521] (**) NVIDIA(0): device LGD (DFP-2) (Using EDID frequencies has been
[ 6.521] (**) NVIDIA(0): enabled on all display devices.)
[ 6.530] (==) NVIDIA(0):
[ 6.530] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 6.530] (==) NVIDIA(0): will be used as the requested mode.
[ 6.530] (==) NVIDIA(0):
[ 6.530] (II) NVIDIA(0): Validated MetaModes:
[ 6.530] (II) NVIDIA(0): "DFP-2:nvidia-auto-select"
[ 6.530] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 6.534] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 6.535] (--) NVIDIA(0): option
[ 6.535] (--) Depth 24 pixmap format is 32 bpp
[ 6.535] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 6.535] (II) NVIDIA: access.
[ 6.637] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 6.637] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 6.637] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 6.637] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 6.637] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 6.637] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 6.637] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 6.637] (II) NVIDIA(0): Config Options in the README.
[ 6.657] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
[ 6.747] Loading extension NV-GLX
[ 6.788] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 6.788] (==) NVIDIA(0): Backing store disabled
[ 6.788] (==) NVIDIA(0): Silken mouse enabled
[ 6.789] (==) NVIDIA(0): DPMS enabled
[ 6.789] Loading extension NV-CONTROL
[ 6.789] Loading extension XINERAMA
[ 6.789] (II) Loading sub module "dri2"
[ 6.789] (II) LoadModule: "dri2"
[ 6.789] (II) Module "dri2" already built-in
[ 6.789] (II) NVIDIA(0): [DRI2] Setup complete
[ 6.789] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 6.789] (--) RandR disabled
[ 6.794] (II) Initializing extension GLX
[ 6.891] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 6.891] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.891] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 6.891] (II) LoadModule: "evdev"
[ 6.891] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.892] (II) Module evdev: vendor="X.Org Foundation"
[ 6.892] compiled for 1.14.0, module version = 2.8.0
[ 6.892] Module class: X.Org XInput Driver
[ 6.892] ABI class: X.Org XInput driver, version 19.1
[ 6.892] (II) Using input driver 'evdev' for 'Power Button'
[ 6.892] (**) Power Button: always reports core events
[ 6.892] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 6.892] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.892] (--) evdev: Power Button: Found keys
[ 6.892] (II) evdev: Power Button: Configuring as keyboard
[ 6.892] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 6.892] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 6.893] (**) Option "xkb_rules" "evdev"
[ 6.893] (**) Option "xkb_model" "evdev"
[ 6.893] (**) Option "xkb_layout" "gb"
[ 6.936] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
[ 6.936] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6.936] (**) Video Bus: Applying InputClass "Keyboard Defaults"
[ 6.936] (II) Using input driver 'evdev' for 'Video Bus'
[ 6.936] (**) Video Bus: always reports core events
[ 6.936] (**) evdev: Video Bus: Device: "/dev/input/event7"
[ 6.936] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6.936] (--) evdev: Video Bus: Found keys
[ 6.936] (II) evdev: Video Bus: Configuring as keyboard
[ 6.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input7/event7"
[ 6.936] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 6.936] (**) Option "xkb_rules" "evdev"
[ 6.936] (**) Option "xkb_model" "evdev"
[ 6.936] (**) Option "xkb_layout" "gb"
[ 6.937] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 6.937] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.937] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 6.937] (II) Using input driver 'evdev' for 'Power Button'
[ 6.937] (**) Power Button: always reports core events
[ 6.937] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 6.937] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.937] (--) evdev: Power Button: Found keys
[ 6.937] (II) evdev: Power Button: Configuring as keyboard
[ 6.937] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[ 6.937] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 6.937] (**) Option "xkb_rules" "evdev"
[ 6.937] (**) Option "xkb_model" "evdev"
[ 6.938] (**) Option "xkb_layout" "gb"
[ 6.939] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
[ 6.939] (II) No input driver specified, ignoring this device.
[ 6.939] (II) This device may have been added with another device file.
[ 6.939] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 6.939] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 6.939] (**) Sleep Button: Applying InputClass "Keyboard Defaults"
[ 6.939] (II) Using input driver 'evdev' for 'Sleep Button'
[ 6.939] (**) Sleep Button: always reports core events
[ 6.939] (**) evdev: Sleep Button: Device: "/dev/input/event2"
[ 6.939] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 6.939] (--) evdev: Sleep Button: Found keys
[ 6.939] (II) evdev: Sleep Button: Configuring as keyboard
[ 6.939] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2/event2"
[ 6.939] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 6.939] (**) Option "xkb_rules" "evdev"
[ 6.939] (**) Option "xkb_model" "evdev"
[ 6.939] (**) Option "xkb_layout" "gb"
[ 6.941] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
[ 6.941] (II) No input driver specified, ignoring this device.
[ 6.941] (II) This device may have been added with another device file.
[ 6.941] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
[ 6.941] (II) No input driver specified, ignoring this device.
[ 6.941] (II) This device may have been added with another device file.
[ 6.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
[ 6.942] (II) No input driver specified, ignoring this device.
[ 6.942] (II) This device may have been added with another device file.
[ 6.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
[ 6.942] (II) No input driver specified, ignoring this device.
[ 6.942] (II) This device may have been added with another device file.
[ 6.943] (II) config/udev: Adding input device Laptop_Integrated_Webcam_2HDM (/dev/input/event6)
[ 6.943] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "evdev keyboard catchall"
[ 6.943] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "Keyboard Defaults"
[ 6.943] (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_2HDM'
[ 6.943] (**) Laptop_Integrated_Webcam_2HDM: always reports core events
[ 6.943] (**) evdev: Laptop_Integrated_Webcam_2HDM: Device: "/dev/input/event6"
[ 6.943] (--) evdev: Laptop_Integrated_Webcam_2HDM: Vendor 0x408 Product 0x2fb1
[ 6.943] (--) evdev: Laptop_Integrated_Webcam_2HDM: Found keys
[ 6.943] (II) evdev: Laptop_Integrated_Webcam_2HDM: Configuring as keyboard
[ 6.943] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input6/event6"
[ 6.943] (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_2HDM" (type: KEYBOARD, id 10)
[ 6.943] (**) Option "xkb_rules" "evdev"
[ 6.943] (**) Option "xkb_model" "evdev"
[ 6.943] (**) Option "xkb_layout" "gb"
[ 6.944] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[ 6.944] (II) No input driver specified, ignoring this device.
[ 6.944] (II) This device may have been added with another device file.
[ 6.945] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
[ 6.945] (II) No input driver specified, ignoring this device.
[ 6.945] (II) This device may have been added with another device file.
[ 6.945] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
[ 6.945] (II) No input driver specified, ignoring this device.
[ 6.945] (II) This device may have been added with another device file.
[ 6.946] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event13)
[ 6.946] (II) No input driver specified, ignoring this device.
[ 6.946] (II) This device may have been added with another device file.
[ 6.946] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6.946] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 6.946] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
[ 6.946] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 6.946] (**) AT Translated Set 2 keyboard: always reports core events
[ 6.946] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 6.946] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 6.946] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 6.946] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 6.946] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6.946] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 6.946] (**) Option "xkb_rules" "evdev"
[ 6.946] (**) Option "xkb_model" "evdev"
[ 6.946] (**) Option "xkb_layout" "gb"
[ 6.947] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
[ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 6.947] (II) LoadModule: "synaptics"
[ 6.947] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 6.948] (II) Module synaptics: vendor="X.Org Foundation"
[ 6.948] compiled for 1.14.0, module version = 1.7.0
[ 6.948] Module class: X.Org XInput Driver
[ 6.948] ABI class: X.Org XInput driver, version 19.1
[ 6.948] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 6.948] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6.948] (**) Option "Device" "/dev/input/event9"
[ 6.967] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5398 (res 42)
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4728 (res 70)
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 6.967] (**) Option "VertEdgeScroll" "on"
[ 6.967] (**) Option "TapButton1" "1"
[ 6.967] (**) Option "TapButton2" "2"
[ 6.967] (**) Option "TapButton3" "3"
[ 6.967] (**) Option "CoastingSpeed" "0"
[ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6.967] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6.986] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
[ 6.997] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
[ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.039
[ 6.997] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 6.998] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6.998] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 6.998] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 6.999] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 6.999] (II) No input driver specified, ignoring this device.
[ 6.999] (II) This device may have been added with another device file.
[ 7.000] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event8)
[ 7.000] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 7.000] (**) Dell WMI hotkeys: Applying InputClass "Keyboard Defaults"
[ 7.000] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[ 7.000] (**) Dell WMI hotkeys: always reports core events
[ 7.000] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event8"
[ 7.000] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[ 7.000] (--) evdev: Dell WMI hotkeys: Found keys
[ 7.000] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[ 7.000] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event8"
[ 7.000] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 13)
[ 7.000] (**) Option "xkb_rules" "evdev"
[ 7.000] (**) Option "xkb_model" "evdev"
[ 7.000] (**) Option "xkb_layout" "gb"
[ 24.896] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 24.896] (**) NVIDIA(0): device LGD (DFP-2) (Using EDID frequencies has been
[ 24.896] (**) NVIDIA(0): enabled on all display devices.)
And my 50-synaptics.conf file (ignore the do not edit this file warning, it's been copied and pasted into the /etc/X11/xorg.conf.d/ directory):
# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
# Option "OptionName" "value"
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "VertEdgeScroll" "on"
Option "CoastingSpeed" "0"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
MatchDevicePath "/dev/input/event*"
EndSection
Section "InputClass"
Identifier "touchpad ignore duplicates"
MatchIsTouchpad "on"
MatchOS "Linux"
MatchDevicePath "/dev/input/mouse*"
Option "Ignore" "on"
EndSection
# This option enables the bottom right corner to be a right button on
# non-synaptics clickpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Default clickpad buttons"
MatchDriver "synaptics"
Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
# To disable the bottom edge area so the buttons only work as buttons,
# not for movement, set the AreaBottomEdge
# Option "AreaBottomEdge" "82%"
EndSection
# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Disable clickpad buttons on Apple touchpads"
MatchProduct "Apple|bcm5974"
MatchDriver "synaptics"
Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection
Thanks in advanceHello kal33,
Welcome to the HP Forums!
I understand the left part of the clickpad is not working. To assist you, please try all of the steps in this HP document: Using and Troubleshooting the TouchPad or ClickPad (Windows 8)
If these steps do not help, then there could be a hardware issue. Since the computer is in warranty, I would contact HP phone support for hardware assistance. You can utilize this website to learn how to contact HP appropriately, based on your region: Contact HP Worldwide
Please let me know if you have any other questions or concerns. Thanks for bringing this issue to the HP Forums. Have a great day!
Mario
I worked on behalf of HP. -
Touchpad touchscreen problems (erratic behavior/not responding correctly/etc) temporary solution.
I bought a HP Touchpad about a month or two after it came out. It worked pretty much as you'd expect it to until some time ago. I started getting a problem where the screen would go crazy and not respond correctly to my touch inputs. Web pages would jump all over the place, cards would zoom out, etc, in other words, they would behave erratically. After some testing I noticed that certain areas of the touchscreen would NOT respond at all to inputs while others would make the screen go crazy like I mentioned previously. I looked for information on the web to see if other people where having the same problem and found reports of the same behavior. Unfortunately there where no solutions offered. At that point I tried turning on and off the Touchpad which did not resolve the problem. My next step was to try to reinstall the OS with WebOS Doctor, but I read a post where the user reported similar behavior and reinstalling with WebOS Doctor didn't fix the problem. Needless to say I was bummed out since I figured it was a hardware problem with the touchscreen. After more testing I found a temporary solution to the problem which seems to suggest that the probem could be software. The solution when you get the problem is to hold down the power button and the home button at the same time and keep them pressed until the screen shuts down and the touchpad restarts. Once the OS comes back up it works like it is supposed to until you get the next episode of screen epilepsy. At that point you need to do the procedure again and it will fix the problem temporarily. Usually the fix lasts for a few days in my case. The fix also solves other problems I have with the touchpad. Problems like, videos not playing fluidly or freezing every few seconds although the sound plays fine (youtube), sound gets messed up (sounds are played in a robot like pitch), and others. If anybody has questions or other suggestions let me know, I will answer the as best as I can.
Post relates to: HP TouchPad (WiFi)I think the YouTube and sound problems are separate from the other erratic behaviour. Recently my touchpad won't play YouTube videos beyond certain points, starting a few seconds in possibly due to the advertising pop-ups - I can skip forwards, but that means I miss crucial parts. My sound also goes 'robot-like' until a reboot, which is incredibly annoying! Your touchscreen problems may be specific to your device - try going to Device Info / Diagnostics and see if that tells you anything.
-
[SOLVED] Slow/sluggish touchpad buttons response (sometimes)
Hi all,
I have had this problem for some months now but have never looked into it, even if it is pretty annoying.
Sometimes (say one boot every three) the touchpad buttons of my laptop (see sig) behave strangely. Their response time is very long, I have to keep them pressed for ~half a second to make them trigger correctly.
This is very annoying when editing texts (selection a section of text with the touchpad) and using any click intensive application (ie editing a presentation with Prezi).
I use KDE and the only touchpad configuration I've ever done has been done via synaptiks.
I cannot tell after what update this started, it was too long ago unfortunately.
Since this happens only sometimes I don't even know where to start looking!
EDIT: I stress the fact that this happens with buttons, not with tapping
Last edited by OdinEidolon (2014-06-29 09:19:30)Just FYI,
this one solved itself some months ago after some kind of update. -
Macbook pro touchpad/curser problems.
macbook pro touchpad curser problems. typing randomly jumps to wherever the curser is resting at the time. unbelievably maddening. multiple devices same all have same problem. hard to believe we cannot find anything on the apple site about this. MANY complaints outside of this site on this issue... clearly a touchpad/battery design flaw being ignored by Cupertino. during the writing of this post, the curser jumped randomly and started typing in a different location six times. IMPOSSIBLE to use as a word processor since typing becomes quite frustrating. HELP. any ideas? Fanboy and shareholder. three macbook pros in the house...all the same problem. (please do not offer separate keyboard as solution...this is a laptop, not a Surface Pro...)
Go step by step and test.
1. Restart
2. Shut down the computer.
Clean the trackpad with moist not wet microfiber cloth.
System Preferences > Point & Click
Try turning off three finger dragging and then turning it on after testing.
3. Is there any Bluetooth device nearby with failing batteries? If so, replace the batteries.
4. Reset PRAM: http://support.apple.com/kb/PH14222
5. Reset SMC. http://support.apple.com/kb/HT3964
Choose the method for:
"Resetting SMC on portables with a battery you should not remove on your own".
6. Close all windows and quit all applications.
Click the Spotlight -the magnifying glass icon- in the menu bar. Enter Disk utility in the box.
Select Disk Utility from the drop down. When the Disk utility window opens up,
select Macintosh HD, then First Aid.
Click Repair Disk Permissions button.
Ignore the time remaining estimate. -
I recently bought a base model macbook. The touchpad button was placed more left than it should be, thus when you click the left part of the button, sometimes it rub the body and then not only generate annoying sound but also make the click difficult. Also the distance between the right side of button and the body is a little bit bigger than that on the left which makes the macbook looks wierd.
Does anyone know how to fix it (Probably just reposite the button a little to the right) easily other than send it to apple and wait?Not sure that this is the same, but my Macbook's trackpad responds intermittently. After MB's in use for say 4 minutes, when I try using the trackpad, it doesn't respond. Always on the left. The left side of the trackpad is unresponsive!
Other problem is the mooing or purring of my optical disk(?).
I am thoroughly disappointed at the performance and these little kinks are annoying! Not to mention the service at the Apple store, from one employee telling me to open my window to let more noise in, in order to drown the mooing/purring sound to another bribing me to buy ProCare, saying only then would they swap the FAULTY Macbook.
Disappointed. Anyone have any ideas how to go about this one? -
Disable Touchpad BUTTONS on an EliteBook 8570w
Dear HP:
I have an HP EliteBook 8570w, which I must say is the most awesome mobile workstation EVER. If only I could solve one problem...
The touchpad BUTTONS - specifically the ones above the touchpad - how can I disable them? I have large hands and find myself accidentaly hitting the buttons, resulting in losing entire paragraphs of text or launching programs I didn't intend to launch. HELP!
Sincerly,
Robert Sytek
Nationwide Inusrance
Columbus, Ohio
This question was solved.
View Solution.Hello RSytek,
Your EliteBook is a Business model. Your issue would be best answered on the HP Enterprise Business Community Forum
Good luck!
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓ -
Hi guys,
So the problem with my laptop is that when I press the power button, the power button itself and the two leftmost lights below the touchpad- power and battery- they light up for a second or two. But the laptop doesn't start up and the lights go off. If I long press the power button, the laptop starts, though.
Now this is not a severe problem as of now, I know. But I'm pretty sure this will escalate into something else. Does anyone know what the problem actually is and what I can do to solve it?
P.S.: Unlike people with power button problems, I didn't do anything with the hardware or software.Hi Sanjana,
Welcome to Lenovo Community!
I’m sorry to hear that the Power button is not working as expected in your G750 Laptop. I would suggest you to perform the Flee-Power, below are the steps to perform the same:
Remove the battery and any other peripheral device connected to the computer.
Hold the power button for 10-15 seconds and then connect only the AC Adapter and try to turn ON the computer.
If the issue persists even after performing Flee-Power, I would suggest you to contact our Technical Support for further Assistance to get the details of the nearest Authorized Service Center to get the issue analyzed.
Click here to open a link where you can select the country and get the exact contact support number. I’m sure they will be a great help.
Do post us back for further queries.
Best Regards
Shiva Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
T430 right touchpad button stuck
Hello,
I'm not sure whether this issue has been talked about here, but i can't find anything on the subject anywhere.
My T430 right touchpad button gets stuck whenever i press it (by stuck, i mean mechanically stuck). Is there anyone else with the same problem?Hi,
Welcome to Lenovo Community Forums!
I’m sorry to hear that right click button of the touchpad got stuck in your Lenovo ThinkPad T430.
In some situations dirt, hair, dust, etc. can obstruct the buttons causing them not to work. Try to insert a sheet of thick paper under the button to remove the dirt that can be stuck there.
If you are confident enough, you can open the laptop to reach under the touchpad, clean and do a proper reseating. Refer the hardware maintenance manual to understand how to reseat the palm rest assembly.
Hope this helps!
Best regards,
Mithun.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
Hello,
Yesterday I bought my new Lenovo T430u and I just saw that one touchpad button right hand side is not in flush. Can it be a problem in the future that touch the display when lid is being closed ?
Link to image 1
Link to image 2
Link to image 3
Link to image 4
Moderator comment: Image(s) >50KB (or totaling >50KB) converted to link(s). Community Rules.pajan2 wrote:
Should I look for a Lenovo service or is a kind of DIY ?
How comfortable are you working inside PCs/laptops?
Have a look at pages 63-66 of your Hardware Maintenance Manual.
Simply reseating the keyboard doesn't look too bad, but take care with the connectors. They are different than many other T-series, but I don't think you'll need to disconnect just to reseat the keyboard.
Hope this helps.
Regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee. -
I've recently just got a ENVY dv6-7307tx less than a week ago. The thing is, the touchpad buttons are irritatingly noisy, especially the left click button. ): It requires extra force to push down and it makes this annoyingly loud sound. Is this how the buttons are supposed to sound like on this model? My previous model, Pavilion tx2000, is so much quieter.
Can this be a faulty hardware or is it just like that? And can something be done to correct this problem?Hello Kayley_charissa,
Normally the touchpad doesn’t have a noise that it physically makes. Because it is less than a week old you have a couple choices, you can contact HP support to talk about a possible service repair, or you can contact the location that you purchased the computer from. They would normally have some options for you.
Please respond back at your earliest convenience.
Thanks
Clicking the White Kudos star on the left is a way to say Thanks!
Clicking the 'Accept as Solution' button is a way to let others know which steps helped solve the problem! -
Hello all
I just bought a Lenovo N500. I find that the touchpad buttons are rather hard and noisy. We have 4 other laptops in the family (HP, Dell, Acer) and no one is so noisy. On my HP 8510w for example, there is absolutely no noise.
Is there a way to reduce the noise when I click with the touchpad button ?
Thanks for a hint
jsHello Kayley_charissa,
Normally the touchpad doesn’t have a noise that it physically makes. Because it is less than a week old you have a couple choices, you can contact HP support to talk about a possible service repair, or you can contact the location that you purchased the computer from. They would normally have some options for you.
Please respond back at your earliest convenience.
Thanks
Clicking the White Kudos star on the left is a way to say Thanks!
Clicking the 'Accept as Solution' button is a way to let others know which steps helped solve the problem! -
Two finger scrolling does not work on Synaptics touchpad + clicking problems in web browsers
Hello, Since yesterday, i have problems with my synaptics touchpad on my HP Elitebook 8570w.The two finger scrolling and scrolling at the edge of the pad does not work.Also in google Chrome, all the links open in a new tab and when i try to click the new tab, it closes (normally that is the action when i click it with the middle touchpad button) Even in the practice mode of the synaptics settings of the touchpad, the two finger scrolling and edge scrolling does not work. Both options are enabled in the settings. I already tried to roll back the driver and reinstall the driver, without any effect.I expect the problem is the touchpad or the buttons itself. Is there a way to test the buttons and touch pad? How can i solve this problem? please help me sincerely, Karel
I would try installing the Windows 8.1 (64-bit) Synaptics touchpad driver available in your sleekbook's web support download section before using compatibility mode. Try the available earlier versions if the current driver does not work for you.
If you still do not have positive results, then use compatibility mode (choose Windows 8) on all three Windows 8.1 synaptics touchpad drivers, starting with the most current one.
To use compatibility mode to install the driver softpaq just right click on the file and choose troubleshoot compatibility. Choose Windows 8 and run the installer.
The following video has a decent explanation, but the narrator does not get to the point for a bit. Skip forward to minute 4 and watch it from there.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer
Maybe you are looking for
-
Windows 7 error code 0x80070017
Trying to install Windows 7 on my 2011 MacPro using Boot Camp Assistant. Using a download purchase of Windows 7 Pro burned onto a DVD. Installer runs but eventually stops on an incomplete Step 2 (Expanding files I think) with Error Code 0x80070017. P
-
Different Tax condition records picked on sales order and invoice
Dear Expert, I have a scenario where the goods supply from plant to different country sales organization customer. it is a n export order. . sales order has been processed with ship to address in Portugal. We did enter end user VATnumber on the ship
-
PSE 7 Sort order in file folder view
In Thumbnail view I can order the photos by oldest first or newest first. When I change my display option to folder view the photos do not display in any order. Not the order taken (oldest to newest) or (newest to oldest) or by filename. I am unable
-
Hi, I need to learn ALV grid, Please give a good material or links to start of with basics of ALV. Also send me step by step procedure to create simple Alv grid example programs. Thanks in advance, Sachidanand.B
-
Hi.. SAP Content Server 6.40 on Solaris 10, Apache 1.3. xx installed successfully. i unable to connect from ECC to SAP Content server gives error in error_logs of app ache [Mon Sep 6 14:46:55 2010] [error] [client 172.16.20.219] File does not exist: