On 15/06/18 13:51, Kyösti Mälkki wrote:
> On Fri, Jun 15, 2018 at 2:14 PM, qtux wrote:
>
>>
>>>> Coreboot did work well, but froze sometimes when booting during the
>>>> assigning resources step (more or less exactly after assigning the PCI
>>
On 15/06/18 02:42, Kyösti Mälkki wrote:
> On Thu, Jun 14, 2018 at 4:38 AM, qtux wrote:
>> On 13/06/18 22:12, Kyösti Mälkki wrote:
>> Hi,
>>
>> S3 is __not__ working on my KCMA-D8. The last time I tried, I had to
>> remove the power cord for a couple of
On 13/06/18 22:12, Kyösti Mälkki wrote:
> Hi
>
> Now that we wiped out K8, I'd like to put my eyes on fam10-15 boards.
>
> Couple questions for board owners:
>
> First, about asus/kcma-d8 and asus/kgpe-d16: Do these have working S3
> support? I remember rumours they originally worked at some
On 03/05/18 21:51, qtux wrote:
> I uploaded a status report for the X201 and it contains the smashed
> stack message. Since then I booted several times but was not able to
> reproduce this stack smashing issue. It seems like that this kind of
> error occurs only once after flashing.
> On Wed, May 2, 2018 at 11:09 AM Kyösti Mälkki <kyosti.mal...@gmail.com>
> wrote:
>
>> On Wed, May 2, 2018 at 8:53 PM, Nico Huber <nic...@gmx.de> wrote:
>>> On 02.05.2018 18:37, qtux wrote:
>>>> Thanks for your detailed explanation. So in esse
hese
cases to solve the issue until the next time I tinker with coreboot (in
particular experimenting with me_cleaner seems to cause this issue quite
often).
Cheers,
Matthias
On 02/05/18 00:42, Nico Huber wrote:
> On 02.05.2018 00:03, qtux wrote:
>> ...
>> ACPI Warning: SystemIO
Maybe these are also caused by copy pasting Sandy Bridge code as I found
a reference to PMIO and GPIO with matching addresses in
src/southbridge/intel/bd82x6x/acpi/pch.asl. Do you have any ideas on
this issue?
Cheers,
Matthias
On 01/05/18 19:35, qtux wrote:
> Beware that patch is incompl
On 01/05/18 18:45, Kyösti Mälkki wrote:
> On Mon, Apr 30, 2018 at 6:46 AM, qtux <m...@qtux.eu> wrote:
>> I wrote a patch [0] for the finalize code issue. With that my X201i is
>> working fine on current master besides an regression introduced in commit
>> 7f5efd
I wrote a patch [0] for the finalize code issue. With that my X201i is working
fine on current master besides an regression introduced in commit
7f5efd90e598320791200e03f761309ee04b58a3 [1]. With that regression USB and SD
card is not working anymore and it raises the following errors:
[
Hello,
I found that after updating my Lenovo X201i the commit
d533b16669a3bacb19b2824e6b4bc76a2a18c92a [1] causes a freeze during
boot. Additionally, if INTEL_CHIPSET_LOCKDOWN is disabled (and thus
booting works), resuming from S3 does not work anymore. I found that the
following patch
10 matches
Mail list logo
