[10:07] ricotz: I have 387.22 in https://launchpad.net/~mamarley/+archive/ubuntu/staging/+packages. For some reason the armhf builds failed without an error email or log. Launchpad was kind of screwy yesterday so it might just be a temporary failure. I just wanted to let you know so you wouldn't go and package the same driver again. [10:07] Also, I haven't done them for Bionic yet because I'm not sure what's going on with that glvnd thing. [11:01] mamarley, you could just retry the armhf build on launchpad [11:02] mamarley, did you pick up the "fixes" from 384? [11:09] ricotz: I did retry the build and it worked this time. Those fixes were for issues that the PPA driver never had, so I didn't do anything with them. [11:09] I think that issue was introduced with 384 and I figured out what it was and fixed it before I initially uploaded. [11:10] mamarley, ok, I assumed so, while t_seliot ignored those changes [11:11] Correct. [11:26] mamarley, do you know if there was some progress regarding 4.14? [11:27] ricotz: I haven't heard anything. I think the license issue is still there. [11:27] I've hacked around that for my personal use, but obviously I can't upload that. [11:28] mamarley, you mean replacing license strings "NVIDIA with GPL" [11:28] Yep [11:28] ok [11:30] Ironically, it was a feature AMD added to the kernel that caused the GPLed symbols to get used by the NVIDIA driver, and AMD won't back down about unmarking them GPL-only. Seems a bit conflict-of-interesty to me. [11:30] haha, interesting [12:02] ricotz: what did I ignore? [12:18] tseliot, e.g. the EGL problem you had to fix [12:18] ricotz: I included the patch that mamarley wrote. I changed that in my latest upload though [12:19] as I said [12:21] you said I ignored those changes. I downloaded the sources yesterday, and I can still see the problem [12:21] https://github.com/tseliot/nvidia-graphics-drivers/commit/a391c65e64948e79e6de8e63645461362216a5e2 [12:21] which I changed doing this https://github.com/tseliot/nvidia-graphics-drivers/commit/d100b808c6180d8fa04906d0c6cf99e3f79a9d16 [12:23] or https://launchpadlibrarian.net/339726913/nvidia-graphics-drivers-384_384.90-0ubuntu1_384.90-0ubuntu2.diff.gz [12:27] ricotz: that's correct, but it's not the problem [12:59] tseliot, what about the gnome-shell specific 71-nvidia.rules change? [13:00] # Make sure the status of KMS is readable [13:00] ACTION=="add" DEVPATH=="/module/nvidia_drm" SUBSYSTEM=="module" RUN+="/bin/chmod 0444 /sys/module/nvidia_drm/parameters/modeset" [13:02] mamarley, https://launchpadlibrarian.net/343791579/nvidia-graphics-drivers-387_387.22-0ubuntu0~gpu17.10.1_387.22-0ubuntu0~gpu18.04.2.diff.gz [13:04] ricotz: Huh? [13:09] mamarley, changes which came up by resyncing with 384 [13:16] Why are we shipping the non-GLVND libEGL? [13:16] We ship the GLVND version of everything else (unless something changed since the last time I checked). [13:24] I don't really understand what is going on in that diff anyway. It looks like it would almost be easier just to abandon the current 387 branch and start from 384 again, but I wasn't the one who did that originally. [13:25] tseliot: Did you switch back to shipping all non-GLVND libraries at some point? From the diff, it looks like that is what happened but I am having a hard time understanding this. [13:26] But there are still some GLVND configuration files in there too. [13:26] * mamarley is befuddled. [14:05] mamarley: I never (intentionally) switched to GLVND [14:50] tseliot: So the idea then is to ship the non-GLVND libraries and only the non-GLVND libraries? If I remember correctly, when they first released GLVND, we packaged the GLVND libraries with the bundled libglvnd. [14:51] If we have switched to shipping the non-GLVND libraries, we also don't need to ship the GLVND configuration files either. [14:52] It seems that the 384 driver in the official archive is in a weird halfway-between state right now. [14:59] mamarley: EGL and vulkan still depend on some GLVND libraries [14:59] which I included [14:59] 18.04 should have support for GLVND though [15:00] OK. It seems like the easiest thing to do for now would just be to abandon the current 387 packaging stuff and branch it off from 384 again. [15:00] I don't have time to do that today though. [15:16] mamarley: I agree [15:44] mamarley, this "rebase" on 384 is what I have done [15:58] Ah, OK.