Might be bad or just incompatible RAM. I swapped sticks around and the system stopped booting entirely. BIOS and memtest still detected all four sticks though.
@BlinkRape Tested two random sticks in a first slot, the system didn't boot with either of them. I've ran memtest on remaining 12 gigs before and it passed, so it probably isn't an issue with the sticks themselves.
@BlinkRape Got the system running again by plugging back all sticks and reset the CMOS a thousandth time. Now it's booting but sees only 8 gigs. :heyface:
@Pawlicker Maybe a clocking issue? That's the same RAM which was running flawlessly in my desktop before upgrade; It's running at 1866 MHz now with no way to change it in BIOS, but I'm pretty sure it was at 1600 MHz before.
@mint remove one stick at a time and see if you find the problem socket. then swap other RAM into that socket and see if the problem persists. If not you've found your faulty module.
You could also run an overnight memtest86 scan on all of them while its on I guess.
Looks like one stick is bad, after all. Tried all four sticks in a single slot, with one of them system started beeping (three short, one long) the same way as if there's no RAM installed at all.
@mint I got a stick of Kingston RAM for my Chinese mini PC and had a similar problem with it. Sometimes it’s POST and load the OS, sometimes it’s POST then crash, and sometimes would error beep. I never got around to running memtest but it was so weirdly inconsistent with the faults it showed.
@gray Memtest on 1600 MHz passed. I've put back the other 1866 stick, and it's back at only detecting 4 gigs. At this point I might as well roll with 14 total gigs until I get a matching 1600 MHz 4 gig stick.
@mint I’d have to look at the specs of that Kingston RAM but I think it’s DDR4 1866 and the system can only do 1600. I thought it’d just run at the lower speed and not just shit the bed.
@gray But the stick might be bad, after all. All three other sticks have no problem running at 1866 (or underclocking them to 1600, idk). All sticks came from the same bundle but the problematic one has the earliest year and week of production, so maybe it's running with older and buggier microcode.
@gray Just took a look at RAM prices, and damn it's getting pretty cheap. 8GB DDR3 DIMM is less than a thousand rubles. I'll try getting two of them and seeing if I can get it running at the whole 24 gigs.
@gray Sticks obtained, the system detected 24 total gigs just fine, taking memtests now. Took a detoure to get some import sodas and was immensely disappointed as there were no vanilla Dr Pepper or lime Schweppes.
When setting up the server, noticed it gets a proper IPv6 with a delay. Started debugging this issue with other device I have on hand and noticed Android doesn't get it at all. Apparently, when you're using radvd, putting a subnet larget than /64 makes the clients spaz out.
Alright, basic system is set up the way I wanted, and there's plenty of room for activities. In following days I'll probably set up Wireguard, LXC and try moving Agency there. Screenshot_20230801_232437.png
@gray Haven't bothered checking it out, and since the amount of container would be in single digits, it's probably not worth the effort when I can just ssh into the machine and manually set everything up as needed.
Ok, maybe not pure Wireguard. Seeing reports of it getting blocked, and another service I host (with Wireguard tunnel to OVH VPS) also stopped working a few hours ago. https://ntc.party/t/wireguard/4968
>blocking VPNs How does this work for business in Russia that use VPNs as part of their operation? Is the двач /s/ thread a good place to be informed about developments on centralized blocking in Russia? Speed considerations aside, can't people use an ssh tunnel? Surely they can't start blocking those without their own infrastructure falling apart.
@laurel SSH is as easy to block as Wireguard, and you generally don't transfer huge amount of data at random intervals through it. Right now it all seems selective, but your best bet would be looking what tunnels Chinese use. I have two Shadowsocks servers running, both wrapped in v2ray, and a backup dnstt node, but haven't used any of them for a while since my current VPN provider isn't blocked yet. As for Wireguard on OVH, wrapping it in udp2raw in faketcp mode helped.
I can understand blocking popular VPN providers. But blocking VPN software, either openvpn or wireguard, will cause problems with firms using this kind of software for legitimate uses. Even more so if someone tries to block ssh.
I've looked a bit into shadowsocks and dnstt before and I'm sure they work much better than ssh tunnels. But it's really about obfuscating them, like the http obfuscation of v2ray, or GoQuiet shadowsocks addon, or routing everything through obfsproxy.
>but your best bet would be looking what tunnels Chinese use. I looked a bit into this and found something that you may find interesting. It's a pretty good write up on how the Chinese firewall works, pretty recent too (April 2023). I found it very interesting that they ignore UDP traffic completely. https://gfw.report/publications/usenixsecurity23/en/