VirtualBox for many Puppies
Hello.
I have installed VirtualBox 4.1.8 in SnowPuppy020. When I start ReactOS in it, I get error: "Kernel driver not installedd (rc=-1908). The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdriver. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup' ".
When i execute /etc/init.d/vboxdrv setup, it fails, even if I load kernel_src-2.6.38.4-lupe20.sfs.
Do you have an idea?
Thanks.
I have installed VirtualBox 4.1.8 in SnowPuppy020. When I start ReactOS in it, I get error: "Kernel driver not installedd (rc=-1908). The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdriver. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup' ".
When i execute /etc/init.d/vboxdrv setup, it fails, even if I load kernel_src-2.6.38.4-lupe20.sfs.
Do you have an idea?
Thanks.
Yes, pemasu, thank you, the kernel source you gave me link, solved the problem:
http://www.smokey01.com/pemasu/Kernel_s ... -lupe5.sfs
http://www.smokey01.com/pemasu/Kernel_s ... -lupe5.sfs
-
- Posts: 1
- Joined: Fri 09 Dec 2011, 04:00
Thanks!
Upgraded 414 to 418 without a hitch. Desktop Icon didn't even need an update. Realized this is where I got the 414.
Thanks for the work on these pets and the info on what goes with what. And the audio info... i knew something was wrong but didn't know it was the usr or the app.
Regards,
Ralph.
Thanks for the work on these pets and the info on what goes with what. And the audio info... i knew something was wrong but didn't know it was the usr or the app.
Regards,
Ralph.
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
I've just upgraded my guest Puppy VM to Slacko 531, from Puppy 431. Guest additions (on VBox 4.1.8 ) work- mostly. To resize the display, I have to resize the VM window, then restart X on the guest, but it will then adjust itself just as it should.
I'll see if I can't make a dot-pet of the guest additions. If it works well, I might make guest additions for other Puppy versions, too.
See you all in a bit...
EDIT: Well, X is falling apart on the VM a little more each time I boot it. Strike that idea. I'll try a few other things, but- as usual- no guarantees.
I'll see if I can't make a dot-pet of the guest additions. If it works well, I might make guest additions for other Puppy versions, too.
See you all in a bit...
EDIT: Well, X is falling apart on the VM a little more each time I boot it. Strike that idea. I'll try a few other things, but- as usual- no guarantees.
- michaellowe
- Posts: 66
- Joined: Sat 17 Dec 2011, 08:33
- Location: The Garden
Win XP Pro Black Ed install issue in Virtual box 4.0.0
Hello, this has been a source of much frustration.
I want to be able to run Win XP Pro in Virtual Box 4.0.0 as I have this loaded as an sfs on the fly in Puppy 5.2.5 which as I understand is supposed to help relieve the memory a little?
Everything went smoothly up until the installation of the win xp pro.
in the VM please find attached a .png file: a screen shot of the message I get, something to do with can't access and lock memory? Have you come across this before? i have also attached a log file of the installation if it may help shed some light into the probem I am faced with. please pay particular attention to line 702 through to line 715 in the log file: vbox.zip which sums up what was going on at the time of the error message
I have the kernelsource sfs and the lupu_devx525.sfs required for my version of puppy loaded as instructed in the vbox usermanual so I can't see why i am getting this error message, what am I missing?Just checked the VBox log and the host ram is 487mb ram available is 232mb
Please help
Kind Regards
M
I want to be able to run Win XP Pro in Virtual Box 4.0.0 as I have this loaded as an sfs on the fly in Puppy 5.2.5 which as I understand is supposed to help relieve the memory a little?
Everything went smoothly up until the installation of the win xp pro.
in the VM please find attached a .png file: a screen shot of the message I get, something to do with can't access and lock memory? Have you come across this before? i have also attached a log file of the installation if it may help shed some light into the probem I am faced with. please pay particular attention to line 702 through to line 715 in the log file: vbox.zip which sums up what was going on at the time of the error message
I have the kernelsource sfs and the lupu_devx525.sfs required for my version of puppy loaded as instructed in the vbox usermanual so I can't see why i am getting this error message, what am I missing?Just checked the VBox log and the host ram is 487mb ram available is 232mb
Please help
Kind Regards
M
- Attachments
-
- VBox.zip
- (61.64 KiB) Downloaded 591 times
Re: Win XP Pro Black Ed install issue in Virtual box 4.0.0
You can change 'Default Machine Folder' to /mnt/home/VirtualBox or somewhere.michaellowe wrote:Everything went smoothly up until the installation of the win xp pro.
in the VM please find attached a .png file: a screen shot of the message I get, something to do with can't access and lock memory?
The setting is at VirtualBox menubar, File>>Preferences>>General.
See also:
http://www.murga-linux.com/puppy/viewtopic.php?t=62110
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
Oh, I am interested in 64-bit, but in a way that doesn't much help, as I have no access to any 64-bit machines on which to create the necessary packages! Alas, I've yet to receive a 64-bit monster for Curbside Christmas!sebus wrote:TheAsterisk!, not that I complain, but you are not interested in x64?
sebus
That being said...
I've been in forum-based correspondence with TaZoC, who makes the puplet "Lighthouse Pup," which I believe is 64-bit, and apparently he's developed some sort of scheme in LHP whereby users can slickly download and install the latest VirtualBox release from Oracle's site, with prepared scripts handling the messy details. If I can figure out what's going on in that, once I have a chance to dissect it (TaZoC hasn't sent me the scripts yet, as far as I know), I'll see what I can do about putting a solution up in this thread.
The issue, of course, would be that I can't test it, so we'll see what happens as it comes up. Keep your fingers crossed, though!
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
I'm going to be eliminating some of the redundant VirtualBox packages tonight and tomorrow. All the version 4.1.8 and 3.x.x packages will be left alone, as will the dot-pets that compile their drivers upon installation, but the other ones are subject to my discretion, and may be cut out if the same Puppy has a newer package available.
As always, if you need an older package for some reason, let me know within the next few weeks. I'll keep some local copies around for at least a little while, just in case.
As always, if you need an older package for some reason, let me know within the next few weeks. I'll keep some local copies around for at least a little while, just in case.
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
I've gone through and removed old VBox packages from my host. I've also decided that since it didn't generate any issues that I'm aware of, the newer package organization, with VBox itself separate from Puppy version-specific drivers, is the way ahead. The more ordinary packages (combined VBox and drivers) have been removed for both VBox 4.1.6 and 4.1.8. (That tidying-up did away with over 770 MB of redundant packages, all said and done.)
If anybody needs a copy for reference or any other reason, you can either send me a message or post a request for it. Otherwise, simply combining the "base" dot-pet and the drivers dot-pet for your Puppy will also produce more or less the same package, if you know how to do that.
Anyway, if any of my rearranging the furniture caused anybody any trouble, all things should be settled now, so go ahead and hit that refresh button or try it again!
If anybody needs a copy for reference or any other reason, you can either send me a message or post a request for it. Otherwise, simply combining the "base" dot-pet and the drivers dot-pet for your Puppy will also produce more or less the same package, if you know how to do that.
Anyway, if any of my rearranging the furniture caused anybody any trouble, all things should be settled now, so go ahead and hit that refresh button or try it again!
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
Added a drivers package for Slacko 5.3.2.6 with kernel version "3.1.10-slacko_4gU"
Slacko 5326 is a beta/preview release. Use it only if you want a sneak peak ahead, or want to help test the new version. Do not yet use that Puppy version if you want a stable, official release.
Icyos was trying to get VBox up and running on 5324. I couldn't find any kernel sources or devx SFS for 5324, but could find it for 5326, so I made a package.
Note that this package is not for the PAE version of that release.
Slacko 5326 is a beta/preview release. Use it only if you want a sneak peak ahead, or want to help test the new version. Do not yet use that Puppy version if you want a stable, official release.
Icyos was trying to get VBox up and running on 5324. I couldn't find any kernel sources or devx SFS for 5324, but could find it for 5326, so I made a package.
Note that this package is not for the PAE version of that release.
Hello TheAsterisk!
Just do as 01micko said in this thread
and rename devx_slacko_5.3.2.1.sfs to devx_slacko_5.3.2.4.sfs
Hope this helps
Catdude
.
You can find them hereTheAsterisk! wrote:...I couldn't find any kernel sources or devx SFS for 5324....
Just do as 01micko said in this thread
and rename devx_slacko_5.3.2.1.sfs to devx_slacko_5.3.2.4.sfs
Hope this helps
Catdude
.
[img]http://www.smokey01.com/CatDude/.temp/sigs/acer-futile.gif[/img]
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
Yes, CatDude, that does help! Sometimes, I feel like I can't read at all. Thanks for the help!CatDude wrote:Hello TheAsterisk!
You can find them hereTheAsterisk! wrote:...I couldn't find any kernel sources or devx SFS for 5324....
Just do as 01micko said in this thread
and rename devx_slacko_5.3.2.1.sfs to devx_slacko_5.3.2.4.sfs
Hope this helps
Catdude
.
I guess the version numbers (5321 versus 5324) and my impatience threw me off on the first go.
I suppose I'll make a package for that version as well, then!
EDIT: Package added for Slacko 5324.
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
Quick note regarding TaZoC and the scripts from LHP for installing 64-bit VBox:
Apparently, TaZoC is not well. (See this post.) I wasn't aware of that, but it would explain why I haven't heard from him.
Sorry to finally hear/read about that, TaZoC. Hope you can recover and get better soon.
Given that news, though, I think I'll try to download a few versions of LHP, and though I can't run the 64-bit versions on my systems, I can at least try to dig out the relevant scripts, etc., from the ISO images or packages, as the case may be. Maybe someone else can make something of them, or maybe they might even work as they are.
Apparently, TaZoC is not well. (See this post.) I wasn't aware of that, but it would explain why I haven't heard from him.
Sorry to finally hear/read about that, TaZoC. Hope you can recover and get better soon.
Given that news, though, I think I'll try to download a few versions of LHP, and though I can't run the 64-bit versions on my systems, I can at least try to dig out the relevant scripts, etc., from the ISO images or packages, as the case may be. Maybe someone else can make something of them, or maybe they might even work as they are.
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
virtualbox-4.1.10.sfs
virtualbox-4.1.10.sfs for Puppy 4.3.1 and most of Puppies 5.x including Lucid Puppy and Slacko.
Does not support 64-bit nor old Puppy's before 4.3.1.
Available from http://shino.pos.to/party/bridge.cgi?puppy/opt/
If you have ever installed another or older virtualbox PET/SFS and trying new, remove old ones and delete '/lib/modules/*/misc/vbox*.ko', /opt/VirtualBox, if they are exists, before loading the new.
virtualbox-4.1.10.sfs has kernel modules for:
2.6.21.7
2.6.25.16
2.6.30.5
2.6.31.14
2.6.32-smp
2.6.32-uni
2.6.32.28
2.6.32.55
2.6.33.2
2.6.37.6
2.6.39
2.6.39.4
3.0.17
3.0.7
3.1.10-slacko_4gA
3.1.10-slacko_paeA
3.1.10-dpup
3.2.11-dpup
Does not support 64-bit nor old Puppy's before 4.3.1.
Available from http://shino.pos.to/party/bridge.cgi?puppy/opt/
If you have ever installed another or older virtualbox PET/SFS and trying new, remove old ones and delete '/lib/modules/*/misc/vbox*.ko', /opt/VirtualBox, if they are exists, before loading the new.
virtualbox-4.1.10.sfs has kernel modules for:
2.6.21.7
2.6.25.16
2.6.30.5
2.6.31.14
2.6.32-smp
2.6.32-uni
2.6.32.28
2.6.32.55
2.6.33.2
2.6.37.6
2.6.39
2.6.39.4
3.0.17
3.0.7
3.1.10-slacko_4gA
3.1.10-slacko_paeA
3.1.10-dpup
3.2.11-dpup
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
- TheAsterisk!
- Posts: 406
- Joined: Tue 10 Feb 2009, 08:52
-
- Posts: 452
- Joined: Thu 20 Mar 2008, 01:48
Thanks asterisk...
also here is the vbox addition and extension pack.
extension pack can be installed from terminal using virtualbox,
ie:
$virtualbox virtualbox.extension.pack.files
http://download.virtualbox.org/virtualbox/
also here is the vbox addition and extension pack.
extension pack can be installed from terminal using virtualbox,
ie:
$virtualbox virtualbox.extension.pack.files
http://download.virtualbox.org/virtualbox/
Cluster-Pup v.2-Puppy Beowulf Cluster
[url]http://www.murga-linux.com/puppy/viewtopic.php?p=499199#499199[/url]
[url]http://www.murga-linux.com/puppy/viewtopic.php?p=499199#499199[/url]