Opened 10 years ago

Closed 6 years ago

Last modified 2 years ago

#6531 closed bug (invalid)

USB Stick boot error

Reported by: stargater Owned by: mmlr
Priority: normal Milestone: R1
Component: Drivers/USB Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

Hi, i usesd the haiku-nightly-hrev38311-x86gcc4hybrid-anyboot on my USB stick on my Lenovo ThinkPad x100e. I Disable ACPI in the Bootloader why this booting stoped on the Device Symbole. So now i have a Kernel Panik Error, see the screenshot.

My Hardware: Lenovo ThinkPad x100e (Red)

Audio, Video = Conexant 20582 SmartAudio HD

GPU = ATI Radeon HD 3200

IDE = ATA/ATAPI Controller (ATA Channel 0, Standard AHCI 1.0 Seriell ATA COntoller)

IDE Device = WDC WD3200BEVT-08A23T1 ATA Device (300 GB)

CPU = AMD Turion Neo X2 Dual Core Processor L625

RAM = 2 GB

SM Driver = SM bios service


Attachments (1)

bug_haiku.jpg (142.8 KB ) - added by stargater 10 years ago.

Download all attachments as: .zip

Change History (7)

by stargater, 10 years ago

Attachment: bug_haiku.jpg added


comment:1 by korli, 9 years ago

Hello, Could you try again please? You can also type the syslog command and take shots of each screen. Maybe only the ones related to USB should be useful.


comment:2 by scottmc, 9 years ago

please retest this with a fresh build of haiku and let us know if there's any changes.

comment:3 by scottmc, 9 years ago

Blocking: 7665 added

comment:4 by diver, 6 years ago

Component: - GeneralDrivers/USB
Description: modified (diff)
Owner: changed from nobody to mmlr

comment:5 by mmlr, 6 years ago

Resolution: invalid
Status: newclosed

This bug report does not contain any debug info that would make it possible to do anything further. This may or may not be USB related, at least a syslog or a capture of the on-screen debug output would be needed to determine the actual component.

In the original report it was mentioned that ACPI was deliberately disabled in the bootloader. This makes it likely that it is an interrupt routing issue, but again, without actual debug output it's not possible to tell.

comment:6 by waddlesplash, 2 years ago

Blocking: 7665 removed
Note: See TracTickets for help on using tickets.