Package Details: catalyst-firepro 15.201.2401-2

Git Clone URL: https://aur.archlinux.org/catalyst-firepro.git (read-only)
Package Base: catalyst-firepro
Description: AMD/ATI beta drivers for FirePro/GL/MV brand cards. catalyst-hook + catalyst-utils + lib32-catalyst-utils + experimental powerXpress suppport.
Upstream URL: http://www.amd.com
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-hook, catalyst-utils, libcl, libgl, mesa-libgl, mesa-libgl-git
Provides: catalyst=15.201.2401, catalyst-hook=15.201.2401, catalyst-libgl=15.201.2401, catalyst-utils=15.201.2401, dri, libatical=15.201.2401, libcl, libgl, libtxc_dxtn, mesa-libgl, mesa-libgl-git
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 5
Popularity: 0.080456
First Submitted: 2011-01-25 17:19
Last Updated: 2016-03-23 18:55

Dependencies (22)

Required by (635)

Sources (31)

  • 4.2-amd-from_crimson_15.11.patch
  • 4.3-gentoo-mtrr.patch
  • 4.3-kolasa-seq_printf.patch
  • 4.4-manjaro-xstate.patch
  • a-ac-aticonfig
  • a-lid-aticonfig
  • arch-fglrx-authatieventsd_new.patch
  • ati-powermode.sh
  • atieventsd.service
  • atieventsd.sh
  • ati_make.sh
  • catalyst-hook.service
  • catalyst.conf
  • catalyst.sh
  • catalyst_build_module
  • cold-fglrx-3.14-current_euid.patch
  • crimson_i686_xg.patch
  • fglrx_gpl_symbol.patch
  • grsec_arch.patch
  • hook-fglrx
  • http://www2.ati.com/drivers/firepro/15.201.2401-linux-retail_end_user.zip
  • lano1106_fglrx-13.8_proc.patch
  • lano1106_fglrx_intel_iommu.patch
  • lano1106_kcl_agp_13_4.patch
  • lib32-catalyst.sh
  • makefile_compat.patch
  • pxp_switch_catalyst
  • switchlibGL
  • switchlibglx
  • temp-links-catalyst.service
  • temp_links_catalyst

Latest Comments

Malekeith commented on 2015-12-28 08:12

@Vi0L0

I've fix the problem, it wasn't GDM making the drivers unable to display.

It was actually xorg, interfering with the installation process. Since every time, I killed xorg with pkill x and re-installed drivers, the next time they boot up it works fine.

the only problem now is, reinstalling the driver every time xorg fails. Well not really a big problem, since I can actually use gdm now

Well, thanks Vi0l0

Vi0L0 commented on 2015-12-26 21:34

Packages are pretty old, from stable repos ie:
gnome-shell 3.18.3-1
gdm 3.18.2-1
clutter 1.24.2-1

Malekeith commented on 2015-12-26 20:59

I've tried a fresh arch installation with Gnome running "gdm 3.18.2-1" and "wayland 1.9.0-1". I'm still currently unsure to why I can't boot up GDM login screen.

Vi0L0, what was the version of GNOME that you tested on ? I tried disabling wayland, and defaulted back to xorg, it got the login screen working, but after logging in it hangs at a grey screen which will not fade away.

EDIT : "ctrl + alt + f2 / f1" skipped the grey screen and made most of GNOMEs, functionality work but at a cost of my gfx getting quite toasty

Vi0L0 commented on 2015-12-25 15:57

No, leave it as is, it's perfectly fine. Just wanted to confirm you have it installed.

Malekeith commented on 2015-12-25 15:53

I'm currently using the one you linked in the comments, should I remove ?

Vi0L0 commented on 2015-12-25 15:19

But you are using patched cogl package (available ie in the [catalyst] repo)? Just checking

Malekeith commented on 2015-12-25 13:31

it works quite fine for the most part, aticonfig --initial and fglrxinfo works fine too. Since, my W8100 got detected

fglrxinfo:
http://pastebin.com/FLdgU2cD

aticonfig --initial:
http://pastebin.com/zAhRt0Ey

xorg:
http://pastebin.com/AEqabEKz

I added "nomodeset" on the bootloader side, and by default using aticonfig made the "/etc/modules-load.d/catalyst.conf" which has "fglrx"

Practically followed the instructions from the wikipage :https://wiki.archlinux.org/index.php/AMD_Catalyst#Configuring_the_driver

Vi0L0 commented on 2015-12-25 11:46

both gnome and gdm works fine here.
What do you mean by `accessing catalyst`? Does aticonfig work fine, can it detect your gpu ie when running `aticonfig --initial`? Whats your gfx? Was fglrx module build correctly?

Malekeith commented on 2015-12-25 11:31

It seems like GDM failed to start after I installed the latest updated drivers.

"linux gdm-launch-environment][494]: pam_systemd(gdm-launch-environment:session): Failed to create session: Resource deadlock avoided"

logging in and using startx helped override gdm. Do you know a fix ? or any method around, since even gnome seems to be acting all wonky

edit : catalyst not functioning, was because of qt4.

other errors, including gdm not working and most of the default desktop environment functions not responding

Vi0L0 commented on 2015-12-23 18:02

thanks JSpaces, updated to 15.201.2401:
- it's like 15.9 but better[1]
- by default it supports up to 4.2 and xserver 1.17
- with community patches up to 4.4 kernel, should also work with grsec kernel

[1]Looks like this driver is the first catalyst one with which my plasma 5.x glitches[2] are gone! :D Had to make some additional testing but definitelly none of the drivers get that far.

[2]http://ati.cchtml.com/show_bug.cgi?id=1182

EDIT: ah, no, looks like it was a coincidence and it was fixed in plasma 5.5.2! :D even better!

All comments