The Old Myron Siren

I might be better off just building a cluster of raspberry pi 4s and using something like ZMQ to have them all communicate together. I'd have to add a third layer of management to distribute the commands but I think I could get away with having 6-8 worker bots per Pi.

General question: Would I be better off just building a new system using the actual socketable CPUs rather than a co processor? I'm fine with having to SSH into them and treating them like their own computers. I have a rack that I could build a system into and just let it sit. I figured they would be different since its not like I'm adding an extra socket to a board. My main goal here is to get as many cores as I can while spending the least amount of money possible (aren't we all?) As far as heat goes, I have plenty of fans I don't mind cramming into a chassis or even mounting them to the card to keep em cool. I'm sure its not the best solution for sure, however I'd wanna be running the machine myself and go along for the ride with it for the sake of it. I might end up having to do something cloud based if that's what it comes to though. But if possible, I'd like to build the rig myself and kinda let it rip. The specially crafted program is the bit that I'm worried about. If the Phi Co Processor is treated like a secondary system then could I install python packages to it and almost treat it like a VM? Or do I need to rerwrite my current Python files to be able to access/utilize the Phi?

Hopefully this is in the right category, if not my apologies! I've been toying around with multiprocessing in Python the last few days and want to see just how far I can push some it. Currently I have a VM running Ubuntu Server that is for a Discord bot I use for testing purposes. I've broken the bot up into multiple processes so that I can process more commands at the same time (although it's unnecessary and not needed at all for its use, I just wanna have fun). In my pursuit of trying to run as many bots as I can, I remembered vaguely about the old Xeon Phi co processors for days past. I have zero understanding of how to work with something like that though. I know I need to make sure my motherboard supports co processers to begin with but beyond that I'm not sure. Would I have to modify my current Python files and implement other libraries to be able to utilize the Phi?

I ended up going with the Cherry POS keyboard and I could not be happier with it. The switches are rubber domes which I actually find to be quite satisfying to press for this kind of use case. It feels super solid and the feet on it practically glue it down to whatever surface its on. The Cherry Tools software for it is pretty fantastic (although it does look fairly dated) and you can assign up to 10 key presses to each key that is stored in on board memory and as far as I can tell you assign "unlimited" if you store the assignment software side. There's also three layers of key assignments (haven't began to tackle that yet) so I'm assuming you could get 420 macros assigned if you left two of the keys to assign to CTRL and SHIFT to access the layers. If anyone else is looking to make their own macro keyboard, this thing is absolutely killer for the price of ~$113 USD.

The first one is more like what I'm looking for, but a larger scale. Also being able to assign multi key combinations to the keys being a native feature would be stellar as well. I plan on using it for soundboards as well as keyboard shortcuts for Resolve. I took a look at the genovation pads and they looked great! Their price wasn't outrageous but again, I'm looking to spend as little as possible. I ended up pulling the trigger on the Cherry G86-6340 POS keyboard, so hopefully I don't end up regretting it too much. 142 keys for $115 US is tough to beat. From what I've read (which is not much seeing as I can't find anything on this keyboard, unsurprisingly) the Cherry Tools software can let you assign macros to all 142 keys, which if that proves to be true, is an absolute God send.

