Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nouveau auto-detection not working? #631

Open
keckelt opened this issue Feb 8, 2015 · 10 comments
Open

nouveau auto-detection not working? #631

keckelt opened this issue Feb 8, 2015 · 10 comments

Comments

@keckelt
Copy link

keckelt commented Feb 8, 2015

Distro: Fedora 21 - Workstatioen (FedUp from Fedora 20)
Kernel: 3.17.8-300.fc21.x86_64 and 3.18.3-201.fc21.x86_64
Manufactorer and model:
baseboard-manufacturer: CLEVO CO.
baseboard-product-name: W35_37ET
baseboard-version : N/A
system-manufacturer : CLEVO CO.
system-product-name : W35_37ET
system-version : N/A
bios-vendor : American Megatrends Inc.
bios-version : 4.6.5
bios-release-date : 11/02/2012

Bumblebee Version: optirun (Bumblebee) 3.2.1

Hi, I discovered that Bumblebee stopped working after updating my Kernel.
The latest version i have installed is 3.18.3-201 and there isn't even the bumblee deamon running (calling optirun in terminal), nor can't I start it as modprobe doesn't find the bbswitch module (bumblebeed --daemon). I tried to re-install both, bbswitch and bumblebee, via yum but that didn't change anything.
When i boot 3.17.7-300 from GRUB it still works and my dedicated NVIDIA GPU is turned off; but also bumblebeed --daemon displays:
modprobe: FATAL: Module bbswitch not found.

I recently installed VirtualBox, following the instructions given here:
http://www.if-not-true-then-false.com/2010/install-virtualbox-with-yum-on-fedora-centos-red-hat-rhel/

Besides that, i didn't do anything more unusual than yum update

Any tips appreciated.

@karolherbst
Copy link

it works for me with 3.8.0 - 3.8.5, so I guess it may be your setup. "modprobe: FATAL: Module bbswitch not found." indicates, that the required modules are not built for your kernel.

@keckelt
Copy link
Author

keckelt commented Feb 8, 2015

It worked for over a year now (including 3.17.7 kernel) and I (think I) didn't change anything.

When the module is not built for my kernel, how can it still work?

EDIT:
Just updated to 3.18.5-201 and:
echo OFF > /proc/acpi/bbswitch works as expected.
However, bumblebee daemon is still not running and the nvidia card wasn't deactivated automatically-

@karolherbst
Copy link

I think the issue is, that modprobe doesn't find bbswitch anymore for some reasons.. I guess bumblebee doesn't check whether bbswitch is already loaded or not :/

@gsgatlin
Copy link

gsgatlin commented Feb 8, 2015

Does running these commands help? (as root)

dkms add -m bbswitch -v 0.8.0
dkms build -m bbswitch -v 0.8.0
dkms install -m bbswitch -v 0.8.0

@keckelt
Copy link
Author

keckelt commented Feb 8, 2015

Thanks for the answers, I got held up in the afternoon:
Manually, I can get the daemon running with:

$ sudo modprobe nouveau 
$ bumblebeed --daemon

Has this something to do with the fact that nvidia and nouveau are both blacklisted in /etc/modprobe.d/bumblebee.conf ?

DKMS commands didn't help:

$ sudo dkms add -m bbswitch -v 0.8.0
Error! DKMS tree already contains: bbswitch-0.8.0
You cannot add the same module/version combo more than once.
$ sudo dkms build -m bbswitch -v 0.8.0
Module bbswitch/0.8.0 already built for kernel 3.18.5-201.fc21.x86_64/4
$ sudo dkms install -m bbswitch -v 0.8.0
Module bbswitch/0.8.0 already installed on kernel 3.18.5-201.fc21.x86_64/x86_64

@karolherbst
Copy link

Has this something to do with the fact that nvidia and nouveau are both blacklisted in /etc/modprobe.d/bumblebee.conf ?

no, this is no problem at all. You should be able to run sudo modprobe nvidia at any time.

@keckelt
Copy link
Author

keckelt commented Feb 8, 2015

Hmm,
After changing /etc/modprobe.d/bumblebee.conf to:

blacklist nvidia
#blacklist nouveau

bumblebee works as expected now, i.e. Intel card is used after boot and I can use optirun.

[I use nouveau drivers, not nvidia]

@gsgatlin
Copy link

gsgatlin commented Feb 8, 2015

See issue #582 for using bumblebee with nouveau driver in fedora. My experiences were that bumblebee-nouveau package was required. (and xorg-x11-drv-modesetting had to be removed) But it sounds like maybe you've got it figured out now? Were you trying to use nouveau or nvidia module with bumblebee?

@keckelt
Copy link
Author

keckelt commented Feb 8, 2015

I wasn't using the bumblebee-nouveau-package so I installed it now and reverted the changes in /etc/modprobe.d/bumblebee.conf, but the problems are the same as before.
I will stick to the "solution" above and comment out the blacklisting of nouveau.

@ArchangeGabriel
Copy link
Member

Hum, this could be autodetection not working if nouveau isn’t loaded. Should take a look at that.

@ArchangeGabriel ArchangeGabriel self-assigned this Feb 16, 2015
@ArchangeGabriel ArchangeGabriel added this to the Bumblebee 4.0 milestone Feb 16, 2015
@ArchangeGabriel ArchangeGabriel changed the title Fedora 21: Bumblebee stopped working with Kernels > 3.17.7 nouveau auto-detection not working? Apr 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants