Opened 5 years ago

Closed 18 months ago

#15347 closed bug (invalid)

PANIC: did not find boot partitions

Reported by: latom Owned by: mmlr
Priority: normal Milestone: Unscheduled
Component: Drivers/USB Version:
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64

Description

Using a thumb drive to try to boot to a ~2008 Lenovo ThinkPad R500.

Issue is attached. the image attached is from me using the newest version, hrev53458. I was originally trying the haiku-r1beta1-x86_64-anyboot and also got the PANIC! error message.

Attachments (3)

haiku.jpg (276.0 KB ) - added by latom 5 years ago.
Picture of the error while booting. Using a Corsair 8 GB thumb drive to boot, this is from the hrev53458 revision.
syslog.jpg (477.1 KB ) - added by latom 5 years ago.
system log 09 15 2019
grep.jpg (440.1 KB ) - added by latom 5 years ago.

Download all attachments as: .zip

Change History (14)

by latom, 5 years ago

Attachment: haiku.jpg added

Picture of the error while booting. Using a Corsair 8 GB thumb drive to boot, this is from the hrev53458 revision.

comment:1 by latom, 5 years ago

Also in case it's pertinent, I'm using balenaEtcher to write the iso to the thumb drive.

While writing this, I tried to write the iso to a Memorex 1GB thumb drive from eons ago. I am now at the "Welcome to Haiku!" screen, using the haiku-r1beta1-x86_64-anyboot image, even using the same slot as before. I was able to "Boot to Desktop" without issue, connected to my wifi, and am online on that machine!

If you want more information, let me know. Looks like this was something causing an issue with this Corsair thumb drive possibly?

comment:2 by waddlesplash, 5 years ago

Milestone: R1/beta2Unscheduled
Priority: highnormal

Please don't add things to milestones.

Yes, more information is needed. Please run "syslog | tail 30" at the KDL prompt, and take a picture of that.

by latom, 5 years ago

Attachment: syslog.jpg added

system log 09 15 2019

comment:3 by latom, 5 years ago

Seems I posted in the wrong place. Sorry about that!

I attached the results from the syslog.

comment:4 by waddlesplash, 5 years ago

Well, not much of interest in that. Can you get a picture with the output of "syslog | grep usb"?

by latom, 5 years ago

Attachment: grep.jpg added

comment:5 by latom, 5 years ago

Sorry about the delay there, attached the output.

comment:6 by waddlesplash, 5 years ago

Component: - GeneralDrivers/USB
Owner: changed from nobody to mmlr

Seems it didn't even detect the device, which is pretty odd.

comment:7 by latom, 5 years ago

quite odd, considering it booted from it lol

comment:8 by waddlesplash, 5 years ago

The BIOS found it of course in order to start the loader; but this is the BIOS/kernel device handoff here. And it seems the USB drivers can't find anything, so obviously there is some problem, likely on our end.

comment:9 by waddlesplash, 5 years ago

Please retest under a recent nightly.

comment:10 by korli, 2 years ago

Please retest under a recent nightly.

comment:11 by waddlesplash, 18 months ago

Resolution: invalid
Status: newclosed

No reply.

Note: See TracTickets for help on using tickets.