mamarleytseliot: ricotz: Last night I tried to package 361.28 for the PPA based on a diff between 361.18 and the 361.28 in NEW for Xenial, but I had a few questions.  First, how long are packages stuck in NEW?  Would it be worth it to re-upload 361.28 for Xenial in the PPA?11:22
mamarleySecond, I'm not quite sure how to handle Wily and Trusty.  In the PPA, the packaging for Xenial and Wily was identical besides the EGL alternative stuff in Xenial.  Should I upload the Xenial packaging for 361.28 to Wily (minus the EGL alternatives), should I base the Wily 361.28 off of the Wily 361.18, or should I backport some subset of the changes?11:22
mamarleyThe packaging for Trusty had several differences between that of Wily and Xenial, so I am not sure what if any of the changes from 361.28 I should backport to that.11:23
tseliotmamarley: as for NEW, that's anybody's guess. I pinged an admin11:24
tseliotyou can reuse the Xenial packaging (minus EGL) in Wily11:25
mamarleyOK, that's what I though.11:25
tseliotas for trusty, I think the same as Wily would work11:26
mamarleyAh, OK, that makes things easier.  Thanks!11:27
* tseliot has just uploaded nvidia-settings in xenial11:27
ricotzdon't forget the substvars modifications11:31
mamarleyricotz: I don't think I am familiar with that change?11:32
ricotzfor trusty to allow installation of the lts-xorg stacks11:32
mamarleyAh, yes.  OK, I will make sure to get those.11:33
tseliotricotz, mamarley: only the xorg-video-abi-$number is needed though11:41
tseliotno need to depend on xserver-xorg-core-lts-* any more11:41
marlincGood afternoon!11:42
mamarleytseliot: It already depends on one of xorg-video-abi 11 throught 20 in the Xenial packaging, so that will be sufficient?11:43
tseliotmamarley: yes, I think so11:43
mamarleyCool, thanks!11:43
mamarleyricotz: I have uploaded 361.28 to https://launchpad.net/~mamarley/+archive/ubuntu/staging/+packages.12:56
ricotz"nvidia-graphics-drivers-361 - 361.28-0ubuntu1+gpu16.04.1" <- NO12:57
ricotzthe official upload should/must override it12:58
mamarleyOops, I actually didn't mean to use a + there.12:59
mamarleyricotz: Are Wily and Trusty OK?  I can re-upload Xenial with a ~.13:07
ricotzmamarley, I don't like to have the 352 transitionals just yet13:15
ricotzso for any 361 upload those should not be there13:16
mamarleyricotz: OK, I will cut those out.  Anything else?13:22
ricotzmamarley, that should be it13:23
ricotztseliot, btw, I really don't like you starting a new changelog with every new series, the packaging doesn't appear out of thin air ;P13:24
mamarleyricotz: Should I leave the transitionals in for Xenial since the official package with transitionals will override ours anyway?13:42
ricotzmamarley, no, otherwise the ppa packages of 352 are gone with them13:43
mamarleyricotz: OK13:44
tseliotricotz: well, it's really a new source package though ;)13:44
ricotztseliot, still, you know what I mean13:45
tseliotI do13:45
tseliotI keep track of all the changes in git, so I really don't need the changelogs to remind myself of what I included (from previous releases) in the packaging13:47
mamarleyricotz: Do you mind if I upload the fixed packages straight to gpu-drivers or should I make another temporary staging PPA for that?14:08
ricotzmamarley, if you are sure you got it right14:20
mamarleyFor Xenial, I replaced the + with a ~ in the version.  For everything, I removed the 352-related stuff from the control.in template.14:21
ricotzmamarley, alright, double-check and upload ;)14:23
* mamarley nervously quadruple-checks his work.14:24
mamarleyricotz: OK, it is all uploaded.  I even checked after running debuild -S -sd to make sure the 352 stuff was gone from the generated control file before uploading. :)14:35
mamarleysoee: 361.28 is ready for testing.  Please use the version from the gpu-drivers PPA and not the one from my staging PPA.  (I hope you disable that when you aren't actively testing something?)15:20
soeemamarley: i have drivers ppa always enabled :)15:20
ricotzmamarley, clear your ppa?15:25
mamarleyricotz: D'oh, yes, I should do that.15:25
soeeupdating now15:27
tseliotmarlinc: can you reproduce the problem and show me your dmesg and X log, please?15:46
marlincAny specific things I should enable first? Should I use the PPA?15:47
tseliotmarlinc: was the problem there after enabling the PPA?15:55
tseliotI'm talking about the last problem you mentioned yesterday15:55
marlincI'm sorry tseliot, lost my connection to the bouncer16:03
tseliotmarlinc: I was already away yesterday, and you pinged me about a problem with hybrid graphics that maybe involved the PPA. Whatever the last problem you ran into was, I would like to see those two files, and possibly the output of a command16:05
marlincOkay, tjaalton asked me to try the PPA. Then I ran into issues where LightDM wouldn't start16:07
marlincOne moment16:07
marlincI'm starting using the PPA now tseliot 16:13
soeenew driver works fine :)16:13
marlincOkay, so yesterday we commented everything in /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf as LightDM was crashing when I switched to the NVIDIA driver using prime-select16:15
marlincCurrently that's causing a black screen with the following errors in the greeter log https://gist.github.com/anonymous/1f8d9e00474afbf209b816:16
soeehmm, mamarley ping16:16
soeemamarley: steam now yields this: http://wstaw.org/m/2016/02/11/snapshot65.png16:17
marlincI see there's a ton of updates, I'll install those to make sure I'm not missing any fixes16:17
marlincIncluding ZFS, nice16:18
mamarleysoee: I'm not where I can look at that.  Can you give a quick description?16:18
tseliotmarlinc: I see a lot of errors but none specific to nvidia16:18
soeemamarley: Could not find required OneGL entry point 'glGetError'! Either your video card is unsupported, or your OpenGL driver  needs to be updated.16:19
marlincLightDM runs a X server right? Is there a way to look at what its doign?16:19
tseliotmarlinc: /var/log/lightdm/ has the different logs16:20
marlincOne moment, I'll reboot the server. Got a kernel update16:21
marlincReboot the laptop*16:22
marlincOkay, I've removed all the logs and restarted LightDM16:23
mamarleysoee: This is new for 361.28?16:24
soeemamarley: i think so. never seen it before16:24
marlincThese are all the logs tseliot https://gist.github.com/anonymous/24846fdffb2cc60f193516:25
marlincI'll post dmesg as well16:25
marlincAnd this is dmesg tseliot https://gist.github.com/anonymous/ade956eeec744021417f16:26
tseliotI don't see it execute the script for prime...16:27
marlincAh, yes tjaalton and I disabled that to debug16:27
marlincI'll re enable it and post some new logs16:27
marlincThe logs might be confusing as LightDM keeps restarting, or rather the X server that LightDM uses I think. Will post the logs now16:29
marlincThere you go tseliot https://gist.github.com/anonymous/c30e9500c63007c82ba016:30
tseliotmarlinc: the greeter got an error from X, and died16:32
marlincI guess that makes sense, unity-greeter crashes which causes the X server to shutdown. And then LightDM tries to start the X server again16:32
marlincAnything else I can do to get more information on the issue16:33
tseliotmaybe it's a problem with the modesetting driver.  Try booting with either gpumanager_uxa or gpumanager_sna, and see which one works16:34
tseliot(kernel parameters)16:35
marlincWill do16:35
tseliottjaalton: I should probably test the PPA myself with hybrid graphics16:37
tseliotjust in case...16:37
marlincOkay, uxa doesn't work. Will test sna now16:37
marlincSame greeter errors16:37
tjaaltonhmm, my old laptop has i+n.. will steal it from the wife and upgrade it to x16:38
tseliotthat would be a good idea... don't tell your wife though :P16:39
marlincOkay now sure if this is better or worse. With sna its just starting X and nothing else16:40
marlincFatal server error:16:40
marlinc(EE) Failed to recover from error!16:40
marlincThis is it https://gist.github.com/anonymous/8c5421e8510189a5736116:41
marlincAnd the two lines I pasted above are what's in the X log16:41
tjaaltontseliot: it was still on vivid, so about time I upgraded it16:41
tseliotright ;)16:42
tseliotmarlinc: ok, so sna is not expected to work (they broke it in the previous release cycle). If uxa doesn't work though, then something else is going on16:43
tseliotbut I can't see what from the logs16:43
tseliotcalling xrandr likely causes the issue16:44
tseliotare you doing this while the external screen is connected?16:44
marlincYes, I'll disconnect it and restart LightDM. But I guess I first have to boot over to either uxa or a regular boot16:46
marlincBut I'm back in about 20-30 minutes have to eat, thanks!16:46
tseliotregular boot would be fine16:47
marlincOkay back tseliot 17:01
marlincA single screen crashes as well tseliot 17:03
marlincSame greeter error17:04
tseliotmarlinc: and it doesn't crash if you comment out the nvidia script?17:05
marlincThen the screen just stays black17:05
marlincWait let me check to be sure17:05
marlincYep stays black17:06
tseliotmarlinc: if the screen stays black, you can try to log in blindly. Just type in your password and press enter, after your hear the drums. Then ssh into the computer17:06
tseliotI need you to run a command after that17:07
marlincI can try logging in, I'm already logged in SSH if that helps17:07
marlincVia SSH*17:07
marlincLets see what the log says if I try to login17:08
tseliotmarlinc: the thing is you need to login from the greeter or the command will fail17:08
tseliotthis is the command: DISPLAY=:0 xrandr --listproviders17:08
marlincAh, you need a active X server. I should be able to run that now17:09
marlincProviders: number : 017:09
tseliotdid you log in from the black screen?17:10
marlincI did17:10
marlincI can see that I logged in as the LightDM shows that17:10
marlincLet me gist it17:10
tseliotboth intel and nvidia should show up there17:10
tseliotright I can see that17:12
tseliottjaalton: randr 1.4 support is broken ^^17:12
tseliotno wonder X dies17:12
marlinc<marlinc> I can see that I logged in as the LightDM log shows that17:13
tjaaltonthat'd be surprising17:13
marlincI have typing problems at the moment :p17:13
tseliotmarlinc: what does /var/log/gpu-manager.log say?17:13
marlincLet me try something, I'll switch to intel using prime-select and see what happens17:14
marlincThere you go17:14
marlincJust tried starting by switching to intel using 'prime-select'. That does work and show LightDM17:16
marlincSwitched back to NVIDIA which has the problems we're looking at17:17
tseliotcan you try this command again after switching to intel, please? DISPLAY=:0 xrandr --listproviders17:17
tseliotthe log looks fine BTW17:17
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:0 xrandr --listproviders17:19
marlincProviders: number : 017:19
marlincBtw the actual session, works just fine when I log in using intel17:19
tseliottjaalton: that is wrong ^17:20
marlincAh that explains it, it started on another display number17:20
marlincIts 1 now17:20
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr --listproviders17:20
marlincProviders: number : 117:20
marlincProvider 0: id: 0x47 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 4 associated providers: 0 name:Intel17:20
tseliotmaybe try again with nvidia then on display 117:20
marlincOkay, will do17:20
tseliotremember to log in17:21
tjaaltonProgress: [ 39%]17:21
tjaaltongetting there17:21
marlincAh, there you go17:21
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr --listproviders17:21
marlincProviders: number : 217:21
marlincProvider 0: id: 0x204 cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 0 name:NVIDIA-017:21
marlincProvider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 0 name:modesetting17:21
tseliotok, that looks much better17:21
marlincNot sure what display 0 is17:22
marlincI can even get GLX info17:22
marlincOpenGL renderer string: GeForce 840M/PCIe/SSE217:22
marlincOpenGL core profile version string: 4.5.0 NVIDIA 352.6317:22
marlincOpenGL core profile shading language version string: 4.50 NVIDIA17:22
marlincI guess that this could make sense?17:23
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr17:23
marlincScreen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 1638417:23
marlincIts supposed to show a VGA, HDMI and internal connection17:23
tseliotyes, it's just that attaching the outputs to nvidia causes X to crash17:23
tseliotonce attached you will see the outputs17:24
marlincWhat does prime-offload do? When I run DISPLAY=:1 sudo prime-offload it actually gets the outputs and doesn't crash17:25
tseliotmaybe try crashing X yourself. I'll give you the command17:25
tseliotso maybe this time we get the error in the log17:25
marlincShall I first restart the LightDM so that the session in which I did prime-offload is closed?17:28
tseliotisn't that a different X?17:28
tseliotit shouldn't really matter17:28
marlincOkay ;)17:29
tseliotDISPLAY=:1 xrandr --setprovideroutputsource modesetting NVIDIA-017:29
marlincThat didn't do much17:29
tseliotmeaning? 17:30
tseliotwhat does this say? DISPLAY=:1 xrandr --listproviders17:30
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr --listproviders17:30
marlincProviders: number : 317:30
marlincProvider 0: id: 0x204 cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 1 name:NVIDIA-017:30
marlincProvider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 1 name:modesetting17:30
marlincProvider 2: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 1 name:modesetting17:30
marlincWait, let me restart the session so its clean. The fact that I ran prime-offload might have done something17:31
marlincSo that's clean again17:32
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr --listproviders17:32
marlincProviders: number : 217:32
marlincProvider 0: id: 0x204 cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 0 name:NVIDIA-017:32
marlincProvider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 0 name:modesetting17:32
marlincAfter I ran your command I got the same17:32
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr --listproviders17:32
marlincProviders: number : 317:32
marlincProvider 0: id: 0x204 cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 1 name:NVIDIA-017:32
marlincProvider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 1 name:modesetting17:32
marlincProvider 2: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 1 name:modesetting17:32
tseliotit looks like a bug17:33
tseliottry running prime-offload manually17:34
marlincJust 'DISPLAY=:1 sudo prime-offload'>17:34
marlincJust 'DISPLAY=:1 sudo prime-offload'?17:34
marlincOkay, once again I got somewhat of an image17:35
marlincMight have to make a picture17:35
tseliotDISPLAY=:1 xrandr --listproviders17:35
marlincmarlinc@marlinc-laptop:~$ DISPLAY=:1 xrandr --listproviders17:36
marlincProviders: number : 317:36
marlincProvider 0: id: 0x204 cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 1 name:NVIDIA-017:36
marlincProvider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 1 name:modesetting17:36
marlincProvider 2: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 1 name:modesetting17:36
tseliotmultiple screens within the same screen17:37
marlincNow it out of nowhere started to show https://goo.gl/PpJWId17:37
tseliotmaybe try removing your ~/.monitors.xml17:38
marlinchttps://gist.github.com/anonymous/1db59dd738a71bcf281d is the general xrandr output17:38
marlincRemoved it17:39
tseliotso that kind of worked17:39
tseliottry simply restarting17:39
tseliot(no external screen plugged in)17:39
marlincOkay, I reran all the commands, LightDM restart, --setprovideroutputsource, prime-offload. Same result as the first picture17:40
marlincIt will probably in a minute switch to the second picture17:40
marlincNow I got https://goo.gl/Vbp0tT instead of the other picture17:41
tseliotthe bug must be in the open drivers17:42
marlincAnd now it again switched to the second picture I posted17:42
marlincBut with a second system error pop up17:42
marlincI'm using the nvidia-352 driver17:42
marlincAnd the regular Intel driver that you get out of the box17:43
tseliotcan you try adding a "sleep 2" in prime-offload and before this line, please? # Remove any previous logs17:43
tseliotthen restart lightdm17:43
tseliotBTW it's beyond EOD for me. We can continue tomorrow17:44
marlincNo change at all17:45
marlincOkay, I'll reboot to my regular install without the PPA17:45
marlincThanks a lot17:45
mamarleytseliot: Do you get the emails sent to the graphics drivers PPA team?  We just got an email reporting the same issue soee reported earlier about Source engine games not running on 361.28.  I think something might be out-of-whack with the libraries.17:59
soeemamarley: i tried also reinstalling steam, but with no luck18:00
mamarleytseliot: Maybe we need to extract the .run files with "--glvnd-glx-client"?18:01
* mamarley doesn't actually have Steam on his system.18:02
ricotzmamarley, one reason not to force an update with transitionals ;)18:08
mamarleyricotz: Indeed, but both of these people upgraded manually.18:08
ricotzmamarley, so if needed they can simply switch back in the meantime until this gets settled18:09
mamarleyHmm, the --glvnd-glx-client argument has no effect when -x is used...18:30
mamarleyBecause all the libraries are extracted, not just the GLVND or non-GLVND ones.18:31
mamarleyBut when installed, the libraries are set up exactly the way https://devtalk.nvidia.com/default/topic/915640/unix-graphics-announcements-and-news/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/ recommends...18:32
mamarleyHmm, after reading https://devtalk.nvidia.com/default/topic/915789/-solved-361-28-gtx-580, it appears that the arch people only got it to work by switching to the non-GLVND libraries.  In other words, this appears to be an upstream regression between 361.18 and 361.28 and not a packaging error on anyone's part.18:44
mamarleysoee: ^18:44
soeemamarley: i see, so we have to wait or next release :)18:45
mamarleytseliot: If you have a contact at NVIDIA, it might be worth mentioning that.18:45
tseliotmamarley: ok, I'll do that tomorrow. Thanks20:18
* tseliot -> off20:18

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!