Chrisswh's Posts

This is perfect, I'm going to implement this for my own system. Thank you for your time, hopefully this will help others as well.
Just to clarify on the TPM maintenance, for the vmware certificates i used sudo mokutil --import MOK.der which I'm guessing means MOK.der is where the certificates are stored for vmware on the TPM, n... See more...
Just to clarify on the TPM maintenance, for the vmware certificates i used sudo mokutil --import MOK.der which I'm guessing means MOK.der is where the certificates are stored for vmware on the TPM, next time there's a kernel update and i need to update my certificates again i can just do sudo mokutil --delete MOK.der to remove them and redo the cert signing process to get vmware back up and running right? There no risk of me getting locked out of my desktop because deleted the ubantu keys right? MOK.der in this instance is strictly for vmware kernel modules right?   kind regards, Christopher
its working! Thank you so much its been a really frustrating morning. To those having facing the same issue its 5 easy steps: First install vmware player/workstation pro then open terminal: openss... See more...
its working! Thank you so much its been a really frustrating morning. To those having facing the same issue its 5 easy steps: First install vmware player/workstation pro then open terminal: openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=My Name/" sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmmon) sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmnet) sudo mokutil --import MOK.der now reboot and re-enroll your key.  
Hello, I'm running a fresh install of Ubantu LTS 22.04.2 on Dell XPS intel 12th gen, secure boot enabled.   First step to getting VMware WS pro 17 to work, Sign the vmmon module:   Sign the vmmon... See more...
Hello, I'm running a fresh install of Ubantu LTS 22.04.2 on Dell XPS intel 12th gen, secure boot enabled.   First step to getting VMware WS pro 17 to work, Sign the vmmon module:   Sign the vmmon module: A. Generate a signing key by running the following command:   openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=My Name/"   This will create two files MOK.priv and MOK.der.   B. Sign the vmmon module by running the following command:   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmmon)   C. Register the key with Secure Boot by running the following command:   sudo mokutil --import MOK.der     reboot, re-enroll.   Secure Boot self-sign complete. -------   Now my vmware VMs can boot up however networking still isn't working, no virtual adapters are showing up.   things I've tried:   sudo nmcli networking on   sudo apt-get update sudo apt-get install build-essential linux-headers-$(uname -r) sudo apt-get install gcc make sudo vmware-installer -u vmware-workstation sudo vmware-installer -i vmware-workstation   sudo nmcli networking on   NOTE* when running > sudo vmware-modconfig --console --install-all ----> (This command will rebuild and install all VMware kernel modules,   including the network adapter module.)   Starting VMware services: Virtual machine monitor                                 failed Virtual machine communication interface                     done VM communication interface socket family                  done Virtual ethernet                                              failed VMware Authentication Daemon                                  done Unable to start services     It seems like VMware is unable to start up certain services pertaining to its networking functionality.   This should be an easy endeavor, im on a clean install of ubantu LTS 22.04.2 and officially supported Dell hardware, this should be almost plug and play what am i getting wrong here? can someone please help me.... when running this command it gives me the following output in at the end of its execution. its possible i have to sign additional modules, so for i've only signed vmmon, its possible the network adapter has its own module that needs to be signed if thats the case please let me know how to go about that step by step, it took 3 lines of code to get vmmon signed and running, its possible i have to concatenate the other modules to the original secure boot self sign. Unfortunately disabling secure boot in not an option, i need this running with secure boot enabled.