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
GTX670M: NVIDIA(0): Failed to assign any connected display devices to X screen 0 #187
Comments
I am experincing the same problem. I am unable to use Bumblebee on a new Clevo Laptop (mainboard P150EMx - BIOS 1.00.04) with Nvidia Optimus GTX 670M. I am using: Ubuntu 12.04 Some info: optirun glxspheres [ERROR]Cannot access secondary GPU - error: XORG NVIDIA(0): Failed to assign any connected display devices to X screen 0 [ERROR]Aborting because fallback start is disabled. /usr/lib/nvidia-current/bin/nvidia-xconfig --query-gpu-info --nvidia-cfg-path=/usr/lib/nvidia-current Number of GPUs: 1 GPU #0: Number of Display Devices: 0 xrandr -q Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) |
So since my issues is referenced I will ask here - what is needed to get these newer chips to run under TBP? Is it kernel additions, nvidia drivers, what? |
To the Bublebee project authors: do you have any clue why you project is not working on these laptops? Do you need more debug information? Can you please point me on the right direction or give some feedback? |
Some people succeeded in using those chips on newer kernel, such as 3.4 or 3.5. Maybe you can give them a try. |
I don't see why a different kernel would make a difference if it's as the developer said it's a driver issue? |
I'm a developer too. ;) We think that it is a driver issue, however, some people succeeded in using it with a newer kernel, so you can try xorg-edgers ppa and their kernel. So maybe they are some hardware enablement in newer kernel for Kepler cards. |
Ah hah didn't even know my bad :), from what i've seen x-org edgers is xorg related drivers but no newer kernels? |
There is everything for X.org indeed, but also kernel : https://launchpad.net/~xorg-edgers/+archive/ppa/+packages?field.name_filter=linux&field.status_filter=published&field.series_filter=precise |
Well the Ubuntu devs are updating the Kernels in LTS releases now so 12.04 will be getting at least the 3.4 kernel so I will sit and wait on that one as I don't want to break my main Kubuntu install. Are there any TBP packages for Ubuntu 12.10 as I could always install that an a seperate partition to test? Or do the nvidia drivers not work on 12.10'spackages yet? |
Right running 3.5 kernel same thing: [ERROR]Cannot access secondary GPU - error: XORG NVIDIA(0): Failed to assign any connected display devices to X screen 0 [ERROR]Aborting because fallback start is disabled. So it doesn't change anything for me :/ |
liam@liam-laptop-kubuntu:~$ /usr/lib/nvidia-current/bin/nvidia-xconfig --query-gpu-info --nvidia-cfg-path=/usr/lib/nvidia-current GPU #0: Number of Display Devices: 0 liam@liam-laptop-kubuntu:~$ xrandr -q |
I have this error too on a Asus N61J, with a Nvidia GT325M. My kernel is 3.4.4-2-ARCH (Archlinux). DEBUG]Reading file: /etc/bumblebee/bumblebee.conf [ERROR]Cannot access secondary GPU - error: XORG NVIDIA(0): Failed to assign any connected display devices to X screen 0 [DEBUG]Socket closed. |
Updated to kernel 3.5.0-030500rc4-generic #201206241635. Problem remains unchanged. |
I don't think it's a higher Kernel that is needed but the newer xorg, correct me if i am wrong though developers. Judging by Phoronix post http://www.phoronix.com/scan.php?page=news_item&px=MTEzNzM |
No, what you're linking is the replacement for Bumblebee, the results of the PRIME project for native support in X.Org. Everything should be in place for Ubuntu 13.04, but you're not concerned for now. Indeed it should solve the problem, but not before still a long time. But here that could be a driver issue, or a Kepler support one. |
Ah, well as reported a newer kernel doesn't fix the issue for me, is there anything else i can try :( |
Please wait for #201 to be fixed (soon), it may solve your problem. |
That would be super if it did :D |
Im on the same kind of laptop brand Clevo and slightly different setup: Clevo P170EM / 17" FHD Glossy 90% Color Gamut / Core I7 3820QM 2,7-3,7 Ghz / GTX 675M 2 GB GDDR5 / 32GB Crosair Vengeance DDR3 1600 MHz / Intel 520 Series 240GB SSD / 750GB 7200RPM Seagate Second Drive / Intel Centrino Advanced 6230 Ive been struggling with this issue as well, so im hoping something good will come out of this =) grep -Fn '(EE' /var/log/Xorg.8.log
/usr/lib/nvidia-current/bin/nvidia-xconfig --query-gpu-info --nvidia-cfg-path=/usr/lib/nvidia-current
xrandr -q
octodur@mainframe:~$ lspci
octodur@mainframe:~$ optirun glxspheres
octodur@mainframe:~$ uname -a
If there is anything i can help to debug or test just let me know, i'll be glad to do so since i want to see this issue resolved. Cheers and thanks for investigating this issue. |
fractaluser, you need to update to 304.22 drivers |
okey so i installed the ppa xorg-edgers and did the upgrade. Now im on kernel 3.5 with the latest drivers. Though still when i run nvidia-xconfig i still get the 640xsomething display. Though i notice something new: octodur@mainframe:~$ optirun glxspheres [ERROR]Aborting because fallback start is disabled. octodur@mainframe:~$ modprobe nvidia though i cant find that the nvidia_current is blacklisted in /etc/modprobe.d/blacklist.conf |
Do a ls /etc/modprobe.d/nvidia. See any nvidia blacklist files? I found one of these on my own machine. |
I'm sorry, that should be showing asterisks around nvidia in the command above. |
octodur@mainframe:/etc/bumblebee$ sudo ls /etc/modprobe.d/nvidia so =) octodur@mainframe:/etc/modprobe.d$ ls -la |
do i need to rebuild the dkms? someone said that in the new drivers its done automagicaly, but i dont know =/ after the upgrade i do have a lot more proprietary drivers to use where one is not active called: Framebuffer driver for nVidia graphics chipset. Not sure if this will do anything? |
Seriously guys can we keep "how do i?" topics out of bug reports getting annoying receiving lots of messages on it when i just want to track bugs. |
just to inform that i solved this issue now (at least i think so) I went into /etc/bumblebee/bumblebee.conf and changed this line: KernelDriver=nvidia-current now i can run glxspheres and i got 3d support and no nagging about no nvidia-current module not being loaded. |
This bug is fixed in the 304.22 driver in the Ubuntu xorg-edgers repository. |
Hello, I'm having this same issue, four months later, but on nvidia-current 304.64. When I go to delete the conf file in /usr/share/X11/xorg.conf.d/ there is no config file. I've fixed the values in bumblebee.conf, but no dice.. optirun glxgears [ 849.703049] [ERROR]Aborting because fallback start is disabled. |
Hi all,
I'm getting this when I try to run optirun.
The symptoms of this problem are identical to those posted in issue #182 (#182), but I do not see any nvidia-current in /usr/share/X11/xorg.conf.d/. Am I missing something?
_EDIT_
My system is a Sager NP9130 (Clevo P151EM1) with the Geforce 670M graphics card. Also:
The text was updated successfully, but these errors were encountered: