[10:38] <darkxst>  I played with the KMS modesetting in the new nvidia drivers today, couldn't get plymouth to work, but it should in theory since I got a DRM DUMB BUFFER working after boot
[10:39] <darkxst> and non-root Xorg seems happy enough but mutter segfaults creating the cogl framebuffer
[10:39] <mamarley> It doesn't support fbdev, which is probably why Plymouth doesn't work?
[10:39] <darkxst> mamarley, plymouth doesnt use fbdev
[10:40] <mamarley> Ah, OK.  I don't use Plymouth, so I was only guessing.
[10:40] <darkxst> but apart from that, the ABI verison of the drm module is causing problems (i.e. there is a modprobe ndivia_drm modeset=1, that fails)
[10:40] <darkxst> and also (probably unrelated) nvidia-persistanced is broken on my system due to user permissions, it seems to think that the nvidia-persistentd user is ID 133, when in acutal fact its 151 or something
[10:41] <mamarley> Sounds like your installation is screwed up somehow.
[10:41] <ricotz> darkxst, just for completeness you are using the 364 ppa packages, not installed it yourself?
[10:42] <darkxst> ricotz, yes ppa packages
[10:44] <darkxst> systemd-udev calls "modprobe nvidia_drm", but locally only "modprobe nvidia_364_drm" works
[10:45] <darkxst> I hacked around that with symlinks (and copying modules into initramfs) was able to get to the point of running and also (probably unrelated) nvidia-persistanced is broken on my system due to user permissions, it seems to think that the nvidia-persistentd user is ID 133, when in acutal fact its 151 or something
[10:45] <darkxst> bad paste
[10:45] <darkxst> running https://github.com/dvdhrm/docs/tree/master/drm-howto
[10:45] <darkxst> that works (and is almost identical to how plymouth works)
[10:50] <darkxst> plymouth passed the drmGetCap call (same as example above)
[10:50] <darkxst> but then failed trying to setup the connectors and/or crtc's
[10:58] <darkxst> anyway I will play around more with the plymouth side of things after beta-2, but can you guys  look at loading the nvidia-drm into initramfs and fixing the modprobe error?
[11:05] <darkxst> this: Mar 23 10:41:07 duhast systemd-udevd[475]: Process '/sbin/modprobe nvidia-drm modeset=1' failed with exit code 1.
[11:39] <mamarley> tseliot: ^
[11:49] <tseliot> darkxst: where did you see that modprobe nvidia_drm modeset=1 fails?
[11:51] <darkxst> tseliot, with 364 drivers and kernel param nvidia-drm.modeset=1 
[11:51] <darkxst> but I also get the same if I rmmod and the try to modprobe
[11:52] <tseliot> darkxst: it works fine here (on 16.04)
[11:52] <tseliot> even if I modprobe manually
[11:53] <tseliot> darkxst: what's the error when you modprobe the module?
[11:54] <darkxst> tseliot, I can't try again right now, but pretty sure it was "can't find nvidia_drm module" or similar
[11:55] <darkxst> then It work with `modprobe nvidia_364_drm`
[11:55] <tseliot> darkxst: ok, I can see that the alias for nvidia-drm is missing
[11:55] <tseliot> that should be the problem
[11:55] <tseliot> (nvidia-modeset has an alias)
[11:55] <darkxst> tseliot, then they need to be in the initramfs
[11:56] <tseliot> darkxst: yes, the aliases will be there. All but nvidia-drm are
[11:56] <tseliot> I'll fix that
[11:56] <darkxst> tseliot, no the modules, so plymouth can get them
[11:56] <tseliot> I'm not sure why things work here though
[11:57] <tseliot> darkxst: we don't do that in Ubuntu. You can add them manually if you like
[11:58] <tseliot> tjaalton: ^ do we do that with intel?
[11:59] <darkxst> tseliot, I think all the other drm drivers are in the initramfs
[11:59] <tseliot> (I could be wrong)
[11:59] <darkxst> nvidia-drm isn't because its like a day old
[11:59] <tjaalton> yep
[11:59] <tseliot> oh, ok then
[11:59] <tseliot> I'll fix that up
[12:02] <darkxst> tseliot, ok, thanks!
[12:03] <ricotz> tseliot, watch out for hyphen vs underscore
[12:07] <tseliot> ricotz: yes, I know
[12:10] <ricotz> tseliot, what I meant is "alias nvidia-modeset $(PKG_module)-modeset" or "alias nvidia-modeset $(PKG_module)_modeset" ?
[12:12] <ricotz> so the existing hyphens seem wrong :\
[14:35] <tseliot> ricotz: I see what you mean. I really don't remember why things are the way they are (it's been a while). I can certainly look into that
[18:13] <tjaalton> scr
[18:13] <tjaalton> bah