SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I finally got Slackware 14.0 x64 up and running and it's been good so far. The only issue I have now is that USB does not exist for VMWare Workstation 8, whereas it did before upgrading from Slackware 13.37 x64. Anyone have any suggestions on this?
I have tried rebuilding the VMWare modules and while there were no errors during the build, my USB devices still do not show in VMWare. I'm using VMWare Workstation 9.0.1 after upgrading from 8.0.5 and this is happening in both versions. Thinking it had something to do with the stock Slackware 14 kernel, I compiled my own 3.6.7 kernel using the one from /testing, but no difference.
I had briefly created a new vm, but stopped prior to installing an OS into it. Assumed that it would show USB devices even without an OS and because it didn't, I also assumed that this issue would occur even with an OS.
I have tried rebuilding the VMWare modules and while there were no errors during the build, my USB devices still do not show in VMWare. I'm using VMWare Workstation 9.0.1 after upgrading from 8.0.5 and this is happening in both versions. Thinking it had something to do with the stock Slackware 14 kernel, I compiled my own 3.6.7 kernel using the one from /testing, but no difference.
I had briefly created a new vm, but stopped prior to installing an OS into it. Assumed that it would show USB devices even without an OS and because it didn't, I also assumed that this issue would occur even with an OS.
I think you need to add the following to your /etc/rc.d/rc.local file:
Code:
/etc/init.d/vmware-USBArbitrator start
Run it manually to test it first. Make sure VMWare is not running first. Hope this helps!
I think you need to add the following to your /etc/rc.d/rc.local file:
Code:
/etc/init.d/vmware-USBArbitrator start
Run it manually to test it first. Make sure VMWare is not running first. Hope this helps!
I'll give it a shot tonight, but it's weird that I would have to add that... VMWare Workstation 8 was working fine before upgrading the Slackware 14.0.
I'm not sure at what point they started doing that. I remember that being a gotcha when I first tried their latest version of VMPlayer. I believe that for rpm based distros, that is already enabled using chkconfig.
I think you need to add the following to your /etc/rc.d/rc.local file:
Code:
/etc/init.d/vmware-USBArbitrator start
Run it manually to test it first. Make sure VMWare is not running first. Hope this helps!
WOW! It worked! That script is there and without ever rebooting the machine, I'm a little surprised why the install script for VMWare never started it afterward. Anyhow starting that script and then opening VMWare has everything working again! Thank you!
WOW! It worked! That script is there and without ever rebooting the machine, I'm a little surprised why the install script for VMWare never started it afterward. Anyhow starting that script and then opening VMWare has everything working again! Thank you!
Awesome! Great to hear. That reason that is not enabled in Slackware by default is because VMWare expects either chkconfig or sysctl (systemd) to be installed. Otherwise, you have to start those scripts manually. I believe that is the only other one script, other than the default, that you need to worry about.
Awesome! Great to hear. That reason that is not enabled in Slackware by default is because VMWare expects either chkconfig or sysctl (systemd) to be installed. Otherwise, you have to start those scripts manually. I believe that is the only other one script, other than the default, that you need to worry about.
Hrmm, but this file is located in /etc/rc.d/init.d along with vmware and vmware-workstation-server with the +x attribute. Don't all executable files in /etc/rc.d including /etc/rc.d/init.d get run during boot?
Hrmm, but this file is located in /etc/rc.d/init.d along with vmware and vmware-workstation-server with the +x attribute. Don't all executable files in /etc/rc.d including /etc/rc.d/init.d get run during boot?
No, you have to add it manually to /etc/rc.d/rc.local as far as I know.
No, you have to add it manually to /etc/rc.d/rc.local as far as I know.
What about the /etc/rc.d/rc?.d directories? I believe those are processed based on runlevels, in which rc2.d, rc3.d and rc5.d all have links pointing to their respective scripts in /etc/rc.d/init.d. vmware-USBArbitrator is one script linked in the rc?.d directories.
What about the /etc/rc.d/rc?.d directories? I believe those are processed based on runlevels, in which rc2.d, rc3.d and rc5.d all have links pointing to their respective scripts in /etc/rc.d/init.d. vmware-USBArbitrator is one script linked in the rc?.d directories.
Hmm...interesting. I'm not sure. I don't think I've looked that deep into the rc?.d directories. I just always put it manually on rc.local. That will always work. :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.