Hey guyz,
I’m just getting back to use opensuse again and installed Leap 42.2 (KDE 64bit) on my Dell 1555 Laptop.
One minute after log on, the touch pad stops working.
I had tried tumbleweed before Leap 42.2, and it didn’t have such a problem.
I have to restart my system to make it work again (ctrl + alt + backspace twice doesn’t fix the problem)
Any help would be appreciated 
thanks
Welcome to openSUSE Forums bluelight. That is a strange issue. More details about your touchpad hardware might help here. Run these commands to start with and report back with the output. Please enclose the output within code tags (refer to the # button in the forum editor).
/usr/sbin/hwinfo --mouse
xinput
This command will show us what modules are loaded pertaining to the i2c device bus (most built-in touchpads and keyboards are connected to this bus).
lsmod|grep i2c
I had tried tumbleweed before Leap 42.2, and it didn’t have such a problem.
I missed this comment initially. That suggests that using a later kernel may help here. It is easy to try switching to the latest stable kernel using
su -
zypper ar -f http://download.opensuse.org/repositories/Kernel:/stable/standard/ kernel:stable
zypper ref
zypper dup --from kernel:stable
then reboot.
See how that goes.
Hi Deano and thanks a lot for your nice message 
and the outputs are:
/usr/sbin/hwinfo --mouse:
35: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: _***.sgQkEajDP63
Parent ID: KRJj.M4_hFzuaxRD
SysFS ID: /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1.3/3-1.3:1.0
SysFS BusID: 3-1.3:1.0
Hardware Class: mouse
Model: "Logitech Unifying Receiver"
Hotplug: USB
Vendor: usb 0x046d "Logitech, Inc."
Device: usb 0xc52f "Unifying Receiver"
Revision: "22.01"
Compatible to: int 0x0210 0x0028
Driver: "usbhid"
Driver Modules: "usbhid"
Device File: /dev/input/mice (/dev/input/mouse3)
Device Files: /dev/input/mice, /dev/input/mouse3, /dev/input/event14, /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse, /dev/input/by-path/pci-0000:00:12.0-usb-0:1.3:1.0-event-mouse, /dev/input/by-id/usb-Logitech_USB_Receiver-mouse, /dev/input/by-path/pci-0000:00:12.0-usb-0:1.3:1.0-mouse
Device Number: char 13:63 (char 13:35)
Speed: 12 Mbps
Module Alias: "usb:v046DpC52Fd2201dc00dsc00dp00ic03isc01ip02in00"
Driver Info #0:
Buttons: 8
Wheels: 2
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #33 (Hub)
40: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: cLrx.op6E2fGFltA
Parent ID: k4bc._63LoM0erv2
SysFS ID: /devices/pci0000:00/0000:00:10.0/usb1/1-2/1-2:1.0
SysFS BusID: 1-2:1.0
Hardware Class: mouse
Model: "G2Touch Multi-Touch by G2TSP"
Hotplug: USB
Vendor: usb 0x2a94 "G2Touch"
Device: usb 0x5201 "Multi-Touch by G2TSP"
Revision: "2.00"
Compatible to: int 0x0210 0x0000
Driver: "usbhid"
Driver Modules: "usbhid"
Device File: /dev/input/mice (/dev/input/mouse2)
Device Files: /dev/input/mice, /dev/input/mouse2, /dev/input/event10, /dev/input/by-id/usb-G2Touch_Multi-Touch_by_G2TSP-event-if00, /dev/input/by-path/pci-0000:00:10.0-usb-0:2:1.0-event
Device Number: char 13:63 (char 13:34)
Speed: 12 Mbps
Module Alias: "usb:v2A94p5201d0200dc00dsc00dp00ic03isc01ip02in00"
Driver Info #0:
Buttons: 0
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #37 (Hub)
48: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.249]
Unique ID: AH6Q.Y_f5kDtfqz2
Hardware Class: mouse
Model: "SynPS/2 Synaptics TouchPad"
Vendor: 0x0002
Device: 0x0007 "SynPS/2 Synaptics TouchPad"
Compatible to: int 0x0210 0x0001
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
Device Number: char 13:63 (char 13:32)
Driver Info #0:
Buttons: 1
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
49: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.249]
Unique ID: AH6Q.MNJ6HzHv6tC
Hardware Class: mouse
Model: "DLL07BD:00 06CB:75BF Touchpad"
Vendor: 0x06cb
Device: 0x75bf "DLL07BD:00 06CB:75BF Touchpad"
Compatible to: int 0x0210 0x0001
Device File: /dev/input/mice (/dev/input/mouse1)
Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event9, /dev/input/by-path/platform-AMD0010:00-event-mouse, /dev/input/by-path/platform-AMD0010:00-mouse
Device Number: char 13:63 (char 13:33)
Driver Info #0:
Buttons: 1
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
xinput:
If 'xinput' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf xinput
lsmod|grep i2c:
i2c_piix4 24576 0
i2c_designware_platform 16384 0
i2c_designware_core 20480 1 i2c_designware_platform
i2c_algo_bit 16384 1 amdgpu
i2c_hid 20480 0
After this I get the following error:
loading linux 4.10.12-1
error: /boot/vmlinux-4.10.12.1 default has invalid signature.
Loading initial ramdisk ...
error: you need to load the kernel first.
press any key to continue
And I had to get back to the previous one from advance menu snapshot
Disable secure-boot in your BIOS settings, so that you can test the new kernel.
There are ways of getting it to boot with secure-boot. But you are just testing, so for now the easiest is to disable secure-boot.
hi nrickert and thanks for your message,
I disabled secure-boot, but after that my laptop straightly booted to Windows 10 without any sign of Grub 2,
I re-enabled secure boot but it seems that the Grub 2 has been removed or something, cuz again my system goes only to Windows without Grub 2 splash.
On many computers, you can hit F12 during boot, and get a BIOS boot menu. Maybe see if that works for you.
If possible, you want to have UEFI enabled but secure-boot disabled. If there’s a BIOS option for CSM (compatibility support module), try disabling that.
No luck,
Is there anyway to bring back grub2?
You might need to boot into rescue mode from a Leap DVD
https://doc.opensuse.org/documentation/leap/startup/single-html/book.opensuse.startup/index.html#sec.trouble.data.recover.rescue
I’m not familiar with EFI systems, so best to wait for further specific advice on this. While waiting, some reading that may be pertinent…
https://forums.opensuse.org/showthread.php/492039-Repair-Grub2-Efi-Boot-Entry-in-Rescue-Console-form-DVD
You might just have one of those systems where the BIOS deletes EFI boot entries that it thinks are not needed. My Dell system tends to do that.
What happens, is it all works nicely for a while. But the BIOS deletes the EFI boot entry for Windows. You don’t notice that, because you can still boot Windows with the grub2 menu.
Then you boot into Windows. And Windows notices that its boot entry is missing. So it reinstalls it. And then the BIOS delete the grub2 boot entry. And now you are stuck.
It can be fixed by booting the install media, mounting the EFI partition somewhere, and using “efibootmgr” to add it back.
Something like
efibootmgr -c -d /dev/sda -p 1 -l '\EFI\opensuse\shim.efi' -L opensuse-secureboot
The man page for “efibootmgr” gives details, and there are online examples. The “-p” parameter is for the partition number of the EFI partition that you are using. The “-l” gives the boot command, best done with Windows path notation, and the “-L” gives the name for the entry.
Or you can go to full rescue mode, and use “shim-install”. But that requires mounting partitions and using “chroot”.
Thank you guyz,
I’m givin it a try and let you know what happened.