coreboot December 2016

coreboot@coreboot.org

57 participants
121 discussions

Re: [coreboot] T430s or T430 (Was: latest greatest thinkpad with coreboot)
by Pok Gu 05 Dec '16

05 Dec '16

Thanks all. I value all your concerns on freedom (not opensource) and security and the feeling of having control. Let's say down to earth. I just wondering are there any other cool things (e.g., unlocking features) we can get. Because it seems the reason that other projects (e.g., OpenWRT) is so popular is it unlock many features along with the freedom/security once a router flash it. 2016-12-05 0:41 GMT+08:00 ron minnich <rminnich(a)gmail.com>: > > > On Sun, Dec 4, 2016 at 1:00 AM Pok Gu <pokgoo002(a)gmail.com> wrote: > >> I own a T430 and T420. It seems there is not a strong motivation for >> doing the T430/T530 port. Unlike the T420/T520, the obvious benefit of >> coreboot is it can replace the sandy bridge CPU with an ivy bridge one. >> What are the explicit benefits that coreboot can bring to the T430/T530 >> except opensource/security? >> > > I am very concerned about thinkpads and bios malware, as installed by > Lenovo: > https://www.techdirt.com/articles/20150812/11395231925/ > lenovo-busted-stealthily-installing-crapware-via-bios- > fresh-windows-installs.shtml > > This may not be a concern to you, but to many people it is an issue. > > Thinkpads are nice. Their BIOS is not nice. >

1 0

Re: [coreboot] Fund a TALOS Secure Workstation as coreboot build system
by Martin Roth 05 Dec '16

05 Dec '16

Update: I've added coreboot's commitment to purchase a board and a processor to the crowdsupply site. Board: 3700 Processor: 1240 We've got $6,200 committed from 11 contributors. If things work out, the rest of the money will be used for the additional components needed, and an upgraded processor. Thanks to everyone who committed to supporting the purchase. Martin On Thu, Nov 10, 2016 at 10:36 AM, Martin Roth <gaumless(a)gmail.com> wrote: > Update: > We've got $4400 promised, with 7 contributors. > > On Mon, Nov 7, 2016 at 2:22 PM, Martin Roth <gaumless(a)gmail.com> wrote: >> >> Update: >> After the weekend, we're up to $3700 with 5 contributors. >> >> Martin >> >> On Sun, Nov 6, 2016 at 1:01 PM, David Hendricks >> <david.hendricks(a)gmail.com> wrote: >>> >>> >>> >>> On Fri, Nov 4, 2016 at 9:36 AM, Martin Roth <gaumless(a)gmail.com> wrote: >>>> >>>> Is getting a Talos workstation as a build server something that people >>>> are interested in contributing money for? >>> >>> >>> Yes, this needs to happen. >>> >>>> >>>> So far, we've got $2500 pledged from two contributors out of the $7500 >>>> needed to get a server. >>> >>> >>> I'll match up to $2000 worth of small/moderate pledges ($250 or less). So >>> if 10 people pledge $200 I'll chip in $2000 to bring us to $6500. >> >> >

1 0

Re: [coreboot] Fund a TALOS Secure Workstation as coreboot build system
by Merlin Büge 04 Dec '16

04 Dec '16

