Description of problem: On an Optimus laptop (ASUS) with an MX150 discrete GPU, upgrading to 4.14.50 broke the GPU (whether I'm using Bumblebee or mageia-prime). I'm using the "pcie_port_pm=off" boot option for all kernel versions. Trying to run anything with bumblebee gives: > $ primusrun glxspheres64 > primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver And dmesg gives: > [ 50.081664] nvidia-nvlink: Nvlink Core is being initialized, major device number 244 > [ 50.475307] nvidia 0000:01:00.0: enabling device (0000 -> 0003) > [ 50.625646] NVRM: The NVIDIA GPU 0000:01:00.0 > NVRM: (PCI ID: 10de:1d10) installed in this system has > NVRM: fallen off the bus and is not responding to commands. > [ 50.675784] nvidia: probe of 0000:01:00.0 failed with error -1 > [ 50.675799] NVRM: The NVIDIA probe routine failed for 1 device(s). > [ 50.675800] NVRM: None of the NVIDIA graphics adapters were initialized! > [ 50.675885] nvidia-nvlink: Unregistered the Nvlink Core, major device number 244 Version-Release number of selected component (if applicable): 4.14.50-desktop-2.mga6 How reproducible: All the time. Steps to Reproduce: 1. Install bumblebee on said hardware 2. Start any program with bumblebee, or run "modprobe nvidia-current"
CC: (none) => marja11Assignee: bugsquad => kernel
Summary: NVIDIA GPU "fallen off the bus" => NVIDIA GPU "fallen off the bus" - upgrading to 4.14.50 broke the GPU
FYI, there is now kernel 4.14.55-desktop in updates testing, i am running it OK now on a Nvidia-only system.
CC: (none) => fri
Thanks for the hint Morgan. I've just tried 4.14.55, it has the same problem as 4.14.50 on my setup.
There is now a 4.14.56 in testing: https://bugs.mageia.org/show_bug.cgi?id=23315 And a new nvidia-current: https://bugs.mageia.org/show_bug.cgi?id=23316 Does any of them solve the issue for you ?
CC: (none) => tmb
Problem is solved with the new kernel. Thank you Thomas.
Status: NEW => RESOLVEDResolution: (none) => FIXED
I'm sorry, I must have missed something (not sure how). The problem is still there with 4.14.56.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Problem is fixed with current kernel and nvidia driver.
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED