From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8E2FB138350 for ; Mon, 4 May 2020 10:53:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1ABE5E09BA; Mon, 4 May 2020 10:53:32 +0000 (UTC) Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id ADCECE09A8 for ; Mon, 4 May 2020 10:53:30 +0000 (UTC) Received: by mail-oi1-x22a.google.com with SMTP id 19so6216699oiy.8 for ; Mon, 04 May 2020 03:53:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=UThjwLKuXllPX9uACnnQbCm8TB6365t6Y2yVJr3Pq04=; b=ikD7KovnhRkIMTidVnl2kT9mlRZMtCtR/rBRr1+fkvPqqjL+FSW3NkSWO/qhXw4x/D 7gYEmEfM4DkpTgs/XT9QzCLeV9It0CRlu8AwvZZ6v3R0P40gV4xEchYU++4+bTnOJ2Gd f4d/nxlfo+dHyjic9/awnGDhv2WgkY9uzXZuXfBwuK+GSCvBJCDheg6kskTQFiQheOOe y+J26rlF2dWJTQx93LdUF8ckUa0lmCIiumy1IxWec8RHkYWJrC7QZIetjCkvT1tHp2zP 8hfqVmbBhoJpRVe9HI2NobWQuKvTTFkoQC1UpRsPeT0rT683Pl15q/XsaEBm1vU9uLrI N0zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=UThjwLKuXllPX9uACnnQbCm8TB6365t6Y2yVJr3Pq04=; b=kOHuJ+rPn/DDeTjQRW6D5knGU3qNlVUJqUcddGaBbOkpK4O4gwagGNtBT4V0KmJ52F usizC3muCBgeC+POPxsX5cu+YeV7Ft+t6BDrAgx6/2z9R9MEBGfKKKnNcHQ0bRE7/xCh QpaHf5NQZz/DDRwTlqOrlWMyou4iL17rRuigULz7lCgwlfESnqtZAJE6MXPF0dvTn1Cx m26bSq7QNtQdVqwZLwgFQFUyfOMPHHFrbj0/MLntico2fiPV3B4IzfXQEBUhkzpJ1vdJ l+rZHHkoWHvrWTi4Ia9pQq9AvTO5uVqZ7FTFH2kG/zcsjB96VOLusXOoTgEghUQMFnIQ mojA== X-Gm-Message-State: AGi0PubCtfICktM+xJEmkzK+gUKUTmUopikCbx2Zo4ikehJP4D9BdVI3 cWgwVWs9Afa9KH+tbUL+lKUn6N1I82GyL6lF6Ie8g96l X-Google-Smtp-Source: APiQypJbhxCTd8TdZVI36h4aFP7izLfBKNrP/7Sivej+J2zwzPTNyVIC3AzDDW08tPYhPlh8k62wz8kaCF/8O/6AnL8= X-Received: by 2002:aca:dd8b:: with SMTP id u133mr8048918oig.55.1588589609535; Mon, 04 May 2020 03:53:29 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20200504002109.ougojgs2tnxg6j5l@ad-gentoo-main> In-Reply-To: <20200504002109.ougojgs2tnxg6j5l@ad-gentoo-main> From: Adam Carter Date: Mon, 4 May 2020 20:53:18 +1000 Message-ID: Subject: Re: [gentoo-user] AMD Radeon R7 370 (Pitcairn) causing the bootup to hang To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="0000000000005ed70805a4d05755" X-Archives-Salt: ee795302-8233-4289-b0ac-33f79e8c89b3 X-Archives-Hash: 75b36250184fc7a4094121d058e7e123 --0000000000005ed70805a4d05755 Content-Type: text/plain; charset="UTF-8" On Mon, May 4, 2020 at 10:21 AM Ashley Dixon wrote: > Hi gentoo-user, > > I'm attempting to configure a mid-range video card: the Radeon R7 370. > Running > on the Pitcairn chipset and a member of the Southern Islands family, > I am > surprised at the complexity of setting up the Radeon driver in comparison > to its > NVIDIA counterpart. > > I followed [1] carefully. Initially opting to compile AMDGPU into the > kernel, I > emerged linux-firmware with the following files. All of the relevant > files were > added to the kernel's CONFIG_EXTRA_FIRMWARE string, using /lib/firmware > as the > base directory. > > radeon/pitcairn_smc.bin > radeon/pitcairn_ce.bin > radeon/pitcairn_mc.bin > radeon/pitcairn_me.bin > radeon/pitcairn_pfp.bin > radeon/pitcairn_k_smc.bin > radeon/pitcairn_rlc.bin > radeon/TAHITI_uvd.bin > radeon/TAHITI_vce.bin > Did it load ok? dmesg | grep -i drm.*firm You should see; [drm] Found UVD firmware Version etc [drm] Found VCE firmware Version etc > Unfortunately, upon booting, the kernel hangs with the following message. > This > seems to be rather common, with a similar complaint being discussed > at [2]. > > fb0: switching to amdgpudrmfb from EFI VGA > Here's what i get (R9 380) # dmesg | grep -i fb0 [ 1.302701] fbcon: amdgpudrmfb (fb0) is primary device [ 1.474076] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device What CONFIG_FB options are enabled? I dont have CONFIG_FB_EFI set to try removing that. > As this all occurs pre-OpenRC, I am incapable of creating an S.S.H.\ > connection > to the machine from my laptop. When booting the kernel with the > `nomodesetting` > parameter, the X server reports the following after a successful > kernel boot > (created when executing `startx`): [timestamps omitted] > > (EE) Failed to load module "fbdev" (module does not exist, 0) > (II) LoadModule: "vesa" > (WW) Warning, couldn't open module vesa > (EE) Failed to load module "vesa" (module does not exist, 0) > (II) RADEON: Driver for ATI/AMD Radeon chipsets: > ATI Radeon Mobility X600 (M24), ATI FireMV 2400, > ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL, > > [...] > > ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, > KABINI, > MULLINS, KAVERI, HAWAII > (II) modesetting: Driver for Modesetting Kernel Drivers: kms > (--) using VT number 7 > > (II) [KMS] drm report modesetting isn't supported. > (EE) open /dev/dri/card0: No such file or directory > (WW) Falling back to old probe method for modesetting > (EE) open /dev/dri/card0: No such file or directory > I'd say that's the key. What CONFIG_DRM options are enabled? --0000000000005ed70805a4d05755 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, May 4, 2020 at 10:21 AM Ashley Dixon <ash@suugaku.co.uk> wrote:
Hi gentoo-user,

