Open gdkrmr opened 7 years ago
Please report this to the nvidia-375 Ubuntu maintainers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1703014
I thought this was a bumblebee issue, reported it anyways to launchpad. CUDA applications crash with error code 999 if I configure the update-alternatives to the mesa driver, but then I get the boot loop if I forget to reconfigure before a reboot.
Also see here: https://github.com/JuliaGPU/CUDAdrv.jl/issues/50
I reported this here, because it started appearing after the last update of bumblebee (3/7/17, bumblebee
and bumblebee-nvidia
, each 3.2.1-100~xenialppa1
over 3.2.1-98~xenialppa1
) from the ubuntu testing ppa (http://ppa.launchpad.net/bumblebee/testing/ubuntu). The last nvidia update was on 1/6/17.
There were only tiny changes, as the blacklist/dependency alternatives for new driver series (378, 381, 384) was added between those 2 versions. Nothing else changed.
You can see the commits here: https://github.com/Bumblebee-Project/bumblebee-ppa/commits/master
Given you are running 375, those changes do not affect your setup in any way.
that is strange, it is probably some issue with my configuration then.
on Ubuntu 16.04, bumblebee testing and nvidia 3.75:
when choosing the nvidia gl driver from
update-alternatives --config x86_64-linux-gnu_gl_conf
, gdm gets stuck in a start-crash loop at startup, when choosing the mesa driver cuda applications do not work: