Oooh ok, I’ll try putting it in the microwave for a bit, thanks!
Oooh ok, I’ll try putting it in the microwave for a bit, thanks!
Impressive engineering, but it comes with a curse.
Where it gets messy is you’d need to supply power on the PCIe rail as well as any extra plugs the GPU needs without powering on the system itself. And then even messier if someone powers on that system. Mad scientist shit.
I made an energy efficient one by replacing the light bulb with an LED bulb and some cooling fins since the design looked like it would trap heat from escaping, but that guide is garbage because it doesn’t work like it’s supposed to!
Just made that one up but it was based on another Frankenstein-like setup another user in a beta testing group was using that I don’t remember the specifics of. His issues started getting mostly ignored until he upgraded his system to something more normal lol.
Ah that’s interesting. If you can swap the devices from one pi to another, try powering it all up on machine A, then swap the devices to machine B and power that on. Might tell you if the issue is with on the pi side or with the devices.
Is latency higher on the first boot than on subsequent ones? I’d be looking into race conditions if you’re seeing a bit of lag cascade out into bigger problems. Race conditions are the worst, especially when the race most often goes the right way and just occasionally goes the wrong way. Though you can force the wrong way by adding delays in your code, if you have an idea of where the race is happening.
Or, after weeks of debugging an issue the user has logs proving they are having weird performance issues despite having a strong GPU, it turns out their parents wouldn’t let them take that GPU out of the family PC so they rigged up a PCIe to USB to wireless transmitter that hooks up to a wireless to USB to serial port that exploits a signal leaking from serial port to PCIe bus bug on the family PC motherboard to act as if the GPU is on their own machine, which both impresses and horrifies you.
And when you try to get approval to drop the issue as unsupported, your manager gives you shit and it takes another week to convince him that it isn’t a use case that you should support. And they only agreed in the end because a more senior technical person happened to overhear you pleading with your manager one day and only had to say, “that’s crazy!” for your manager to 180 immediately on the issue. But it’s still cited as a negative on your next performance review (“you spent weeks working on something we don’t even support!”).
Another angle to try is to set the date one day ahead and see if the bug shows up then. Might need to disconnect from network and set it in the BIOS for the test to work properly.
I could be wrong, but I figure after being off for an hour, all capacitors should have discharged by then, so it’s probably not based on how long the hardware has been unpowered.
Though one other angle I just thought of, if you have something that runs periodically, maybe the bug is related to that period being missed once or n times. Or it could be related to something that is meant to wake the computer to run some job and then go back to sleep but instead just sets it in a bad state.
Yeah that’s fair, though it doesn’t help with the frustration. Especially when it’s management getting in the way of things. Like with all the enshitification, my guess is that there’s a dev or team of devs that hate themselves for going along with it.
Yeah, that’s something a shitty developer who is bad at debug would say.
Bugs frustrate me more because I can often guess at why they are happening and how to fix them but can’t just apply the fix myself. Even more frustrating when there’s an update and I’ll think, “oooh maybe they finally fixed that annoying bug!” and then see it again shortly after installing the update.
There have been a few times where I want to get back into a game, load up an old save, flounder around in it because I forgot some essential game mechanics, decide “fuck it, I’ll just start a new save” and then get back to where I was and beyond quicker than I remember getting there in the first place.
Not to mention the selection of games available is pretty paltry.
Was doing some woodworking with the big power tools my dad had set up in the basement. First time using the table saw, I start my cut and realize the blade wasn’t high enough and wasn’t cutting through the whole piece of wood. I knew that I couldn’t let go of the wood while the machine was running, or it would become a projectile.
So I turned it off and immediately let it go, turning it into a projectile because the blade was still spinning. Luckily it only caught the back of my finger, though it left a scar.
Manly men condition their beard so it is softer than the kitten.
Yeah, it’s kinda like asking your mail deliverer when something you pre-ordered will arrive.
Or saying that the only global maps we should accept are ones projected onto spheres. Same thing for partial global maps above a certain size threshold (projected onto partial spheres).
I’m curious what that threshold is. Like how long do North/South roads need to be before there’s a non-trivial divergence towards the equator? How far do parallel East/West roads need to be before one is noticeably longer if measured from the same longitudes?
Maybe the output side is clogged up and the attempt to push more air through than it can handle causes turbulence that results in slower air flow, or affects what air it is sucking up so that it pulls more from the sides rather than below.
I’ve always interpreted the other thing coming as a threat or an unpleasant surprise. Ie, the consequences of thinking the thing they think.
Shouldn’t that be semi-monthly? Rounding months to 4 weeks, of course.
Or maybe that’s just me wanting bi and semi to have consistent meanings. Bi is two, semi is a half.
No, you must go back and tell him that the moon moves at a very predictable rate and once you get close enough it will even pull you in.
Also I’m pretty sure the ISS moves a lot faster than the moon but we still manage to dock spacecraft with it. I’m pretty sure it’s a bit smaller than the moon and docking can require higher precision than landing on a surface. Even Boeing managed to do it.
The important bit is to power one on first before the swap, then you’ll have one setup where the pi was recently powered on and another setup where the connected devices were recently powered on. You might see the issue on only one of the devices, at which point you can say if it’s the pi being off for a while or the devices that triggers the issue.