From owner-freebsd-ports@freebsd.org Sun Feb 18 17:57:36 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A4CCF1CBC5 for ; Sun, 18 Feb 2018 17:57:36 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward102o.mail.yandex.net (forward102o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::602]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D64EF826D0 for ; Sun, 18 Feb 2018 17:57:35 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from mxback12j.mail.yandex.net (mxback12j.mail.yandex.net [IPv6:2a02:6b8:0:1619::87]) by forward102o.mail.yandex.net (Yandex) with ESMTP id E59975A0363C; Sun, 18 Feb 2018 20:57:32 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback12j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id dBW63wPrW6-vWYuxEvh; Sun, 18 Feb 2018 20:57:32 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1518976652; bh=aeMX74AkJVyRjpx9kz/V4vm0pScimou8mMD7GDh87y8=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References; b=oIhK3HnukXFNlozq3roVUELC+NT8COM3or/e2b4q+tuO1sio6T0R7ud34fuqXZU5/ uBlanZ5G7zk82yrUgcwEQaO05rkKVTxBfTCUsW2KpHTh2wHCjFwfvKUHyrPbVoo7Mr 9jegjod4aAXU/OvkjI2lDEhiD8LPUOZltW9Z8EqA= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ATadqn7HXK-vUsqel4j; Sun, 18 Feb 2018 20:57:31 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1518976651; bh=aeMX74AkJVyRjpx9kz/V4vm0pScimou8mMD7GDh87y8=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References; b=KltUnB6wSrOxtfR7Um/NZ3fZacmL9pg422Hk39ydbiB/kRzkiDZQ5np43pGKDfgUk 2BdsiYaTQ9emZaskM7vA5AwQDd4tD9qDAdpqiY2ncX4OGjeHaP61HqV6BaboK+kBvw Y5EApYLAtKSkX+4a1GnBt3usmNi4L/KlRu6cspOc= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1518976648.45203.0.camel@yandex.com> Subject: Re: sysutils/devcpu-data error "Please update your system in order to update CPU microcode." From: Stari Karp To: Nikos Kastanas , freebsd-ports@freebsd.org Date: Sun, 18 Feb 2018 12:57:28 -0500 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 17:57:36 -0000 On Sun, 2018-02-18 at 18:41 +0200, Nikos Kastanas wrote: > Hello > > I have a problem that i cannot seem to able to find the answer to. > > I have a Lenovo X220 laptop that runs FreeBSD-11.1-RELEASE fully > updated > with freebsd-update > I installed sysutils/devcpu-data in order to update the cpu > microcode, then > i checked that cpuctl is loaded in kldload and then i added > microcode_update_enable="YES" in /etc/rc.conf > > https://forums.freebsd.org/threads/introducing-cpupdate-a-microcode-too l-for-freebsd.64588/ Looks very good.