nVidia driver half-working, LUbuntu 17.10

[zeroth404]

I installed a 4.12 kernel package. I tried the autoinstall of nvidia 384, still getting the same darn problem.

[zeroth404]

I have tried kernel 4.10, 4.11, and 4.12 packages from the mainline ubuntu repo. They all boot, but the nvidia 384 driver doesn't work with any of them.

I also tried nvidia 340 with kernel 4.10 just to see what would happen. lsmod still shows the driver loaded but it still isn't functioning.

[dorian7]

Are you using the ACPI workaround? You need to have your boot parameters include: acpi_osi=! acpi_osi="Windows 2009"
Only then will it boot properly with the drivers installed.

EDIT : If you're on the 4.10 kernel, you can drop the ACPI parameters. However, I needed to then add pcie_aspm=force to allow the system to conserve power usage and generate less heat. More of an issue on laptops of course.

[zeroth404]

I was just about to install a previous version of LUbuntu when I decided to try your last suggestion, dorian7. It was when I went in to grub to add the boot parameters you recommended when I noticed "nomodeset" was listed there. This was something I had to add in order for the LiveCD to not lock up during boot-up, but I didn't realize it saved the darn thing to the system during installation. From what I gather, nomodeset is only supposed to prevent the drivers from loading *before* X starts, but in this case it seems to have prevented the drivers from loading at all.

I removed nomodeset from my boot parameters, and (after `ubuntu-drivers autoinstall`) now I can run glx-gears. NVidia driver 384.111, kernel 4.13.0-250-generic, LUbuntu 17.10.

Thank you all for your support.

[Bashing-om]

zeroth404; Yuk, and great !

I called myself looking for that eventuality of "nomodeset" - do not know how I missed it .

Wonderful that you are up and running ..

Once we have dorian7's closing remarks:

Please mark this thread solved;
aides others seeking the solution,
helps keep the forum clean and
precludes others miss-directing efforts to aid.
https://wiki.ubuntu.com/UnansweredPo.../SolvedThreads

good things can happen

[dorian7]

Sorry for holding up the close
Glad it got sorted! Sometimes it ends up being something so simple lol
Bash on!

[noabody2]

It was when I went in to grub to add the boot parameters you recommended when I noticed "nomodeset" was listed there.

Same problem here. Found "nouveau.runpm=0" let me boot the live CD and caused less trouble before I caught, and removed it, from the installed OS kernel option.