Hey all, > > I pledge 1,000 $. > Awesome! I think we are far more than half by now! For those who did not read (all) Updates, here is an excellent write-up on (vendor) hardware lockdown and its consequences for the free software world. [0] (for those of you who don't know about it already...) > People care, and ~$380k over 280+ pledges confirms this. But the TALOS > project is asking for about an order of magnitude more funding, and > 2-100x more money per working end product, than pretty much any other > CrowdSupply hardware platform crowdfunding effort likely to be of > interest to free software people (Novena, Librem 13, Librem 15, > EOMA68, USB Armory, etc). They surely target another group than the projects you mentioned. Not only in that Talos is more expensive (i.e. many people cannot afford it) than other free hardware projects, but also that probably most of them do not need such a powerful workstation -- at least for me, that's the case. But if you need the power and can spend $2k on a workstation, you can also spend $4k. And btw. Librem is shit, freedom-wise. > I realise that the TALOS is unique in its combination of technologies, > and that these technologies were chosen for very good reasons. But I > also realise that not many people can afford to buy a $7100 computer, > especially if one of the existing Libreboot or coreboot-supported > devices would meet most of their needs. > > As for the non-hardware options TALOS offers, I suspect people have > some difficulty justifying making charitable donations towards a > for-profit enterprise, or paying for SaaSS under a time limit and with > only fairly limited use-cases. To me, the point of this campaign is not to get cool free hardware, but to create/restore the very foundations that are needed to have them, i.e. research (so we can build on that and have that knowledge) and development (so we / other people have the ability to buy free and high-performance computing hardware). Really, if you're reading a bit on what's going on in the world regarding the freedom of hardware (e.g. article above, more and more lockdowns), imo it's easily justified to spend a few hundred dollars or, if you can, a few thousands for it -- without obtaining any actual hardware. That said, I think the most important thing is now 1) spreading the word, and 2) pulling oneself together to spend some money "just" for our digital freedom. Just imagine that *awesome* moment when Talos got funded, knowing that *you* were an indispensable part of it! I think that's easily worth it. Regards, Merlin [0] https://www.crowdsupply.com/raptor-computing-systems/talos-secure-workstati… -- Merlin Büge <toni(a)bluenox07.de>

2 1

Re: [coreboot] T430s or T430 (Was: latest greatest thinkpad with coreboot)
by ron minnich 04 Dec '16

04 Dec '16

On Sun, Dec 4, 2016 at 1:00 AM Pok Gu <pokgoo002(a)gmail.com> wrote: > I own a T430 and T420. It seems there is not a strong motivation for doing > the T430/T530 port. Unlike the T420/T520, the obvious benefit of coreboot > is it can replace the sandy bridge CPU with an ivy bridge one. What are the > explicit benefits that coreboot can bring to the T430/T530 except > opensource/security? > I am very concerned about thinkpads and bios malware, as installed by Lenovo: https://www.techdirt.com/articles/20150812/11395231925/lenovo-busted-stealt… This may not be a concern to you, but to many people it is an issue. Thinkpads are nice. Their BIOS is not nice.

1 0

Re: [coreboot] T430s or T430 (Was: latest greatest thinkpad with coreboot)
by Sam Kuper 04 Dec '16

04 Dec '16

On 04/12/2016, Pok Gu <pokgoo002(a)gmail.com> wrote: > It seems there is not a strong motivation for doing > the T430/T530 port. [...] What are the > explicit benefits that coreboot can bring to the T430/T530 except > opensource/security? Freedom & security are, arguably, *very* strong motivations. > -Unlock RAM speed and WIFI whitelist removel? There are already Modded BIOS > for this The modded BIOSes lack the freedom and security enhancements offered by Coreboot. > -Remove evil ME? This is a huge freedom and security enhancement, if achievable on the T430(s).

1 0

Re: [coreboot] T430s or T430 (Was: latest greatest thinkpad with coreboot)
by Nico Huber 04 Dec '16

04 Dec '16

On 03.12.2016 01:46, Sam Kuper wrote: > On 02/12/2016, Nico Huber <nico.h(a)gmx.de> wrote: >> The T430 seems to be unsupported. >> Also I guess, it would only be one or two days of work > > One or two days of work for whom? E.g. did you have in mind a specific > person (if so, who?), or a non-specific person with a specific skill > set (if so, which skill set?)? Well, it's a really rough estimate to be honest. I'd say one day for somebody who already did a Sandy/Ivy Bridge ThinkPad port. Two days for somebody who knows his way around Intel boards in coreboot. Maybe it can also be done in two days with autoport and asking questions in IRC (by somebody coreboot experienced who is skilled in C). This doesn't account for hardware access (flashing, debugging) ofc. Nico

3 2

33c3 congress organisation
by Alexander Couzens 03 Dec '16

03 Dec '16

hi, the chaos communication congress is knocking at the door. I started a pad to track the hardware which is there for hacking. https://pads.ccc.de/coreboot-33c3 best, lynxis ps. there is also a wiki link https://events.ccc.de/congress/2016/wiki/Assembly:Coreboot -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604

1 0

Re: [coreboot] Fund a TALOS Secure Workstation as coreboot build system
by Paul Menzel 03 Dec '16

03 Dec '16

Dear Martin, Am Freitag, den 04.11.2016, 10:36 -0600 schrieb Martin Roth: > Is getting a Talos workstation as a build server something that people are > interested in contributing money for? Yes, let’s do this. > So far, we've got $2500 pledged from two contributors out of the $7500 > needed to get a server. I pledge 1,000 $. Everyone, the TALOS campaign only reached 10 % of the funding goal, and there are only twelve days left. Only 184 people have pledged 10 $, and only 15 pledged 250 $. Please help spread the word. Do you know somebody working at some newspaper, magazine, or has a blog, in the Linux kernel community, or at the EFF or at Mozilla. Please tell them about that. Currently, it looks like free software people don’t care about getting control over their hardware back. Thanks, Paul [1] https://www.crowdsupply.com/raptor-computing-systems/talos-secure-workstati…

2 1

Re: [coreboot] Execute Linux on AMD DB-FT3b-LC through GRUB2
by Zoran Stojsavljevic 03 Dec '16

03 Dec '16

Excellent, Grigore. One problem less. At least, I learned from your practical experience handful! :-) Zoran On Fri, Dec 2, 2016 at 6:04 PM, Grigore Lupescu <grigore(a)arista.com> wrote: > Restarting the config from scratch and setting Keep Vesa framebuffer I am > able to enter gfxterm in GRUB2. > Linux is also booting now, happy day :) > > On Fri, Dec 2, 2016 at 3:24 PM, Grigore Lupescu <grigore(a)arista.com> > wrote: > >> Hi Zoran, >> >> Thanks for your suggestions - it may not be vBIOS but it's most likely >> somewhere around there. >> >> I updated the VBIOS from Coreboot (~2014) with the newest one from AMD >> (~2015) with no impact on the behavior. >> At this point I think the Coreboot settings for the platform may cause >> this i.e. for some reason *vga_text* is chosen over *gfxterm* which is >> not even configured but barely exists. >> >> I have though managed to improve the status of the *vga_text* mode. So >> GRUB2 was restarting when reaching the end of the screen. I traced this to >> the *screen_read_char* which is issued when the *inc_y* == ROWS (this >> call would break GRUB2). I didn't go even further with the debug though. I >> just clear the screen and set grub_curr_pos.y to 0 and by using set pager=1 >> I can browse with enter through all the output page by page. It's not ideal >> but it was fast and practical. >> >> Linux though still doesn't boot. I am currently looking why the vga_text >> mode is selected over gfxterm which is not even configured properly. >> >> Thanks, >> Grigore >> >> On Wed, Nov 30, 2016 at 7:15 PM, Zoran Stojsavljevic < >> zoran.stojsavljevic(a)gmail.com> wrote: >> >>> Hello Grigore, >>> >>> Did not abandon you ("Dr. House" lookalike, same age, same attitude). I >>> though about the issue... Gave it hard try/thought! At least, I have tried. >>> And here is what I came with... >>> >>> > Differences on GRUB2 environment: >>> > AMI BIOS + *GRUB2.02beta2-36ubuntu3.1* => terminal_output=*gfxterm*, >>> see USB-SATA SSD as (*hd0*), (*hd0*, gpt0).., works >>> > both on USB2.0 and USB3.0. >>> > Coreboot + *GRUB2.02beta3* => terminal_output=*vga_text*, see >>> USB-SATA SSD as (*usb0*), (*usb0*, gpt0).., works only on USB2.0. >>> >>> So... Here are bullet points: >>> [1] Above: you are telling/writing to me that Coreboot has newest GRUB2 >>> SW than Ubuntu 16.04 LTS, Linux ft3b-lc 4.4.0-31-generic??? Question to >>> you: are you sure? Please, check again? >>> [2] *VERY/CRITICALLY important:* Are you sure that in BOTH cases above >>> you are using *THE SAME vBIOS *component? >>> In other words, you should go to: https://ami.com/products/bios >>> -uefi-tools-and-utilities/bios-uefi-utilities/... And try to extract >>> vBIOS out of your AMI BIOS you are alternately using to test... And >>> replace/swap one (you are using currently) in Coreboot. >>> >>> Good luck! :-) >>> Zoran >>> _______ >>> >>> On Tue, Nov 29, 2016 at 2:44 PM, Grigore Lupescu <grigore(a)arista.com> >>> wrote: >>> >>>> Hello Zoran, >>>> First of all thank you very much for your feedback - any idea would be >>>> worth trying. >>>> >>>> I am sorry about the mixup by putting the 3.13 commands there (it was >>>> 4.4 actually). I use TAB press to get the actual version on the SSD drive >>>> (4.4.0-31) and those exact commands. So my bad on the last email, these are >>>> the actual ones: >>>> >>>> grub> set root=(hd0,gpt2) >>>> grub> linux /boot/vmlinuz-4.4...-generic root=/dev/sda2 >>>> grub> initrd /boot/initrd.img-4.4...-generic >>>> grub> boot >>>> >>>> So I am trying to boot from an SSD with Linux connected to a USB port - >>>> why I am doing this ? :) because the board has a dedicated embedded style >>>> power supply and 1 SATA cable, hence even though I can connect the SSD >>>> directly I cannot power it - so I use a USB to SATA drive where I have the >>>> SSD plugged in (and legacy Ubuntu Linux x64 4.4 on it). >>>> >>>> Below are the full details of the AMI BIOS, Linux OS, Coreboot I am >>>> trying to boot over Coreboot (latest). So looking at these ++ previous ones >>>> it looks like vBIOS is in both. >>>> >>>> AMI BIOS 2.17.1246 Copyright 2015 >>>> Core Version 4.6.5.4 >>>> UEFI 2.3.1; PI 1.2 >>>> Project Version 1ASNG 0.02 x64 >>>> Chipset->GFX Configuration >>>> IGD VBIOS Version ATOMBIOSBK-AMD VERO15.042.000.002.0000000 >>>> Advanced->CPU Configuration >>>> AGESA Version 1.0.0.5 >>>> terminal_output: *gfxterm* >>>> >>>> Ubuntu 16.04 LTS, Linux ft3b-lc 4.4.0-31-generic #50 Ubuntu SMP Wed Jul >>>> 13 UTC 2016 x86_64 >>>> GNU GRUB 2.02~beta2-36ubuntu3.1 >>>> >>>> Coreboot (latest branch) >>>> I have the latest Coreboot sources, have set config accordingly (e.g. >>>> CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), getting an >>>> image on HDMI and the GRUB2 payload is executing. In GRUB2 payload I seem >>>> to have an overflow issue possibly related to the *vga_text* mode. >>>> terminal_output: *vga_text* >>>> GRUB 2.02 beta3 >>>> >>>> Differences on GRUB2 environment: >>>> AMI BIOS + GRUB2.02beta2-36ubuntu3.1 => terminal_output=*gfxterm*, see >>>> USB-SATA SSD as (*hd0*), (*hd0*, gpt0).., works both on USB2.0 and >>>> USB3.0. >>>> Coreboot + GRUB2.02beta3 => terminal_output=*vga_text*, see USB-SATA >>>> SSD as (*usb0*), (*usb0*, gpt0).., works only on USB2.0. >>>> >>>> Thank you, >>>> Grigore >>>> >>>> On Mon, Nov 28, 2016 at 10:40 PM, Zoran Stojsavljevic < >>>> zoran.stojsavljevic(a)gmail.com> wrote: >>>> >>>>> Grigore, >>>>> >>>>> Here are my comments to what you wrote to me: >>>>> >>>>> On Mon, Nov 28, 2016 at 7:59 PM, Grigore Lupescu <grigore(a)arista.com> >>>>> wrote: >>>>> >>>>>> Hello Zoran, >>>>>> >>>>>> [1-3] I am using the latest Ubuntu 16.04 LTS x64 desktop, 4.4 kernel. >>>>>> >>>>> >>>>> Perfect. Got it. Good to know. 16.04 LTS support back-ports to kernel >>>>> 4.4 APIs most of the newer features exceeding 4.4 version for some time >>>>> (this is very important info to/for me, never mind). >>>>> >>>>> >>>>>> [4] I don't know exactly if it's x64 or x86. I have no control over >>>>>> AMI BIOS since it's just a binary I flash into the SPI ROM, which supports >>>>>> the board. >>>>>> >>>>> >>>>> Even if it is a binary, you should be able to enter it (CMOS) pressing >>>>> at the very beginning of the boot <esc> or <F2> (maybe <F1>, Lenovo 420T >>>>> supports <F1>, as example), or simultaneously - alternately both of them, >>>>> one after another (NOT both at the same time). Then you can read the BIOS >>>>> version from system BIOS page. Maybe version says what is the architecture. >>>>> Other that that, it is bloody hard to tell what BIOS (32 or 64) you have. >>>>> It is easier if you do have UEFI BIOS, but you must have/gain access to EFI >>>>> shell, which is another problem, another dimension. >>>>> >>>>> >>>>>> [5] I boot Linux using legacy mode (in AMI, the Linux was installed >>>>>> for legacy boot on the HDD/SSD which connects via USB - USBtoSATA) >>>>>> >>>>> >>>>> You see... BIOS is a beast. With BIOS, if you have already attached >>>>> HDMI monitor, BIOS should/must detect this and record, and pass such info >>>>> to OS, somehow (very long story). Regardless what your GRUB2 supports (or, >>>>> at least, this is my naive understanding). >>>>> >>>>> If your BIOS is a legacy one, guess who is doing this detection? Which >>>>> part of BIOS?! I'll tell this secret (ONLY) to you: vBIOS! ;-) >>>>> >>>>> >>>>>> [6] I'm not sure. So I have the following checked: >>>>>> - Run VGA Option ROMs, Native Mode >>>>>> - Add a VGA BIOS image -> 3rdparty/blobs.../VBIOS.bin >>>>>> - Set framebuffer resolution (any, without this + above, I have no >>>>>> HDMI output) >>>>>> >>>>> >>>>> The secret, I'll whisper only to you again... You MUST add to Coreboot >>>>> vBIOS as video component, because vBIOS will pass to Linux so-called VBT >>>>> (the same it does above, being part of BIOS), where these info are recorded >>>>> (Coreboot, no Coreboot, does NOT matter, but for Linux video, vBIOS >>>>> component extremely DOES matter). >>>>> >>>>> (for UEFI boot, this works completely differently... Just tiny note) >>>>> >>>>> >>>>>> [7] It's the same one referenced from Coreboot in the external >>>>>> payloads - GRUB 2.02 beta3. >>>>>> >>>>> >>>>> I apologize. I made here a mistake. Forgot to mention - outdated >>>>> Coreboot GRUB2 payload. Here is a naive exercise to be done: >>>>> Please, program back BIOS into flash and boot your system (Ubuntu >>>>> 16.04). Please, stop in GRUB2, after BIOS, and inspect the Ubuntu 16.04 LTS >>>>> GRUB2 data. What is the GRUB2 version? >>>>> >>>>> And, as you have said: you are able (also) to execute in BIOS GRUB the >>>>> following (?!): >>>>> grub> set root=(hd0,gpt2) >>>>> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >>>>> grub> initrd /boot/initrd.img-3.13.0-29-generic >>>>> grub> boot >>>>> >>>>> Can you do this with the kernel 4.4??? Exact the same (above) >>>>> commands? And from where you do have 3.13? Also as entry in grub.cfg? >>>>> How/from where? Or, maybe... You use different HDD/SSD for Coreboot >>>>> purposes?! >>>>> >>>>> And if you use the same HDD/SSD, how do you have two different kernels >>>>> you are (after all) executing: >>>>> [A] Using GRUB2 as Coreboot payload as GRUB 2.02 beta3, executing >>>>> kernel 3.13??? >>>>> [B] Using GRUB2 (hidden behind MBR on the HDD/SSD) executing kernel >>>>> 4.4??? >>>>> >>>>> I did not get out of these emails the complete picture, I admit... :-( >>>>> >>>>> From your view where would the overflow / boot problems come from ? >>>>>> >>>>> >>>>> Still not able to answer this question, since I do not have clear >>>>> understanding what you actually do? I am trying... >>>>> >>>>> Thank you, >>>>> Zoran >>>>> >>>>> >>>>>> Thank you, >>>>>> Grigore >>>>>> >>>>>> On Mon, Nov 28, 2016 at 6:31 PM, Zoran Stojsavljevic < >>>>>> zoran.stojsavljevic(a)gmail.com> wrote: >>>>>> >>>>>>> Hello Grigore, >>>>>>> >>>>>>> I have here some dummy questions (forgive me for my ignorance), but >>>>>>> I need to ask them just for the sake of curiosity (maybe, after all, we can >>>>>>> get somewhere if I articulate questions in the right direction/right format >>>>>>> for this problem): >>>>>>> >>>>>>> > If I put a proprietary AMI BIOS, GRUB2 works without issue >>>>>>> in gfxterm mode and boots Linux without issue. >>>>>>> >>>>>>> [1] What Linux architecture are you using (32 or 64)? >>>>>>> [2] Which Linux distro? >>>>>>> [3] Which kernel version? >>>>>>> >>>>>>> If you put AMI BIOS, the following questions I would like to know: >>>>>>> >>>>>>> [4] Are you using 32 or 64 BIOS? >>>>>>> [5] Which mode are you using for booting (legacy/CSM ON or UEFI/CSM >>>>>>> OFF)? >>>>>>> [6] In the accordance with [5], what video component you have set >>>>>>> with CMOS: vBIOS or GOP driver? >>>>>>> >>>>>>> Not sure, but it seems to me that you are using too old/outdated >>>>>>> GRUB2 version (or maybe I am also mistaken)? >>>>>>> [7] Could you tell us, which GRUB2 version you are using? >>>>>>> >>>>>>> Thank you, >>>>>>> Zoran >>>>>>> >>>>>>> On Mon, Nov 28, 2016 at 7:13 PM, Grigore Lupescu via coreboot < >>>>>>> coreboot(a)coreboot.org> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I am trying to run Linux through the GRUB2 payload. I am not tied >>>>>>>> to GRUB2 but it's the only payload that gives me HDMI output (board has no >>>>>>>> serial port) using Coreboot and AMD FT3B-LC. >>>>>>>> >>>>>>>> I have the latest Coreboot sources, have set config accordingly >>>>>>>> (e.g. CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), >>>>>>>> getting an image on HDMI and the GRUB2 payload is executing. >>>>>>>> In GRUB2 payload I seem to have an overflow issue possibly related >>>>>>>> to the *vga_text* mode. If I put a proprietary AMI BIOS, GRUB2 >>>>>>>> works without issue in gfxterm mode and boots Linux without issue. >>>>>>>> >>>>>>>> Using Coreboot every time the screen gets full of text, GRUB2 >>>>>>>> re-executes. If I though set the terminal_output to cbmemc then commands >>>>>>>> would execute but Linux still fails to execute - at the end GRUB2 would >>>>>>>> restart. >>>>>>>> >>>>>>>> Also the GRUB2 payload on Coreboot does see the drive/files and >>>>>>>> attempts to execute - I looks like a GRUB2/Coreboot config/code problem. >>>>>>>> >>>>>>>> I execute the below in GRUB2 (which work on AMI BIOS + GRUB2). >>>>>>>> grub> set root=(hd0,gpt2) >>>>>>>> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >>>>>>>> grub> initrd /boot/initrd.img-3.13.0-29-generic >>>>>>>> grub> boot >>>>>>>> >>>>>>>> 1. Would anyone have any recommendation about the overflow in GRUB2 >>>>>>>> payload ? - related to Coreboot. >>>>>>>> 2. Any suggestions on booting Linux given this board's limitations >>>>>>>> on output (HDMI only) ? >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Grigore >>>>>>>> >>>>>>>> -- >>>>>>>> coreboot mailing list: coreboot(a)coreboot.org >>>>>>>> https://www.coreboot.org/mailman/listinfo/coreboot >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

