#11530 closed bug (invalid)
The boot just hangs after selecting the USB key media with the image anyboot hrev48397 (x86)
Reported by: | LkpPo | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | System/Boot Loader | Version: | R1/Development |
Keywords: | boot-failure | Cc: | saulery@…, pulkomandy@… |
Blocked By: | Blocking: | ||
Platform: | All |
Description
With image anyboot hrev48397 for x86, on AMD Senprom LE-1200 x86_64 (http://www.cpu-world.com/CPUs/K8/AMD-Sempron%2064%20LE-1200%20-%20SDH1200IAA4DE%20%28SDH1200DEBOX%29.html).
After selecting USB key in the Boot Menu, the PC displays the disk table and the IRQ table. Then it displays:
Verifying DMI Pool Data ......... Update Success
Then nothing happens. I tried the usb front and rear. Nothing to do.
I enclose the info on my machine and the dmesg my Debian system.
I noticed the following errors in dmesg early in the startup:
148:[ 0.000000] tsc: Fast TSC calibration failed 233:[ 0.076115] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM 580:[ 1.672021] ata4: softreset failed (device not ready) 582:[ 1.672076] ata3: softreset failed (device not ready) 632:[ 3.408563] sd 6:0:0:0: [sdb] Asking for cache data failed 676:[ 7.711659] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Linux ignores but perhaps not haiku.
Attachments (4)
Change History (13)
by , 10 years ago
Attachment: | cpuinfo.txt added |
---|
by , 10 years ago
by , 10 years ago
by , 10 years ago
comment:1 by , 10 years ago
Platform: | x86 → x86-64 |
---|
comment:2 by , 10 years ago
Platform: | x86-64 → All |
---|
comment:3 by , 10 years ago
Blocking: | 7665 added |
---|
comment:4 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 6 years ago
Keywords: | boot-failure added |
---|
comment:6 by , 6 years ago
Blocking: | 7665 removed |
---|
comment:7 by , 6 years ago
comment:9 by , 5 years ago
Milestone: | R1 |
---|
Remove milestone for tickets with status = closed and resolution != fixed
Please retest with a recent nightly.