So how well performed Haiku on multi cores system? I currently assigned just two cores for my Haiku on VirtualBox. My real machine has 8 cores.
I don’t know enought to give you a proper answer, but I can say that according to the activity monitor both cores on my cpu are active, and often one is working hard while the other is doing much less.
Haiku lacks video acceleration and a modern browser. Otter is most close thing we got. Haiku has great potential to be a Web Kiosk, but only if we have decent graphic support and a modern web browser, it’s very far, though.
Does someone know about gaming status on Haiku? Could someday we have Haiku as a gaming platform? Oh, I think it’s my own wet dream.
So you are dual core like me? I want to know what someone with more cores experience. Perhaps 4 cores or above.
Seems to run nicely on a Dell T3400 with a 6 core Xeon W3690, 24GB RAM and a GForce7300GT
Depends. Web+ uses Webkit (used by Otter Browser and Safari) which is still supported and modern.
Haiku runs most games that are not too graphics intensive or don’t require 2D/3D graphic hardware acceleration for decent performance. For games, see: Gaming on Haiku
Haiku can handle a lot of threads, cores, and RAM…
I just installed Haiku on a USB-disk and booted on my AMD Ryzen 2700X with Radeon X590. Seems to work just fine, even OpenGL. Haiku detects 16 cores (this is a 8core/16thread CPU) and all 16GiB RAM.
So far I havent done any benchmarks or so, but at least all hardware seems to work fine.
Beta2/RC2 works for my on my System76 Oryx Pro, Wi-Fi included. Sounds works with headphones only. The only thing is that I changed the repo to be r1beta2 for the package manager, but pkgman list-repos shows HaikuPorts master in the identifier. Not sure if that matters or not.
~> pkgman list-repos
Haiku
base-url: https://eu.hpkg.haiku-os.org/haiku/r1beta2/x86_64/current
identifier: https://hpkg.haiku-os.org/haiku/r1beta2/x86_64/current
priority: 1
HaikuPorts
base-url: https://eu.hpkg.haiku-os.org/haikuports/r1beta2/x86_64/current
identifier: https://hpkg.haiku-os.org/haikuports/master/x86_64/current
priority: 1
That is for now expected, yes.
I had been planning on dropping in a compatible WiFi card in a Thinkpad X140e this weekend anyway, and installing Haiku on bare metal.
This build worked for me. No issues seen.
@donn: Exactly. I’m having the same problem right now. “The Installer cannot upgrade an existing installation.” Nobody said it should. Why not provide an option “Wipe existing partition and just proceed to install”? Where is that “guide to upgrade on the Haiku homepage” announced by the error message? And how I am supposed to access SoftwareUpdate from Beta 1 when it has been deactivated for Beta1? What is the “R1/beta2 update channel”, and how do I get into it? (Also, when I booted from USB to desktop, the CPU was absolutely flooded and the system stuck with no workload yet - until I disconnected the Internet. What was happening there?)
We noticed pretty late that this feature was broken and made a rather minimal change to Installer to avoid broken installations. We will rework this more cleanly for beta 3.
The “guide to update” is not published yet because beta2 is not yet released. For now you can review it here: https://github.com/haiku/website/pull/376/files
Thanks. (Uh, and what feature was that? The Internet?) And why should it be the Installer’s business at all what’s on the partition I tell it to use for the install? “This partition is not empty.” So what? It will be formated anyway. And if the “guide to update” is unpublished as yet, why do you refer to it in the error message? I just looked at the draft version in the link, and the first step is “Get the latest updates” - how? SoftwareUpdater won’t work from Beta 1 anymore. As I said. I was hoping to install Beta 2 to get access to HaikuDepot and the Updater again. So, I effectively can neither install nor upgrade to that Beta 2 release candidate now. Must admit, I’m a little bit disappointed here.
Currently that’s not the case, Installer never formats the partition. The idea is that you could use it to update an existing system. I personally wouldn’t allow that, but apparently others think it’s useful.
As for the “guide to update”, as I said, it will be published when beta2 is released. You are testing a release candidate of a beta release (another thing I think is rather strange, soon we will have alpha versions of release candidates of beta of release candidates of version 1 or whatever, this makes no sense).
The software updater will work if you follow the instructions in this guide, I hope, at least. If it doesn’t, indeed the guide should be fixed to have the correct instructions (that’s the point of having a guide thre).
In any case, yes, the process isn’t perfect here, that’s one of the things we are working on during the beta phase. It is, after all, the first time that it’s possible to update an existing Haiku install from one release to another. Of course there are rough edges, things not going as smoothly as we had expected, and so on. The goal here is to experiment with this, catch as much as we can of these problems, and set up a plan so that the update from beta 2 to beta 3 works better.
1 Like
Why not just make the Installer ignore what’s on the partition I tell it to use? I did it in Fedora Linux a few weeks ago - upgrade from F31 to F32 wouldn’t work, so I just made a fresh install from DVD-R, overwriting an existing one. The Fedora Installer merely asked: “Not enough free space on hard disk. Reclaim space?”, and when I typed “y”, it just wiped the disk and proceeded. As intended.
How much did you pay for the operating system?
How much are most of the developers paid?
The answer is nothing in both cases. Please adjust your expectations accordingly, and be prepared to expend a little effort yourself.
As it happens, this release candidate works extremely well, all things considered, and is defintiely worth the small amount of time it will take you to install it. I, personally, am absolutely delighted with it.
@Sebrof: So, something does not cost any money isn’t worth anything and can’t be expected to work, if I get your argument correctly? But let’s not have that discussion right now. I love Haiku - it has the most intuitive GUI I’ve ever seen, tons of customisation options, and I’d be ready to make it my everyday OS if it were not for the stability issues (approx. 1 crash per session currently, I just can’t trust it with my bread job. I hope Beta2 will run more stable). And it’s a beautiful thing. It’s, however, not a little experimental thing for a few afficionados, but aimed at the general public, a full-fledged OS with a large software repository and constant updates and maintenance. We’re not talking about TempleOS here, Haiku is in size as well as in scope equivalent to a Linux distro. Therefore, an upgrade should come with a procedure intelligible for the general public, and the requisite instructions be readily available at the time of release (by whatever name you call it, alpha, beta, pre-alpha, candidate - if you put it on the Web to download, it’s a release). Of course I’m investing the time necessary, and gladly so, but I would have liked a clear procedure “How to upgrade from Beta1 to this release candidate version” (without having to refer to a draft document under discussion somewhere on GitHub that nobody except the developers knows about) - or just an Installer option “Wipe disk and proceed to install”.
Actually, it’s a release candidate.
It’s good that you appreciate the many good points of Haiku, but we all need to appreciate the work of the developers too, and treat them with respect and good manners. They do a great job with very limited resources.
On my system the beta is working well, and the only problem I have had involves a website known (to me at least) to be difficult. It’s netweather.tv and it has never worked well with either Net+ or Otter for some reason.
Anyway, good luck.
I meant Web+ of course, not Net+.
To help clarify: The instructions for updating from Beta1 to Beta2 will likely be on the website in time for the final release of Beta2.