Hi,
I never saw any documentation about those CMOS settings so didn't realize they were available to modify! :-)
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.
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".
If I have no drives installed the system does get to the memtest payload but then hangs after 4 seconds. Could this be related to the minimum memory voltage I set?
I've also noticed ever since I put coreboot on this system a few weeks ago it intermittently hangs half way through the boot process at the following line:
PCI: 00:14.3 a0 <- [0x00f8710000 - 0x00f8710000] size 0x00000001 gran 0x00 mem
Is this indicative of anything?
Kind regards,
Pete
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, December 1, 2018 6:36 PM, Taiidan@gmx.com Taiidan@gmx.com wrote:
On 12/01/2018 11:56 AM, Nico Huber wrote:
Hi Pete, On 01.12.18 17:21, petecb via coreboot wrote:
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.
it's a configuration issue. If you have nvram settings enabled (CONFIG_ USE_OPTION_TABLE), you can enable `sata_ahci_mode` with nvramtool.
Ah so that is why it works for me but not for him, since I always customize my CMOS options :D
No idea why combined mode is the default, it's only useful for OSes from the '90s. It's not about the type of drives (SATA vs PATA) connected but how the SATA controller identifies itself to the OS.
AHCI is faster and better as it supports NCQ, TRIM etc.
Conga-rats petey now you can fix it easy! just enable cmos settings in menuconfig then go to the kgpe-d16 coreboot board directory and change cmos.default, recompile/flash then reset your CMOS - OR if you already have use cmos enabled you can simply change it via the cmos tool with the required iomem=relaxed in the kernel command line.
I would also lower the log/debug level via menuconfig to speed boot times and maybe change some other things in cmos.default like me
I have experimental_memory_speed_boost enabled, my 1394 controller set to disabled and SATA ALPM to enabled.
coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot