coreboot August 2017

coreboot@coreboot.org

59 participants
132 discussions

Howto enable AMD Cool'n'Quiet support
by Michael Graichen 15 Aug '17

15 Aug '17

Hey, i tried running coreboot on my old ASUS K8V-X Mainboard. I'm using Coreboot tag/4.6 from git and its SeaBIOS. Booting seems to do fine, it detects the harddrive and a USB stick (Ubuntu MATE). But when i'm booting from the USB stick i get an error message from the kernel: "Make sure that your Bios is up to date and Cool'n'Quiet support is enabled in BIOS setup." I checked the error message in the linux source and found it in: drivers/cpufreq/powernow-k8.c The for-loop there just scans memory C0000 to FFFF0 for a string "AMDK7PNOW!" I checked coreboot.rom-file and my vendor BIOS for that but can't find it. Did I miss to enable something in make menuconfig? Can someone give me a hint how to find the missing blob. Thanks, Micha

1 0

Re: [coreboot] help with Chromebook linux install
by Sean Felipe Wolfe 15 Aug '17

15 Aug '17

Awesome, thanks Matt and great site :) On Tue, Aug 15, 2017 at 9:36 AM, Matt DeVillier <matt.devillier(a)gmail.com> wrote: > Sean, > > you can easily change the firmware boot flags using my Firmware Utility > Script: https://mrchromebox.tech/#fwscript > > you'll want option #4, then select the option for '1s + Legacy Boot > default.' You can optionally remove the Developer Mode splash screen > completely via option 6. > > cheers, > Matt > > On Tue, Aug 15, 2017 at 11:12 AM, Sean Felipe Wolfe <stjohnskid(a)gmail.com> > wrote: > >> Hey everybody, I'm installing Linux Mint on a Samsung Chromebook 11. >> >> I've successfully installed the OS by removing the write-protect screw, >> then running John Lewis's firmware update script. I'm now trying to get rid >> of the startup developer-mode screen to have the system boot right up to >> Mint. That's the one where I press Ctrl-L to get the SeaBios prompt. I >> found this article, >> >> https://johnlewis.ie/how-to-make-the-legacy-seabios-firmware >> -slot-the-default-on-a-haswell-broadwell-based-chromebook/ >> >> But this requires ChromeOS to still be installed and I overwrote it when >> I put in Mint. >> >> How can I remove that initial Google developer mode screen without >> ChromeOS installed? >> >> Thanks in advance, >> >> ps. if this is the wrong mailing list could you make a suggestion for >> another? >> >> Thanks!! >> >> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot >> > >

1 0

Re: [coreboot] help with Chromebook linux install
by Matt DeVillier 15 Aug '17

15 Aug '17

Sean, you can easily change the firmware boot flags using my Firmware Utility Script: https://mrchromebox.tech/#fwscript you'll want option #4, then select the option for '1s + Legacy Boot default.' You can optionally remove the Developer Mode splash screen completely via option 6. cheers, Matt On Tue, Aug 15, 2017 at 11:12 AM, Sean Felipe Wolfe <stjohnskid(a)gmail.com> wrote: > Hey everybody, I'm installing Linux Mint on a Samsung Chromebook 11. > > I've successfully installed the OS by removing the write-protect screw, > then running John Lewis's firmware update script. I'm now trying to get rid > of the startup developer-mode screen to have the system boot right up to > Mint. That's the one where I press Ctrl-L to get the SeaBios prompt. I > found this article, > > https://johnlewis.ie/how-to-make-the-legacy-seabios- > firmware-slot-the-default-on-a-haswell-broadwell-based-chromebook/ > > But this requires ChromeOS to still be installed and I overwrote it when I > put in Mint. > > How can I remove that initial Google developer mode screen without > ChromeOS installed? > > Thanks in advance, > > ps. if this is the wrong mailing list could you make a suggestion for > another? > > Thanks!! > > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot >

1 0

help with Chromebook linux install
by Sean Felipe Wolfe 15 Aug '17

15 Aug '17

Hey everybody, I'm installing Linux Mint on a Samsung Chromebook 11. I've successfully installed the OS by removing the write-protect screw, then running John Lewis's firmware update script. I'm now trying to get rid of the startup developer-mode screen to have the system boot right up to Mint. That's the one where I press Ctrl-L to get the SeaBios prompt. I found this article, https://johnlewis.ie/how-to-make-the-legacy-seabios-firmware-slot-the-defau… But this requires ChromeOS to still be installed and I overwrote it when I put in Mint. How can I remove that initial Google developer mode screen without ChromeOS installed? Thanks in advance, ps. if this is the wrong mailing list could you make a suggestion for another? Thanks!!

1 0

ASUS KGPE-D16 Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand 15 Aug '17

15 Aug '17

The ASUS KGPE-D16 fails verification for branch master as of commit 506bc8e2ff34565e5c50940d0ef3addb93b07faa The following tests failed: BOOT_FAILURE Commits since last successful test: 506bc8e device/smbus: Drop some never used boilerplate 6bfcf66 stoneyridge: Fix CPU ASL _PR table 029dfff i2c: Move to Linux like `struct i2c_msg` 673e014 libpayload: add *SECS_PER_SEC macros to stddef.h ea38367 Makefile.inc: lint: Update to run lint-extended scripts <16 commits skipped> b58366a soc/intel/cannonlake: Add missing _PCH_DEV definitions 285f9f2 payloads/external/tianocore: Add and apply patches for tianocore 6c9c196 copy & update test routines from what-jenkins-does e624e27 Make: Move testing into a subdirectory fea9216 Documentation: Add binary extraction documentation See attached log for details This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineering.com> regarding any issues stemming from this notification

1 0

Question about finalization of SMM
by Persmule 15 Aug '17

15 Aug '17

Hi all, When using chipsec ( https://github.com/chipsec/chipsec ) to analyse possible vulnerabilities inside coreboot systems, I noticed that on several intel-based systems running coreboot,(e.g. https://review.coreboot.org/cgit/board-status.git/tree/lenovo/x230/4.6-938-… ) several registers on the pci-e root complex (host bridge) is not locked while locked on the same system running oem firmware. Digging into the source code, I found a function defined inside ${COREBOOT_DIR}/src/northbridge/intel/{nehalem, sandybridge, haswell}/finalize.c to lock these registers and finalize smm, but this function will only be called if #SMI APM_CNT gets triggered with a certain parameter. ( The handler of #SMI APM_CNT is usually defined as function "southbridge_smi_apmc" inside ${COREBOOT_DIR}/src/${VENDOR}/${MAINBOARD}/smihandler.c or ${COREBOOT_DIR}/src/southbridge/intel/${CHIPSET}/smihandler.c, and the lockdown function will be called with parameter register APM_CNT == APM_CNT_FINALIZE.) That these registers are left unlocked indicates that smm is left unfinalized, and #SMI APM_CNT is never triggered with APM_CNT == APM_CNT_FINALIZE during boot. I would like to ask, that when does the smm is expected to be finalized, and which component of the system (e.g. coreboot, payload, or os kernel) is responsible for that? Thanks. Persmule

1 0

Re: [coreboot] Why I don't like links in commit messages and comments ...
by ron minnich 15 Aug '17

15 Aug '17

I don't agree. You don't need links as long as you have google or its competitors or successors. But that's just me, no need to continue this, I just thought it was funny that the 1994 had 0 working links :-)

1 0

Re: [coreboot] Why I don't like links in commit messages and comments ...
by Felipe Sanches 15 Aug '17

15 Aug '17

Other that, the other solution I can think of would involve the creation a coreboot-webreferences git repo (or wiki page, or something else) where people have to make mandatory backup copies of any web-content they reference on commit-messages and any other documentation. That solution is certainly a bit harder to maintain, but much more robust if your goal is to make sure the info will not be lost. There's a catch with copyright law in that case, though... but there could arguably be a defense based on historical preservation purposes similar to the Archive.org project. 2017-08-15 0:51 GMT-03:00 Felipe Sanches <juca(a)members.fsf.org>: > It is not perfect, off course! > But it is their stated mission to do the best for the longevity of the > preserved data and they seem serious enough about that goal. And it is > definitely better than the current state of not backing up web-references > anywhere. > > 2017-08-15 0:40 GMT-03:00 ron minnich <rminnich(a)gmail.com>: > >> Why are you assuming that the internet archive will be here in 20 years >> :-) >> >> On Mon, Aug 14, 2017 at 8:32 PM Felipe Sanches <juca(a)members.fsf.org> >> wrote: >> >>> There's a rather simple solution to that: stipulate that any link in >>> commit messages must be first saved on the Internet Archive's Wayback >>> Machine. That is as easy as pasting the original URL into a text field in >>> this page and clicking the "Save Page Now" button: >>> >>> https://archive.org/web/ >>> >>> 2017-08-14 21:44 GMT-03:00 ron minnich <rminnich(a)gmail.com>: >>> >>>> This is an interesting headline: >>>> >>>> "I Bought a Book About the Internet From 1994 and None of the Links >>>> Worked" >>>> >>>> What's interesting? That's only 5 years before linuxbios started. I can >>>> make the totally unwarranted claim that the half life of a link is around >>>> 12 years. I justify this claim with one bogus data point, namely, this >>>> headline :-) >>>> >>>> But still, what's amazing is when I did a check, about 15 years after >>>> linuxbios began, about 25% of the links were in fact dead. So the 12 year >>>> number may not be great, but ... maybe it's not that bad either. >>>> >>>> And now you know why I don't like links in commit messages :-) >>>> >>>> ron >>>> >>>> -- >>>> coreboot mailing list: coreboot(a)coreboot.org >>>> https://mail.coreboot.org/mailman/listinfo/coreboot >>>> >>> >

1 0

Re: [coreboot] Why I don't like links in commit messages and comments ...
by Felipe Sanches 15 Aug '17

15 Aug '17

It is not perfect, off course! But it is their stated mission to do the best for the longevity of the preserved data and they seem serious enough about that goal. And it is definitely better than the current state of not backing up web-references anywhere. 2017-08-15 0:40 GMT-03:00 ron minnich <rminnich(a)gmail.com>: > Why are you assuming that the internet archive will be here in 20 years :-) > > On Mon, Aug 14, 2017 at 8:32 PM Felipe Sanches <juca(a)members.fsf.org> > wrote: > >> There's a rather simple solution to that: stipulate that any link in >> commit messages must be first saved on the Internet Archive's Wayback >> Machine. That is as easy as pasting the original URL into a text field in >> this page and clicking the "Save Page Now" button: >> >> https://archive.org/web/ >> >> 2017-08-14 21:44 GMT-03:00 ron minnich <rminnich(a)gmail.com>: >> >>> This is an interesting headline: >>> >>> "I Bought a Book About the Internet From 1994 and None of the Links >>> Worked" >>> >>> What's interesting? That's only 5 years before linuxbios started. I can >>> make the totally unwarranted claim that the half life of a link is around >>> 12 years. I justify this claim with one bogus data point, namely, this >>> headline :-) >>> >>> But still, what's amazing is when I did a check, about 15 years after >>> linuxbios began, about 25% of the links were in fact dead. So the 12 year >>> number may not be great, but ... maybe it's not that bad either. >>> >>> And now you know why I don't like links in commit messages :-) >>> >>> ron >>> >>> -- >>> coreboot mailing list: coreboot(a)coreboot.org >>> https://mail.coreboot.org/mailman/listinfo/coreboot >>> >>

1 0

Re: [coreboot] Why I don't like links in commit messages and comments ...
by ron minnich 15 Aug '17

15 Aug '17

Why are you assuming that the internet archive will be here in 20 years :-) On Mon, Aug 14, 2017 at 8:32 PM Felipe Sanches <juca(a)members.fsf.org> wrote: > There's a rather simple solution to that: stipulate that any link in > commit messages must be first saved on the Internet Archive's Wayback > Machine. That is as easy as pasting the original URL into a text field in > this page and clicking the "Save Page Now" button: > > https://archive.org/web/ > > 2017-08-14 21:44 GMT-03:00 ron minnich <rminnich(a)gmail.com>: > >> This is an interesting headline: >> >> "I Bought a Book About the Internet From 1994 and None of the Links >> Worked" >> >> What's interesting? That's only 5 years before linuxbios started. I can >> make the totally unwarranted claim that the half life of a link is around >> 12 years. I justify this claim with one bogus data point, namely, this >> headline :-) >> >> But still, what's amazing is when I did a check, about 15 years after >> linuxbios began, about 25% of the links were in fact dead. So the 12 year >> number may not be great, but ... maybe it's not that bad either. >> >> And now you know why I don't like links in commit messages :-) >> >> ron >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot >> >

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot August 2017