The AMD/ATI Bar & Grill

kiodo1981 · 2015-11-27 17:48:54

spencer_brown wrote:

I've added the xorg1.17 repository, how do I install xorg-server 1.17?

You have to put it before the others.

Jannis · 2015-11-28 05:51:57

spencer_brown wrote:

I've added the xorg1.17 repository, how do I install xorg-server 1.17?

after you've added the repo before the others in pacman.conf, just do a

# pacman -Syyuu

-yy forces a refresh of cached repo databases (probably don't even need this),
-uu enables downgrades if repo version of a package is older than locally installed package.

DarksideEE7 · 2015-11-29 20:47:22

So should we still use linux-lts with catalyst-hook-15.11-1 (and other related catalyst packages...)? I haven't upgraded in a while, so it's time for a hail mary pacman -Syu...

Total Download Size: 1536.82 MiB
Total Installed Size: 5360.30 MiB
Net Upgrade Size: 155.97 MiB

Let's see what gets broken...

EDIT:

Looks like I can boot just fine with the normal kernel. So far so good.

Last edited by DarksideEE7 (2015-11-29 22:56:49)

turtlepleasure · 2015-11-30 02:18:18

Will 15.11 be moved to stable (catalyst-total) soon? Don't really feel like dealing with the gcc49 dependency on 15.9-6 (currently on 15.9-2).

Vi0L0 · 2015-12-01 10:58:39

turtlepleasure wrote:

Will 15.11 be moved to stable (catalyst-total) soon?

Depends on the tests. I didn't get many reports so its hard to me to decide, aspecially after getting news about windows' crimson edition poor fan control (and so higher temperatures on gpu).
I will test till Sunday and if everything will be "fine" and I won't get negative reports/comments then I will move it to stable.

turtlepleasure · 2015-12-01 16:03:55

Sounds good, thanks for the reply!

And thanks for all you do with maintaining these packages, sincerely.

clfarron4 · 2015-12-01 21:12:11

I just read this on Anandtech

Anandtech wrote:

Overall this means that the entire Radeon HD 5000 and 6000 series have been retired. So have the Radeon HD 7000 to 7600 parts, and the Radeon HD 8000 to 8400 parts.

So, if you're doing a [hd56k], it's going to cover a bit more than just 5000 and 6000 series?

Vi0L0 · 2015-12-01 21:29:58

clfarron4 wrote:

So, if you're doing a [hd56k], it's going to cover a bit more than just 5000 and 6000 series?

Yes. Putting 7 into the repo name would be a lie, since radeon hd > 7700 is gcn and so is still supported.
Naming repo as pregcn would misslead hd234k users, as their hardware is also pregcn but would not be supported by the repo.
Leaves hd56k, but I'm ready for other propositions.

Some hd 5 6 k users said that they have no problems with newest crimson drivers, others claimed to bring working solution - so the news about dropped support is not that clear, looks more like for now it's not as dropped/locked as hd234k. Anyhow creating the repo would probably be a good idea.

BTW: Tear Free desktop with Tear Free option disabled @ plasma DE with compositing enabled
Enabling Tear Free option in amdcccle always had negative inpact on de performance (no matter if any kind of vsync was disabled).
But on plasma desktop its possible to have Tear/Flicker free screen without enabling Tear Free option.
Here are the steps:
1. on amdcccle: enable Tear Free + set vsync to always on. Press OK to save the changes.
2. reboot system
3. on amdccle disable Tear Free (and leave vsync to always on) - setting it without rebooting doesnt work for me
4. profit - no tearing/flickering, and desktop working on high speed, without any kind of negative impact
edit: also you can leave plasma's built-in vsync option disabled
Did someone notice it/can confirm?

Last edited by Vi0L0 (2015-12-02 08:23:11)

Jannis · 2015-12-04 20:01:59

Vi0L0 wrote:

BTW: Tear Free desktop with Tear Free option disabled @ plasma DE with compositing enabled
Enabling Tear Free option in amdcccle always had negative inpact on de performance (no matter if any kind of vsync was disabled).
But on plasma desktop its possible to have Tear/Flicker free screen without enabling Tear Free option.
Here are the steps:
1. on amdcccle: enable Tear Free + set vsync to always on. Press OK to save the changes.
2. reboot system
3. on amdccle disable Tear Free (and leave vsync to always on) - setting it without rebooting doesnt work for me
4. profit - no tearing/flickering, and desktop working on high speed, without any kind of negative impact
edit: also you can leave plasma's built-in vsync option disabled
Did someone notice it/can confirm?

My results in Plasma 5 with Catalyst Crimson 15.11 and KWin 5.4.3 (build-in vsync set to "never") on a Radeon HD 7870:

With compositing, desktop usage:
Works as expected on my primary monitor but exactly one tear on my secondary, slowly moving in position from top to bottom.

With compositing, in game TF2:
Exactly one tear in the upper third of the screen, framerate locked to 60 and drops more often than it did with tear free on and vsync off.

Without compositing, desktop usage:
Horrible tearing everywhere.

Without compositing, in game TF2:
No tearing, framerate locket at 60, drops often.

With the previous workaround of enabling tear free and then disabling vsync everywhere, composited desktop performance is slightly choppier but no tearing anywhere and when in-game in TF2 without compositing (disabled for gaming), framerate isn't locked to 60 and stays above 60 most of the time with much fewer drops, no tearing and subjectively less output delay (aka input lag).

P.S.: I'll certainly buy a FreeSync compatible monitor and gfx card next time.

Vi0L0 · 2015-12-04 20:35:39

Jannis wrote:

P.S.: I'll certainly buy a FreeSync compatible monitor and gfx card next time.

Same here. Thanks for detailed report .

Jannis · 2015-12-04 20:57:51

Vi0L0 wrote:

Jannis wrote:
P.S.: I'll certainly buy a FreeSync compatible monitor and gfx card next time.
Same here. Thanks for detailed report .

No problem. And about FreeSync: After having mentioned it, I did some research but couldn't find out if Crimson even supports it on linux. Does anyone know this? And do the open drivers support VESA Adaptive-Sync?

EremiticWolf · 2015-12-07 03:47:23

Please disregard I can not figure out how to delete this post.

Last edited by EremiticWolf (2015-12-07 04:53:35)

Amanda S · 2015-12-07 09:45:56

Vi0L0 wrote:

Amarildo wrote:
Hi Vi0l0. Have you had time to check why Catalyst can't build it's modules on linux-grsec?
Thanks.
I started work on grsec but had no time to finish as other bugs were more important. Now grsec is 1st on the catalyst list.
We still have problems with 4.2 kernel (hope AMD will solve it soon as ubuntu 15.10 should be released within days), so I'm going to work on 4.1 (yes, there's grsec-4.2 already on arch repos, I know).

