Quote:
Originally Posted by gaitos
Just for a first simple experiment I've installed the 4.19.77-huge kernel from -current (I think that for the kernel it doesn't matter if it's installed as a binary or recompiled) and indeed amdgpu no longer complains about lack of firmware, however...
Code:
[ 8.780604] ------------[ cut here ]------------
[ 8.780746] WARNING: CPU: 3 PID: 751 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_base.c:64 dal_gpio_open_
ex.cold+0xc/0x14 [amdgpu]
..followed by the full debug info (let me know if I need to post that, it's rather long) and after that, something that is quite rare nowadays:
Code:
[ 8.925929] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
To be clear, this happens right at kernel initialization of drm and fbcon (on boot), without X being started. What is more, if I reboot after booting with 4.19.77, the card fails to initialize, I have to push the reset button in order to get an image on the monitor.
This warning and NULL pointer BUG don't happen with amdgpu pro (in fact the only trouble I have with that approach is that chromium based browsers don't work).
Before posting this I have tried the 5.3.4 kernel again and now that there is a firmware present it doesn't complain about that (and fbcon properly initializs), however it somewhat randomly (i.e. 1 out of 5 cold reboots, but on every warm reboot) gives similar warnings in dmesg (and on the console, of course), but no NULL pointer BUG messages. It also leaves the card in a better state, so that warm reboots work.
I don't know if these warnings would prevent the rest of the amdgpu drivers (xorg and so on) from working, but I suspect so! |
I was running into similar issues with my RX570 on 14.2 with the 4.19 kernel (self compiled). I think it just requires newer versions of quite a bit of software and 14.2 just can't hack it well. I've been in the process of upgrading various components of 14.2 to get it working, but I hit a roadblock (see next paragraph for the details). I'm debating restoring 14.2 packages back to stock and then try again.
I seem to have the crashes gone with the updates I've done (basically upgrade mesa, libdrm, llvm, and most of Xorg and any dependencies along the way and running the 5.3.1 kernel), but I knocked out opengl while doing all these updates. Based on this, I'm guessing this would work fine in -current with a newer kernel (5.3.1 seems to be working fine here), but I don't think I want to fully switch to -current.
I'm hoping if I go through the process to upgrade the software stack in 14.2 again that I'll bypass whatever issue I had before. Now I just need to find the time to do it!
Quote:
Originally Posted by gaitos
I will try and get the 5.3.4 firmware to see if there are any changes.
The newer firmware is the same for this card (same version) so that doesn't change anything.
|
The firmware is supposed to be for any kernel and not necessarily tied to a specific version. The kernel-firmware SlackBuild will just clone the kernel-firmware git and put everything in a Slackware package.
Quote:
Originally Posted by gaitos
However, should I have known this I would have went with nVidia, it's funny that I bought AMD after reading that they have better open-source drivers. Right!
|
Their open source drivers are much better, but trying to run newer hardware on a 3+ year old system will run into serious problems, because the software stack doesn't have support for the newer hardware. This should be much better on -current and I imagine if -current ends up getting the 5.4 kernel, which is expected to be the next LTS, all these problems will be gone.
Quote:
Originally Posted by gaitos
Also: should I create a new thread for this? It's getting somwhat unrelated to amdgpu pro.
|
You could "Report" your post and request it to be split from the rest of the topic.
