search

imageguy / fglrx-for-Fedora

Patch for the AMD fglrx proprietary video driver 15.302 for installing on Fedora 23, kernel versions 4.4.* and later
MIT License
31 stars 8 forks source link

Black Screen on kernel 4.7.5-200 #7

Open EpicJhon opened 8 years ago

EpicJhon commented 8 years ago

I tried to install, but does not work in the new kernel 4.7.5-200

EpicJhon commented 8 years ago

that point does not pass

image

mirh commented 7 years ago

Still an issue?

kbtz commented 7 years ago

@mirh I think so, if I remember correctly, I ran into the same issue about a month ago

imageguy commented 7 years ago

Yes, still an issue. It's on my "list of things to look at", but at this point I just live with it, though it's annoying. The login screen is there in a sense, it just doesn't show. If you press enter, it will log you into whatever account was used last. Nothing will show until you type in the password, after that my KDE starst up.

mirh commented 7 years ago

Wait a minute Described this way, I have the exact fucking same in Manjaro. With xfce.

Sometimes annoying

imageguy commented 7 years ago

If I understand it properly, the login screen is independent of the desktop you run, be it KDE, Gnome, Xfce. I've saved relevant logs but haven't had a chance to really work on it. A long while ago, I tried the process that was outlined in one of the entries on the community discussion site, but it didn't work for me. Most likely I messed something up, but hadn't had time to really look at it then.

imageguy commented 7 years ago

....though I'd say often annoying instead of sometimes annoying.....

mirh commented 7 years ago

If I understand it properly, the login screen is independent of the desktop you run, be it KDE, Gnome, Xfce.

Mhh, you have a point, it's handled by the display manager. And quite funnily intriguinly both KDE and xfce use SDDM.

Threfore this situation can only make sense. It would be interesting to compare with GDM and LightDM then.

mirh commented 7 years ago

Ohhh, it starts to get always more and more interesting. https://aur.archlinux.org/cgit/aur.git/tree/arch-fglrx-authatieventsd_new.patch?h=catalyst-utils Notice how there are GDM and LDM entries for, well, fixing something. Which eventually seems to derive from these problems. Very similar to what we have. Also this is worth investigating.

Last but not least then, are you perhaps getting [fglrx:firegl_unlock] *ERROR* firegl_lock_free failed! too?

imageguy commented 7 years ago

According to my /var/log/messages, mine fails in shader compilation:

Sep 12 17:20:40 localhost journal[1636]: Shader compilation failed:#012Fragment shader failed to compile with the following errors:#012ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context#012ERROR: error(#273) 1 compilation errors. No code generated#012 Sep 12 17:20:40 localhost journal[1636]: Failed to link GLSL program:#012Vertex and Fragment shader(s) were not successfully compiled before glLinkProgram() was called. Link failed. #012 Sep 12 17:20:40 localhost journal[1636]: driver/gl/cogl-pipeline-progend-glsl.c:384: GL error (1282): Invalid operation

There are a couple of patches for cogl that are supposed to fix this problem (see https://bugzilla.gnome.org/show_bug.cgi?id=756306). The first time i tried, long ago, I messed something up and cogl just wouldn't work any more. I just tried again, cogl works, but no change in behavior. Based on the comments at the bottom of the page, patches might not be good or enough, but I haven't had a chance to study the thread yet.

imageguy commented 7 years ago

I haven't seen the fglrx_lock_free error, at least not in messages.

mirh commented 7 years ago

Oh, that's in dmesg. I had never checked /var/log/messages then cause that's all in journalctl in arch

Give a check to https://bugzilla.gnome.org/show_bug.cgi?id=771587 https://bbs.archlinux.org/viewtopic.php?id=57084&p=287#p1571522

imageguy commented 7 years ago

As far as I understand, dmesg stuff, at least on Fedora, is one of the things going into /var/log/messages. I checked and there are no fglrx_lock_free messages on my box.

The version issue is apparently at the root of the problem - it's supposed to be addressed in gl_Add_a_quirk_for_the_GLSL_version_to_use_on_AMD_v2.patch in https://bugzilla.gnome.org/show_bug.cgi?id=756306, but that code seems slightly different than the one in 771587 and has an earlier date.

I took a peek today and I think my cogl patch didn't install, or probably installed in a wrong spot, when I did a make install. The README refers to the "INSTALL" document, which is nowhere to be found. I'll take a peek at the Makefile and if all fails try copying stuff over by hand and see what gives.

imageguy commented 7 years ago

No luck luck with the patches. I applied both patches from 756306, then added the patch from 771587 on top - it did add an extra piece to the other patches. I then rebuilt my fglrx, but no luck, I still get the version failure. I did make sure it's installed in /usr/lib64 (/lib64 links to it on my box) so, as far as I know, I am picking up the patches. I'll poke some more as I have time and if I get any ideas...

mirh commented 7 years ago

~~Mhh, I dunno, maybe time has brought in some new breakage? Can you downgrade easily on fedora?~~

Mhh, Vi0L0 was indeed reporting back that KDE behaves differently. In other news, I just double checked journal and xorg.log and I'm not getting that error. Which possibly implies it has nothing to do with black screen. Maybe we should open another issue for that?

imageguy commented 7 years ago

I am not 100% sure that my "fix" was good, though I do know this error is one of the causes of the black login screen, and it is at the right time in the log. I have a feeling there are several possible causes of the black login screen - it looks like yours is different than mine. You might try opening an issue for that....