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