• 0 Posts
  • 122 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle






  • This will be my first Framework, already preordered a few weeks ago.

    They finally offer a 120 Hz display, and while it has slightly rounded corners which isn’t ideal, but I’ll take the 120 Hz with VRR and higher resolution over perfect corners. They explained they had to use a panel that was already on the market because they don’t have enough volume that they can afford to order a custom display and with the Framework 13 using a 3:2 aspect ratio options were apparently very limited.

    They also offer a keyboard with the Super key having a neutral label (not a Windows logo) now.

    The new webcam is apparently quite a lot better, but I don’t care too much about that.

    I went for the i5 125H model, I think the difference of almost 400,-€ to the i7 155H isn’t worth it for most use cases, as you only get 2 more P cores (with all other core clusters being identical, I think 4+8+2 vs. 6+8+2) and 8 instead of 7 GPU CUs. I feel the difference will be negligible for my use case as soon as it hits power/thermal limits anyway. This also seems to be the stop-gap generation of CPUs, with both AMD and Intel appearing to make noticeable steps forward in the generation.

    There’s also the AMD model which is great and got most upgrades the Ultra model did (new display, webcam and keyboard options), only missing out on a slightly improved cooling system. Between the i7 and R7 I probably would’ve gone for the Ryzen 7, but I feel the i5 is the better choice compared to the Ryzen 5, primarily because the iGPU is stripped quite a bit compared to the R7. Intel is also less restrictive on which expansion slot supports what, with every port supporting full USB 4 including DisplayPort. Not a big deal as there are still enough fully-featured slots on the AMD model, but it’s a bit more convenient to just plug in any card anywhere and it works.








  • Today’s CPUs usually expose some USB connections directly. Ryzen 7000 desktop CPUs expose 4 USB 3.2 Gen 2 directly on their on-package I/O die for example. So if you connect your USB drives directly to the ports your mainboard connects directly to the CPU, the chipset (“southbridge”) and any third-party USB controllers are out of the equation.

    This is just information, I’m not advising to use USB for fixed storage.


  • I was in a similar situation at the end of last year losing all WhatsApp chats dating back to ~2016.

    I got a new iPhone 15 Pro (and didn’t keep it, but that’s another story), wanting to upgrade from my 13 Pro.

    Now normally, I just transfer all data from the old phone to the new phone which always worked fine. But WhatsApp has its own backup mechanism, which normally works in addition to the regular iCloud backup. But a year ago or two they introduced end-to-end encrypted backups, which I enabled. Apparently this blacklists WhatsApp chats from being backed up to iCloud as part of the standard iPhone backup (even when WhatsApp is explicitly enabled in the backup settings) and also blacklists them from being transferred via direct phone transfer for some reason only some developer at Meta knows.

    So, that meant the new chats weren’t on the new iPhone 15, but I didn’t know that yet. I then launched WhatsApp on the iPhone 15, going through verifying my phone number again, which is the normal procedure. It then asked me to generate a new encryption phrase, and this should have been the first sign something went wrong. Basic WhatsApp configuration apparently transferred just fine, which is why WhatsApp never asked to restore the backup it made. This was my first failure, as I didn’t suspect anything and simply set a new encryption phrase. Sure enough, WhatsApp wiped the existing (WhatsApp specific) backup off of iCloud and started a new (empty) backup. Apparently WhatsApp is designed to only support one backup per iCloud account/phone number.

    The “old” iPhone conveniently asked if I wanted to factory reset/wipe it after the transfer was successful. This was my second failure, as I simply confirmed the prompt, thinking the transfer was completed (which it was, except for the WhatsApp chats) and also thinking I had the iCloud backup of the phone (which I had, but that excluded the chats as well).

    My third failure then was not having any local backup of the phone. I thought I had a backup that was at most a few weeks old on my Mac, but apparently I deleted it and I also moved to a new NAS recently and didn’t transfer the Time Machine backup of the Mac, so it wasn’t in that backup either (I wiped the old NAS).

    So it was a chain of UX nightmares/stupid design on Meta’s part and my own stupidity on multiple occasions.

    I somewhat cared that my chats were gone as they were a decent database for actually useful stuff and WhatsApp is searchable quite fast, so I frequently used it to find older stuff like links, photos or documents. There were some more personal chats that I’d have like to keep as well. I actually got some chat history back by asking one guy I share a lot of groups with to export their shared group chats and send them to me. I also got a more personal chat back from a person I’m close with.

    Most chats are still missing and gone for good, but I’m mostly over that as I shouldn’t live in the past anyway. I also tried contacting Apple to restore iCloud to an older state, but as the WhatsApp backup isn’t on the actual user-facing “iCloud Drive” there’s no way to recover this data.

    What bothered me more back then and sometimes still bothers me is how my own mistakes contributed to losing all my chat history. Just not fucking up one single part of this would’ve resulted in me having a working backup of all chats/a working live version on the old phone. It was completely unnecessary to instantly wipe the old phone for example. I absolutely hate fucking something up that I’m not able to fix/do anything about.

    One thing I can tell you is to focus on what lessons you take away from this. What I took from this is to of course be more careful, but also to not trust proprietary/cloud-based backups. In the back of my head I always wanted to backup my iCloud Photo Library locally to my NAS, but I never did it. I searched for an app that automatically backs up original versions of all photos/videos to my Synology NAS and I now have a regular, automated, append-only backup of all my iCloud photos. I backup personal data from my NAS to an external SSD weekly, and have a separate cloud backup of the most important data running every night.

    Then there’s also time. Time lets you get past most things. Sure, you’ll probably think back once in a while and think “oh damn”, but then you’ll move on the next second and it’ll be fine. Trust me.


  • “ASRock” and “ASRock Rack” are two different series of motherboards.

    Here’s the QVL of one of their AM5 mainboards: https://www.asrockrack.com/general/productdetail.asp?Model=B650D4U-2L2T/BCM#Memory - it doesn’t limit these modules to specific CPUs. All CPUs with ECC compatibility also support these modules on this mainboard. Some of these Rack boards are over a year old, and they always had some ECC modules on their QVL. This - again - isn’t EPYC 4004 specific, they couldn’t have validated it with EPYC 4004 CPUs a year ago. In fact, their CPU support list doesn’t even list EPYC 4004 CPUs as of today, as they haven’t released a BIOS update adding (official) compatibility in for these CPUs (it will probably be released shortly though).

    ASRock Rack AM4 mainboards also officially support ECC memory. So if you wanted verified ECC support on a comparatively cheap AMD platform you could’ve always gone for one of these boards with a regular Ryzen CPU (not an APU). The boards are a bit on the expensive side but if you want official support (for whatever reason you’d need that in a homelab environment) you can get it.