Comment # 59
on bug 109206
from Jay Fitzpatrick
(In reply to Jay Fitzpatrick from comment #56) > (In reply to Ondrej Lang from comment #53) > > According to the linux kernel 5.2 changelog > > (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2), the fix for > > the DMCU firmware issue on raven1 platform is included in that release. > > > > I went ahead and tested this and can confirm that I was able to boot without > > a blank screen into my machine with kernel 5.2 without needing to use the > > workaround. > > > > I tested with: > > 1.) re-installed latest linux-firmware package > > 2.) installed kernel 5.2 > > 3.) re-generated the initramfs > > 4.) booted into linux using kernel 5.2 and had no blank screen, dmesg output > > is clean with no erros for amdgpu > > > > Tested on: > > HP HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.21 04/29/2019 > > > > I guess if someone else can confirm my findings, maybe on different raven1 > > hardware, this ticket can be closed. > > > Hi Ondrej > > While I have not been able to test the 5.2 kernel on my Fedora system I have > installed the 5.3 kernel from rawhide and am seeing the same results: > > [root@envy ~]# cp /home/XXX/raven_dmcu.bin /usr/lib/firmware/amdgpu/ > [root@envy ~]# dracut -f --kver 5.3.0-0.rc0.git2.2.fc31.x86_64 > [root@envy ~]# reboot > > Tested on HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.20 12/25/2018 > Kernel version 5.3.0-0.rc0.git2.2.fc31.x86_64 > > Installing rawhide kernel on Fedora without debug enabled: > sudo dnf config-manager > --add-repo=http://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/ > fedora-rawhide-kernel-nodebug.repo > sudo yum upgrade --Update-- While kernel versions 5.3.0-0.rc0.git2.2.fc31.x86_64 and 5.3.0-0.rc0.git2.4.fc31.x86_64 versions of the kernel seemed to be pretty stable when it came to booting the system / touchscreen working etc, there was a massive amount of video tearing (within Chrome / Konsole) within my KDE session, enough to force me to roll back to 5.1.16-300.fc30.x86_64 Jay
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
