You are not logged in.
Does anyone know how to enable tear-free on Radeon? Google taught me it is supported but I'm not sure what is the correct way to enable it. Can you tell me?
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Option "EXAVSync" "yes"
Reduced the tearing for me.
Or it was just a placebo.
'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard
Offline
Option "EXAVSync" "yes"
Reduced the tearing for me.
Or it was just a placebo.
Yes, 'man radeon' gives some tips.
Offline
Thanks guys, I will take a look at the manpage!
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Now llvm from my mesa-git is llvm-3.3svn (llvm-amdgpu-svn). If you want llvm from tstellar's repo, just grab llvm-amdgpu-snapshot from community.
Well, mesa didn't build for me with the one from community today (perhaps it was only --enable-opencl, didn't look) while with your 3.3 it works fine. But it's really huge. Is it necessary to have it with debugging stuff enabled?
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
lordheavy wrote:Now llvm from my mesa-git is llvm-3.3svn (llvm-amdgpu-svn). If you want llvm from tstellar's repo, just grab llvm-amdgpu-snapshot from community.
Well, mesa didn't build for me with the one from community today (perhaps it was only --enable-opencl, didn't look) while with your 3.3 it works fine. But it's really huge. Is it necessary to have it with debugging stuff enabled?
* mesa from the git trunk needs llvm-3.3svn at least, mesa from 9.1.x branch needs llvm from tstellar repo (llvm-amdgpu-snapshot in community)
* debugging symbols are stripped from llvm-amdgpu-svn packages.
Offline
Ah sorry, I misread something there and assumed it would have debugging enabled because of something with the size without checking the pkgbuild. I'm too tired today.
Last edited by Cdh (2013-03-11 23:26:08)
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
I feel a bit of clarifying is needed, so i'll try.
Llvm 3.3 will have the amdgpu backend code included, and The code by tom stellar was added to llvm master trunk a few days ago.
Mesa master git switched from tstellar out-of-tree code to llvm svn master trunk.
So any GIT package that used llvm-amdgpu-git has to switch to an llvm-amdgpu-svn package .
Currently there are 2 choices for llvm-amdgpu-svn and lib32-llvm-amdgpu-svn :
1. aur packages maintained by me
https://aur.archlinux.org/packages/llvm-amdgpu-svn/
https://aur.archlinux.org/packages/lib3 … mdgpu-svn/
2.
Lordheavy's repo on pkgbuild.com
http://pkgbuild.com/~lcarlier/mesa-git/sources/
I've peeked at lordheavy's sources and while there are many similarities they are not identical.
For those that need help, want to report a bug something make clear which packages you are using !
I'll look deeper into the differences later this week.
-----------------------------------------------------------------------------------
about sizes of the llvm packages :
My llvm-amdgpu-svn is 19.2 Mib (x86_64) download size, the lib32- package has 16 Mib .
Lordheavy's packages are similar in size.
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
I did a reinstall of Arch recently and am having a problem I've never had before.
When I try to start an X server with the 'X' command, all I get is a black screen. Computer still responds to input since I can still change virtual terminals. No errors in the output of the command and nothing out of the ordinary in Xorg.0.log (radeon seems to load and configure perfectly fine). I have no custom configurations done for X -- everything is as it is after initial install. Using the packages in the official repo. Ideas?
Offline
I did a reinstall of Arch recently and am having a problem I've never had before.
When I try to start an X server with the 'X' command, all I get is a black screen. Computer still responds to input since I can still change virtual terminals. No errors in the output of the command and nothing out of the ordinary in Xorg.0.log (radeon seems to load and configure perfectly fine). I have no custom configurations done for X -- everything is as it is after initial install. Using the packages in the official repo. Ideas?
Probably need more details. What DE are you trying to run? Are you starting it with systemd?
Offline
Hamsterkill wrote:I did a reinstall of Arch recently and am having a problem I've never had before.
When I try to start an X server with the 'X' command, all I get is a black screen. Computer still responds to input since I can still change virtual terminals. No errors in the output of the command and nothing out of the ordinary in Xorg.0.log (radeon seems to load and configure perfectly fine). I have no custom configurations done for X -- everything is as it is after initial install. Using the packages in the official repo. Ideas?
Probably need more details. What DE are you trying to run? Are you starting it with systemd?
Not trying to run a DE yet. Starting it by command line (# X). Just trying to get the test X environment to show that display and mouse are working before I try to set up a DE.
Last edited by Hamsterkill (2013-03-12 22:18:13)
Offline
Not trying to run a DE yet. Starting it by command line (# X). Just trying to get the test X environment to show that display and mouse are working before I try to set up a DE.
It isn't related to radeon driver, you prabably missed to install some xorg related packages (or configuring some files).
Offline
X alone doesn't display anything.
Just install xorg-xinit and openbox, create a ~/.xinitrc und put
exec /usr/bin/openbox-session
in there and use startx.
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
X alone doesn't display anything.
Just install xorg-xinit and openbox, create a ~/.xinitrc und put
exec /usr/bin/openbox-session
in there and use startx.
Well, there's no need for openbox or messing with xinitrc, but this helped. I was under the impression that X and startx did the same thing and that's apparently not the case. All I had to do was run startx to see the test display I was expecting. Thanks.
Offline
Hm. I was trying PRIME and saw that there was a new llvm in the the repository: http://pkgbuild.com/~lcarlier/mesa-git/ … pkg.tar.xz
So I installed it and recompiled mesa but with glxgears I get
LLVM ERROR: Cannot select: target intrinsic %llvm.SI.load.const
Is it just me?
Last edited by Cdh (2013-03-21 10:08:33)
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
Using my own aur packages glxgears runs normally on a HD 4890 / R600 driver.
Versions :
mesa-r300-r600-radeonsi-git version 20130320-1
llvm-amdgpu-svn 177498 .
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
No problems here with radeon 6870HD
Your problem seems related to the radeonsi driver. I will update my repo with latest llvm-svn and mesa, just check if it fix your problem, otherwise don't hesitate to fill a bug report on freedesktop.org, or ask on irc in the #radeon channel
Last edited by lordheavy (2013-03-21 12:10:00)
Offline
Hm. I was trying PRIME and saw that there was a new llvm in the the repository: http://pkgbuild.com/~lcarlier/mesa-git/ … pkg.tar.xz
So I installed it and recompiled mesa but with glxgears I getLLVM ERROR: Cannot select: target intrinsic %llvm.SI.load.const
Is it just me?
This intrinsic is implemented here http://llvm.org/viewvc/llvm-project?vie … ion=177273
An updated llvm-svn should fix it, it will be available soon in my repo.
Offline
Thanks, this works.
I also tried the llvm amdgpu git version from aur but it with that mesa didn't compile...
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
Thanks, this works.
I also tried the llvm amdgpu git version from aur but it with that mesa didn't compile...
Yes, llvm amdgpu git is only for mesa 9.1.x branch, it won't work with master branch
Offline
Would it be possible for you to build clang with it? If you want to compile mesa with --enable-opencl you need libclc and building libclc requires clang...
I'm not sure if it should work already, probably not, but it would be nice to be able to compile it at least.
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
Would it be possible for you to build clang with it? If you want to compile mesa with --enable-opencl you need libclc and building libclc requires clang...
I'm not sure if it should work already, probably not, but it would be nice to be able to compile it at least.
I was thinking the same when i created the aur llvm-amdgpu-svn package.
There are workarounds to have a split package in aur and --enable-opencl is one of the few experimental flags my aur mesa git packages don't use yet.
I hope to have time to add llvm-ocaml-svn , clang-svn and clang-analyzer-svn sometime next week.
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
Hi!
I'm new in ATI open driver - earlier I was used amd proprietary driver(for some strange reasons i decided change it).
I think everything is ok, but:
My laptop is very noisy because of this driver, earlier even if was loud for some time - returning for tolerable value of noise.
I check temperature by lm-sensor and this what i showing:
# sensors
radeon-pci-0200
Adapter: PCI adapter
temp1: +78.0°C
acpitz-virtual-0
Adapter: Virtual device
temp1: +26.8°C (crit = +100.0°C)
temp2: +0.0°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +54.0°C (high = +95.0°C, crit = +105.0°C)
Core 2: +49.0°C (high = +95.0°C, crit = +105.0°C)
For me is very bad temperature when computer is idle(only two cards in chrome).
My card is Radeon HD5400 series(but i really don't know how model exactly).
Someone can help or explain me this situation?
EDIT:
Oh, and second issue:
I have set KMS early start. It's normal if that screen "flashing" before something starts boot? Without KMS i didn't say anything like this.
Last edited by xorgx3 (2013-04-02 18:27:31)
Offline
the proprietary driver is much better in power management then the open driver, but you can tweak some settings.
check the ati page on the wiki page here : https://wiki.archlinux.org/index.php/Radeon#Powersaving
for your 2nd question :
there should be no flashing with kms early start, unless you mean the switch from text mode to native resolution when KMS kicks in.
Does the text look smaller after the 'flash' then just before ?
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
Yea, probably I thought about "switch from text mode to native resolution when KMS kicks in" but i didn't know how it calls(anyway this is little annoying).
I'll try do something with this powersaving.
Another problem is 3D games, but this is not important for now.
EDIT:
If i used mesa-git repo my 32bit folder isn't in: /usr/lib32/xorg/modules/dri/ place. Because of them i have a little trouble: https://bbs.archlinux.org/viewtopic.php?id=160767
and I have remove this repo. This is bug or future?
Last edited by xorgx3 (2013-04-03 10:42:27)
Offline