November 2015 - coreboot - mail.coreboot.org

Lenovo T410 Coreboot
by A. Veek Dec. 14, 2018

Dec. 14, 2018

2 1

Re: [coreboot] No VGA output on e350m1 after flashing. what to do?
by Reiner Luett Sept. 12, 2017

Sept. 12, 2017

Hi! On 30.06.2013 19:28, Christian Weinz wrote: > Maybe I didn't include the VGA option in the make menuconfig process. > How can I solve this problem? You need to add the VGA Option ROM (VGA BIOS -> Add VGA BIOS image). I've extracted it from the UEFI, but you also could use these: http://www.coreboot.org/index.php?title=ASRock_E350M1&oldid=11114 at the end of the page or you also may be able to use the default AMD fam14 (Persimmon) vbios. You will need to agree to the click through: http://wwwd.amd.com/support/vbioslic.nsf/userverify?openform http://www.coreboot.org/AMD_DB-FT1_PERSIMMON It's a pity, that bios_extract didn't work for now. You could use the AMI Aptio EFI MMTool with wine: http://win-lite.de/benutzer/fernando/BIOS-Tools/AMI_Aptio_EFI_MMTool_v4.50.… You need to extract OntarioEFIVbios with PCI ID 1002,9802 as Option ROM. Regards, Reiner --

5 6

ASUS KCMA-D8 workstation board port offer
by Timothy Pearson Jan. 20, 2017

Jan. 20, 2017

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, After reviewing some of the comments on the ASUS KGPE-D16 being essentially too large of a system and too expensive for many people, and the fact that modern, blob-free systems are not really available in the mid-range arena, Raptor Engineering would like to offer to create a native initalization blob-free port for the ASUS KCMA-D8, which is essentially the KGPE-D16's ATX-compatible "little brother". We would be asking $15,000 for the port, including upstreaming to the master coreboot tree. We already have extensive experience with these Family 10h/15h boards, and would be able to create a port of similar quality to the existing KGPE-D16 source in terms of both code quality and overall functionality. If this is something you might be interested in please let me know. We are able to accept multiple payments from various sources for the same project (within limits), so if this is something your local Linux groups or similar might be interested in we should be able to keep the cost on any one individual or organization to a reasonable level. Thank you for your consideration, - -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) http://www.raptorengineeringinc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJWQROpAAoJEK+E3vEXDOFbR2cH/3FTqGFH+cU/HVrBUPcoKjii h9OC7SGeXdyoLZvob/YayG+g47Yppkg2um4pAC7dmGl/OXtkGh13hlsrQ8BNiYcz g0kQUdNKYh9dmBC3YnlxU6a7psh473TdyuLILrl7/8WgI8DZnRtjy62Oo5k6XAKW jfYb/bGC8I3tArYrgQDmFxz2dOejuTZit56I+mbWNtvbuQov2BDmrPPMLRuEvG3M QHCAo/Pjaajzl4rmtrgu0GHcxHsgAnJcnrcPkFYeSDKt7QxSTNOB6NqhcnYdh1SY RiA5Z/3enuDs+XNhS+6qMeKOcrEuf+Ccs7sGsgq5tWm20JA+bBoByvrXhHqVUxU= =DKfR -----END PGP SIGNATURE-----

7 16

Re: [coreboot] On Intel Boot Guard
by Alexander Couzens April 15, 2016

April 15, 2016

Hi Iru, we aren't still sure which boards use Intel Boot Guard and which doesn't use it. But we expect most board use it, because it's "recommended" by intel - as we dont recommend it. Also there isn't yet a test script for Intel Boot Guard. Can you post a link to that forum post? I would like to look into a x240 flash image. If you have such board it would be nice if you can send me a copy of the flash image via private mail. Cheers, lynxis -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)jabber.ccc.de mobile: +4915123277221

2 2

FOSDEM deadlines now!
by Carl-Daniel Hailfinger Jan. 13, 2016

Jan. 13, 2016

Hi, we obviously want to participate in FOSDEM. https://fosdem.org/2016/news/2015-09-24-call-for-participation/ ACT NOW! Some deadlines already expired. Some can still be managed. Main track talks: Deadline 2015-10-30 (10 days left) One hour of entertainment, huge audience. Anyone up for the challenge? Stands: Deadline 2015-11-13 (24 days left) I can send in the proposal if I'm not going to be alone there. How many tables do we want for our stand/booth(s)? Who is coming? Lightning talks: Deadline 2015-11-27 (38 days left) Short and to the point. Your 15-minute elevator pitch. Can you sell the project? All deadlines are at 23.59 UTC Developer room proposal: Deadline EXPIRED Maybe some developer room will accept talks/demos from us. Regards, Carl-Daniel

3 4

CBFS file format changed but documentation not updated
by Kevin O'Connor Jan. 1, 2016

Jan. 1, 2016

