Re: [Bug 206175] Fedora >= 5.4 kernels instantly freeze on boot without producing any display output

Re: [Bug 206175] Fedora >= 5.4 kernels instantly freeze on boot without producing any display output

[Linus Torvalds]

Dave, Alex,
 there's an odd bugreport on bugzilla, where Artem is seeing an odd
early-boot failure.

That one almost certainly has nothing to do with you guys, but see the
later odd (and apparently unrelated) report about some AMD graphics
firmware issue and a black screen.

                     Linus

On Tue, Jan 14, 2020 at 1:17 PM <bugzilla-daemon@bugzilla.kernel.org> wrote:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=206175
>
> --- Comment #9 from Matt Yates (matt@fast-mail.org) ---
> My BIOS vendor is "Insyde Corp.".  There is a TPM module.  When I disabled it,
> it caused my EFI boot entry to disappear, so I couldn't test it.
>
> However, I think we may have two separate problems.  I switched back from
> Fedora to Debian Testing, and the Debian installer upgraded the kernel from 5.3
> to 5.4 series prior to the first boot.  The 5.4 kernel booted up on first boot.
>  I could see boot messages scrolling, but the screen went to a black while
> trying to load lightdm because I did not have the "firmware-amd-graphics"
> package installed required for graphics.  After installing the amd graphics
> package, the 5.4 kernel freezes as before (right at the start of the boot
> process).  The 5.3 kernel boots as normal, and graphics work.
>
> The "firmware-amd-graphics" package (version 20190717-2) was the only thing I
> changed, so I guess the problem must be some sort of conflict with the amd
> graphics firmware and the 5.4 kernel.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [Bug 206175] Fedora >= 5.4 kernels instantly freeze on boot without producing any display output

[Alex Deucher]

On Tue, Jan 14, 2020 at 4:41 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Dave, Alex,
>  there's an odd bugreport on bugzilla, where Artem is seeing an odd
> early-boot failure.
>
> That one almost certainly has nothing to do with you guys, but see the
> later odd (and apparently unrelated) report about some AMD graphics
> firmware issue and a black screen.

Odd.  I have a similar picasso based raven laptop and it is working
fine with F31 and the latest 5.4.8 kernel.  I think the firmware is a
red herring as the driver won't load without it so if you don't have
it installed, the driver won't be running in the first place.  I'll
follow up in the bug report and ask him to file a new bug about the
amdgpu issue to avoid cluttering up the current report.

Alex

>
>                      Linus
>
> On Tue, Jan 14, 2020 at 1:17 PM <bugzilla-daemon@bugzilla.kernel.org> wrote:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=206175
> >
> > --- Comment #9 from Matt Yates (matt@fast-mail.org) ---
> > My BIOS vendor is "Insyde Corp.".  There is a TPM module.  When I disabled it,
> > it caused my EFI boot entry to disappear, so I couldn't test it.
> >
> > However, I think we may have two separate problems.  I switched back from
> > Fedora to Debian Testing, and the Debian installer upgraded the kernel from 5.3
> > to 5.4 series prior to the first boot.  The 5.4 kernel booted up on first boot.
> >  I could see boot messages scrolling, but the screen went to a black while
> > trying to load lightdm because I did not have the "firmware-amd-graphics"
> > package installed required for graphics.  After installing the amd graphics
> > package, the 5.4 kernel freezes as before (right at the start of the boot
> > process).  The 5.3 kernel boots as normal, and graphics work.
> >
> > The "firmware-amd-graphics" package (version 20190717-2) was the only thing I
> > changed, so I guess the problem must be some sort of conflict with the amd
> > graphics firmware and the 5.4 kernel.
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel