[coreboot] How can My linux kernel detect gpio or pinctrl on denverton platform ?
Hi, Linux kernel- 4.14. confing debug gpio and pinctrl-denverton, pinctrl-intel. Coreboot-4.10 using denverton and harcuvar. However, linux kernel not dectect gpio and pinctrl. Thanks. Jason ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Activity for implementing Intel Security Advisories
Hi, I am trying to understand what is the activity corresponding to the fixes suggested by Intel security advisories relating to the processor/controller flaws. I took a glance at commit history and did grep "CVE" but there is nothing there. Once the advisories are released by Intel, on average, what is the timeline to get them implemented on a general note. I understand coreboot is an open community project, but while working on one feature of coreboot, I would want to be sure that some of my friend in the community is taking of security issues. Regards, Naveen ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Extended IvyBridge CPU configuration
Hi, Lars. Update: I flashed the original Lenovo BIOS v2.81 (with keyboard EC mod) and the issues seem to be gone. Do you have any freezes/crashes while running latest coreboot (from master) without the HT patch? ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: [RFT] Linux fails to detect devices on AGESA board with `nosmp`
Sergej Ivanov: > I can reproduce this bug on Biostar AM1ML. I think this bug is ACPI > related, if i add 'nosmp acpi=off' Ubuntu boots fine. > > чт, 16 янв. 2020 г., 15:23 Paul Menzel : >> It’d be great, if you could test this on your coreboot boards, and report >> back. Adding `nosmp` to the Linux kernel command line, for example, by >> pressing e in the GRUB menu (and then Ctrl + x or F10 to boot) should be >> all >> that is needed. Booting Debian 9 from USB stick on Lenovo G505s with nosmp results in it being unable to find the root file system device and getting dumped into BusyBox. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: [RFT] Linux fails to detect devices on AGESA board with `nosmp`
I can reproduce this bug on Biostar AM1ML. I think this bug is ACPI related, if i add 'nosmp acpi=off' Ubuntu boots fine. чт, 16 янв. 2020 г., 15:23 Paul Menzel : > Dear coreboot folks, > > > My coreboot test S-ATA hard disk had `nosmp` on the Linux command line > configured so that Linux boots on the Lenovo T60. Now, testing this on the > AGESA board ASRock E350M1, Linux failed to detect the disk (/dev/sda), and > was unable to boot (USB and AHCI devices got error -22). Removing `nosmp` > from the command line made it boot. Using GRUB or SeaBIOS as payload didn’t > make a difference, and the old coreboot image I had (before switching to > C environment bootblock) *does* have the *same* problem, so the bug is > there longer. It’s reproducible with Linux 4.16.x and Linux 5.4.x. > > It’s not reproducible on the Lenovo T60 (other way around), and QEMU i440fx > and Q35. > > It’d be great, if you could test this on your coreboot boards, and report > back. Adding `nosmp` to the Linux kernel command line, for example, by > pressing e in the GRUB menu (and then Ctrl + x or F10 to boot) should be > all > that is needed. > > > Kind regards, > > Paul > > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] [RFT] Linux fails to detect devices on AGESA board with `nosmp`
Dear coreboot folks, My coreboot test S-ATA hard disk had `nosmp` on the Linux command line configured so that Linux boots on the Lenovo T60. Now, testing this on the AGESA board ASRock E350M1, Linux failed to detect the disk (/dev/sda), and was unable to boot (USB and AHCI devices got error -22). Removing `nosmp` from the command line made it boot. Using GRUB or SeaBIOS as payload didn’t make a difference, and the old coreboot image I had (before switching to C environment bootblock) *does* have the *same* problem, so the bug is there longer. It’s reproducible with Linux 4.16.x and Linux 5.4.x. It’s not reproducible on the Lenovo T60 (other way around), and QEMU i440fx and Q35. It’d be great, if you could test this on your coreboot boards, and report back. Adding `nosmp` to the Linux kernel command line, for example, by pressing e in the GRUB menu (and then Ctrl + x or F10 to boot) should be all that is needed. Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
