Opened 17 years ago
Closed 17 years ago
#1295 closed bug (fixed)
Did not find any boot partitions :S
Reported by: | meanwhile | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description (last modified by )
Using build 21613 gives KDL on boot:
PANIC: did not find any boot partitions! Welcome to Kernel Debugging Land... Running on CPU 0
Attachments (2)
Change History (12)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
Please add a complete syslog. And you hard disk layout would probably be helpful as well.
comment:3 by , 17 years ago
I'm unfamiliar with syslogs but some info on the Haiku site told me it can be found inside Haiku. If that's correct, I don't know how to reach it since this KDL happened at the very first boot of this build and I can't get further than this bootscreen/KDL combination that shows up.
As for the HD layout setup: here's a screenshot: http://www.xs4all.nl/~rrvvww/screen46.png (This window didn't allow for resizing in width, alas)
comment:4 by , 17 years ago
Well, I actually don't mean the syslog, but the serial debug output, which you would need to capture via a serial-connected computer. I figured you already did that, since you had some KDL lines in the bug description.
comment:5 by , 17 years ago
Yeah, in this case I could actually type in some things; I typed 'db' to get those lines. Is there any other command I should type to get the needed info?
I do have a null-modem and another BeOS machine but unfortunately SerialConnect also gave me an error message of its own:
"parrot: can't open /dev/ports/serial1 (Device/File/Resource busy)"
comment:6 by , 17 years ago
I get the same here; i attached a serial debug output, hrev21617; if you need something more, feel free...
comment:7 by , 17 years ago
Should be fixed in hrev21624. Please verify.
@meanwhile: "db" in KDL does not result in useful output. The most interesting information is usually provided by "sc" (stack crawl).
comment:10 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
(Installing build 20797 minutes earlier on the same hardware went fine)