On Wed, 19 Aug 2020 02:20:01 +1000
Jonathan Gray <j...@jsg.id.au> wrote:

> On Tue, Aug 18, 2020 at 12:09:56PM -0400, Jon Fineman wrote:
> > On Wed, 19 Aug 2020 00:06:59 +1000
> > Jonathan Gray <j...@jsg.id.au> wrote:
> >   
> > > On Sun, Aug 16, 2020 at 02:27:46AM +0000, Jon Fineman wrote:  
> > > > I was not able to do a proper sendbug report because the PC
> > > > hangs.
> > > > 
> > > > I have an Acer Aspire A315 laptop. 6.6 works fine. When I
> > > > upgrade to 6.7 Release or Snapshot I get the below firmware
> > > > load error. Below that output is the dmesg from a 6.6 boot so
> > > > you can see the hardware.    
> > > 
> > > The first boot after a new install will not have the firmware.
> > > fw_update(1) will run and install it into /etc/firmware/amdgpu/
> > > 
> > > Does amdgpu still not attach after you've verified the files are
> > > present and rebooted?  
> > 
> > 
> > I mounted the memory stick and verified the amd firmware files are
> > present in /etc/firmware/amdgpu. I also downloaded the ones from 6.7
> > and copied them to that directory.
> > 
> > When I booted it wanted to update the firmware for amdgpu and vmm.
> > 
> > Then it dies while re-ording the kernel.
> > 
> > I am not sure how I would tell if the amdgpu attached or not.
> > 
> > /var/log/message from this test:
> > 
> > Aug 18 11:54:56 laptop /bsd: softraid0 at root
> > Aug 18 11:54:56 laptop /bsd: scsibus4 at softraid0: 256 targets
> > Aug 18 11:54:56 laptop /bsd: root on sd1a (c5239493226aa09b.a) swap
> > on sd1b dump on sd1b Aug 18 11:54:56 laptop /bsd: initializing
> > kernel modesetting (STONEY 0x1002:0x98E4 0x1025:0x1192 0xDA). Aug
> > 18 11:54:56 laptop /bsd: amdgpu_irq_add_domain: stub Aug 18
> > 11:54:56 laptop /bsd: amdgpu0: 1366x768, 32bpp Aug 18 11:54:56
> > laptop /bsd: wsdisplay0 at amdgpu0 mux 1: console (std, vt100
> > emulation), using wskbd0 Aug 18 11:54:56 laptop /bsd: wsdisplay0:
> > screen 1-5 added (std, vt100 emulation)  
> 
> It has attached here.  If there is fatal error such as missing
> firmware it will detach and efifb or vga will reclaim the console.


After comparing the logs from my first and second test I notice the
below line from amdgpu_attachhook *ERROR*. Does that imply that the
attach failed?

> Aug 14 09:58:42 laptop /bsd: drm:pid0:gfx_v8_0_init_microcode *ERROR*
> gfx8: Failed to load firmware "amdgpu/stoney_pfp.bin" Aug 14 09:58:42
> laptop /bsd: [drm] *ERROR* Failed to load gfx firmware! Aug 14
> 09:58:42 laptop /bsd: [drm] *ERROR* sw_init of IP block <gfx_v8_0>
> failed -2 Aug 14 09:58:42 laptop /bsd: drm:pid0:amdgpu_device_init
> *ERROR* amdgpu_device_ip_init failed Aug 14 09:58:42 laptop /bsd:
> drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init Aug 14
> 09:58:42 laptop /bsd: efifb0 at mainbus0: 1366x768, 32bpp Aug 14
> 09:58:42 laptop /bsd: wsdisplay0 at efifb0 mux 1: console (std, vt100
> emulation), using wskbd0 Aug 14 09:58:42 laptop /bsd: wsdisplay0:
> screen 1-5 added (std, vt100 emulation)

Reply via email to