From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: Re: KMScon vs. AMD Radeon Date: Mon, 22 Apr 2019 13:48:52 +0200 Message-ID: <20190422114852.gu23mbtgzqjgseq4@pelzflorian.localdomain> References: <875zrbnfzb.fsf@gnu.org> <20190419121703.mdl3b5yckrbynnlh@pelzflorian.localdomain> <87mukmaut0.fsf@gnu.org> <20190419171116.htt7gchbb3hporoy@pelzflorian.localdomain> <87zhol9feb.fsf@gnu.org> <87bm11asms.fsf@ambrevar.xyz> <20190420103957.lvhx3tri244zzp6x@pelzflorian.localdomain> <20190420132129.5a61d66c@station.home> <87wojoamg0.fsf@ambrevar.xyz> <87tvesam4z.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([209.51.188.92]:46201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hIXRT-0002Vh-GC for guix-devel@gnu.org; Mon, 22 Apr 2019 07:49:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hIXRS-0001Qn-D1 for guix-devel@gnu.org; Mon, 22 Apr 2019 07:48:59 -0400 Content-Disposition: inline In-Reply-To: <87tvesam4z.fsf@ambrevar.xyz> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt Cc: guix-devel@gnu.org On Sat, Apr 20, 2019 at 02:37:00PM +0200, Pierre Neidhardt wrote: > OK, apparently it's possible to force AMDGPU onto Southern Island / Sea > Island: > > https://wiki.archlinux.org/index.php/AMDGPU#Enable_Southern_Islands_(SI)_and_Sea_Islands_(CIK)_support > It seems like this does not help. > We'd need to things: > > - enable the following in linux-libre > > --8<---------------cut here---------------start------------->8--- > # CONFIG_DRM_AMDGPU_SI is not set > # CONFIG_DRM_AMDGPU_CIK is not set > --8<---------------cut here---------------end--------------->8--- > > - Make sure amdgpu is loaded before radeon. Can we do that in the > operating-system declaration? > I added the above definitions --- gnu/packages/linux.scm | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm index b562a23b2f..0173176be3 100644 --- a/gnu/packages/linux.scm +++ b/gnu/packages/linux.scm @@ -275,7 +275,9 @@ for ARCH and optionally VARIANT, or #f if there is no such configuration." ("CONFIG_VIRTIO_MMIO" . m) ("CONFIG_FUSE_FS" . m) ("CONFIG_CIFS" . m) - ("CONFIG_9P_FS" . m))) + ("CONFIG_9P_FS" . m) + ("CONFIG_DRM_AMDGPU_SI" . #t) + ("CONFIG_DRM_AMDGPU_CIK" . #t))) (define (config->string options) (string-join (map (match-lambda -- 2.21.0 and changed nothing about the modules and their ordering. Then I reconfigured. As before, when I do not specify modprobe.blacklist=radeon, the display gets stuck with [ 8.679377] fb0: switching to radeondrmfb from EFI VGA Before, I could add modprobe.blacklist=radeon to boot to a console. Now I add modprobe.blacklist=radeon and get [ 9.507629] fb0: switching to amdgpudrmfb from EFI VGA It seems like now it is still broken just with amdgpu instead. Regards, Florian