this post was submitted on 29 Feb 2024
682 points (94.3% liked)

linuxmemes

21272 readers
422 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 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 sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] ashaman2007@lemm.ee 36 points 8 months ago (2 children)

    My current tower started out on Windows, and for some reason after a year or so it started crashing out randomly. Load didn’t matter, it would pass benchmark tests and then crash randomly 5mins after boot. However there was not a single useful error I could find. Installed Fedora, and looked at journalctl after a crash. Immediately I see “GPU has fallen on the bus”. Apparently it is relatively common, but I also found a thread that said it actually can be caused by loose connection. Did a complete reinstall on my GPU, haven’t had the problem again (~6mo now, had both 535 and 545 drivers). Sometimes it really might be a descriptive error message 😆

    [–] MystikIncarnate@lemmy.ca 13 points 8 months ago

    I had a problem like this with a CPU.

    Fresh from the box OEM hardware, either Dell or HP... I forget. A laptop system.

    We couldn't get the damn thing to do windows updates, which was part of our initial prep for the system. It kept crashing, no useful info from logs.

    I booted off of an Ubuntu live image I had on a USB. Turns out, one of the CPU cores on die was faulty. If I reduced the CPU cores visible to the system to one, it worked fine. All enabled? Crash.

    A call to support and a quick service visit sorted out the system, but Microsoft's error reporting was useless at diagnosing the issue.

    [–] TimeSquirrel@kbin.social 8 points 8 months ago (2 children)
    [–] SatansMaggotyCumFart@lemmy.world 5 points 8 months ago (2 children)

    Whoever wrote that error message doesn't know how to spell separate.

    [–] TimeSquirrel@kbin.social 3 points 8 months ago

    😳 your username...

    [–] AnUnusualRelic@lemmy.world 2 points 8 months ago

    More people ought to enable a spell checker in their code editor...

    [–] AVincentInSpace@pawb.social 4 points 8 months ago* (last edited 8 months ago) (1 children)

    I'm just trying to figure out why, if you'd programmed it to detect /boot wasn't mounted properly, instead of having it error out, you'd have it do the install anyway and then snarkily print "hey, jsyk, that thing I just did probably led to system corruption. Hope you're reading this log and/or feel like spending five hours debugging a nonbootable system! Have fuuuun!"

    Like why would you do that

    [–] TimeSquirrel@kbin.social 2 points 8 months ago* (last edited 8 months ago)

    The dev spent 1,000,000 hours making the entire codebase their second language and knows it like the back of their hand, why can't you?