https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #69 from Jay Fitzpatrick ---
Upgraded to 5.3.11-300.fc31.x86_64 this morning with
linux-firmware-20191022-103.fc31.noarch and no evidence of regression
Jay
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #68 from Luya Tshimbalanga ---
(In reply to Alex Deucher from comment #67)
> (In reply to Luya Tshimbalanga from comment #65)
> > Change the title reflecting the impact on Raven Ridge
>
> This is completely unrelated to your issue.
https://bugs.freedesktop.org/show_bug.cgi?id=109206
Alex Deucher changed:
What|Removed |Added
Summary|Kernel 5.3.11 and onward|Kernel 4.20 amdgpu fails to
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #64 from Luya Tshimbalanga ---
Created attachment 145952
--> https://bugs.freedesktop.org/attachment.cgi?id=145952=edit
Journal boot from hp envy x360 cp0xxx
The bug caused the Raven Ridge firmware to fail is back on kernel
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #63 from Talha Khan ---
I updated my kernel to 5.1.19, and the firwmare files were updated, but I
wasn't able to boot. I had to boot back into 5.1.16 and perform the workaround
before being able to boot into 5.1.19.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #62 from Chris ---
Just wanted to say that on Kernel 5.2rc7, BIOS F.21 I'm able to boot with
raven_dmcu.bin in /lib/firmware/amdgpu. I also updated raven_dmcu.bin from the
linux firmware git. Not sure which part helped though or all
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #61 from Talha Khan ---
(In reply to Michael Eagle from comment #60)
> Created attachment 144787 [details]
> attachment-8612-0.html
>
> I am seeing reports with old BIOS, such as F.19.
> I have a 15-cp0001na
>
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #60 from Michael Eagle ---
I am seeing reports with old BIOS, such as F.19.
I have a 15-cp0001na
https://support.hp.com/ie-en/drivers/selfservice/hp-envy-15-cp-x360-convertible-pc/20270303/model/23086446
Latest available is F.42
I am seeing reports with old BIOS, such as F.19.
I have a 15-cp0001na
https://support.hp.com/ie-en/drivers/selfservice/hp-envy-15-cp-x360-convertible-pc/20270303/model/23086446
Latest available is F.42 Rev.A
I am wondering if by any chance would be a match to other models also.
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #59 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://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #58 from Joe Coutcher ---
Update - After adding init=nomwait and iommu=pt to my kernel parameters, I'm no
longer seeing garbage on the display, and the system has been stable for the
past hour on 5.2rc7.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #57 from Joe Coutcher ---
(In reply to Ondrej Lang from comment #55)
> Hi Joe,
>
> I'm quite sure your issue is not related to this ticket. The problem in this
> bug report is quite specific and is related to the raven_dmcu.bin
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #56 from Jay Fitzpatrick ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #55 from Ondrej Lang ---
(In reply to Joe Coutcher from comment #54)
> Ondrej - I'm on a fresh install of Ubuntu 19.04 with no workarounds applied,
> using a similar setup to yours (HP Envy x360 15m-bq121dx.) I installed
> kernel
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #54 from Joe Coutcher ---
Ondrej - I'm on a fresh install of Ubuntu 19.04 with no workarounds applied,
using a similar setup to yours (HP Envy x360 15m-bq121dx.) I installed kernel
5.2 RC7 (since the AMD64 build of 5.2 final on
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #53 from Ondrej Lang ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #52 from Talha Khan ---
(In reply to Ondrej Lang from comment #50)
> I tested this yesterday with kernel 5.1.8 and if the file raven_dmcu.bin is
> present in the /lib/firmware/amdgpu/ folder when you are updating the kernel
> (or
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #51 from moregin...@warpmail.net ---
Also cannot boot without nomodeset or modprobe.blacklist=amdgpu. With the
latter, I get a black screen if I run `modprobe amdgpu`.
I have Ryzen 2400G.
The trick with moving raven_dmcu.bin (as
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #50 from Ondrej Lang ---
I tested this yesterday with kernel 5.1.8 and if the file raven_dmcu.bin is
present in the /lib/firmware/amdgpu/ folder when you are updating the kernel
(or manually rebuilding the initramfs), the computer
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #49 from Talha Khan ---
I updated my kernel to 5.1.7 and did not need to run dracut to rebuild my
initramfs. I was able to boot just fine.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #48 from Alex Deucher ---
The patch is for the kernel.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #47 from Ondrej Lang ---
The patch is not part of the kernel package itself, it is part of the
linux-firmware package, there was no new release of linux-firmware since I
tested this.
I think the reason why you did not have to
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #46 from Talha Khan ---
Thanks for the update Ondrej. It seems that the patch may be in place. Since
I've updated my Fedora 30 system's kernel to 5.1.6, I haven't had to run dracut
to rebuild my initramfs. The raven_dmcu.bin file
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #45 from Ondrej Lang ---
I just came across this article, which seems to suggest a fix for the issue
mentioned in this thread is coming in a future linux-firmware update:
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #44 from Ondrej Lang ---
Created attachment 144316
--> https://bugs.freedesktop.org/attachment.cgi?id=144316=edit
Kernel log 5.1.3 showing amdgpu drm crash
Experiencing the same problem. On boot with any kernel > 4.20, the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #43 from Talha Khan ---
I updated my Fedora KDE spin system from Fedora 29 to Fedora 30 and had the
same experience as Jay's.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #42 from Jay Fitzpatrick ---
This was an upgrade from Fedora 29 with the above workaround applied to a v5
kernel.
Booting from the KDE spin of Fedora 30 would only work with limited graphics
(nomodset) as the default boot hung.
I
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #41 from Talha Khan ---
Thanks for the update Jay. Did you upgrade or do a fresh install?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #40 from Jay Fitzpatrick ---
Issue still present on Fedora30 with Kernel 5.0.9-301.fc30.x86_64
Workaround
sudo mv /usr/lib/firmware/amdgpu/raven_dmcu.bin /home/XXX/
sudo dracut -f --kver 5.0.9-301.fc30.x86_64
Tested and working
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #39 from Alex Deucher ---
(In reply to Adrian Garay from comment #38)
> (In reply to Alex Deucher from comment #33)
> > (In reply to Talha Khan from comment #31)
> > > I moved the raven_dcmu.bin file to another directory, but
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #38 from Adrian Garay ---
(In reply to Alex Deucher from comment #33)
> (In reply to Talha Khan from comment #31)
> > I moved the raven_dcmu.bin file to another directory, but unfortunately I am
> > still unable to boot any kernel
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #37 from Talha Khan ---
The issue occurs (and workaround works) on kernels 5.0.8 and 5.0.9.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #36 from Talha Khan ---
(In reply to JerryD from comment #35)
> Well, I just ran Fedora updates which brought kernel to 5.0.7-200.fc29 and
> there was also an update to mesa-dri-drivers.x86_64 18.3.6-1.fc29. My laptop
> failed to
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #35 from JerryD ---
Well, I just ran Fedora updates which brought kernel to 5.0.7-200.fc29 and
there was also an update to mesa-dri-drivers.x86_64 18.3.6-1.fc29. My laptop
failed to boot with or without the raven_dmcu.bin file after
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #34 from Talha Khan ---
(In reply to Alex Deucher from comment #33)
> (In reply to Talha Khan from comment #31)
> > I moved the raven_dcmu.bin file to another directory, but unfortunately I am
> > still unable to boot any kernel
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #33 from Alex Deucher ---
(In reply to Talha Khan from comment #31)
> I moved the raven_dcmu.bin file to another directory, but unfortunately I am
> still unable to boot any kernel newer 4.20. For me at least, I get a black
> screen
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #32 from Talha Khan ---
Created attachment 143893
--> https://bugs.freedesktop.org/attachment.cgi?id=143893=edit
Journalctl output for kernel 5.0.5-200.fc29.x86_64
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #31 from Talha Khan ---
I moved the raven_dcmu.bin file to another directory, but unfortunately I am
still unable to boot any kernel newer 4.20. For me at least, I get a black
screen with a horizontal line near the bottom of orange
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #30 from Chris ---
(In reply to Talha Khan from comment #29)
> Also, it seems that for the HP Envy x360 laptop, the latest BIOS is back to
> F.10; F.20 is listed in "previous versions".
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #29 from Talha Khan ---
Also, it seems that for the HP Envy x360 laptop, the latest BIOS is back to
F.10; F.20 is listed in "previous versions".
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #28 from Talha Khan ---
I'm not sure if I want to delete raven_dcmu.bin on my system, would renaming it
or moving it have the same effect? I have the same system as JerryD and am
running Fedora 29 KDE.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #27 from JerryD ---
I am following 7 serious bug reports on kernel, redhat, freedesktop bugzillas.
This one is by far the most critical when one can not boot the machine. I am
happy to try to test things. I am not set up to compile
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #26 from Tim Carr ---
Edit to my above statement about the amd-staging-drm-next kernel working.
Either, I had forgotten to return the raven_dmcu.bin file to it's appropriate
folder when I tested it, or upgrading my bios to F.20
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #25 from Nicola Orlando ---
(In reply to Harry Wentland from comment #17)
> I don't have that laptop but this link mentions a method to "Update the BIOS
> when Windows does not start": https://support.hp.com/ca-en/document/c00042629
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #24 from Adrian Garay ---
Since I didn't clearly specify above, my result was with amd-staging-drm-next,
but the behavior is identical to the current 5.0 release. When the screen goes
blank the machine stops responding, but it
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #23 from Adrian Garay ---
I am on firmware F.20 and the above does not work for me. I still see the
scrambled line of garbage at boot, but instead of crashing my screen just goes
blank.
If I add modprobe.blacklist=amdgpu to the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #22 from Adrian Garay ---
Created attachment 143560
--> https://bugs.freedesktop.org/attachment.cgi?id=143560=edit
logged when modprobe amdgpu is run
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #21 from Tim Carr ---
I can confirm that the amd-staging-drm-next kernel also works for my system.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #20 from Gavin A. ---
I changed my kernel to the linux-amd-staging-drm-next-git which already has
patch applied. System boots, X starts fine, and I am able to run intensive 3d
app without any performance/rendering issues, no
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #19 from Tim Carr ---
(In reply to Harry Wentland from comment #15)
> Can you see if this patch fixes it:
> https://patchwork.freedesktop.org/patch/277181/
Wasn't able to get that patch to apply cleanly to either 4.20 or 5.0rc2. I
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #18 from JerryD ---
(In reply to Adrian Garay from comment #12)
> (In reply to matrix8967 from comment #11)
> > This is the exact same issue I had and the above solution for removing
> > /lib/firmware/amdgpu/raven_dmcu.bin worked
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #17 from Harry Wentland ---
I don't have that laptop but this link mentions a method to "Update the BIOS
when Windows does not start": https://support.hp.com/ca-en/document/c00042629
I'd be more curious to know if the patch I
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #16 from Matrix ---
Is it possible to upgrade the Bios from Linux? I think it's just a windows-only
bios upgrade from HP right? Will it work in Freedos?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #15 from Harry Wentland ---
Can you see if this patch fixes it:
https://patchwork.freedesktop.org/patch/277181/
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #14 from Harry Wentland ---
I'd recommend updating the System BIOS.
Early BIOSes on HP Envy x360 (and possibly other Raven laptops) had trouble
loading the DMCU FW.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #13 from Zdenek ---
I get hard lock during LibreOffice start after this workaround. Nothing
interesting in logs can be found.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #12 from Adrian Garay ---
(In reply to matrix8967 from comment #11)
> This is the exact same issue I had and the above solution for removing
> /lib/firmware/amdgpu/raven_dmcu.bin worked for me.
>
> For Ubuntu Users on 4.20 you'll
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #11 from matrix8...@gmail.com ---
This is the exact same issue I had and the above solution for removing
/lib/firmware/amdgpu/raven_dmcu.bin worked for me.
For Ubuntu Users on 4.20 you'll need to also run
sudo update-initramfs -u
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #10 from cd ---
I also encounter this bug on my HP Envy x360 Ryzen 5 2500U.
What worked for me as a workaround was to first upgrade the kernel to 4.20.7,
then remove "raven_dmcu.bin" and finally run "mkinitcpio -p linux".
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #9 from grak...@gmail.com ---
Raven_dmcu.bin can get packed in the initramfs Image if amdgpu is loaded at
boot. Check the initramfs by running “lsinitcpio /boot/name of initramfs.img”.
If you see raven_dmcu.bin in the image from
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #8 from edo...@hotmail.it ---
I encounter the same bug on my HP Envy x360, Ryzen 2500U.
Deleting raven_dcmu.bin and setting iommu=pt on kernel 4.20.5 still doesn't
solve the bug.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #7 from grak...@gmail.com ---
Can confirm that removing raven_dmcu.bin allows amdgpu to load. Note that
kernel 4.20 also requires iommu=pt kernel option.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #6 from Chris ---
Still having the same bug in kernel 5.0-rc4 and my raven_dmcu.bin also matches
to the previously attached bin file(sha256
a45972418d1c078afbd7884ffd58784954220759bc0d5464ce60165ffe1775bd).
However, in one of my
https://bugs.freedesktop.org/show_bug.cgi?id=109206
Nicola Orlando changed:
What|Removed |Added
CC||niki.o...@yahoo.it
--- Comment #5
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #4 from grak...@gmail.com ---
Created attachment 142979
--> https://bugs.freedesktop.org/attachment.cgi?id=142979=edit
Raven dmcu firmware
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #3 from grak...@gmail.com ---
Created attachment 142978
--> https://bugs.freedesktop.org/attachment.cgi?id=142978=edit
List of files in /lib/firmware/amdgpu
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #2 from David Francis ---
Could you give me a list of all files in /lib/firmware/amdgpu/?
And if it contains a file called raven_dmcu.bin, please attach that file.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #1 from grak...@gmail.com ---
Created attachment 142935
--> https://bugs.freedesktop.org/attachment.cgi?id=142935=edit
Kernel 4.20 log showing firmware loading crash
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=109206
Bug ID: 109206
Summary: Kernel 4.20 amdgpu fails to load firmware on Ryzen
2500U
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
69 matches
Mail list logo
