The first full builds from the Haiku R1/beta5 branch (currently in the “testing” phase so this is “Test Candidate 0”, not a Release Candidate yet) are available for x86_64 and x86_gcc2h:
If you have time, please test these on whatever hardware you have, in as many configurations as you can, and fill out this survey for each one (and of course, if you run into any bugs that you have not before, file tickets in addition to reporting it in that survey.)
Is the idea simply to make a USB stick and try booting from that and experimenting? Rather than attempting to update our current installs (I’m running a nightly)?
Yes, the idea is to boot a totally from-scratch install and report back (after all, you may have set various configurations or blacklisted files to get things to boot; we want to get feedback from a totally unmodified install.)
If you don’t have any packages blacklisted or extra drivers installed, I guess you can skip that, and just switch your running install to the r1beta5 package repos and then pkgman full-sync.
Just installed the Beta5 Test Candidate. Install went well with no issues noticed on my test machine. WebPositive seems to load websites much faster with the updated haikuwebkit/webkit.
Used HaikuDepot to install beam and the installation went smoothly. The repositiories are no longer showing beta 4 or beta 5.
Updated via command line haikuwebkit-1.9.12 along with libjpegturbo_devel and texinfo. no issues during update.
Did some testing with the x86_64 live image on my desktop computer (AMD Ryzen 5 on a MSI motherboard) and I was honestly surprised by how smooth it runs and how network just worked. I’m going to file some bug reports later, but here’s the quick overview:
audio: not working (motherboard onboard audio was detected but did not work, USB speaker was not detected, bluetooth audio paired but was not shown on media settings output list).
bluetooth: was a bit buggy, but I was able to scan and pair my bluetooth headphone.
network: ethernet and wifi worked. But wifi list is showing way too many networks (a lot of them without any name), and when disabling and re-enabling ethernet, I had to disable and re-enable DHCP to get an IP.
browser: webpositive worked nicely. I was able to check this discussion board, use duckduckgo, download some sample audio files, etc.
monitor: I use an ultrawide monitor and it worked great. Haiku looks beautiful in 3440x1440.
I have a stock thinkpad T510 with 32bit haiku and I updated my repositories to R1Beta5, so far the only issue I’m noticing is the bluetooth app crashing, but that is happening on my 64 bit install as well so I don’t know if its a bug, or at least a new bug.
This looks like a bug indeed, I will have to look into that. Probably I missed updating a configuration file somewhere. The “Release Cookbook” is supposed to specify what changes to make here, perhaps it’s incomplete…
Unsurprisingly, just like previous betas and nightlies, the test image runs nicely on my now 10 year old notebook. Wifi connects, sound plays…
No problems with Teapot or Haiku3D.
HaikuDepot causes a bit of trouble:
it opens on “All packages”
the “Featured packages” tab is empty
on first launch it showed 4000+ packages but I didn’t find “clipdinger” or “quicklaunch”. On second launch they were there.
this is a “HaikuDepot -v trace” output, in case it hints to where the “Featured packages” have gone: https://0x0.st/X4Ml.txt
Web+ downloading has an issue we’ve seen before:
Downloads work for me, but cancelling a download doesn’t stop it. I have to quit Web+ and after some seconds it stops.
Something to do with the curl-backend…? Maybe @PulkoMandy remembers.
One more thing: On first bootup, there used to be a notification of keys being generated, which took some seconds. That’s not happening in the test image. Intentionally?
How long is the testing period? This is essentially a 4-day weekend here in France, but next week I will get back home, test on various machines I have, and also ask my colleagues to try it
For once I will not take credit here: most of the performance gains are thanks to Waddlesplash work on the TCP/IP stack and other areas, and WebKit is only a very small piece of the puzzle
Gee I would really like to understand this one a bit better. I have tried a few things to try to reproduce the problem on virtual and hardware. Do you recall what you might have been doing at the time? Are you able to reproduce the problem at all?
on first launch it showed 4000+ packages but I didn’t find “clipdinger” or “quicklaunch”. On second launch they were there.
This is strange. I can see both packages. When you say “didn’t find” – do you mean using the “search” function in the application or by scrolling in the list in the “all packages” tab?
the “Featured packages” tab is empty
This will be because the R1B5 system is picking up a repository ID of tag:ha.....s/r1beta5/x86_64 but this identifier is not registered in HDS.
Authenticate as an admin users with HDS
Navigate to the list of Repositories
Click on HaikuPorts
Click on haikuports_x86_64 Source
Edit and add the extra identifier
Save
Do the same thing for the haikuports_x86_gcc2 Source.
You can get the correct IDs to use from pkgman list-repos on the R1B5 machine. Note that the URLs listed from that command appear to be incorrect.
