Hello Stan,
On Sun, Oct 21, 2018 at 09:37:19AM -0700, stan wrote:
>
> You could compare the journal messages from the older firmware when
> it succeeded with those from the failing firmware to see if there is any
> difference. For that matter, compare the successful old load with the
> failing o
Hello Allan,
On Sun, Oct 21, 2018 at 10:40:32PM -, Allan wrote:
> >amdgpu :06:00.0: Direct firmware load for amdgpu/raven_gpu_info.bin
> > failed with error -2
> >
>
> I have had the same fight with A
Hi Suvayu...
> Hello,
>
[..]
>amdgpu :06:00.0: Direct firmware load for amdgpu/raven_gpu_info.bin
> failed with error -2
>
I have had the same fight with AMDGPU-PRO drivers on Centos.
The problem is that
On Sun, 21 Oct 2018 19:15:01 +0530
Suvayu Ali wrote:
> Sorry for the late response, I wasn't monitoring the list.
Not a problem.
> I actually thought of what you mentioned in the other post, the
> firmware making a persistent change in some register. I really don't
> know how I could investiga
Hi Stan,
Sorry for the late response, I wasn't monitoring the list.
I actually thought of what you mentioned in the other post, the firmware making
a persistent change in some register. I really don't know how I could
investigate that :-|
On Wed, Oct 17, 2018 at 09:18:18AM -0700, stan wrote:
On Wed, 17 Oct 2018 09:26:01 +0530
Suvayu Ali wrote:
> I have already tried both rebuilding the initrd, and reinstall the
> kernel to no avail :(
Thinking about this, I wonder if the new firmware set something in the
device memory that the old firmware is not aware of? The old firmware
loads, bu
On Wed, 17 Oct 2018 09:26:01 +0530
Suvayu Ali wrote:
> I have already tried both rebuilding the initrd, and reinstall the
> kernel to no avail :(
I don't know if firmware loading is done similarly to a kernel module.
If it is, you could try modprobe.
The other thing is to do an
rpm -q --files
On Mon, Oct 15, 2018 at 04:41:12PM +, Rick Stevens wrote:
> >
> > My hunch is, as the ROCm installation uses dkms to build the kernel module
> > (which failed btw, that's why ROCm didn't work for me), the uninstallation
> > somehow leaves behind some configuration which persists across kerne
On 10/12/18 7:49 PM, Suvayu Ali wrote:
> Hello Rick,
>
> On Fri, Oct 12, 2018 at 11:51:40PM +, Rick Stevens wrote:
>>>
>>> [drm] amdgpu kernel modesetting enabled.
>>> [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1458:0xD000
>>> 0xC6).
>>> [drm] register mmio base: 0xFE6
Hello Rick,
On Fri, Oct 12, 2018 at 11:51:40PM +, Rick Stevens wrote:
> >
> > [drm] amdgpu kernel modesetting enabled.
> > [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1458:0xD000
> > 0xC6).
> > [drm] register mmio base: 0xFE60
> > [drm] register mmio size: 524288
On 10/12/18 4:12 PM, Suvayu Ali wrote:
> Hello,
>
> I have a strange issue. I am on one of AMD's Raven Ridge APUs (Ryzen 5
> 2400G). Everything was working fine, with the 4.18.x series kernels.
> However I wanted to experiment with the ROCm drivers[1] that are under
> development. I managed
Hello,
I have a strange issue. I am on one of AMD's Raven Ridge APUs (Ryzen 5 2400G).
Everything was working fine, with the 4.18.x series kernels. However I wanted
to experiment with the ROCm drivers[1] that are under development. I managed
to install after some fiddling, but the firmware k
12 matches
Mail list logo
