On Tue, Mar 15, 2022 at 10:47 PM Brandon Nielsen <nielsenb(a)jetfuse.net> wrote:
On 3/15/22 3:04 PM, Peter Robinson wrote:
>> Was hoping to add a bit of test coverage, and ran into a strange issue.
>> The beta Server compose boots, but there is no VGA output after the
>> initial rainbow, u-boot, GRUB, and "Booting..." text (using an
>> adapter) on a Raspberry Pi 3b. Cockpit works so boot clearly succeeded.
>> Fedora Minimal for the same compose works as expected with text based
>> initial setup appearing over VGA.
>> Is this a known issue or intended behavior? I couldn't find anything in
> The HDMI to VGA adapters have always been as ropey as hell on the RPi,
> in fact they were never particularly great even on the OLPCs back in
> the day either.
> They're also very variable from device to device so it's very much a
> case of it may or may not work but we don't really get a lot of
> reports either way these days TBH.
I figured that was probably the case. The only thing of note I see in
the logs is:
Feb 16 00:01:21 fedora kernel: of_clk_hw_onecell_get: invalid index 15
Feb 16 00:01:21 fedora kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed
to get clock: -2
Feb 16 00:01:21 fedora kernel: vc4-drm soc:gpu: failed to bind
3f806000.vec (ops vc4_vec_ops [vc4]): -2
Interesting that I don't see the issue on minimal.
It's not really, your not driving the the 3D engine or trying to push
it's resolution to the max that the display can support and hence
juggling between the usually straight forward EDID report-able display
and what the VGA interface can do. For text you can generally request
the basics and it'll work, for graphics you wan the best so you need
to actively query and that generally fails in this game of musical