Le vendredi 22 septembre 2023 à 13:41 +1000, Jonathan Gray a écrit :
> On Thu, Sep 21, 2023 at 11:40:24AM -0400, Solène Rapenne wrote:
> > On Thu, 2023-09-21 at 17:50 +1000, Jonathan Gray wrote:
> > > On Thu, Sep 21, 2023 at 09:05:50AM +0200, Solène Rapenne wrote:
> > > > > Synopsis: my GPU AMD Sapphire RX 6600 isn't recognized
> > > > > Category: kernel
> > > > > Environment:
> > > > System : OpenBSD 7.4
> > > > Details : OpenBSD 7.4-beta (GENERIC.MP) #1372: Wed
> > > > Sep 20 09:43:54 MDT 2023
> > > >
> > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENER
> > > > IC.MP
> > > >
> > > > Architecture: OpenBSD.amd64
> > > > Machine : amd64
> > > > > Description:
> > > > I can't get accelerated graphics with a Sapphire RX
> > > > 6600.
> > > > The amdgpu firmware is correctly installed after
> > > > running fw_update
> > >
> > > > [drm] *ERROR* visible_vram_size 1ff000000 or aper_base_kaddr
> > > > 0x0 is not initialized.
> > > > [drm] *ERROR* Failed to process memory training!
> > > > [drm] *ERROR* sw_init of IP block <psp> failed -22
> > > > drm:pid0:amdgpu_device_init *ERROR* amdgpu_device_ip_init
> > > > failed
> > > > drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init
> > > > efifb0 at mainbus0: 1920x1080, 32bpp
> > >
> > > Does the bios have an option to disable resizable pci bar?
> > >
> > > Doing an install with csm enabled (vga instead of efifb)
> > > may also change things.
> >
> > disabline the bar thing in the bios allowed me to have the GPU
> > recognized, but for some reason GDM started but didn't display
> > anything. Enabling auto login into gnome to circumvent the issue
> > with GDM, I ended in a frozen gnome with only gnome-shell loaded.
> >
> > with xenodm and cwm it worked
> >
> > until I've lost the screen, ssh was still working and I got access
> > to dmesg which has some stuff related to GPU
>
> does this diff change what happens?
>
> Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c,v
> retrieving revision 1.10
> diff -u -p -r1.10 amdgpu_gmc.c
> --- sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 19 Jun 2023 00:38:02
> -0000 1.10
> +++ sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 22 Sep 2023 03:37:10
> -0000
> @@ -670,15 +670,6 @@ void amdgpu_gmc_get_vbios_allocations(st
> } else {
> size = amdgpu_gmc_get_vbios_fb_size(adev);
>
> -#ifdef __amd64__
> - /*
> - * XXX Workaround for machines where the framebuffer
> - * size reported by the hardware is incorrect.
> - */
> - extern psize_t efifb_stolen();
> - size = max(size, efifb_stolen());
> -#endif
> -
> if (adev->mman.keep_stolen_vga_memory)
> size = max(size,
> (unsigned)AMDGPU_VBIOS_VGA_ALLOCATION);
> }
no, same behavior, gdm and gnome aren't working
And I didn't try long enough on fvwm to trigger a crash.