So, how is it going?

d00maz · 2015-12-08 17:42:19

how's the new catalyst-test aka crimson? Any comparisons to OS driver + mesa?
Atm im using the OS + mesa combo and i'm happy with it.(it's better than the previous catalyst).

Last edited by d00maz (2015-12-08 17:54:08)

sawyerbergeron · 2015-12-09 03:10:16

I have a FirePro v4800, who's radeon equivalent is the HD5670. When I originally installed from the latest in the repo, it was saying that it was dropping support for 5xxx and 6xxx series cards, and when I tried to run aticonfig --initial it spat back at me that no supported adapters are detected. Any help?

jasonwryan · 2015-12-09 03:14:02

sawyerbergeron wrote:

I have a FirePro v4800, who's radeon equivalent is the HD5670. When I originally installed from the latest in the repo, it was saying that it was dropping support for 5xxx and 6xxx series cards, and when I tried to run aticonfig --initial it spat back at me that no supported adapters are detected. Any help?

Antgeros is a separate distribution, ask on their boards, we only support Arch: https://wiki.archlinux.org/index.php/Fo … pport_ONLY

sawyerbergeron · 2015-12-09 11:45:39

jasonwryan wrote:

sawyerbergeron wrote:
I have a FirePro v4800, who's radeon equivalent is the HD5670. When I originally installed from the latest in the repo, it was saying that it was dropping support for 5xxx and 6xxx series cards, and when I tried to run aticonfig --initial it spat back at me that no supported adapters are detected. Any help?
Antgeros is a separate distribution, ask on their boards, we only support Arch: https://wiki.archlinux.org/index.php/Fo … pport_ONLY