I've been doing a lot more editing on my computer recently and find my self constantly navigating through menus to add various effects and such. I also have been getting into making Soundboards to use in Discord calls to spice things up a bit when needed. I currently use a G910 as my keyboard which has 3 pages of 9 macro keys. These work fine and well, but I would like to avoid cycling through pages and profiles to get access all of my keybinds. I figured I would look into getting something large with enough buttons that I wouldn't know what to do with them all, while also spending as little money as possible A.K.A the impossible dream. I found this keyboard on Amazon that seems to be a pretty good deal, however I can't seem to find much information about or reviews seeing as it's intended to be a POS keybaord. Does anyone have any experience with this keyboard or know if I would be able to assign macros to each key? It's advertised as being fully programmable, but what exactly would that entail. This biggest thing for me would be being able to use something like "CTRL + ALT + 1" as an assignment, seeing as I would never hit those combination of keys regularly. Thanks for the read and any responses are always appreciated! EDIT: I ended up going with the Cherry POS keyboard and I could not be happier with it. The switches are rubber domes which I actually find to be quite satisfying to press for this kind of use case. It feels super solid and the feet on it practically glue it down to whatever surface its on. The Cherry Tools software for it is pretty fantastic (although it does look fairly dated) and you can assign up to 10 key presses to each key that is stored in on board memory and as far as I can tell you assign "unlimited" if you store the assignment software side. There's also three layers of key assignments (haven't began to tackle that yet) so I'm assuming you could get 420 macros assigned if you left two of the keys to assign to CTRL and SHIFT to access the layers. If anyone else is looking to make their own macro keyboard, this thing is absolutely killer for the price of ~$113 USD.

I believe mine go directly downstairs. I'm on the second floor as is the room that the router and modem are in. I believe there is a panel in the garage however which is where our cable line actually comes into the house.

I believe our house was build around 2008/2010 so its somewhat recent, but, I agree that its more than likely something to do with the wiring.

For a while now I've had my server rack in my actual bedroom seeing as that is where my main computer is setup and I want to be hardwired on both my servers and my daily driver. However, the noise has been far too much to bear and I finally cracked and moved it into an empty bedroom across the house. This of course meant I had to move my modem and router there as well to maintain a wired connection for the server, leaving my daily driver at the mercy of WiFi. I thought about running cables through my walls and ceiling for the connection, but I also know that there are coaxial adapters exactly for this. I'm fine dropping about 100-150 bucks on adapters if it saves me the day or so of running cables through the walls. I've tried a set of power line adapters previously but I believe the way my houses power is wired, it causes issues. Even when the plugs are in the same room (and same breaker) I can't seem to get above 10-15Mbs even though they are advertised for a full gigabit. What are my options here? I found this pair of coaxial adapters and figured it should do the trick? Thank in advance guys!

Not yet. The weird thing is since I posted this, I plugged in the cable again and now its only been doing it occasionally (only about twice so far). The headset is setting on the desk not moving so it's not like the cables being moved around a whole lot.

Thats what I'm thinking. Like it can't be that there's too many ports, why else would they all be here? I wanna avoid dropping 27 bucks or so on a PCIE card for it, but if it comes to that it's not the end of the world.

I've been experiencing an issue with the USB port on my motherboard for a few months now, but I just assumed it was the cable that I was using. I recently picked up an Oculus Link compatible USB C cable and it worked perfectly for the first day, but I am back to having the issue of the headset connecting and disconnecting in a loop for about 30 seconds or so before stopping. I originally had this issue whenever I connected my phone. I've install the drivers for the motherboard from Asus' website but the issue still remains. Could it possibly be that I have two many devices using USB ports? I have 8 in total plugged in. I wouldn't imagine that it would be an issue but what else could it be? Could I just have gotten two cheap cables that are shoddy out of the box?

I just install an LSI 9260-8i into my home server to free up some SATA ports and clean up the wiring a bit. However, none of the drives that are connected through the SAS Controller are showing. I am using SAS to 4-SATA cables and all of the drives that are being connected are 4TB HP Midline drives. The drives show up in the controller's BIOS all with their proper capacities, but once in Windows they're nowhere to be found. I've checked device manager and the controller is listed there with the most recent drivers. What is it that I'm missing here? As always, thanks in advance guys!

I pulled the trigger on the Quest last night after doing some more research. Apparently, theres a workaround way to even use the Quest over wifi so you end up with completely wireless VR, which I dont exactly expect to be perfect but it's worth at least a try. I have an extra, dual band wifi card that I could chuck into my machine and use a hotspot to handle the connection, so hopefully that serves me better than hooking up a router. I was also looking at something like this to replace the rather lackluster head strap on the Quest, although I'll have to see for myself how I like the original strap. Excited to finally get my feet wet with VR!

Thank you so much for that break down! Lots of information, I love it It sounds like the Quest is actually the better system compared to the Rift S if you end up getting the Quest Link cable, which I wouldn't mind investing in. I wasn't aware that the resolution of the Quest was actually higher compared to the Rift S. I know its not exactly much compared to the Rift S, but if they have the same panel the higher resolution would help with SDE, correct? I wouldn't exactly be particularly interested in the mobile aspect of the Quest, but having it as a potential alternative/option just in case is quite appealing. From the looks of it, the Quest is a no brainer if I don't mind buying that adapter cable?

How come the Quest over the Rift S? They seem to be the same price and the Rift S appears to have better specs across the board.

I've been reading a lot more and it seems the Cosmos is just not worth the 700 bucks for it. As much as I would love the Index, I just can't justify spending 1000 bucks before any games for it. At the same time though, I'd rather wait and spend 1000 for the Index than pay 400 for the Rift S and then eventually another 1000 for the Index later on. I'm not even sure my 1080 would be enough for the Index though. Whats the big difference between the Quest and the Rift S? It seems they're the same price so I'd rather just go with the Rift S at first glance, unless there's differences that make the Quest better in terms of usage. I'd rather move my rig and my headset if the visuals are better.

I recently tried out a friends Rift S over the weekend and I'm quickly learning that that was a mistake on my part seeing as I know am selling off my stockpiled hardware to get the funds for a VR setup. I didn't have any complaints with the Rift S while I played (roughly 2 hours or so in one go). No motion sickness, eye strain, or tracking issues. I was pleasantly surprised considering a lot of what I've read about the potential horrors that VR can be sometimes. I at first wanted to get the Rift S until I remembered that there was a headset that peaked my interest a while back that was still unreleased: the Cosmos. As far as I know it has a higher resolution and refresh rate (90Hz I think?). I have read that the Cosmos is a bit of a sh*tshow in terms of its software and I've seen some people say that the tracking is awful and their headset frequently complains about the room being too dark. These issues coupled with the 699 price tag makes me hesitant to pull the trigger. Additionally, I'm not sure if either of these two are really the best options. The inside out tracking sounds fantastic for me since I'm not exactly keen on mounting sensors around my room, although I do know that it would offer better tracking. All in all, I dont mind spending ~700 bucks on the Cosmos, so long as its the best option for that price. I've heard the Index is far and away the kind at the moment, but they're not exactly easy to find as well as the additional 300 dollars. On the other hand, I could get the Rift S for 399 and use that extra 300 dollars for games and other upgrades. I am a confused man in need of some serious help! As always, thanks in advance guys

So it seems that I was misunderstanding the guide. The premade config file it was offering me were meant for laptop users, which clearly I am not! Down side is I cannot find any clover config files for my board/chipset.

Oof alrighty. Whould that just be a KVM virtual machine inside of something like Ubuntu Server?

I don't believe so? Every optional config is listed by Intel Graphics name. So they're all like "HD3000", ""HD5600" and the like.

Not sure if you're able to help, but I figured I'd ping you just in case. I have to select a config file based on what Intel GPU I have (per the guide), but the cpus I'm using are Xeon x5690s, which don't have integrated graphics. Do you have any idea what I'm supposed to do? Thanks for the help so far!

Oh man, perfect! Thanks so much

I haven't really done much at all with Mac OS so I'm totally lost in the sauce with it. Would I have to run it within a VM or could I install it directly to an SSD with a boot USB drive? Thank you! I'll take a look at those and read through it all. Any tips or should the articles be more or less enough?

The overall goal of this thread is to figure out just how much of a deep hole am I going into with a potential Hackintosh build. I've been working on a multi user "LAN Party" machine for a while now that I had running before with different hardware. I recently upgraded another rig and was planning on using those old parts in the multi user machine, but I feel like it would go under utilized. I have friends over less and less for gaming in general now so I feel like its usage is getting thin. I have always liked the look and feel of Mac OS and went ahead and put Elementary OS on an old laptop just for giggles. I've been gushing over the never ending store of Linus' hackintosh and I've been reading a lot of forum posts from years back of people using dual x5690 xeons for nice little hackintoshes. Since the build was originally meant for multiple VMs, I have a ton of RAM and GPUs to cram in it. I also believe that only AMD cards are compatible for Mac OS? So the 970s will just become two RX 480s and one RX 580. Working in Linux to create a multiple Windows VMs was a bit of a whirlwind for me and I imagine a hacktintosh is definitely much harder than that. But, a challenge is a challenge! What are some things I should know, look out for, avoid; anything that will help out with the process! I might just continue on with the multi user build if this all becomes too much, but I think it would be pretty nice to have a Mac in the house.