coreboot December 2018

coreboot@coreboot.org

52 participants
62 discussions

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by Taiidan＠gmx.com 05 Dec '18

05 Dec '18

Maybe try installing a SATA drive to test things? Worse case maybe disabling the SATA controller would fix it? as you say you don't need it. I hope timothy pearson sees this and replies as he would know what to do to fix it.

1 0

Configuration for Apollo Lake FSP (Github/MR5)
by Alexey Borovikov 04 Dec '18

04 Dec '18

Hi, Nico! Is there an external superio on your board? At the moment I am trying to solve the problem of initializing the external superio chip for the SOC Baytrail processor, but so far without success.

2 2

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by Nico Huber 04 Dec '18

04 Dec '18

On 03.12.18 19:50, petecb via coreboot wrote: > I have attached a text file with an overview of all the options I have > selected with the nconfig utility, on the off-chance someone spots > something I have done wrong. Best way to find out is to disable USE_OPTION_TABLE again and leave everything else as is. If that doesn't result in a reliable image, the option table is not to blame. Actually, we try to discourage developers from adding options that may result in a failure, but you never know. You can use `make savedefconfig` to save the options that differ from their default. It writes into a file `defconfig`. That's probably better than your "screenshots" (unless the D16 requires non-default settings to work). Regarding the cmos.default, IMHO, somebody should go through all the options (from `interleave_chip_selects` to `maximum_p_state_limit` in cmos.layout), check where they are used in the code (e.g. `git grep \"interleave_chip_selects\"`) and document their defaults in absence of the option table (i.e. when get_option() returns a failure or doesn't do anything at all). Then we'd be able to discuss sane defaults. Though, we'd need to take all boards using the respective code paths into account. Nico

2 1

FOSDEM Hardware Enablement Devroom
by Paul Kocialkowski 04 Dec '18

04 Dec '18

A Hardware Enablement devroom will be taking place at FOSDEM this year, on Sunday 10 December 2017. This newly-created devroom is the result of 3 proposals that were merged together. It is co-organized by several individuals. The devroom covers all aspects related to hardware enablement and support with free software, including aspects related to boot software, firmwares, drivers and userspace tools and adaptation. Proposals for talks related to these topics are welcome and can be submitted until Sunday 26 November 2017 via the pentabarf interface. Short talks are encouraged over longer ones in order to cover a wide range of topics. The announcement for the devroom, that contains all the useful information, was published at: https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html Cheers and see you at FOSDEM! -- Paul Kocialkowski, developer of free digital technology and hardware support Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/

3 3

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by Nico Huber 03 Dec '18

03 Dec '18

Hi Pete, On 02.12.18 23:13, petecb via coreboot wrote: > As the default SATA setting already appeared correct, I modified the 3 > additional settings that Taiidan had already indicated worked > (memory_speed_boost, 1394 controller and SATA ALPM) so in my mind I was > only adjusting one additional setting, the memory voltage. I thought > this was fairly sensible as my RAM is definitely 1.35V. did you have CONFIG_USE_OPTION_TABLE before? If not you potentially have changed all settings. The defaults in the cmos.default file don't have to be the same defaults that are hardcoded in the code and the file only takes effect if CONFIG_USE_OPTION_TABLE is set. As I looked at the SATA code, I know the AHCI setting is one that definitely differs. That's a thing that could easily be improved. Check all the options and their defaults in the source code and agree on one single reasonable default. > > I would value confirmation that it is safe to run the Crucial > CT16G3ERSLD4160B RAM I have in this board at 1.5v. Yes, all DDR3L should be 1.5V compatible. I'm fairly confused that such a board has a 1.35V option, though. Nico

3 2

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by Peter Stuge 02 Dec '18

02 Dec '18

petecb via coreboot wrote: > Thank you for all those details. I've now compiled a version with > the default CMOS settings apart from the following changes > > Minimum memory voltage = 1.35v > experimental_memory_speed_boost enabled > 1394 controller disabled > SATA ALPM enabled. Please do not ever change more than a single thing at a time. You waste not only your own time, but also that of those who help you. > Unfortunately, this results in the Qubes installation on the SSD crashing Try changing only the SATA setting before moving on to anything else. //Peter

2 1

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by Taiidan＠gmx.com 02 Dec '18

02 Dec '18

On 12/02/2018 10:43 AM, Angel Pons wrote: > Hello, > > On Sun, Dec 2, 2018 at 4:07 PM petecb via coreboot > <coreboot(a)coreboot.org> wrote: >> Thank you for all those details. I've now compiled a version with the default CMOS settings apart from the following changes >> >> Minimum memory voltage = 1.35v >> experimental_memory_speed_boost enabled >> 1394 controller disabled >> SATA ALPM enabled. > But what about the other one that you need? SATA AHCI mode? Of course I also wouldn't start modding stuff before you get things working to start though. > Okay. > >> Unfortunately, this results in the Qubes installation on the SSD crashing before it gets to the password prompt and the Qubes installer crashing shortly after booting. They both produce a similar error message that has been too quick to catch so far but mentions "PCI" and "IRQ". > > One of the options you selected has the word "experimental" on its > name. I would suspect it may cause issues. Ah well the good thing is that it is easy to remedy if you have added the nvramcui to your selected payload (it is a cmdline cmos settings utility) My money is on the memory voltage though since the experimental option works for me (it is an optimization related to 63xx CPUs not actually RAM itself) > > Regards, > > Angel Pons >

1 0

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by Angel Pons 02 Dec '18

02 Dec '18

Hello, On Sun, Dec 2, 2018 at 4:07 PM petecb via coreboot <coreboot(a)coreboot.org> wrote: > Thank you for all those details. I've now compiled a version with the default CMOS settings apart from the following changes > > Minimum memory voltage = 1.35v > experimental_memory_speed_boost enabled > 1394 controller disabled > SATA ALPM enabled. Okay. > Unfortunately, this results in the Qubes installation on the SSD crashing before it gets to the password prompt and the Qubes installer crashing shortly after booting. They both produce a similar error message that has been too quick to catch so far but mentions "PCI" and "IRQ". One of the options you selected has the word "experimental" on its name. I would suspect it may cause issues. Regards, Angel Pons

1 0

KGPE-D16/KCMA-D8 "PIKE" LSI SAS 2308 addon cards are going for $22 on fleabay
by Taiidan＠gmx.com 01 Dec '18

01 Dec '18

Thought y'all should know. This is what installs in the weird reversed pci-e x4 slot at the bottom of the motherboard. Notes: * It will obstruct the usage of the PCI slot and the use of a dual slot card in the bottom most PCI-e slot (the white one not the blue "graphics" slots) * KCMA-D8 has a SR5670 instead of the better with more PCI-e lanes SR5690 on the D16 according to the manual using a PIKE will shut off one of your PCI-e slots (lame!) although this is still a better deal than buying a more expensive regular LSI card. * They have working FLR so they can be assigned to VM's easily. If anyone knows how to get SR-IOV working on LSI controllers me know - the 2008/2308 controllers were the first ones that according to the advertising literature were meant to have the ability to assign drives to virtual functions and then those virtual functions to VM's meaning you could have some drives attached to one VM and some to another and so on - with the ability to have a SAS expander one could have native pass through physical drives for every VM this way.

1 0

Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
by petecb 01 Dec '18

01 Dec '18

In addition to the previous info, I have found this code in sata.c, located at src/southbridge/amd/sb700 : /* Below is CIM InitSataLateFar */ if (sata_ahci_mode) { /* Disable combined mode */ byte = pci_read_config8(sm_dev, 0xad); byte &= ~(1 << 3); pci_write_config8(sm_dev, 0xad, byte); } else { /* Enable interrupts from the HBA */ byte = read8(sata_bar5 + 0x4); byte |= 1 << 1; write8((sata_bar5 + 0x4), byte); } I'm wondering if my problem is related to not having any SATA drives installed? (I just have a PCI-E SSD). It may be the case that the logic to disable combined mode is not getting triggered in my scenario, yet it would do if there was a SATA drive present. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, December 1, 2018 3:45 PM, petecb via coreboot <coreboot(a)coreboot.org> wrote: > No worries, please find it attached. > > This output looks a little more helpful as it contains the line: > AMD-Vi: SP5100 erratum 28 detected, disabling IOMMU. > > I've discovered this thread that refers to it: > https://mail.coreboot.org/pipermail/coreboot/2017-November/085440.html > > It appears to be an issue with combined sata mode being enabled. > In this case the fix may be to make an amendment to the coreboot source code to disable combined sata mode and then rebuilding it and flashing it. If this is the best route, is there any guidance you can provide? > > However, I have just seen this post from you that indicates that this error doesn't crop up in Xen 4.10 > https://mail.coreboot.org/pipermail/coreboot/2017-November/085542.html > > Is it straightforward to configure an install of Qubes 4 with Xen 4.10? > > Kind regards, > > Pete > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Friday, November 30, 2018 10:09 PM, Taiidan(a)gmx.com Taiidan(a)gmx.com wrote: > > > Oops sorry forgot I also need "sudo xl dmesg" from dom0! > > > > coreboot mailing list: coreboot(a)coreboot.org > > https://mail.coreboot.org/mailman/listinfo/coreboot > > -- > > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot December 2018