[–] [S] 1 point 11 months ago

Wow, I had no idea about the green button info, thanks! I am not too bothered about VRR (it seems totally broken on Wayland for my GPU at the moment anyways, and I have been fine without it so far), but I bought this TV for the 120Hz and good colors, which so far have been mutually exclusive :P

  • source
  • parent
  • context
  • [–] [S] 2 points 11 months ago

    My understanding is that it doesn't have VRR for people (at least without the special firmware, which indeed only works for some). Not seen anything about it not supporting 4k@120Hz, though maybe I missed it as I read so many different threads about this topic...

  • source
  • parent
  • context
  •  

    I recently purchased a LG OLED C2 TV, which supports 4k120Hz but only has HDMI 2.1 ports. I am aware of HDMI 2.1 being an issue on AMD, even though my GPU is Nvidia (RTX 3060Ti) I want to switch to AMD in the future, so I opted to invest in an AMD-friendly setup. I purchased the Cable Matters active DisplayPort -> HDMI 2.1 converter mentioned in this Reddit thread, which purportedly can do 4k120. However, when I change it from the default 4k60 modeline to 4k120, the TV shows a "no signal" message. In fact, to get 120Hz I need to drop the resolution down to 1440p.

    Even though I'm not going for VRR (yet), I also tried flashing the VRR-enabled "Spyder" firmware just in case it fixes the refresh rate (it does not). I tested every DP port on the 3060Ti as well, with no changes. What might I be doing wrong?

    [–] 3 points 1 year ago (2 children)

    What makes a flake config a flake config is simply the flake.nix entry point. So, technically if you read that file to see what file it loads for the nixosConfiguration you want to "port", you should be able to just go directly from that file and bypass the flake.nix. For the longest time, my own flake simply forwarded to my configuration.nix.

    However, depending on your needs of course, but using flakes even at a basic level can be very useful and I'd 100% encourage doing a basic setup for someone starting out. The main feature here is being able to lock your dependencies (including nixpkgs) to a specific commit, which means you will always get the same resulting setup (not depending on when you installed it, like it does without flakes). But, you know better than me the requirements of your own setup :)

  • source
  • [–] 2 points 1 year ago (4 children)

    My work self hosts Gitea because Forgejo doesn't support Windows. While I agree with Forgejo's decision, it sucks to be basically stuck with an old pre-fork version of the forge I self-host.

  • source
  • [–] 6 points 1 year ago

    Yet enforcing your copyright is exclusive to the rich. I had to move off of GitHub because of Microsoft infringing my code licenses and selling them as "GitHub Copilot", and I have no way of fighting back/recover my losses.

  • source
  • parent
  • context
  •  

    Hi! I hope this post is on-topic enough. I've just moved into a flat in Germany and its thermostat has an incredibly loud clock ticking every second. My landlord allows me to replace it, so I looked for options and learned it uses a proprietary interface (Vaillant 7-8-9) and my only real option is from the brand Tado. I e-mailed them and confirmed their V3+ wired model is compatible... but costs 220€; way above my budget. However, if I set the site to Germany the price drops to 100€.

    Before spending so much on a device (100€ is still a lot!), I'd love to check whether I can use it with Home Assistant. I recently installed it on a spare SBC and got the zbdongle-e working, ready to start connecting things. I found (cw: AI image) this blog post that says it works by having HA emulate Apple's HomeKit, does this mean it should work fine, regardless of the zbdongle-e? Should I be aware of any caveats to this approach, or to the Tado thermostat itself?

    Thanks :)

    view more: next ›