Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wsx
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
wsx
11y ago
Sorry, I forgot about ACPI :) Now that you posted this, I think I recall one friend telling me that hibernation killed his laptop. But this was over 10 years ago and I only know about one such incident. OTOH, what UEFI gave us is basically
2.
▲
by
wsx
11y ago
Well, it's still a solution to problem which shouldn't exist in the first place. Before UEFI, x86 boxes were hard to brick unless you really knew what you were doing.
3.
▲
by
wsx
11y ago
Well, the insanity would rarely enter official releases. There is no comparison between the bugginess of BIOSes and OpenSSH.
4.
▲
by
wsx
11y ago
> These hardware vendors at all levels - storage controllers, chipsets, radios, and more all have absolutely no QA on their code Hardware vendors do have QA, but it's mainly about ensuring that things work, not about trying to break
5.
▲
by
wsx
11y ago
> I just know the next laptop I buy will be whatever the highest end liberated Chromebook at the time is, preferably without cancerous firmware blobs that control everything, but that seems unlikely considering how anti-freedom Intel is.
6.
▲
by
wsx
11y ago
I'm not sure how moving boot settings from one OS-accessible place to another improves security. If you are bothered by people booting unauthorized disks on your hardware, enforce signature checking on OS images.
7.
▲
by
wsx
11y ago
The thing I find particularly hard to grok is that they came up with this idea of putting disk-specific boot information on the motherboard. Then it was one simple step for board manufacturers to mix this with low level hardware settings wh
8.
▲
by
wsx
11y ago
Probably not in this case, because affected systems don't give even a slightest sign of life.
9.
▲
by
wsx
11y ago
It's very funny until they drop BIOS compatibility mode from new machines.
10.
▲
by
wsx
11y ago
tl;dr: This can permanently brick some/many/all? UEFI devices. Three cases confirmed so far on Lenovo/MSI/unknown hardware. Linux distribution other than Arch are likely to be affected as well because systemd is hardcode
11.
▲
No POST after rm -rf /
(bbs.archlinux.org)
422 points
by
wsx
11y ago
|
169 comments