Uh? It should never be possible to trigger a kernel panic. The Installer should just kindly tell the user that it can’t see any hard disk. Which is fine, because you can install from one USB drive to another, or to an SD card, or to an SCSI drive.
So, please take a screenshot of the KDL and submit a bugreport.
Could there be value in inviting someone to do a magazine review of Beta1 just before it is official (but not publish it yet), so that when they find something accidental like an off-by-one or a “it’s a shame the beta 1 had this little tiny bug”, then that can be fixed before the real beta 1 is released?
Heard the news of an unofficial beta build (for real this time) from R1 Beta 1 Testing Image - Pre-RC! Awesome – I look forward to showing this on my blog soon as I can!
Pretty much adjust your branch in the Haiku repo url from ‘master’ to ‘r1beta1’ and do a full sync. Technically you’ll be downgrading to the beta, but you’ll get the ‘stabilization fixes’ in it. (aka disabling known broken things, etc)
There isn’t a branch for HaikuPorts, and i’m not 100% we’re going to do one for the r1beta1… I think most people want bleeding edge ports.
Haiku 32-bit hrev52292 doesn’t work on IBM T23 laptop (Intel Pentium III, 1024 Mb RAM): while booting live-CD it say “PANIC: attempting to clone non-user-cloneable kernel area”.
Will R1/beta1 support Intel P-III CPUs?
P.S. I can’t try hrev52295 because it doesn’t fit to CD image (803 Mb is much more than 700Mb).
Yeah, Mac’s are tricky. We do have a UEFI bootloader (which seems to work better in these situations), but it isn’t build as part of the image yet. (nor do we have an automatic installation process if you’re installing to your machine)
@jessicah is working on that, but didn’t make the r1beta1 branch. We still have some hope thought she’ll finish it up before R1 beta1 is released.
Interesting.
Now the r1beta1 rc 1 is out with the hrev52295 and additional there is now the normal hrev52309 out.
Which one is more stable and more mature?
Before I thoughted, that after the r1beta1 rc1, all upcomming versions are r1beta1 rcs until r1beta1 is published.
The other possibility would be, that Haiku would be forked: An stable r1beta1 tree and a tree with additional features, which will not be included in r1beta1.
But the revision number is an upcounting number and hrev52309 is not as r1beta1 rc marked.