OK, so install standard Arch and check back here? As I've asked a couple times there and there's just no one there that really seems to know how to deal with Catalyst. Great forum there but just doesn't have this niche filled.
Sorry to appear rude, I'm slightly more used to dealing with the Ubuntu crowd as that's what I used before this.

AnnS · 2015-12-10 17:55:53

sawyerbergeron wrote:

I have a FirePro v4800, who's radeon equivalent is the HD5670. When I originally installed from the latest in the repo, it was saying that it was dropping support for 5xxx and 6xxx series cards, and when I tried to run aticonfig --initial it spat back at me that no supported adapters are detected. Any help?

It's the same for me. I have a 6550M and everything (even Catalyst Control Center) is working fine, but since the latest update aticonfig just doesn't work, it says "no supported adapters are detected". I know AMD dropped support for these cards, but this update (15.11) is compatible, right? Since everything seems normal, I haven't been paying too much attention to it, but is there anything I can do? I like to keep the temperature monitored but now it's not possible.

spencer_brown · 2015-12-11 16:55:42

Just a quick question. Its my first time installing the catalyst drivers. After installing all the packages from viol0's repository, all I have to do to configure X is to do

aticonfig --initial --output

?
After that, I then do the boot modules thing mentioned in the wiki and disable modesetting?
Is that it? I just wanted to make sure before I actually install and do this. Also, I'm assuming I should use catalyst-stable? Or is that wrong. I saw something somewhere about needing to use an LTS kernel, but didnt see that on the wiki. Please let me know if I've missed anything.

ChemBro · 2015-12-11 21:28:29

Disable Modesetting and you're good to go. Well let's say, you should be good to go. :-)

spencer_brown · 2015-12-12 04:05:23

OK, so I am a little bit confused.
I did

aticonfig --initial --output

and it returned this

aticonfig: option '--output' requires an argument
aticonfig: parsing the command-line failed.

From this it seems that after output I need to put the location for the xorg.conf? This is in the wiki but didnt seem so clear. Is this what I am supposed to put

/etc/X11/xorg.conf.d/20-radeon.conf

or

/etc/X11/xorg.conf

and do i do --initial and --output in the same command? I'm not sure what the wiki note in this section means. This is the last thing I still have to figure everything out.
Sorry to be so needy and thanks for your time.

Last edited by spencer_brown (2015-12-12 04:28:11)

bosyi · 2015-12-12 10:12:09

aticonfig --initial
should be enough.

spencer_brown · 2015-12-12 15:12:36

OK I've finished doing all the installation, and now I have some errors I need to try and figure out.
I have a Radeon R9 255 and installed using the [catalyst] and [xorg117] repositories.
This is the output of

fglrxinfo

Error: unable to open display (null)

This is the output of

grep '(EE)' /var/log/Xorg.0.log

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    98.464] (EE) AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[   133.970] (EE) systemd-logind: failed to release device: Connection was disconnected before a reply was received
[   133.970] (EE) systemd-logind: failed to release device: Connection is closed
[   133.970] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.988] (EE) systemd-logind: ReleaseControl failed: Connection is closed

And now the output of

grep '(WW)' /var/log/Xorg.0.log

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    96.098] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    96.098] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    96.113] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    96.284] (WW) Falling back to old probe method for fglrx
[    96.699] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:0) found
[    96.700] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:1) found
[    96.700] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[    96.746] (WW) fglrx(0): board is an unknown third party board, chipset is supported
[    96.747] (WW) fglrx(0): board is an unknown third party board, chipset is supported
[    97.486] (WW) fglrx(0): Option "VendorName" is not used
[    97.486] (WW) fglrx(0): Option "ModelName" is not used
[    99.386] (WW) evdev: Lenovo Black Silk USB Keyboard: ignoring absolute axes.
[   133.988] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[   133.988] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[   133.988] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error

