Separate names with a comma.
Appreciate the shout-out but @(GalaxyMaster) deserves most if not all of the praise. He has taken the mantle of tracking down every issue. I...
Or, it's saving the checksum/serial number/unlock code or whatever ties the VM to that particular machine in Keychain, which is likely the safest...
The KB Robot, @GampaA@Parallels, and his 'recommended' article fail to mention an extremely important fact that if you are using the TPM Chip you...
FC35 just updated to kernel 5.18.4 and am happy to say the update from 5.17.14 was completely seamless with the patch installed. Cheers,...
I am absolutely certain if you search this forum you will find out how to do it.
If you log out of root you need to use sudo. If you're already logged in as root, you don't use sudo.
Wait... that was stupid of me. You're already logged in as root, so there's no need for sudo. Just run ./install.
Are you entering the correct root password?
Damn. Was worth a shot. As a developer, I get the impression that trying to merge Intel and ARM in the same distribution was massive mistake for...
I'm just guessing here, but is the USB to the vinyl cutter USB 2.0 or 3.x? Wonder if something they changed for ARM did something weird in the way...
@ChipM No, don't reinstall... that's a complete waste of time and it shouldn't have been recommended. Shut the VM down if it's running then double...
Not sure when this started happening, but I'm noticed this problem in Linux and Windows VMs, manifesting in different ways for quite a while. BTW:...
Why: Windows has a completely different set of keystrokes. Where Apple uses Cmd, Windows (and Linux) uses Ctrl. Conversely, the Cmd key is used to...
Parallels Team's first ever participation into this thread of 24 posts is to say "your welcome" to a "thank you" that was clearly meant for...
Maybe he's 'instigating' again.
I'm still on FC35 (kernel 5.17.12 as of yesterday), but I'm sure it's fine (no self-pun intended).
Turns out it's not just Intel. Red Hat-based kernels require the prl_eth fix.
Huh? Did you not see that the above patch was to be applied TO 17.1.4... TO FIX IT? So, the answer is no, not for this, nor for the other things...
Cheers!
Oh, I've already fixed it by conditional omission. It was in my amended patch for 17.1.2, and still hasn't been fixed in 17.1.4 so I had to...