[11:34] <lotuspsychje> blogten: wich chipset is that
[11:34] <blogten> the nvidia you mean?  or the motherboard?
[11:34] <lotuspsychje> yea your graphics
[11:34] <blogten> nvidia gtx 660
[11:34] <blogten> (it's a server *other* than the one we talked about a while ago)
[11:34] <lotuspsychje> blogten: check: sudo lshw -C video please
[11:35] <blogten> indeed, a GTX 660
[11:35] <lotuspsychje> blogten: what does driver say at bottom driver=
[11:35] <blogten> LOL nothing
[11:36] <lotuspsychje> blogten: does card say 'unclaimed' ontop?
[11:36] <blogten> ah sorry, not in a line of its own
[11:36] <blogten> grep shows "driver=nvidia"
[11:36] <lotuspsychje> blogten: ok, check nvidia-smi
[11:36] <blogten> I had been looking at that a bit ago, what would you like to know?
[11:37] <lotuspsychje> blogten: wich driver version is active
[11:37] <blogten> 430.40
[11:37] <lotuspsychje> blogten: does ubuntu-drivers list show other versions?
[11:38] <blogten> ubuntu-drivers?... is that a cli program?... there's no which ubuntu-drivers
[11:38] <lotuspsychje> blogten: ah never tested on server, its a built in command normally: ubuntu-drivers list
[11:39] <blogten> apt suggests installing ubuntu-drivers-common
[11:39] <lotuspsychje> hmm
[11:40] <blogten> it's installing
[11:40] <lotuspsychje> blogten: apt-cache policy nvidia-driver-390
[11:40] <blogten> (fyi the only access I have to the box right now is via SSH)
[11:40] <lotuspsychje> kk
[11:40] <blogten> ok, ubuntu-drivers list is thinking
[11:41] <lotuspsychje> hehe
[11:41] <blogten> 6 driver suggestions: 430, 415, 410, 390, 340, and 304
[11:41] <blogten> interesting
[11:41] <lotuspsychje> lets try something less high for server
[11:42] <lotuspsychje> 390 or 410
[11:42] <blogten> 16.04 used to work with nvidia-driver-418, which is not listed here, and 418 right now points to 430...
[11:42] <blogten> sure, hang on
[11:43] <blogten> ... purging 430...
[11:44] <blogten> and autoremoved the 430 remnants too
[11:44] <lotuspsychje> cool
[11:45] <blogten> do you want a reboot before installing a lower driver?
[11:45] <lotuspsychje> blogten: no you can install the new one then reboot after
[11:45] <blogten> ok, let's see
[11:45] <blogten> how about 410...
[11:45] <lotuspsychje> sure
[11:46] <blogten> aptitude is meditating on the subject now...
[11:47] <lotuspsychje> lol
[11:47] <lotuspsychje> good boy apt
[11:47] <blogten> blah blah compiling driver blah blah update-initramfs...
[11:48] <blogten> ok, done
[11:48] <blogten> reboot?
[11:48] <lotuspsychje> yes
[11:48] <blogten> ok, I'll go to the other room and see what the console does
[11:56] <blogten> back.  after the machine BIOS boots, the blinking cursor advances one or two lines very quickly from the top, then the screen goes blank, and stays blank.  nothing happens.  I can see the box is responsive because e.g. num lock changes as I swap TTYs, but nothing shows on the monitor.  the box never had the desktop components installed, and it's no
[11:56] <blogten> t mean to.
[11:56] <lotus|i5> hmm
[11:56] <lotus|i5> blogten: try another reboot
[11:56] <lotus|i5> if that doesnt solve, try the 390
[11:58] <blogten> soft, or hard reboot?
[11:58] <blogten> hard as in -h, rather than -r
[11:58] <lotus|i5> doesnt matter i think
[11:58] <blogten> down the box goes again... brb
[11:59] <lotuspsychje> ill be bbl for a while
[12:02] <blogten> back.  same exact behavior.  also, I (think I) set grub to show the menu before the kernel boots, and not even that shows up in the monitor.  nothing at all.  before that, the BIOS shows, and I can see the GTX as well as the RAID card announcing themselves and all that...
[12:03] <lotuspsychje> ok try 390
[12:04] <blogten> in dmesg there's a note about the driver asking for multiple BARs, but that happens way after the kernel boots (and obviously after grub should have shown up but didn't)
[12:05] <blogten> also, nvidia-smi says whether the adapter is on or off is N/A... that is really odd
[12:05] <lotuspsychje> yeah means something went wrong with driver load
[12:06] <blogten> another bit I looked into is the kernel module bbswitch... although it was installed in the kernel, the relevant files didn't show up in /proc/acpi...
[12:06] <blogten> apt is nixing the 410 driver...
[12:06] <blogten> now aptitude is meditating about the 390 driver...
[12:07] <lotuspsychje> lol make sure apt doesnt spit out errors while installing
[12:08] <lotuspsychje> some cases dkms conflicts
[12:09] <blogten> there's "Not creating home directory `/nonexistent'.", but I think that's because right before it adds the user nvidia-persistenced
[12:10] <blogten> there were some errors in the log files before, but that's because the very very very old 304 driver which I uninstalled a long time ago left broken symlinks, I deleted those
[12:11] <lotuspsychje> kk reboot after install
[12:11] <blogten> I do not see errors from the install
[12:11] <lotuspsychje> allrighty
[12:12] <lotuspsychje> bbl
[12:14] <blogten> same thing
[12:17] <blogten> I see something about a request the NVIDIA driver makes, i.e. this:
[12:17] <blogten> requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
[12:17] <blogten> right after that, there's a note that the NVIDIA requested multiple BARs
[12:18] <blogten> and still, even grub didn't show up
[12:20] <blogten> why would that not work, even without the nvidia drivers installed?
[12:20] <blogten> that is, even without the nvidia drivers, I still get a blank screen
[12:45] <blogten> now that's interesting, the vesafb is "mapped to 0x        (ptrval)" as per the log, shouldn't that be 0xSOMEDEADBEEF?
[12:52] <blogten> ok, fixed some of the breakage
[12:53] <blogten> went to BIOS, disabled decoding PCI above 4gb => now I have video
[12:53] <blogten> two problems remain: 1) slow because the console is in graphical mode rather than text (so slow that makes boot slower!), 2) needs newer drivers....
[13:18] <blogten> newer drivers in, now the text mode...
[19:42] <mmercer> does apt-get not support http authenticaiton ?
[19:44] <tomreyn> apt_auth.conf(5)
[20:10] <mmercer> tomreyn: tyvm.  i was hoping it used netrc format, i just wasnt sure where to look
[20:10] <mmercer> issue fixed, woot woot