
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. ๐ฌ๐ง Language/ัะทัะบ/Sprache
- This is primarily an English-speaking community. ๐ฌ๐ง๐ฆ๐บ๐บ๐ธ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. ย
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Those modules, manโฆ theyโre the biggest cause ofโdare I say it?โbloat in the kernel.
For the few people here who may not know about it: thereโs a utility called modprobe-db that watches what kernel modules get loaded at runtime, and can generate a kernel build config file accordingly. Thereโs even an ArchWiki article about it. You need to keep it around for a while (e.g. several weeks or months) so it can get a proper sample of the modules you use; that way, your kernel can have all the modules you need (ask me how I know). If you do it right, however, you can slim down your compile time significantly.
I feel like the boot time is almost entirely uefi ram timing shenanigans these days
Fun fact about monitors turning on slowly: did you know Windows has a bluescreen code for that?
The WIN32K_POWER_WATCHDOG_TIMEOUT bug check has a value of 0x0000019C. This indicates that Win32k did not turn the monitor on in a timely manner.
That's right, Windows will panic and throw a bluescreen if your monitors take a little too long to wake up. Had the pleasure of dealing with this suddenly becoming an issue and causing wide bluescreens on wakeup after an update back in mid-2024, on any Surface Dock using DisplayPort with specific Acer monitors.
Woah woah..... is there someplace in the event logs where this would show? Does this mean that you cannot run a windows computer headless?
It gets logged in the event viewer, yeah. That's how I discovered it, on account of the screens not waking up in time to show the actual bluescreen. The users were only reporting that their computers were deleting all their windows when waking up. From their perspective, all they saw was their computer taking a mildly longer time to wake up from deep sleep and then losing their entire session, but what it was actually doing was hard rebooting.
Headless is fine, the bug was specifically triggered when a computer woke up and detected a monitor exists, but the monitor took some unspecified amount of time too long to wake up. It was also fixed at some point, I'm not sure when, but it went on long enough that we swapped dozens of cables because it specifically only happened on the ones using DisplayPort, not HDMI.
Oh shit, this may be the problem I've been having with my laptop dock at work
What's this "boot" of which you speak?
Do people really turn their machines off these days?
You've got to reboot after kernel updates, otherwise it can't load new modules. I've been confused at least twice why something didn't load until.I remembered the reboot.
I think the command "systemctl kexec" would like to have a word. Great command to know if you have a VM on a system you dont manage / share with others.
Gtk what replaced 'telinit 3'
Yes, I'm not wasting my hardware life and electricity for no gain.
Thermal cycling
Every day
yes
I hate my monitor for that. Entering the bios is guesswork about when to press a key if I remember what key to press. Also I can't turn it on too early before the PC or it will go to stand by after not receiving a signal for two seconds and then take even longer.
I want a monitor turns on and stays on.
Entering the bios is guesswork about when to press a key
What is there to guess? Just spam the fuck out of that key.
However, I also don't know why you're visiting the BIOS regularly.
Let me guess, samsung odyssey? Had one of those, never again.
Friend even called me that he has fucked up his pc rebuild - his Samsung monitor was just not waking up because it literally turns off.
All modern monitors are like this now. Dell, HP, Asus...
Doesn't detect input? Instant power off. Now you have to press the menu key every 5 seconds to try and find the input for your PC.
Beyond ridiculous. I have a Dell that's like 15 years old and it stays on for multiple minutes before going into power saving. It's glorious
I've learned the hard way that there's only one decent Samsung product line - from big appliances to little electronics - and it's their phones (and even those leave questions on privacy).
That's funny, while I still buy Samsung TVs, I hate their phones. So much of what their phones can do is usually locked to only working in Samsung's apps and those are universally dog shit. The phones themselves are also often privacy and user control nightmares.
Granted, there isn't a lot of good choices for phones these days. I'm still running an old LG phone and have been looking outside Android as my next possible solution. But, I also haven't had a reason to upgrade.
Have a Samsung TV and it's by far my least favorite. Turns off at random, takes forever to switch inputs, turns on at random...
As for phones I'm eyeing the Motorola RazrFold, since they're supposedly offering it Graphene-ready
Turn off all of the Energy Saving/Eco Solution crap. It will stop turning off and you will get s brighter inage that doesn't shift in brightness.
You should also switch to Movie mode in the picture settings and set dejudder/deblur (under Motion Clarity) to 0 while you're at it so it doesn't turn everything into 60 fps with fake frames.
I heard Samsung's SD cards are good
Their SSDs are/were considered amongst the best options, but I haven't looked into them since the 970 Evo days and they could be crap now for all I know.
Keep going. Kevin can get smaller, leaner, faster and hopefully has apparmor or selinux already.