Haiku R1 alpha3 boot failed on specific netbook hardware

1

Hello there.

I tested haiku-r1alpha3-anyboot copied to an SD-card as explained in the doc “Making a Haiku USB stick” (on Windows):

(1) On my personal netbook, a Lenovo Ideapad S10-2 (with the HDD replaced by a OCZ Vertex 2 SSD).
=> It did not work. After the BIOS has finished I can shortly see “Starting system”, but than immediately after that, without the possibility to press the space bar with any effect, the following error message appears:

*** PANIC ***
mmu_init(): Failed to add physical memory range 0x7f4e20000 - 0x7f5bb0000

Press key to reboot.
I also tested, unfortunately all with the same result, "*** PANIC ***":
   - the SD-card via a USB-card-reader
   - the image copied to an IDE-HDD, booted via USB
   - changing the SATA controller setting from "AHCI" to "compatible"
   - removing the SSD

(2) On another notebook, an HP Compaq 6720s, it booted without a problem with the same boot device, the SD-card.

Any suggestion for a fix, workaround or steps to clarify the matter or bring it further?

2

First, did you tried to enter the boot loader menu (keep pressed the shift key during boot) and enable the safe boot mode?

Second, the quite only reason this panic message could show up is when there is more than MAX_PHYSICAL_ALLOCATED_RANGE (8) physical memory addresses range.
As the physical memory map is given by the BIOS, I wonder if you could not disable some exotic features related to memory in your BIOS setup, which could allow the boot loader to pass this issue.

Another point could be that, maybe, 8 ranges of addresses is too short these days of complex physical memory layout…

3

Thank you for your reply.

No, but now I did, but without any good. The boot load menu does not appear, only the error message without delay.

I did not quite catch this one – call me a noob, especially regarding OS debugging.
Nevertheless, I replaced the 2 GB RAM module with the original 1 GB, but again without any luck (only a different memory range, of course).

Unfortunately not, it is a very basic BIOS. The only interesting option seems to be the one for the SATA controler and USB legacy.

Can you be more explcit about the MAX_PHYSICAL_ALLOCATED_RANGE-problem?

4

I was about to suggest you to file a bug report, but in fact I think this issue is already reported and tracked here:

http://dev.haiku-os.org/ticket/7869

Which also mean that R1Alpha3 wont boot on any machine were BIOS report more than 8 usable physical memory blocks. And that you’ll need to try again with a nightly build instead, when this issue will be fixed.
http://www.haiku-files.org/haiku/development/

Stay tuned.

5

r42717 works. Splendid job. :slight_smile:
Now I will try to get comfortable.