Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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.
Context: Windows Update bricking stuff
I learned one morning that a cmos battery could become a resistor. It can fail in a way that it's not working nor completely dead but passes just enough current to make a server motherboard that otherwise might A: Work, B: detect it's dead/missing and boot anyway with defaults to instead C: just freeze and not do anything. That was a fun full day of time wasted.
Using the capital punishment symbol instead of the killed in action symbol suggests windows was executed after the war (likely by installing linux lol)
There are variations of the Skull and Crossbones here that have specific meaning?
On wikipedia, capital punishment is a skull and amd bones, killed in action is a christian cross
Thats kinda shitty its a cross. Like holding one religion above the others on a fucking encyclopedia.
It is not a Christian cross, the symbol is the dagger β which is also often used for adding post-scriptum information or challenging parts of a text.
People often mistake it for a cross, given the look, but there's no actual preference towards any religion here.
The cross is an entirely different unicode character: β
Huh TIL. I searched just to confirm and its listed even on wikipedia itself. Thanks for claifying.
Is there a symbol for a zombie, something that supposedly died many times over but keeps coming back?
Because KIA takes way too much room on the page.
I have a motherboard in a state where it won't boot unless you pull and reinsert the cmos battery. After this it will boot exactly once.
It will also boot without issue if you don't have a cmos battery at all. This is obviously not ideal.
I wonder if these issues are related? I purchased the motherboard second hand in this state about a year ago. So it is far too early for this update, but it remains a mystery.
Have you tried putting in a new battery?
Ain't nobody got time for that
I had something kiind of similar once, where it would only boot after trying to boot once, letting it run a bit in idle, and then rebooting where it would actually succeed. Turned out I forgot to put the clear cmos jumper back to neutral after i reset cmos.
So my best guess (other than new battery) is check the jumpers maybe
What? The penguin bird is so fat that it is bigger than a window? Or... I know: "Stick penguin into hole!" But why? Nah... Hey, can somebody read ancient Egyptian?
Does "Secure Boot" actually benefit the end user in any way what so ever? Genuine question
For you? No. For most people? Nope, not even close.
However, it mitigates certain threat vectors both on Windows and Linux, especially when paired with a TPM and disk encryption. Basically, you can no longer (terms and conditions apply) physically unscrew the storage and inject malware and then pop it back in. Nor can you just read data off the drive.
The threat vector is basically βour employees keep leaving their laptops unattended in publicβ.
(Does LUKS with a password mitigate most of this? Yes. But normal people canβt be trusted with passwords and need the TPM to do it for them. And that basically requires SecureBoot to do properly.)
Thatβs only one use of secure boot. Itβs also supposed to prevent UEFI level rootkits, which is a much more important feature for most people.
True. Personally, Iβm hoping for easier use of SecureBoot, TPM and encryption on Linux overall. People are complaining about BitLocker, but try doing the same on Linux. All the bits and pieces are there, but integrating everything and having it keep working through kernel upgrades isnβt fun at all.
It prevents rootkit malware that loads before the OS and therefore is very difficult to detect. If enabled, it tells your machine to only load the OS if it's signed by a trusted key and hasn't been tampered with.
Well yes, assuming that:
With this you can make your laptop very tamper resistant. It will be basically impossible to tamper with the bootloader while the laptop is off. (e.g install keylogger to get disk-encryption password).
What they can do, is wipe the bios, which will remove your custom keys and will not boot your computer with secure boot enabled.
Something like a supply-side attack is still possible however. (e.g. tricking you into installing a malicious bootloader while the PC is booted)
Always use security in multiple layers, and to think about what you are securing yourself from.
Yes, as long as you get the option to disable it. And use custom keys.
It's uh, more secure.
I enrolled custom keys and bricked my motherboard π
Same. Should've listened to securebootctl telling me the key was malformed.
My keys were fine, I'd used them on a previous system. My best guess is boot failed because GPU firmware wasn't signed with my keys, only Microsoft's keys. And of course, I can't just CMOS clear, and I don't have an iGPU. It's crazy that an OS can brick my motherboard; I'd be a lot more forgiving if a BIOS option bricked it, but exposing a "brick me" option in efivars for any ring 0 software to press??
It's so secure that the first thing under Wikipedia's entry for Secure boot is Secure boot criticism
Yes this is a real, I'm not joking.
You can set it to run only specifically signed binaries on boot.
Specifically signed by anyone with a key - which, considering multiple where leaked over time - is everyone.
I had this problem at work a week ago or so, at least with Fujitsu PCs. For them, the main cause isn't an empty CMOS battery, but rather that Fujitsu generally had too little BIOS cache, since there is nothing about it in the UEFI standard. The update basically overfilled that cache, rendering the BIOS completely unusable. The POST doesn't even go through fully.
The PC are sort of bricked, you gotta put the mainboard into recovery mode, put the ROM file on a freeBSD formatted stick and wait until you see instructions on the screen. Follow them, restart the PC. I recommend setting the BIOS to the optimized default settings, as not doing that might make the boot of Windows pretty slow in some cases. I did hear that it can delete the keys from the TPM, but I haven't seen that with my PCs at work.
JFC
Wait... Microsoft is shit?!
What all am I looking at here? Or is this all meme?
It's a meme about how draining the cmos battery bricked some PC's, I think. It's formatted like the Wikipedia sidebar summary for articles on wartime battles.
Wow what a super cool website without cookie opt-out.
Use Reader View in Firefox. I never accepted the cookies. π
Not only that, if you try to click any of the links, like the partner list or privacy statements, it takes you to another page with the same pop-up over it... So you have to accept the shit to read their disclosures... What a shitty website, unless the purpose was to keep the information a secret, then it works great because I sure as shit didn't read it.
The URL (borncity) has nothing to do with the topic (Windows Update), that's a sign of an SEO content farm
But how many civilians cannibalized?
we prefer to classify that a 'charitably donated meals'
There are no civilians when profit is involved.
Allen&Heath sound controllers on Ubuntu had a funny failure too. It's touchscreen and extra screen would show nothing on boot although the sound controls (for one surface config) works. In order to fix that, you need a replacement battery, a keyboard to boot into it's BIOS and a password they don't disclose publicly. I revived a couple of these by a pure luck of discovering someone posting said passwords 5+ years ago. It's so hostile I hate it.