Puppy Linux Discussion Forum

[rasul]

VirualBox gives the following warning when it starts and has no sound as a consequence:

"No audio device could be opened. Selecting the NULL audio backend with the consequence that no sound is audible. Error ID: HostAudioNotResponding".

Any idea how to have sound in my guest Windows XP?

PS. My Upup Raring has sound and it plays nicely all my audio and video files, so there is no sound problem in the host. Only to mention.

[TheAsterisk!]

UPDATED to release 4.2.12.
Finally! Got my mirrors working again!

[rasul]

Actually currently I am on Upup Raring 3.8.7 but as far as my memory could help I had the same issue also on Upup Raring 3.8.4.2 . But I followed you suggestions and changed the host audio driver in VB's setting for my Guest OS to PulseAsuio and OSS and both made my Guest OS having audio perfectly, although as you already know at the cost of temporarily losing audio in the Host OS, but never mind, when I am in the guest I am there and very rarely may I need simultaneous audio also in host. Good if it will be fixed but anyway at least now I can hear the audio of the apps that I have windows only for working with them!

Warm thanks for your kind answer

Oh, meanwhile, I also installed pulseaudio but it didn't make any success in having simultaneous audio in host and guest.

Also if I decide to use the 3 series versions of VB, would I lose the USB and folder sharing capabilities? ( although I could not set up a folder sharing yet, at least the way I was doing so in other distros ;( )

[James186282]

I hate asking for help so much but I've spent a couple days (nights) on this and I'm starting to loose it. Its probably an "operator error" also known in the Air Force as a "Short circuit between the headphones"

I've installed all the proper pets for Slacko 5.5 and I have devx, linux header files etc. The VirtualBox gui comes up ok but when I try to create a Virtual Machine the "Type" entry is blank. Scrolling up and down doesn't show any options for file format. I had tried using an old .sfs version first so I figured I had some kind of messed up system.

So I tried to run the setup script
/etc/init.d/vboxdrv setup
For the most part it seems to work. I see
Stopping VirtualBox kernel modules ...done
Removing old VirtualBox pci, netadp, netflt, kernel module(s) ...done
Then its tells me
modprobe: invalid option -- 'l'
Starting VirtualBox kernel modeules ...done.

I think this is line #163 in the rc.vboxdrv
if [ "$(modprobe -l vboxdrv)" = "" ]; then

This looks totally kosher to me so I tried
modprobe - l to list my modules and got the same invalid option error.
modprobe -V tells me its Version 9
modprobe --list) and get the same error.

This seems very odd. Can anyone thump me over the head and tell me what I'm doing "rong"

[James186282]

Sooo... in slacko 5.5 kmod replaces modprobe. Thus its not operating exactly the same.

Which explains the inability to -l LIST modules. It also explains the Version 9 which seemed like such a huge jump from the 2. something in previous puppies.

I don't want to volunteer but I wonder why kmod doesn't process the same setting that modprobe does? I understand modprobe is no longer being worked on. But here is a general question. I "get" working on things to fix bugs. I get the desire to add features. I also get the desire to make small systems so things like busybox might be a dual improvement. Whats wrong with leaving well written (Bug free) programs alone? One reason I dislike windows is the bloat and chronic updates that almost never fix bugs but make them backward compatable features.

This will probably nuke my installation but I wonder if adding back all the modprobe utils (and leaving kmod where it is) is smart? ie it won't blow up the system.

modprobe: invalid option -- 'l'
Starting VirtualBox kernel modeules ...done.

I think this is line #163 in the rc.vboxdrv
if [ "$(modprobe -l vboxdrv)" = "" ]; then

I haven't made a lot of progress but I started a fresh install of Slacko 5.5 and am trying to compile source directly from Oracle. But if you hear faint cursing in the distance thats probably me.

I've had some luck compiling things and having them work but they always seem to older X programs or CLI type programs like Kismit. Is there anyone doing a system with minimal abstraction layers. Like an X only (No GTK QT Cairo layer) super tiny puppy?

[tiangeng]

PrecisePuppy5.7.1,kenel is 3.9.11

[shinobar]

virtualbox-4.2.18-1.sfs(updated on 2013-10-08) for Puppy 4.3.1 and most of Puppies 5.x including Lucid, Precise Puppy and Slacko-5.6.
Available from http://shino.pos.to/party/bridge.cgi?puppy/opt/

It has pre-build kernel modules for Puppy-4.3.1, Wary-511, Lucid, Precise-5.5/5.6.1/5.7.1, and Slacko-5.6.
As for the Puppy-4.3.1, need to install SDL.
For other kernels, you need devx and kernel source packages to build the kernel modules.
Type 'virtualbox' on a terminal after loaded the virtualbox-xxx.sfs.

[shinobar]

(UPDATE: 23-Oct-2013)
virtualbox-4.3-1.sfs for Puppy 4.3.1 and most of Puppies 5.x including Lucid, Precise Puppy, Slacko-5.6 and more.
Available from http://shino.pos.to/party/bridge.cgi?puppy/opt/

It has pre-build kernel modules for Puppy-4.3.1, Wary-511, Lucid, Precise-5.5/5.6.1/5.7.1, and Slacko-5.6.
Built-in kernel versions:
2.6.30.5
2.6.32.28
2.6.33.2
2.6.37.6
3.10.5
3.2.29
3.2.44
3.2.48
3.4.52
3.8.5.1
3.9.9-upup
3.9.11
For other kernels, you need devx and kernel source packages to build the kernel modules.

As for the Puppy-4.3.1, need to install SDL.
ftp://distro.ibiblio.org/puppylinux/pet_packages-4/SDL-1.2.13-i386.pet

See the detail:
http://www.murga-linux.com/puppy/viewtopic.php?t=63332&start=4

[umair]

hello every one:
I managed to run vbox in Carolina 1. but I when I created the VM. I am facing the following problem. Anybody have an idea about that ?
Thnx in advance.

[umair]

[umair]

[quote="umair"]

[TheNH813]

@TheAsterisk!
Thanks again for something I needed! I need XP in a VM to print stuff till I get the driver im hacking up working.
BTW: I like your profile image, that hilarious smile crossed with a puppy. Its genius!

[TheNH813]

@umair
Is network sharing disabled in VBox prefs? If not, I believe the Virtualbox Host networking module is missing, corrupted or not compatible with your NIC. Search the Debian repos for the Virtualbox and try installing the package from there using Puppy Package manager, with verify dependencies checked/enabled. All I can think of is a bad module or missing library at this time.

[umair]

[Pete22]

I am running lighthouse pup with Linux-kernel-3.8.7 recompiled in 6.02 from Fatdog64 config.

I don't see a version of the download for this kiernel.

Can you help me?


Pete