| 1 |
Daiajo Tibdixious posted on Sat, 08 Oct 2016 20:35:55 +1100 as excerpted: |
| 2 |
|
| 3 |
> This relates to my ATI driver conflict with xorg-server problem. |
| 4 |
> Sorry if this comes though in html format I did not realise the last one |
| 5 |
> was in html mode. |
| 6 |
> I'm trying the solution to stop using fglrx and just use the radeon |
| 7 |
> driver, |
| 8 |
> however I'm getting weird problems. |
| 9 |
> |
| 10 |
> I removed fglrx from VIDEO_CARDS. Enabled radeon driver as a module in |
| 11 |
> the kernel, |
| 12 |
> plus several other options recommended by the wiki. |
| 13 |
> First I hacked \etc\X11\xorg.conf to removed the ATI specific code, |
| 14 |
> however I get the same problem with X -configure code. |
| 15 |
> |
| 16 |
> Googling the actual error "Screen 0 deleted because of no matching |
| 17 |
> config section" |
| 18 |
> shows that its not that, its some kind of driver problem. |
| 19 |
> I've tried everything I can think of (except putting the driver in |
| 20 |
> kernel with firmware blobs). |
| 21 |
> |
| 22 |
> Instead of my phone I borrowed another computer and can transfer stuff |
| 23 |
> to it via USB. |
| 24 |
> |
| 25 |
> I have enclosed xorg.conf (from X -configure) and /var/log/Xorg.0.log |
| 26 |
> |
| 27 |
> Any hints on what else I can try? I don't want to try the other |
| 28 |
> alternative (use fglrx with old versions of xorg-server and the |
| 29 |
> input-evdev,video-ati drivers) yet. |
| 30 |
|
| 31 |
From the log... |
| 32 |
|
| 33 |
> [ 32385.590] Build Operating System: Linux 4.4.6-gentoo x86_64 Gentoo |
| 34 |
|
| 35 |
> [ 32385.606] (II) [KMS] drm report modesetting isn't supported. |
| 36 |
> [ 32385.606] (EE) Screen 0 deleted because of no matching config |
| 37 |
> section. |
| 38 |
> [ 32385.606] (II) UnloadModule: "radeon" |
| 39 |
|
| 40 |
That's the problem. Reasonably new xf86-video-ati (the radeon driver) |
| 41 |
requires KMS, kernel mode setting. Because it can't detect that it |
| 42 |
doesn't even get as far as detecting the radeon chipset. |
| 43 |
|
| 44 |
Just to be sure we're looking at the same wiki page: |
| 45 |
|
| 46 |
https://wiki.gentoo.org/wiki/Radeon |
| 47 |
|
| 48 |
Most of this appears to be covered in the wiki, which you mentioned, but |
| 49 |
just to be sure (I have a monolithic-build kernel here, module loading |
| 50 |
disabled, so the below reflects that): |
| 51 |
|
| 52 |
Kernel config, drivers, graphics: |
| 53 |
|
| 54 |
[*] Direct Rendering Manager |
| 55 |
|
| 56 |
(My 4.7 kernel doesn't show the radeon options here under DRM/DRI as the |
| 57 |
wiki implies. They're elsewhere. Of course that means no mode-setting |
| 58 |
option here either.) |
| 59 |
|
| 60 |
Still directly under graphics: |
| 61 |
|
| 62 |
[*] ATI Radeon |
| 63 |
|
| 64 |
(There's an always enable userptr support sub-option, not checked here, |
| 65 |
but the help says it selects mmu_notifier, which a search says is already |
| 66 |
on for other reasons. It shouldn't hurt to turn it on, tho, and may |
| 67 |
help.) |
| 68 |
|
| 69 |
Still directly under graphics: |
| 70 |
|
| 71 |
Frame buffer Devices |
| 72 |
|
| 73 |
This is hard-enabled here by options I've set elsewhere. |
| 74 |
|
| 75 |
*** WARNING, UNINTUITIVE *** |
| 76 |
|
| 77 |
Do *not* set ATI Radeon display support here, under frame-buffer |
| 78 |
devices. On the wiki it's unset, but it's both unintuitive and easy to |
| 79 |
miss that it's unset. The radeon-specific framebuffer driver is for UMS, |
| 80 |
not KMS. All that's needed is that the main/generic framebuffer support |
| 81 |
option be enabled (which as I said it is here, no option to disable it). |
| 82 |
|
| 83 |
I also have enabled, but am not sure it's necessary: |
| 84 |
|
| 85 |
Under graphics, Console display driver support: |
| 86 |
|
| 87 |
[*] Framebuffer console support |
| 88 |
|
| 89 |
The map the console to the primary display device sub-option is hard- |
| 90 |
enabled, no way to turn it off. |
| 91 |
|
| 92 |
(I also keep vga text console enabled as a fallback, in case I switch to |
| 93 |
an incompatible video card or something, but the framebuffer console is |
| 94 |
what's actually used.) |
| 95 |
|
| 96 |
If all those checkout, note that as the wiki says, firmware blobs are |
| 97 |
required for r600+. I use the radeon-ucode package, but if you need |
| 98 |
other blobs you may prefer the linux-firmware package. |
| 99 |
|
| 100 |
As the wiki says, if you're building the module into the kernel (as I do, |
| 101 |
since I have a monolithic kernel with all modules builtin), you'll need |
| 102 |
the firmware builtin as well. |
| 103 |
|
| 104 |
The kernel log (dmesg) should confirm whether and what firmware loaded, |
| 105 |
or report that it couldn't, if that's the problem. |
| 106 |
|
| 107 |
|
| 108 |
(Personal note, since I'm known to be rather particular about proprietary |
| 109 |
code. My personal line is code loaded on whatever device, vs. code run |
| 110 |
on the CPU. While I don't consider firmware blobs like the above that |
| 111 |
run on some other device, in this case the GPU, to be ideal, I can and |
| 112 |
will, if reluctantly, load them, while I won't run the proprietary |
| 113 |
drivers as they run on the CPU. That's the distinction I have made for |
| 114 |
some time, tho with GPUs being used for more than graphics these days, I |
| 115 |
realize that can be more of a compromise than it was when such things |
| 116 |
were single-purpose dedicated. But as I'm not (yet?) running anything |
| 117 |
but graphics on the GPU, that's a bridge I've yet to cross.) |
| 118 |
|
| 119 |
-- |
| 120 |
Duncan - List replies preferred. No HTML msgs. |
| 121 |
"Every nonfree program has a lord, a master -- |
| 122 |
and if you use the program, he is your master." Richard Stallman |
Archives