I tried doing this from the wiki

# mkdir -p /usr/X11R6/lib64/modules/dri
# ln -s /usr/lib/xorg/modules/dri/fglrx_dri.so /usr/X11R6/lib64/modules/dri/fglrx_dri.so

but fglrxinfo still outputs ERROR: (null)
Now the

grep '(EE)' /var/log/Xorg.0.log

outputs

	
[   133.970] (EE) systemd-logind: failed to release device: Connection was disconnected before a reply was received
[   133.970] (EE) systemd-logind: failed to release device: Connection is closed
[   133.970] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.971] (EE) systemd-logind: failed to release device: Connection is closed
[   133.988] (EE) systemd-logind: ReleaseControl failed: Connection is closed

Without the falied to open fglrx_dri.so error.
From the Open ACPI Failed warning I think I might need to do this command from the wiki?

aticonfig --acpi-services=off

--EDIT--
I did this command and installed acpi and acpid. I then enabled acpid in systemd. The Open ACPI warning is no longer there.
There are now no Errors in

grep '(EE)' /var/log/Xorg.0.log

but the

grep '(WW)' /var/log/Xorg.0.log

still looks the same except for the ACPI error being gone. And I still get a black screen when starting sddm, and startx still hangs. Any help would be apreciated. I've done all I can figure out how to do.

Last edited by spencer_brown (2015-12-12 17:58:55)

spencer_brown · 2015-12-12 20:33:57

I just wanted to say I figured it out and its working now. I was looking at the output of lspci | grep VGA.
I knew I had two AMD devices. An integrated R7 that I dont use/have connected to my moniter, and a Radeon R9 255 discreet card.
The Bus for my R7 is 0:01.0
The bus for my R9(that I use) is 1:00.0
The device bus listed in the auto generated xorg.conf was 0.1.0.
Just out of desperation I tried changing the first 0 and the 1.
Xorg will now start. I can only assume, with my limited knowledge, that the graphic output was being sent to the non-connected device.
Kinda proud of myself, mostly relieved.

Vi0L0 · 2015-12-13 13:54:13

Sorry, latelly i had to focus on other projects...
I'm still not that sure is moving crimson to [catalyst-stable] the best idea. I took AMD's code from 15.11 and applied on 15.9 and now we don't need this gcc4.9 anymore - soon (after playing with grsec) I will apply it into packages.
So now 15.9 is mainly missing proper tty support (but it can be fixed by uvesa), while 15.11 is missing radeons 5 6 k support.
The crimson move has to be done sometime, but is this the right moment? I don't know. Somehow I don't feel it.

Edit: some acisc were removed from fglrxko_pci_ids.h header, wondering if bringin them back and probably modifying control file could bring hd 5 6 k support back to crimson driver... gimme some time, will prepare source file for potential testers (cant test it on my own, dont have proper gfx)

Amarildo wrote:

Vi0L0 wrote:
Amarildo wrote:
Hi Vi0l0. Have you had time to check why Catalyst can't build it's modules on linux-grsec?
Thanks.
I started work on grsec but had no time to finish as other bugs were more important. Now grsec is 1st on the catalyst list.
We still have problems with 4.2 kernel (hope AMD will solve it soon as ubuntu 15.10 should be released within days), so I'm going to work on 4.1 (yes, there's grsec-4.2 already on arch repos, I know).
So, how is it going?

