Red Hat Bugzilla – Bug 505145
include also AMD ucode
Last modified: 2010-01-18 11:27:11 EST
get it from http://www.amd64.org/support/microcode.html
I don't believe we can redistribute it, because they don't grant the right to redistribute explicitly, and it's all rights reserved. I'll subscribe spot to this bug to review the legal text in case I am wrong.
I'll poke someone to poke someone at AMD to see if we can get this sorted out.
; Copyright 2008, ADVANCED MICRO DEVICES, INC. All Rights Reserved.
; AMD is granting you permission to use this Microcode Patch software
; internally in object code form only (the "Materials"), subject to the
; following terms and conditions. Your use of any portion of the Materials
; shall constitute your acceptance of the following terms and conditions. If
; you do not agree to the following terms and conditions, please do not use or
; retain any portion of the Materials.
; LIMITATION OF LIABILITY: THE MATERIALS ARE PROVIDED "AS IS" WITHOUT ANY
; EXPRESS OR IMPLIED WARRANTY OF ANY KIND, INCLUDING BUT NOT LIMITED TO
; WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, TITLE, FITNESS FOR ANY
; PARTICULAR PURPOSE, OR WARRANTIES ARISING FROM CONDUCT, COURSE OF DEALING,
; OR USAGE OF TRADE. IN NO EVENT SHALL AMD OR ITS LICENSORS BE LIABLE FOR ANY
; DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF
; PROFITS, BUSINESS INTERRUPTION, OR LOSS OF DATA OR INFORMATION) ARISING OUT
; OF AMD'S NEGLIGENCE, GROSS NEGLIGENCE, THE USE OF OR INABILITY TO USE THE
; MATERIALS, EVEN IF AMD HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
; BECAUSE SOME JURISDICTIONS PROHIBIT THE EXCLUSION OR LIMITATION OF LIABILITY
; FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR THE EXCLUSION OF IMPLIED
; WARRANTIES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
; AMD does not assume any responsibility for any errors which may appear in
; the Materials or result from use of the Materials.
; You agree that you will not reverse engineer or decompile the Materials.
; NO SUPPORT OBLIGATION: AMD is not obligated to furnish, support, or make any
; further information, software, technical information, know-how, or show-how
; available to you. Additionally, AMD retains the right to modify the
; Materials at any time, without notice, and is not obligated to provide such
; modified Materials to you.
; U.S. GOVERNMENT RESTRICTED RIGHTS: The Materials are provided with
; "RESTRICTED RIGHTS." Use, duplication, or disclosure by the Government is
; subject to the restrictions as set forth in FAR 52.227-14 and
; DFAR252.227-7013, et seq., or its successor. Use of the Materials by the
; Government constitutes acknowledgement of AMD's proprietary rights in them.
; EXPORT ASSURANCE: You agree and certify that neither the Materials, nor any
; direct product thereof will be exported directly or indirectly, into any
; country prohibited by the United States Export Administration Act and the
; regulations there under, without the required authorization from the U.S.
; government nor will be used for any purpose prohibited by the same.
You are correct. We do not have the right to redistribute this content. If possible, we should ask AMD/ATI to explicitly grant this permission.
Any news out there ? , otherwise I will close it
Don't close this one. I opened a dialog with AMD, and they're "working on the issue". No idea when or if it will happen, but it isn't dead in the water.
You may download the AMD microcode from this site. The necessary changes
to the license has been made and pushed through legal.
Russ, please follow through to ensure this package is included in RHEL6 as well.
Thanks for the update. We'll need to run this past our Legal counsel first to make sure that this is appropriate.
Tom, any updates from legal about this?
I have not yet heard back from AMD. While their new license is improved over the previous one, some of the wording ("for internal evaluation only") is unacceptable for Fedora. I am hopeful that AMD will drop that restriction so that we can move forward.
AMD dropped the restriction around "evaluation" usage, so the current license text is acceptable for Fedora.
Lifting FE-Legal, the AMD microcode should be fine to go into this package.
Thanks, I'll get on this this week.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
(In reply to comment #11)
> Thanks, I'll get on this this week.
any news out there ?
Ok, didn't get to it that week, but some week... ;-)
Feel free to try this scratch build, I don't have an AMD box to test this on, so I'll rely on someone external to tell me I didn't make a hash of things.
spot, I assumed that we were required to distribute the microcode license along with it, so I did so, but my head was spinning a bit due to all the legalese.
For some bizarre reason the last one had a broken initscript for an unrelated reason... Fixed build here tested by jforbes.
Ok, confirmed as working by a bunch of folks, so uploaded it to F11, F12, and rawhide.
microcode_ctl-1.17-1.56.fc12 has been submitted as an update for Fedora 12.
microcode_ctl-1.17-1.52.fc11 has been submitted as an update for Fedora 11.
microcode_ctl-1.17-1.56.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update microcode_ctl'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12779
microcode_ctl-1.17-1.52.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update microcode_ctl'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-12837
# /etc/init.d/microcode_ctl start
/etc/init.d/microcode_ctl: line 59: syntax error near unexpected token `}'
/etc/init.d/microcode_ctl: line 59: `}'
see bug #527701