• 2 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: March 4th, 2024

help-circle




  • He’s an Edison, he’s a Carnegie, he’s a Rockefeller. He’s a robber baron like countless before and that on its own is enough of a condemnation.

    Dude single-handedly ruined many, many foss and other software projects because he couldn’t buy, bully, or otherwise get obscenely rich from. He would use windows’ reach to kill projects. “Windows ain’t done until wordperfect won’t run”

    He played dirty to get his money and now that he’s “won” and has enough money for his family to be generationally wealthy for ever he’s donating amounts that don’t cut into his oligarch lifestyle. Guess he hired a good PR team though, cuz everyone seems to forget what he did to get so filthy rich.

    Not to jump down your throat over it - I just hate that he’s managed to erase the shitty things he’s done by donating the money he got by doing shitty things.









  • Search “switch hacking is easy” - there’s an ancient site that got dcma’d (or something) that is defunct but someone rehosted it under “switch hacking is still easy” on github.

    That’ll help you tell whether you’re able to use the joycon jumper method or not. If not, it’s a very fiddly modchip install that I wouldn’t recommend unless you’re experienced in soldering.

    Be sure you understand the difference between launching directly and installing a parallel OS (sysmmc vs emummc, I think?)

    Someone might need to check me but if you do sysmmc then boot into it without the hacks and Nintendo domain blocking, it’ll connect up to Nintendos servers and report the hack and ban your console







  • Honestly it might still just be the SOC failing - when I worked in hardware repair most laptops had separate chips for each but now tech has progressed to have them both on one “system on a chip”. So back in my day if it was gpu the cpu might keep humming along while the gpu was fried, but that’s less relevant now-a-days.

    Sorry bro, I’d say back anything you give a shit about up because she’s probably on the way out. If my experience holds, even with the single chip boards - eventually it’ll artifact like this every boot and you’ll be digging out the hard drives to get at your files.

    In your shoes I’d recommend fucking with the drivers and your OS, it’s still possible that it’s the drivers are interacting with the hw wrong and causing the issues, but in reality that’s a long shot. Also run memtest86 overnight one night and see if maybe its the ram?

    If it does die and you’re feeling hack-y, the dude who suggested an oven reflow is not wrong. If you manage to figure out getting the motherboard out (make sure no plastic that could melt!!) and put it in the oven at reflow temp, you might revive it. If picking the laptop up and twisting the body slightly can cause the crash, it’s almost definitely soldier joint issues.

    Are the fans doing anything under normal load? If it’s not moving air at all that’s cause for concern too. Dead fans mean thermal issues, which can cook chips.

    Oh one last edit, check how long the warranty is - fucky soldier is a manufacturing defect.

    Best of luck brother, sorry for the shitty news.