• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • I must have missed that negative sentiment entirely. I played all three and had no complaints. Did some searching, and apparently a lot of the gripes were related to levels being cut down in size / broken down into pieces to allow for a console release (strict memory requirements). Also I think they changed engines for the 3rd game, or at least a lot of people complain that movement and controls were worse in DS. I guess ignorance is bliss, cause I enjoyed them all.



  • Not the person you replied to, but I’m in agreement with them. I did tech hiring for some years for junior roles, and it was quite common to see applicants with a complete alphabet soup of certifications. More often than not, these cert-heavy applicants would show a complete lack of ability to apply that knowledge. For example they might have a network cert of some kind, yet were unable to competently answer a basic hypothetical like “what steps would you take to diagnose a network connection issue?” I suspect a lot of these applicants crammed for their many certifications, memorized known answers to typical questions, but never actually made any effort to put the knowledge to work. There’s nothing inherently wrong with certifications, but from past experience I’m always wary when I see a CV that’s heavy on certs but light on experience (which could be work experience or school or personal projects).


  • I also unplugged the psu for a while. It makes a slight buzzy noise after powering the computer, but I do not know if this is normal.

    I’d recommend starting with the PSU. A buzzing noise is not a good sign. This article has details on how you can test your PSU: https://www.howtogeek.com/172933/how-can-i-test-my-computers-power-supply/

    You can perform a basic test with just a paper clip or a bit of 16 or 18 gauge wire.

    It sounds like the PSU is giving some power, given that the keyboard lights up. The issue could be isolated to one or more rails, e.g. it’s not delivering anything / enough on the 12V or 3.3V rail. I’m guessing 5V is OK since that’s USB voltage and your USB keyboard gets power. You’d need a multimeter to check individual power pins on the PSU connector.

    Edit: if you have access to a second PC, you can swap PSUs between them. If the problem follows the PSU then that’s the faulty component. If the problem stays with the original PC then it’s likely motherboard, CPU or RAM.

    If you can determine that the PSU is OK then the next step is to try booting with the bare minimum amount of hardware. That’s motherboard, CPU and one stick of RAM. If that won’t boot then you try with a different RAM. If it still won’t boot then the issue is motherboard or CPU. Before you replace either of those expensive components, try replacing the cheap CMOS battery as another poster recommended.







  • OpenAI on that enshittification speedrun any% no-glitch!

    Honestly though, they’re skipping right past the “be good to users to get them to lock in” step. They can’t even use the platform capitalism playbook because it costs too much to run AI platforms. Shit is egregiously expensive and doesn’t deliver sufficient return to justify the cost. At this point I’m ~80% certain that AI is going to be a dead tech fad by the end of this decade because the economics just don’t work now that the free money era has ended.


  • It’s likely CentOS 7.9, which was released in Nov. 2020 and shipped with kernel version 3.10.0-1160. It’s not completely ridiculous for a one year old POS systems to have a four year old OS. Design for those systems probably started a few years ago, when CentOS 7.9 was relatively recent. For an embedded system the bias would have been toward an established and mature OS, and CentOS 8.x was likely considered “too new” at the time they were speccing these systems. Remotely upgrading between major releases would not be advisable in an embedded system. The RHEL/CentOS in-place upgrade story is… not great. There was zero support for in-place upgrade until RHEL/CentOS 7, and it’s still considered “at your own risk” (source).


  • Anything that pushes the CPUs significantly can cause instability in affected parts. I think there are at least two separate issues Intel is facing:

    • Voltage irregularities causing instability. These could potentially be fixed by the microcode update Intel will be shipping in mid-August.
    • Oxidation of CPU vias. This issue cannot be fixed by any update, any affected part has corrosion inside the CPU die and only replacement would resolve the issue.

    Intel’s messaging around this problem has been very slanted towards talking as little as possible about the oxidation issue. Their initial Intel community post was very carefully worded to make it sound like voltage irregularity was the root cause, but careful reading of their statement reveals that it could be interpreted as only saying that instability is a root cause. They buried the admission that there is an oxidation issue in a Reddit comment, of all things. All they’ve said about oxidation is that the issue was resolved at the chip fab some time in 2023, and they’ve claimed it only affected 13th gen parts. There’s no word on which parts number, date ranges, processor code ranges etc. are affected. It seems pretty clear that they wanted the press talking about the microcode update and not the chips that will have the be RMA’d.


  • I’m sure there would be a way to do this with Debian, but I have to confess I don’t know it. I have successfully done this in the past with Clover Bootloader. You have to enable an NVMe driver, but once that’s done you should see an option to boot from your NVMe device. After you’ve booted from it once, Clover should remember and boot from that device automatically going forward. I used this method for years in a home theatre PC with an old motherboard and an NVMe drive on a PCIe adapter.