[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GRUB as coreboot payload with *working* AHCI mode support
From: |
Vladimir 'φ-coder/phcoder' Serbinenko |
Subject: |
Re: GRUB as coreboot payload with *working* AHCI mode support |
Date: |
Sun, 28 Apr 2013 13:25:23 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 |
On 28.04.2013 11:02, Paul Menzel wrote:
> Dear GRUB folks,
>
>
> just for your information, I successfully tested revision 4911
> containing the AHCI support, Vladimir committed yesterday. Big thanks to
> Vladimir! Here is the serial log from running coreboot with the GRUB
> payload on the ASRock E350M1.
>
Nice to hear. Thanks for testing.
> 02.316: <1b>[H<1b>[J<1b>[1;1Hdisk/ahci.c:211: dev: 0:11.0
>
> Here the debug messages start as there is `set debug="ahci"` in
> `grub.cfg` in the memdisk. (Not sure where the strange characters in the
> beginning come from though.)
It's an escape sequence ehich causes screen clear when running vt100
compatible terminal.
> 02.317: disk/ahci.c:267: AHCI is in compat mode. Switching
>
> I have to read about that and figure out, if and where I can configure
> that mode in coreboot. Vladimir, could you please add to the error
> message, to what mode the mode is switched to?
It's not an error, it's perfectly specified part of AHCI startup. It's
GHC.AE
> 10.269:
> 10.269:
> <1b>[m<1b>[4;2H+----------------------------------------------------------------------------+<1b>[5;2H|<1b>[5;79H|<1b>[6;2H|<1b>[6;79H|<1b>[7;2H|<1b>[7;79H|<1b>[8;2H|<1b>[8;79H|<1b>[9;2H|<1b>[9;79H|<1b>[10;2H|<1b>[10;79H|<1b>[11;2H|<1b>[11;79H|<1b>[12;2H|<1b>[12;79H|<1b>[13;2H|<1b>[13;79H|<1b>[14;2H|<1b>[14;79H|<1b>[15;2H|<1b>[15;79H|<1b>[16;2H|<1b>[16;79H|<1b>[17;2H+----------------------------------------------------------------------------+<1b>[m<1b>[18;2H<1b>[m
> 10.269: Use the ^ and v keys to select which entry is
> highlighted.
> 10.269: Press enter to boot the selected OS, `e' to edit the
> commands
> 10.269: before booting or `c' for a command-line.
> […]
>
> So my Western Digital WD20EARS seems to take about ten seconds to start
> up. (Under SeaBIOS it has the same behavior.)
Hm, it's somewhat slow to spinup but sounds credible that some drives
would need so much time.
signature.asc
Description: OpenPGP digital signature