You are not logged in.
Well I talked a bit fast... Actually when I boot Debian Sid (latest updates applied) I have a working system even with nice performance for gaming. But when I boot Archlinux (latest "testing" updates) I get the same result as before updating, crashes when starting games, reboot is the only option. I'm not sure what is failing since the linux-firmware package seems to be the same in both distros (at least it is packaged the same day), and it is the one that fixed almost everything on Debian. I'm a little lost there, I hope there are other Grenada users to help with this.
M/B: Asus M5A97 LE R2.0 CPU: AMD FX(tm)-6100 Six-Core Processor GPU: XFX R9 390 DD Black Edition RAM: Kingston HyperX Beast DDR3 1866 2X4GB SSD: Crucial M4 128GB SATA 3
CPU and GPU are watercooled by Ibercool kit.
Offline
Would you be willing to put llvm-svn packages with full debug symbols enabled into the repository too? That would make it easier to provide better backtraces for bugs like https://github.com/iXit/Mesa-3D/issues/163
Also, does anyone else have that problem with nine?
Offline
I'm experiencing difficulty using mesa-git on my machine: I've installed everything from the repo for mesa-git, but whenever I try using a desktop environment that uses opengl for compositing, I get a ton of artifacts and glitching as well as what seems like a super-oversaturated screen. My card is a FirePro v4800. Thanks in advance for any help.
Offline
sawyerbergeron, please post your Xorg.0.log & lspci -k output
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
sawyerbergeron, please post your Xorg.0.log & lspci -k output
I need to run a reinstall as I messed my system completely up trying to get the proprietary ones to work. I'll edit this post when I reinstall and run those commands to include output.
Offline
@lordheavy
You may want to update the pkgbuilds of llvm-svn and lib32-llvm-svn to include "make ocaml_doc" for the time being: https://groups.google.com/d/msg/llvm-de … k1do5iCQAJ
@sawyerbergeron
To know whether the driver can actually be used running
LIBGL_DEBUG=verbose glxinfo | grep OpenGL
should say something like renderer string: Gallium 0.4 on AMD.....
Offline
@lordheavy
For the time being, can you compile llvm with -mstackrealign like this?
-DCMAKE_C_FLAGS:STRING="-m32 -mstackrealign" \
-DCMAKE_CXX_FLAGS:STRING="-m32 -mstackrealign" \
Offline
@lordheavy
For the time being, can you compile llvm with -mstackrealign like this?-DCMAKE_C_FLAGS:STRING="-m32 -mstackrealign" \
-DCMAKE_CXX_FLAGS:STRING="-m32 -mstackrealign" \
Sure, i can do that
Offline
Thanks, nine works with it.
Offline
@sawyerbergeron
To know whether the driver can actually be used running
LIBGL_DEBUG=verbose glxinfo | grep OpenGL
should say something like renderer string: Gallium 0.4 on AMD.....
Here's the output of that:
`OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.43.0, LLVM 3.8.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0-devel (git-97eee90)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.2.0-devel (git-97eee90)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.0-devel (git-97eee90)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:`
last I checked my card isn't able to run Gallium, correct?
sawyerbergeron, please post your Xorg.0.log & lspci -k output
this is the content of Xorg.0.log: http://pastebin.com/fkyFFzus
and here is the output of lspci -k: http://pastebin.com/VyNXNUPf
Thanks for taking the time to help me in this.
Last edited by sawyerbergeron (2015-12-20 01:17:14)
Offline
last I checked my card isn't able to run Gallium, correct?
No, all radeon gpus from the last 10+ years are using the gallium driver framework.
You may be thinking about radeon r300g/r600g (up to including the radeon HD ~6xxx GPUs) v.s. radeonsi (starting from about the 7xxx series). Redwood is using the r600g driver, but that is something you shouldn't even have to know as there should be no problem.
The glxinfo output looks fine, it was just to confirm the driver is actually used, because sometimes for some or the other reason it fails to be loaded and then everything is rendered with a software renderer on the cpu instead. But "OpenGL renderer string: Gallium 0.4 on AMD REDWOOD" is telling us that it's working fine.
So you are probably suffering from some bug in the driver. Perhaps the FirePro v4800 has some subtle differences to the consumer equivalent of the gpu that the driver isn't considering.. Just a wild guess...
Offline
last I checked my card isn't able to run Gallium, correct?
Wrong , the main difference between amd consumer cards and firepro cards is component quality and features.
Typically they tend to be designed towards stability & reliability,sometimes at the cost of performance.
under the hood they use the same chipsets and can use the same driver.
The pastebin of your Xorg.0.log appears to have been expired, you'll have to post it again.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
@haagch oh, ok. Didn't know Gallium was the base for my card, as it has the same internals as an HD 5670 EDIT: I was thinking of glamor
@Lone_Wolf Here's a link to a log I uploaded to my google drive: https://drive.google.com/file/d/0BxwYn8 … sp=sharing
Thanks again for helping.
Last edited by sawyerbergeron (2015-12-20 20:00:24)
Offline
There are no errors visible in the Xorg.0.log , but i did notice you have 2 monitors connected.
If you disconnect 1, do you also have artifacts with composting window managers ?
Last edited by Lone_Wolf (2015-12-21 11:21:16)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Just tried that, and uninstalled and reinstalled everything xorg and graphics related and the issue persists. Only one monitor connected.
Offline
Ok,so the artifacts are not due to the card having to drive 2 screens.
If you use a non-compositing WM like openbox or twm , do you have any issues ?
Which DE / compositing WM have you tried ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Just a little question here. I recently installed [mesa-git] to have latest mesa and llvm packages (many thanks to lordheavy, they wouldn't compile on my machine) but I still face some issues. I've been advised here to use latest llvm and mesa-git to avoid VM issues, but I still get these errors. So I don't know if this is an issue of llvm not being *that* up to date or if I'm missing something (likely).
As a reminder: I have an R9 390 (grenada) with radeonsi, that should work as R9 290 since it is almost the same hardware (hawaii, which is what lspci shows for me).
Thanks.
M/B: Asus M5A97 LE R2.0 CPU: AMD FX(tm)-6100 Six-Core Processor GPU: XFX R9 390 DD Black Edition RAM: Kingston HyperX Beast DDR3 1866 2X4GB SSD: Crucial M4 128GB SATA 3
CPU and GPU are watercooled by Ibercool kit.
Offline
Ok,so the artifacts are not due to the card having to drive 2 screens.
If you use a non-compositing WM like openbox or twm , do you have any issues ?Which DE / compositing WM have you tried ?
I haven't tried it on either of those, but I've tried Gnome 3, KDE Plasma 4 and 5, and what I'm pretty sure is a default X GUI with xterm (launched using sudo startx.)
I didn't encounter any issue on the X server, and when I use xrender with KDE (I'm pretty sure this is a CPU driven GUI) I don't encounter any major artifacts, but no effects or anything can be run.
Anything that attempt to use OpenGL (2 or 3.1) for compositing has the aforementioned artifacts and graphical glitches.
I can try openbox when I get home, but I wouldn't be surprised if I encountered no issue on that either.
The problem is that I really like Plasma and would really like to get that working, preferably with a bit of eye candy
EDIT: Just remembered: I had at one point tried with Wayland on Plasma and it just didn't load, at all
Last edited by sawyerbergeron (2015-12-22 13:57:59)
Offline
Anything that attempt to use OpenGL (2 or 3.1) for compositing has the aforementioned artifacts and graphical glitches.
make sure compositing is allowed for full screen applications, that can help with those.
You can also try switching to Glamor (your card uses EXA for HW acceleration by default).
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Just a little question here. I recently installed [mesa-git] to have latest mesa and llvm packages (many thanks to lordheavy, they wouldn't compile on my machine) but I still face some issues. I've been advised here to use latest llvm and mesa-git to avoid VM issues, but I still get these errors. So I don't know if this is an issue of llvm not being *that* up to date or if I'm missing something (likely).
As a reminder: I have an R9 390 (grenada) with radeonsi, that should work as R9 290 since it is almost the same hardware (hawaii, which is what lspci shows for me).
Thanks.
That thread also mentions the need to use latest firmware from git, did you install those ?
I think Lordheavy updates the packages in mesa-git repo about once a week, but you can check builddates yourself here .
Since i'm the maintainer of AUR mesa-git (and build that and aur llvm-svn approx 2 times per week for my own systems ) : did you report your compile problems ?
Last edited by Lone_Wolf (2015-12-22 21:56:49)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Anything that attempt to use OpenGL (2 or 3.1) for compositing has the aforementioned artifacts and graphical glitches.
make sure compositing is allowed for full screen applications, that can help with those.
You can also try switching to Glamor (your card uses EXA for HW acceleration by default).
I'll try that and report back. Hopefully it'll work.
Offline
Lone_Wolf: The firmware-linux package in [testing] is from the same day that the Debian Sid's version, which works for me. Still, tomorrow I'm going to install firmware-git and try compiling again your packages from AUR. If I remember correctly, every core would just fail one by one aproximately at 85%. Maybe I should just build them with one thread to be sure? Thanks for your help, it's much appreciated
Edit: I didn't report anything about AUR package because I tried [mesa-git] afterwards. Tomorrow I'll do it.
Last edited by Jojonintendo (2015-12-22 22:30:16)
M/B: Asus M5A97 LE R2.0 CPU: AMD FX(tm)-6100 Six-Core Processor GPU: XFX R9 390 DD Black Edition RAM: Kingston HyperX Beast DDR3 1866 2X4GB SSD: Crucial M4 128GB SATA 3
CPU and GPU are watercooled by Ibercool kit.
Offline
Latest mesa-git fails to build with:
configure: error: Package requirements (libdrm_nouveau >= 2.4.66) were not met:
Requested 'libdrm_nouveau >= 2.4.66' but version of libdrm_nouveau is 2.4.65
As libdrm 2.4.66 hasn't been tagged or released yet, we'd need a libdrm-git package. Unfortunately such a package doesn't exist yet.
For non-nouveau users a temporary workaround is to remove nouveau from gallium-drivers & dri-drivers lines in the PKGBUILD
-------------------------
@jojonintendo : both aur mesa-git & llvm-svn build fine using multiple cores with makepkg.
In case you are using an aur helper (like yaourt) try building with makepkg.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Was futzing around with a few things in KDE and used 20-radeon.conf to enable glamor, and now when playing with the compositing settings I was able to get it working (I think) but not well. I have DRI3 and Glamor enabled through 20-radeon.conf and when I set the rendering backend to opengl 3.1 and the opengl interface to egl, everything looks OK but I can't seem to get any effects working, almost exactly like xrender.
EDIT: turns out that enabling DRI3 had disabled any compositing through EGL. I changed it to DRI2 and it was back to its...tricks.
Any ideas are welcome.
Last edited by sawyerbergeron (2015-12-23 00:16:33)
Offline
I've got a Radeon HD 8400 / R3 Series.
Catalyst nor xf86-video-ati seems to recognize it. Is there anything that does support this APU?
Offline