Description of problem: During bootup Fedora 25 displays nouveau: 136000a1 unrecognised chipset for gtx 1060 on my optimus notebook. In details in Gnome I have only Intel HD 530 (Skylake GT2) displayed. This is urgent, since most likely because of that and HDMI monitor can't be seen (HDMI is most likely connected to Nvidia). I will file a separate bug about this. Version-Release number of selected component (if applicable): How reproducible: Try to boot fedora on optimus enabled GALLERIA QSF1060HE laptop with Nvidia gtx 1060. Steps to Reproduce: 1. Install fedora 25 2. Boot Actual results: nouveau: 136000a1 unrecognised chipset message No nvidia card displayed in details No HDMI monitor detected Expected results: no error message from nouveau detection of external HDMI monitor
The situation remains unchanged in kernel 4.9.3.
I have this problem too. Using the proprietary NVIDIA drivers worked but it comes at cost of efficient power management (no Intel/Nvidia switch), battery life becomes half it could be.
My Fedora 24 installation on a lenovo B560 (Intel / NVIDIA Optimus) with nouveau (standard video driver) stopped recognizing the Optimus chipset after update to Kernel 4.9.X. "Just after login to GNOME, video gets frozen." Deactivating Optimus at BIOS is a workaround to logged to GNOME again. Now, I suspect I have the same problem as reported here (as well as probably many other users). I read anywhere in the Kernel Bug-tracking, that Kernel 4.10. should solve problems with NVIDIA-Optimus laptops. If true, when will Fedora 24 get an update to Kernel 4.10.X?? Many thanks!
After latest fedora update: $ lspci -nn | egrep "VGA" 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) Does this means we are close to have optimus support? :D
Hi marcio, all, In fact, during last weeks, since Fedora released Kernel 9.9.7 my NVIDA Optimus has been recognized and seems to be back working as usual. So, I would suggest you look for an kernel-update.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.