While not talked about as much as the Intel CPU security mitigations, Intel graphics security mitigations have added up over time that if disabling Intel graphics security mitigations for their GPU compute stack for OpenCL and Level Zero can yield a …www.phoronix.com
Well, I'm back online after a 4 hour blackout due to the heat in Brooklyn.
I found out that my ISP Optimum had issues with their equipment in Brooklyn due to the heat and humidity set on by this week's weather.
Now I'm worried that things will be really harsh on my equipment in the living room.
Any suggestions on how to keep the modem/router from overheating and causing problems?
Simplest thing is to drag your fridge over to wherever your equipment may be and leave the door open at all times. 🙃
Seriously though, most consumer gear can handle up to 130F at a minimum. If you're worried, just point a fan at it.
Comment: X11 is very far from dead – no matter if some want it to beLiam Proven (The Register)
Hey, there is an entire wayland bad x11 good article hidden in the last 4/5ths of the article!
Anyway, the article seems to argue that "toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg".
It seems to me that now that wayland has become the clear focus of development, most devs sinply want X11 to remain as a legacy element, not causing unnecessary issues elsewhere, just remaining on lts.
The train has sailed, wayland is the norm and everyone is working on implementing the last leftovers the article is parading in its weird latter half, rather than through much greater efforts achieving worse results in patching up X11.
They should have forked X 10 years ago, when people were still interested in improving it.
It being left behind is a logical and fully adequate explanation, arguing eee makes little sense when wayland is clearly a simpler protocol. If you wanted to harm linux or foss, and your plan was the transition to wayland and freezing of X11 development, I would call you stupid.
I don't see why this fork, and this article, have to get conspiritorial about something this easily explained.
Now that we have the conspiracy crap addressed: wayland defense time
The Reg FOSS desk is nearing 60, [...] He doesn't care about [...] high and variable refresh rates, tear-free video,
My fancy new monitor I got in '22 doesn't work on X11. I'd have to replace my other monitors with matching new ones for a few grand, or keep watching videos and all else at 15fps, getting a headache. If you wanna keep your crt, why not keep an ancient X11, why this fork?
X11 doesn't support normal modern hardware, my monitor wasn't even special, it's just higher fps than my other monitors and 4k.
Wayland does not currently allow controlling window position. This means that when you open KiCad, it cannot remember where you last placed your windows.
The window pos remembering api (name made up by me, I forgot the real one) has been finalized, and will be in this or the next KDE version, etc.. The wayland people are fixing the criticism faster than the critics can shorten their list of remaining issues.
.
uhhhh... ok that's all the wayland criticism, 'cause surprise, the last 2/5ths of the article are actually a rant about ... gnome? I think?
Something about no more shortcut support or how removing title bars is bad and the gnome disk manager has bad ui.
Idk my shortcuts are better than ever and my title bars were still there last time I checked.
But maybe this "big no-accessibility" is why absolutely no tiling dwms have ever been seen for wayland ever. If you switch to wayland you will have to tile by mouse exclusively, you heard it here first!
Hyprland and dwl are actual, existing tiling dwms for Wayland.
i wonder what you thought "dwl" stood for lol
over_clox likes this.
Not in the way you're probably thinking, which I assume is like in a Windows-y kind of way.
Finding an exploitable escalation of privileges in Linux is rare, but unpatched machines get hacked all the time, but the world of worms, and such is kind of gone.
The way most end-user machines get compromised these days is by supply chain attacks, undiscovered zero-day exploits, user error, and social engineering. Groups that discover zero-days usually keep it close the vest, and they don't get found for long periods of time after they've been out in the wild.
The way most corporate machines get attacked is social engineering, supply chain, and zero-days. Mostly crypto mining schemes and enterprise-level ransoms for data.
All the Windows botnets you hear about out there are largely unpatched machines exposed to the internet in various stupid ways that groups prey on to take control of.
Edit: Forgot about leaked secrets. Lots of companies get hit from plaintext secrets that get out in the wild via various stupid means.
Carrots? Don’t you mean waffles!!? HAHAHAHHAAHHAHAHAHAHA
fucking kill me I hate that that exists in my brain
If it were real facts we'd just call them facts.
If it were real medicine we'd just call it medicine.
If it were real news we'd just call it news.
Alternative rock is fine.
In my language, 'alternative' is somewhat synonymous with 'progressive' (though we still have the bullshit meaning of 'alternative facts', 'alternative medicine'). Is that not a thing in English, too? We rarely have an original thought when it comes to words like this.
Iran's foreign minister warned earlier Sunday that the Islamic Republic "reserves all options to defend its sovereignty" after U.S. airstrikes.Spencer Kimball (CNBC)
I don't know why, but I always have this mental image of people who identify as male/masculine to just have their living spaces look like a dumpster (okay maybe its a bit hyperbole, not a literal dumpster, but you know what I mean), while people who identify as female/feminine to be extra tidy? (Perhaps its mainstream media's portrayal affecting my subconscious?) Is this actually true?
Sorry if this sounds offensive, I don't mean it that way.
Churbleyimyam
in reply to cm0002 • • •I've seen this being recommended for audio production but was put off disabling it because I didn't understand what it was. I'd like the performance gain though.
Has anyone else here disabled it?
SteveTech
in reply to Churbleyimyam • • •The common sketchy performance advice is to disable mitigations in the kernel, this post is about disabling mitigations in Intel's userspace graphics stack because it's already checked in the kernel.
Assuming you meant disabling kernel mitigations, since AFAIK audio stuff doesn't usually use OpenCL:
Nah, my understanding is it's not worth it on newer CPUs, and in some cases, the microcode expects things to be mitigated for best performance. Older CPUs (pre-2019ish) it does make a difference though.
But you're welcome to benchmark it, and see if it makes a worthwhile difference on your CPU. Kernel mitigations are easy enough to turn on and off.