Domi @ domi @lemmy.secnd.me

Posts

1

Comments

385

Joined

2 yr. ago

Same here, even asked the developer if the Steam Deck is supported but they couldn't tell me.

Refunded it for now, might check back next sale if it works and the microtransactions are acceptable.

I mainly use it instead of googling and skimming articles to get information quickly and allow follow up questions.

I do use it for boring refactoring stuff though.

Those are also the main uses cases I use it for.

Really good for getting a quick overview over a new topic and also really good at proposing different solutions/algorithms for issues when you describe the issue.

Doesn't always respond correctly but at least gives you the terminology you need to follow up with a web search.

Also very good for generating boilerplate code. Like here's a sample JSON, generate the corresponding C# classes for use with System.Text.Json.JsonSerializer.

Hopefully the hardware requirements will come down as the technology gets more mature or hardware gets faster so you can run your own "coding assistant" on your development machine.

That depends, we have quite a few images that are just a single shell script or a collection of shell scripts which run as jobs or cronjobs. Most of them are used for management tasks like cleaning up, moving stuff or debugging.

Has the big advantage of being identical on each node so you don't have to worry about keeping those shell scripts up to date with volumes. Very easy to just deploy a job with a debug image on every node to quickly check something in a cluster.

Of course, if the shell script "belongs" to an application you might as well add the shell script in the application container and override the start arguments.

Environments like Kubernetes only run containers so you would deploy any shell script with containers as well.

Anything interesting going on in the kernel log while connection doesn't work?

If so, you could maybe write a bug report at the amdgpu repo.

One thing I could imagine that is happening is that Linux chooses a higher chroma subsampling than on Windows. Had that issue before with a monitor that had a wrong EDID. Unfortunately it's a real pain to set the chroma subsampling on Linux with AMD.

That's strange, 6.6.14 is the same version that's on Fedora currently. My friend with a 7900 XTX is still on 6.5.0 so I can't get him to test that version right now.

Fix is merged already though: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9c2f0338bbd132a4b12b988004d796798609d297 Should hopefully not be long before it is backported.

Having a bleeding edge kernel can and will come back to bite you. There's a reason why many distros hold back with kernel updates for so long, there's issues that only can be found with user feedback.

From experience, "stable" in the kernel world doesn't mean much unfortunately. I encountered dozens of issues over various versions and different hardware already and it's the main reason I don't run rolling release distros on my main rig.

There's also been enough times where the latest Nvidia driver borked my test system at work so I'm fine with just not running the latest kernel instead.

Over DisplayPort? That's interesting, I knew AMD can't do HDMI 2.0 but there shouldn't be a problem with DP.

Might wanna try a proper new certified DP 2.1 cable, just to be safe.

I "only" drive a AW3423DW but no issues at 3440x1440 with 165Hz.

Since people normally only report on negative experiences: I was lucky enough to get a reference AMD 6900 XT during the GPU shortages.

Switched from Ubuntu to Fedora for it because Ubuntu didn't have firmware for it yet.

Ever since then it has been a rock solid GPU. Never even had such a stable GPU under Windows.

Have been running Fedora with Wayland for more than 2 years now and can count the crashes on a single hand, most were my fault.

I'm sure once that issue is sorted out that GPU is going to ride along for years with minimal maintenance required.

(You might want to downgrade your kernel until then though)

I would not depend on DNS records being private. On the off chance that one of the nameservers messes up, I would prefer if no subdomains are leaked.

But you're correct, most of the time those leaks happen somewhere else.

You can avoid these scans by only using wildcards on your DNS entries and SSL certificates.

Both of these are commonly used by bots to find new domains.

Will have to try that, also a good way to one-up my neighbor with those CDs hanging outside. :)

Already have a few of those, always a good party gag for the ones that know.

Yes, I've got quite a few types, good idea.

Thanks for the artist view on things. :)

I mostly want something pretty to look at but adding a message to it is an excellent idea.

I have like 30 old hard drives laying around and have been thinking about doing a cool art installation with them for a while.

Maybe shatter the platters to create a spiky landscape and epoxy them in, or something like that.

Any ideas?

Definitely go with K3s instead of K8s if you want to go the Kubernetes route. K8s is a massive pain in the ass to setup. Unless you want to learn about it for work I would avoid it for homelab usage.

I currently run Docker Swarm nodes on top of LXCs in Proxmox. Pretty happy with the setup except that I can't get IPv6 to work in Docker overlay networks and the overlay network performance leaves things to be desired.

I previously used Rancher to run Kubernetes but I didn't like the complexity it adds for pretty much no benefit. I'm currently looking into switching to K3s to finally get my IPv6 stack working. I'm so used to docker-compose files that it's hard to get used to the way Kubernetes does things though.

I prefer to do things properly once rather than do it again every day.

For example, I have an automation that I can trigger from my phone with a single button that does all these things:

• Lowers all my blinds in the living room
• Turns on all lights in the living room and dims them a little bit
• Powers up the smart plugs for my projector, receiver and player(s)
• Sets the correct volume and source on the receiver
• Starts playing random music in my living room

The alternative would be to do each of these steps manually, every day I get home. I'm lazy, probably wouldn't do it all or just leave stuff running.

IoT devices (the non-shitty ones that don't connect to the internet) become useful together when they are automated.

I use an 6900 XT and run llama.cpp and ComfyUI inside of Docker containers. I don't think the RX590 is officially supported by ROCm, there's an environment variable you can set to enable support for unsupported GPUs but I'm not sure how well it works.

AMD provides the handy rocm/dev-ubuntu-22.04:5.7-complete image which is absolutely massive in size but comes with everything needed to run ROCm without dependency hell on the host. I just build a llama.cpp and ComfyUI container on top of that and run it.

It does not.

ROCm runs directly through the open source amdgpu kernel module, I use it every week.