DimensionQuest is a name I thought up in the mid-late 90's. It seemed to fit my interest in tech and sci-fi. 2022 marks a new beginning for the name as I'm returning to blogging, accompanied by detailed video tutorials on Linux, Virtualization, Self Hosting, Home Labs, and more. As a technology professional since the mid 90s, I have had the opportunity to work my way up in the industry. I have always been a fan of sharing the knowledge I have gained.
This is all way over my head. I don't know how to use the terminal. Why are so many things on Linux so hard to do, why is it so ... broken? Why can't things just ... work?
thank you so much for this! liked and subbed :) im running nobara and thankfully i can actually edit now! i looked at a forum on blackmagic design and their solution was to buy a windows 10 key. there is ALWAYS another way.
I followed the guide until the gpu fix. Did the gpu fix correctly and installed rocm-opencl but davici still dosnt see my gpu. I have a radeon 6700 xt! PS: the bash to download the 4 libraries. The link in the description are broken (youtube chaged the link, to do some redirectioning and that makes those link dont work!). Have to copy all 4 links by hand looking at the paused video! If you wanna change the descryption and use pastebin or something like that!
Code snippet removed from video description and replaced with link to GitHub Gist: gist.github.com/burkeazbill/f11099a970b22e99f5e13468bd65afff -- thanks again for reporting the issue!
If you're running Ubuntu 24.0.4.4 and VMware 17.5.2 just google this for the solution: Unable to install all modules" error while installing VMware Workstation Pro 17.5.2 on EndeavourOS
LOL, happy to hear it continues to work! I have to keep re-applying every few kernel versions or different Linux OS installs as my host. This video has helped me as much as it has helped others :D
Thank you! Yes, I have been quite busy due to work changes and requirements so I've had less time to be comfortable on my home lab environment. I certainly hope to get back into a better release cadence!
Is there any chance you've run make & sudo make install on that system before with the same source code?? If so, try doing a "make clean" first.. This looks similar to when I had tried to re-use existing code after a kernel update.
@harryf1ashman - thanks for the support. I appreciate you viewing and taking the time to come in and comment. I'm glad that my effort has paid off in the form of helping yet ANOTHER viewer that faced similar challenges as me!
sorry to say but the most useless video I have ever seen and the reason is that why you are not performing every step by yourself step wise. only taking that do this or that how can we understand. dont take my words as a criticism but hope you will take this make your videos better
Wow, harsh choice of words on content that has resulted in helping dozens of people get the software working… while I appreciate constructive criticism, this comment doesn’t quite qualify due to your choice of words. This is an old video that I produced to quickly help me and others get past an issue we face when using VMware Workstation on Linux. My intention is solely to get past the issue. This channel is a hobby. If I were actually being paid for the content, I’d probably put a little extra effort and research into trying to provide more details about the WHY on each thing. For my purpose, and a majority of people that find this solution, the video suits its purpose. Perhaps this whole comment was put through a translator and that resulted in the phrasing… well, in any case; thanks for watching!
Seems UTM has no concept of running the VM in the background and then connecting to the console. As soon as you start the VM on the macOS host, it starts the VM inside a window, and if you close that window, it kills the VM. The window is the running VM. Because of this, any remote viewing app like UTM Remote is doomed to fail - you can't have another app/window connect to the same session. So, the VM would need to be off in order for you to start it with UTM Remote before you can then connect to it. Once connected, you can't disconnect without killing the VM - so the advice is to shut it down gracefully when you are finished with it. Meanwhile, on the macOS host you are locked out of the VM. As it stands UTM Remote has no value. Even if it wasn't appallingly slow and unstable it would have no value. This is terrible. You thought was a UI problem, but it looks like it's worse than that, it's a platform design problem. It actually makes Hyper-V look really nice, and I despise Hyper-V. I think UTM is potentially a good way to spin up a macOS box for testing, but for literally anything else, Fusion or Parallels are the way to go. Given the whole VMware attacking their own customers thing, I'd lean towards Parallels. I don't trust Broadcom.
Yes, it does. There was a comment 3 weeks ago on my other video "How to fix Unable to Install all modules VMware Workstation Linux" by a user that confirmed this.
I do gotta say I feel a bit uneasy installing random things of github. But you did say they'd fixed this in the past, Do you think VMware will fix this in the future as well or do they simply leave their Linux releases broken like this indefinitely? If not maybe I could just wait it out?
This has been an issue for many years now due to the speed at which the open source community releases kernel updates vs. a big commercial company releasing a product. I've seen this github referenced by "internal" teams when running into issues with getting VMware Workstation installed and working under Linux. This has been, and continues to be, a valid solution to our problem. I'm not part of engineering or even the team responsible for it so I have no "official" word on this one way or the other - just what I've witnessed and experienced. You could try posting in the official communities to see if there is any "official" response to this continuing problem.
@@DimensionQuest I see. Thank you for the information and the insight. But if you say the repo is reputable and even referenced internally I suppose I'd go with that solution then. 👍
Woah! Thank you so much!! You’re the first Super I have gotten since the channel became eligible!!! I’m very happy that my content satisfied you enough for you to express such generosity!
Update Note: Make sure to re-download the latest available code from the github repo linked. This is frequently required due to the kernel updates in Linux. In recent (as of this comment) builds of the kernel, I have had to do the following for VMware Workstation Pro 17.5.2: Pre-Req: Make sure you have the following packages installed first: elfutils-libelf-devel kernel-devel kernel-headers - Download latest code from github (17.5.1 is latest there and works with Workstation Pro 17.5.2) - cd into the folder - run: make && sudo make install NOTE: If the kernel update (OS Upgrade) results in issue recurring and you are Still running Workstation 17.5.2, you must first CLEAN in the code folder (ONLY if re-using your last download): - cd into existing folder - make clean && make && sudo make install Otherwise, you get some sort of mis-match error when attempting make install. UPDATE 2024-06-30: I ran into problems with Fedora 40 running kernel 6.9.6-200.fc.x86_64 .. Here are the steps that allowed me to run Workstation again: git clone -b tmp/workstation-17.5.2-k6.9.1 github.com/nan0desu/vmware-host-modules.git cd vmware-host-modules/ sudo make tarballs && sudo cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/ sudo vmware-modconfig --console --install-all Source: github.com/mkubecek/vmware-host-modules/issues/257 Good luck everyone!!
@Canleaf08 - I updated my pinned comment with some extra details.. Do you have elfutils-libelf-devel kernel-devel kernel-headers installed? sudo dnf install elfutils-libelf-devel kernel-devel kernel-headers
Update Note: Make sure to re-download the latest available code from the github repo linked. This is frequently required due to the kernel updates in Linux. In recent (as of this comment) builds of the kernel, I have had to do the following for VMware Workstation Pro 17.5.2: Pre-Req: Make sure you have the following packages installed first: elfutils-libelf-devel kernel-devel kernel-headers - Download latest code from github (17.5.1 is latest there and works with Workstation Pro 17.5.2) - cd into the folder - run: make && sudo make install NOTE: If the kernel update (OS Upgrade) results in issue recurring and you are Still running Workstation 17.5.2, you must first CLEAN in the code folder (ONLY if re-using your last download): - cd into existing folder - make clean && make && sudo make install Otherwise, you get some sort of mis-match error when attempting make install. UPDATE 2024-06-30: I ran into problems with Fedora 40 running kernel 6.9.6-200.fc.x86_64 .. Here are the steps that allowed me to run Workstation again: git clone -b tmp/workstation-17.5.2-k6.9.1 github.com/nan0desu/vmware-host-modules.git cd vmware-host-modules/ sudo make tarballs && sudo cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/ sudo vmware-modconfig --console --install-all Source: github.com/mkubecek/vmware-host-modules/issues/257 Good luck everyone!!
Yes, ESXi is very particular when it comes to network cards. There are 3rd party vibs that can be used, but typically the easiest workaround is to get a USB NIC. William Lam has covered this pretty well in his blogs (both the vibs as well as the USB nics). In any case, thanks for watching and commenting!
Hmmm…. Are the permissions of the .ssh folder on Debian set properly? I’ve seen the same message when the SSH server I’m connecting to doesn’t have the proper permissions set on the folder and the file… responding from phone so can’t be more specific right now… Maybe this will help? superuser.com/questions/1822718/windows-11-ssh-fails-to-connect-using-a-private-key-specified-in-config …. Or maybe this one: learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_keymanagement
Steps you have done all I did to join with ad but when I am trying to log in, it gives me the error username or password is invalid though my password is so easy. can you please help me with it, I am using Ubuntu 22.04.4 LTS. please find below error "● sssd.service - System Security Services Daemon Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2024-06-05 11:31:58 IST; 1 day 4h ago Main PID: 550 (sssd) Tasks: 4 (limit: 9309) Memory: 68.4M CPU: 8.494s CGroup: /system.slice/sssd.service ├─550 /usr/sbin/sssd -i --logger=files ├─713 /usr/libexec/sssd/sssd_be --domain drcsystems.local --uid 0 --gid 0 --logger=files ├─718 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files └─720 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files Jun 05 11:32:08 ubuntu.test sssd[1313]: tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server not found in Kerberos database. Jun 05 11:32:08 ubuntu.test sssd[1313]: tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server not found in Kerberos database. Jun 06 11:32:07 ubuntu.test adcli[219110]: GSSAPI client step 1 Jun 06 11:32:07 ubuntu.test adcli[219110]: GSSAPI client step 1 Jun 06 11:32:07 ubuntu.test adcli[219110]: GSSAPI client step 1 Jun 06 11:32:08 ubuntu.test sssd[219112]: tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server not found in Kerberos database. Jun 06 11:32:08 ubuntu.test sssd[219112]: tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server not found in Kerberos database. Jun 06 11:32:08 ubuntu.test sssd[219115]: tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server not found in Kerberos database. Jun 06 11:32:08 ubuntu.test sssd[219115]: tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server not found in Kerberos database. Jun 06 16:02:13 ubuntu.test krb5_child[260868]: No credentials cache found (filename: /tmp/krb5cc_1194203982_iETT1h)"
Check the “Computers” container in your Active Directory server: is the ubuntu machine there? Your error says “Server not found in kerberos database” so that would be my guess…
I’m very rusty with Active Directory and have not attempted what you described. This thread may help: community.spiceworks.com/t/unable-to-join-domain-what-to-do/130845/10
[Fedora 40] (VMWare Workstation Pro 17.5.2 Kernel version 6.8.10-300.fc40.x86_64) Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded.
Whenever that comes up, the instructions in the video have to be followed again... I haven't run workstation for a couple weeks. I just launched it today and got the same message as you, except I'm still running Fedora 39. Even though I'm also using Workstation Pro 17.5.2, the latest branch in the repo is workstation-17.5.1. As noted in other comments, that DOES work for me and others running VMware Workstation Pro 17.5.2. Since my kernel is now up to 6.8.11-200.vc39.x86_64, I had to simply re-run "make" and then "sudo make install" in the folder as per the instructions in this video. Now, my Workstation Pro 17.5.2 is once again launching without issue... until another kernel version or Workstation version breaks it ;) Good Luck!
