iturnedintoanewt

Yeah...kinda. Now on multi-monitor setup I have a weird glitch...when one of the monitors are turned off. Screen will start flickering rearranging the windows. Weird.

Yeah thanks! I got it working in the end with the updated recent AMD firmware from the kernel release, updating to an 6.5-oem kernel, and rebuilding initramfs with the updated firmware files, as detailed here: https://askubuntu.com/questions/1451506/how-to-make-ubuntu-22-04-work-with-a-radeon-rx-7900-xtx

As most people suggested, I guess I don't need the proprietary drivers at all. I managed to get it working with kisa's ppa and an updated AMD firmware file for the kernel (and a quick initramfs rebuild). However I'm experiencing a weird glitch on multi-monitor setup now...

Thanks. I wasn't aware of the difference privative vs public ones on AMD. On Nvidia (where I came from) it's kinda the opposite, noveau kinda works, but if you really want to play with proper performance, you should head for the privative one. In the end it was just easier to download the AMD firmware from the latest linux release, and recompile with that. It worked after that.

Yeah well...out of the box I had a non-booting linux, and in safe mode it failed to recognize the secondary display :)

Yup...but out of the box I encountered a system failing to boot and unable to recognize my secondary display :)

Sigh...Just for the sake of it...It needed to recompile the kernel with the LATEST firmware you needed to download manually. Instructions here: https://askubuntu.com/questions/1451506/how-to-make-ubuntu-22-04-work-with-a-radeon-rx-7900-xtx

I changed the file download to the latest, which at this moment is linux-firmware-20231111.tar.gz. After the update-initramfs, reboot (since I already ran the PPA earlier...to no avail), and this time it worked, and it immediately showed me the second monitor, which had been dead for the last couple of hours since I started fighting this thing.

Again, incorrect. The answer is above. And still, you haven't read the thread. This is NOT about getting rescuezilla to install in the current PC. This is to get it to install in a DIFFERENT PC, which happens to be OFFLINE. So apt by itself will FAIL when it tries to resolve dependencies.

The whole mechanism of working of Clonezilla is about the least intuitive I have ever found. So many chances for errors/mistakes, especially if you're trying to do a network backup. Rescuezilla invokes clonezilla as a backup mechanism, but it saves you all the trouble with a way more intuitive UI. It's been a revelation to me since I found about it, and refuse to use clonezilla alone.

Still not correct. The path is perfectly correct. Even using full path. This method EXPECTS a repo package, not a file. I already figured the answer, it's in this thread.

Something something reading the post...

Thanks! How does this work with OS permissions? As it's rescuezilla and veracrypt I'm trying to use, both need access to the system partitions in order to be able to mount/read/copy to them. Flatpak can be a bit limited regarding permissions...Moreso on a live iso I guess.