Re: GRUB as coreboot payload with *working* AHCI mode support

[Paul Menzel <paulepanter@users.sourceforge.net>]

[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]

Am Sonntag, den 28.04.2013, 13:25 +0200 schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
> On 28.04.2013 11:02, Paul Menzel wrote:

[…]

> >         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.

Good to know. Thanks. I used `readserial.py` from SeaBIOS [1] which
prints the timing at the beginning. It looks like it ignores such
sequences.

> >         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

Sorry, I meant debug message and not error message.

As mentioned on IRC, I thought I had configured coreboot to set it into
AHCI mode and have to find out, why it does not set this bit.

> >         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.

I only have one comparison setup. On a T60 the laptop drive Hitachi
HTS7210… seems to only take five seconds for spin-up.


Thanks,

Paul


[1] http://review.coreboot.org/gitweb?p=seabios.git;a=blob;f=tools/readserial.py;h=d85392eba67933e85ff58ab1ad53db6dd3759b29;hb=HEAD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]