[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Out of Range Monitor Problim




On 6/29/2023 1:56 PM, Felix Miata wrote:
Stephen P. Molnar composed on 2023-06-29 11:50 (UTC-0400):

Felix Miata wrote:
Stephen P. Molnar composed on 2023-06-29 06:55 (UTC-0400):
I have Bullseye currently installed on my main Linux platform.
When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz
error.
What was the system stated immediately before trying? IOW, was it
suspended, off, hibernated, asleep?
It's hard to help much when you tell so little about your current
system. Was your cat sleeping on it when you came to use it? Is it a
laptop? How many displays are attached? What GPU(s)? Which DE or WM?
Inxi -GSaz is a good way to provide needed system info, if you can
get logged in successfully somehow, maybe by rebooting, or
Ctrl-Alt-F3 then Alt-F7/F1 cycled a time or three, or cycling the
display's power. Is your video cable loose? Ancient? Is your display
ancient, or VGA (analog)? Is your display under warranty? Maybe it's
hinting you'd be wise to upgrade to Bookworm, or shouldn't be
tempted. How old is it?
So many unanswered questions. :(

First of all, I don't have a cat, so let's forego any further cattiness.
It really wasn't meant to be humorous. Horizontal configurations with top vents
are attractive to cats napping, leading to hair buildup collecting on components,
overheating, and strange behavior over time.

I built the system on 6/26/2015 and have kept up on maintenance
ASUS M5 A97 R2.0 Motherboard BIOS 2603
I see no video outputs on this one:
https://www.newegg.com/asus-m5a97-le-r2-0/p/N82E16813131872

AMD FX-8320 Eight-Core Processor 3500MHz
No GPU found on that either:
https://www.amd.com/en/products/cpu/fx-8320

8179 MB (DDR 1600MHz)
Not likely system RAM has anything to do with an out-of-range display problem.

The display is a 23 in LG flat screen (3 years old).
My then 3 year old LG from 2017 needed new LED strips, shortly after its warranty
expired. LG was Goldstar before its name change.

All the cables are firmly attached.
When did that happen last, 3 years ago? eBay stuff, or good stuff, and what type?
USB-C to DP? HDMI to HDMI? DVI to HDMI? Any adapters? These come in many flavors.
Is a KVM switch involved?

All components were purchased from tho Microcenter herein Columbus.
It could, in fact, connect to a TV on the LAN in the same room, But now I get form the TV: Computer No signal is it on?
inxi -GSaz, in safe mode, returns-  bash: inxi: command not found


Is inxi that hard for you to do? No help from rebooting, rebooting in failsafe
mode, or trying a TV instead of your 23?
# inxi -GSaz
System:
   Ho st: ara88 Kernel: 5.10.0-20-amd64 arch: x86_64 bits: 64 compiler: gcc
     v: 10.2.1 parameters: BOOT_IMAGE=/vmlinuz root=LABEL=<filter> noresume
     ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0
     radeon.cik_support=0 amdgpu.cik_support=1
   Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
     vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
   Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu
     v: kernel alternate: radeon arch: GCN-2 code: Sea Islands
     process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1, DVI-D-1,
     HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f
     class-ID: 0300
   Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu
     dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
   Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
     s-diag: 944mm (37.18")
   Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-left model: NEC EA243WM
     serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
     size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
     max: 1920x1200 min: 640x480
   Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l
     model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60
     dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
     ratio: 16:9 modes: max: 2560x1440 min: 720x400
   Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-right model: Dell P2213
     serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
     size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
     max: 1680x1050 min: 720x400
   Monitor-4: VGA-1 mapped: VGA-0 pos: middle-r model: Lenovo L2251x Wide
     serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
     size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes:
     max: 1680x1050 min: 720x400
   API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD KAVERI (DRM 3.40.0
     5.10.0-20-amd64 LLVM 11.0.1) direct-render: Yes

Out of range is a not infrequent occurrence here, with 11 or so displays shared
among 30+ computers. Reasons are many, including software that works the first
time, then barfs until a restart of X, or the whole PC. Asus' BIOS aren't stellar
performers either. Two of my FM2+ Asus motherboards from 2014 died over a year
ago, leaving me with an AMD PRO A8-8650B on the shelf, and an AMD A10-7850K moved
to an Asrock. Some UEFI BIOS don't like to play nice with their connected
displays. I see more out-of-range from them than from the oldies.

It wouldn't hurt for us to see /var/log/Xorg.0.log in addition to inxi output. If
not found, look for ~/.local/share/xorg/Xorg.0.log.

cat for both logs returns:  no such file or directory

Let me pose a hypothetical - Would installing Debian 12 on a different drive boot. or would I (most likely) muck-up the entire computer?

--
Stephen P. Molnar, PhD
https://insilicochemistry.net
(614)-312-7528
Skype: smolnar1


Reply to: