Hi, I began to play with this OS not long ago (last time I was using BeOS R4 long time ago) And I would like te know the state of x86_64.
I have installed gcc2-hybrid on my main system and it run fine (unlike on my laptop but it’s another thing), I got to blacklist fw_raw module that was making the sound system crash because of the firewire, that’s all fine, I don’t use fw anyway.
The problem I have actually is a memory problem.
Here are my spec :
CPU : AMD FX-8120 @ 4Ghz
RAM : 16GB DDR3
VIDEO : Radeon 7970 3GB
I think that I have that issue where the video card memory go in the way, because I can’t even allocate like, 1GB to java because “I don’t have enough memory”. Some site say that I have a limit of 768MB for each programs (4GB - 256MB of random stuff from the board - 3GB for the vid).
The solution would be to switch to x86_64. So I downloaded the src, compiled it, put the anyboot image in my phone and told it to emulate a R/W usb key.
I got the splash screen and the system rebooted without any of the small icon lit… On the second boot I got to like 3-4 icon and I got a small white console on top talking about no root device. So I dd-ed it on a usb key just in case my phone was acting stupid and tried again… could not get past the first icon, no debug mode seam to work as it does not seam to reach logging capability before rebooting.
Do the x86_64 have the same USB support than the X86 one? I’m guessing it’s the problem, like he is not able to load himself). And when I was able to reach the 4e icon and got the white terminal, I was not able to type anything in it.
The other question would be, do I have a way, with the X86 version, to know how much memory a program can access for himself?
Try a Haiku built image to see if there is anything wrong with your setup:
http://download.haiku-os.org/nightly-images/x86_64/
[quote=richienyhus]Try a Haiku built image to see if there is anything wrong with your setup:
http://download.haiku-os.org/nightly-images/x86_64/[/quote]
Same problem exactly. Reboot before the first start-up icon lit.
Same build version but x86_gcc2 boot fine.
EDIT : Booting a douzen time, I’m able to go past the first icon. after that, one time out of two it crash at the rocket (the last) icon, before or after the video card initialization (White flash). I was able to install it and I have the same issue booting from the HDD.
Is the Be file system solid enough (if it need about 5-10 crash during the boot process to reach the desktop)? Once it’s booted it look as stable as the x86_gcc2.
Most of the drivers (including USB) are available for x86_64. Exceptions are drivers for very old video cards (Voodoo and the like), which we didn’t bother making 64-bit safe yet.
The main difference between x86 and x86_64 is that the latter currently has less applications available. This will be solved when we automate the package repository management, however.
As for memory constraints, in 32-bit Haiku an application can only allocate about 2GB. This is because the 32-bit address space can have at most 4GB, and we reserve half of it for kernel things. The hardware mapping of your video card to RAM is not relevant, Haiku, even the 32 bit version, is able to use PAE and address physical memory using 64-bit, the 32 bit limit is applied only per application.
Well, x86_64 is not useable (for me).
Crash totally when I try to play a youtube or when I do ./configure.
Going to stay with x86_gcc2 for a while
Edit : After some archaeology dig, I managed to find a old laptop with a serial port, a null modem cable and a serial port header. I will try to get some log from it and report them.