Opened 7 years ago

Closed 6 years ago

#9363 closed bug (fixed)

doesn't boot on acer s5-391-73514G25akk

Reported by: cipri Owned by: nobody
Priority: normal Milestone: R1
Component: Drivers Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


I have an acer acer s5-391-73514G25akk and tried to install the nightly hrev45131 (x86_64) , from an external usb-cd-rom. After it starts to read from the cd-rom i land direclty at the fail-save options (without pressing space etc.). There whatever i choose just "rebooting" is possible, and the option "continue booting" is disabled. My harddisk ... are two ssd harddisk in raid 0. This might be the problem?

Change History (11)

comment:1 by cipri, 7 years ago

now i changed in bios from raid to ahci mode, and now it starts to boot, but after the 4th symbol highlights i endup in kernel debug land .... with the following messages:

Thread 14 "main2" running on CPU 0 strack trace for thread 14 "main2" kernel stack: 0xffffffff81c88000 to 0xffffffff81c8c000

<kernel_x86_64> ach_debug_stack_trace + 0x13

<kernel_x86_64> _ZL22stack_trace_trampolinePv()+0x09

<kernel_x86_64> arch_debug_call_with_fault_handler()_+ 0x16

<kernel_x86_64> debug_callwith_fault_handler() + 0x74

<kernel_x86_64> _ZL20kernel_debugger_loopPKcs0_P13va_list_tagi() + 0x22c

<kernel_x86_64> _ZL24_kernel_debugger_internalPKcs0_P13va_list_tagi() + 0x10b

<kernel_x86_64> panic() + 0xc3

<kernel_x86_64> vfs_mount_boot_file_system()+0x2c4

<kernel_x86_64> _ZL5main2Pv() + 0x9c

<kernel_x86_64> _ZL19common_thread_entryPv() + 0x7b

comment:2 by diver, 7 years ago

Platform: Allx86-64

I assume that a regular x86 nightly image boots fine on the same laptop, or does it?

comment:3 by diver, 7 years ago

Owner: changed from nobody to xyzzy
Status: newassigned
Version: R1/alpha4.1R1/Development

comment:4 by cipri, 7 years ago

using the regular haiku nightly (32bit), it fails very similar

arch_debug_stack_trace() + 0x12 stack_trace_trampoline_FPv() + 0x0b arch_debug_call_with_fault_handler() + 0x1b debug_call_with_fault_handler() + 0x5e kernel_debugger_loopFPCcT0Pc1() + 0x21 kernel_debugger_internalFPCcT0Pc1() + 0x53 panic() + 0x36 vfs_mount_boot_file_system() + 0x7f main2_PFv() + 0xae (or 0xad or 0xa0 ... because i can not read my own handwriting) common_thread_entry_FPv() + 0x80

comment:5 by anevilyak, 7 years ago

That trace looks similar to the one you'd get from the "Could not find any boot partitions" panic.

comment:6 by cipri, 7 years ago

Yes, i think i saw that error message too.... but i was thinking it could also continue without a boot partition, because i inserted a usb-key and a sd-disk, and intended to install it on sd-disk, or usb-key, in case writing to ssd didn't work.

comment:7 by anevilyak, 7 years ago

No, in this case "boot partition" is whatever you're booting off to try and install it. If it can't find that, it can't load drivers and bring the rest of the system up (and for that matter, subsequently install it elsewhere), all it has is the subset of drivers that's in the early boot archive and nothing else.

comment:8 by diver, 7 years ago

Owner: changed from xyzzy to nobody
Platform: x86-64All

comment:9 by korli, 6 years ago

Summary: haiku64 doesn't boot on acer s5-391-73514G25akkdoesn't boot on acer s5-391-73514G25akk

comment:10 by cipri, 6 years ago

now my ultrabook boots finally (tested on x86). What I noticed is that the screen resolution was not detected automatically, but I could set it manually. The atheros wifi network adapter is so far also not working (but I created for that a new ticket). So I guess, one can close this ticket.

comment:11 by korli, 6 years ago

Resolution: fixed
Status: assignedclosed

Thanks for the feedback!

Note: See TracTickets for help on using tickets.