Bug 1227411 - Touchpad not work on MBB+I5-3317U HM77 X300 (Exo Nifty N5185P) with Fedora 22 [NEEDINFO]
Summary: Touchpad not work on MBB+I5-3317U HM77 X300 (Exo Nifty N5185P) with Fedora 22
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-02 15:34 UTC by ggsalas
Modified: 2015-11-23 17:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-23 17:14:59 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
fpaste --sysinfo --printonly > fpaste.log (11.64 KB, patch)
2015-06-02 15:34 UTC, ggsalas
no flags Details | Diff

Description ggsalas 2015-06-02 15:34:55 UTC
Created attachment 1033846 [details]
fpaste --sysinfo --printonly > fpaste.log

Description of problem: Touchpad is not working on my ultrabook Exo Nifty N5185P http://www.exo.com.ar/content/nifty-n5185p

On fedora 21 the touchpad can work  adding "splash i8042.noloop=1" to "GRUB_CMDLINE_LINUX" (I found this help on http://samiux.blogspot.com.ar/2011/04/howto-ubuntu-1104-on-gigabyte-touchnote.html )

Yesterday (1/6/15) my touchpad are working (on fedora 22) with:

GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet splash i8042.noloop=1"

Today is not working

How reproducible:
Always

Steps to Reproduce:
1. Liveusb of fedora22
2. Install and update, still not working

Actual results:
The touchpad do not work.

Expected results:
Work normally


Additional info:   

$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech USB Receiver                   	id=10	[slave  pointer  (2)]
⎜   ↳ Logitech USB Receiver                   	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=12	[slave  keyboard (3)]


$ lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

$ lsusb
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Comment 1 ggsalas 2015-06-03 14:23:34 UTC
I have found a way to use the touchpad at least one time. This is the workaround:

1. Boot with fedora 22 liveusb plug on the pc
2. Select this option on boot menu http://i.imgur.com/qKdumnY.png
3. See this error http://i.imgur.com/d1tLRK7.png
4. Ctrl+Alt+Del
5. Normal boot and get touchpado working!

For this to work you need configure the grub on this way (same as fedora 21):

- Edit /etc/default/grub
- Add "i8042.noloop=1" to "GRUB_CMDLINE_LINUX"
- Do: grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Hope this helps to fix this bug. Not is a good fix do this each time you boot.

Comment 2 ggsalas 2015-06-15 00:34:58 UTC
 On the bios configuration I have changed Fast boot > VGA support > "Efi driver" for "Auto" and now it's working. Hope this helps. Screenchot: http://i.imgur.com/dVnfJgA.png

Comment 3 Justin M. Forbes 2015-10-20 19:26:41 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.

Comment 4 Fedora Kernel Team 2015-11-23 17:14:59 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.