Wi-Fi and Bluetooth is supported under Linux using mwifiex driver. There is no FreeBSD driver for this chipset. Touch screen and pen requires an IPTS (Intel Precise Touch) driver. Webcam doesn’t even work on Linux to be honest and most things require a patched kernel.
Interesting observation with: " Debugging over serial (or on screen debugger) must be enabled, otherwise a weird timing issue causes the OS to KDL with “get_boot_partitions failed” ".
I have noted that a few users had mentioned in posts having encountered issues with finding/getting the boot partition on other systems. Maybe these issues are all related. Maybe enabling the debugger is a workable way to reach the desktop for the time being.
Also, I have not yet encountered a notebook for which enabling fail safe graphics mode was not needed to reach the desktop stage.
Probably why my laptop failed last night (Dell m6700)(ATi FireGL Mobile)
I’ll have to try the image in safe mode tonight.
I’m excited to see the progress over the last few years!
Update as I can’t reply to this thread for some reason:
Tested 32 & x64 builds last night on my laptop (Dell m6700 - i5, 16Gb, SSD, FireGL)
Both builds behaved the same and there was no apparent difference between a USB2 and USB3 boot stick.
Normal boot from USB: reached rocket stage and booted to a black screen - wifi light on the status strip was on solid.
Shift boot from USB: reached rocket stage and booted to a black screen - wifi light on the status strip was flashing constantly.
For comparison Nightly falls over with “Panic: Did not find any boot partitions!” but that might just have been trying to boot off a USB3 disk.
Given there’s no KDB firing off in the RC candidate images and no boot to desktop, whats the best way to get some debugging info so I can raise a bug ticket?
This is the one thing that have been keeping me from running Haiku on my laptop! Will install as soon as I have time again… With its fast boot and shut-down time Haiku/BeOS had been my default OS for any quick work on a laptop in the past (before EFI). Having to run it in Virtual Machine missed the strong point of using Haiku for me (speed).
It means you don’t have to use legacy BIOS emulation which not all EFIs even implement… the wifi in my laptop actually works when booted from EFI and doesn’t when booted with the Legacy CSM enabled.
The point of EFI itself was to have a modern codebase for developing system firmware… BIOS of old is literally a bunch of unmaintainable binary blobs. While to the end user it isn’t that big a deal unless your computer suports coreboot… it still means it boots faster than a BIOS could and potentially can have more and better features.
Newbie to Haiku here. I have a question: How do I update this to the final build? Will it be seamless?
I remember being able to just manually install over the top nightly images before. I’m sure that remains possible, but can this update to Final within the OS? Maybe automatically? What about future releases?
Thanks, and sorry if this is the wrong place to post.
There is and has been for a long time, please read the user manual. @un_spacyar seems to have this configured properly.
It looks like the beta1 repos never got updated; the buildbot hasn’t been doing some builds automatically and we’ve had to kick it ourselves. I just did that; so hopefully -66+ will appear within an hour or so in the repos.
Thanks - both for your work, as well as for the correction.
I guess I was thrown off by:
That goes to show I should run more instances of Haiku
@un_spacyar:
I’m quite eager to find out as well whether Haiku will boot successfully with UEFI-only firmware. I’ve only got one piece of hardware, and it has no (functional) legacy mode.
Gpd win running EFI USB. Note that it loaded the VESA driver dispite being an intel chipset, and the device uses a tablet screen which you have to set to rotated otherwise it’s sideways, don’t know how to fix that on Haiku:
Wifi doesn’t work out of the box its Broadcom 4356 will try to build my own image with preinstalled wifi firmware and see how that goes.
touchscreen doesn’t work.
Mouse stick works as it emulates a USB mouse or an XBox or Joystick controller selectable by the switch in the middle of the device.
Keyboard works fine.
Didnt’ test sound.
With its fast boot and shut-down time Haiku/BeOS had been my default OS for any quick work on a laptop in the past (before EFI). Having to run it in Virtual Machine missed the strong point of using Haiku for me (speed).
But I have a new problem network don’t work, and USB3 too 