Timur Tabi
2025-Apr-08 15:59 UTC
[6.13.6 stable regression?] Nouveau reboot failure in r535_gsp_msg_recv()
On Mon, 2025-04-07 at 21:09 +0100, David Woodhouse wrote:> It *was* working, as long as I could tolerate it being scaled to 200% like > the internal display. It *did* light up the external display just fine.Ok, the only thing I can think of is to do a bisect between 6.13.4 and 6.13.6 to determine the commit that broke it.
David Woodhouse
2025-Apr-08 16:21 UTC
[6.13.6 stable regression?] Nouveau reboot failure in r535_gsp_msg_recv()
On Tue, 2025-04-08 at 15:59 +0000, Timur Tabi wrote:> On Mon, 2025-04-07 at 21:09 +0100, David Woodhouse wrote: > > It *was* working, as long as I could tolerate it being scaled to 200% like > > the internal display. It *did* light up the external display just fine. > > Ok, the only thing I can think of is to do a bisect between 6.13.4 and > 6.13.6 to determine the commit that broke it.I meant, the proprietary driver was working. It messed up when I asked it to scale the displays, but that's a separate issue. It *did* light up the external DP display on the USB-C port. If I set the BIOS to use the external display at boot time, that works and Linux starts booting using the USB-C monitor ? until nouveau inits, at which point it stops working. Is it useful to provide the logfiles from debugfs and drm.debug=0x100 logs from such a boot? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5069 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20250408/d26fdff6/attachment-0001.bin>