

1·
3 hours agoIf I have to read about the topological naming problem one more time…


If I have to read about the topological naming problem one more time…


remmina.
Auto scaling works way better than in the native msdtc client.


Had this happen with both, the Qualcomm and the MediaTek wifi7 chips when they came out. Took years for a fix in the driver. Vendor support for linux drivers is sadly still bad.
I think it’s a Self Encrypting Drive. https://wiki.archlinux.org/title/Self-encrypting_drives There are basically two standards out there, the most common should be OPAL:
Install sedutil https://github.com/Drive-Trust-Alliance/sedutil/wiki/Command-Syntax Check #sedutil-cli scan This should list your drive with the locked state. You can unlock it using this tool if you remember the password - or reset it using the PSID (long number a sticker on NVMes, here possibly internal so you’ll have to open the case or read it from Samsung Drive Magician?) with the aptly named “yesIreallywanttoERASEALLmydatausingthePSID”.
Also in Samsung Drive Magician there should be an option for “Secure Erase” - which does the same thing and removes the password protection. But not for some drives, had the issue with a EVO Pro 990 - but the OEM variant, which Drive Magician macically no longer recognizes as a Samsung drive and refuses to cooperate.