Re: [coreboot] [RFH] Native AMD fam10-15 support
On Sat, Jul 14, 2018 at 1:46 AM, taii...@gmx.com wrote: > Another regression I have noticed is that my 4th SATA hard drive doesn't > appear in linux for some reason, although it does appear in grub...ideas? > > Also kyosti what logs and tests would you like? For now I have > re-flashed my old 4.6 coreboot but I will flash master again soon for you. > > Output of following after having done S3 resume would be of my interest: `cbmem -c (or -1)` `cbmem -t` and `dmesg`. Better have those collected for normal boot path as well. Also it's worth having low_memory_corruption_check=1 and low_memory_corruption_check_size=512k as kernel parameters when checking S3, we have had regressions there for both Intel and AMD, and cases where initial implementation was just wrong (AGESA). Kyösti -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] ACPI Errors on Lenovo X201i
Hi Patrick,
I built with the current origin/master, so the Nehalem fix
https://review.coreboot.org/#/c/coreboot/+/26287/ is already included. I
see "ACPI:* H8" and have the following mentions of HBDC inside the
dsdt.dsl:
External (HBDC, IntObj)
and
Method (GBDC, 0, NotSerialized)
{
If (HBDC)
{
Local0 = One
If (BTEB)
{
Local0 |= 0x02
}
Local0 |= 0x04
Return (Local0)
}
Else
{
Return (Zero)
}
}
Method (SBDC, 1, NotSerialized)
{
If (HBDC)
{
Local0 = ((Arg0 & 0x02) >> One)
BTEB = Local0
}
}
Hope that helps.
Cheers,
Matthias
On 13/07/18 23:41, Patrick Rudolph wrote:
> Hi Matthias,
> It looks like the Ssdt generator on x201/nehalem doesn't work as expected.
> It was broken and has been fixed in commit
> https://review.coreboot.org/#/c/coreboot/+/26287/
> Do you see "ACPI:* H8" in coreboot console log ?
> Do you see any HBDC method in disassembled ACPI ?
> Regards Patrick
>
> Am 13. Juli 2018 22:46:12 MESZ schrieb Matthias Gazzari :
>> Hello,
>>
>> commit f1114d891865e70ae1f2ba58844fec11d055ae3a (ec/lenovo/h8/acpi: Add
>> BDC interface) introduces the following ACPI errors on the Lenovo
>> X201i:
>>
>> ACPI BIOS Error (bug): Could not resolve [\_SB.EC.HKEY], AE_NOT_FOUND
>> (20180313/dswload2-160)
>> ACPI Error: AE_NOT_FOUND, During name lookup/catalog
>> (20180313/psobject-221)
>> ACPI Error: Ignore error and continue table load
>> (20180313/psobject-604)
>> ACPI Error: Skipping Scope block (20180313/psloop-532)
>>
>> and
>>
>> ACPI BIOS Error (bug): Could not resolve
>> [\_SB.PCI0.LPCB.EC.HKEY.GBDC.HBDC], AE_NOT_FOUND (20180313/psargs-330)
>> ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC.HKEY.GBDC,
>> AE_NOT_FOUND (20180313/psparse-516)
>>
>> Do you have any idea on how to fix these issues?
>>
>> Cheers,
>> Matthias
>>
>> --
>> 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
Re: [coreboot] ACPI Errors on Lenovo X201i
Hi Matthias, It looks like the Ssdt generator on x201/nehalem doesn't work as expected. It was broken and has been fixed in commit https://review.coreboot.org/#/c/coreboot/+/26287/ Do you see "ACPI:* H8" in coreboot console log ? Do you see any HBDC method in disassembled ACPI ? Regards Patrick Am 13. Juli 2018 22:46:12 MESZ schrieb Matthias Gazzari : >Hello, > >commit f1114d891865e70ae1f2ba58844fec11d055ae3a (ec/lenovo/h8/acpi: Add >BDC interface) introduces the following ACPI errors on the Lenovo >X201i: > >ACPI BIOS Error (bug): Could not resolve [\_SB.EC.HKEY], AE_NOT_FOUND >(20180313/dswload2-160) >ACPI Error: AE_NOT_FOUND, During name lookup/catalog >(20180313/psobject-221) >ACPI Error: Ignore error and continue table load >(20180313/psobject-604) >ACPI Error: Skipping Scope block (20180313/psloop-532) > >and > >ACPI BIOS Error (bug): Could not resolve >[\_SB.PCI0.LPCB.EC.HKEY.GBDC.HBDC], AE_NOT_FOUND (20180313/psargs-330) >ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC.HKEY.GBDC, >AE_NOT_FOUND (20180313/psparse-516) > >Do you have any idea on how to fix these issues? > >Cheers, >Matthias > >-- >coreboot mailing list: coreboot@coreboot.org >https://mail.coreboot.org/mailman/listinfo/coreboot -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
[coreboot] ACPI Errors on Lenovo X201i
Hello, commit f1114d891865e70ae1f2ba58844fec11d055ae3a (ec/lenovo/h8/acpi: Add BDC interface) introduces the following ACPI errors on the Lenovo X201i: ACPI BIOS Error (bug): Could not resolve [\_SB.EC.HKEY], AE_NOT_FOUND (20180313/dswload2-160) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180313/psobject-221) ACPI Error: Ignore error and continue table load (20180313/psobject-604) ACPI Error: Skipping Scope block (20180313/psloop-532) and ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.EC.HKEY.GBDC.HBDC], AE_NOT_FOUND (20180313/psargs-330) ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC.HKEY.GBDC, AE_NOT_FOUND (20180313/psparse-516) Do you have any idea on how to fix these issues? Cheers, Matthias -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFH] Native AMD fam10-15 support
Hi guys! I have just tested my KGPE-D16's suspend a few times with the latest master and it works fine - takes around a minute to get back to my linux terminal. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFH] Native AMD fam10-15 support
I will provide logs soon! what do you want exactly? One apparent regression I have noticed is that "sensors" reports CPU power usage at idle is now steady at 101W vs the usual 50W (which used to be 40 before a kernel update) while I am not sure if it is accurate as the cpu temp doesn't reach high levels expected for such wattage it does have one bad effect in that Turbo 2 no longer works...and even before this update with my v4.6 to get Turbo 1 on all cores as AMD advertises I must use "tpc -psmax 1"[1] which brings up the sensors reported TDP to 125W whereas normally it wouldn't work due to maxing out at 115W and 3.35ghz rather than T1 3.5ghz the TDP determining when the CPU enters full turbo 1. I use Turbo 2 to obtain better performance on non-multithreaded games so this is disappointing but I will investigate further. [1] turionpowercontrol, an overclocking software -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