I noticed that commit 0d618afc modified the CBFS file format. (It looks like the "checksum" field was replaced with a new file "attributes" feature.) However, the CBFS documentation in the repository (Documentation/cbfs.txt) was not updated. It would be great if the documentation could be kept in sync with the CBFS implementation. (Or, if that's not feasible, I think it would be preferable to remove Documentation/cbfs.txt .) Having up to date specifications helps other projects (eg, SeaBIOS) keep up with changes. Also, I didn't see any emails for the above change on the mailing list. What is the best way to keep up with notable architectural changes in coreboot? -Kevin

2 1

Porting Libreboot to the C201 Chromebook (veyron_speedy)
by Paul Kocialkowski Dec. 24, 2015

Dec. 24, 2015

Over the past week or so, I've been working to get Libreboot running on the latest ARM Chromebook: the C201, manufactured by Asus (codename veyron_speedy). The laptop is running with a RK3288 SoC and ships with Google's version of Coreboot preinstalled. It should require no proprietary code nor any proprietary firmware load or microcode update to boot, thus it would be a good fit for Libreboot, as a fully free distribution of Coreboot. In addition to that, the device's embedded controller (that handles aspects of power management as well as the keyboard and a few other things) is a microcontroller that is also running free software: the free embedded controller firmware from Google. Aside from that, it has a soldered Wi-Fi/bluetooth BCM4354 chip (cannot be removed) that has a free driver but requires to load a proprietary firmware on the chip. However, it is easy to work around that issue and not use that chip at all, e.g. using an ath9k_htc dongle on one of the two USB ports. The GPU is a Mali T764, on which Luc has been doing some early work to have free software support for it. It is uncertain[0] how long it will take to have an usable free replacement for it, but now that there is that hardware available, free graphics for Mali T GPUs would mean having a recent laptop running fully free software, down to the firmware level, without losing any major hardware feature, something that has hardly ever been achieved yet. Thus, I believe it is of the utmost importance to back Luc up on this, even if big players like ARM are trying hard to make Lima not happen and to make it difficult for Luc to keep going. Another aspect that I still have to look at in-depth is the ability to use hardware video encoding/decoding. The RK3288 has an auxiliary processor for that task, but it is unclear whether it can be used with free software or not, though the first indications that I've gathered are positive. At this point, I've been able to boot up Debian on the device, and the xfce4 interface is quite usable. It even runs big programs like Iceweasel/Firefox and LibreOffice without inconveniences. However, it cannot run desktop environments that depend on GL acceleration, such as gnome-shell, which is a shame since those would be a good fit for it. The CPU is simply too slow for offering a decent experience with software rendering (llvmpipe). Overall, I truly hope this device creates an incentive to free the last remaining parts that can only work with proprietary software to this day. Its potential would be huge, especially since it's a good fit for travellers. With the security model inherited from Chromium OS, this would be one of the safest laptops to be used by journalists or activists. If Tails was to be ported to it, it would become easy to have a secure and anonymous setup. I have successfully fixed and compiled Coreboot and all the necessary bits and pieces for the C201, so I'll be spending the next few days sending patches, discussing how to integrate it to Libreboot and getting the actual work done. I also plan on documenting all my findings (especially things like how to access UART, how to remove the SPI flash's write protect, how to reflash it externally, etc) on my coding blog, for now. Cheers! References: [0]: http://libv.livejournal.com/27461.html -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/

2 1

setting up a bug tracker
by Patrick Georgi Dec. 18, 2015

Dec. 18, 2015

Hey coreboot folks, people were nagging me to set up a bug tracker for the project. Last time we dicussed that, we mostly quibbled over the UI and data model (whether the tracker should feature free form vs. structured data bug entry), and that's a discussion I don't want to participate in, so I'm staying out of the decision which bug tracker it should be. My offer is: Figure out (collectively) what issue tracker is suitable for coreboot, promise you'll help keeping it clean (so it doesn't become a graveyard like our trac instance), and I'll set it up. Only four constraints as far as I'm concerned: 1. It must be somewhat CPU efficient. Funnily that rules out trac. 2. It must be maintained. I have no interest in watching out for XSS issues myself. 3. It must be OSI friendly licensed. Jira and similar "special license for open source projects we like" stuff doesn't count. 4. It must run on Linux (since that's what the server uses) It also shouldn't be too esoteric. I reserve the right to simply give up if installing the tracker involves having to figure out how to set up an S/360 emulator, then build the open source issue tracker using a K compiler that can only be found on Abandonware websites that are written in scripts (as in character sets) that I can't read. Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle

9 16

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Coreboot Test Stand Dec. 1, 2015

Dec. 1, 2015

The ASUS KFSN4-DRE fails verification as of commit bd88fa0ef62339bfc3027423d230a6ffcd1419ae The following tests failed: BOOT_FAILURE Commits since last successful test: bd88fa0 fsp_baytrail: Remove use of BAYTRAIL_SMM Kconfig symbol 4013469 build system: add dependencies for SeaBIOS output 3093038 nb/amd/amdmct/mct_ddr3: Use StopOnError to decrease training time 9586dc7 mainboard/intel: Add Little Plains b4b298c mainboard/asus/kgpe-d16: Limit HT speed to 2.6GHz <7 commits skipped> 551b383 build system: move defconfig creation into a cbfs-files filter 10420cc build system: break overly long lines into logical units c35bd54 build system: Move manual cbfstool add* invocations to cbfs-files 1eee076 build system: don't try to add cbfs-files with no backing file 9b5b536 build system: establish priority levels for CBFS file additions See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

ASUS KFSN4-DRE (K8) Automated Test Failure
by Raptor Engineering Automated Coreboot Test Stand Dec. 1, 2015

Dec. 1, 2015

The ASUS KFSN4-DRE (K8) fails verification as of commit bd88fa0ef62339bfc3027423d230a6ffcd1419ae The following tests failed: BOOT_FAILURE Commits since last successful test: bd88fa0 fsp_baytrail: Remove use of BAYTRAIL_SMM Kconfig symbol 4013469 build system: add dependencies for SeaBIOS output 3093038 nb/amd/amdmct/mct_ddr3: Use StopOnError to decrease training time 9586dc7 mainboard/intel: Add Little Plains b4b298c mainboard/asus/kgpe-d16: Limit HT speed to 2.6GHz <7 commits skipped> 551b383 build system: move defconfig creation into a cbfs-files filter 10420cc build system: break overly long lines into logical units c35bd54 build system: Move manual cbfstool add* invocations to cbfs-files 1eee076 build system: don't try to add cbfs-files with no backing file 9b5b536 build system: establish priority levels for CBFS file additions See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE (K8) test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0