I am on a Thinkpad X230. I mean in the computer bios, boot setup, I have a choice of using UEFI or legacy. When I tried playing with UEFI boot following this “UEFI Booting Haiku | Haiku Project”, my intel wifi chip was not correctly recognized anymore. When booting in legacy, I have no problem.
If you still have the LiveCD, you can try to verify if it boots in UEFI or in legacy mode.
Basically check what says Screen app; it should be different. In case of UEFI, it will mention framebuffer.
Once you’re certain that your LiveCD boots in legacy mode, you can reasonably think that it could work booting from a disk. The easiest way would be to install bootmanager so you take the hand before Grub does. Though you shouldn’t try that if your partitions are made using GPT partition scheme because you may overwrite some infos at beginning of the disk.
This script is not needed unless you use hardware built in the 1990s. I don’t know why people insist on trying to run it.
If I remember correctly, this is normal, the OpenBSD drivers don’t have an explicit “rescan” command but they always scan for networks in the background.
Not if there is a driver for the videocard. So that isn’t a reliable way to check for this.
It’s hard to guess more about what went wrong from the info here. I think you can open a bugreport as said in the first reply, and you can include the syslog (/var/log/syslog) from both the working livecd case, and the non-working install. We can analyze them and hopefully understand the difference.
With Haiku gaining in popularity, less users will have a technical background. Perhaps, this information is important enough to figure in AboutSystem? It would be easier to retrieve than checking the syslog.
Just create an account, if you haven’t already, then log in and chose 'New Ticket".
The reason why we are giving the link to this page is that there are useful informations in ‘Using the tracker’ section. At first, default Trac theme is a bit puzzling, indeed. Once you know that things in red are links, it goes better.
I don’t see the point, the user isn’t who has to fix this but the developer. and we want the syslog. Maybe we can make this easier to access (maybe a system log application) or easier to open a bug report (maybe allow logins via third party providers too?)
But in the end this info is not relevant to end users.