Re: [coreboot] SATA init on FSP 2.0 for Skylake

[Naresh G. Solanki]

Hi,

Looking at

coreboot-4.7-51-g2ca4ca3f21-dirty Thu Jan 18 22:05:03 UTC 2018
romstage starting...
pm1_sts:  pm1_en:  pm1_cnt: 
gpe0_sts[0]:  gpe0_en[0]: 
gpe0_sts[1]:  gpe0_en[1]: 
gpe0_sts[2]:  gpe0_en[2]: 
gpe0_sts[3]:  gpe0_en[3]: 

It seems to me that PM base is not setup properly.(this should be fixed first)


Also before you use SATA, make sure FspSUpd for sata is set to be
enabled. Also respective sata port is enabled.

Above that, also check in fit tool whether right setting is done for
flex io for sata port.


On Sun, Apr 1, 2018, 6:43 PM Zheng Bao  wrote:

> I met the same problem. I use the FSP1.1 and the 0:17h:0 disappears after
> raminit.
> It seems that the FSP disable the SATA.
>
> The SATA device can be disabled if SCFD is set. But it can not re-enable.
>
> SATA Controller Function Disable (SCFD): BIOS program this bit to 1 to
> disable
> the SATA Controller function. When 0, SATA Controller function is enabled.
> When
> disable, SATA Host Controller will not claimed the register access
> targeting its
> Configuration Space. In IOSF primary Fabric Decode scheme, it's expected
> BIOS also
> program the corresponding bit used by the Fabric Decoder accordingly hence
> both
> SATA SIP and Fabric Decoder are in sync, and BIOS need to program this bit
> before
> programming the one in Fabric Decoder. Once this bit is set, BIOS isnot
> able to revert
> it back to Function Enable until next round of platform reset.
>
> Zheng
>
> --
> *From:* coreboot  on behalf of roman
> perepelitsin 
> *Sent:* Wednesday, March 28, 2018 2:51 PM
> *To:* coreboot@coreboot.org
> *Subject:* [coreboot] SATA init on FSP 2.0 for Skylake
>
> Hi!
> I got a little problem with SATA controller in H110 Skylake PCH (desktop).
> SATA device geographical address - 0:17h:0 on PCI, and it enabled via
> devicetree.cb. This params correctly send in FspSiliconInit. After this
> coreboot run PCI bus scan. And my SATA device return 0x on PCI read
> config cycles. I search in Intel datasheet for specific SATA disable pin or
> something else, but there is no methods that can make SATA inactive. Maybe
> somebody advice about it?
>
>
>
> --
> regards,
> Perepelitsin Roman
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] Problems with NVidia on Lenovo ThinkPad T430

[Tobias Dausend]

Hello everybody!

I have problems with getting coreboot running on a Lenovo ThinkPad T430.
Better to say: Running with the integrated second graphics adapter NVS
5400M. The Intel HD 4000 is working fine and from the wiki I know that
NVidia Optimus is not supported for now. So what to do exactly getting
the graphics adapter running? Even only NVidia only would be great. Both
adapters are not needed on GNU-Linux for my usecase. I have two VGA-ROMs
extracted and compiled this using the concurrent stable-version 4.7. Is
this wrong? Some help and hints would be appreciated.

Best regards,
Tobias.

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Server systems shipped with coreboot

[Sam Kuper]

On 23/03/2018, Thierry Laurion  wrote:
> If ... ME is disabled with its modules erased, could
> the maker pursue the seller for having made those modifications?

Interesting question. ThinkPenguin seems to be willing to take that
risk, but hedges it by voiding the warranty:

"Backdoors in modern computing devices are unfortunately a certainty
today and while we can't be sure of a fix here it is possible to
partially disable one component believed to be a problem. This option
does have side-effects and will void any return." [1]

(AFAICT, that laptop has the ME "disabled" if the buyer wishes, but it
does not ship with Coreboot or Libreboot.)

[1] https://www.thinkpenguin.com/gnu-linux/penguin-z-gnulinux-laptop

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot