waiting for /dev to be fully populated nvidia discrete/optimus
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
waiting for /dev to be fully populated nvidia discrete/optimus
Hi all,
I am running into a weird issue. It's usually intermittent and fixes itself after a few boot attempts, but right now it is pretty consistent. I have nvidia quadro video card with a Lenovo W520 - it's one of those cards with the NVidia Optimus feature.
Every time that I set the bios to use discrete graphics, my boot hangs on "waiting for /dev to be fully populated". When I switch to the integrated intel card, everything works fine. Is there a way to debug this to narrow it down and figure out what's causing the issue? The boot won't finish, it just sits there at the message and I have to restart and switch to the onboard intel car to be able to boot into linux. I have to reboot between 5-10 times for something to finally kick in with the discrete card and then the boot finishes, but it's very frustrating.
This issue is frustrating me so much, that I am considering switching back to windows to use my nvidia card to its full extent.
Linux Mint Debian edition 3.2 kernel.
Last edited by alagenchev; 06-02-2012 at 04:07 PM.
I was aware of the bumblebee project, but wasn't planning on using that yet. Are you suggesting that the current nvidia driver I am using is faulty and I should switch to bumblebee, hoping to fix my problem in doing so?
Nvidia is working on this with the latest beta driver from Nvidia (302.7)
Save for Intel would be to compile kernel module like this to keep the standard GL libs for your internal intel card
Code:
NVIDIA-Linux-x86_64-302.07.run --no-opengl-files
If installed; See: usr/share/doc/NVIDIA_GLX-1.0/html/optimus.html and;
Quote:
Why does the VBIOS fail to load on my Optimus system?
On some notebooks with Optimus graphics, the NVIDIA driver may not be able to retrieve the Video BIOS due to interactions between the System BIOS and the Linux kernel's ACPI subsystem. On affected notebooks, applications that require the GPU will fail, and messages like the following may appear in the system log:
NVRM: failed to copy vbios to system memory.
NVRM: RmInitAdapter failed! (0x30:0xffffffff:858)
NVRM: rm_init_adapter(0) failed
Such problems are typically beyond the control of the NVIDIA driver, which relies on proper cooperation of ACPI and the System BIOS to retrieve important information about the GPU, including the Video BIOS.
Nvidia is working on this with the latest beta driver from Nvidia (302.7)
Save for Intel would be to compile kernel module like this to keep the standard GL libs for your internal intel card
Code:
NVIDIA-Linux-x86_64-302.07.run --no-opengl-files
If installed; See: usr/share/doc/NVIDIA_GLX-1.0/html/optimus.html and;
Hope this helps
Do you have any idea what's the advantage/disadvantage of going with 302.7 vs bumblebee? From the bumblebee wiki here: https://wiki.debian.org/Bumblebee it looks like bumblebee is using the nvidia proprietary modules and drivers, which is what I have installed now, so I am not sure if that would solve the problem with the hanging. If I understand things correctly, bumblebee just provides the switching between the cards, which I am doing manually myself now via the switch in the bios. I don't understand the reason behind the limitation on Linux. It's obvious that NVidia is providing active support to their drivers, I wonder why they can't just make it work on linux like the already did on windows? There is probably a good reason for it.
Last edited by alagenchev; 06-09-2012 at 06:40 PM.
I can't believe that I am posting this, but a year later I found a solution to this annoying problem. I am extremely surprised that there isn't more information online by now since I firmly believe this is a very common issue. We just bought quite a few new W520s at work and they all have this problem. The solution is to disable virtualization from the BIOS. Once virtualization is disabled the computer boots without issues. Virtualbox and VMware will be slow if you need them, but oh well. Here is some more info about the problem: http://forums.lenovo.com/t5/Linux-Di...ia/td-p/577789
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.