[00:47] <kuwer> Hello!
[00:47] <kuwer> I want to install a driver for my nvidia geforce 8400 cs video card
[00:48] <kuwer> I am following this tutorial http://ubuntuguide.net/install-latest-nvidia-graphics-drivers-in-ubuntu-linux but it seems different
[00:48] <kuwer> Perhaps it was donne for an older ubuntu server version
[00:48] <kuwer> Could someone help me please?
[00:48] <kuwer> I already downloaded NVIDIA-Linux-x86_64-340.102.run file from nvidia website
[01:08] <sarnold> kuwer: that guide looks eight years old or so. it's probably fair to ignore it entirely.
[01:09] <patdk-l2> I always thought you just install the normal nvidia package and be done with it
[01:09] <patdk-l2> unless you want to do something odd, like use cuba in your applications for like bitcoin
[01:09] <patdk-l2> then your going have hell and be mostly on your own, cause that crap is not fun
[01:09] <kuwer> patdk-l2: well, yes. I need Cuba, OpenCL
[01:09] <sarnold> I don't think anyone does bitcoin mining on gpus anymore
[01:09] <patdk-l2> atleast I gave up on it, and it takes a lot to do that
[01:10] <patdk-l2> sarnold, I know a guy that just setup 12 amd video cards for it this week
[01:10] <kuwer> I am not mining bitcoins but other coinis
[01:10] <sarnold> patdk-l2: yikes
[01:10] <kuwer> yeah, Bytecoin, Ethereum, well there is hundreds
[01:11] <sarnold> this wiki page suggests 'sudo ubuntu-drivers devices' is a good starting point https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia
[01:11] <sarnold> what's funny is it jumps from that right into installing nvidia-nnn   -- maybe nvidia users are forced to install the new driver updates by hand? dunno..
[01:11] <patdk-l2> they have to
[01:11] <sarnold> anyway based on this wiki the first thing I'd try is "apt-get install nvidia-375"
[01:12] <patdk-l2> cause the ones in ubuntu don't have the cuba stuff in them
[01:12] <patdk-l2> get a intel phi :)
[01:12] <kuwer> The correct driver for my video card is NVIDIA-Linux-x86_64-340.102
[01:15] <kuwer> I could use wget http://us.download.nvidia.com/XFree86/Linux-x86_64/340.102/NVIDIA-Linux-x86_64-340.102.run
[01:15] <kuwer> chmod u+x NVIDIA-Linux-x86_64-190.42-pkg2.run
[01:15] <kuwer> ups
[01:16] <kuwer> chmod u+x 340.102/NVIDIA-Linux-x86_64-340.102.run
[01:16] <kuwer> chmod u+x NVIDIA-Linux-x86_64-340.102.run
[01:16] <kuwer> sudo apt-get install linux-headers-$(uname -r) build-essential
[01:16] <kuwer> Is that necessary?
[01:17] <sarnold> probably; you have to compile portions of the drivers on your system
[01:20] <kuwer> How about https://askubuntu.com/questions/66328/how-do-i-install-the-latest-nvidia-drivers-from-the-run-file
[01:28] <kuwer> Used chmod +x driver
[01:28] <kuwer> then sudo ./driver.run
[01:29] <kuwer> And http://imgur.com/a/Vk5iu
[01:29] <sarnold> kuwer: pastebin the logfile?
[01:29] <sarnold> (the pastebinit tool from the pastebinit package can make that easy)
[01:29] <kuwer> sarnold: this is the log file
[01:30] <sarnold> is that the WHOLE log file? or just the last few lines?
[01:30] <kuwer> last few lines
[01:31] <sarnold> good good :) pastebin the whole thing and then we might stand a chance of spotting the error
[01:31] <kuwer> how can I send out from the server this line?
[01:32] <sarnold> apt-get install pastebinit ; pastebinit /var/log/nvidia-installers.log
[01:33] <kuwer> paste.ubuntu.com/24812224
[01:34] <kuwer> Perhaps this driver was not meant to server
[01:34] <sarnold> WARNING: You do not appear to have an NVIDIA GPU supported by the 340.102 NVIDIA Linux graphics driver installed in this system
[01:35] <sarnold> are you sure that your card is supported by this driver/ I hear they are aggressive about dropping support for 'old' hardware
[01:36] <kuwer> This is not the latest driver
[01:36] <kuwer> I went to nvidia and check for my video card model driver
[01:36] <kuwer> And this is the one it pointed me to
[01:38] <kuwer> As http://imgur.com/a/vHo8c
[01:39] <kuwer> Maybe I should Run 'make oldconfig && make prepare' on kernel src to fix it.";
[01:40] <sarnold> I don't think that would help
[01:43] <sarnold> kuwer: the patches on https://gist.github.com/tpruzina look promising
[01:44] <sarnold> kuwer: from your pastebin, the actual errors are starting on lines 3588 and then in 3598
[01:44] <sarnold> all look like hotplug cpu related
[01:44] <sarnold> kuwer: so try making the same changes that the patch that disables the hotplug support ..
[01:45] <kuwer> Well, something I got to say is I am running this Ubuntu Server on a VirtualBox machine just to test.
[01:46] <patdk-l2> dunno how that would work
[01:46] <kuwer> Probably I will be doing the same procedure soon on a ssd driver I am waiting
[01:51] <kuwer> I don´t think there is path for my driver version
[01:52] <sarnold> did you pass the pci through?
[01:52] <kuwer> what do you mean, sorry
[01:53] <sarnold> in order to use devices inside vms you have to use pci passthrough
[01:53] <sarnold> I've never tried it before
[01:54] <kuwer> Oh, not really.
[01:54] <kuwer> Let me check that
[01:58] <kuwer> Not sure where to set PCIE
[01:58] <kuwer> Checking
[02:10] <kuwer> Don´t think my BIOS has BIOS that has the IOMMU
[07:42] <lordievader[m]> Good morning
[09:12] <jamespage> coreycb: checklist via PPA for pike b2 - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2808/+packages
[13:03] <zul> jamespage:  looks like you need zunclient now
[13:03] <jamespage> zul: and some
[13:03] <jamespage> zul: https://launchpad.net/ubuntu/artful/+queue?queue_state=0&queue_text=python
[13:03] <zul> ahaha
[15:19] <hashwagon> Hey nacc, do you have any example of a preseed copy? A file copy from USB/CDROM to the newly installed system if possible. Google isn't being useful to me.
[15:24] <nacc> hashwagon: https://help.ubuntu.com/lts/installation-guide/example-preseed.txt down at the advanced options
[15:25] <nacc> hashwagon: that's how you run any old shell command
[15:26] <nacc> mwhudson: jamespage: is it expected that there is no python-celery-sphinx? I think the new celery is loading a module from it, but there's only python3-celery-sphinx, afaict
[15:26] <nacc> s/celery-sphinx/sphinx-celery/
[15:26] <tomreyn> hashwagon: a more complex example: https://github.com/gc3-uzh-ch/openstack-tools/blob/master/etc/ubuntu-preseed.cfg#L489
[15:27] <nacc> tomreyn: nice, thanks!
[15:27] <tomreyn> and here you got a copy https://lists.ubuntu.com/archives/ubuntu-installer/2007-December/000130.html
[15:28] <tomreyn> oops this one doesn't work, sorry
[15:31] <tomreyn> this one uses 'cp' an is said to work https://help.ubuntu.com/community/InstallCDCustomization/PreseedExamples
[15:38] <jamespage> nacc: hmm that's odd
[15:38] <jamespage> I would expect both versions
[15:38]  * jamespage looks
[15:45] <hashwagon> tomreyn, nacc, thanks guys.
[15:51] <mwhudson> nacc: no idea
[16:08] <nacc> jamespage: yeah, it's surprising to me -- i also only see python3 in debian (afaict)
[16:08] <nacc> mwhudson: np, thanks
[16:09] <jamespage> nacc: apparently that's right but I have no idea why there is no py2
[16:09] <jamespage> maybe the maintainer was being visionary!
[16:10] <nacc> jamespage: yeah, and i think celery won't build without the py2 -- or I have to dig a bit into the internals
[16:27] <nacc> jamespage: i'm looking to see if it's easy to add -- it seems like it's unexpected to only be py2 (and the debian side is just a trival stdeb generated thing (it seems). I wonder if it's just oversight
[16:57] <nacc> jamespage: http://paste.ubuntu.com/24816633/ it builds. I'm verifying the autopkgtest now
[17:03] <nacc> jamespage: tests pass, and it is exactly what fails with celery (import'ing sphinx_celery) :)
[17:52] <hashwagon> Is it normal for a 16.04 server preceed install to have GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" in /etc/default/grub? This prevents me from booting to a tty unless I remove quiet and splash.
[17:56] <hashwagon> sed command to resolve that: http://downloads.linux.hpe.com/SDR/project/minnow/current/Ubuntu_16.04_RAID1_preseed.cfg - odd behavior though..
[18:19] <jerichowasahoax> I created a new apache2 vhost at a specific subdomain, and now my default vhost is being clobbered. What gives?
[18:21] <compdoc> creator typo
[18:21] <jerichowasahoax> The vhost in question: https://paste.pound-python.org/show/aZwN2OyZqjb3ee74YiZQ/
[18:22] <jerichowasahoax> Note there are no wildcards in that vhost, and yet it's answering to ALL requests, not just ones directed at mantis.lavacano.net
[18:22] <jerichowasahoax> I've currently disabled that site configuration.
[18:23] <jerichowasahoax> Google says something about a NameVirtualHost directive but it doesn't appear to actually do anything
[18:25] <sarnold> "If multiple virtual hosts contain the best matching IP address and port, the server selects from these virtual hosts the best match based on the requested hostname. If no matching name-based virtual host is found, then the first listed virtual host that matched the IP address will be used. As a consequence, the first listed virtual host for a given IP address and port combination is the default virtual host for that IP and port combi
[18:25] <sarnold> https://httpd.apache.org/docs/2.4/mod/core.html#virtualhost
[18:25] <sarnold> that's my guess..
[18:26] <jerichowasahoax> sarnold: Assuming 000-default.conf is parsed before 100-mantis.conf, then *:80 should come first and take priority, no?
[18:26] <sarnold> https://httpd.apache.org/docs/2.4/vhosts/ suggests using apachectl -S  to dump the parsed configuration as a useful troubleshooting tip
[18:26] <sarnold> jerichowasahoax: I'd hope so :)
[18:29] <tomreyn> jerichowasahoax: instead of <VirtualHost mantis.lavacano.net:80> you'd usually use <VirtualHost 149.56.132.23:80>
[18:29] <tomreyn> using hostnames there is "not recommended"
[18:29] <tomreyn> https://httpd.apache.org/docs/2.4/mod/core.html#virtualhost
[18:30] <jerichowasahoax> tomreyn: But that IP address points to a couple different FQDNs, as I'm sure you noticed while you were checking my DNS records
[18:30] <tomreyn> jerichowasahoax: if you mean the alias, there's only one
[18:30] <tomreyn> mantis.lavacano.net is an alias for andariel.lavacano.net.
[18:30] <jerichowasahoax> tomreyn: Not the CNAME, the IP itself
[18:31] <jerichowasahoax> tomaw: and andariel.lavacano.net when contacted directly should be serving different content
[18:31] <jerichowasahoax> er
[18:31] <tomreyn> oh your mean PTR records?
[18:31] <jerichowasahoax> tomreyn: see above
[18:31] <tomreyn> that's what ServerName is for
[18:32] <tomreyn> see the example in the docs i pointed to
[18:32] <jerichowasahoax> ServerName isn't working either
[18:32] <tomreyn> VirtualHost uses an ip address, ServerName an FQDN
[18:32] <jerichowasahoax> or now it is
[18:33]  * jerichowasahoax makes a mental note: any virtualhost that isn't <VirtualHost *:80> is practically invalid
[18:34] <tomreyn> if thisis a general statement then i'd disagree
[18:34] <jerichowasahoax> i know the technical explanation is "explicitly defined addresses take priority over wildcards"
[18:34] <jerichowasahoax> which is why "mantis.lavacano.net" was clobbering things
[18:34] <jerichowasahoax> but if I don't overgeneralize I'll just keep screwing that up over and over and over
[18:35] <tomreyn> VirtualHost defines the ip address + port to service this ServerName FQDN on.
[18:35] <jerichowasahoax> tomreyn: apachectl -S was putting "149.56.132.23:80" over "*:80"
[18:35] <sarnold> ahh because it's more specific..
[18:35] <jerichowasahoax> sarnold: yes
[18:35] <sarnold> sigh stupid complicated mess
[18:36] <jerichowasahoax> to be fair, the google results and docs weren't entirely clear on exactly what i was trying to put where
[18:36] <jerichowasahoax> all they really said was "VirtualHost some.domain.com" and "VirtualHost some.domain2.com"
[18:37] <jerichowasahoax> it didn't occur to me that they were assuming those names had different addresses
[19:39] <SuperLag> Do you folks have any recommendations to *automatically* do some kernel cleanup, so /boot doesn't keeep filling up?
[19:39] <SuperLag> it'd be nice to only keep 2-3 kernels...
[19:39] <compdoc> how about: sudo apt autoremove
[19:41] <sarnold> SuperLag: do you have /etc/kernel/postinst.d/apt-auto-removal on your system? it should auto-generate a list of packages to keep in /etc/apt/apt.conf.d/01autoremove-kernels that works with /etc/apt/apt.conf.d/01autoremove
[19:42] <SuperLag> sarnold: I wasn't aware of that. I'll investigate.
[19:42] <SuperLag> thank you, btw!