I’ll say it. Cats have bad work ethic.
I’ll say it. Cats have bad work ethic.
I’m not having a great time with DisplayLink driver support, personally. Various applications I use with mixed levels of support too, along with missing out on Windows specific GPU features.
This has been my most successful round of Linux adoption, but there are still niggling issues and confusion. The biggest difficulty is that my accumulated support knowledge of like 20 years is useless and I am relearning basic issue identification and resolution processes.
The internet being a raging dumpster fire, support is kind of patchy on more niche topics. All the good, useful discussions are largely happening behind closed doors at this point on everyone’s Discords and whatnot.
Bitwarden is too functional and too affordable for me to really consider moving.
That’s the real sticking point for me, it is a problem for my desire to transition to Linux as a daily driver.
I’m on DietPi 9 and the latest version for Debian 12 is 1.17.1, sadly. Though I do see 1.19.1 is in testing as of today, according to Debian’s package tracker site. Probably not worth trying to install an unstable version of it.
I think the worst I watched was someone speaking for 5-10 minutes about their bitter divorce before getting to the subject matter.
As long as the router has the IP explicitly reserved for the device your PiHole is running off of then it won’t be reassigned.
I’m very happy with my little PiHole on a Pi Zero 2 W running DietPi, easy set up and then you can just forget about it apart from periodic updates. No issue with it being via WiFi either, which makes placing it much easier.
My first thought on this was immediately “did you also reserve that static IP address on your router to make sure it remains assigned”. From what I’ve read that does seem to be the issue, so that’s a little validating.
I’m going to try to take this in the spirit that it was provided, but you’re using a lot of "…"s, and a lot of implications that what I’m saying is obvious, for a person trying to provide earnest assistance. I wasn’t requesting technical support or expressing surprise at these things, I was merely expressing that these were the things I was generally encountering difficulty with my transition to Linux as a daily driver.
The DisplayLink driver for instance is running, and basically functional, but ends up running slowly, with distortions, and instability. It also isn’t signed, so my plan to still run Secure Boot with the distro I’m using alongside Windows is out (without a lot of faff), but that largely won’t matter excusing some specific work setups that I don’t currently have to worry about. Having useful AMD specific driver level tools on Windows that don’t exist in Linux isn’t a surprise, it is a discouragement.
Forum content and non-Reddit content are a pain to locate, especially when you don’t know how to frame your problem in Linux syntax, as you say. Communities are either open but in specific places that I will never find without already knowing about it, or happening in places that aren’t accessible without having already joined, like the Discord of the specific software I need guidance on. My experience has been that there is basic info and there is advanced info out there, but intermediate info that lets you bridge the gap is a challenge to locate, especially with subtle differences in certain steps that are distro/package manager specific. Yet I press on.