Here is the source file of catalyst-grsec package: http://catalyst.wirephire.com/tarball/catalyst-grsec/
The bad side is that it has to be build on booted grsec kernel, if you want i can also give you catalyst-hook source but it will build modules only for grsec kernel...
For now it's kinda dirty and 15.9 only (but it works with gcc 5), in a free time (could be not that soon) I will try to modify it and add to main catalyst packages.
Tested on current community 4.2.7 grsec kernel, with kernel.grsecurity.harden_ipc set to 0, as it was the most easy and noobish solution to get rid of 'denied write of overly-permissive IPC object' error ;P
Edit: ok, got working grsec build-in into standard catalys-hook 15.9 package, will release it soon to stable repo and aur
So to summarize: there will be 2 big 15.9 updates today in stable repo, while none of them was tested by the community (cross your fingers)... don't like it, but catalyst-test is already owned by 15.11

edit2: on i686 im getting error while building fglrx module for community's grsec kernel:
cc1: error: fail to initialize plugin ./tools/gcc/size_overflow_plugin/size_overflow_plugin.so
somehow i feel that it will be gone after compiling linux-grsec from the ground - edit3: hehe, was right , compiling linux-grsec without changing a thing in config or anything fixed the problem, probably i686 community linux-grsec build should be fixed

Ok, so just to clarify:
[catalyst-stable] repo still has 15.9 but has been upgraded:
- gcc49 was removed, you can remove it as wel,
- new catalyst-hook and catalyst-generator packages contains new patches from crimson 15.11, also initial grsec kernel support has been added,
- catalyst pkg was removed, you should switch to catalyst-hook or catalyst-generator
Also AUR's catalyst, catalyst-generator and catalyst-hook were updated in same way.

There's also archive repository in case of problems:
[catalyst-stable-15.9-gcc49]
Server = http://mirror.rts-informatique.fr/archl … lyst/$arch
Server = http://catalyst.wirephire.com/repo/catalyst/$arch

Last edited by Vi0L0 (2015-12-13 22:10:05)

Arch Linux

#7226 2015-11-27 17:48:54

Re: The AMD/ATI Bar & Grill

#7227 2015-11-28 05:51:57

Re: The AMD/ATI Bar & Grill

#7228 2015-11-29 20:47:22

Re: The AMD/ATI Bar & Grill

#7229 2015-11-30 02:18:18

Re: The AMD/ATI Bar & Grill

#7230 2015-12-01 10:58:39

Re: The AMD/ATI Bar & Grill

#7231 2015-12-01 16:03:55

Re: The AMD/ATI Bar & Grill

#7232 2015-12-01 21:12:11

Re: The AMD/ATI Bar & Grill

#7233 2015-12-01 21:29:58

Re: The AMD/ATI Bar & Grill

#7234 2015-12-04 20:01:59

Re: The AMD/ATI Bar & Grill

#7235 2015-12-04 20:35:39

Re: The AMD/ATI Bar & Grill

#7236 2015-12-04 20:57:51

Re: The AMD/ATI Bar & Grill

#7237 2015-12-07 03:47:23

Re: The AMD/ATI Bar & Grill

#7238 2015-12-07 09:45:56

Re: The AMD/ATI Bar & Grill

#7239 2015-12-08 17:42:19

Re: The AMD/ATI Bar & Grill

#7240 2015-12-09 03:10:16

Re: The AMD/ATI Bar & Grill

#7241 2015-12-09 03:14:02

Re: The AMD/ATI Bar & Grill

#7242 2015-12-09 11:45:39

Re: The AMD/ATI Bar & Grill

#7243 2015-12-10 17:55:53

Re: The AMD/ATI Bar & Grill

#7244 2015-12-11 16:55:42

Re: The AMD/ATI Bar & Grill

#7245 2015-12-11 21:28:29

Re: The AMD/ATI Bar & Grill

#7246 2015-12-12 04:05:23

Re: The AMD/ATI Bar & Grill

#7247 2015-12-12 10:12:09

Re: The AMD/ATI Bar & Grill

#7248 2015-12-12 15:12:36

Re: The AMD/ATI Bar & Grill

#7249 2015-12-12 20:33:57

Re: The AMD/ATI Bar & Grill

#7250 2015-12-13 13:54:13

Re: The AMD/ATI Bar & Grill

Board footer