From nobody Thu Nov 27 15:47:47 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dHLRV4smSz6HTdB; Thu, 27 Nov 2025 15:47:50 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta004.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dHLRV2d1tz40P1; Thu, 27 Nov 2025 15:47:50 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; none Received: from shw-obgw-4002b.ext.cloudfilter.net ([10.228.9.233]) by cmsmtp with ESMTPS id OdQBvKetEPzKyOeDlvQ1ua; Thu, 27 Nov 2025 15:47:49 +0000 Received: from spqr.komquats.com ([70.66.136.217]) by cmsmtp with ESMTPSA id OeDjvRhB7UZWaOeDkv26sK; Thu, 27 Nov 2025 15:47:49 +0000 X-Auth-User: cschuber X-Authority-Analysis: v=2.4 cv=Ls6fC3dc c=1 sm=1 tr=0 ts=692872a5 a=h7br+8Ma+Xn9xscxy5znUg==:117 a=h7br+8Ma+Xn9xscxy5znUg==:17 a=IkcTkHD0fZMA:10 a=6UeiqGixMTsA:10 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=YxBL1-UpAAAA:8 a=pGLkceISAAAA:8 a=CeIHQudJlSsTNqHkSmQA:9 a=QEXdDO2ut3YA:10 a=LK5xJRSDVpKd5WXXoEvA:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy.cwsent.com [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id 4056FD8; Thu, 27 Nov 2025 07:47:47 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (Postfix) with ESMTP id 2CDA330E; Thu, 27 Nov 2025 07:47:47 -0800 (PST) Date: Thu, 27 Nov 2025 07:47:47 -0800 From: Cy Schubert To: FreeBSD User Cc: Lars Tunkrans , freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: FreeBSD/X11: Howto revive DisplayPort? Message-ID: <20251127074747.2c250a85@slippy.cwsent.com> In-Reply-To: <20251127062631.5d8026c4@hermann> References: <20251126163059.3376d3e8@hermann> <77c2a2fb-ac5f-4b4a-98c6-660a39ee87b2@gmail.com> <20251127062631.5d8026c4@hermann> Organization: KOMQUATS X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd16.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-CMAE-Envelope: MS4xfCafrCaaoKsnHc/ECiGiCl5IxalzKGTTEPODlHQy99GpFkFx9/MtRNqJAXPmO4JvHHDtwcglZhzSzPK6HecPhGduWpRF7Vt5pyxV47mkRfPazDLw8ITW Lj49GcdreQp7WpN8XJ5sben0XW3q38cVantFR15EOEhCkoOQShhwWfsnmqtFHAfKmPMZ4WVKZ0iqUcnlke33WzAFKpBRljReQqcDhwUWBH/RWwow/hUwGPto eLNWegJpa6e9Eg0snEFWr9TYMT7velJvfO4652qgiqkS2u3HmNSb0yqPtfZN3I5+6B6LRFSTVEAl2qbHk2jSCQ== X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dHLRV2d1tz40P1 One of HP 840 G5's docking station's DPs is connected to a VGA KVM switch via a DP to VGA connector. Confirmed, this is an issue. The VGA KVM switch is also connected to my employer's HP 840 G9, also via a DP to VGA connector. No problems there. Though that machine uses the newer Thunderbolt docking station. Given that it's a newer machine with a newer docking station I think the comparison only goes so far. Whether this is a FreeBSD or a UEFI BIOS problem isn't quite understood by me. When booting the FreeBSD machine and if the KVM is not switched to the FreeBSD machine, the text mode console will have the wrong geometry. Even in single user the login prompt is far below the bottom of the monitor. But once XDM has started it assumes a graphic geometry that fits the laptop's screen, not the external monitor. I have a script that disables the LVDS when the VGA is connected. I suspect that this problem will require more tinkering (not by myself) to better understand it. There are too many variables to say it's a single issue. Another issue is, X segfaults on occasion on this machine. The segfault always occurs when firefox is active. The screen goes blank as drm-66-kmod (I think) is corrupted. (This happens maybe once or twice a month, not enough to pull me away from other projects.) Are you talking about this or the first issue above? --=20 Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e**(i*pi)+1=3D0 On Thu, 27 Nov 2025 06:31:34 +0100 FreeBSD User wrote: > On Wed, 26 Nov 2025 22:31:20 +0100 > Lars Tunkrans wrote: >=20 > > HI > >=20 > > =C2=A0 =C2=A0Yes I=C2=A0 have=C2=A0 same experience. > >=20 > > =C2=A0 =C2=A0I beleive its because the=C2=A0 DDC/ EDID=C2=A0 =C2=A0inf= o sent from screen over=C2=A0=20 > > the=C2=A0 connection cable > > =C2=A0 =C2=A0is=C2=A0 lost=C2=A0 if=C2=A0 the=C2=A0 KVM=C2=A0 and scre= en is not connected to the computer=20 > > at start up. > > =C2=A0 =C2=A0 If I make sure that=C2=A0 the screen is attached to=C2= =A0 the computer when=20 > > the computer powers up > > =C2=A0 =C2=A0 =C2=A0a=C2=A0 Usable resoultion/timing is selected by th= e graphics card. > >=20 > > =C2=A0 Regards. =20 >=20 > Exactly. > this behaviour is observed by myself on FreeBSD, Linux or Windows, on the= contrary, seems > to have a solution to reestablish a DP connection, so it might be possibl= e on FreeBSD > also (but is somehow by default disabled, I hope). >=20 > Having for computer attached to one KVM, three of them are FBSD boxes and= one is a Linux > based commercial product provided by my employer leaves me with trouble w= hen powering up > all machines. >=20 > Kind regards, >=20 > oh >=20 > >=20 > >=20 > > Den 2025-11-26 kl. 16:37, skrev FreeBSD User: =20 > > > Using FreeBSD CURREN and FreeBSD STABLE/15. > > > Also, most systems are attached to a KVM switch, connected via DP. > > > > > > Hosts booting all UEFI. > > > > > > On hosts using X11/xdm GUI, switching forth and back to the output/ho= st I want to use > > > DP does obviously not "lose" DP output, so after graphics has been in= itialized I'm > > > able to see the GUI. > > > > > > The situation is completely different with plain consoles, provided b= y FreeBSD's > > > EFI/UEFI simple framebuffer device driver. Working on the console on = one host, > > > switching to another host, working there and trying to switch back le= aves me with no > > > output anymore! I see this behaviour with different types of KVM swit= ches I have at > > > hand. > > > > > > Can this behaviour be changed, even with no X11? > > > > > > Thanks in advance and wishes, > > > > > > O. Hartmann > > > =20 >=20 >=20