Hide Forgot
Description of problem: I just installed Fedora 23 Cinnamon spin on my new Dell Inspiron 7559 (it is equipped with an I7-6700HQ and a Nvidia GeForce GTX960m 4GB). The laptop came with Windows 10 pre-installed: I added an M2 SSD 250GB (it has a free M2 slot) and moved the OS on it, leaving his 1TB drive as an archive partition. Then, I wanted to add Fedora 23 Cinnamon spin in dual-boot with it. The bootable usb (created with Rufus in Win10) immediately gave me problems: it could not start with the options "Start Fedora Live" or the "Test this media and start Fedora Live" since in both options it got frozen at the end of Fedora logo's loading. Starting the bootable usb via the "Troubleshooting" -> "Start Fedora Live with minimal graphic environment" worked, and I could successfully install Fedora 23 Cinnamon spin with the minimal graphics in dual boot with my Windows 10. Everytime I start the OS, Cinnamon tells me that it started in Software Rendering mode, and tells me that there is some driver issue. It works at full resolution (1920*1080), but naturally it uses a lot of CPU and lags with some applications (IDEs or similar), and the HDMI port isn't working (I'm sure it works since I can normally use it in Windows). The first thing I tried to do was to install Bumblebee following this guide: https://fedoraproject.org/wiki/Bumblebee but, at a certain point, this broke my system: 1) Starting the computer with Secure Boot disabled resulted in an hard freeze of the laptop just before the login screen and after the Fedora logo loading (had to press the power button to turn off my pc by force). I noticed that in this situation with the 5-10% of probability it loaded the login screen, but after the login the system is unusable, with heavy lags and panels, terminals, menus not opening at all. 2) Starting the computer without Secure Boot resulted in a console boot, without graphical environment. I solved this situation by doing a "dnf remove \*nvidia*\". Now, with Secure Boot activated, the system starts in Software Rendering mode. With Secure Boot deactivated, it hard freezes. I played around with the Secure Boot stuff since I noticed that the system could not load the "bbswitch" module with it activated: I guess that in this moment, when Secure Boot is activated, it fails to load bbswitch and so the system starts in Software Rendering mode. At this point I'm quite lost, since I'm not an expert in kernel's or driver's managing. Fedora is fully updated (4.3.3 kernel is the last one installed at time of posting). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1 - Purged everything bumblebee-related; 2 - Those commands to get bumblebee: 543 dnf -y --nogpgcheck install http://install.linux.ncsu.edu/pub/yu...2-1.noarch.rpm 544 dnf -y --nogpgcheck install http://install.linux.ncsu.edu/pub/yu...2-1.noarch.rpm 545 dnf install bumblebee-nvidia bbswitch-dkms VirtualGL.x86_64 VirtualGL.i686 primus.x86_64 primus.i686 kernel-devel 546 dnf --allowerasing install bumblebee-nvidia bbswitch-dkms VirtualGL.x86_64 VirtualGL.i686 primus.x86_64 primus.i686 kernel-devel Now... if I boot with Secure Boot Off, it freezes most of the times. 1 time on 10 it boots, but works strangely and freezes after a while. If I boot with Secure Boot On, it works in software rendering mode. Actual results: Not working video drivers, laptop starts in Software Rendering mode. Expected results: Working video drivers. Additional info: Some outputs. [mike@localhost ~]$ optirun glxgears [ 255.898262] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver [ 255.898305] [ERROR]Aborting because fallback start is disabled. [mike@localhost ~]$ bumblebee-nvidia --check nvidia.ko compiled into in the kernel tree ok. modinfo output for NVIDIA: filename: /lib/modules/4.3.3-300.fc23.x86_64/kernel/drivers/video/nvidia.ko alias: char-major-195-* version: 352.63 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.3.3-300.fc23.x86_64 SMP mod_unload parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp Check bbswitch kernel module... Warning! bbswitch is not loaded into this kernel! Since bbswitch is not loaded into the kernel, lets do additional checks on it... obsolete rpm package bbswitch is installed. It is suggested you remove bbswitch and instead install bbswitch-dkms First, remove bbswitch: rpm -e bbswitch Fedora: dnf install bbswitch-dkms RHEL/CentOS: yum install bbswitch-dkms dkms status bbswitch output: bbswitch, 0.8.0, 4.3.3-300.fc23.x86_64, x86_64: installed if the bbswitch package is installed, you may wish to try: /usr/sbin/dkms add -m bbswitch -v 0.8.0 /usr/sbin/dkms build -m bbswitch -v 0.8.0 /usr/sbin/dkms install -m bbswitch -v 0.8.0 /sbin/modprobe bbswitch To get clues as to why bbswitch is failing on this kernel... All checks completed successfully! NVIDIA driver appears to have compiled ok. Documentation on bumblebee for RHEL / CentOS / fedora can be found at: https://www.linux.ncsu.edu/bumblebee/ Xorg.0.log: http://pastebin.com/rwiujtFs Xorg.8.log: http://pastebin.com/43Z72qDk
I uninstalled Bumblebee, and installed the Rawhide kernel 4.5. The laptop does not freeze anymore booting without secure boot, but it still uses Software rendering. Some output: https://paste.fedoraproject.org/311242/
I found a workaround for now. 1 - Uninstall everything bumblebee-related. 2 - Remove by the kernel parameters "nomodeset".
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.