User Support Forum

Questions/problems with Haiku? Post here and get help from the community. If you think you have found a bug, please file a bug report at dev.haiku-os.org.

Help installing Haiku under VMware

Forum thread started by Tolingo on Sun, 2009-04-12 18:30

Hi Everybody!

I'm having a bad moment trying to install Haiku under VMware. I follow directions in http://www.haiku-os.org/documents/user/installation but when start the virtual machine I get an error message:

Cannot check for the existence of an old redo log for disk "d:\VM\Haiku\haiku.vmdk". Failed to configure disk ide0:0. The virtual machine cannot be powered with an unconfigured virtual disk.

I have tried both in Windows and Linux as well as vmware version 1 and 2. I've also tried to rename haiku-alpha.vmdk to haiku.vmdk but no success.
Sure I'm doing something wrong but don't know what. Any tip would be appreciated.

Thank you very much for your help in advance.

Tolingo

Can't build Haiku under BeOS

Forum thread started by haiqu on Mon, 2009-03-30 06:25

The version of Jam available on this website at http://www.haiku-os.org/documents/dev/haiku_development_getting_started is not capable of building Haiku under BeOS. Reported error is:

Archive actions too long (max 20480)!

I have tried incrementally building the files, but the main compilation is still to big for the limits of this version of Jam. Linux versions have a different limit, which I believe is 40960, and apparently all the developers are now building under Ubuntu.

I would have reported this bug directly to Trac but I don't have access for the purpose of reporting bugs, despite verifying my subscription.

haiqu

Mostly-Successful VirtualBox Settings

Forum thread started by Michael Crawford on Fri, 2009-03-27 13:14

I found that the March 26th Haiku Pre-Alpha worked on the first try in VirtualBox. On the Haiku development list, Niels Reedijk asked me to post details about my configuration. Maybe I just got lucky by stumbling on the right settings.

First you need to make a VirtualBox compatible disk image. To do that, download one of the raw Haiku images and unzip it.

I used the pre-Alpha r29739 build from March 26th.

Now convert is from the raw format to the VirtualBox VDI format:

$ VBoxManage convertfromraw -format VDI haiku-alpha.image haiku-alpha.vdi

A raw image is a physical copy of an entire disk drive, basically what you'd get if you used the dd command with "bs=512" and copied the entire disk device into a regular file.

I don't know all the details, but basically a VDI also adds some metadata as well as some compression by not having to store sectors that are all zeroes. The VDI images will grow in size as these zero sectors get non-zero data written into them.

Next add your VDI file to the Virtual Media Manager, then create a new virtual machine and attach your VDI file to it.

Here are all of my settings - I didn't see a network interface at all with the PCfast NIC, but with the Intel PRO/1000 MT Desktop the net came right up, configured by DHCP and all, so right away I was able to use the web browser, ssh and cvs.

I'm running Fedora 10 Linux on a Core Quad Xeon - x86_64. I'm not able to get sound working, but otherwise everything else is working really well.

Maybe my particular settings just happened to get lucky...

VirtualBox 2.1.4 - the official Sun version, not the Open Source version.

Base Memory: 268 MB
Video Memory: 32 MB
ACPI: Enabled
IO APIC: Enabled

I think the APIC may be important because it distributes interrupts evenly among multiple CPU cores, and is used on just about all modern PCs as far as I know.

VT-x/AMD-V: Enabled

The VT-x/AMD-V is probably important - that's hardware support for virtualizing guest OSes that don't have explicit support for virtualization. That is, if you have hardware virtualization, you should be able to run any PC operating system.

Only certain models of CPUs have the hardware virtualization support - just recent ones, and even then just higher-end models. I thought that all of Intel's latest chips had VT-x but they don't; you have to check the specs on Intel's website, and similarly for AMD's chips.

VirtualBox can run an OS without hardware virtualization; I'm not real clear what the difference is in the case of VirtualBox - maybe it just runs slower, or not as well.

Windows 2000 runs just fine on my Core Duo MacBook Pro - that's the first-generation Core Duo, not the Core 2 Duo; it doesn't have VT-x.

Xen, by contrast, can't run an OS like Windows at all unless the CPU has hardware virtualization; without it, the guest OS kernel has to be extensively patched - or "paravirtualized" - to enable Xen support.

Nested Paging: Disabled
PAE/NX: Disabled
IDE Controller Type: PIIX4
3D Accelleration: Enabled

(GLTeapot gets hundreds of frames per second!)

Network: Intel Pro/1000 MT Desktop (NAT)

USB: Disabled

I can't get sound to work at all though, and with certain VirtualBox Audio settings, I get a repeatible crash when I restart the media server.

I hope that helps.

Mike

BeBox doesn't see all its memory

