this post was submitted on 30 Oct 2024
6 points (100.0% liked)

Linux.zip

387 readers
2 users here now

Linux community for Lemmy.zip. ~~also this needs mods pretty bad~~ apparently not as bad as I thought (either that or this community isnt alive enough for troublemakers yet)


Community Rules:

  1. Do not violate any laws, third-party rights, and/or proprietary rights.
  2. Do not harass others, be abusive, threatening, and/or harmful.
  3. Do not be needlessly defamatory and/or intentionally misleading.
  4. Do not upload without marking obscene and/or sensitive content as such.
  5. Do not promote racism, bigotry, hatred, harm, and violence of any kind.

^i^ ^may^ ^or^ ^may^ ^not^ ^have^ ^stolen^ ^these^ ^rules^ ^from^ ^another^ ^linux^ ^community^ ^on^ ^another^ ^instance^

founded 1 year ago
MODERATORS
 

cross-posted from: https://lemmy.zip/post/25426678

This is not to be confused with systemd_bsod, which has a similar function but fails in scenarios that crash user space, unlike DRM_Panic.

top 2 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 month ago (1 children)

“Supported”? Like it’s a feature or something? Weird wording. “We support full disk encryption via ransomware!”

[–] [email protected] 5 points 1 month ago* (last edited 1 month ago)

It is a feature Linux has been trying to add. They want Windows style BSOD crash reporting but that requires driver support.

Btw, DRM here refers to Direct Rendering Manager