| 1 |
I can confirm, that radeon KMS is running despite enabling this option. |
| 2 |
From now on I'll run X radeon KMS driver with this option enabled on two |
| 3 |
machines (server and notebook). I report back if something pops up. |
| 4 |
Interesting: Dw. |
| 5 |
-- |
| 6 |
dr Tóth Attila, Radiológus, 06-20-825-8057 |
| 7 |
Attila Toth MD, Radiologist, +36-20-825-8057 |
| 8 |
|
| 9 |
2013.Január 31.(Cs) 00:32 időpontban Dave Armstrong ezt írta: |
| 10 |
> Patching the Linux kernel to disable the sys_iopl and sys_ioperm system |
| 11 |
> calls (e.g., by setting CONFIG_GRKERNSEC_IO=y) used to cause the xserver |
| 12 |
> to fail to start even with KMS-enabled drivers -- at least in the case |
| 13 |
> of the in-kernel radeon driver. |
| 14 |
> |
| 15 |
> I don't know what recent changes are responsible but for whatever |
| 16 |
> reason, X now works fine without the aforementioned system calls on the |
| 17 |
> same hardware. |
| 18 |
> |
| 19 |
> Unfortunately, it doesn't work on another machine using the Intel driver |
| 20 |
> and same X/kernel versions. It fails with the error: "failed to set |
| 21 |
> IOPL". Does anyone know why the Intel, but not Radeon driver, might be |
| 22 |
> failing? I don't have any particular knowledge of the inner-workings of |
| 23 |
> the graphics stack |
| 24 |
> |
| 25 |
> A quick search turned up the following on the X mailing list: "Fix |
| 26 |
> initialization when iopl is forbidden": |
| 27 |
> http://lists.x.org/archives/xorg-devel/2012-September/033656.html |
| 28 |
> |
| 29 |
> http://cgit.freedesktop.org/~ajax/xserver/patch/?id=d88fb00d791c2b19cf9dd244276838aba3a6b442 |
| 30 |
> |
| 31 |
> The above patch applies to x11-base/xorg-server-1.13.2 (with a fuzz |
| 32 |
> factor of 2 but it's good) but I haven't had a chance to test it on the |
| 33 |
> affected machine. I'll post a followup if it fixes the problem. |
| 34 |
> |
| 35 |
> Dave |
| 36 |
> |
| 37 |
> |
Archives