Bumblebee not working in Ubuntu 16.04 #759
Comments
|
optirun -vv glxgears |
|
Same here (Ubuntu 16.04 amd64) With none of the available drivers from "ppa:graphics-drivers/ppa" bumblebee is working. Probably should try "ppa:xorg-edgers/ppa" ??? PS: Ubuntu 14.04 and nvidia-352 runs perfectly. |
|
This line should serve as starting point: Apparently the About bumblebee-ui, it was removed on 5 March, perhaps @ArchangeGabriel knows more about it? |
|
@Lekensteyn |
|
About bumblebee-ui: everyone implied in it, including @glyptostroboides, was agreeing on the useless state of the code (it wasn’t functionning anymore on any current distro, and it was even a reusable code base), while people where still opening issue about it not working. So, after a one week span for discussion where everyone involved in that repo as agreed, it has been removed. For the state of this project, see #710. I’ll be back soon to handle all pending issues and fixes. |
|
After many hours of trial, I finally get a solution for "optirun Error : Xlib: extension "GLX" missing on display ":8"."
try to run glxinfo & optirun glxinfo to check that all the configurations are correct |
|
Yeah that fixed it for me, I was playing with aliases all afternoon but the real trick was in the path configs, great catch on that. So any guesses on who broke it: ubuntu or nvidia? Edit: In order to make sure running CUDA applications works, I did have to add: to |
|
In order to make CUDA application run without adding those lines (it will load necessary module automatically), you need to install nvidia-modprobe package by command
|
|
Didn't seem to work. When I commented out my addition, Starting glxgears:
|
|
Check out my tutorial for getting bumblebee working on 16.04 LTS: http://lenovolinux.blogspot.com.au/ I finished it a few hours ago. It is well tested on a Lenovo laptop, but may work for you as well. |
|
So, this is a packaging issue specific to Ubuntu 16.04? A bit like #749 so… Definitively don’t like that distro. Anyway, this should probably be reported in Launchpad. |
|
Maybe a bug should be filed at https://bugs.launchpad.net/ubuntu/+source/bumblebee. |
|
The only thing we can do (I'm about to) is to fix the modprobe blacklist to add the new drivers. The update-alternative, the modprobe aliases and the paths have to be configured manually on Ubuntu, because of how the drivers are packaged there. |
|
I've published on the test repository a version that should fix all problems with the modules, if someone is available to help testing it would be great! https://launchpad.net/~bumblebee/+archive/ubuntu/testing Please make sure that /lib/nvidia-/modprobe.conf is symlinked in /etc/modprobe.d/, otherwise link it and run sudo depmod (and then open a bug in launchpad against nvidia-driver). |
|
@sapjunior @Queuecumber - could you please give the testing PPA a shot and see if it solves your issues? |
|
I'll give it a shot today after reverting whatever I did that fixed it before |
|
@bluca Hi, I have used the testing PPA and got the following error: [ 33.789057] [INFO]Running application using primus. |
|
@grzjab - what is your KernelDriver settings in /etc/bumblebee.conf ? Also what's the output of sudo dkms status ? What is the content of /lib/modules/4.4.0-22-generic/updates/dkms ? |
|
|
Try: KernelDriver=nvidia-361 |
|
My 2¢: I'm using Ubuntu 16.04, bumblebee and intel-virtual-output for feeding DVI outputs on a Lenovo T430. My configuration stopped working after upgrading to Ubuntu 16.04, here's what I did differently to the tutorial by @molecularentropy:
Blacklisting nvidia-drm and nvidia-modeset does not seem to be necessary in this configuration: After clean boot, Installing Note that uninstalling the nvidia driver, or installing a different one, fails brutally if the nvidia kernel module is locked. I had to switch to internal graphics in BIOS at some point to revert to a stable apt state. I'm posting this as a self-reminder and in the hope that it will be useful. |
|
Having KernelDriver=nvidia-367 doesn't load nvidia-drm automatically? |
|
@bluca: Doesn't. |
|
Ok. So, with the testing PPA and that configuration, it is working ok for you then? |
|
Yes, optirun works fine with that configuration, and I'll post here tomorrow should intel-virtual-output fail to display on the secondary screens for some reason. |
|
@bluca nothing in /etc/modprobe.d |
|
intel-virtual-output currently does not work with in this configuration. |
|
No haven't backported that, would you like me to? I don't mind if it can be useful/needs testing |
|
It could have explain @krlmlr issue if you had backported it, that’s why I asked. I prefer to wait for nouveau to be dropped and my PR to be rebased against that before it’s integrated. ;) |
|
Chris Wilson, the maintainer of i-v-o, helped a lot sorting out the issue, it looks like a problem with the NVidia driver. I'm now on a patched version of i-v-o, I hope Chris will push a fix soon. |
|
OK, nice to hear. :) |
|
Installing from the https://launchpad.net/~bumblebee/+archive/ubuntu/testing PPA along with nvidia-367 on Ubuntu-gnome 16.04 breaks GDM on boot: I suspect this is breakage in some of the update-alternatives? |
|
Yes most likely, but we don't ship those in bumblebee, they are part of the driver packages. Try to re-configure them: |
Looks like it's pointed in the right place? |
|
Hi |
|
Just here giving thanks. I'm on Ubuntu 14.04 with a 4.6.6 kernel and nvidia-367, and following both @molecularentropy and @krlmlr's instructions, and an extra run of |
Yes, this appears to be a bug related to nvidia-drivers-364+. Could you share the i-v-o patches? Many thanks! |
|
@haarp: Here you go: diff --git a/tools/virtual.c b/tools/virtual.c
index 77e6a58..bf85d74 100644
--- a/tools/virtual.c
+++ b/tools/virtual.c
@@ -631,12 +631,12 @@ static int disable_crtc(Display *dpy, XRRScreenResources *res, RRCrtc crtc)
XRRPanning panning;
if (crtc) {
- XRRSetPanning(dpy, res, crtc, memset(&panning, 0, sizeof(panning)));
+ //XRRSetPanning(dpy, res, crtc, memset(&panning, 0, sizeof(panning)));
if (XRRSetCrtcConfig(dpy, res, crtc, CurrentTime, 0, 0, None, RR_Rotate_0, NULL, 0) != Success)
return 0;
- if (XRRSetPanning(dpy, res, crtc, memset(&panning, 0, sizeof(panning))) != Success) {
+ if (0 && XRRSetPanning(dpy, res, crtc, memset(&panning, 0, sizeof(panning))) != Success) {
DBG(XRR, ("%s failed to clear panning on CRTC:%ld\n", DisplayString(dpy), (long)crtc));
if (verbose) {
XRRCrtcInfo *c;Works for me, but the |
|
Thank you, this works :) |
|
@krlmlr I'm trying to figure out whether Chris Wilson fixed this as you said he'd do and whether the fix has been deployed to Ubuntu 16.04 or a later version of Ubuntu. I'm having difficulty to do so on my own as I'm not familiar enough with the technical details of this yet. Can you have a look please? Some links I gathered, perhaps they may help you: |
|
Thanks. I'm not using Bumblebee anymore, on my new laptop external displays "just work". |
|
I remember using custom builds of ivo ( |
|
@krlmlr Thank you. I've emailed Chris Wilson about this and will cite his answer here. Also can someone here give me a summary of whether any other non-configuration-only fixes are needed on Ubuntu 16.04 or above besides the patch to intel-virtual-output? |
|
Here's a summary of steps addressing this issue that worked for me. |
|
Thanks to everyone in this thread. Adding the nvidia paths to the ld.so.conf files seemed to be what finally fixed it for me. |
|
I have created a new guide on setting up Bumblebee on Ubuntu 17.10. Check it out, if you like: http://lenovolinux.blogspot.com.au/2018/02/bumblebee-on-lenovo-t440p-nvidia-gt.html |
Enviroment : Ubuntu 16.04 // Nvidia 364.15
optirun Error : Xlib: extension "GLX" missing on display ":8".
Interesting Xorg.8.log entry :
Full Xorg Log
The text was updated successfully, but these errors were encountered: