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

help-circle



  • This isn’t a Windows thing, it’s a firmware thing. It’s HP’s doing, and HP is well known for screwing with the usability of their devices. In my case, on my Victus, it’s F10 that opens UEFI, but the menus are incredibly stripped down. Looking online, F10 seems to be the key to access it on your device, too. Maybe you just aren’t getting the timing right, sometimes you gotta mash the absolute hell out of that button to get it to register. Once you do get it, setting a post delay will make it easier in the future.



  • Yeah, maybe. My experience has been a multitude of hangs and flash drive rewrites. At first, I thought my flash drive might be bad, so I tried another and quickly determined that the other one was actually bad before going back to the first. Eventually, I ended up just unplugging everything out of desperation and for some reason that worked.

    I’m actually still working on this as I type this, currently waiting on partition changes because, while I read that 500MiB is recommended for Pop’s boot partition, the installer has told me that it’s too small…

    Since I’m still dealing with this, and given the issues I had booting the live disk, there’s a good chance this won’t even be useable in the end. I’ve used Ubuntu before, and it boots fine, but fuck if I want to deal with snap.

    Edit: Went up to 750MB (yeah, MB not MiB here, easier to think about later). Still says it’s too small. Sure wish I had some detailed documentation to work with here, instead of just “use Clean Install” in the official docs and a single Reddit comment saying “500MiB is good.” That would the bee’s damned knees.

    Edit 2: Works fine once installed. The live disk just would not boot with anything else plugged in for some reason.









  • They admitted they were slowing users with ad blockers, but many Firefox users reported experiencing the slowdown regardless of whether they used an ad blocker.

    The article I linked, however, says that they couldn’t get the delay to happen at all, so it’s entirely possible it was just so poorly implemented that it was affecting people almost at random.


  • Except that they’ve already displayed that they won’t. Recently, Firefox users were targeted with an artificial delay on YouTube. When caught, they claimed it was about ad blockers… Except it didn’t affect chrome users with adblock and affected Firefox users without adblock.

    And this has happened multiple times over the years, where little headaches and inconveniences would crop up on Google services, all of which could be fixed by changing your user agent so the site thinks you’re running chrome.