Coyote's Blog

I jJust wanted to report the success of replacing my Quadro P2200 (5G) with an RTX 4000 (16G) in my T640. The A4000 GPU is a 140W single-slot GPU. It takes power from an X16 PCIe slot (75W) and needs a 6pin PCIe connector for the rest (65W). Since I like my T640 silent, the GPU PDU board was not an option for me. On the T640 platform, adding the GPU PDU board under the mainboard makes the machines require to add the infamous and noisy GPU External fans (pictured below, along with the GPU PDU Board): The lower half of my T640's front is occupied by a 16x2.5 SFF SAS/SATA backplane which luckily has a cable with two SATA connectors on its back: With that in mind, I did the follwing Math: a SATA connector can carry up to 54W, which meant a total of 108W for the two SATA connectors. The 6pin PCIe connector required to power the A4000 will likely not exceed 65W since 75W is coming from the X16 PCIe slot. With that in mind, a very Simple StarTtech dual-SATA to PCIe 6pin adapter was obtain...

 I have a Dell PowerEdge T140 with an 8C Xeon @ 3.4Ghz, 128G of RAM and about 32Tb of 12Gbps SAS Flash. The default cooling configuration works but it tends to become noisy under load. Also, the Xeon CPU tends to reach into the 75C/78C, too close to the 80C limit for my taste. I like my Home Lab silent and powerful but in the summer, my T140 was often louder than the T640. So Here is what I did: - CPU FAN: The Default heatsink has to go, there's nothing to salvage here but keep the fan, we'll need it later. The heatsink itself would probably be better suited for a 35W CPU but it's not good enough for an 8C/16T Xeon SP Gen2 (E-2278G): The FAN has a super proprietary connector that I have not yet identified but we'll keep it for later. The good news is that -any- Dell PowerEdge T340 heatsink will work in the T140. These heatsinks have a lot more fins and don't require you to do tricks to fit the heatsink to the mobo. The T140/T340 mobos are proprietary and it is not e...

 Yesterday - Jan 1st 2024 - I ported OWacomp + XView to RHEL8 and gcc-8.5. Ihad been using OWacomp on RHEL8 but these binaries were being built on RHEL7 and gcc-3.4. In the process, I tested some of the 64bit XView codebases available on Git Hub but rolled back because introducing the boost pre-processor broke some OWacomp apps (most notably the filemgr). In the end, I changed less than 500 lines of C code and I'll be suitable for a few more years. I'm not a C programmer, I work in IT, but I am not a programmer per trade. If I can keep using the Desktop env (olvwm) that I've been using with just a few hours of code each year, I'm willing to see how far the rabbit hole goes. I tried asking ChatGPT for help, but the bot did not even -look- at the GitHub repo I had provided, and its help was more or less paraphrasing the C compiler errors. It felt like working with 'Captain Obvious'. I know it's a lost battle, but I already have a contingency plan in place for ...