From: Thomas Zimmermann <tzimmermann@suse.de>
To: Nick Bowler <nbowler@draconx.ca>
Cc: Doug Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
regressions@lists.linux.dev
Subject: Re: PROBLEM: AST2500 BMC video output disabled by reboot (regression)
Date: Fri, 10 Oct 2025 09:10:48 +0200 [thread overview]
Message-ID: <22de3e4b-bce4-43ec-8c62-55a7fbbf3baa@suse.de> (raw)
In-Reply-To: <hyyyuqsyf7c3ed2ku57fp4sjwkpcacygtrwnkgupn2xdq7ez4u@sg6xeg4shkdd>
Hi
Am 10.10.25 um 01:56 schrieb Nick Bowler:
> Hello,
>
> On Tue, Oct 07, 2025 at 10:51:29AM +0200, Thomas Zimmermann wrote:
>> Am 04.10.25 um 02:31 schrieb Nick Bowler:
>>> But it introduces a new problem: the screen no longer turns back on if
>>> I boot the patched kernel from the "display off" state. The unpatched
>>> 6.17 kernel would at least turn the display back on from this.
>>> Furthermore, rebooting from this state keeps the display off.
> [...]
>> Thanks again for testing. Looks like your BMC is especially picky about
>> these settings. :)
>>
>> Attached are two patches; each trying to eliminate one of the possible
>> causes. Could you please test them individually and report the results?
> 0001-ast-Use-VGACR17-sync-enable-and-VGACRB6-sync-off.patch
> ^ Everything appears to work fine with this patch applied on
> top of 6.17.
That's great news. I'll prepare the patch so that it can go into the
kernel. Thanks again for testing.
Best regards
Thomas
>
> 0001-ast-Use-VGACR17-sync-enable-and-VGASR01-screen-disab.patch
> ^ This one has the same problem as the last patch: the screen
> does not turn back on if it was previously off during bootup.
>
> Thanks,
> Nick
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-10-10 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 4:26 Nick Bowler
2025-04-28 20:40 ` Doug Anderson
2025-04-30 13:28 ` Nick Bowler
2025-04-30 17:05 ` Doug Anderson
2025-04-30 17:52 ` Nick Bowler
2025-04-30 23:31 ` Doug Anderson
2025-08-29 13:07 ` Thomas Zimmermann
2025-09-17 15:14 ` Nick Bowler
2025-09-18 2:04 ` Nick Bowler
2025-09-18 10:46 ` Thomas Zimmermann
2025-09-18 11:17 ` Thomas Zimmermann
2025-10-01 7:26 ` Thomas Zimmermann
2025-10-04 0:31 ` Nick Bowler
2025-10-07 8:51 ` Thomas Zimmermann
2025-10-09 23:56 ` Nick Bowler
2025-10-10 7:10 ` Thomas Zimmermann [this message]
2025-09-17 9:22 ` Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22de3e4b-bce4-43ec-8c62-55a7fbbf3baa@suse.de \
--to=tzimmermann@suse.de \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®