aka. dont use OpenOffice

cross-posted from: https://lemmy.ca/post/21305656

[Feature Request] Vote for a Proton VPN App for Ubuntu Touch on ProtonMail’s UserVoice Forum

https://protonmail.uservoice.com/forums/932836-proton-vpn/suggestions/47523629-ubuntu-touch-app

hi so i recently switched my GPU to an AMD card from an Nvidia one. Im wondering if there is an easy way to remove all the nvidia packages on arch.

thanks in advance ^^

SOLUTION:

I was missing this package sudo dnf install rocm-hip-devel as per instructions here: https://fedoraproject.org/wiki/SIGs/HC

Hi, I'm trying to get GPU acceleration on AMD to work in Blender 4.1 but I can't seem to be able to. From what I've seen it should be working with ROCm just fine but I had no luck with it.

I'm using Fedora 40 GNOME with Wayland and my GPU is RX 6800 XT.

System is up to date. I've also installed all these packages:

sudo dnf install rocminfo

sudo dnf install rocm-opencl

sudo dnf install rocm-clinfo

sudo dnf install rocm-hip

and restarted system after.

rocminfo gives me this

rocm-clinfo gives me this

___``___

The tl;dr for those like me, who don't understand the technical parts:

This week we merged support for the VK_EXT_image_drm_format_modifier extension in NVK, the new open-source Vulkan driver for NVIDIA hardware. We've also back-ported the code to the Mesa 24.1 staging branch so it will be part of the upcoming Mesa 24.1 release.

DRM format modifier support is one of the most important features we've landed in NVK in a while. Though it's not a very interesting feature to most Vulkan applications or game developers, it's very important to the Linux display pipeline. Importantly to users, this is the last piece required to support GameScope. It's also an important piece in making Zink+NVK a robust OpenGL solution.

cross-posted from: https://lemm.ee/post/32128978

Switching from Endeavour OS to Nobara

Hi all, I've been having issues with my favorite games on EndeavourOS Linux. Also, on top of that, an update the other day deleted my whole plasma desktop and left me with a skeleton of SDDM. I got it fixed, but some things are still wonky. I'm honestly getting tired of maintaining it and I just want something that just works for my video games and some coding. Nobara sounded awesome after some research. I do have a couple of questions for you all before switching:

1. Is Nobara atomic? Immutable? Or whatever those distros are called.

2. I have my /root, /home separate each in their own drive, plus a 3rd one for my steam and other games. Since I'm coming from Arch and I'll only be formatting my root drive, what folders/files will I need to remove from my /home directory after switching to Nobara so I don't have issues?

3. Since I separate drives for everything, I'll be doing a manual partitioning when I install Nobara, and will be choosing btrfs for my /root so I can do snapshots with timeshift. My question is, does Nobara set up the subvolumes automatically for me when I do manual partitioning, or do I need to set them up myself?

4. How hard is it to set up snapshots in grub?

5. Or does Nobara have a back up tool already that already does snapshots?

Thank you.

Most of the functionality is present but many important bits are still being developed.

What is it?

You can use Smokeless_UMAF to configure almost all options on AMD systems including UMA Buffer size (For systems like the steamdeck and laptops), RAM overclocking, CPU power states and voltage settings, and much more, even if your system's BIOS doesn't expose the option for you.

Tutorial for increasing your UMA buffer on an AMD Phoenix Laptop

Boot into a FAT32 drive with the downloaded Zip extracted to the root, and then use the "Device Manager" section to locate the UMA buffer size.

The location within the utility is at

Device Manager > AMD CBS > NBIO Common Options.

Once set, back out and apply the changes, rebooting your system. You can then confirm that the option has been applied by checking your system monitor of choice (Windows > Task Manager, Linux > Whatever) and checking to see if your available RAM has decreased (indicating greater allocation of memory to the iGPU).

This may not remain applied through BIOS updates, and may cause hardware damage if misconfigured, and may result in an unbootable system if misused or by chance. You may need to reset your BIOS if that's the case, if possible by your system manufacturer.