Opened 12 years ago

Closed 12 years ago

#1544 closed bug (fixed)

Haiku doesn't detect boot partition on real hardware

Reported by: plfiorini Owned by: axeld
Priority: normal Milestone: R1
Component: System Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

I built Haiku rev22448 (compiled on Linux 32bit with gcc 2.95) and tried to run it on real hardware, it boots and shows the Haiku logo but suddenly it goes in KDL with a message like this:

PANI: didn't find boot partition

I generated the images with

jam haiku-vmware-image.

Both haiku.image and haiku.vmdk works (tested with qemu-kvm and VMware Server on openSUSE 10.3 32bit).

Made the /dev/sda5 partition of type BeOS (tried with 100MB and even up to 500MB), then tried to dd the image:

dd if=generated/haiku.image of=/dev/sda5 jam run ":<build>makebootable" /dev/sda5

If I mount /dev/sda5 with the (readonly) BFS file system on Linux I see the Haiku folders and files so it seems that the dd went ok.

Grub is configured like this:

title Haiku

rootnoverify (hd0,1) chainloader (hd0,4)+1

My computer is a AMD 64 x2 with 2GB RAM. Here's my hardware specs: 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a2) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 03:08.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1)

Unfortunately I don't have any serial port so I can't send the serial debug output.

Change History (3)

comment:1 by marcusoverhagen, 12 years ago

try:

rootnoverify (hd0,4) chainloader +1

comment:2 by plfiorini, 12 years ago

I tried now with hrev22527 and it boots. It wasn't a grub configuration problem because I tried your suggestion and it's the same. Maybe the recent partition changes made it working for me? Anyway now I have a completely different problem: frequency out of range, I'll open an issue.

comment:3 by bonefish, 12 years ago

Resolution: fixed
Status: newclosed

I haven't changed anything related in the disk device manager in the meantime, so I suppose, an AHCI related changed must have fixed. Anyway, closing the ticket.

Note: See TracTickets for help on using tickets.