Bug #11518
Linux 4.x QXL 64-bit kernel modesetting breaks 32-bit X.Org
100%
Description
With Linux 4.x we get KMS for QXL enabled by default. But then, when mixing a 64-bit kernel with 32-bit userspace, X.Org fails to start and says something like: “failed to set DRM interface version 1.4: Inappropriate ioctl for device”.
What works:
- booting with the 32-bit kernel (I’m starting to really want
Feature #8183) qxl.modeset=0
I’ve tried a local xserver-xorg-video-qxl 0.1.4-3~bpo8+1 backport, but it did not help.
This affects feature/10298-linux-4.x-aufs (Feature #10298) and feature/stretch (KMS is required since X.Org runs as non-root; and maybe Bug #11441 too).
Subtasks
Related issues
Related to Tails - |
Resolved | 2016-05-18 | |
Related to Tails - |
Resolved | 2015-08-11 | |
Blocked by Tails - |
Resolved | 2016-10-11 |
History
#1 Updated by intrigeri 2016-06-08 08:30:01
- Assignee deleted (
intrigeri)
I’ll workaround this by disabling qxl.modeset
, not sure what are the drawbacks nor if it’s an acceptable long-term solution.
#2 Updated by intrigeri 2016-06-08 08:30:19
- related to
Feature #8183: Ship a 64-bit (x86_64) instead of 32-bit userspace added
#3 Updated by intrigeri 2016-06-08 08:36:54
- related to
Bug #11441: Stretch's X.Org cannot start with Linux 3.16's qxl added
#4 Updated by intrigeri 2016-06-09 05:15:53
- Description updated
#5 Updated by intrigeri 2016-06-09 08:15:37
intrigeri wrote:
> I’ll workaround this by disabling qxl.modeset
, not sure what are the drawbacks nor if it’s an acceptable long-term solution.
I think it’s not a good enough solution for 3.0, since on Stretch X runs as non-root, and so we really need KMS to work.
#6 Updated by intrigeri 2016-06-10 11:57:59
- Target version changed from 2016 to Tails_3.0
- Parent task deleted (
)Feature #10298
The current solution is good enough for Feature #10298, but not for 3.0 => unparenting and adjusting target version accordingly.
#7 Updated by intrigeri 2016-06-10 11:58:13
- related to
Feature #10298: Upgrade to Linux 4.x added
#8 Updated by intrigeri 2016-07-30 09:49:18
- Priority changed from Normal to High
This problem currently prevents X from starting on feature/stretch with the 64-bit kernel (workaround: manually select the 32-bit kernel), so bumping priority.
#9 Updated by intrigeri 2016-08-23 02:53:06
Workaround’ed with commit:348e22764d258ba3710141e20e1a7ba778bc63d4, that should be reverted once we do Feature #8183.
#10 Updated by anonym 2016-08-23 10:12:13
intrigeri wrote:
> Workaround’ed with commit:348e22764d258ba3710141e20e1a7ba778bc63d4, that should be reverted once we do Feature #8183.
Thanks to this I’ve pushed the revert commit:649547083e293e52f07b9fe3200d062d53a0b517 so QXL is used in the automated test suite again.
#11 Updated by bertagaz 2016-11-15 10:33:24
- Assignee set to intrigeri
- QA Check set to Info Needed
Unless I’ve mistaken the problem, sounds to me that this ticket could be closed as we’re going full 64 bit userland in Tails 3.0 (as per Feature #8183).
#12 Updated by intrigeri 2016-11-15 11:42:08
- related to deleted (
)Feature #8183: Ship a 64-bit (x86_64) instead of 32-bit userspace
#13 Updated by intrigeri 2016-11-15 11:42:21
- blocked by
Feature #8183: Ship a 64-bit (x86_64) instead of 32-bit userspace added
#14 Updated by intrigeri 2016-11-15 11:44:01
Right. I’m marking this as blocked by Feature #8183. I don’t want to close this ticket yet, since this problem does exist on current feature/stretch, and our workaround is hackish.
#15 Updated by intrigeri 2016-11-15 17:42:21
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
- QA Check deleted (
Info Needed)