I'm attempting to configure a mid-range video card: the Radeon R7 370.= =C2=A0 =C2=A0Running
on the Pitcairn chipset and a member=C2=A0 of=C2=A0 the=C2=A0 Southern=C2= =A0 Islands=C2=A0 family,=C2=A0 I=C2=A0 am
surprised at the complexity of setting up the Radeon driver in comparison t= o its
NVIDIA counterpart.

I followed [1] carefully.=C2=A0 Initially opting to compile AMDGPU into the= kernel, I
emerged linux-firmware with the following files.=C2=A0 All of the relevant = files were
added to the kernel's CONFIG_EXTRA_FIRMWARE string, using /lib/firmware= =C2=A0 as=C2=A0 the
base directory.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_smc.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_ce.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_mc.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_me.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_pfp.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_k_smc.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/pitcairn_rlc.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/TAHITI_uvd.bin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 radeon/TAHITI_vce.bin

=
Did it load ok?
dmesg | grep -i drm.*firm
Yo= u should see;
[drm] Found UVD firmware Version etc
= [drm] Found VCE firmware Version etc
=C2=A0
Unfortunately, upon booting, the kernel hangs with the following message.= =C2=A0 =C2=A0This
seems to be rather common, with a similar=C2=A0 complaint=C2=A0 being=C2=A0= discussed=C2=A0 at=C2=A0 [2].

=C2=A0 =C2=A0 =C2=A0 =C2=A0 fb0: switching to amdgpudrmfb from EFI VGA
<= /blockquote>

Here's what i get (R9 380)
# = dmesg | grep -i fb0
[ =C2=A0 =C2=A01.302701] fbcon: amdgpudrmfb (fb0) is= primary device
[ =C2=A0 =C2=A01.474076] amdgpu 0000:01:00.0: fb0: amdgp= udrmfb frame buffer device

What CONFIG_FB options = are enabled? I dont have CONFIG_FB_EFI set to try removing that.
<= div>

As this all occurs pre-OpenRC, I am incapable of creating an S.S.H.\=C2=A0 = connection
to the machine from my laptop.=C2=A0 When booting the kernel with the `nomo= desetting`
parameter, the X server reports the following after=C2=A0 a=C2=A0 successfu= l=C2=A0 kernel=C2=A0 boot
(created when executing `startx`): [timestamps omitted]

=C2=A0 =C2=A0 =C2=A0 =C2=A0 (EE) Failed to load module "fbdev" (m= odule does not exist, 0)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (II) LoadModule: "vesa"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (WW) Warning, couldn't open module vesa
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (EE) Failed to load module "vesa" (mo= dule does not exist, 0)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (II) RADEON: Driver for ATI/AMD Radeon chipsets= :
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ATI Radeon Mobility= X600 (M24), ATI FireMV 2400,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ATI Radeon Mobility= X300 (M24), ATI FireGL M24 GL,

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [...]

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ARUBA, TAHITI, PITC= AIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 MULLINS, KAVERI, HA= WAII
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (II) modesetting: Driver for Modesetting Kernel= Drivers: kms
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (--) using VT number 7

=C2=A0 =C2=A0 =C2=A0 =C2=A0 (II) [KMS] drm report modesetting isn't sup= ported.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (EE) open /dev/dri/card0: No such file or direc= tory
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (WW) Falling back to old probe method for modes= etting
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (EE) open /dev/dri/card0: No such file or direc= tory

I'd say that's the key. Wh= at CONFIG_DRM options are enabled?

--0000000000005ed70805a4d05755--