Opened 17 years ago

Closed 14 years ago

#1567 closed bug (fixed)

Haiku doesn't boot on IDE HDD with JMicron 363 controller

Reported by: patrick lafarguette Owned by: marcusoverhagen
Priority: normal Milestone: R1
Component: Drivers/Disk Version: R1/pre-alpha1
Keywords: Cc: j_freeman
Blocked By: Blocking:
Platform: All

Description

Haiku fails to boot on an IDE HDD attached to the JMicron 363 controller of my P5B Deluxe motherboard. The JMB363 is set to AHCI in the BIOS. Haiku goes to KDL with "PANIC: did not find any boot partitions!".

Attachments (3)

haiku-debug.txt (105.5 KB ) - added by patrick lafarguette 17 years ago.
Serial debug
haiku-r22594-ahci.txt (95.5 KB ) - added by patrick lafarguette 17 years ago.
Serial debug of revision 22594 with backtrace. JMB363 in BIOS set to AHCI
haiku-r22594-ide.txt (85.8 KB ) - added by patrick lafarguette 17 years ago.
Serial debug of revision 22594 with backtrace. JMB363 in BIOS set to IDE

Download all attachments as: .zip

Change History (10)

by patrick lafarguette, 17 years ago

Attachment: haiku-debug.txt added

Serial debug

comment:1 by plfiorini, 17 years ago

It's like my bug -> http://dev.haiku-os.org/ticket/1544 Can you try hrev22527 and check if it works now?

comment:2 by patrick lafarguette, 17 years ago

I tested hrev22528 to make the serial debug attached.

comment:3 by umccullough, 17 years ago

Don't forget to include a backtrace from kdl in the serial log :)

comment:4 by marcusoverhagen, 17 years ago

Owner: changed from axeld to marcusoverhagen

by patrick lafarguette, 17 years ago

Attachment: haiku-r22594-ahci.txt added

Serial debug of revision 22594 with backtrace. JMB363 in BIOS set to AHCI

by patrick lafarguette, 17 years ago

Attachment: haiku-r22594-ide.txt added

Serial debug of revision 22594 with backtrace. JMB363 in BIOS set to IDE

comment:5 by j_freeman, 16 years ago

Cc: j_freeman added

comment:6 by scottmc, 14 years ago

Can you try this again with a fresher build of Haiku?

comment:7 by scottmc, 14 years ago

Resolution: fixed
Status: newclosed

This one has probably been fixed. If anyone has the same hardware as the original ticket and can recheck this let us know. Closing it for now as "probably fixed".

Note: See TracTickets for help on using tickets.