Slackware :: Virtualbox Usb On 13.1 - No USB Support
Dec 29, 2010
I downgraded a computer a couple of weeks ago from -current to 13.1. At that point in time the USB support in my Virtualbox stopped working. Since then I have installed Virtualbox on my wife's laptop, which also runs 13.1, and the USB support doesn't work there either. So I tried it on yet another 13.1 box that I have lying around no USB support. Then I upgraded the latter box to -current and USB works! Given that sequence of events, I'm pretty sure this is a Slackware 13.1 problem rather than a Virtualbox problem. what might be causing this?
I know a lot of discussion has been made about this issue, but I cannot seem to find an answer that works. I have used VirtualBox for a few years and just adding the user to group vboxusers used to work.Before that I had to add the user to usbusers or something like that. Now niether completely work.I say completely, because the only usb device available for use is my printer nothing else. Here is what I have done: added 'user' to the group vboxusers (gave me usb printer access but nothing else)
-attempted an old fix involving mounting /proc/dev/usb/ (or something like that) and get an error that that file does not exist ran virtualbox with sudo with full functionality (just to see)
I swear I was using this about 6 months ago with no issue. I also have installed extensions pack, and need to say I have tried every forum suggestion I could find before coming here.
trying to understand the two underlined sentences below I got to ask Step by step. I created a new group called usb. I inserted a usb printer and scanner. I tried to find the file usbfs and there is where get stuck already. I only can find a folder with that name. The sentence (3 -) makes almost no sense to me.
a) modify file /etc/fstab clear open terminal, go to etc, su gedit fstab
b) inserting a line yes I understand that!
c) the right path and the number corresponding the "usb" group :
This is my humble tutorial on how to get VirtualBox properly up and running on Fedora 11 (including USB support). It's located on my web blog here: How To: Install VirtualBox on Fedora 11 [Tutorial]
I saw many linux OSes have a smooth stability with sun virtualbox.for example VBoxaddons already initially installed.I installed fedora 12 x86_x64 (within vbox in xp64bit)but only 800x600 resolution is avaible.Smooth Mouse jumping from Pc to vbox etc.
1.is there any good installer that have already packages initially installing for virtualbox ? 2.Which version listed below have x64 kernel?
I installed Slackware 13 in VirtualBox 3.1 (seehere)When I'm logged in as a normal user, I get a mesage that Intel *** (sound device) doesn't work anymore and I hear no sound.But it works very fine when I'm logged in as root.
I have installed multilib support in my 64bit slackware 13.37 installation than I proceed it to install google earth from slackbuilds... and did ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3Now when I try to run google earth I get:[ 760.092745] googleearth-bin[3647]:segfault at 984f7d31 ip 00000000984f7d31 sp 00000000ffbfe100 error 4
I downloaded from http://ftp.nluug.nl/os/Linux/distr/s...ce/n/net-snmp/ source and I build new package and works ok no errors. If I change net-snmp.SlackBuild and add CFLAGS --with-mib-modules=ucd-snmp/lmSensors --with-ldflags=-lsensors while I need lmsensors support in net-snmp. But the package compiling ends with error:
How much support does Slackware have for drivers?I have an Asus motherboard, and the onboard sound doesn't work with Ubuntu, and also it won't recognize my HP printer.Would I have better luck with Slackware?
I am trying to convince the "higher ups" in a small office of about 15 users about migrating from windows to Slackware, one question I have is how long after a release are security updates available? I subscribe to the security mailing list and often see updates that go as far back as Slackware 8.0. What would the safe number be? 5 years, 10 years? Longer? Any input would help me with my cause of eliminating windows all together.
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
I have an ISO of 13.37, I have selected the ISO as the booting medium in the Virtual Box and I do get uptil the screen where one is supposed to select the source media. Because I am installing from an ISO what option I am supposed to select out of the 6 present there?
The latest release of VirtualBox (3.1.6) corrects most of the problems that I had with Slackware and KDE. If you have been avoiding VirtualBox or KDE because of those issues you might want to take another look.The only problem that I'm having now is that I have to click somewhere on the desktop to get a proper display when switching VirtualBox into "seamless" mode. The rest of the window display issues appear to be fixed and full screen mode also works correctly.
Virtualbox, is great, except that I have no wireless networking or USB support. Problem one, is USB support. As far as I know there is a personal free use version of Virtualbox that includes USB support, however I can't find this copy to download it. Any ideas where I can find it? Second problem, I have an integrated wireless networking card in my laptop, that Ubuntu recognizes with no problems, but Virtualbox can't even "see" the device. I found a tutorial that addresses this know issues with wireless and Virtualbox, but I don't understand the instructions
[URL]
Quote:
Wireless Networking Setting up a normal bridged network generally doesn't work if you're bridging from a wireless card to VirtualBox. A simple script that utilises the parprouted tool will allow your VM full access to the wireless network. You will require parprouted to do this: sudo apt-get install parproutedNext, using your favorite text editor, create and edit the script, for example:
sudo nano /etc/network/if-up.d/vbox_networkThen, enter the script (replacing $USER with your username (or whoever you intend to run virtualbox as)). Replace wlan0 with the name of your wireless interface. Use an available IP address on your network for tap0 (I have used 192.168.1.100 in this case):
sysctl net.ipv4.ip_forward=1 VBoxTunctl -b -u $USER ip link set tap0 up ip addr add 192.168.1.100/24 dev tap0
parprouted wlan0 tap0Finally, make sure the new file is executable by root: sudo chmod 700 /etc/network/if-up.d/vbox_networkNow your networking script is installed, the virtual interface tap0 will be available on boot for VirtualBox. Rather than reboot, let's just run the script now:
sudo /etc/network/if-up.d/vbox_networkThe final thing to do is tell VirtualBox to use the new virtual device tap0. Open VirtualBox, highlight a VM and click settings. Now choose the network option and select Host Interface on the 'attached to' drop down menu.
In the Interface Name text box, enter: tap0 Click ok and start your VM. The VM should now behave as though it was another physical machine on your network!! For more information on the process up to this point, please visit Bridged Networking with VirtualBox on Linux Hosts Using DHCP in the Guest VM It was possible to get DHCP to work on the guest virtual machine. Instructions were taken from here. Because parprouted does not relay multicast, we need to use an additional helper daemon to manage this. I tried dhcp-helper and bcrelay, and had the most success with bcrelay.
Use it as follows:
sudo apt-get install bcrelay sudo bcrelay -i tap0 -o wlan0At this point, my /etc/network/if-up.d/vbox_network is as follows: #!/bin/sh sysctl net.ipv4.ip_forward=1
[code]....
bcrelay -i tap0 -o wlan0 &It seems that I have to start the script by hand after boot. Other than that, host networking now seems to work fine (this issue should be solved by adding the "#!/bin/sh" line just at the beginning of the script.
Installed 13.1 as a guest in VirtualBox with Debian Lenny 5 64bit as host. The mouse, gpm, and the keyboard work alright at the black screen but in the graphical thing, forget its name.....Xsomething, not KDE, there is no mouse or keyboard; for example the screensaver just goes on and on and nothing will stop it.
Since my upgrade to 13.37 + VirtualBox 4.0.4 (from SBo) I'm having trouble with one of my VMs containing a PostgreSQL installation (also from SBo) which has been running fine before on 13.1 + VBox 3.2.10.
This is what happens: I'm starting an I/O heavy job on the DB that should take about an hour but never finishes because the virtual disk stops working after 10 to 40 minutes.
Code: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen ata1.00: failed command: READ FPDMA QUEUED ata1.00: cmd 60/00:00:e8:11:44/01:00:02:00:00/40 tag 0 ncq 131072 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) lots of these
Just grabbed Slackware64-current and installed on my laptop. Also put Alien Bob's multilib on.need it for my Absoft fortran compiler.The problem I'm having is that VirtualBox-3.1.6 doesn't install. I've looked at other problems on the list related to this and I don't think that any of the ones that I've seen applies to my situation. My feeling is that there is an incompatibility problem with gcc. The stock kernel was compiled with gcc-4.4.3 which comes with Slackware64-current. However, Bob's multilib backdates this to gcc-4.3.3. So, when the Virtualbox installation procedure runs it sees a kernel compiled with a version of gcc that is different from the one that is currently installed and chokes. recompile the kernel with the current gcc. Haven't done a kernel compile in a long time though and I'd like to get it right. So, my question is "Is the stock .config file in the linux source folder the one used to configure the default kernel?". I like the stock kernel and would like to recompile with all the bells 'n whistles in the stock kernel.
I am running Windows XP in VirtualBox. I generally only use it for iTunes and some light browsing occassionally. Downloads only occur on iTunes, but it does have internet access. And my wife will still only use Windows, so if she uses this particular machine it is available to her, and she occassionally goes to facebook on this machine.
Should I install an anti-virus? Is it really necessary? I am pretty certain my Linux install would be unaffected even if a virus or other malware did occur in VirtualBox.
I'm trying to run Slackware 13.37 64-bit in a VirtualBox virtual machine. My VirtualBox version is 3.2.12. I had to disable compositing to keep the X-Server from reporting a segfault.Now the problem is that on logout from KDE I get a completely black screen. I can switch to a console session and type commands to get the login screen again.
telinit 3 telinit 4
I tried editing "kdmrc" to add the line "TerminateServer=true" but it had no effect on the problem.I had this working with Slackware 13.1 at one time, but I can't seem to get it working properly now even without desktop effects.I'm trying to avoid changing my VirtualBox software since each version seems to just introduce new and different bugs. The 4.X versions are not yet very stable.
I'm trying to compile virtualbox 3.2.10 con slackware current 32bit through sbopkg
I get this error (I'll copy only the end part)
Code: CXX VMMR3 - {C}/src/VBox/VMM/VMMAll/TMAllCpu.cpp cc1plus: warnings being treated as errors In file included from /tmp/SBo/VirtualBox-3.2.10_OSE/src/VBox/VMM/VMMAll/PGMAll.cpp:236:0:
I'm trying to install virtualbox on slackware 13 and I'm running into header issues I think...it says it can't find libcap..any ideas? I downloaded libcap from slackbuild and tried to run make but I get errors (the second code block)
Code: VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_echo VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_cp VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_install VirtualBox-2.1.4_OSE/kBuild/env.sh patching file VBox.sh Checking for environment: Determined build machine: linux.x86, target machine: linux.x86, OK. code....
I need to evaluate PostBooks, an accounting packages that's 32-bit only,needs PostgreSQL and I only have Slackware 64-bit boxes available, I don't really want to install multilib, so I'm thinking VirtualBox for a quick and dirty (got the DVD, got 32-bit, got PostgreSQL, what the heck). Then I got to wondering -- before I screw something up, do you write to the virtual drive MBR or is there a better way?
I plan to install SlackBuild: virtualbox-ose (3.2.10) on my stand alone laptop.The following are excerpts from the SlackBuild Readme file and I was hoping that someone might have the time to clarify a few things: "By default VirtualBox will be compiled with hardening enabled. That means all binaries will be run suid root, which is the default behaviour of upstream packages. However, you are still able to disable this by passing HARDENING=no to the script."Why would I want to do this? If I did want to do this, how do I pass 'HARDENING=no' to the script? What script?
Edit: I found something on this and see that I'll just include my user in the proper group and I should be ok.'To compile virtualbox without the Qt4 GUI pass QT4=no to the script'I have a package called: qt-4.6.2_2d3d3e5-i486-1 installed - does this mean that I have Qt4 installed?'To enable the webservice pass WEBSERVICE=yes to the script. This adds gsoap to the list of required dependencies.'Why would I want to do this? If I did want to do this, how do I pass 'WEBSERVICE=yes' to the script? Also, to do this I would have to install gsoap first, right?'If you want to attach VirtualBox to a VDE network you will need vde2.I don't need this for my stand alone world, right?This requires acpica, and the virtualbox-kernel package is needed at runtime.'Does this mean that VDE network requires acpica or that this SlackBuild require acpica?
pretty comfortable at the command line and in kde. found 2 'supplementary kernel drivers' for virtualbox at slackbuild (thank you heinz!). followed the how-to at slackbuild and built and installed both packages, but additions weren't working. (i thought they were standalone) noticed the 'supplemental' in their description, and so installed the guest additions for linux from vbox site. additions still not working. at this point i start restarting my slackware vm, and redoing everything in various sequences. finally, additions work! but i'm not sure why! critical pieces and sequence for getting guest additions working once i have slackware installed?
I'm having trouble compiling virtualbox-ose.SlackBuild 3.1.6 on Slackware64 13.0 with multilibs made from the Slackware64 13.0 dvd iso. I've changed arch to x86_64 and libdirsuffix to "". acpica.SlackBuild built successfully and virtualbox-ose.SlackBuild is attempted built after running ". /etc/profile.d/32env.sh" as specified in the multilib documentation. All is well until..
I tried to build the virtualbox 3.1.6 kernel using the files from slackbuilds.org and I got this error that says it cannot find the kernel include directory. My current kernel is 2.6.33.2 (slack 13.1).
I tried SOME_VAR=/usr/include --> (I forgot the exact variable name, but I used the variable name I saw in the error message) just a guess , but it didn't work of course.
Is it at /usr/src/linux-2.6.33.2/include or something like that? Or is there anything wrong with the slackbuild script?
I installed in my Slackware 13.1 with generic kernel 2.6.33.4-smp VirtualBox packages taken from SlackBuilds.org (acpica, virtualbox-ose and virtualbox-kernel). Then for testing purposes I installed in VirtualBox Windows XP using CD-ROM drive connected to USB port. It's a lot of fun to see Windows as an application in Linux!
Now I'm trying to install in VirtualBox Linux Mint using either USB flash drive prepared with unetbootin or mere ISO image. Without success. It seems VirtualBox 3.2.10 OSE doesn't recognize either USB flash drives or ISO images though it recognizes CD-ROM drive connected to USB port. I found some advices searching Internet but all of them are useless.
I've tried been trying my hardest and tried researching as much as I can to get Mac OS X Version 10.6.3 in VirtualBox in slackware. I've found a tutorial but it was for previous versions of Snow Leop and it hasn't seemed to help me get mine to run. I get to the part where it should start loading the cd (I purchased a copy of Snow Leopard from Amazon) and the closest I've gotten is to what seems to be a bootup and a loading page of some sort. The screen goes gray with a Mac "busy" mouse icon on the screen.
PS - Running Slack 12.1.0.
PPS - I have the Snow Leopard disc that has "boot camp" on it
