Opened 10 months ago
Closed 3 months ago
#18792 closed bug (duplicate)
Installer fails to detect a hard drive on laptop
| Reported by: | Redysz | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta5 |
| Component: | Drivers/Disk/AHCI | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | #18536 | Blocking: | |
| Platform: | All |
Description (last modified by )
The installer for R1beta4 detects the hard drive in the laptop without any problem, and I can format it properly so as to install Haiku. The R1Development version (hrev57576-x86_64) does not see the same drive. It is impossible to install the system.
Laptop: Lenovo IdeaPAD 110 (trying to install on real machine). Laptop/Enivronment details in attachments.
My steps:
- Download haiku-r1beta4-x86_64-anyboot.iso
- Make USB-boot with Rufus 4.4 (no options can be modified so I used "standard" ones)
- Boot with this USB stick on Legacy bios mode
- Select install Haiku
- Hard drive visible
~Alternative reality:~
- Download haiku-master-hrev57576-x86_64-anyboot.iso
- Make USB-boot with Rufus 4.4 (no options can be modified so I used "standard" ones)
- Boot with this USB stick on Legacy bios mode
- Select install Haiku
- Hard drive is not visible
I've tried to format hard drive with gparted, make in "unallocated" and others - nothing works.
Attachments (8)
Change History (23)
by , 10 months ago
| Attachment: | installator beta4.jpg added |
|---|
by , 10 months ago
| Attachment: | listdev.txt added |
|---|
Result of listdev command (performed on Haiku R1beta4 - because there hard drive is visible)
by , 10 months ago
| Attachment: | listimage.txt added |
|---|
Result of listimage | grep drivers command (performed on Haiku R1beta4 - because there hard drive is visible)
comment:1 by , 10 months ago
| Description: | modified (diff) |
|---|
comment:2 by , 10 months ago
| Description: | modified (diff) |
|---|
follow-up: 4 comment:3 by , 10 months ago
| Component: | Applications/Installer → Drivers/Disk |
|---|---|
| Keywords: | Hard drive Installer removed |
| Platform: | x86-64 → All |
Can you attach the system log (from /var/log/syslog) for both versions?
comment:4 by , 10 months ago
comment:5 by , 9 months ago
| Component: | Drivers/Disk → Drivers/Disk/AHCI |
|---|
comment:6 by , 9 months ago
AHCI driver seems to be stuck in a loop of:
614 KERN: ahci: Enable: Starting port already running! 615 KERN: ahci: Disable: port 0 error DMA engine still running 616 KERN: ahci: PortReset: port 0 unable to shutdown! 617 KERN: ahci: ResetDevice: port 0 unable to hard reset device
so the device can't be enabled but also can't be disabled. Then it gives up after a few tries.
comment:7 by , 9 months ago
| Keywords: | boot-failure added |
|---|---|
| Milestone: | R1/beta5 → Unscheduled |
| Priority: | critical → normal |
comment:8 by , 9 months ago
| Keywords: | boot-failure removed |
|---|
follow-up: 12 comment:9 by , 9 months ago
Please try booting with ACPI disabled and see what happens (it may just not boot at all, however.)
comment:10 by , 9 months ago
| Milestone: | Unscheduled → R1/beta5 |
|---|
I think we should keep this in he beta5 milestone since it seems to be a regression (worked fine in beta4)
follow-up: 13 comment:11 by , 9 months ago
Looks like it's reading only 0xff values from PCI.
ahci: cap: Interface Speed Support: generation 15 ahci: cap: Number of Ports: 32 (raw 0x1f)
Does the device need a power up?
comment:12 by , 9 months ago
Replying to waddlesplash:
Please try booting with ACPI disabled and see what happens (it may just not boot at all, however.)
Then the hard drive is not visible in both (development and beta4) by the installer.
comment:13 by , 9 months ago
Replying to korli:
Looks like it's reading only 0xff values from PCI.
ahci: cap: Interface Speed Support: generation 15 ahci: cap: Number of Ports: 32 (raw 0x1f)Does the device need a power up?
Is that question for me? Device is a standard hdd. Model: WD5000LPCX-24VHAT0
comment:14 by , 9 months ago
The pictures in #18536 show a similar error from the AHCI driver. From the complete syslog in that ticket and the rather narrow revision range in the other, we should be able to find a solution?
comment:15 by , 3 months ago
| Blocked By: | 18536 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
I looked more closely at the syslogs and I see that #18536 has the same SATA controller. So I'm going to close this as a duplicate of the earlier ticket, they are similar enough that this is very likely the same problem.
Let's continue the dscussion there.
Installator beta4