INTL 3:770/1 3:770/3
REPLYADDR bp@www.zefox.net
REPLYTO 3:770/3.0 UUCP
MSGID:  09796e75
REPLY:  c56e61e4
PID: SoupGate-Win32 v1.05
bp@www.zefox.net wrote:
> I'd like to try dual monitors with a Pi5 running Bookworm and Wayland.
> The system is up to date as of this writing.
>
> The system was initially configured with a Dell HDMI 1920 by 1080
> monitor as the primary, so I added  a Dell DVI 1600 by 900 as the
> secondary using a DVI-to_HDMI adapter on the cable..
>
> After reboot the system came up with the 1600 by 900 as primary,
> and the Screen Configuration utility doesn't notice the original
> primary monitor, which was powered  on during boot.
>
> Switching the monitors between hdmi ports makes no difference,
> the origninal primary monitor is ignored and the 1600 by 900
> monitor is primary.
>
> If I run xrandr, it reports:
>
> Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192
> HDMI-1 connected primary 1600x900+0+0 (normal left inverted right x axis y
axis) 443mm x 249mm
>    1600x900      59.98*+
>    1280x1024     75.02    60.02
>    1152x864      75.00
>    1024x768      75.03    60.00
>    800x600       75.00    60.32
>    640x480       75.00    59.94
>    720x400       70.08
> HDMI-2 disconnected (normal left inverted right x axis y axis)
>
> The "maximum 8192 x 8192" seems absurd.
>
> HDMI-2 is NOT disconnected, it's connected and powered up.
>
> Is there a fix for this problem? I do have a couple other
> monitors (natively DVI with HDMI adapters) but none are
> exact matches. For now I'll try switching away from Wayland
> to see if that helps, but would rather not, long term.

I just tried each of the three options for a GUI; X11,
Wayland and a third which appears to be Wayland with a
different window manager.

All fail to detect the dual monitor setup, using instead the
older 1600 by 900 display and being completely oblivious to
the second monitor connected and powered on.

I do notice that during boot, the status LED on the unrecognized
monitor briefly goes from amber (asleep) to blue (awake), suggesting
that the monitor does detect some activity on the HDMI port it's
connected to. Unfortunately it goes back to sleep in about a second.

Thanks for reading, and any suggestions.

bob prohaska

--- SoupGate-Win32 v1.05
 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 19/10 103/705 105/81 106/201 124/5016 128/187 129/305
SEEN-BY: 153/757 7715 154/110 218/0 1 601 700 840 220/70 221/1 6 360
SEEN-BY: 226/17 30 100 227/114 229/110 111 114 200 206 275 300 317
SEEN-BY: 229/400 426 428 470 550 616 664 700 705 240/1120 266/512
SEEN-BY: 267/800 291/111 292/854 301/1 113 812 310/31 320/219 322/757
SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1
SEEN-BY: 770/3 100 330 340 772/210 220 230 902/26 2320/105 5020/400
SEEN-BY: 5020/1042 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426