|
Post by pharrisire on Jun 18, 2010 14:48:52 GMT -5
I thought I could keep KNOS up and running AND have access to any of programs I might need that are installed on the hard drives by running KNOS in VirtualBox. It almost worked too - it booted up fine all the way to the finished desktop. The menus dropped down like normal , then 'poof', they'd disappear. So everything LOOKED right, it just didn't ACT right. Rats. I was gonna do everything in KNOS, but if I had something 'unKNOSable' I'd just switch screens instead of having to reboot. Yeah I know, I'm lazy.
|
|
|
Post by Kevin McAleavey on Jun 18, 2010 16:32:59 GMT -5
I thought I could keep KNOS up and running AND have access to any of programs I might need that are installed on the hard drives by running KNOS in VirtualBox. It almost worked too - it booted up fine all the way to the finished desktop. The menus dropped down like normal , then 'poof', they'd disappear. So everything LOOKED right, it just didn't ACT right. Rats. I was gonna do everything in KNOS, but if I had something 'unKNOSable' I'd just switch screens instead of having to reboot. Yeah I know, I'm lazy. Sorry to hear that. I've never played with VirtualBox, but have with VMware and chances are VMware might fare better, but we don't have the funding to go after that as yet. We do have the ability to put out KNOS in an IMG format for VM's as a normal part of our build process but with all the headaches we had with Verizon's crappy DSL trying to get the ISO's uploaded over an entire week of fail, never bothered to even try to upload those IMG files. I trust you tried to feed VB the ISO file? Our Read-onlies might have been a problem for it or else for some reason VB might not fully support BSD, at least not in our unique RO mode. Thanks for giving it a shot tho' ... once we have some money, we'll pursue a happier answer there ...
|
|
|
Post by pharrisire on Jun 19, 2010 4:44:00 GMT -5
There are still plenty of options to try - (enable IO APIC, EFI,PAE/NX, VT-x/AMD-V, nested paging, etc......) - and, No, I don't know what they all mean but it is more than enough to keep me from sitting on the porch in a rocking chair with a quilt on my lap!
One unrelated oddity: On the desktop I normally (w/ xpp, pubuntu, SimplyMepis, etc..) hear any thing I'm listening to with the volume control way down- roughly 10%, but to hear the same thing in KNOS I need to crank the volume dial wayyy up -roughly 80% - to hear it. This is not a problem - UNLESS I forget to turn it back down when rebooting - then Ouch!!!
|
|
|
Post by Kevin McAleavey on Jun 22, 2010 3:39:06 GMT -5
There are still plenty of options to try - (enable IO APIC, EFI,PAE/NX, VT-x/AMD-V, nested paging, etc......) - and, No, I don't know what they all mean but it is more than enough to keep me from sitting on the porch in a rocking chair with a quilt on my lap! One unrelated oddity: On the desktop I normally (w/ xpp, pubuntu, SimplyMepis, etc..) hear any thing I'm listening to with the volume control way down- roughly 10%, but to hear the same thing in KNOS I need to crank the volume dial wayyy up -roughly 80% - to hear it. This is not a problem - UNLESS I forget to turn it back down when rebooting - then Ouch!!! I've noted that on a handful of machines in testing myself. In the ones around here, everything seems to have pretty loud sound, but almost always with the volume thingy cranked almost the way up. On Macintoshes though, it's quite weak. I think it might have something to do with "gain block" ... in other words, most audio devices require a boost setting in their firmware and it appears as though what we're using now only uses the default "gain block" and can't kick up the amplifier beyond whatever level it comes up in when the machine boots. Right now, I'm looking at where we're going with the next build but have marked this up as something to check into in a saner moment in time. I'm not sure that the coders who set up the ESS and Pulseaudio stuff even bothered to code that so far or there would have been a configure tweak. I haven't seen any so far, but am still looking for one ...
|
|
|
Post by pharrisire on Oct 2, 2010 8:02:07 GMT -5
(still trying - now it just stops at "Starting avahi-daemon.')
Which fork of BSD is most compatible with KNOS? - FreeBSD, OpenBSD, or NetBSD
|
|
|
Post by Kevin McAleavey on Oct 3, 2010 3:19:08 GMT -5
(still trying - now it just stops at "Starting avahi-daemon.') Which fork of BSD is most compatible with KNOS? - FreeBSD, OpenBSD, or NetBSD Curious indeed ... I'm going to have to guess that your problem there is running out of silicon somehow ... nothing in KNOS can change, thus the mystery. Something on the main machine hosting the emulator must have run you down and is reporting the wrong amount of RAM available to KNOS. As to KNOS, the beta 2 is running FreeBSD (largely - that's what we started with) with many modifications. The version of BSD in KNOS was the current as of June which is now their official 8.1 release version but with heavily modified "world" for KNOS. But it's the same kernel and security stuff as the FreeBSD 8.1 release. We've been having more than our share of adventures with their final release - too broken still for us to use, particularly the gnome 2.30 part of it which is *highly* broken. For our next release, we're sticking with the 2.28 gnome which we managed to stabilize nicely. 2.30 is not going to happen here until they manage to fix it. Just wanted to let you know about that before you find out yourself with the *real* BSD. DO let me know how it goes ... I was hoping for more feedback as to KNOS than we've gotten ...
|
|
|
Post by Kevin McAleavey on Oct 3, 2010 3:24:30 GMT -5
Oh ... since I'm seeing this again ... found a way for you to get the volume issue solved. Mentioned it in the "tricks" portion in another thread. If you right click on the top toolbar, and then select "add to panel," it will bring up a list of addons. In there is an item marked "Volume control." If you add that, you can control the volume level of the sound source. Once it's on your toolbar, RIGHT click it and select "Preferences." You can then select "PCM" (which is usually the device that has the low volume) and use the second volume control to turn that up. Solves your "blasting" problem if you didn't notice the trick elsewhere here.
|
|
|
Post by pharrisire on Oct 4, 2010 13:31:52 GMT -5
>"Curious indeed ... I'm going to have to guess that your problem there is running out of >silicon somehow .."
You nailed it - I maxed out the memory available to it and it made it all the way! All this time and all it needed was more memory - SheeeWizzz!
Now if I can just get the 'Guest Additions' installed I'll be able to drag and drop my passwords from KeePass/PasswordSafe into the vm'ed KNOS..... a kludgey temporary work-around I know......
|
|
|
Post by Kevin McAleavey on Oct 4, 2010 17:22:01 GMT -5
>"Curious indeed ... I'm going to have to guess that your problem there is running out of >silicon somehow .." You nailed it - I maxed out the memory available to it and it made it all the way! All this time and all it needed was more memory - SheeeWizzz! Now if I can just get the 'Guest Additions' installed I'll be able to drag and drop my passwords from KeePass/PasswordSafe into the vm'ed KNOS..... a kludgey temporary work-around I know...... Drop me an email to support(at)knosproject.com once you get that all hooked up and get me your details on what you're doing and I'll see about adding support for it in our next build. I'm sure you're not alone in doing what you want to do there ... Yeah, VM's can be fun since I haven't seen one yet that completely emulates the hardware beneath fully.
|
|
|
Post by pharrisire on Jan 20, 2011 11:47:29 GMT -5
KNOS3 boots up fine in the new VirtualBox 4.02
As with the older version of VB and KNOS1 and 2: -Without getting GuestAdditions running the screen is limited to 640x480 so is kinda small -Reboot is normal
---The BIG change is that now Shut Down works normally where before it would just reboot. So something has changed in that regard, but I can't tell you if the change is VB or KNOS3.
|
|