I cannot speak for this card itself, but moving from Nvidia to AMD made my life so much easier. Wayland works a treat, and updates never leave me with a black screen from silly diver issues. However anything for local llms is a massive pain in the ass to use compared to Nvdias cuda, rocm is quite half-baked.
Amongussussyballs100
Pixels second hand are decently cheap from my experience
I do not like Apple as a company and would never buy direct. This one is second-hand and much cheaper than a framework. I would definitely buy a framework if that was an option.
I would not even consider it if it was 8GB, but this one is 16GB with 512gb of storage. It is a decent deal for what it is, and I've been looking for a decently powerful arm machine for awhile.
What is this cube everyone is so happy about?
WHAT! might I ask if you need any special version of discord? Or does audio sharing just-work on wayland
I got an all amd msi laptop with ryzen 7 5800h and rx6700m a few month ago, and it's been great. Wayland compatibility was ridiculously good compared to the nvidia 3060 desktop I had previously, not to mention no fear of a completely black screen on update. If I had to complain about something it would be no real cuda support, and I still cannot get my llm working with rocm.
Thank you so much, adding --disable-gpu to /opt/Mullvad VPN/mullvad-vpn solved it. Thank you for your time
Thank you for your answer. It does not matter if it is X11 or wayland, both have the issue.
I have tried to upload an image of nvtop (I think it was done correctly?) and it seems like a mullvad service is using the dgpu for some unknown reason. I have no clue why it is doing this, as it does not on KDE. I do not know how I would force this to use integrated so any help would be appreciated.
This looks like an interesting project. Can the vpn container only route traffic that are in other containers, or can regular applications get their traffic routed by the vpn container too?
Sorry for the late reply, I also did not have a Debian system running. Installed it on an old laptop I had lying around to find the error. Seems like its due to Debian changing something around debian 10. Its still possible with systemctl reboot.
How well does the M1 chip keep up? What size models are you running with it? Interested in getting an M1 laptop and I am curious.