Jump to content

rsethc

Member
  • Posts

    37
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

rsethc's Achievements

  1. Thanks. Haven't tested for very long but it seems to be stable at 3133 MHz so far. If it turns out to be that small of a decrease for stability I can live with that (I got this memory at a significantly reduced price for being open box - so maybe this is the exact reason someone returned it before). Still would like PSU suggestions if you have any, as I do plan to replace that fairly soon regardless of the memory situation.
  2. Looking for some suggestions on a good PSU to upgrade to, & also a bit of diagnosis help with stability problems. Yesterday I finally built an upgraded system for gaming & code compilation usage, with some old and some new parts: - AMD Ryzen 3900X - ASRock X570 Taichi - G.Skill Trident Z RGB 2X32GB 3200Mhz - (old) Nvidia 750 Ti - (old) 2X 7200rpm 3.5" spinning rust - (old) 1X 5400rpm 2.5" laptop spinning rust - (old) 1X SATA SSD - 2X Samsung 980 M.2 SSDs - (old) Corsair CX600M After I finished building it, I did get the system to run, but had some trouble getting the memory to work at 3200 MHz as it's rated for. The XMP profile didn't work, and I thought I solved it by increasing the memory voltage from 1.35V to 1.38V since it then booted just fine, but playing some BeamNG.drive with a bunch of AI cars (yeah not the most scientific test but it was pretty consistent) the game would crash after a few minutes, and after a few game crashes it would be a BSOD with some memory related error. Under the assumption that memory errors meant not enough memory overclock stability, I increased DRAM voltage, increased SOC voltage a lot too, and still got the same exact behavior. I did run across this article: https://www.ifixit.com/Wiki/Troubleshooting_Computer_Memory So before recommendations for new PSU (I do plan to get one anyway to be able to upgrade my GPU when the market is no longer experiencing a resonance cascade), if anyone could speak to whether they have personally had or seen a build where memory issues were happening but then swapping PSUs solved it? The PSU is old, from day one that I bought the Bulldozer board and CPU something like 7 years ago, but it never seemed to cause similar problems in that system. Could it just be because the new stuff is drawing quite a lot more power that I am seeing this happening now? Second question: What PSU should I go get in order to comfortably support up to the following items as I continue to improve the system? These aren't all items I plan to get but do want to at least know I can upgrade to without worrying about stability. I did go X570 for a similar reason as I don't want to compromise on PCIe 4 capabilities. - AMD Ryzen 5950X - ASRock X570 Taichi - 4X32GB DDR4-3200 - RTX 3080 or the top AMD offering - 3X 7200RPM spinning rust - 3X M.2 SSDs - 2X SATA SSDs I don't know how important listing SSDs of either kind is in terms of power draw, but I thought I might as well list them too since I'm specifying mechanical hard disks (I do think the moving parts in those are demanding enough to potentially matter to the PSU choice). Also any suggestions for retailers are welcome, I like Microcenter but they don't appear to have a great PSU selection, with anything over 1000W being their house brand PowerSpec which has not so good reviews on their own site. Thanks for suggestions on any aspect of the above.
  3. What I'm wondering about in terms of the "how do they work" part is more like: how do they access memory (do they have onboard memory too?), and how does the OS become aware of those cores? If everything has to go over PCIe routing, is it only certain motherboards that support them (like you'd have to have a certain chipset, such that those mining boards won't work)? Or is it something the OS has to have had support implemented for, or is it a driver...?
  4. I don't know any in-depth details about how Xeon Phi's work but my basic understanding is that they behave like normal CPUs that you can add via PCIe add-in cards. Today I wondered about two things: If you bought a mining motherboard (you know, one of those that has like 20 PCIe slots), and enough Xeon Phi cards to completely populate it, would it work at all? And if it did work, and you ran some synthetic CPU benchmarks and productivity workloads on it (I would expect gaming to completely suck), how would it compare to just a single 64-core Threadripper? Or if anyone wants to chip in w/ an explanation of just how those cards worked in general, that would be pretty cool to know as well.
  5. What about just caching the files on the editors' machines? Instead of having the cache be in a centralized location, each workstation would have its own cache and you would also have less network traffic. I am not sure if Windows supports this but there may be some third party software to do it. The idea would be that when you attempt to open a file in the cache directory, if it does not exist (or there is a mismatch of last-modified time stamp) then Windows (or whatever third party software) would stream in the file, in its entirety or maybe in certain sized chunks, to the cache, and meanwhile also serve it to the file handle that is trying to read. As for the "in its entirety" / "chunks" this would mean that there would not have to be an explicit request by the application to read a small region, in order to go ahead and also load what is likely to be read next anyway since it's nearby the requested region. Although I'm not sure if Windows / certain file APIs used by the application already try to pre-load more data themselves and buffer it in memory.
  6. By the way here are the mounting options (they used to work fine before this, but I thought I might as well post them).
  7. Now I have a much larger concern. After reinstalling Samba from the repositories like a normal person, I am unable to mount one of my disks... what the heck could this mean?
  8. I'll leave the compiled-from-source stuff alone for now. I tried that command (sudo update-rc.d samba defaults) and did not see any output (not sure what it does anyway), opened up Synaptic and reinstalled the samba packages. The version of all of them appears to be "2:4.3.11+dfsg+0ubuntu0.16.04.12".
  9. I have an ancient machine I use as a NAS, with some various old hard drives in it and a Pentium 4 CPU. It's got a 100-mbit NIC onboard, so network file transfers are of course significantly slower than file transfers to the rest of my old network (I have three other machines I use as NAS, each of which has a Gigabit NIC.). I also had a bunch of old ethernet NICs sitting around, salvaged from other old computers. So, very recently it occurred to me that maybe I could speed up file transfers in some situations by adding some of those NICs to the ancient server. Currently, the server has two 100-Mbit NICs in it: one is integrated into the motherboard, and the other is in a PCI slot. The server runs Ubuntu 16.04.3, and I've been using the Samba version from the Ubuntu repositories. At first, I tried to set up NIC teaming but that didn't go so well (and, since I manage the server remotely, screwing up the network configuration means having to go attach a keyboard, mouse, and monitor) but I found out that Windows 10 (and Server 2012) are capable of a technology called SMB Multichannel which will make use of multiple NICs by splitting communications across multiple connections. Samba supports this feature now, but the version in Ubuntu repositories is older than the first versions where this feature was implemented. By the way, I took a look at FreeNAS but it is nowadays only for 64-bit processor systems and requires much more performance and memory than this machine has. No dice. So, I went and grabbed the latest stable Samba source, compiled it, cd'ed to the extracted location, and ran: sudo ./configure over and over and over again until I resolved every obstacle I ran into by installing whatever package it complained about, sudo make and then finally sudo make install But I have no idea how to do the final thing: installing the freshly compiled Samba as a (systemd?) service so that it will run at all times, and I can use it normally. Basically, I need help figuring out how to do the same thing the package manager would do automatically.
  10. cfosSpeed works fine for me in Windows 10 as it had in Windows 7, but I had to uninstall and reinstall the program at several times: when upgrading from Windows 7 to Windows 10 it got broken and I had to reinstall, and then this also happened with major Windows updates too. I suspect it has something to do with the updates breaking drivers the program installs to intercept network traffic.
  11. The results are consistent between both so I don't think it's an issue much farther out than my local dealings with the ISP.
  12. Alright, I power-cycled my modem by unplugging not only its power cable but also the coax cable, and made sure to leave it off for a generous 20 seconds. No dice, I did another speed test and everything is the same as before I did that.
  13. Actually I unplugged the modem accidentally while I was setting the new router up, but the coax cable was plugged in the whole time. I might as well try disconnecting everything from it if the cable itself can provide power. 10 seconds fully disconnected from power & coax should be good, I assume.
  14. The QoS features were already disabled, though.
  15. Did a speed test with the program uninstalled and as I had expected there was no difference. It wouldn't have made sense for the program to have been the cause of the issue anyway though, since my upload speed had *dropped* between routers at first, from 6 Mb/s to 1.5-2 Mb/s, without any change to the program (though, for the sake of not ruling anything out I have to admit that perhaps it would be possible for the program to detect a hardware change and change its behavior as a result, but I highly doubt that was what happened).
×