On 2015-11-10 23:29 +0100, David Christensen wrote: > On 11/07/2015 12:32 AM, Sven Joachim wrote: >> Fair enough, I won't bother you again then. My apologies for >> mistakenly thinking you would appreciate help. > > First, I apologize for my earlier complaint about shipping product > with known bugs. Companies that refuse to disclose relevant technical > information needed for open-source software development inflict the > problem upon all of us.
Apologies accepted. > And, Dell Latitude E6520 laptop computers > like mine have both Intel HD Graphics and an Nvidia graphics card, > which is a corner case: > > https://en.wikipedia.org/wiki/Nvidia_Optimus Thanks, that's important to know. I'm not experienced with Optimus, since I don't have any such hardware myself. > I *do* appreciate help. But, I do not have the knowledge, skills, > time, or interest to "figure out why [the nouveau kernel module] is > not loaded earlier by udev". If you would like to work together on > this, I can run commands for you, post files, etc., so you can debug > it remotely. Tell me what you need. My theory was that the nouveau kernel module had been blacklisted, since udev runs modprobe with the "-b" parameter, while the X server does not. But maybe I'm wrong. Could you please start your system without X? On a standard Jessie installation with systemd as init and gmd3 as display-manager, you can add "systemd.unit=multi-user.target" to the kernel command line to achieve that. Log in at the console and see if the nouveau kernel module is loaded ("lsmod | grep ^nouveau"). If not, 1. Run "modprobe -b nouveau" and check again. If that does not load the nouveau module, 2. Run "modprobe nouveau" and check again. If the nouveau kernel module has been loaded in steps 1 or 2, you can try to run X (start your display manager, or use startx). Does it work then? Cheers, Sven
