Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
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
[coreboot] KGPE-D16/KCMA-D8 "PIKE" LSI SAS 2308 addon cards are going for $22 on fleabay
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. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
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. 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. Hope that helps, Nico -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
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
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, taii...@gmx.com taii...@gmx.com wrote:
>
> > Oops sorry forgot I also need "sudo xl dmesg" from dom0!
> >
> > 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 mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?
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, taii...@gmx.com wrote: > Oops sorry forgot I also need "sudo xl dmesg" from dom0! > > - > > coreboot mailing list: coreboot@coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot Xen 4.8.4-6.fc25 (XEN) Xen version 4.8.4 (user@) (gcc (GCC) 6.4.1 20170727 (Red Hat 6.4.1-1)) debug=n Wed Oct 31 02:30:27 UTC 2018 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB 2.02~beta3 (XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M iommu=on ucode=scan smt=off (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009fc00 (usable) (XEN) 0009fc00 - 000a (reserved) (XEN) 000f - 0010 (reserved) (XEN) 0010 - bfd89000 (usable) (XEN) bfd89000 - d000 (reserved) (XEN) f870 - f8704000 (reserved) (XEN) feb0 - feb01000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fed0 - fed01000 (reserved) (XEN) fed4 - fed45000 (reserved) (XEN) 0001 - 00084000 (usable) (XEN) ACPI: RSDP 000F6250, 0024 (r2 COREv4) (XEN) ACPI: XSDT BFD990E0, 0074 (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: FACP BFD9B930, 00F4 (r3 COREv4 COREBOOT0 CORE0) (XEN) ACPI: DSDT BFD99280, 26A7 (r2 COREv4 COREBOOT1 INTL 20180810) (XEN) ACPI: FACS BFD99240, 0040 (XEN) ACPI: SSDT BFD9BA30, 1AD2 (r2 COREv4 COREBOOT 2A CORE 2A) (XEN) ACPI: MCFG BFD9D510, 003C (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: APIC BFD9D550, 00DE (r2 COREv4 COREBOOT0 CORE0) (XEN) ACPI: SRAT BFD9D630, 01A8 (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: SLIT BFD9D7D8, 0030 (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: SRAT BFD9D810, 01A8 (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: SLIT BFD9D9B8, 0030 (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: IVRS BFD9D9F0, 00BC (r1 COREv4 COREBOOT0 CORE0) (XEN) ACPI: HPET BFD9DAB0, 0038 (r1 COREv4 COREBOOT0 CORE0) (XEN) System RAM: 32765MB (33551520kB) (XEN) SRAT: Node 1 has no memory. BIOS Bug or mis-configured hardware? (XEN) Domain heap initialised DMA width 32 bits (XEN) IOAPIC[0]: apic_id 32, version 33, address 0xfec0, GSI 0-23 (XEN) IOAPIC[1]: apic_id 33, version 33, address 0xf000, GSI 24-55 (XEN) Enabling APIC mode: Phys. Using 2 I/O APICs (XEN) xstate: size: 0x3c0 and states: 0x4007 (XEN) Speculative mitigation facilities: (XEN) Hardware features: IBPB (XEN) Compiled-in support: INDIRECT_THUNK (XEN) Xen settings: BTI-Thunk LFENCE, SPEC_CTRL: No, Other: IBPB (XEN) Support for VMs: PV: RSB, HVM: RSB (XEN) XPTI (64-bit PV only): Dom0 disabled, DomU disabled (XEN) PV L1TF shadowing: Dom0 disabled, DomU disabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2800.036 MHz processor. (XEN) Initing memory sharing. (XEN) AMD-Vi: SP5100 erratum 28 detected, disabling IOMMU. (XEN) If possible, disable SATA Combined mode in BIOS or contact your vendor for BIOS update. (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 32 KiB. (XEN) HVM: ASIDs enabled. (XEN) SVM: Supported advanced features: (XEN) - Nested Page Tables (NPT) (XEN) - Last Branch Record (LBR) Virtualisation (XEN) - Next-RIP Saved on #VMEXIT (XEN) - VMCB Clean Bits (XEN) - DecodeAssists (XEN) - Pause-Intercept Filter (XEN) - TSC Rate MSR (XEN) HVM: SVM enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) spurious 8259A interrupt: IRQ7. (XEN) CPU1: No irq handler for vector e7 (IRQ -2147483648) (XEN)
Re: [coreboot] riscv: how to running coreboot on HiFive Unleashed?
Hi again, On Tue, Nov 27, 2018 at 12:20:53PM +0800, 王翔 wrote: > > coreboot-4.8-2282-gc88828daeb Mon Nov 26 09:56:26 UTC 2018 bootblock > > starting... > > Boot mode: 15 > > Couldn't load romstage. I just tried the same version (coreboot-4.8-2282-gc88828daeb), and it worked, both with a 1 MiB coreboot image and a 32 MiB coreboot image: coreboot-4.8-2282-gc88828daeb Mon Nov 26 09:56:26 UTC 2018 bootblock starting... Boot mode: 15 CBFS: 'Master Header Locator' located CBFS at [20100:200) CBFS: Locating 'fallback/romstage' CBFS: Found @ offset 80 size 2dca CBMEM:ot-4.8-2282-gc88828daeb Mon Nov 26 09:56:26 UTC 2018 romstage starting... IMD: root @ 00027000 254 entries. IMD: root @ 00027fffec00 62 entries. CBFS: 'Master Header Locator' located CBFS at [20100:200) CBFS: Locating 'fallback/ramstage' CBFS: Found @ offset 2ec0 size 532f coreboot-4.8-2282-gc88828daeb Mon Nov 26 09:56:26 UTC 2018 ramstage starting... BS: BS_PRE_DEVICE times (us): entry 0 run 0 exit 1 BS: BS_DEV_INIT_CHIPS times (us): entry 1 run 0 exit 0 Enumerating buses... CPU_CLUSTER: 0 enabled scan_bus: scanning of bus Root Device took 2050 usecs done BS: BS_DEV_ENUMERATE times (us): entry 1 run 9289 exit 1 Allocating resources... Reading resources... CPU_CLUSTER: 0 missing read_resources Done reading resources. Setting resources... Done setting resources. Done allocating resources. BS: BS_DEV_RESOURCES times (us): entry 0 run 16149 exit 0 Enabling resources... done. BS: BS_DEV_ENABLE times (us): entry 0 run 2605 exit 0 Initializing devices... Root Device init ... Root Device init finished in 1910 usecs Devices initialized BS: BS_DEV_INIT times (us): entry 0 run 9464 exit 0 Finalize devices... Devices finalized BS: BS_POST_DEVICE times (us): entry 0 run 3473 exit 0 BS: BS_OS_RESUME_CHECK times (us): entry 0 run 1 exit 0 Writing coreboot table at 0x27ffdc000 0. 8000-80011fff: RAMSTAGE 1. 80012000-8003: RAM 2. 8004-80044fff: RAMSTAGE 3. 80045000-00027ffdbfff: RAM 4. 00027ffdc000-00027fff: CONFIGURATION TABLES Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8de2 Bad address:00027ffdc0f4 Stored ra: 8d36 Stored sp: 80040ec8 CBFS: 'Master Header Locator' located CBFS at [20100:200) Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8d6a Bad address:00027ffdc10c Stored ra: 8d66 Stored sp: 80040ec8 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8d6e Bad address:00027ffdc114 Stored ra: 8d66 Stored sp: 80040ec8 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8d74 Bad address:00027ffdc11c Stored ra: 8d66 Stored sp: 80040ec8 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8d7e Bad address:00027ffdc0fc Stored ra: 8d66 Stored sp: 80040ec8 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8d82 Bad address:00027ffdc104 Stored ra: 8d66 Stored sp: 80040ec8 FMAP: Found "FLASH" version 1.1 at 2. FMAP: base = 0 size = 200 #areas = 4 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 8d8e Bad address:00027ffdc104 Stored ra: 8d8a Stored sp: 80040ec8 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 80001c68 Bad address:00027ffdc124 Stored ra: 80001c66 Stored sp: 80040e58 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 80001c72 Bad address:00027ffdc12c Stored ra: 80001c72 Stored sp: 80040e58 Exception: Store address misaligned Previous mode: machine Bad instruction pc: 80001c68 Bad address:00027ffdc13c Stored ra: 80001c66 Stored sp: 80040e58 Exception: Store address misaligned Previous mode:
