| 1 |
On Mon, May 4, 2020 at 10:21 AM Ashley Dixon <ash@××××××××××.uk> wrote: |
| 2 |
|
| 3 |
> Hi gentoo-user, |
| 4 |
> |
| 5 |
> I'm attempting to configure a mid-range video card: the Radeon R7 370. |
| 6 |
> Running |
| 7 |
> on the Pitcairn chipset and a member of the Southern Islands family, |
| 8 |
> I am |
| 9 |
> surprised at the complexity of setting up the Radeon driver in comparison |
| 10 |
> to its |
| 11 |
> NVIDIA counterpart. |
| 12 |
> |
| 13 |
> I followed [1] carefully. Initially opting to compile AMDGPU into the |
| 14 |
> kernel, I |
| 15 |
> emerged linux-firmware with the following files. All of the relevant |
| 16 |
> files were |
| 17 |
> added to the kernel's CONFIG_EXTRA_FIRMWARE string, using /lib/firmware |
| 18 |
> as the |
| 19 |
> base directory. |
| 20 |
> |
| 21 |
> radeon/pitcairn_smc.bin |
| 22 |
> radeon/pitcairn_ce.bin |
| 23 |
> radeon/pitcairn_mc.bin |
| 24 |
> radeon/pitcairn_me.bin |
| 25 |
> radeon/pitcairn_pfp.bin |
| 26 |
> radeon/pitcairn_k_smc.bin |
| 27 |
> radeon/pitcairn_rlc.bin |
| 28 |
> radeon/TAHITI_uvd.bin |
| 29 |
> radeon/TAHITI_vce.bin |
| 30 |
> |
| 31 |
|
| 32 |
Did it load ok? |
| 33 |
dmesg | grep -i drm.*firm |
| 34 |
You should see; |
| 35 |
[drm] Found UVD firmware Version etc |
| 36 |
[drm] Found VCE firmware Version etc |
| 37 |
|
| 38 |
|
| 39 |
> Unfortunately, upon booting, the kernel hangs with the following message. |
| 40 |
> This |
| 41 |
> seems to be rather common, with a similar complaint being discussed |
| 42 |
> at [2]. |
| 43 |
> |
| 44 |
> fb0: switching to amdgpudrmfb from EFI VGA |
| 45 |
> |
| 46 |
|
| 47 |
Here's what i get (R9 380) |
| 48 |
# dmesg | grep -i fb0 |
| 49 |
[ 1.302701] fbcon: amdgpudrmfb (fb0) is primary device |
| 50 |
[ 1.474076] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device |
| 51 |
|
| 52 |
What CONFIG_FB options are enabled? I dont have CONFIG_FB_EFI set to try |
| 53 |
removing that. |
| 54 |
|
| 55 |
|
| 56 |
> As this all occurs pre-OpenRC, I am incapable of creating an S.S.H.\ |
| 57 |
> connection |
| 58 |
> to the machine from my laptop. When booting the kernel with the |
| 59 |
> `nomodesetting` |
| 60 |
> parameter, the X server reports the following after a successful |
| 61 |
> kernel boot |
| 62 |
> (created when executing `startx`): [timestamps omitted] |
| 63 |
> |
| 64 |
> (EE) Failed to load module "fbdev" (module does not exist, 0) |
| 65 |
> (II) LoadModule: "vesa" |
| 66 |
> (WW) Warning, couldn't open module vesa |
| 67 |
> (EE) Failed to load module "vesa" (module does not exist, 0) |
| 68 |
> (II) RADEON: Driver for ATI/AMD Radeon chipsets: |
| 69 |
> ATI Radeon Mobility X600 (M24), ATI FireMV 2400, |
| 70 |
> ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL, |
| 71 |
> |
| 72 |
> [...] |
| 73 |
> |
| 74 |
> ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, |
| 75 |
> KABINI, |
| 76 |
> MULLINS, KAVERI, HAWAII |
| 77 |
> (II) modesetting: Driver for Modesetting Kernel Drivers: kms |
| 78 |
> (--) using VT number 7 |
| 79 |
> |
| 80 |
> (II) [KMS] drm report modesetting isn't supported. |
| 81 |
> (EE) open /dev/dri/card0: No such file or directory |
| 82 |
> (WW) Falling back to old probe method for modesetting |
| 83 |
> (EE) open /dev/dri/card0: No such file or directory |
| 84 |
> |
| 85 |
|
| 86 |
I'd say that's the key. What CONFIG_DRM options are enabled? |
Archives