• Setting up dual monitors in Bookworm

    From bp@www.zefox.net@3:770/3 to All on Thu Feb 20 17:42:25 2025
    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.

    Thanks for reading,

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to bp@www.zefox.net on Thu Feb 20 19:02:34 2025
    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)
  • From bp@www.zefox.net@3:770/3 to bp@www.zefox.net on Thu Feb 20 19:37:27 2025
    bp@www.zefox.net wrote:
    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.


    Ok, now I'm totally confused. I switched the monitors back into their
    original configuration, which didn't work when first tried repeatedly,
    and now it works just as expected. Both monitors display the boot output,
    when the GUI is started I get the normal display on HDMI0 and the default wallpaper on HDMI1.

    If you've read this far, thank you!

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Paul Hardy@3:770/3 to All on Fri Feb 21 15:01:00 2025
    Ok, now I'm totally confused. I switched the monitors back into their original configuration, which didn't work when first tried repeatedly,
    and now it works just as expected. Both monitors display the boot output, when the GUI is started I get the normal display on HDMI0 and the default wallpaper on HDMI1.

    In my experience over 50 years, at least 85% of computer hardware problems
    are bad connections - cured by reseating boards or replugging cables.

    --
    Paul at the paulhardy.net domain

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Paul Hardy on Fri Feb 21 15:24:49 2025
    Paul Hardy <p.g.hardy@btinternet.com> wrote:
    Ok, now I'm totally confused. I switched the monitors back into their
    original configuration, which didn't work when first tried repeatedly,
    and now it works just as expected. Both monitors display the boot output,
    when the GUI is started I get the normal display on HDMI0 and the default
    wallpaper on HDMI1.

    In my experience over 50 years, at least 85% of computer hardware problems are bad connections - cured by reseating boards or replugging cables.


    Maybe that's it. One of the micro-HDMI ports is a noticeably tighter fit
    than the other. However, the problem didn't seem tied to that port. It's certainly true that modern, tiny connectors are much more frail than older, larger styles. Micro-HDMI seems to be asking for trouble. Same for USB-C.

    Thanks for writing,

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to Paul Hardy on Fri Feb 21 17:58:17 2025
    On 21/02/2025 15:01, Paul Hardy wrote:
    Ok, now I'm totally confused. I switched the monitors back into their
    original configuration, which didn't work when first tried repeatedly,
    and now it works just as expected. Both monitors display the boot output,
    when the GUI is started I get the normal display on HDMI0 and the default
    wallpaper on HDMI1.

    In my experience over 50 years, at least 85% of computer hardware problems are bad connections - cured by reseating boards or replugging cables.

    Not in mine. Probably because I always plugged things in properly.

    --
    "If you don’t read the news paper, you are un-informed. If you read the
    news paper, you are mis-informed."

    Mark Twain

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to bp@www.zefox.net on Fri Feb 21 17:59:23 2025
    On 21/02/2025 15:24, bp@www.zefox.net wrote:
    Paul Hardy <p.g.hardy@btinternet.com> wrote:
    Ok, now I'm totally confused. I switched the monitors back into their
    original configuration, which didn't work when first tried repeatedly,
    and now it works just as expected. Both monitors display the boot output, >>> when the GUI is started I get the normal display on HDMI0 and the default >>> wallpaper on HDMI1.

    In my experience over 50 years, at least 85% of computer hardware problems >> are bad connections - cured by reseating boards or replugging cables.


    Maybe that's it. One of the micro-HDMI ports is a noticeably tighter fit
    than the other. However, the problem didn't seem tied to that port. It's certainly true that modern, tiny connectors are much more frail than older, larger styles. Micro-HDMI seems to be asking for trouble. Same for USB-C.

    Thanks for writing,

    bob prohaska

    That's why my PIs go in boxes with extension cables to full size sockets
    --
    "If you don’t read the news paper, you are un-informed. If you read the
    news paper, you are mis-informed."

    Mark Twain

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to The Natural Philosopher on Fri Feb 21 19:00:47 2025
    The Natural Philosopher <tnp@invalid.invalid> wrote:

    That's why my PIs go in boxes with extension cables to full size sockets

    What sort of "boxes? Regular commercial enclosures, or something more special.

    My PIs are in normal cases, clipped to a shelf and connected by normal cables.

    Thanks for writing,

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to bp@www.zefox.net on Fri Feb 21 19:29:09 2025
    On 21/02/2025 19:00, bp@www.zefox.net wrote:
    The Natural Philosopher <tnp@invalid.invalid> wrote:

    That's why my PIs go in boxes with extension cables to full size sockets

    What sort of "boxes? Regular commercial enclosures, or something more special.

    I have a 3D printer :-)

    My PIs are in normal cases, clipped to a shelf and connected by normal cables.

    Thanks for writing,

    bob prohaska

    Rolling your own is more fun and better.

    --
    “Some people like to travel by train because it combines the slowness of
    a car with the cramped public exposure of 
an airplane.”

    Dennis Miller

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From druck@3:770/3 to bp@www.zefox.net on Fri Feb 21 21:08:55 2025
    On 21/02/2025 15:24, bp@www.zefox.net wrote:
    Paul Hardy <p.g.hardy@btinternet.com> wrote:
    In my experience over 50 years, at least 85% of computer hardware problems >> are bad connections - cured by reseating boards or replugging cables.


    Maybe that's it. One of the micro-HDMI ports is a noticeably tighter fit
    than the other. However, the problem didn't seem tied to that port. It's certainly true that modern, tiny connectors are much more frail than older, larger styles. Micro-HDMI seems to be asking for trouble. Same for USB-C

    Unless your Pi 4 or 5 with micro HDMI ports is going to be plugged in
    once and never touched again, I recommend getting one of the cases which
    bring out the video on full size HDMI ports. That will prevent the
    easily damaged micro connectors failing, particular if used with heavy
    adapters rather than micro HDMI cables.

    ---druck

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)