I suppose if you don’t know what you’re doing - that’s true. It’s not something unique to nvidia either - it’s true of any drivers outside the kernel source. But that’s what dkms is for - it automatically handles it for you when you update your kernel.
If you don’t want to learn how the system you use works then you suffer the consequences. Or you just continue to blame nvidia for your own ignorance as I’m sure you will.
If you don’t want to learn how the system you use works then you suffer the consequences.
No consequences here. I’m perfectly happy continuing on using AMD.
you just continue to blame nvidia for your own ignorance as I’m sure you will.
It’s nothing to do with my ignorance and everything to do with me simply not want to spend hours upon hours digging through forums and entering commands that do nothing.
Why do you think AMD always work out of the box and people constantly have problems with Nvidia? Is it because they’re “ignorant” or because it’s unnecessarily convoluted?
No consequences here. I’m perfectly happy continuing on using AMD.
Sure - and you’re limited to systems that use an AMD chip. Consequences. I’m sure you justify this to yourself though.
Why do you think AMD always work out of the box and people constantly have problems with Nvidia? Is it because they’re “ignorant” or because it’s unnecessarily convoluted?
I don’t think - I know. Because one is integrated with the kernel and built and distributed with it and the other is a separate module. This isn’t something unique to nvidia either - my system has modules from system76 as well as v4l2loopback that are also compiled separately.
But since I install my packages using “apt” they are all managed by dkms and I don’t need to worry about it. Because I took a few minutes to learn about how my computer works.
![[Solved] Sorry if this not related to this community because I don't know where to ask, but should I buy this laptop? and does it play nice with Linux.](https://lemmy.ca/pictrs/image/a4dfcf61-653f-46ae-bcc4-c3608b2bc33f.jpeg){kind=link}
I suppose if you don’t know what you’re doing - that’s true. It’s not something unique to nvidia either - it’s true of any drivers outside the kernel source. But that’s what dkms is for - it automatically handles it for you when you update your kernel.
If you don’t want to learn how the system you use works then you suffer the consequences. Or you just continue to blame nvidia for your own ignorance as I’m sure you will.
No consequences here. I’m perfectly happy continuing on using AMD.
It’s nothing to do with my ignorance and everything to do with me simply not want to spend hours upon hours digging through forums and entering commands that do nothing.
Why do you think AMD always work out of the box and people constantly have problems with Nvidia? Is it because they’re “ignorant” or because it’s unnecessarily convoluted?
Sure - and you’re limited to systems that use an AMD chip. Consequences. I’m sure you justify this to yourself though.
I don’t think - I know. Because one is integrated with the kernel and built and distributed with it and the other is a separate module. This isn’t something unique to nvidia either - my system has modules from system76 as well as v4l2loopback that are also compiled separately.
But since I install my packages using “apt” they are all managed by dkms and I don’t need to worry about it. Because I took a few minutes to learn about how my computer works.
Once again, not a consequence.
You know…what?
My guy, I don’t even know what these words mean. And with AMD, I don’t have to become a software engineer. It just works.
This is the literal definition of a consequence. 🤣
Fucking hell…
…what is?
…was there something you wanted to add?
Consequence: “a result or effect of an action or condition.”
e.g “being stuck buying only amd kit”
Oh no, absolutely nothing else to add. I don’t want to confuse you with “software engineer speak”. Enjoy the self-imposed ignorance.
For the third time, not a consequence. Consequence implies some sort of sacrifice.
Excellent, glad to hear it. 👍