I’m trying to install Haiku on an old HP dv9643eo laptop (dv9500 series). It has an AMD Turion TL-58 CPU and an NVIDIA GeForce 8400M GPU.
The Live USB works flawlessly — everything boots up and runs smoothly (wifi doesnt work, but i have USB wifi stick which works just fine). However, after installing Haiku to the internal hard drive, the system hangs during boot. Specifically, it stops at the fourth icon (the disk with a leaf), which I understand indicates a problem with disk access or file system initialization.
Here’s what I’ve tried so far:
Verified that the installation completes without errors, tried many times…
Tried Intel/uuid partitions
Booted from USB again to confirm hardware compatibility
Checked BIOS settings (legacy mode, SATA settings, etc.)
Tried boot options like noapic, noacpi, etc…
Any ideas what might be causing this? Could it be related to the video driver, disk controller, or something else? Is there a way to enable verbose boot logging or use safe mode options from the bootloader?
That’s difficult to diagnose without more information.
Please go into the boot options again,go to “Select debug options” and check both “Enable on screen debug output” and “Disable on screen paging” there.
That displays debug output while booting.
You can make a photo when it’s stuck.
Beware that only enabling on screen output without also disabling paging causes a boot error here.
It shows timeout errors when trying to read data from your hard disk.
Maybe your hard disk is defective,or it might be a driver issue.
With error messages now available,I leave further help to the experts.
I changed different HDD from another old laptop, but same problem exist… system was always stuck to fourth icon. Chatgpt gave an advice to check disable_ide_dma in boot parameters and holy sh*t that worked. Only problem now is that I have to check that setting every time when I want to use Haiku. Chatgpt gave some advices to edit some kernel files but those didn’t work…
Was that file /boot/home/config/settings/kernel/drivers/kernel? To get it, you need to access the disk, which needs the driver loaded, so I’m not sure it could work. But then I don’t know the booting process, there was a change some years ago so that the driver also checked that file.
If you are daring enough, you could build your own after changing the default false in ATAChannel.cpp.
