Nouveau does not appear to support Pascal cards right now, so you should use the proprietary NVIDIA driver, available from the Additional Drivers applet.
Once you have NVIDIA's driver installed, you may notice some color banding. The driver does not seem to detect the bpc of the panel properly, so you will need to set this yourself.
- Generate xorg.conf.
sudo nvidia-xconfig
- Add this line under the
Screensection of the config to turn on dithering:
Option "FlatPanelProperties" "Dithering = Enabled"
Plymouth looks like it's running at 640x480. To increase the resolution,
follow this guide, but ignore the step
for installing v86d. You can set the resolution to 1920x1080. Note that
the splash may cut to black after a bit, with the dots being redrawn. No
idea why that happens, and there doesn't appear to be an easy fix.
The keyboard on the laptop is a USB HID keyboard, and sends its own
scancodes for hotkeys instead of going through ACPI, where the asus-wmi module
would have handled it. This will require you to compile your own driver.
Download the source for the current version of your kernel (probably from here), and apply these patches:
- https://github.com/endlessm/linux/commit/0bec892edb6039c833f93de7fb9105bca98066a0
- https://github.com/endlessm/linux/commit/7186733659b7e6567fb3c32a1406721a3b2d2079
- https://github.com/endlessm/linux/commit/de5402bd2775e90c65ef7ff4b8246b8bc06bda0d
Unmarked on the keyboard are the camera key (Fn+V), Splendid Utilities
key (Fn+C, mapped to KEY_PROG2), and Power4Gear Hybrid key (Fn+Space,
mapped to KEY_PROG3, but doesn't actually work on this particular model).
The ROG key is mapped to KEY_PROG1.
After you patch things up, build the module (see https://askubuntu.com/a/515408).
Copy the module to its proper directory in /lib, sudo depmod -a,
and rebuild your initrd (sudo update-initramfs -u).
After you get the hotkey driver installed, you need to add a script for
Fn+F7 to work. Follow the instructions here,
but use video/displayoff DOFF 00000089 00000000 for the event line. (You
may need to use acpi_listen to find the actual event, if the above does
not work.)
Update: appears to be fixed as of driver 375.26.
This is a known issue in the NVIDIA driver. See here for the thread. For now, you'll have to switch between one of the ttys (Ctrl-Alt-F1) and X.Org (Ctrl-Alt-F6) to get the screen to turn back on.
Also a driver bug. Do the same thing as above to reset things.
This is a bug in the ACPI DSDT. We're waiting for the Linux devs to sort out what they want to call the airplane mode button before efforts to get the light to behave properly goes anywhere.
I just got the ASUS GL702VMK and I've mainly had problems getting a small Win10 partition to co-operate, otherwise the issues are mainly as stated earlier.
nouveau.modeset=0, but then resolution was 800x600. Could install at least, without painstakingly guessing mouse-pos step by step via right-clicking to see where the context-menu opens XD.NVIDIA-Linux-x86_64-384.59.run(latest available upon writing this comment), and then the graphics were all good (this machine has the 1060)dmesg(I'm sorry, don't remember, doing all this in haste, as always with things you just want to be done with) - so I removed 4.12.6 viaapt(ukuudoesn't work outside of X-env despite being command-line!!! Fucktardme).sudo startxduring my testing, this left~/.Xauthorityowned byroot.rootcausing lock-timeout. This was a mistake caused by my testing, not by the driver/OS/GPU combo - since the symptom is the same as for problems that can be "original", I thought I'd mention it here in case someone else also does a stupid thing like this while desperately throwing commands around to generate logs XDAs for the rest of things (not gfx related), I will simply wait until support "arrives" with later updates - I'll see them as "free upgrades" down the line XD
I've had a similar situation with an ASUS about seven years ago, took two years until all the HW was supported fully in linux (touchpad, bluetooth, etc.). I still opt for ASUS because I've never had one fail on me hardware and build-wise.
@YontiLevin - I also got this machine because of it's performance: that should be all good, while it still maintains a pretty slim form factor. Though for deep-learning you should probably consider a stationary machine park. For this machine, be warned: it looks insanely "sporty"! I had unfortunately not looked this up at all, I just bought it based on specs, it looks like some '90s neon Nike shoes or something XD