1 0

Re: [coreboot] latest greatest thinkpad with coreboot
by Charlotte Plusplus 02 Dec '16

02 Dec '16

I see recommendations for a X230, but I disagree. If you really want the best, it's a W520 or a W530. In either, you can have 32G of Ram, and you can replace the default CPU with a Intel i7 3940XM cpu. But only on the W520 you will have a full size display port and (more important) an eSATAp connector. On thinkpads, you can usually have 3 drives: - a normal 2.5" SSD - another 2.5" in the optibay - a mSata in the WWAN port But with the eSATAp connector, you can have 4 drives, one of which will be external - either connected to the side of the laptop or to the dock. Useful for backups at proper SATA speeds. About the screen, the dock has extra display port connectors, and the internal LCD is 1920x1080, not high resolution but good enough. The CPU support vt-x and vt-d, so external displays can be used with qemu vfio (I don't have a dock yet, but I plan to do that soon) If we are talking about CPU, in theory, a modern P70 is faster. But if you overclock the 3940XM to 4.6 GHz, there is no faster thinkpad on the market. Cf the results from: https://thinkpad-forum.de/threads/199076-Projekt-quot-Das-Letzte-Thinkpad-q… (it requires a shell script to change the TDP and Turbo multipliers) The only issues with the W520 on coreboot is the power consumption, which I hope to fix when I will understand better how to talk to the EC to properly disable the NVidia GPU like the default bios does. With only the integrated 9 cell battery, I get about 4h, while putting my SSD into a similar W530 (same CPU) where I can do proper power management on the default bios, I get 7h (don't know how much precisely) Add a slice battery if you need more battery time (approx double) Charlotte On Thu, Dec 1, 2016 at 12:04 PM, ron minnich <rminnich(a)gmail.com> wrote: > what's the latest best one? What's the battery life like (can't be worse > than this mac pro that's always hot and now seems to have a life of 90 > minutes, always). How much dram/ssd can I jam in it? > > thanks > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot >

1 0

← Newer
1
...
7
8
9
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot December 2016