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

[RFC] Ignore failure to set DRM interface #771

Merged
merged 1 commit into from
May 19, 2016

Conversation

bluca
Copy link
Member

@bluca bluca commented May 14, 2016

This always fail due to problems in libdrm, but does not affect
Bumblebee's functionality. See GH-652 for more details.

XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

This throws user off track often, since it's reported whether or not Bumblebee works, so IMHO we should ignore it. A user spent some time investigating, and apparently it's down to a problem in libdrm: #652

This always fail due to problems in libdrm, but does not affect
Bumblebee's functionality. See Bumblebee-ProjectGH-652 for more details.
@Lekensteyn
Copy link
Member

👍 less noise is always good. Any idea why this happens? Maybe rootless Xorg, or is only one client allowed to connect/change this option in the kernel?

@bluca
Copy link
Member Author

bluca commented May 19, 2016

It happens on Jessie too, where there is no rootless Xorg.
I'm not sure for the actual reason, but there was some analysis in #652 and it seems it's down to a certain version of libdrm and up.

@ArchangeGabriel
Copy link
Member

I’ve always been reluctant to blacklisting this one, since I’ve never been sure of the root cause (which I am for all the other ones). Anyway, never seen any issue really related to this, so LGTM.

@ArchangeGabriel ArchangeGabriel merged commit 881fab5 into Bumblebee-Project:develop May 19, 2016
@bluca bluca deleted the drm_red_herring branch June 2, 2016 22:12
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

Successfully merging this pull request may close these issues.

None yet

3 participants