Forum thread started by Michael Crawford on Fri, 2009-03-27 05:41

Yeah, I know this isn't about Haiku, but I want to get some code working on BeOS 5 Pro first, and then I'll make sure it works on Haiku.

A friend scored me a 133 MHz Revision 6 BeBox at HSC Electronic Supply in Sunnyvale, California. It booted right up, and came with 32 MB installed as four 8 MB SIMMs in the first four slots.

Today, also at HSC, I bought four 32 MB SIMMs, all of them labeled 8x32. But when I install them all into the last four slots, the BeOS only sees a total of 128 MB. I don't get any complaints about bad memory, and everything seems to work OK - I just don't see all the RAM I should have. There should be 4 * 8 + 4 * 32 = 160 MB of memory.

Note that BeBox memory must be installed in matched pairs, as the SIMMs have a 32-bit data bus, but the CPUs have a 64-bit data bus.

I've tried rearranging the SIMMs, and it seems that whatever sticks are installed in the 4/5 bank are seen as 64 MB, but whatever is installed in the 6/7 bank is only seen as 32 MB. If I take the sticks from 6/7 and put them into 4/5, their size magically doubles to the correct amount.

Is this a problem with my BeBox, or a problem with my memory? If there is a way to make the BeOS see all my memory, I'd appreciate any clues you can give me.

Installing and Dual Booting Haiku and Windows XP

Forum thread started by jrash on Tue, 2009-03-24 16:30

I wanted to dual boot Haiku and XP on my EeePC 1000H, and after a few days of troubleshooting I was able to get it all working. I thought I would post a condensed version of the steps below.

(I recalled these from memory, and tried to double check every step, but let me know if there are any errors.)

1) Get Haiku installed on a USB stick or SD card, the following article worked like a charm.

http://www.haiku-os.org/community/forum/how_to_install_haiku_to_usb_flas...

2) Make sure you have a free partition on your internal drive, and make sure it has been setup before you start installing Haiku, as the option to create a new partition using DriveSetup isn't implemented yet. Boot Haiku from the USB Stick, launch DriveSetup and initialize the partition with BFS. Give the new disk a name other then "Haiku" so it won't conflict with the boot drive, I named mine "Haiku HD".

3) Mount the new drive and copy all of the files from the root of the USB stick to the root of the new drive.

4) Open a terminal window and cd into the /bin directory, run the following command:
makebootable /Haiku\ HD

after that is done run this command:
dd if=/dev/disk/path/to/haiku/partition of=/Haiku\ HD/home/haiku.img bs=512 count=1

5) Now copy the haiku.img file to another FAT formatted USB thumb drive, or if you have network access, email it to yourself. Reboot into Windows.

6) Once back in Windows, Copy the haiku.img file to the root of the c:\ drive. Open the c:\boot.ini file and add the following line to the end of the [operating systems] list:

c:\haiku.img="Haiku"

(Sometimes, even after you enable "show hidden files" you cannot directly access boot.ini, but you can still edit it by using "Control Panel > System > Advanced > Startup and Recovery > System Startup > Edit")

7) Reboot, you should now be prompted to select which OS to boot, select Haiku and sit back and enjoy the Haiku goodness.

What is the Objective in developing Haiku?

Forum thread started by richards31040 on Mon, 2009-03-16 15:52

The FAQ page states that: Haiku aims to be developed under a single unified vision for the whole OS. ....
Frankly the only distinguishing characteristic about the original BeOS was the fine grained and extremely effective task priority controls that ensured that foreground application always had priority.
All the current GUI OSes (Windows, MacOS, Linux etc.. I haven't tried Haiku yet) suffer form the same problem. The user is not the first priority. In all cases applications can bring the OS response to a crawl if the application misbehaves for whatever reason.
To have an OS where the system ALWAYS responded to my key press or mouse click would be a godsend.
Is Haiku that OS?

usb_ecm dhcp timeout

Forum thread started by MatteBlack on Sun, 2009-03-08 02:57

Hi Everybody!

I have installed Haiku on my eee, and it is running really really well. I am trying to get internet access without using an ethernet cable to make the best use of the portability of the machine. I realise that wi-fi and Bluetooth/GPRS are out of the picture at the moment, but I thought I would have some success using my mobile 3G connection over a usb cable. Sure enough Haiku is picking the mobile up as a usb_ecm device quite happily, but syslog shows the DHCP is timing out without successfully setting up the connection. I looked into setting up the connection with static IP addresses, but when I ran some tests on another OS the subnet ranges alter with each setup, so DHCP seems necessary.

Have I missed something in the setup? Is the usb_ecm driver capable of doing what I want, or do I just have to wait until some other connection method becomes available?

Cheers,

Matt

Syndicate content