Oh yeah, I forgot back when I used like kubuntu I had to install one or two additional ssh things separately first
(I think it was just apt install openssh-server?)
All that avahi stuff is something to do with letting your computers find each other by their hostname.local in your LAN.
If you have more than one computer,
you should DEFINITELY try out ssh!
It's way easier than you think it is!
And sshfs is also awesome
-- it lets you mount stuff on another computer (even all the way up to its root),
and then just treat it exactly as though it was a directory on the local...
I dunno, I did a lot of rebooting and resetting before that, and it was only after I tried it under mxlinux that anything seemed to actually change...
Anyway, I think these are all my notes on useful things I learned / set up / improved / got more comfortable with while fixing this...
Hey, don't say that to me -- as far as I can tell, mxlinux solved the problem for me somehow,
which I wasn't expecting and still find utterly baffling.
I thought I did already set it as "solved?" It's showing up that way to me, at least...?
Yeah, I'd generally agree, but I guess my intuition is kinda leaning towards this indeed actually being that EDID problem
(well, assuming it's fixable at all, and not just old hardware burning out some buried components that aren't practically fixable...)
I did get the OSD working,
and did the...
... <facepalms> garr, of course, thank you. I didn't think to shorten it to "SM" when doing ctrl-f cuz I was just looking at the label on the monitor and it just says "SyncMaster",
but okay, that's at least one part of the problem solved!!
Thank you thank you!
(I almost didn't notice that...
Huh, weird... ohhh, I think cuz I used markdown to write the post,
and usually this forum does a good job automatically converting markdown to bbccode,
but I guess when I copied the markdown in I didn't remove that "mouseover text" feature, and the forum didn't know how to handle that?
ha ha, yeah, thanks. I just wanted to acknowledge that it's kinda goofy of me to basically go like
"Push a few buttons? Sure, I'll give that a try... EVENTUALLY."
But the thing is, I remain pretty sure that the problem/solution is most likely something like described here:
RepairEDID - Debian...
@KGIII Thanks! However, I already had it completely unplugged for several hours yesterday.
And in a similar vein,
I even found one person saying they once got problems from having the signal and power cables running together parallel
(ie, the power cable was "wirelessly" interfering with the...
I... huh? what? Are you... trolling or something? ... no, that would be bizarre -- I must just... not have been clear enough somehow...?
I'll try to restate it more clearly:
I do have snapper. That has the same backup/restore functionality as timeshift
I definitely will be buying a new monitor soon anyway,
but that's no reason to just junk this one.
And the problem started while messing around with the rotation in the software (ie xrandr),
so that is arguably something to do with linux.
And I just found this...
But the problem persists even while running the system of a live-USB
(where the monitor had worked before).
And every time you boot from a live-USB,
you get exactly the same system back into its prior state.
So since the monitor doesn't work on the live-USB system it used to work...
Thanks, but you mean like this, right?:
xrandr --output HDMI-1 --mode 1600x900
That doesn't work, because the monitor doesn't work...
When I plug the monitor in
-- even before I turn it on!
the buttons, including the power button, are weird flat touch-surface type things,
so I guess...
... what? Did you accidentally respond to the wrong post? Cuz neither of those seem relevant to my problem, no?
Like, I'm on opensuse tumbleweed,
but since the problem persists even while using a live-USB of a different distro (MX-linux),
the distro obviously isn't relevant
-- but rather, it...
So my monitor stopped working,
when I was messing around with the the rotation
(ie xrander -o [ normal, left, right, inverted ] stuff).
The monitor input is DVI (DVI-D Dual Link),
and the laptop's output port is HDMI,
so they're connected with an adapter.
All (I think) of the...
Oh wait, I forgot I also need to figure out the journal stuff...
There's a flag like
$journalctl -t systemd-sleep
which I think is the only thing I need.
I'm not sure how to check if there's anything other than systemd-sleep I should also use...
The manpage says:
Oh cool, thanks, that seems like probably everything I need to know!
Hmm, and $systemctl suspend -h
says there's a --dry-run flag,
which may help with testing things are functioning as you expect without needing to actually sleep/wake for every single test.
(I'll make sure to come back and add...
First of all, I'm not completely sure what the official terms are.
I think it's "suspend"/"resume",
with "sleep"/"wake" being synonyms
(and I'm not sure if there are any other common synonyms).
And there's other, related-but-different stuff, namely "hibernate",
which is much more rarely used...