[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SATA disk on cntroller in AHCI mode not found: `disk/ahci.c:225: couldn'
From: |
Paul Menzel |
Subject: |
SATA disk on cntroller in AHCI mode not found: `disk/ahci.c:225: couldn't start CR` |
Date: |
Fri, 05 Apr 2013 12:54:55 +0200 |
Dear GRUB developers,
as reported to the coreboot mailing list already [1][2], using GRUB
(4778) as a payload [3] on the AMD SB800 based ASRock E350M1 [4], the
SATA disk attached to the SATA controller is not found when the
controller is in AHCI mode. Using IDE mode works.
grub> set
?=0
boot_once=true
color_highlight=black/white
color_normal=white/black
debug=ahci,ata
default=1>Debian GNU/Linux, with Linux 3.2.0-4-686-pae
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feature_menuentry_options=y
feature_ntldr=y
feature_platform_search_hint=y
grub_cpu=i386
grub_platform=coreboot
lang=
locale_dir=
menu_color_highlight=white/blue
menu_color_normal=cyan/blue
menuentry_id_option=--id
pager=
prefix=(memdisk)/boot/grub
prev_saved_entry=
root=mduuid/fb7f3dc5d183cab6121231201a2207b9
saved_entry=
secondary_locale_dir=
grub> insmod ahci
disk/ahci.c:291: Requesting AHCI ownership
disk/ahci.c:294: Waiting for BIOS to give up ownership
disk/ahci.c:305: AHCI ownership obtained
disk/ahci.c:311: AHCI is in compat mode. Switching
disk/ahci.c:357: 6 AHCI ports
disk/ahci.c:367: status 0:123
disk/ahci.c:184: found device ahci0 (port 0)
disk/ahci.c:225: couldn't start CR
Increasing to timeout unfortunately does not help [2].
=== modified file 'grub-core/disk/ahci.c'
--- grub-core/disk/ahci.c 2013-03-25 09:32:56 +0000
+++ grub-core/disk/ahci.c 2013-03-31 21:32:18 +0000
@@ -193,7 +193,7 @@
}
dev->hba->ports[dev->port].command &= ~GRUB_AHCI_HBA_PORT_CMD_ST;
- endtime = grub_get_time_ms () + 1000;
+ endtime = grub_get_time_ms () + 10000;
while ((dev->hba->ports[dev->port].command &
GRUB_AHCI_HBA_PORT_CMD_CR))
if (grub_get_time_ms () > endtime)
{
SeaBIOS [5] has no problem initializing the controller and strangely it
seems to work on Intel based hardware too.
I’ll gladly test patches and provide more information.
Thanks,
Paul
[1] http://www.coreboot.org/pipermail/coreboot/2013-March/075583.html
[2] http://www.coreboot.org/pipermail/coreboot/2013-April/075592.html
[3] http://www.coreboot.org/GRUB2
[4] http://www.coreboot.org/ASRock_E350M1
signature.asc
Description: This is a digitally signed message part
- SATA disk on cntroller in AHCI mode not found: `disk/ahci.c:225: couldn't start CR`,
Paul Menzel <=