libera/#devuan/ Tuesday, 2018-08-28

xrogaanthis is why we can't have nice things: https://github.com/mate-desktop/mate-terminal/blob/078d0b1fdac2e50dfa4411b612e78a4be134e47d/src/terminal-screen.c#L143100:49
xrogaanbeen trying to get colors properly setup, but mate is yet again being silly.00:49
xrogaanhttps://github.com/mate-desktop/mate-terminal/issues/209 < yeah, I believe it is time for me to switch DE01:19
xrogaanwhich terminal do you guys use?02:03
xrogaanurxvt is a bit too raw for me.02:03
fsmithredxfce4-terminal in xfce, lxterminal with openbox, and xterm is used by refractainstaller02:05
gnarfacewhat's wrong with urxvt?02:07
phoggurxvt is the best. It has every feature you could want and a rather good amount of compatibility02:08
xrogaanyeah, but xterm somehow doesn't set TERM to xterm-256color02:10
xrogaaneven though it should be compatible by default02:10
fsmithredwhen do you use TERM?02:11
xrogaanI don't.02:11
fsmithredwhen does anyone use it?02:11
xrogaanxterm use term02:11
fsmithredmine is set to xterm, but xterm never comes up unless I call it02:11
xrogaanand the bashrc thing use $TERM02:11
xrogaantput colors use TERM02:12
xrogaanwith just xterm, tput will output 8.02:12
MinceRurxvt is slow as molasses02:12
phoggMinceR: compared to what?02:12
MinceRcompared to just about everything else02:12
MinceRvery visible on a raspberry pi 102:12
MinceRi use terminate, but that isn't perfect either02:12
xrogaanSo I can't detect if the current term is stupid or does support 256 colors. Which means I can't properly configure my bash prompt.02:13
MinceRwell, everything i had on raspbian7, anyway02:13
xrogaanI installed guake from source, because for some reason its TERM env was overridden by something.02:14
xrogaanIt's quite frustrating.02:14
MinceRyeah, i use guake for dropdown terminal where xfce4-terminal doesn't support that mode yet02:16
MinceRbut i only use it to launch stuff, pretty much02:16
MinceRlike a smarter run dialog02:16
xrogaanwhat does echo $TERM in xfce4-terminal returns?02:20
MinceRxterm-256color02:24
fsmithredmy xfce4-terminal says xterm02:25
xrogaanhuh02:33
xrogaanapparently, xfce4-terminal shouldn't set the $TERM variable and thus use defaults?02:35
xrogaanbut it's weird that both of you get different results.02:36
fsmithredxfce4-term and lxterm give me full palette of colors02:36
fsmithredoh, that's for bg and fg02:37
xrogaanreally? Does `tput colors' returns 256?02:37
fsmithredare you messing with the colors in bashrc?02:37
xrogaanno02:37
fsmithred802:37
xrogaanI'm trying to not override $TERM02:38
fsmithred8 in xfce and lx02:38
MinceRi checked it on slackware though02:38
MinceRthat's where i have xfce4-terminal atm02:38
xrogaanIf I understand the source correctly, xfce4 inherit the environment variables.02:40
xrogaanI had the same issue with guake, it was setting $TERM to xterm-256color yet the final value get set to xterm.02:41
xrogaanprobably something rotten in MATE02:43
xrogaanor maybe not02:43
xrogaanthe gnome-terminal works just fine. And guake from pip works just fine too.02:44
xrogaanfsmithred: htop makes use of xterm-256color03:49
xrogaanactually, any cli app that make use of color will benefit from it.03:49
gnarfaceit makes emacs super nice :)03:54
fsmithredlooks like I have 256 colors.03:56
fsmithred256-colors.sh says so03:56
xrogaanyes, everybody does.04:12
xrogaanunless you connect through putty or another weird use case that doesn't give you all the colors.04:13
DocScrutinizer05it's quite funny how $TERM comes up as a topic now that I asked09:07
DocScrutinizer05[2018-08-26 15:36:41] <DocScrutinizer05> damn, did "recent" ssh client updates (+ related libs) cghange the environment and/or behavior of *server* where I log in to with this ssh client? E.G. I can't start mc anymore, I get:09:07
DocScrutinizer05[2018-08-26 15:36:45] <DocScrutinizer05> IroN900:~# mc09:07
DocScrutinizer05[2018-08-26 15:36:45] <DocScrutinizer05> Error opening terminal: xterm-256color.09:07
DocScrutinizer05oops sorry, I hit "paste" instead of "edit"09:07
DocScrutinizer05AIUI there's a linux world wide move from TERM=xterm to TERM=xterm-256color, across all distros, maybe started by https://bugzilla.gnome.org/show_bug.cgi?id=740641 - alas some "old" systems don't like that move so you get hiccups when you log in to those from a system whose ssh exports a TERM=xterm-256color, see above old Iron900 maemo system09:12
DocScrutinizer05I wonder what's the canonical way to deal with this now. "Fix" my old systems that need TERM=xterm, with a [ "xterm-256color" == "$TERM" ] && TERM=xterm, somewhere in .profile or .bashrc  or ssh logon or whatever (and what/where, then), or revert&fix back to plain TERM=xterm on all "new" systems, or only with ssh client of those "new" systems09:19
acdimalevDocScrutinizer51: For dealing with large-scale infrastructure that I don't manage, I've found setting up an SSH alias that sets `TERM` to be very effective.  For anything that I do manage, I would be tempted to either backport a package, or look ahead at where a future update will dump the terminfo file and just drop a copy there.09:46
DocScrutinizer05"future update" sounds a tad funny for this particular case: maemo509:47
DocScrutinizer05thanks, it sounds very reasonable approach09:48
DocScrutinizer05I gather I could deal with this in .ssh/vonfig too?09:50
DocScrutinizer05config even09:50
acdimalevNo problem.  I've had to deal with this problem ever since I adopted a terminal emulator that doesn't set `TERM` to either `xterm` or `xterm-256color`.09:50
DocScrutinizer05I mean, _all_ my ssh logins have a record in my ssh config09:51
acdimalevNot that I've been able to tell.  The SSH config file controls which environment variables get forwarded, but I haven't seen any options for setting environment variables.09:51
acdimalevI wish it did, and if anybody can point out an oversight on my behalf, I'd be delighted.09:52
DocScrutinizer05hmmm, I guess when I do NOT forward xterm-256color then the target system falls back to sane?09:52
acdimalevJust run `unset TERM` on a local terminal and try a few things.09:52
acdimalevI don't think the sane defaults are going to meet your expectations.09:53
DocScrutinizer05damn, I should write a ssh alias that copies my complete "environment" like ~/.profile ~/.aliases ~/bin etc pp, on *each* login ;-)09:53
DocScrutinizer05;-)09:54
acdimalevNot that I have time to look into it at the moment, but that does make me wonder how difficult it would be to add support for such an option to Open SSH.09:55
acdimalevIt would be incredibly useful to be able to specify environment variables for a specific SSH host.09:56
DocScrutinizer05"such an option" to set $ENV?09:56
DocScrutinizer05or to run a script during login?09:57
acdimalev`SetEnv TERM xterm` in `~/.ssh/config` is what I'm thinking.09:57
DocScrutinizer05the latter should cover the former, sourcing instead of exec'ing the script09:58
acdimalevIt would be useful for way more than just setting up a term.09:58
acdimalevIn the days where my server logins were single digit and automated server builds were not a thing, it made sense to try and adjust everything server-side.09:59
DocScrutinizer05script for sure. I know you can define binaries to execute regardless of commandline, on ssh *server* side in the pubkey record10:00
DocScrutinizer05a pity that despite it sounds very similar, it doesn't apply at all for this usecase10:00
acdimalevIt sounds like you're dealing with a single device?  In that case, definitely do not trouble yourself with an effort besides correcting that single instance.10:02
DocScrutinizer05hmmmmm, you could get a wrapper script around the `ssh` binary, to parse your ~/.ssh/config10:02
DocScrutinizer05acdimalev: ack, but I *love* solving problems for good. since I hate running into them a second time ;-)10:03
DocScrutinizer05a wrapper script should be versatle and simple enough to even be fun to implement10:06
DocScrutinizer05what sucks a bit is duplicating all the parameter&option parsing syntax/semantics of ssh cmdline10:07
acdimalevWell... what all would you want to be able to modify about the runtime environment based on the contents of the SSH config?10:10
acdimalevI have a use-case for setting environment variables, but I'm not too sure I have a solid use-case for anything else.10:11
DocScrutinizer05(parse) actually not that bad, only [-F configfile] needs special treatment, discard all other -options and catch the first non-option argument which is user@]host[:port]  or [user@]hostname10:13
acdimalevIf I really wanted a "do anything" setup, it would involve executing a binary with the the original SSH command, but also with an additional command-line switch to exclude running the binary wrapper (to avoid recursive binary wrapper execution).10:16
DocScrutinizer05then parse ${configfile:-~/.ssh/config} for the $"[user@]hostname" you derived from step#1, and in that record find the new command "#!source <filename>"10:16
acdimalevBut I really can't think of a use-case that would require such a binary wrapper to do anything other than set environment variables to fixed values.10:17
DocScrutinizer05then `source <filename> && ssh $@`10:17
DocScrutinizer05I can't think of a usecase where I would bother to restrict the capabilities of such a wrapper10:18
acdimalevI don't mean regarding restriction... it just seems excessive for what would otherwise be an option to set environment variables to fixed values.10:19
DocScrutinizer05after all it's pretty hard to come up with a shorter generic solution10:19
DocScrutinizer05for such "option to set environment variables to fixed values" you also need a wrapper, or patch the binary10:20
DocScrutinizer05for your convenience, I will add "#!setenv  ENV=value" as valid new command, concurrently to "#!source <filename>" - will only cost an additional 4 LOC in that wrapper script10:22
DocScrutinizer05:-)10:22
DocScrutinizer05while the "#!source <filename>" prolly only costs 3 LOC10:23
DocScrutinizer05the rest is common to both approaches10:23
acdimalevI would think a binary patch is likely to be upstreamed.10:23
DocScrutinizer05I'm sure a wrapper script isn't10:23
DocScrutinizer05but I'm also sure I don't feel like messing with ssh sourcecode10:24
DocScrutinizer05again and again for each update, until my patch actually gets upstreamed maybe, eventually10:24
DocScrutinizer05;-)10:25
acdimalevI have good news.10:31
acdimalevYou won't have to.10:31
acdimalevhttps://anongit.mindrot.org/openssh.git/tree/ssh_config.5#n143510:31
acdimalevWe're now just waiting for a version of Open SSH to release that has this functionality.10:32
DocScrutinizer05umm what am I looking at? :-o10:33
acdimalevDocumentation for a `SetEnv` option in `ssh_config` for the master branch of upstream Open SSH.10:34
DocScrutinizer05documentation? ooooh10:35
DocScrutinizer05anyway, seems you're happy10:35
DocScrutinizer05while I know how to tackle my problem10:35
acdimalevSounds about right.10:37
acdimalevSoftware fresh off the shelf... Open SSH made a release five days ago that has this new functionality.10:37
DocScrutinizer05ooh10:38
DocScrutinizer05you got a version string or whatever, to look for?10:39
acdimalev7.8p110:40
DocScrutinizer05ta!10:40
DocScrutinizer05OpenSSH_7.6p1, OpenSSL 1.1.0h-fips  27 Mar 2018   here, hmmmm10:41
acdimalevAs I said, five days ago.  :)10:41
acdimalevI'm sure it'll take a minute for even the rolling-release distros to push this out.10:42
acdimalevCan always build from source if super-anxious.10:42
DocScrutinizer05that's what I wonder10:43
DocScrutinizer05for my distro, maybe there's sth in factory10:43
DocScrutinizer05https://build.opensuse.org/package/show/home%3Avicidial/openssh  7.7p110:47
acdimalevOnly one release behind.  :)10:53
Centurion_Danthe other way to do it is to include the command in the stanza in ~/.ssh/authorized_keys on the host  that way it's run post login anyway.  In fact you should be able to define this as an action in the ssh_dconfig on the server your connecting to for a universal setting specific to that server.11:28
Centurion_Dan*sshd_config11:29
Centurion_DanDocScrutinizer05: ^^11:29
DocScrutinizer05Centurion_Dan: yes, that's what I incorrectly(?) referred to as "define binaries to execute regardless of commandline, on ssh *server* side in the pubkey record"11:33
lead_dipperwhat would need to happen to make debsecan work properly in devuan? it uses debian's security tracker, would devuan need something similar? Sorry if this has been asked before, I couldn't find any mentions on the forum or wiki.11:33
DocScrutinizer05Centurion_Dan: alas this isn't client specific unless you got a one unique key pair per client11:33
Centurion_Danlead_dipper: we have somebody working on this already...11:35
lead_dippernice11:35
acdimalevCenturion_Dan: I assume this is where any security tracking will surface?:  https://devuan.org/os/security/11:45
Centurion_DanDocScrutinizer05: it is if you only set it up on the pubkey entry on the servers where you want it.  I have several keys in use so it wouldn't be such an issue.  For a start I have a different key for devuan servers then I use for my clients.  And when you combine that with using ~/.ssh/config to direct which keys to use for which host - it's all good.11:47
Moanehello/bonjour/hola12:45
DocScrutinizer05aloha13:49
leventehey, I was wondering if I am able to install the proprietary nvidia drivers from the repos19:17
gnarfaceyep, that's a thing19:21
gnarface(they're in non-free)19:21
leventehow can I enable that?19:22
gnarfaceyou should also enable contrib at the same time19:23
golinuxIn sources.list19:23
gnarfaceit should be as easy as adding " contrib non-free" to the end of every line in sources.list19:23
gnarfacepastebin your sources.list if you want it proofread19:23
gnarface(and don't forget you'll need to run `apt-get update` for changes to take effect)19:24
furrywolfisn't sources.list management something that should have a pointy-clicky frontend by now?19:26
leventehttps://pastebin.com/cN0MHuRW19:27
leventeDoes this look good19:27
gnarfacei think so19:29
leventethanks19:29
gnarfaceif you need NEW nvidia drivers, you'll need them from backports19:30
gnarfaceotherwise this should be fine19:30
leventewhat are the main nvidia driver packages?19:30
leventeand do I have to manually disable nouveau19:30
gnarfacenvidia-driver19:30
gnarfacenvidia-driver-bin19:30
gnarfacelibgl1-nvidia-glx19:30
gnarfacenvidia-settings19:30
gnarfaceyea, you probably have to manually disable nouveau.19:31
leventeah okay19:31
leventethanks19:31
leventeso these packages should suffice?19:31
gnarfaceyea, probably.  it should get all the 64-bit stuff you need anyway.  and just blacklist nouveau in /etc/modules.d if it isn't already when they're installed.19:31
gnarfaceif you also need 32-bit stuff (like for wine and steam support) you'll need to also enable multi-arch19:32
leventedoesn't wine have a 64 bit version19:32
leventeI'm back, I rebooted19:36
leventethe resolution is wrong19:36
leventeI'm not sure where the logs are for this19:36
gnarfaceit would probably be either /var/log/Xorg.0.log or ~/.local/share/xorg/Xorg.0.log19:38
gnarfaceand yes, wine has a 64-bit version but a lot of windows software still requires 32-bit support even when it's 64-bit (i'll refrain from soapboxing about the stupidity and injustice of that, just accept that it's the case)19:39
leventeuhh nouveau loaded for some reason but the resolution is bad, it was fine before the reboot19:39
gnarfaceyou sure it actually loaded?19:40
gnarfacedid you forget to blacklist nouveau?19:40
levente(II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so19:40
leventewhere do I whitelist it again?19:40
gnarfaceblacklist19:41
leventeyeah, that sorry19:41
gnarfacedo me a favor and run this command19:41
gnarface grep -rni 'blacklist.*nouveau' /etc/modprobe.d19:41
gnarfacesee any output?19:41
leventeno, I didn't whitelist it just yet, I just disabled it with the grub config19:41
gnarface*blacklist19:41
gnarfacethere is an important difference in terminology here19:42
gnarfacepick any conf file in /etc/modprobe.d or add your own then add this line to it:19:42
gnarfaceblacklist nouveau19:42
gnarface(then reboot again)19:42
leventeI'm getting spammed with a few 'possible missing firmware' warnings, is that fine19:43
leventewhen updating initramfs19:43
gnarfaceit might be fine it might not19:43
gnarfacedepends on which firmware it's  missing19:44
leventeshould I pastebin it19:44
gnarfacethe nvidia drivers should have their own firmware.  it's about some other hardware, isn't it?19:44
leventesomething about rtl_nic19:44
gnarfacego ahead and pastebin it i'll see if i recognize it19:44
gnarfaceyea you probably are missing the realtek firmware for gigabit ethernet links19:44
gnarfacethat's a separate issue, stay on target19:45
leventeah okay19:45
leventerebooting again19:45
leventeIt's still wrong19:47
leventeI've seen something about nvidia_drm not being able to load when booting19:47
gnarfacewell that's not unexpected, but first we have to make sure nouveau didn't load first19:47
leventeokay19:47
gnarfacethe resolution could be wrong for additional reasons.  sometimes it still needs a manual configuration depending on your display type19:48
leventenouveau was able to detect it, I don't see why the proprietary driver won't19:49
gnarfacesometimes blacklisting nouveau isn't enough and some other wrong driver just loads instead19:49
gnarfacebut you shouldn't be super surprised that nouveau is better at playing nice with xorg19:49
gnarfaceit's got worse hardware support but it's not made by people who support linux under duress19:50
gnarfacecan you pastebin the Xorg log?19:50
leventenvidia drivers suck, I don't know why they don't care about linx users19:50
leventeyes19:50
gnarfacethe missing firmware for that ethernet device is probably in "firmware-realtek" (also in non-free)19:51
gnarfacebut it may also be in the package firmware-linux-free which is in main19:51
leventehttp://0x0.st/stm8.log19:52
leventethe log file19:52
gnarfaceugh19:52
gnarfacenope19:52
gnarfacenot clickin on that19:52
gnarfacecould you use paste.debian.net please?19:52
leventeoh, sorry19:52
leventeyes19:53
gnarfacethat's not channel policy that's just my policy19:53
leventebut it's hard to paste from CLI and I can do that to 0x0.st with curl19:53
gnarfacethere's a cli program called pastebinit19:53
gnarfaceit's in the repo19:53
leventehttp://paste.debian.net/1039688/19:54
leventegot it, thanks19:54
gnarfacehmmm19:54
gnarfacestill loading nouveau19:54
leventeI have blacklisted it19:54
gnarfacecheck this output:  lsmod |grep nouveau19:55
leventeno output19:55
gnarfacedo you have a log file in ~/.local/share/xorg?19:55
leventeroot or my actual user19:56
gnarfaceyour actual user19:56
leventenope, I don't even have a xorg directory19:56
gnarfaceyou're starting Xorg as your actual user, right?19:56
gnarfaceor are you using a graphical login manager?19:56
leventeI don't know how slim starts it19:56
leventeyes19:56
gnarfacehmm. ok19:56
gnarfaceso the log is /var/log/Xorg.0.log and you can tell by the datestamps that it's being replaced every time you reboot, right?19:57
leventeshould I delete it and reboot?19:57
gnarfaceno, but there's some cases where it might be changed to Xorg.1.log or something like that if you're running more than one xorg instance19:57
leventeI only have Xorg.1.log19:57
leventeno, I mean 019:57
leventeXorg.0.log19:58
gnarfacehmm. ok19:58
gnarfacein your /etc/default/grub file, is it setting a console resolution at boot?19:59
leventelet me paste it20:00
leventehttp://paste.debian.net/1039691/20:00
gnarfaceok20:01
gnarfaceonly one thing is different there from mine20:01
gnarfaceline #1020:01
gnarfacechange yours to this: GRUB_CMDLINE_LINUX="nomodeset"20:01
leventeokay20:01
gnarfaceactually20:01
gnarfacei also removed quiet from line 920:02
gnarfacebut that's not necessary20:02
leventewhat does quiet do?20:02
gnarfaceit just suppresses a lot of the console output at startup20:02
leventeby the way, what init system does devuan use by default20:02
gnarfacethe old one that debian was using before systemd (wheezy and earlier)20:03
leventesystemvinit?20:03
gnarfaceyes, but the other ones are all still present and available as options20:03
leventeOkay, I updated grub20:03
leventeshould I reboot now20:04
gnarfaceyea, just to try it.  but we may still need to make an xorg.conf for you20:04
leventeI am back with a bad driver again20:07
gnarfacelevente: i just remembered something.  you also have to add that user to the "video" group20:07
leventeah20:07
leventedone20:08
gnarfaceyou'll have to reboot, or at least restart slim]20:08
leventerebooting is easier and faster20:08
leventebrb then20:08
leventeyup, still bad20:10
gnarfacehmm. drat20:10
leventeyeah20:10
gnarfaceok, let's see the new xorg.log20:10
gnarfacesomething should have changed at least20:10
gnarface*Xorg.0.log20:10
leventehttp://paste.debian.net/1039694/20:11
gnarfacesomething's still not right20:12
gnarfacei'm missing something still20:12
gnarfacehmmmm20:12
gnarfaceok gimme 10 minutes i have to go AFK sorry20:12
leventeye np, thanks for your help so far20:13
gnarfacewe gotta figure out why this is still loading nouveau20:13
leventeI got used to gentoo, So I could rebuild the kernel20:13
fsmithredupdate-grub after editing /etc/default/grub20:14
leventeI did20:14
fsmithredok20:14
fsmithredmaybe you need xorg.conf20:15
fsmithreddid nvidia make one for you?20:15
fsmithred(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)20:15
leventeI'm not sure20:19
fsmithredI think if you run nvidia-xconfig it will make a sample xorg.conf20:20
fsmithredbeen a couple years since I've used nvidia20:20
leventeI don't have any command called nvidia-xconfig20:20
fsmithredok20:20
leventeI did have it on other distros though, which is weird20:20
fsmithredit might be a separate package20:20
fsmithredand you get it by default if you install the binaries downloaded from nvidia20:21
leventeI installed the drivers with apt20:21
fsmithredyeah, I haven't done it that way as many times as I've done it the other way20:21
gnarfacelevente: what's the card model?20:29
gnarfacelevente: it occurs to me that nvidia has deprecated everything before the 600 series20:30
leventeI have a GTX 750 TI20:30
gnarfacethat should still work20:30
leventeyeah...20:30
gnarfaceis it an optimus laptop?20:30
leventeIt's a desktop20:30
gnarfaceok.  and the GPU isn't onboard?20:30
leventeNo, it's a dedicated GPU20:31
gnarfaceok20:31
gnarfaceso this should work and we're just overlooking something20:31
gnarfaceit might be the xorg.conf but i feel like nvidia should at least LOAD without it...20:31
gnarfaceit shouldn't be loading a blacklisted driver that's for sure20:31
gnarfacelevente: when you blacklisted nouveau, did you create a new file or add to an existing one?20:32
leventethere was already a file named nvidia-blacklists-nouveau.conf20:32
gnarfaceok20:32
leventeit already had 'blacklist nouveau' in it20:32
gnarfaceok, that should be working20:32
gnarfacehmmm20:34
gnarfacelevente: what if you run this as root?  `X -configure`20:37
leventeserver already active, let me stop it20:37
gnarfaceit should generate an xorg.conf.new but i'm curious what i'll put in it20:37
gnarfaceyou'll have to stop slim too20:37
leventeyes20:37
leventeyeah, I did that20:38
leventeIt didn't list nvidia when it listed all the drivers though20:39
gnarfacehmm20:40
gnarfaceshow me the output of: dpkg -l |grep nvidia -i20:40
gnarfacealso, re-run `update-initramfs -u -k all` just for good measure20:41
leventehttp://paste.debian.net/1039699/20:42
gnarfacehmmm20:43
gnarfacelooks fine20:43
gnarfacewhat about the contents of /etc/X11/Xsession.options?20:43
leventehttp://paste.debian.net/1039700/20:44
gnarfacesame as mine20:45
gnarfacei feel like there's something i'm forgetting20:45
leventehmm20:45
gnarfacebut nothing comes to mind right now except my manual xorg.conf creation20:45
leventenvidia drivers never liked me20:46
gnarfaceso i guess that's what we should try next for you20:46
gnarfacein theory you shouldn't need the whole thing so we'll just start with a snippet20:46
gnarfacestand by i'll try to find a similar example here20:46
leventealso, what should I do with xorg.conf.new?20:47
leventesince you made me make one20:47
leventeX -configure listed all the drivers but nvidia wasn't among them20:47
gnarfaceoh, i was gonna ask you to pastebin the xorg.conf.new if it used the nvidia driver by default20:47
leventeI doubt that, but I will paste it anyways20:48
gnarfacejust hold onto it for now you still may need to reference it20:48
leventexorg.conf.new: http://paste.debian.net/1039700/20:48
leventewrong paste20:48
leventehttp://paste.debian.net/1039702/20:49
gnarfaceoh20:51
gnarfaceinteresting20:51
gnarfacethat looks right actually20:51
gnarfaceyou might only actually need this much of it though: http://paste.debian.net/1039703/20:52
gnarfacethe critical point is that it should at least error about why it can't load the nvidia driver instead of just skipping it20:52
gnarfacewe should see a change in the log file20:52
leventesomeone posted a snippet from the file above20:52
leventelet me look for it20:52
levente<fsmithred> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)20:53
leventefrom the X log file, that is20:53
gnarfaceyea, i saw that but it's already loading nouveau by then which should be blacklisted20:54
gnarfaceso something is going wrong before that20:54
gnarfacesomething on the order of "are you sure this is the machine your terminal is actually logged into" wrong20:55
gnarfaceso part of making an xorg.conf snippet is just to see if the log output actually changes in an expected fashion whether it works or not20:55
leventeokay, let me put that in the config file20:56
gnarfaceif you get literally no change to the log output, something is REAAALY wrong here20:56
leventewhere is the main config file for X located?20:57
gnarfaceby default it no longer exists.  but it still belongs in /etc/X1120:58
leventeso just in /etc/X11?20:58
leventeno subdirectories?20:58
gnarfaceyou can create the file at /etc/X11/xorg.conf or in the subdirectory /etc/X11/xorg.conf.d20:59
gnarfacethere's a couple other places too20:59
leventexorg.conf, right?20:59
gnarfaceyes20:59
leventeI will symlink it to xorg.conf.d just to make sure, or is that a bad idea?21:00
gnarfacewell if you're gonna use the whole thing make it /etc/X11/xorg.conf but if you're just going for a snippet make it something like /etc/X11/xorg.conf.d/10-snippet-for-nvidia.conf21:00
gnarfaceno symlinks21:00
gnarfacethe top of that log file will tell you what configs it actually picks up21:00
gnarfaceso we'll know if it even reads it21:00
leventeso do I reboot now?21:00
gnarfaceyea21:01
leventesomething went horribly wrong, slim wouldn't even load21:06
leventeI saw a message from the init though, it said 'error running install command for nvidia#21:06
gnarfacehmmm21:07
gnarfaceok21:07
gnarfacei wonder if dkms went awry21:08
gnarfaceyou have a package called "nvidia-kernel-dkms" installed, right?21:08
gnarfaceif you do, run `dpkg-reconfigure nvidia-kernel-dkms` if not, install it.21:08
gnarfacefirst install the "dkms" package if it's not present too21:08
leventeModule build for kernel 4.9.0-6-amd64 was skipped since the21:09
leventekernel headers for this kernel does not seem to be installed.21:09
leventeI think that may be the root of the problem21:09
gnarfaceoh21:09
gnarfaceyea, that's it21:10
gnarfacethat would have made dkms fail, which would have meant your initrd.img won't have the nvidia module at boot time21:10
gnarfacethat doesn't really explain how it loaded nouveau inspite of being blacklisted but it explains why nvidia didn't load21:10
gnarfacemake sure you've installed 'linux-image-amd64' and 'linux-headers-amd64' then they'll both stay current with updates21:10
leventeI've installed them21:12
leventeIt still says that the kernel headers are not installed21:13
leventebut it's building something21:13
leventeso I guess that's good21:13
gnarfacedid the kernel update when you just did that?21:13
leventeDKMS: install completed.21:13
leventeNo, it's still 4.921:13
gnarfaceit's possible the headers and kernel you installed were not matching to the running one21:13
gnarfacethat might have been the cause of the complaint21:14
leventeHaven't updated my kernel at all21:14
gnarfacewell, either way, reboot agian to see if it worked21:14
leventeokay, brb21:14
leventeThat seemed to fix it, my screen is back to normal now21:16
leventethanks21:16
gnarfacewhew21:16
gnarfacewhat amess21:16
gnarfaceglad it works again though21:16
leventeI'm writing this down jesus christ, this was certainly a mess21:17
leventeyes, and it uses the nvidia driver now21:17
leventetysm21:17
gnarfaceno problem. it's not supposed to be that hard but nobody is really reaching the rest of the way across the aisle on this one21:17
gnarfaceif you need to support 32-bit components of wine or steam you should just need to add libgl1-nvidia-glx:i38621:19
gnarface(after enabling multi-arch of course)21:19
leventeokay, thanks21:20

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!