Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SWC fails to create WLD DRM context for nouveau drivers unless WLD_DRM_DUMB environment variable is set. (possibly WLD bug?) #32

Open
faithanalog opened this issue Aug 3, 2015 · 3 comments

Comments

@faithanalog
Copy link
Contributor

I use the nouveau drivers. Running swc-launch velox without WLD_DRM_DUMB results in

[swc:libswc/drm.c:161] DEBUG: /dev/dri/card0 is the primary GPU
# find_driver: Trying DRM driver `intel'
# find_driver: Trying DRM driver `nouveau'
[swc:libswc/drm.c:319] ERROR: Could not create WLD DRM context
[swc:libswc/swc.c:133] ERROR: Could not initialize DRM

And with WLD_DRM_DUMB=nouveau, it starts properly.

I'm unsure of whether this is a wld bug or an swc bug, but I'm submitting here because the error was printed in swc code. I did add some debug statements to wld, and verified that driver_device_supported is returning true for nouveau, and wld is returning the nouveau driver in drm.c, so I'm not sure what the actual problem is.

@faithanalog faithanalog changed the title swc fails to create WLD DRM context for nouveau drivers unless WLD_DRM_DUMB environment variable is set. (possibly wld bug?) SWC fails to create WLD DRM context for nouveau drivers unless WLD_DRM_DUMB environment variable is set. (possibly WLD bug?) Aug 3, 2015
@michaelforney
Copy link
Owner

What generation card do you have?

I only have an NVC0, so that is all that is supported by wld at the moment. If you want to try to get your card supported, you could take a look at nouveau.c.

@faithanalog
Copy link
Contributor Author

GTX 760, which I believe would be NVE4

@michaelforney
Copy link
Owner

Cool. If you uncomment https://github.com/michaelforney/wld/blob/master/nouveau.c#L112, there is a chance that it will just work. However, there is also a chance that it won't. If it seems like nothing is displaying, I think normal key bindings should work, but just in case, you should make sure you have a way to ssh in and kill velox.

Let me know how it goes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants