| Summary: | AMD Catalyst 15.101 for Fedora 22 with X.Org X11 Server 1.16 | ||
|---|---|---|---|
| Product: | Package Reviews | Reporter: | Linards <hx> |
| Component: | Review Request | Assignee: | RPM Fusion Package Review <rpmfusion-package-review> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | germano.massullo, leigh123linux, quanttek, rpmfusion-package-review, sergio |
| Priority: | P5 | ||
| Version: | Current | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| See Also: | https://bugzilla.rpmfusion.org/show_bug.cgi?id=3161 | ||
| namespace: | |||
|
Description
Linards
2015-06-10 08:34:05 CEST
Closed due to invalid format. http://rpmfusion.org/Contributors FYI rpmfusion no longer includes catalyst driver since F20 (no one at rpmfusion has any interest in maintaining it) so it would require a full review and someone to maintain it. http://cvs.rpmfusion.org/viewvc/rpms/xorg-x11-drv-catalyst/F-20/?root=nonfree (In reply to comment #2) > FYI rpmfusion no longer includes catalyst driver since F20 (no one at rpmfusion > has any interest in maintaining it) so it would require a full review and > someone to maintain it. > > > http://cvs.rpmfusion.org/viewvc/rpms/xorg-x11-drv-catalyst/F-20/?root=nonfree So you are saying that even if there is so,me pretty detailed guide, already made patches and some folks to consult with - no one is willing to put it all together .. its just feels like some standard build management on fedora builders ... koji, for example. Sound weird to me. (In reply to comment #3) > (In reply to comment #2) > > FYI rpmfusion no longer includes catalyst driver since F20 (no one at rpmfusion > > has any interest in maintaining it) so it would require a full review and > > someone to maintain it. > > > > > > http://cvs.rpmfusion.org/viewvc/rpms/xorg-x11-drv-catalyst/F-20/?root=nonfree > > So you are saying that even if there is so,me pretty detailed guide, already > made patches and some folks to consult with - no one is willing to put it all > together .. its just feels like some standard build management on fedora > builders ... koji, for example. > > Sound weird to me. No maintainer = no package The detailed guide you refer to is a total hack, downgrading Xorg isn't recommended. (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > FYI rpmfusion no longer includes catalyst driver since F20 (no one at rpmfusion > > > has any interest in maintaining it) so it would require a full review and > > > someone to maintain it. > > > > > > > > > http://cvs.rpmfusion.org/viewvc/rpms/xorg-x11-drv-catalyst/F-20/?root=nonfree > > > > So you are saying that even if there is so,me pretty detailed guide, already > > made patches and some folks to consult with - no one is willing to put it all > > together .. its just feels like some standard build management on fedora > > builders ... koji, for example. > > > > Sound weird to me. > No maintainer = no package > The detailed guide you refer to is a total hack, downgrading Xorg isn't > recommended. Oh, I see. Ok, thx for info, mate. (In reply to comment #3) > > So you are saying that even if there is so,me pretty detailed guide, already > made patches and some folks to consult with - no one is willing to put it all > together .. [...] Sound weird to me. That "detailed guide" tells users to downgrade their X-Server to the one from F21. That's weird IMHO and it's afaics nothing RPM Fusion does or should do. To me it feels like buying a new car model, ripping some important part out and replace it with that part from the previous model. (In reply to comment #6) > (In reply to comment #3) > > > > So you are saying that even if there is so,me pretty detailed guide, already > > made patches and some folks to consult with - no one is willing to put it all > > together .. [...] Sound weird to me. > > That "detailed guide" tells users to downgrade their X-Server to the one from > F21. That's weird IMHO and it's afaics nothing RPM Fusion does or should do. To > me it feels like buying a new car model, ripping some important part out and > replace it with that part from the previous model. Hi. Sorry, if this is not right way to do this, but here is new update: https://linardsliepins.wordpress.com/2015/06/23/amd-catalyst-15-3-finally-installable-on-fedora-22/ ... maybe you can put bits together and just for this one time make it built here or on COPR? I know FGLRX has no maintainer, but still mannyy people will be just crazy happy to be able to install it w/o tackling terminal... (In reply to comment #6) > (In reply to comment #3) > > > > So you are saying that even if there is so,me pretty detailed guide, already > > made patches and some folks to consult with - no one is willing to put it all > > together .. [...] Sound weird to me. > > That "detailed guide" tells users to downgrade their X-Server to the one from > F21. That's weird IMHO and it's afaics nothing RPM Fusion does or should do. To > me it feels like buying a new car model, ripping some important part out and > replace it with that part from the previous model. Hi. Sorry, if this is not right way to do this, but here is new update: https://linardsliepins.wordpress.com/2015/06/23/amd-catalyst-15-3-finally-installable-on-fedora-22/ ... maybe you can put bits together and just for this one time make it built here or on COPR? I know FGLRX has no maintainer, but still mannyy people will be just crazy happy to be able to install it w/o tackling terminal... Either shutup and leave this bug closed or submit a proper review request following the proper steps. http://rpmfusion.org/Contributors FYI the catalyst doesn't qualify for COPR as it's non-free! Leigh, please be more kind and refrain from telling people to "shut up." He may not know the proper way to create a package, but we can all help him out if he decides he wants to pick up the work. (In reply to comment #10) > Leigh, please be more kind and refrain from telling people to "shut up." He may > not know the proper way to create a package, but we can all help him out if he > decides he wants to pick up the work. Kindness isn't required now "shut up"! Here's a f22 repo you can try sudo dnf config-manager --add-repo=https://dl.dropboxusercontent.com/u/6907158/catalyst/catalyst.repo dnf install akmod-catalyst (In reply to comment #12) > Here's a f22 repo you can try > > > sudo dnf config-manager > --add-repo=https://dl.dropboxusercontent.com/u/6907158/catalyst/catalyst.repo > dnf install akmod-catalyst Note that I'm fine if you want to reintroduce it for f21 if it's worksforyour (not f22 as it will requires additional works from my side - but f22 users can grab from f21-nonfree). (In reply to comment #13) > (In reply to comment #12) > > Here's a f22 repo you can try > > > > > > sudo dnf config-manager > > --add-repo=https://dl.dropboxusercontent.com/u/6907158/catalyst/catalyst.repo > > dnf install akmod-catalyst > > Note that I'm fine if you want to reintroduce it for f21 if it's worksforyour > (not f22 as it will requires additional works from my side - but f22 users can > grab from f21-nonfree). It depends if feedback is positive on the dropbox repo as I haven't got the hardware to test it. I'm also reluctant to package catalyst as even it's latest release doesn't support kernel-4.0.0 without patching which doesn't bode well here. (In reply to comment #13) > (In reply to comment #12) > > Here's a f22 repo you can try > > > > > > sudo dnf config-manager > > --add-repo=https://dl.dropboxusercontent.com/u/6907158/catalyst/catalyst.repo > > dnf install akmod-catalyst > > Note that I'm fine if you want to reintroduce it for f21 if it's worksforyour > (not f22 as it will requires additional works from my side - but f22 users can > grab from f21-nonfree). Ok I have reintroduced it for F21 repo > but f22 users can grab from f21-nonfree).
Unfortunately with the latest update to 4.1.5, the kernel x86_64 4.1.5-100.fc21 got introduced as dependency, which means F22 users can't use this version anymore. Also it requires the removal of kernel x86_64 4.1.3-200.fc22, which is quite suprising.
It would be extremely helpful if you could make the dependency a bit more agnostic, so it works with F22 version like before.
Thanks :)
(In reply to comment #16) > > but f22 users can grab from f21-nonfree). > > Unfortunately with the latest update to 4.1.5, the kernel x86_64 4.1.5-100.fc21 > got introduced as dependency, which means F22 users can't use this version > anymore. Also it requires the removal of kernel x86_64 4.1.3-200.fc22, which is > quite suprising. akmod-catalyst has no such dep > > It would be extremely helpful if you could make the dependency a bit more > agnostic, so it works with F22 version like before. > > Thanks :) $ rpm -qp --requires akmod-catalyst-15.7-4.fc21.x86_64.rpm warning: akmod-catalyst-15.7-4.fc21.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID a668b376: NOKEY /bin/sh akmods catalyst-kmod-common >= 1:15.7 kmodtool rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 $ rpm -qp --provides akmod-catalyst-15.7-4.fc21.x86_64.rpm warning: akmod-catalyst-15.7-4.fc21.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID a668b376: NOKEY akmod-catalyst = 1:15.7-4.fc21 akmod-catalyst(x86-64) = 1:15.7-4.fc21 catalyst-kmod = 1:15.7-4.fc21 (In reply to comment #18) > $ rpm -qp --requires akmod-catalyst-15.7-4.fc21.x86_64.rpm > warning: akmod-catalyst-15.7-4.fc21.x86_64.rpm: Header V3 RSA/SHA256 Signature, > key ID a668b376: NOKEY > /bin/sh > akmods > catalyst-kmod-common >= 1:15.7 > kmodtool > rpmlib(CompressedFileNames) <= 3.0.4-1 > rpmlib(FileDigests) <= 4.6.0-1 > rpmlib(PayloadFilesHavePrefix) <= 4.0-1 > rpmlib(PayloadIsXz) <= 5.2-1 > > > > $ rpm -qp --provides akmod-catalyst-15.7-4.fc21.x86_64.rpm > warning: akmod-catalyst-15.7-4.fc21.x86_64.rpm: Header V3 RSA/SHA256 Signature, > key ID a668b376: NOKEY > akmod-catalyst = 1:15.7-4.fc21 > akmod-catalyst(x86-64) = 1:15.7-4.fc21 > catalyst-kmod = 1:15.7-4.fc21 Sorry, I got that a little bit wrong: While this query shows a dependency for a kernel version I don't have,... dnf repoquery --requires kmod-catalyst-4.1.5-100.fc21.x86_64 --releasever 21 Last metadata expiration check performed 0:05:15 ago on Mon Aug 24 23:23:23 2015. catalyst-kmod-common >= 1:15.7 kernel-uname-r = 4.1.5-100.fc21.x86_64 solvable:prereqmarker /bin/sh /usr/sbin/depmod ...I got into the problem because I tried to install the driver with the wrong command. I tried to dnf install xorg-x11-drv-catalyst --releasever 21, but I should have done dnf install akmod-catalyst --releasever 21. Thanks for the pointers Hi, any news? Catalyst driver is no longer maintained by amd |