On 7/1/23 02:59, Barry wrote:


On 30 Jun 2023, at 18:26, Robert Moskowitz <rgm@htt-consult.com> wrote:



On 6/30/23 13:13, George N. White III wrote:
On Fri, Jun 30, 2023 at 1:19 PM Robert Moskowitz <rgm@htt-consult.com> wrote:
I just rebooted after applying new updates.  In the past, this got the external video going.  Not this time.

VGA suggests an old monitor, so try to verify that it didn't fail by connecting to another system or playing
with configuration options until it works.  No point wasting time on a dead or dying monitor that is worth less
than the cost of proper disposal.

Actually the bottleneck is my KVM which only supports VGA.  The monitor works fine when I switch the kvm to another system.

In have seen issues with KVMs messing up EDID in tne past.
Suggest you test by pluging the monitor directly into your laptop.

My Win10 x140e system works just fine on this KVM right now.  I plugged this F38 x140e into the cables the Win10 uses and no external video.

So it is either the F38 software that decided to hickup between working Tuesday night and then failing Friday morning after many suspend/resume cycles while on the road.

Or the hardware died.  That is an option to test as I have another x140e that has F35 on it.  "All I need to do" is shut down, move drive and memory, power up and see what happens.   Yeah, that is all....

So first try and see if it is software as this is not the first time for this.  I would have it rather frequently on F35, but worst case a reboot took care of it.  That did not happen here (i.e. rebooting restoring external monitor).






"xrandr --query" may have some useful info.

# xrandr --query
-bash: xrandr: command not found



Check "inxi -Fzx" for missing graphics hardware.

# inxi -Fzx
-bash: inxi: command not found

FYI to install a command you can do this:

$ sudo dnf install /usr/bin/xrandr
$ sudo dnf install /usr/bin/inxi
Etc.


  There should be details in "sudo journalctl -b N"
(sudo gives details that are not included when run as regular user).   Look at a boot that worked for lines
related to the external monitor and compare with what is in the latest boot.

That may take for ever.  what file do I grep to look for dates when it worked?  I booted the system Monday after a kernel install and the video worked fine then.


One thing to watch is EDID -- some older monitors have bad data that newer drivers reject.

And what is EDID?  And would that come through the KVM?

thanks


--
George N. White III


_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue