Compare commits
325 Commits
Author | SHA1 | Date |
---|---|---|
Leah Rowe | d8bcd5c704 | |
Leah Rowe | f5db507ecd | |
Leah Rowe | f81b24134d | |
Leah Rowe | 3f427a43a5 | |
Leah Rowe | 88ca46ad4c | |
Leah Rowe | aea5574f17 | |
Leah Rowe | 2a116950ed | |
Leah Rowe | 592fd5a385 | |
Leah Rowe | 38539e9fea | |
Leah Rowe | 557921522a | |
Leah Rowe | 6b95fd6afd | |
Leah Rowe | 99728a5cef | |
Leah Rowe | eb5f72881c | |
Leah Rowe | d68baade32 | |
Leah Rowe | 6afed5dd43 | |
Leah Rowe | e06b3adc5f | |
Gusher_123 | 6fa59464fa | |
Gusher_123 | 94c1e51ce3 | |
Gusher_123 | e4823653c6 | |
Leah Rowe | e27edff387 | |
chrislogan2 | da2ec62369 | |
Leah Rowe | 89868f9fa9 | |
Leah Rowe | ec4e4007fa | |
Leah Rowe | 1930325800 | |
Leah Rowe | 040249ca74 | |
Leah Rowe | 1ea2893e03 | |
Leah Rowe | b2b2b7a956 | |
Leah Rowe | 15f0b41108 | |
Leah Rowe | 31acab41da | |
sertonix | 91e4e3974a | |
Nicholas Chin | 222db52b57 | |
Leah Rowe | 699d8a8b87 | |
Leah Rowe | c1c9a60e67 | |
Ben Westover | 10b6ca1f63 | |
Leah Rowe | 0a66ed0e22 | |
Leah Rowe | 6520f681fa | |
Leah Rowe | 8c407d05c9 | |
Leah Rowe | 0fb8d5d757 | |
Leah Rowe | 061f47fd3a | |
Leah Rowe | 8451f94036 | |
Leah Rowe | a02fe843e6 | |
Leah Rowe | f671d89294 | |
Leah Rowe | 5d5ed3b930 | |
Leah Rowe | cb8dbd0f38 | |
Leah Rowe | 96e51ca06e | |
Leah Rowe | 83de07b603 | |
Leah Rowe | 4f992eedaa | |
Leah Rowe | ef774e2587 | |
Leah Rowe | 32b14145b3 | |
Leah Rowe | 27283a84d3 | |
Leah Rowe | 511d24b9ff | |
Leah Rowe | eb209ce899 | |
Leah Rowe | feb43add4d | |
Leah Rowe | 20fd775c85 | |
Leah Rowe | b7a4d7b121 | |
Leah Rowe | 71fc7a1981 | |
Leah Rowe | e62d443e81 | |
Leah Rowe | e647adc841 | |
Leah Rowe | 67770346e2 | |
Leah Rowe | dc7d5cef90 | |
Leah Rowe | b716e3fedd | |
Leah Rowe | 87a56ba001 | |
Riku Viitanen | 128d9e6094 | |
Leah Rowe | e0400031b9 | |
Leah Rowe | 20e2f572fb | |
Leah Rowe | b47f09e497 | |
Leah Rowe | 14f649771f | |
Leah Rowe | 240bfc950e | |
Leah Rowe | 2080975e95 | |
Leah Rowe | b1f3b1b4a6 | |
Leah Rowe | 0f56d4ce91 | |
Leah Rowe | e921e7536b | |
Integral | 67fb1bb6a6 | |
Leah Rowe | 51c06dcae2 | |
Integral | 64584fd7d3 | |
Integral | 0b02df943c | |
Leah Rowe | 3a23e0c350 | |
Riku Viitanen | 5e1ca595cd | |
Leah Rowe | 01c11b27d9 | |
Leah Rowe | ef8c2a7e59 | |
Leah Rowe | ad4e593dbf | |
Leah Rowe | 0a9bf4aa84 | |
Leah Rowe | d4886e608d | |
Leah Rowe | e2ce9110fb | |
Leah Rowe | a12f3efde7 | |
Leah Rowe | 8cc24220ec | |
Integral | a3be07f16d | |
Integral | 4aa7859146 | |
Leah Rowe | 7efde76782 | |
Leah Rowe | 9b4e436214 | |
Leah Rowe | 0081c6057a | |
Leah Rowe | c619e583b9 | |
Leah Rowe | 05036a5171 | |
Leah Rowe | b9bfa323b9 | |
Leah Rowe | 035468136a | |
Leah Rowe | cbac0dd6ea | |
Leah Rowe | 4847e31bfa | |
Leah Rowe | a9c4cfb2f6 | |
Leah Rowe | 94eff325ad | |
Leah Rowe | 62b45c4eb6 | |
Leah Rowe | 197ed1bab4 | |
Leah Rowe | a66c42170e | |
Leah Rowe | 2451bbcd0f | |
Leah Rowe | 7c200e1757 | |
Leah Rowe | 4fe298b3f3 | |
Leah Rowe | 6f4e9fd028 | |
Leah Rowe | 04a8bd8f7b | |
Leah Rowe | 4b580c489d | |
Leah Rowe | 01175b9f04 | |
Leah Rowe | eb6e09199b | |
Leah Rowe | 230e710292 | |
Leah Rowe | 93a742734e | |
Leah Rowe | 860909e3b7 | |
Leah Rowe | e0da53e540 | |
Leah Rowe | f4a5220ab2 | |
Riku Viitanen | 484e03812e | |
Leah Rowe | 04247d5016 | |
Leah Rowe | bedc002098 | |
Leah Rowe | a7e620e9a4 | |
Riku Viitanen | 2e4cff4335 | |
Riku Viitanen | c438c650aa | |
Riku Viitanen | b8bec5077c | |
Leah Rowe | 1476d8f9ef | |
Leah Rowe | 4c4fe77213 | |
Leah Rowe | 6c00c96374 | |
Leah Rowe | 9cf86a1c7f | |
Leah Rowe | a2de3ef6c2 | |
Leah Rowe | bc7e48dd94 | |
Leah Rowe | 237f6347ef | |
Leah Rowe | 092041ecee | |
Leah Rowe | d707c2ae31 | |
Leah Rowe | 3c1b13c2a3 | |
Leah Rowe | a84ab5fe7a | |
Leah Rowe | f2d4c76be9 | |
Leah Rowe | bf87a748e9 | |
Riku Viitanen | 7c73c4503d | |
Leah Rowe | 57cf037e17 | |
Leah Rowe | 2397c4c07c | |
Leah Rowe | 1d567f132b | |
Leah Rowe | 80274d293a | |
Leah Rowe | 6ba3133615 | |
Leah Rowe | ad148e0de9 | |
Leah Rowe | 4c62f7e4e1 | |
Leah Rowe | 7e5a1514d4 | |
Leah Rowe | 5de3d00672 | |
Riku Viitanen | 7ee4ad9f0a | |
Leah Rowe | f0deab660b | |
Leah Rowe | cc2aff727e | |
Leah Rowe | 1ad11d5512 | |
Leah Rowe | 4542dbad5e | |
Leah Rowe | de2ddf6d51 | |
Leah Rowe | 28f7d2a7e2 | |
Leah Rowe | 3171dc4ed8 | |
Leah Rowe | a61286298d | |
Leah Rowe | 6b521b1883 | |
Leah Rowe | 14c49868b6 | |
Leah Rowe | 660d9d87c7 | |
Leah Rowe | 1db5a7b31d | |
Leah Rowe | f0164c068a | |
Leah Rowe | e5ac0dc722 | |
Nicholas Chin | cd6c98c007 | |
Leah Rowe | e36c187728 | |
Leah Rowe | c4ede31c15 | |
Leah Rowe | 1eab9f9361 | |
Leah Rowe | b357ce21cc | |
Leah Rowe | b91e8d794d | |
Leah Rowe | c4d4e5c8f4 | |
Leah Rowe | fb428da88a | |
Leah Rowe | 3cd584af0d | |
Leah Rowe | 2dda91146d | |
Leah Rowe | c471157949 | |
Leah Rowe | d8cdbd744d | |
Lorenzo Aloe | e4b7dae859 | |
Leah Rowe | 9795f8d3c9 | |
Leah Rowe | e751bf37d6 | |
Leah Rowe | 22749922b6 | |
Leah Rowe | 551714f209 | |
Leah Rowe | e6151430c2 | |
Leah Rowe | b1790c0653 | |
Leah Rowe | 34a7f7c351 | |
Leah Rowe | c2a16bd33f | |
Leah Rowe | 1122c128c8 | |
Leah Rowe | 29d07bdbd9 | |
Leah Rowe | 95c0c089a7 | |
Leah Rowe | af4842b784 | |
Leah Rowe | b896e299d4 | |
Leah Rowe | 5c2fed17de | |
Leah Rowe | 4fb82aba55 | |
Leah Rowe | 03f2157108 | |
Leah Rowe | 6507b4741f | |
Leah Rowe | 365f8eb2c9 | |
Leah Rowe | 16ae385b84 | |
Leah Rowe | 2b2761eb47 | |
Leah Rowe | c617137f31 | |
Leah Rowe | 0c0be37eb9 | |
Leah Rowe | 464270371e | |
Riku Viitanen | 1b3fc7af6f | |
Leah Rowe | 3c5204487c | |
Leah Rowe | d54f193f64 | |
Leah Rowe | 6a6b7cbee0 | |
Leah Rowe | a41e4b0de1 | |
Leah Rowe | b0e43ae2ce | |
Leah Rowe | 98cfe4b37d | |
Leah Rowe | 31600fc44e | |
Leah Rowe | e32cbd0dfd | |
Leah Rowe | de7254b03d | |
Leah Rowe | a1f31c8932 | |
livio | ee168a0069 | |
Leah Rowe | 172e989463 | |
Leah Rowe | 06b57643a2 | |
Leah Rowe | 7d2813ee1b | |
Leah Rowe | 6e009f3818 | |
Leah Rowe | ce62a34fcb | |
Leah Rowe | 26bf88b05d | |
Leah Rowe | a5ab3969e0 | |
Leah Rowe | 1682d2731d | |
Leah Rowe | 11ca7793ee | |
Leah Rowe | 869342fd50 | |
Leah Rowe | 62faae9acd | |
Leah Rowe | 81f5521bfd | |
Leah Rowe | d75c3bb9dd | |
Leah Rowe | af1a9ac585 | |
Leah Rowe | 8f1ec9378e | |
Leah Rowe | 95306c9a8f | |
Leah Rowe | ed8f8969cd | |
Leah Rowe | 3e4e66b312 | |
Leah Rowe | fcdeb7114f | |
Leah Rowe | e0192ef6c9 | |
Leah Rowe | 1e31ca120c | |
Leah Rowe | 70c1ff6a55 | |
Riku Viitanen | 5d50d05f49 | |
Riku Viitanen | 506b6a2290 | |
Leah Rowe | 555bf879d1 | |
Leah Rowe | 40f5af0a45 | |
Leah Rowe | 8afcf59684 | |
Nicholas Chin | f0bc8ca6e0 | |
Nicholas Chin | 8f21d0625a | |
Nicholas Chin | 5291ce8c39 | |
Leah Rowe | 20c3d75020 | |
Leah Rowe | 972a412517 | |
Leah Rowe | 463bcbeeed | |
Leah Rowe | 7eec07383e | |
Leah Rowe | c9fb0a28ed | |
Leah Rowe | de6d67ce76 | |
Leah Rowe | f2da6c382c | |
Leah Rowe | fce013cc44 | |
Leah Rowe | 5b7cc0e859 | |
Leah Rowe | 71aecb2d90 | |
Leah Rowe | 3ae238c74c | |
Leah Rowe | 401c811b95 | |
Leah Rowe | 22d6aea226 | |
Leah Rowe | a5d383f503 | |
Leah Rowe | 44471f81a3 | |
Leah Rowe | 55ddbad186 | |
Leah Rowe | 0899e07e8c | |
Leah Rowe | 779b25d337 | |
Leah Rowe | 49fdc28d09 | |
Leah Rowe | 57915c2cfb | |
Leah Rowe | d2bc3ec116 | |
Leah Rowe | c37201b91b | |
Leah Rowe | 374f1c096b | |
Leah Rowe | 87ab083fb0 | |
Leah Rowe | 9684d47d23 | |
Leah Rowe | 4c78d74742 | |
Leah Rowe | 127d3c3262 | |
Leah Rowe | 34d442d651 | |
Leah Rowe | 87f9e850b8 | |
Leah Rowe | b4ef7c4eb6 | |
Leah Rowe | 2311db3d90 | |
Leah Rowe | f195e362f8 | |
Leah Rowe | cd570a5323 | |
Leah Rowe | e3c86b5c6a | |
Leah Rowe | 1bb2040650 | |
Leah Rowe | bd2a3297fa | |
Leah Rowe | 673ccb0589 | |
Leah Rowe | 4d91bb2e89 | |
Leah Rowe | 2d7bce5a3a | |
Leah Rowe | 84cd507eea | |
Leah Rowe | 66bee9741d | |
Leah Rowe | 1c49dfb1bc | |
Leah Rowe | 38fd4569f4 | |
Leah Rowe | 06acdb2865 | |
Leah Rowe | 28889ee6a4 | |
Leah Rowe | a8bbac960f | |
Leah Rowe | 454b171975 | |
Leah Rowe | b67d96fe7e | |
Leah Rowe | 3acf5fab95 | |
Leah Rowe | 6ebb88528e | |
Leah Rowe | 3e2882776c | |
Leah Rowe | cb69845699 | |
Leah Rowe | 29c93c8fc4 | |
Leah Rowe | a0cfac617c | |
Leah Rowe | e34f48a89d | |
Leah Rowe | 6e5ea12bdb | |
Leah Rowe | 4db82ace6f | |
Wei Mingzhi | bde19f8cb7 | |
Leah Rowe | ce6d9da778 | |
Leah Rowe | 24347a8362 | |
Leah Rowe | 050192f7c5 | |
Leah Rowe | dab74c3174 | |
Leah Rowe | 12ad68f543 | |
Wei Mingzhi | 31bef18593 | |
Leah Rowe | cace2e3bcb | |
Leah Rowe | e7a144d5cf | |
Leah Rowe | b1db92629a | |
Leah Rowe | 297f57056d | |
Leah Rowe | 819195233a | |
Leah Rowe | 33f28eec8c | |
Leah Rowe | 962ba02cba | |
Leah Rowe | d20bcc38fd | |
Leah Rowe | 4261d55010 | |
Leah Rowe | dafba8a5cb | |
Leah Rowe | 239ef69956 | |
Leah Rowe | aee0da2bea | |
Leah Rowe | 6951fc6f43 | |
Leah Rowe | 88869036a6 | |
Leah Rowe | 97451d48e4 | |
Leah Rowe | b3a420c239 | |
Leah Rowe | 4a15228d6d | |
Nicholas Chin | b52b93ebad | |
Nicholas Chin | 42814e9326 | |
Nicholas Chin | 8e8180d996 | |
Leah Rowe | f3001eae57 | |
livio | deeb98e312 | |
livio | e37788494d |
5
site.cfg
5
site.cfg
|
@ -1,5 +1,6 @@
|
||||||
TITLE="-T Libreboot"
|
# SPDX-License-Identifier: CC0-1.0
|
||||||
|
TITLE="Libreboot"
|
||||||
DOMAIN="https://libreboot.org/"
|
DOMAIN="https://libreboot.org/"
|
||||||
BLOGDIR="news/" # leave as empty string if you want the blog to be the homepage
|
BLOGDIR="news/" # leave as empty string if you want the blog to be the homepage
|
||||||
CSS="--css /global.css"
|
CSS="/global.css"
|
||||||
LAZY="y"
|
LAZY="y"
|
||||||
|
|
|
@ -3,7 +3,19 @@ title: Kontakt
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
**TODO: mailing lists, mastodon server and peertube account.**
|
Buy Libreboot pre-installed
|
||||||
|
==========
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
If you're installing Libreboot yourself, support for that is also available.
|
||||||
|
Contact information (IRC, mailing list etc) is below:
|
||||||
|
|
||||||
User support
|
User support
|
||||||
============
|
============
|
||||||
|
@ -11,10 +23,18 @@ User support
|
||||||
IRC oder Reddit werden bevorzugt, sofern Du eine Support Anfrage hast (IRC empfohlen).
|
IRC oder Reddit werden bevorzugt, sofern Du eine Support Anfrage hast (IRC empfohlen).
|
||||||
Für Informationen bzgl. IRC and Reddit siehe unten.
|
Für Informationen bzgl. IRC and Reddit siehe unten.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
============
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
Entwicklungs Diskussion
|
Entwicklungs Diskussion
|
||||||
======================
|
======================
|
||||||
|
|
||||||
Eine Mailing Liste ist für die Zukunft in Planung. Bis dahin, siehe unter
|
Siehe unter
|
||||||
[der Git Seite](git.md) für Informationen wie Du dich an der Entwicklung beteiligen kannst.
|
[der Git Seite](git.md) für Informationen wie Du dich an der Entwicklung beteiligen kannst.
|
||||||
|
|
||||||
Hier finden sich ebenso Anleitungen zum Senden von Patches (via Pull-Requests).
|
Hier finden sich ebenso Anleitungen zum Senden von Patches (via Pull-Requests).
|
||||||
|
|
|
@ -0,0 +1,98 @@
|
||||||
|
---
|
||||||
|
title: Contatti
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
Buy Libreboot pre-installed
|
||||||
|
==========
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
If you're installing Libreboot yourself, support for that is also available.
|
||||||
|
Contact information (IRC, mailing list etc) is below:
|
||||||
|
|
||||||
|
Supporto utenti
|
||||||
|
===============
|
||||||
|
|
||||||
|
IRC o Reddit sono consigliati, sebbene preferiamo che usi il canale IRC
|
||||||
|
per avere o per offrire supporto tecnico. Continua a leggere per avere
|
||||||
|
ulteriori informazioni.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
============
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
|
Discussione sullo sviluppo
|
||||||
|
==========================
|
||||||
|
|
||||||
|
Per ora dai un occhiata sulla
|
||||||
|
[pagina Git](git.md) per avere maggiori informazioni su come puoi
|
||||||
|
assistere con lo sviluppo.
|
||||||
|
|
||||||
|
Su quella stessa pagina puoi trovare informazioni su come inviare
|
||||||
|
correzioni (patches) tramite pull requests.
|
||||||
|
|
||||||
|
Canale IRC
|
||||||
|
==========
|
||||||
|
|
||||||
|
IRC e' il modo principale per contattare chi collabora con il progetto libreboot.
|
||||||
|
Il canale ufficiale e' `#libreboot` su Libera IRC.
|
||||||
|
|
||||||
|
Webchat:
|
||||||
|
<https://web.libera.chat/#libreboot>
|
||||||
|
|
||||||
|
Libera e' una tra le piu' grandi reti IRC usate per i progetti di software libero.
|
||||||
|
Maggiori informazioni le trovi qui: <https://libera.chat/>
|
||||||
|
|
||||||
|
Puoi usare il client IRC che preferisci (come weechat or irssi) usando le seguenti informazioni:
|
||||||
|
|
||||||
|
* Server: `irc.libera.chat`
|
||||||
|
* Canale: `#libreboot`
|
||||||
|
* Porta (TLS): `6697`
|
||||||
|
* Porta (non-TLS): `6667`
|
||||||
|
|
||||||
|
Ti suggeriamo di usare la porta `6697` e ablitare la cifratura TLS...
|
||||||
|
|
||||||
|
Inoltre ti suggeriamo di abilitare l'autenticazione SASL. Le pagine web
|
||||||
|
di Libera spiegano come:
|
||||||
|
|
||||||
|
* Guida per WeeChat: <https://libera.chat/guides/weechat>
|
||||||
|
* Guida per Irssi: <https://libera.chat/guides/irssi>
|
||||||
|
* Guida per HexChat: <https://libera.chat/guides/hexchat>
|
||||||
|
|
||||||
|
Comunque dovresti sempre controllare la documentazione del tuo client IRC preferito.
|
||||||
|
|
||||||
|
Reti sociali online
|
||||||
|
===================
|
||||||
|
|
||||||
|
Libreboot esiste ufficialmente in molte piattaforme.
|
||||||
|
|
||||||
|
Mastodon
|
||||||
|
--------
|
||||||
|
|
||||||
|
Il fondatore e sviluppatore principale, Leah Rowe, e' su Mastodon:
|
||||||
|
|
||||||
|
* <https://mas.to/@libreleah>
|
||||||
|
|
||||||
|
Posta elettronica
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
Leah puo' essere contattata anche via email a questo indirizzo:
|
||||||
|
[leah@libreboot.org](mailto:leah@libreboot.org)
|
||||||
|
|
||||||
|
Reddit
|
||||||
|
------
|
||||||
|
|
||||||
|
Usato principalmente come canale di supporto e per annunciare notizie:
|
||||||
|
<https://www.reddit.com/r/libreboot/>
|
||||||
|
|
|
@ -3,7 +3,19 @@ title: Contact
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
**TODO: mailing lists, mastodon server and peertube account.**
|
Buy Libreboot pre-installed
|
||||||
|
==========
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
If you're installing Libreboot yourself, support for that is also available.
|
||||||
|
Contact information (IRC, mailing list etc) is below:
|
||||||
|
|
||||||
User support
|
User support
|
||||||
============
|
============
|
||||||
|
@ -11,10 +23,18 @@ User support
|
||||||
IRC or Reddit are recommended, if you wish to ask for support (IRC recommended).
|
IRC or Reddit are recommended, if you wish to ask for support (IRC recommended).
|
||||||
See below for information about IRC and Reddit.
|
See below for information about IRC and Reddit.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
============
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
Development discussion
|
Development discussion
|
||||||
======================
|
======================
|
||||||
|
|
||||||
Mailing lists are planned for the future. For now, see notes
|
See notes
|
||||||
on [the Git page](git.md) for information about how to assist with development.
|
on [the Git page](git.md) for information about how to assist with development.
|
||||||
|
|
||||||
Instructions are also on that page for sending patches (via pull requests).
|
Instructions are also on that page for sending patches (via pull requests).
|
||||||
|
|
|
@ -3,7 +3,19 @@ title: Зв'язок
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
**TODO: списки розсилки, сервер mastodon та обліковий запис peertube.**
|
Buy Libreboot pre-installed
|
||||||
|
==========
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
If you're installing Libreboot yourself, support for that is also available.
|
||||||
|
Contact information (IRC, mailing list etc) is below:
|
||||||
|
|
||||||
Підтримка користувачів
|
Підтримка користувачів
|
||||||
============
|
============
|
||||||
|
@ -11,10 +23,18 @@ x-toc-enable: true
|
||||||
IRC або Reddit рекомендовані, якщо ви бажаєте попросити про допомогу (найкраще IRC).
|
IRC або Reddit рекомендовані, якщо ви бажаєте попросити про допомогу (найкраще IRC).
|
||||||
Дивіться інформацію нижче щодо IRC та Reddit.
|
Дивіться інформацію нижче щодо IRC та Reddit.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
============
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
Обговорення розробки
|
Обговорення розробки
|
||||||
======================
|
======================
|
||||||
|
|
||||||
Списки розсилки плануються на майбутнє. Зараз, подивіться нотатки
|
Зараз, подивіться нотатки
|
||||||
на [сторінці Git](git.md) для інформації щодо допомоги з розробкою.
|
на [сторінці Git](git.md) для інформації щодо допомоги з розробкою.
|
||||||
|
|
||||||
На цій сторінці також знаходяться інструкції по відправці патчів (через pull request'и).
|
На цій сторінці також знаходяться інструкції по відправці патчів (через pull request'и).
|
||||||
|
|
101
site/contrib.md
101
site/contrib.md
|
@ -196,33 +196,13 @@ systems.
|
||||||
Joshua Gay
|
Joshua Gay
|
||||||
----------
|
----------
|
||||||
|
|
||||||
Joshua is former FSF staff.
|
Joshua was in a position during 2014-2016 to help promote Libreboot in the
|
||||||
|
media, in his capacity working for the employer he worked for at the time;
|
||||||
|
I credit him specifically. Joshua was one of Libreboot's earliest supporters.
|
||||||
|
|
||||||
Joshua helped with the early founding of the Libreboot project, in his capacity
|
He made sure everyone knew what I was doing, and he taught me a *lot* about
|
||||||
(at that time) as the FSF's licensing and compliance manager. It was his job to
|
licensing; many of Libreboot's practises today are still based on his lessons,
|
||||||
review products sent into to the FSF for review; the FSF has a certification
|
such as the pitfalls of GPL compliance and how to really audit everything.
|
||||||
program called *Respects Your Freedom* (RYF) where the FSF will promote your
|
|
||||||
company's products if it comes with all Free Software.
|
|
||||||
|
|
||||||
I, Leah Rowe, was initially just selling ThinkPad X60 laptops with regular
|
|
||||||
coreboot on them, and this included CPU microcode updates. At the time, I didn't
|
|
||||||
think much of that. Joshua contacted me, in his capacity at the FSF, and asked
|
|
||||||
if I would be interested in the FSF's RYF program; I was very surprised that the
|
|
||||||
FSF would take me seriously, and I said yes. This is what started the early
|
|
||||||
work on Libreboot. Joshua showed me all the problems my products had, and from
|
|
||||||
that, the solution was clear:
|
|
||||||
|
|
||||||
Joshua used his media connections at the FSF to heavily promote my work, and
|
|
||||||
on December 13th, 2013, the Libreboot project was born (but not called that).
|
|
||||||
Joshua made sure that everyone knew what I was doing!
|
|
||||||
|
|
||||||
A few months later, the name *Libreboot* was coined, and the domain name
|
|
||||||
*libreboot.org* was registered. At that point, the Libreboot project (in early
|
|
||||||
2014) was officially born. Once again, Joshua provided every bit of help he
|
|
||||||
could, heavily promoting the project and he even wrote this article on the FSF
|
|
||||||
website, announcing it:
|
|
||||||
|
|
||||||
<https://web.archive.org/web/20171222063358/https://www.fsf.org/blogs/licensing/replace-your-proprietary-bios-with-libreboot>
|
|
||||||
|
|
||||||
Klemens Nanni
|
Klemens Nanni
|
||||||
-------------
|
-------------
|
||||||
|
@ -233,55 +213,28 @@ libreboot, and several tweaks to the build system.
|
||||||
Lisa Marie Maginnis
|
Lisa Marie Maginnis
|
||||||
-------------------
|
-------------------
|
||||||
|
|
||||||
Lisa is a former sysadmin at the Free Software Foundation. In the early days of
|
Lisa was one of Libreboot's early contributors to Libreboot. She personally
|
||||||
the project, she provided Leah with a lot of technical advice. She initially
|
helped me set up a lot of the early infrastructure, including things like IRC,
|
||||||
created Libreboot IRC channel, when Leah did not know how to
|
mailing list and so on. She provided a lot of technical guidance, while working
|
||||||
use IRC, and also handed +F founder status to Leah for the channel. As an FSF
|
in a sysadmin job for a certain free software organisation; she was both a
|
||||||
sysadmin, it was Lisa's job to maintain a lot of the infrastructure used by
|
mentor and a friend.
|
||||||
Libreboot; at the time, mailing lists on the Savannah website were used by
|
|
||||||
the Libreboot project. When Paul Kocialkowski was a member of the project in
|
|
||||||
2016, she helped him get help from the FSF; he was the leader of the Replicant
|
|
||||||
project at the time, which had funding from the FSF, and the FSF authorized him
|
|
||||||
to use some of that funding for his work on Libreboot, thanks to Lisa's
|
|
||||||
encouragement while she worked at the FSF.
|
|
||||||
|
|
||||||
Lisa also stepped in when Leah Rowe missed her LibrePlanet 2016 talk. Leah was
|
She got me in touch with a lot of people, and at one point was instrumental in
|
||||||
scheduled to do a talk about Libreboot, but didn't show up in time. Lisa, along
|
helping Paul Kocialkowski secure funding to work on the Veyron Speedy boards
|
||||||
with Patrick McDermott (former Libreboot developer, who was present at that
|
in Libreboot, e.g. ASUS Chromebook C201PA - at the time, this was using
|
||||||
conference) did the talk in Leah's place. The talk was never recorded, but the
|
Google's own Depthcharge payload, which you can find in 2016 Libreboot
|
||||||
Free Software Foundation has these photos of that talk on their LibrePlanet
|
releases.
|
||||||
website (the woman with the blue hair is Lisa, and the long-haired dude with the
|
|
||||||
moustache is Patrick):
|
|
||||||
|
|
||||||
<http://web.archive.org/web/20170319043913/https://media.libreplanet.org/u/libreplanet/m/session-02-c-mws-png-libreplanet-2016-sessions/>
|
Lorenzo Aloe
|
||||||
|
------------
|
||||||
|
|
||||||
<http://web.archive.org/web/20170319043915/https://media.libreplanet.org/u/libreplanet/m/session-02-c-wide-png-libreplanet-2016-sessions/>
|
Provided hardware testing for the [Dell OptiPlex 9020](docs/hardware/dell9020.md),
|
||||||
|
also provided testing for proxmox with GPU passthrough on Dell Precision T1650,
|
||||||
|
confirming near-native performance; with this, you can boot operating systems
|
||||||
|
virtually natively, performance-wise, on a Libreboot system in cases where
|
||||||
|
that OS is not natively supported.
|
||||||
|
|
||||||
Fun fact: Patrick is also the lead developer of ProteanOS, an FSF-endorsed
|
All round good guy, an honest and loyal fan.
|
||||||
embedded OS project: <http://proteanos.com/> (uses BusyBox and Linux-libre)
|
|
||||||
|
|
||||||
Leah Rowe ran *2* LibrePlanet workshops; one in 2015 and another in 2016, while
|
|
||||||
visiting Boston, MA, USA on both occasions to attend these conferences. These
|
|
||||||
workshops were for Libreboot installations. People came to both workshops, to
|
|
||||||
have Libreboot installed onto their computers. As FSF sysadmin, at that time,
|
|
||||||
Lisa provided all of the infrastructure and equipment used at those workshops.
|
|
||||||
Without her help, those workshops would have not been possible.
|
|
||||||
|
|
||||||
When the ASUS KGPE-D16 mainboard (high-end server board) was ported to Libreboot,
|
|
||||||
Leah, working with Timothy Pearson (the one who ported it), shared patches back
|
|
||||||
and forth with Lisa around mid 2016, mostly raminit patches, to get the board
|
|
||||||
running at the FSF offices. This work ultimately lead to a most wonderful
|
|
||||||
achievement:
|
|
||||||
|
|
||||||
The FSF and GNU websites now run on
|
|
||||||
Librebooted ASUS KGPE-D16 based servers, on a fully free GNU+Linux distro. This
|
|
||||||
means that the FSF now has full software freedom for their hosting infrastructure.
|
|
||||||
|
|
||||||
The FSF also provides access to this infrastructure for many other projects
|
|
||||||
(besides GNU projects).
|
|
||||||
|
|
||||||
Lisa was a strong supporter of Libreboot in the very early days of the project,
|
|
||||||
and her contributions were invaluable. I, Leah Rowe, owe her a debt of gratitude.
|
|
||||||
|
|
||||||
Marcus Moeller
|
Marcus Moeller
|
||||||
--------------
|
--------------
|
||||||
|
@ -305,10 +258,6 @@ relating to the [Intel Management Engine](../faq.md#intelme), in addition
|
||||||
to making several improvements to the build system in libreboot. **Former
|
to making several improvements to the build system in libreboot. **Former
|
||||||
libreboot project maintainer.**
|
libreboot project maintainer.**
|
||||||
|
|
||||||
In 2016, Leah Rowe ran a Libreboot installation workshop at the FSF's
|
|
||||||
LibrePlanet conference. Working alongside Leah, Patrick helped run the workshop
|
|
||||||
and assisted with installing Libreboot onto people's machines.
|
|
||||||
|
|
||||||
Paul Kocialkowski
|
Paul Kocialkowski
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
|
@ -337,6 +286,8 @@ Helped write the [FAQ section about DMA](../faq.md#hddssd-firmware), and provide
|
||||||
general advice in the early days of the project. Peter was a coreboot developer
|
general advice in the early days of the project. Peter was a coreboot developer
|
||||||
in those days, and a major developer in the *libusb* project (which flashrom
|
in those days, and a major developer in the *libusb* project (which flashrom
|
||||||
makes heavy use of).
|
makes heavy use of).
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024.
|
||||||
|
|
||||||
Peter also wrote the *bucts* utility used to set Backup Control (BUC) Top Swap
|
Peter also wrote the *bucts* utility used to set Backup Control (BUC) Top Swap
|
||||||
(TS) bit on i945 laptops such as ThinkPad X60/T60, which is useful for a
|
(TS) bit on i945 laptops such as ThinkPad X60/T60, which is useful for a
|
||||||
|
|
|
@ -1,454 +0,0 @@
|
||||||
---
|
|
||||||
title: Учасники проекту
|
|
||||||
x-toc-enable: true
|
|
||||||
...
|
|
||||||
|
|
||||||
У цьому списку не обов'язково вказується, хто зараз працює над проектом,
|
|
||||||
але в ньому вказано людей, які зробили значний внесок у проект.
|
|
||||||
|
|
||||||
Якщо ми забули вас тут згадати, повідомте нам, і ми вас додамо. (або якщо
|
|
||||||
ви не хочете, щоб вас згадували, повідомте нас, і ми видалимо ваш
|
|
||||||
запис)
|
|
||||||
|
|
||||||
Інформацію про те, хто працює над libreboot і як працює проект, можна
|
|
||||||
знайти на цій сторінці: [who.md](who.md)
|
|
||||||
|
|
||||||
Ви можете дізнатися історію проекту libreboot, просто прочитавши цю сторінку.
|
|
||||||
Тут докладно розповідається про всі основні внески в проект і
|
|
||||||
загалом про те, як створювався проект (і хто допоміг його створити).
|
|
||||||
|
|
||||||
Лія Роу
|
|
||||||
---------
|
|
||||||
|
|
||||||
**Засновник проекту Libreboot, а зараз провідний розробник** Лія
|
|
||||||
працює над усіма аспектами libreboot, такими як:
|
|
||||||
|
|
||||||
* Загальне керівництво. Лія обробляє всі зовнішні внески до libreboot,
|
|
||||||
переглядає пул реквести, має справу із звітами про помилки, делегує завдання, коли це необхідно
|
|
||||||
або бажано. Лія контролює серверну інфраструктуру libreboot.org, розміщену
|
|
||||||
в її лабораторії.
|
|
||||||
* Лія має останнє слово щодо всіх рішень, беручи внесок через обговорення з
|
|
||||||
представниками громадськості, переважно на IRC. Лія контролює випуски libreboot
|
|
||||||
і загалом підтримує проект. Без Лії не було би Libreboot!
|
|
||||||
* Система збірки (lbmk, скорочення від libreboot Make). Це автоматизована
|
|
||||||
система збирання, яка лежить в серці libreboot; він завантажує, патчить, налаштовує
|
|
||||||
та компілює відповідні компоненти, такі як coreboot, GRUB, і генерує образи ROM
|
|
||||||
libreboot, які ви можете знайти в архівах випусків.
|
|
||||||
* Апстрім робота над coreboot, коли необхідно (та іншими проектами, які libreboot
|
|
||||||
використовує). Це також означає роботу з людьми поза межами проекту libreboot,
|
|
||||||
щоб об'єднати виправлення (між іншим) в апстрім проектах,
|
|
||||||
які libreboot використовує
|
|
||||||
* Надання підтримки користувачів на IRC
|
|
||||||
|
|
||||||
Калеб Ла Гранж
|
|
||||||
---------------
|
|
||||||
|
|
||||||
**Вторинний розробник, номер два для Лії.** Калеб - розробник libreboot на повний робочий день
|
|
||||||
з вузьким фокусом. Калеб зосереджується на кількох напрямках розвитку:
|
|
||||||
|
|
||||||
* Система побудови. Калеб відповідає за вдосконалення та виправлення системи побудови libreboot Make.
|
|
||||||
Зокрема, управління бінарними блобами, автоматизація та відтворюваність.
|
|
||||||
* Апаратна модифікація. Калеб має пристрасть до переробки апаратного забезпечення; паяння,
|
|
||||||
розпаювання, та тестування libreboot на отриманому обладнанні.
|
|
||||||
* Перенесення плати. Все, що підтримується в Coreboot, можна перенести на libreboot, Калеб
|
|
||||||
перевірить і перенесе будь-яку плату, до якої зможе потрапити. Крім того, будь-хто може
|
|
||||||
зв'язатись з Калебом, щоб створити образи libreboot для тестування на своїй платі.
|
|
||||||
* Документація. Калеб активно веде документацію щодо зазначених вище сфер
|
|
||||||
інтересу. Додатково, Калеб відповідає за посібники з розбирання з власними
|
|
||||||
малюнками та діаграмами для кількох плат.
|
|
||||||
* Підтримка користувачів. Калеб активний в irc і готовий допомогти будь-якому користувачеві, який зацікавлений в
|
|
||||||
використанні libreboot або потребує допомоги.
|
|
||||||
* Цілі проекту. Калеб співпрацює з Лією над визначенням цілей проекту.
|
|
||||||
Лія має останнє слово в кожному рішенні.
|
|
||||||
|
|
||||||
Зовнішні проекти
|
|
||||||
================
|
|
||||||
|
|
||||||
Проект Coreboot
|
|
||||||
----------------
|
|
||||||
|
|
||||||
Без coreboot проект libreboot був би просто неможливий.
|
|
||||||
|
|
||||||
Людей і компаній, які працюють над coreboot, багато, і вони роблять
|
|
||||||
проект libreboot таким, яким він є. Проект libreboot активно використовує coreboot
|
|
||||||
для ініціалізації обладнання.
|
|
||||||
|
|
||||||
GRUB
|
|
||||||
--------
|
|
||||||
|
|
||||||
GRUB - це завантажувач, який використовується libreboot. Само собою зрозуміло, що
|
|
||||||
розробники GRUB стимулюють libreboot своєю роботою.
|
|
||||||
|
|
||||||
SeaBIOS
|
|
||||||
-------
|
|
||||||
|
|
||||||
Прошивка libreboot надає SeaBIOS як опцію корисного навантаження. SeaBIOS забезпечує
|
|
||||||
застарілу реалізацію BIOS x86.
|
|
||||||
|
|
||||||
U-Boot
|
|
||||||
------
|
|
||||||
|
|
||||||
Libreboot використовує U-Boot як корисне навантаження coreboot на ноутбуках
|
|
||||||
ARM Chromebook з підтримкою coreboot.
|
|
||||||
|
|
||||||
Внески в алфавітному порядку
|
|
||||||
============================
|
|
||||||
|
|
||||||
Алісса Розенцвейг
|
|
||||||
-----------------
|
|
||||||
|
|
||||||
Переключила веб-сайт на використання розмітки замість рукописного HTML та користувацького
|
|
||||||
PHP. **Колишній супроводжувач проекту libreboot (системний адміністратор libreboot.org).**
|
|
||||||
|
|
||||||
Алісса написала оригінальний генератор статичних сайтів (скрипти `sh`, що перетворюють
|
|
||||||
markdown в html, через pandoc) для libreboot.org. Цей генератор статичних сайтів
|
|
||||||
був значно змінений і відгалужений Лією Роу у формальний проект:
|
|
||||||
|
|
||||||
<https://untitled.vimuser.org/> (untitled - це робота Лії, а не Алісси, але вона базується на
|
|
||||||
оригінальній роботі Аліси над генератором статичних сайтів, який раніше використовував Libreboot;
|
|
||||||
веб-сайт Libreboot тепер створено за допомогою Untitled)
|
|
||||||
|
|
||||||
Альпер Небі Ясак
|
|
||||||
----------------
|
|
||||||
|
|
||||||
Надав інтеграцію системи збірки та документацію для використання
|
|
||||||
U-Boot в якості корисного навантаження, та початкові порти Libreboot деяких ARM Chromebook
|
|
||||||
виходячи з того.
|
|
||||||
|
|
||||||
Альпер також займається розробкою на U-Boot, напр. продовжив майже завершений
|
|
||||||
порт плати `gru-kevin` і об'єднав його з апстрімом.
|
|
||||||
|
|
||||||
Артур Хейманс
|
|
||||||
--------------
|
|
||||||
|
|
||||||
Об'єднав патч із coreboot у libreboot, дозволяючи режимам живлення C3 та C4
|
|
||||||
правильно працювати на ноутбуках GM45. Це була давня проблема до внеску
|
|
||||||
Артура. Артур також виправив розмір відеопам'яті на i945 на системах
|
|
||||||
GM45, що дозволило максимально розподілити VRAM для вбудованих графічних процесорів
|
|
||||||
у цих системах, ще одна давня проблема в libreboot.
|
|
||||||
|
|
||||||
Артур також працював над системою збірки Libreboot, коли він був учасником
|
|
||||||
проекту. Він досі працює над coreboot, і Libreboot отримує велику
|
|
||||||
користь від його роботи. Його внесок у проект coreboot і Libreboot
|
|
||||||
неоціненний.
|
|
||||||
|
|
||||||
Володимир Сербіненко
|
|
||||||
-------------------
|
|
||||||
|
|
||||||
Перенес багато thinkpad, які підтримуються в libreboot, на coreboot, а
|
|
||||||
також зробив багато виправлень у coreboot, які принесли користь проекту libreboot.
|
|
||||||
|
|
||||||
Володимир написав багато вихідного коду ініціалізації відео, який використовується різними
|
|
||||||
платформами Intel у Libreboot, під час прошивки (зараз переписаний
|
|
||||||
іншими в Ada, для libgfxinit в coreboot, але спочатку він був написаний на
|
|
||||||
C і включений безпосередньо в coreboot; libgfxinit є субмодуль третьої сторони).
|
|
||||||
|
|
||||||
Демієн Замміт
|
|
||||||
-------------
|
|
||||||
|
|
||||||
Підтримує порт coreboot Gigabyte GA-G41M-ES2L, інтегрований у
|
|
||||||
libreboot. Також працює над іншим апаратним забезпеченням на користь
|
|
||||||
проекту libreboot.
|
|
||||||
|
|
||||||
Демієн не працював безпосередньо над самим Libreboot, але він багато працював з
|
|
||||||
Лією Роу, інтегруючи патчі та нові порти плати в Libreboot на основі
|
|
||||||
попередньої роботи Демієна над coreboot.
|
|
||||||
|
|
||||||
Денис Каріклі
|
|
||||||
-------------
|
|
||||||
|
|
||||||
На основі роботи, виконаної Пітером Стюджем, Володимиром Сербіненко та іншими
|
|
||||||
в проекті coreboot, вдалось налагодити нативну ініціалізацію графіки для роботи
|
|
||||||
на ThinkPad X60, що дозволяє підтримувати її в libreboot. Денис дав
|
|
||||||
багато порад і допоміг створити проект libreboot.
|
|
||||||
|
|
||||||
Денис був наставником Лії Роу в ранні дні, коли вона заснувала проект
|
|
||||||
Libreboot. Багато прийнятих рішень, особливо щодо системи збірки
|
|
||||||
Libreboot (lbmk), були натхненні розмовами з Денисом.
|
|
||||||
|
|
||||||
Денис навчив Лію про регістри, які використовуються графічним процесором Intel для керування підсвічуванням.
|
|
||||||
В ранні дні, ноутбуки ThinkPad X60 та T60 в Libreboot не мали працюючого
|
|
||||||
контроля підсвічуванням, тому яскравість завжди була 100%. За допомогою Дениса,
|
|
||||||
Лія змогла налаштувати керування підсвічуванням шляхом зворотньої розробки
|
|
||||||
правильних значень для запису в ці регістри. На основі цього в coreboot
|
|
||||||
було написано просте виправлення; однак виправлення перезаписувало безпосередньо регістр
|
|
||||||
і не працювало з елементами керування яскравістю на основі ACPI. Інші в coreboot
|
|
||||||
пізніше вдосконалили його, змусивши елементи керування підсвічуванням на основі ACPI працювати належним чином, на основі цієї
|
|
||||||
попередньої роботи.
|
|
||||||
|
|
||||||
Джерун Квінт
|
|
||||||
------------
|
|
||||||
|
|
||||||
Додав кілька виправлень до документації libreboot, пов'язаної зі
|
|
||||||
встановленням Arch з повним дисковим шифруванням у системах libreboot.
|
|
||||||
|
|
||||||
Джошуа Гей
|
|
||||||
----------
|
|
||||||
|
|
||||||
Джошуа колишній співробітник FSF.
|
|
||||||
|
|
||||||
Джошуа допоміг із раннім заснуванням проекту Libreboot, будучи
|
|
||||||
(на той час) менеджером з ліцензування та відповідності FSF. Його роботою було
|
|
||||||
переглядати продукти, надіслані до FSF для перевірки; FSF має програму
|
|
||||||
сертифікації, під назвою *Поважає Вашу Свободу* (Respects Your Freedom), за якою FSF рекламуватиме
|
|
||||||
продукти вашої компанії, якщо вони постачаються з усім вільним програмним
|
|
||||||
забезпеченням.
|
|
||||||
|
|
||||||
Я, Лія Роу, спочатку просто продавала ноутбуки ThinkPad X60 із звичайним
|
|
||||||
coreboot, і це включало оновлення мікрокоду ЦП. У той час
|
|
||||||
я не дуже про це думала. Джошуа зв'язався зі мною, в своїх повноваженнях FSF, і спитав,
|
|
||||||
чи зацікавить мене програма RYF FSF; Я була дуже здивована, що FSF
|
|
||||||
сприйме мене серйозно, і я сказала так. Саме з цього почалася рання робота
|
|
||||||
над Libreboot. Джошуа показав мені всі проблеми з моїми продуктами, і з
|
|
||||||
цього, рішення було очевидним:
|
|
||||||
|
|
||||||
Необхідно, щоб існував проект із повністю вільною версією coreboot без будь-яких
|
|
||||||
бінарних блобів. У той час (і це актуально й сьогодні) coreboot не був
|
|
||||||
повністю вільним програмним забезпеченням і за замовчуванням постачався з двійковими блобами. Зокрема,
|
|
||||||
оновлення мікрокоду ЦП включено за замовчуванням на всіх машинах x86. Працюючи
|
|
||||||
з Джошуа, я створила повністю вільну версію coreboot.
|
|
||||||
Спочатку він не називався Libreboot, і робота була призначена виключно для моєї
|
|
||||||
компанії (на той час вона називалася Gluglug), яку просувала FSF.
|
|
||||||
|
|
||||||
Джошуа використовував свої медійні зв'язки в FSF, щоб активно рекламувати мою роботу, і
|
|
||||||
13 грудня 2013 року народився проект Libreboot (але не названий так).
|
|
||||||
Джошуа переконався, щоб всі знали, що я роблю!
|
|
||||||
|
|
||||||
Через кілька місяців було створено назву *Libreboot* і зареєстровано доменне ім'я
|
|
||||||
*libreboot.org*. У цей момент офіційно народився проект Libreboot (на початку
|
|
||||||
2014 року). Знову Джошуа надав всю можливу допомогу,
|
|
||||||
активно просуваючи проект, і навіть написав цю статтю на веб-сайті FSF
|
|
||||||
оголосивши про це:
|
|
||||||
|
|
||||||
<https://web.archive.org/web/20171222063358/https://www.fsf.org/blogs/licensing/replace-your-proprietary-bios-with-libreboot>
|
|
||||||
|
|
||||||
Ендрю Роббінс
|
|
||||||
--------------
|
|
||||||
|
|
||||||
Працював над великими частинами старої системи збірки Libreboot і пов'язаною документацією.
|
|
||||||
Ендрю приєднався до проекту Libreboot як штатний розробник у червні 2017,
|
|
||||||
до моменту свого відходу в березні 2021 року.
|
|
||||||
|
|
||||||
Я, Лія Роу, дуже вдячна Ендрю Роббінсу за його численні внески
|
|
||||||
протягом багатьох років.
|
|
||||||
|
|
||||||
Клеменс Нанні
|
|
||||||
-------------
|
|
||||||
|
|
||||||
Внесено багато виправлень і покращень у конфігурацію GRUB, яка використовується в
|
|
||||||
libreboot, а також кілька змін у системі збірки.
|
|
||||||
|
|
||||||
Ліза Марі Магінніс
|
|
||||||
-------------------
|
|
||||||
|
|
||||||
Ліза - колишній системний адміністратор Free Software Foundation. На перших днях
|
|
||||||
проекту вона давала Лії багато технічних порад. Спочатку вона створила
|
|
||||||
IRC-канал Libreboot, коли Лія не знала, як користуватися
|
|
||||||
IRC, а також передала +F статус засновника для каналу. Як системний
|
|
||||||
адміністратор FSF, роботою Лізи було підтримувати велику частину інфраструктури,
|
|
||||||
яку використовує Libreboot; на той час списки розсилки на веб-сайті Savannah
|
|
||||||
використовувалися проектом Libreboot. Коли Пол Коціалковскі був
|
|
||||||
учасником проекту в 2016 році, вона допомогла йому отримати допомогу від FSF; на той час він був
|
|
||||||
керівником проекту Replicant, який фінансував FSF, і FSF дозволив
|
|
||||||
йому використати частину цього фінансування для його роботи над Libreboot, завдяки Лізи
|
|
||||||
підтримці, коли вона працювала у FSF.
|
|
||||||
|
|
||||||
Ліза також втрутилася, коли Лія Роу пропустила виступ на LibrePlanet 2016. Лія мала
|
|
||||||
виступити з доповіддю про Libreboot, але не з'явилася вчасно. Ліза разом
|
|
||||||
із Патріком Макдермоттом (колишнім розробником Libreboot, який був присутній
|
|
||||||
на тій конференції) виступили замість Лії. Розмова ніколи не була записана, але
|
|
||||||
Фонд вільного програмного забезпечення має ці фотографії цієї розмови на веб-сайті LibrePlanet
|
|
||||||
(жінка з блакитним волоссям - Ліза, а довговолосий хлопець із вусами -
|
|
||||||
Патрік):
|
|
||||||
|
|
||||||
<http://web.archive.org/web/20170319043913/https://media.libreplanet.org/u/libreplanet/m/session-02-c-mws-png-libreplanet-2016-sessions/>
|
|
||||||
|
|
||||||
<http://web.archive.org/web/20170319043915/https://media.libreplanet.org/u/libreplanet/m/session-02-c-wide-png-libreplanet-2016-sessions/>
|
|
||||||
|
|
||||||
Цікавий факт: Патрік також є провідним розробником ProteanOS, проекту вбудованої
|
|
||||||
ОС, схваленого FSF: <http://proteanos.com/> (використовує BusyBox і Linux-libre)
|
|
||||||
|
|
||||||
Лія Роу провела *2* семінари LibrePlanet; один у 2015 році та інший у 2016 році,
|
|
||||||
відвідуючи Бостон, Массачусетс, США в обох випадках для участі в цих конференціях. Ці
|
|
||||||
семінари стосувалися встановлення Libreboot. Люди приходили на обидва семінари, щоб
|
|
||||||
встановити Libreboot на свої комп'ютери. Як системний адміністратор FSF, на той час,
|
|
||||||
Ліза забезпечила всю інфраструктуру та обладнання, яке використовувалося на цих семінарах.
|
|
||||||
Без її допомоги ці майстер-класи були б неможливими.
|
|
||||||
|
|
||||||
Коли материнська плата ASUS KGPE-D16 (серверна плата високого класу) була перенесена на Libreboot,
|
|
||||||
Лія, працюючи з Тімоті Пірсоном (той, хто її переніс),
|
|
||||||
приблизно в середині 2016 року поділилася з Лізою виправленнями, в основному виправленнями raminit, щоб отримати плату, яка працює в офісах FSF. Ця робота
|
|
||||||
зрештою призвела до чудового досягнення:
|
|
||||||
|
|
||||||
Веб-сайти FSF і GNU тепер працюють на, з встановленим Libreboot,
|
|
||||||
заснованих на ASUS KGPE-D16 серверах, на повністю вільному GNU+Linux дистрибутиві. Це
|
|
||||||
означає, що FSF тепер має повну свободу програмного забезпечення для своєї
|
|
||||||
інфраструктури хостингу.
|
|
||||||
|
|
||||||
FSF також надає доступ до цієї інфраструктури для багатьох інших проектів
|
|
||||||
(крім проектів GNU).
|
|
||||||
|
|
||||||
Ліза була сильною прихильницею Libreboot на перших днях проекту,
|
|
||||||
і її внесок був неоціненним. Я, Лія Роу, у боргу перед нею.
|
|
||||||
|
|
||||||
Маркус Мьоллер
|
|
||||||
--------------
|
|
||||||
|
|
||||||
Зробив логотип libreboot.
|
|
||||||
|
|
||||||
Nicholas Chin
|
|
||||||
-------------
|
|
||||||
|
|
||||||
[Ported Dell Latitude E6400 to Libreboot](news/e6400.md).
|
|
||||||
|
|
||||||
Патрік "П. Дж." Макдермотт
|
|
||||||
---------------------------
|
|
||||||
|
|
||||||
Патрік також провів багато досліджень і написав розділ поширених запитань libreboot,
|
|
||||||
пов'язаний із [Intel Management Engine](../faq.md#intelme), а також зробив кілька покращень у
|
|
||||||
системі збірки libreboot. **Колишній супроводжувач проекту
|
|
||||||
libreboot.**
|
|
||||||
|
|
||||||
У 2016 році Лія Роу провела семінар зі встановлення Libreboot на конференції FSF
|
|
||||||
LibrePlanet. Працюючи разом з Лією, Патрік допомагав вести семінар
|
|
||||||
та допомагав установлювати Libreboot на комп'ютери людей.
|
|
||||||
|
|
||||||
Пітер Стюдж
|
|
||||||
-----------
|
|
||||||
|
|
||||||
Допоміг написати [розділ поширених запитань про DMA](../faq.md#hddssd-firmware), та надав
|
|
||||||
загальні поради на перших днях проекту. У той час Пітер був розробником coreboot
|
|
||||||
і головним розробником проекту *libusb* (який flashrom
|
|
||||||
активно використовує).
|
|
||||||
|
|
||||||
Пітер також написав утиліту *bucts*, яка використовується для встановлення біта Top Swap
|
|
||||||
(TS) для керування резервним копіюванням (BUC) на ноутбуках i945, таких як ThinkPad X60/T60, яка є корисною для
|
|
||||||
обхідного шляху для прошивки Libreboot без використання зовнішнього обладнання; на цій машині,
|
|
||||||
з Lenovo BIOS, можна перепрошити все, крім головного завантажувального
|
|
||||||
блоку, але платформи Intel мають 2 завантажувальні блоки, і ви вказуєте, який із них
|
|
||||||
використовувати, встановленням біта TS. Потім ви завантажуєтеся лише з одним прошитим завантажувальним блоком
|
|
||||||
(завантажувальним блоком проекту coreboot на цій машині), а потім скидаєте
|
|
||||||
bucts перед повторною прошивкою ROM, щоб прошити основний завантажувальний блок. Libreboot
|
|
||||||
розміщує копію його роботи, оскільки його веб-сайт, на якому розміщено bucts,
|
|
||||||
більше не відповідає.
|
|
||||||
|
|
||||||
Пол Коціалковський
|
|
||||||
-----------------
|
|
||||||
|
|
||||||
Переніс ноутбуки Chromebook на основі ARM (Rockchip RK3288 SoC) до
|
|
||||||
libreboot. Також один із головних розробників [Replicant](http://www.replicant.us/).
|
|
||||||
|
|
||||||
Пол Менцель
|
|
||||||
-----------
|
|
||||||
|
|
||||||
Дослідив та виправив помилку в coreboot на ThinkPad X60/T60, яку виявляло
|
|
||||||
ядро Linux 3.12 і новіших версій, через яку прискорення 3D не
|
|
||||||
працювало, а відео загалом ставало нестабільним. Проблема полягала в тому, що
|
|
||||||
coreboot під час ініціалізації відеочіпсета Intel, відображав *GTT Stolen Memory* в
|
|
||||||
не тому місці, оскільки код базувався на коді ядра, а в ядрі Linux
|
|
||||||
була така сама помилка. Коли Linux це виправив, він виявив ту саму помилку в coreboot.
|
|
||||||
|
|
||||||
Пол працював над цим із Libreboot,
|
|
||||||
періодично надсилаючи патчі для тестування, доки помилку не було виправлено
|
|
||||||
в coreboot, а потім допоміг ій інтегрувати виправлення в libreboot.
|
|
||||||
|
|
||||||
Riku Viitanen
|
|
||||||
-------------
|
|
||||||
|
|
||||||
Added support for HP Elite 8200 SFF desktop PC to Libreboot. You can read
|
|
||||||
about this in the hardware page:
|
|
||||||
|
|
||||||
[HP Elite 8200 SFF](docs/hardware/hp8200sff.md)
|
|
||||||
|
|
||||||
Стів Шентон
|
|
||||||
-------------
|
|
||||||
|
|
||||||
Стів виконав першу роботу зі зворотньої розробки Intel Flash Descriptor, який використовується
|
|
||||||
на машинах ICH9M, таких як ThinkPad X200. Він створив структуру C, що визначає (використовуючи
|
|
||||||
бітові поля в C) цю область дескриптора. За допомогою деяких хитрих трюків він зміг
|
|
||||||
виявити існування біта в дескрипторі для *вимкнення* Intel ME
|
|
||||||
(management engine) на цих платформах.
|
|
||||||
|
|
||||||
Його початкове підтвердження концепції визначило лише дескриптор, і зробило би це:
|
|
||||||
|
|
||||||
* Читання дескриптора за замовчуванням і регіонів GbE з ROM Lenovo X200 (прошивка
|
|
||||||
за замовчуванням, не coreboot)
|
|
||||||
* Вимкнення ME, встановивши 2 біти в дескрипторі
|
|
||||||
* Вимкнення регіона ME
|
|
||||||
* Переміщення дескриптора+GbE (загалом 12КБ) поруч
|
|
||||||
* Виділення решти флеш-пам'яті для регіону BIOS
|
|
||||||
* На основі цього створено 12КБ регіон дескриптор+область GBE для вставки
|
|
||||||
в образ ROM coreboot.
|
|
||||||
|
|
||||||
У перші дні, до того, як Libreboot підтримував платформи GM45+ICH9M, такі як
|
|
||||||
ThinkPad X200/T400, ви могли використовувати ці машини, але щоб уникнути
|
|
||||||
Intel ME, вам доводилося виконувати прошивку без області дескриптора. У ті часи це працювало нормально,
|
|
||||||
тому що ME обробляв лише TPM та AMT на цих машинах, і система
|
|
||||||
працювала нормально, але Intel Flash Descriptor також обробляє область Intel GbE NVM
|
|
||||||
у флеш-пам'яті, яка використовується для інтерфейсу Intel Gigabit Ethernet.
|
|
||||||
|
|
||||||
Отже, ви або мали Intel ME, або не підтримували ethernet. Стів зрозумів, як
|
|
||||||
вимкнути Intel ME за допомогою 2 бітів перемикання в дескрипторі, а також як видалити область
|
|
||||||
Intel ME з флеш-пам'яті.
|
|
||||||
|
|
||||||
Ґрунтуючись на його дослідженні, я, Лія Роу, працюючи разом зі Стівом, також виконала зворотню розробку
|
|
||||||
області Intel GbE NVM (енергонезалежна пам'ять) у
|
|
||||||
завантажувальній флеш-пам'яті. Цей регіон визначає параметри конфігурації для вбудованої мережевої карти Intel
|
|
||||||
GbE, якщо присутня.
|
|
||||||
|
|
||||||
На основі цього я змогла взяти початкове підтвердження концепції та написати
|
|
||||||
утиліту `ich9gen`, яка генерує Intel Flash Descriptor та регіон GbE NVM,
|
|
||||||
з нуля, без визначення регіону Intel ME. Саме цей інструмент,
|
|
||||||
інструмент `ich9gen`, використовує Libreboot для надання образів ROM для GM45+ICH9M
|
|
||||||
платформ (таких як ThinkPad X200/T400/T500/W500), із повнофункціональним
|
|
||||||
дескриптором та функціональним Gigabit Ethernet, але *без* необхідності мікропрограми Intel
|
|
||||||
Management Engine (ME), що робить ці машини *вільними* (ME
|
|
||||||
повністю вимкнено, коли ви використовуєте образ дескриптора+gbe, створене `ich9gen`).
|
|
||||||
|
|
||||||
З *моїм* інструментом `ich9gen` (інструмент Стіва називався `ich9deblob`), вам більше
|
|
||||||
не потрібен був дамп оригінальної мікропрограми Lenovo BIOS! Я не могла би написати цей інструмент
|
|
||||||
без первинного підтвердження концепції Стіва. Я працювала з ним
|
|
||||||
протягом багатьох місяців. Вся GM45+ICH9M підтримка (X200, T400 і так далі) в
|
|
||||||
Libreboot стала можливою завдяки його роботі у 2014 році.
|
|
||||||
|
|
||||||
Тімоті Пірсон
|
|
||||||
---------------
|
|
||||||
|
|
||||||
Перенес плату ASUS KGPE-D16 до coreboot для компанії Raptor
|
|
||||||
Engineering, генеральним директором якої є Тімоті.
|
|
||||||
Тімоті підтримує цей код у coreboot, допомогаючи проекту,
|
|
||||||
з його інтеграцією з libreboot. Контактні
|
|
||||||
дані цієї людини є на сайті raptor.
|
|
||||||
|
|
||||||
**Підтримку D16 було припинено 19 листопада 2022 року. Ви все ще можете використовувати
|
|
||||||
старіші версії Libreboot, і старіші випуски.**
|
|
||||||
|
|
||||||
Swift Geek
|
|
||||||
----------
|
|
||||||
|
|
||||||
Додав патч для ich9gen для створення дескрипторів розміром 16MiB.
|
|
||||||
|
|
||||||
Після цього Swift Geek повільно почав долучатися, поки не став розробником на повний
|
|
||||||
робочий день. Внески Swift Geek насправді ніколи не були у формі *коду*,
|
|
||||||
але те, що йому не вистачало в коді, він компенсував чудовою підтримкою як для користувачів,
|
|
||||||
так і для інших розробників, допомагаючи іншим дізнатися більше про технології на
|
|
||||||
низькому рівні.
|
|
||||||
|
|
||||||
Коли Swift Geek був учасником проекту, його роль здебільшого полягала в
|
|
||||||
наданні підтримки користувачам (на каналі IRC) і проведенні досліджень. Swift Geek знає
|
|
||||||
багато про апаратне забезпечення. Swift Geek також зробив деяку апстрім розробку GRUB.
|
|
||||||
|
|
||||||
Swift Geek неодноразово надавав технічні поради Лії Роу
|
|
||||||
та допоміг їй покращити її навички паяння, а також навчив її
|
|
||||||
деяким навичкам ремонту, до того моменту, коли вона тепер може виправляти більшість несправностей
|
|
||||||
на материнських платах ThinkPad (під час перегляду схем та бордв'ю).
|
|
||||||
|
|
||||||
Swiftgeek залишив проект у березні 2021 року. Я, Лія Роу, бажаю його всього найкращого в його
|
|
||||||
починаннях і дуже вдячна за його численні внески протягом багатьох
|
|
||||||
років.
|
|
||||||
|
|
||||||
vitali64
|
|
||||||
--------
|
|
||||||
|
|
||||||
Додав підтримку cstate 3 на macbook21, що забезпечує тривалий термін служби батареї
|
|
||||||
та нижчу температуру процесора під час простою. vitali64 на irc
|
|
|
@ -25,6 +25,28 @@ libreboot from the available source code.
|
||||||
The following document describes how `lbmk` works, and how you can make changes
|
The following document describes how `lbmk` works, and how you can make changes
|
||||||
to it: [libreboot maintenance manual](../maintain/)
|
to it: [libreboot maintenance manual](../maintain/)
|
||||||
|
|
||||||
|
Multi-threaded builds
|
||||||
|
=====================
|
||||||
|
|
||||||
|
Libreboot's build system defaults to a single build thread, but you can change
|
||||||
|
it by doing e.g.
|
||||||
|
|
||||||
|
export XBMK_THREADS=4
|
||||||
|
|
||||||
|
This would make lbmk run on 4 threads.
|
||||||
|
|
||||||
|
More specifically: when compiling source trees via `script/trees`, `-jTHREADS`
|
||||||
|
is passed, where THREADS is the number of threads. This is also set when running
|
||||||
|
xz commands for compression, using the `-t` option.
|
||||||
|
|
||||||
|
Environmental variables
|
||||||
|
=======================
|
||||||
|
|
||||||
|
Please read about environmental variables in [the build
|
||||||
|
instructions](../maintain/), before running lbmk. You should set
|
||||||
|
your variables accordingly, though you do not technically need to; some
|
||||||
|
of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
|
||||||
|
|
||||||
Sources
|
Sources
|
||||||
=======
|
=======
|
||||||
|
|
||||||
|
@ -93,6 +115,13 @@ Actual development/testing is always done using lbmk directly, and this
|
||||||
includes when building from source. Here are some instructions to get you
|
includes when building from source. Here are some instructions to get you
|
||||||
started:
|
started:
|
||||||
|
|
||||||
|
Zero..st, check time/date
|
||||||
|
-------------------------
|
||||||
|
|
||||||
|
Make sure date/hwclock report the correct time and date on your system,
|
||||||
|
because parts of the build process download from HTTPS servers and wrong
|
||||||
|
time or date can cause connections to be dropped during negotiation.
|
||||||
|
|
||||||
First, install build dependencies
|
First, install build dependencies
|
||||||
---------------------------------
|
---------------------------------
|
||||||
|
|
||||||
|
@ -174,118 +203,3 @@ example want to modify a config, e.g.:
|
||||||
|
|
||||||
Or perhaps add a new board! The maintenance manual will teach you how the
|
Or perhaps add a new board! The maintenance manual will teach you how the
|
||||||
Libreboot build system (lbmk) works!
|
Libreboot build system (lbmk) works!
|
||||||
|
|
||||||
Post-compilation steps
|
|
||||||
======================
|
|
||||||
|
|
||||||
So you compiled your Libreboot image? Congratulations!
|
|
||||||
|
|
||||||
Before you flash, please make sure that you *dumped* two copies of the original
|
|
||||||
firmware just in case (verifying the hashes of each dump, to ensure that they
|
|
||||||
match), using the `-r` option in flashrom.
|
|
||||||
|
|
||||||
There are some additional considerations:
|
|
||||||
|
|
||||||
Regarding binary blobs
|
|
||||||
----------------------
|
|
||||||
|
|
||||||
Firstly, you should read the Libreboot *Binary Blob Reduction Policy*:
|
|
||||||
<https://libreboot.org/news/policy.html>
|
|
||||||
|
|
||||||
A lot of mainboards in Libreboot will boot entirely with free software,
|
|
||||||
but there are certain newer mainboards supported in Libreboot
|
|
||||||
that need binary blobs added to them, mostly for minor initialisation tasks.
|
|
||||||
|
|
||||||
They are *automatically* inserted during the build process, but then deleted
|
|
||||||
during the *release* process; images built directly from lbmk can be flashed
|
|
||||||
without further modification, but release images need to have these files
|
|
||||||
re-inserted (e.g. KBC1126 EC firmware on HP EliteBooks). Please read this page
|
|
||||||
for context:
|
|
||||||
<https://libreboot.org/docs/install/ivy_has_common.html>
|
|
||||||
|
|
||||||
The scripts under directory `script/update/vendor/` are the ones that do this.
|
|
||||||
Specifically, `script/vendor/download`. The benefit of this is that you
|
|
||||||
do not need to extract anything from the original vendor image (e.g. Lenovo
|
|
||||||
UEFI image).
|
|
||||||
|
|
||||||
To know if this was performed on your board, you can read the Freedom Status
|
|
||||||
page which documents which files are used (if any), on which boards:
|
|
||||||
<https://libreboot.org/freedom-status.html>
|
|
||||||
|
|
||||||
There are specific files that you must know about, so they will be covered
|
|
||||||
next:
|
|
||||||
|
|
||||||
### Regarding CPU microcode
|
|
||||||
|
|
||||||
Libreboot release archives provide ROMs with or without CPU microcode updates,
|
|
||||||
but the newest revisions of lbmk (from `lbmk.git`) *only* build ROM images that
|
|
||||||
contain microcode updates, by default. Libreboot's build system contains a script
|
|
||||||
that will generate release archives, and this is used to provide Libreboot
|
|
||||||
releases; this script is what provides the images with microcode removed,
|
|
||||||
alongside the default ones generated by lbmk during the build.
|
|
||||||
|
|
||||||
Please read:
|
|
||||||
<https://libreboot.org/freedom-status.html#cpu-microcode>
|
|
||||||
|
|
||||||
The linked page has info, and includes instructions about how to manually remove
|
|
||||||
them, if you wish to do so. Removal of CPU microcode updates (on Intel/AMD
|
|
||||||
processors) will result in unpredictable security/stability issues, so beware.
|
|
||||||
|
|
||||||
Further context is provided in the Libreboot *Binary Blob Reduction Policy*:
|
|
||||||
<https://libreboot.org/news/policy.html>
|
|
||||||
|
|
||||||
We *recommend* that you do not delete these updates, but you have the freedom
|
|
||||||
to choose. Additionally: we have only tested certain mainboards under this
|
|
||||||
configuration. To know which ones they are, do this in `lbmk.git`:
|
|
||||||
|
|
||||||
cd config/coreboot/
|
|
||||||
git grep microcode_required
|
|
||||||
|
|
||||||
Example entry:
|
|
||||||
|
|
||||||
e6400_4mb/target.cfg:microcode_required="n"
|
|
||||||
|
|
||||||
If it says `="n"`, that means it has been tested. That *does not* mean it will
|
|
||||||
be stable, it's just that we're reasonably sure it will at least *boot* most
|
|
||||||
of the time, but you should expect random instability e.g. kernel panics.
|
|
||||||
|
|
||||||
If a given mainboard *excludes* `microcode_required` in `target.cfg`, or if
|
|
||||||
it says `microcode_required="y"`, then the release ROMs will only contain
|
|
||||||
microcode updates. Manual removal (as above) is still possible, but it has
|
|
||||||
not been tested and is not recommended.
|
|
||||||
|
|
||||||
NOTE: ARM-based chromebooks (that Libreboot supports) don't use microcode at
|
|
||||||
all. This section is only revelant for x86 (Intel/AMD).
|
|
||||||
|
|
||||||
### Regarding Nvidia GPU ROM (Dell Latitude E6400)
|
|
||||||
|
|
||||||
Dell Latitude E6400 comes in two variants: Nvidia graphics, or Intel graphics.
|
|
||||||
More information is available on the page:
|
|
||||||
<https://libreboot.org/docs/hardware/e6400.html>
|
|
||||||
|
|
||||||
The intel graphics model can boot with coreboot's native video initialisation,
|
|
||||||
which is free software. The *Nvidia* model (comes with Nvidia GPU) requires
|
|
||||||
proprietary code called a *VGA Option ROM* to initialise the video display in
|
|
||||||
early boot.
|
|
||||||
|
|
||||||
Libreboot automatically fetches this during the build process, inserting it into
|
|
||||||
the very same ROM image that can be flashed on either model, but the VGA ROM
|
|
||||||
will only be *executed* if you actually have the Nvidia *GPU* on your board.
|
|
||||||
|
|
||||||
**ALSO: Libreboot 20230625 did not support Nvidia models at all (only Intel).
|
|
||||||
In releases, only Libreboot 20231021 and newer will support it.**
|
|
||||||
|
|
||||||
Pre-built ROM images from release archives since 20231021 will *not* contain
|
|
||||||
this file by default, but it will be present if you compiled directly from lbmk.
|
|
||||||
To remove it, do this:
|
|
||||||
|
|
||||||
./cbutils/default/cbfstool libreboot.rom remove -n pci10de,06eb.rom
|
|
||||||
|
|
||||||
The cbfstool binary was compiled when your image (target `e6400_4mb`) was
|
|
||||||
compiled, which can alter the file system within your coreboot image.
|
|
||||||
|
|
||||||
Obviously, removing this VGA ROM will mean that the ROM image will only work
|
|
||||||
correctly on Intel GPU variants of E6400, but you probably knew that already!
|
|
||||||
|
|
||||||
(If you're using a release archive instead, you can re-insert the VGA ROM by
|
|
||||||
following [these instructions](../install/ivy_has_common.md))
|
|
||||||
|
|
|
@ -35,6 +35,55 @@ libreboot з доступного джерельного коду.
|
||||||
Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни
|
Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни
|
||||||
до нього: [керівництво обслуговування libreboot](../maintain/)
|
до нього: [керівництво обслуговування libreboot](../maintain/)
|
||||||
|
|
||||||
|
Release status
|
||||||
|
==============
|
||||||
|
|
||||||
|
Information about status will be reported during builds; if a board is
|
||||||
|
marked as stable, the build proceeds without further input. If the board is
|
||||||
|
marked anything other, a warning appears asking if you wish to proceed; to
|
||||||
|
disable these warnings, do this before building (not recommended):
|
||||||
|
|
||||||
|
export LBMK_STATUS=n
|
||||||
|
|
||||||
|
In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`.
|
||||||
|
The "unstable" marking means that the board boots mostly/entirely reliably
|
||||||
|
annd should be safe to use, but may have a few issues, but nothing which would,
|
||||||
|
for example, cause safety issues e.g. thermal, data reliability etc.
|
||||||
|
|
||||||
|
The `broken` setting means that a given board will likely brick if flashed.
|
||||||
|
The `untested` setting means untested.
|
||||||
|
|
||||||
|
Release status is always set with regards to the current lbmk revision, on
|
||||||
|
the theory that the current revision is being used to generate a full release.
|
||||||
|
The setting is decided on a board-by-board basis, taking its various quirks
|
||||||
|
and idiosynrasies into account.
|
||||||
|
|
||||||
|
Multi-threaded builds
|
||||||
|
=====================
|
||||||
|
|
||||||
|
Libreboot's build system defaults to a single build thread, but you can change
|
||||||
|
it by doing e.g.
|
||||||
|
|
||||||
|
export LBMK_THREADS=4
|
||||||
|
|
||||||
|
This would make lbmk run on 4 threads.
|
||||||
|
|
||||||
|
Environmental variables
|
||||||
|
=======================
|
||||||
|
|
||||||
|
Please read about environmental variables in [the build
|
||||||
|
instructions](../maintain/), before running lbmk. You should set
|
||||||
|
your variables accordingly, though you do not technically need to; some
|
||||||
|
of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
|
||||||
|
|
||||||
|
Environmental variables
|
||||||
|
=======================
|
||||||
|
|
||||||
|
Please read about environmental variables in [the build
|
||||||
|
instructions](../maintain/), before running lbmk. You should set
|
||||||
|
your variables accordingly, though you do not technically need to; some
|
||||||
|
of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
|
||||||
|
|
||||||
Git
|
Git
|
||||||
===
|
===
|
||||||
|
|
||||||
|
@ -61,6 +110,13 @@ Python
|
||||||
Python2 не використовується lbmk або будь-чим, що завантажується в якості модулів. Ви
|
Python2 не використовується lbmk або будь-чим, що завантажується в якості модулів. Ви
|
||||||
маєте переконатись, що команда `python` виконує python 3 на вашій системі.
|
маєте переконатись, що команда `python` виконує python 3 на вашій системі.
|
||||||
|
|
||||||
|
Zero..st, check time/date
|
||||||
|
-------------------------
|
||||||
|
|
||||||
|
Make sure date/hwclock report the correct time and date on your system,
|
||||||
|
because parts of the build process download from HTTPS servers and wrong
|
||||||
|
time or date can cause connections to be dropped during negotiation.
|
||||||
|
|
||||||
Побудова з джерельного коду
|
Побудова з джерельного коду
|
||||||
============================
|
============================
|
||||||
|
|
||||||
|
|
|
@ -4,7 +4,7 @@ title: Intel D510MO and D410PT desktop boards
|
||||||
|
|
||||||
<div class="specs">
|
<div class="specs">
|
||||||
<center>
|
<center>
|
||||||
![Intel D510MO]()
|
Intel D510MO
|
||||||
</center>
|
</center>
|
||||||
|
|
||||||
| ***Specifications*** | |
|
| ***Specifications*** | |
|
||||||
|
|
|
@ -0,0 +1,240 @@
|
||||||
|
---
|
||||||
|
title: Dell OptiPlex 9020 SFF/MT (and 7020), and XE2 MT/SFF
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**NOTE: Dell XE2 MT/SFF are also known to work, using the 9020 images. Same
|
||||||
|
motherboards as the 9020 and 7020.**
|
||||||
|
|
||||||
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020sff.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff.jpg" /></span>
|
||||||
|
<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020sff_ports.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_ports.jpg" /></span>
|
||||||
|
<br/>
|
||||||
|
<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020sff_inside.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_inside.jpg" /></span>
|
||||||
|
<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020mt.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020mt.jpg" /></span>
|
||||||
|
<br/>
|
||||||
|
<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020mt_ports.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020mt_ports.jpg" /></span>
|
||||||
|
<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020mt_inside.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020mt_inside.jpg" /></span>
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | Dell |
|
||||||
|
| **Name** | OptiPlex 9020 SFF/MT |
|
||||||
|
| **Variants** | OptiPlex 9020 SFF/MT |
|
||||||
|
| **Chipset** | Intel Q87 Express |
|
||||||
|
| **CPU** | Intel Haswell |
|
||||||
|
| **Graphics** | Intel HD Graphics |
|
||||||
|
| **Memory** | DDR3 DIMMs (max 32GB, 4x8GB) |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **Original boot firmware** | Dell UEFI firmware |
|
||||||
|
| **Intel ME/AMD PSP** | Present. Can be disabled with me_cleaner. |
|
||||||
|
| **Flash chip** | 2x SOIC-8, 12MiB (8+4) (96Mbit) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
?: UNKNOWN AT THIS TIME
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | W+ |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Display (discrete CPU, SeaBIOS payload only)** | W* |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|----------------------------|-----------|
|
||||||
|
| **GRUB (libgfxinit only)** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Unavailable in Libreboot 20240126 or earlier. You must [compile from
|
||||||
|
source](../build/), or use a version newer than Libreboot 20240126**
|
||||||
|
|
||||||
|
Official information about this machine can be found here:
|
||||||
|
<https://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/optiplex-9020-micro-technical-spec-sheet.pdf>
|
||||||
|
|
||||||
|
Buy Libreboot preinstalled
|
||||||
|
======================
|
||||||
|
|
||||||
|
You can buy this machine professionally serviced, with Libreboot preinstalled
|
||||||
|
and your choice of Linux/BSD system. Many upgrades are also available. See:
|
||||||
|
|
||||||
|
<https://minifree.org/product/libreboot-9020/>
|
||||||
|
|
||||||
|
Sales are conducted to provide funding for the Libreboot project. Leah Rowe
|
||||||
|
who runs Minifree, is also Libreboot's founder and lead developer.
|
||||||
|
|
||||||
|
Patch
|
||||||
|
=====
|
||||||
|
|
||||||
|
Mate Kukri is the author of the original coreboot port. Thanks go to Kukri.
|
||||||
|
Kukri's patch is here:
|
||||||
|
|
||||||
|
<https://review.coreboot.org/c/coreboot/+/55232/31>
|
||||||
|
|
||||||
|
This patch, at this revision (patchset 31), is what Libreboot uses for this
|
||||||
|
port.
|
||||||
|
|
||||||
|
QUBES: how to get it working
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
Qubes requires IOMMU to be turned on. Please now read the next section.
|
||||||
|
Qubes *WILL* work, if you configure Libreboot as directed below, but otherwise
|
||||||
|
it will fail by default. This is because Libreboot *disables the IOMMU by
|
||||||
|
default*, on this board.
|
||||||
|
|
||||||
|
Graphics cards and IOMMU
|
||||||
|
--------------
|
||||||
|
|
||||||
|
IOMMU is buggy for some reason (we don't know why yet), when you plug in
|
||||||
|
a graphics card. The graphics card simply won't work. On some of them,
|
||||||
|
you can use the console but as soon as you start xorg, it will just b0rk.
|
||||||
|
|
||||||
|
Current Libreboot revisions *disable IOMMU by default*, on this board. The
|
||||||
|
coreboot code for initialising IOMMU was modified by the Libreboot project, to
|
||||||
|
make it a toggle. IOMMU works fine if you use only Intel graphics.
|
||||||
|
|
||||||
|
The way coreboot works is this: if vt-d is present on the CPU, it enables an
|
||||||
|
IOMMU, and only if vt-d is present. This is still the behaviour in Libreboot,
|
||||||
|
but Libreboot adds an additional check: if `iommu` is not set in nvram, it
|
||||||
|
defaults to on, but if it's set to disabled, then IOMMU is not initialised.
|
||||||
|
|
||||||
|
On all other Haswell boards, LIbreboot enables IOMMU by default. To enable
|
||||||
|
it on the 9020, do this on your ROM:
|
||||||
|
|
||||||
|
nvramtool -C libreboot.rom -w iommu=Enable
|
||||||
|
|
||||||
|
Then flash the ROM image. You can find nvram
|
||||||
|
under `src/coreboot/default/util/nvramtool`. Do this in lbmk if you don't
|
||||||
|
already havse `src/coreboot/default/`:
|
||||||
|
|
||||||
|
./update trees -f coreboot default
|
||||||
|
|
||||||
|
Then do this:
|
||||||
|
|
||||||
|
make -C src/coreboot/default/util/nvramtool
|
||||||
|
|
||||||
|
The binary `nvramtool` will then live in that directory. More information
|
||||||
|
available in [Libreboot build instructions](../build/). Information about
|
||||||
|
dumping/flashing the ROM can be found
|
||||||
|
in [Libreboot flashing instructions](../install/)
|
||||||
|
and [Libreboot external flashing instructions](../install/spi.md).
|
||||||
|
|
||||||
|
NOTE: If IOMMU is enabled, you can still use a graphics card, but you must
|
||||||
|
pass this on the Linux cmdline paramaters: `iommu=off`
|
||||||
|
|
||||||
|
NOTE2: Libreboot uses a *static option table* on all boards that have nvram,
|
||||||
|
which is why you must use the `-C` option on your ROM, to change the static
|
||||||
|
table that is baked into it.
|
||||||
|
|
||||||
|
Here is an example of the type of errors we got when testing graphics cards
|
||||||
|
with IOMMU enabled:
|
||||||
|
|
||||||
|
<https://av.vimuser.org/error.jpg>
|
||||||
|
|
||||||
|
Make sure to configure your image accordingly.
|
||||||
|
|
||||||
|
7020 compatibility
|
||||||
|
------------------
|
||||||
|
|
||||||
|
7020/9020 MT each have the same motherboard. Flash the 9020 ROM from Libreboot
|
||||||
|
on your 7020, and it will work.
|
||||||
|
|
||||||
|
Ditto 7020/9020 SFF, it's the same motherboard. However, Libreboot provides
|
||||||
|
separate targets for MT and SFF.
|
||||||
|
|
||||||
|
Build ROM image from source
|
||||||
|
---------------------------
|
||||||
|
|
||||||
|
For the MT variant (7020 MT and 9020 MT):
|
||||||
|
|
||||||
|
./build roms dell9020mt_12mb
|
||||||
|
|
||||||
|
For the SFF variant (7020 SFF and 9020 SFF):
|
||||||
|
|
||||||
|
./build roms dell9020sff_12mb
|
||||||
|
|
||||||
|
It is important that you choose the right one. The MT variant is the full
|
||||||
|
MTX tower.
|
||||||
|
|
||||||
|
Installation
|
||||||
|
============
|
||||||
|
|
||||||
|
Insert binary files
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
If you're using a release ROM, please ensure that you've inserted extra firmware
|
||||||
|
required refer to the [guide](../install/ivy_has_common.md) for that. (failure
|
||||||
|
to adhere to this advice will result in a bricked machine)
|
||||||
|
|
||||||
|
Libreboot's build system automatically downloads and processes these files if
|
||||||
|
you build Libreboot from source, but the same logic that it uses must be re-run
|
||||||
|
if you're using a release image.
|
||||||
|
|
||||||
|
Set MAC address
|
||||||
|
---------------
|
||||||
|
|
||||||
|
This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
|
||||||
|
region. As such, release/build ROMs will contain the same MAC address. To
|
||||||
|
change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
|
||||||
|
|
||||||
|
Flash a ROM image (software)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
If you're already running Libreboot, and you don't have flash protection
|
||||||
|
turned on, [internal flashing](../install/) is possible.
|
||||||
|
|
||||||
|
Internal flashing can also be done with the original Dell BIOS, if the
|
||||||
|
SERVICE_MODE jumper near the PCIe slots is installed. Before flashing,
|
||||||
|
|
||||||
|
rmmod spi-intel-platform
|
||||||
|
|
||||||
|
needs to be run to prevent errors. Once Libreboot is installed, the
|
||||||
|
SERVICE_MODE jumper can be removed.
|
||||||
|
|
||||||
|
**Note: The Dell BIOS can write EFI variables to flash when shutting
|
||||||
|
down, which could corrupt the newly flashed Libreboot ROM and render
|
||||||
|
the system unusable. To prevent this, after flashing internally from
|
||||||
|
the original Dell BIOS, remove power from the computer instead of
|
||||||
|
shutting it down normally. It's recommended to use a live USB instead
|
||||||
|
of the internal drive to prevent potential filesystem corruption.**
|
||||||
|
|
||||||
|
Flash a ROM image (hardware)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
**REMOVE all power sources and connectors from the machine, before doing this.
|
||||||
|
This is to prevent short circuiting and power surges while flashing.**
|
||||||
|
|
||||||
|
For general information, please refer to [25xx NOR flash
|
||||||
|
instructions](../install/spi.md) - that page refers to use of socketed flash.
|
||||||
|
|
||||||
|
There are two SOIC-8 chips. You can split up your 12MB ROM image
|
||||||
|
like so:
|
||||||
|
|
||||||
|
dd if=libreboot.rom of=4mb.rom bs=1M skip=8
|
||||||
|
dd if=libreboot.rom of=8mb.rom bs=1M count=8
|
||||||
|
|
||||||
|
The side cover comes off easily, and you can find the flash ICs next to the RAM.
|
||||||
|
|
||||||
|
Here's the SOIC8 ICs being flashed:
|
||||||
|
|
||||||
|
<img tabindex=1 alt="SOIC8 flash IC on 9020 SFF" style="max-width:35%" src="https://av.libreboot.org/9020/9020sff_flash1.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_flash1.jpg" /></span>
|
||||||
|
<img tabindex=1 alt="SOIC8 flash IC on 9020 SFF" style="max-width:35%" src="https://av.libreboot.org/9020/9020sff_flash2.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_flash2.jpg" /></span>
|
||||||
|
|
||||||
|
Enjoy!
|
|
@ -0,0 +1,52 @@
|
||||||
|
---
|
||||||
|
title: Dell Latitude thermal throttling
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
On some Dell Latitude laptops, you may encounter random shutdowns on
|
||||||
|
heavy load. We believe this is because the SMSC EC is overly conservative
|
||||||
|
by default; it is in charge of handling thermals and fan control on this
|
||||||
|
machine. Our theory is that coreboot needs to write certain EC commands
|
||||||
|
to allow higher temperatures; please read:
|
||||||
|
|
||||||
|
<https://codeberg.org/libreboot/lbmk/issues/202>
|
||||||
|
|
||||||
|
Basically, what you need to do is:
|
||||||
|
|
||||||
|
* Use high quality thermal paste (don't use the same dried up paste that the
|
||||||
|
laptop came with, if you bought it on ebay for example). Arctic MX-6 is good.
|
||||||
|
* Check that the fan works reliably
|
||||||
|
|
||||||
|
Also: the `intel_pstate` driver can be used to artifically cap CPU speed. See:
|
||||||
|
|
||||||
|
<https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html>
|
||||||
|
|
||||||
|
When you use this machine, it is recommended that you cap the CPU speed once
|
||||||
|
you've booted into Linux. Set it to something like 50% at first. Then run a
|
||||||
|
stress test, for example:
|
||||||
|
|
||||||
|
stress -c x
|
||||||
|
|
||||||
|
Where `x` is the number of CPU cores, e.g. 2. Monitor the temperatures using
|
||||||
|
something like `xsensors`, making sure the CPU doesn't exceed 80c temperature.
|
||||||
|
|
||||||
|
You can also monitor CPU speeds in Linux like so:
|
||||||
|
|
||||||
|
watch -n .2 grep MHz /proc/cpuinfo
|
||||||
|
|
||||||
|
This will let you know what speed you're at. You can use this to determine
|
||||||
|
whether the `intel_pstate` driver is working. How to cap speed to 50 percent, as
|
||||||
|
in the above example:
|
||||||
|
|
||||||
|
echo 50 > /sys/devices/system/cpu/cpufreq/intel_pstate/max_perf_pct
|
||||||
|
|
||||||
|
Gradually increase the CPU speed (up to 100 on `max_perf_pct`), waiting a few
|
||||||
|
minutes each time. You should ensure that your machine does not exceed 80C.
|
||||||
|
|
||||||
|
Dell's thermal safety is far too protective by default, on some of these, and
|
||||||
|
we don't yet know how to properly configure it. Running a CPU below 80c in
|
||||||
|
temperature and never higher than that, is a good idea anyway, for the
|
||||||
|
long term life of your CPU.
|
||||||
|
|
||||||
|
Regardless, thermal shutdown is extremely reliable on this machine, but Dell
|
||||||
|
makes it shut down *earlier*, before it can even start to CPU throttle.
|
|
@ -0,0 +1,84 @@
|
||||||
|
---
|
||||||
|
title: Dell Latitude E5520
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but otherwise the machine will be mostly stable.
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
Dell Latitude E5520
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | Dell |
|
||||||
|
| **Name** | Latitude E5520 |
|
||||||
|
| **Variants** | E5520 with Intel GPU supported |
|
||||||
|
| **Released** | 2012 |
|
||||||
|
| **Chipset** | Intel Sandy Bridge |
|
||||||
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
|
| **Original boot firmware** | Dell UEFI |
|
||||||
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
|
| **Flash chip** | 2xSOIC-8, 6MiB (4MiB and 2MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | W+ |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Display (if Nvidia GPU)** | U |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | P+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Libreboot 20231021 and releases newer than this have ROMs available for
|
||||||
|
Dell Latitude E5520.**
|
||||||
|
|
||||||
|
ROM images for Dell Latitude E5520 are available for flashing in the Libreboot
|
||||||
|
releases *after* 20230625, or you can compile a ROM image for installation via
|
||||||
|
lbmk, see: [build instructions](../build/)
|
||||||
|
|
||||||
|
Only the Intel GPU variants are supported, currently. All models with Intel GPU
|
||||||
|
are assumed to work.
|
||||||
|
|
||||||
|
Unlike the E6400, this one does require a neutered Intel ME image to run. This
|
||||||
|
means running it through `me_cleaner` before flashing; the Libreboot build
|
||||||
|
system does this automatically, during build, or you can insert a neutered
|
||||||
|
ROM image using the vendor scripts, see guide:
|
||||||
|
|
||||||
|
[Insert vendor files](../install/ivy_has_common.md)
|
||||||
|
|
||||||
|
As with the E6400, this one is flashable in software, from Dell UEFI firmware
|
||||||
|
to Libreboot. Please refer to the installation instructions.
|
||||||
|
|
||||||
|
**To install Libreboot, see: [E5520 installation
|
||||||
|
instructions](../install/e6430.md)**
|
|
@ -0,0 +1,86 @@
|
||||||
|
---
|
||||||
|
title: Dell Latitude E5530
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but otherwise the machine will be mostly stable.
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
Dell Latitude E5530
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | Dell |
|
||||||
|
| **Name** | Latitude E5530 |
|
||||||
|
| **Variants** | E5530 with Intel GPU supported |
|
||||||
|
| **Released** | 2012 |
|
||||||
|
| **Chipset** | Intel Ivy Bridge |
|
||||||
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
|
| **Original boot firmware** | Dell UEFI |
|
||||||
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
|
| **Flash chip** | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | W+ |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Display (if Nvidia GPU)** | U |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | P+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Libreboot 20231021 and releases newer than this have ROMs available for
|
||||||
|
Dell Latitude E5530.**
|
||||||
|
|
||||||
|
ROM images for Dell Latitude E5530 are available for flashing in the Libreboot
|
||||||
|
releases *after* 20230625, or you can compile a ROM image for installation via
|
||||||
|
lbmk, see: [build instructions](../build/)
|
||||||
|
|
||||||
|
Only the Intel GPU variants are supported, currently. All models with Intel GPU
|
||||||
|
are assumed to work.
|
||||||
|
|
||||||
|
Unlike the E6400, this one does require a neutered Intel ME image to run. This
|
||||||
|
means running it through `me_cleaner` before flashing; the Libreboot build
|
||||||
|
system does this automatically, during build, or you can insert a neutered
|
||||||
|
ROM image using the vendor scripts, see guide:
|
||||||
|
|
||||||
|
[Insert vendor files](../install/ivy_has_common.md)
|
||||||
|
|
||||||
|
As with the E6400, this one is flashable in software, from Dell UEFI firmware
|
||||||
|
to Libreboot. Please refer to the installation instructions.
|
||||||
|
|
||||||
|
**To install Libreboot, see: [E5530 installation
|
||||||
|
instructions](../install/e6430.md)**
|
||||||
|
|
||||||
|
Of note: this machine features a Broadnic nic, for ethernet.
|
|
@ -3,6 +3,12 @@ title: Dell Latitude E6400
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but otherwise the machine will be mostly stable.
|
||||||
|
|
||||||
<div class="specs">
|
<div class="specs">
|
||||||
<center>
|
<center>
|
||||||
<img tabindex=1 alt="Dell Latitude E6400" class="p" src="https://av.libreboot.org/e6400/e6400-seabios.jpg" /><span class="f"><img src="https://av.libreboot.org/e6400/e6400-seabios.jpg" /></span> <img tabindex=1 alt="Dell Latitude E6400 XFR" class="p" style="max-width:24em" src="https://av.libreboot.org/e6400/e6400xfr-seabios.jpg" /><span class="f"><img src="https://av.libreboot.org/e6400/e6400xfr-seabios.jpg" /></span>
|
<img tabindex=1 alt="Dell Latitude E6400" class="p" src="https://av.libreboot.org/e6400/e6400-seabios.jpg" /><span class="f"><img src="https://av.libreboot.org/e6400/e6400-seabios.jpg" /></span> <img tabindex=1 alt="Dell Latitude E6400 XFR" class="p" style="max-width:24em" src="https://av.libreboot.org/e6400/e6400xfr-seabios.jpg" /><span class="f"><img src="https://av.libreboot.org/e6400/e6400xfr-seabios.jpg" /></span>
|
||||||
|
|
|
@ -0,0 +1,84 @@
|
||||||
|
---
|
||||||
|
title: Dell Latitude E6420
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but otherwise the machine will be mostly stable.
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
Dell Latitude E6420
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | Dell |
|
||||||
|
| **Name** | Latitude E6420 |
|
||||||
|
| **Variants** | E6420 with Intel GPU supported |
|
||||||
|
| **Released** | 2012 |
|
||||||
|
| **Chipset** | Intel Sandy Bridge |
|
||||||
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
|
| **Original boot firmware** | Dell UEFI |
|
||||||
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
|
| **Flash chip** | 2xSOIC-8, 6MiB (4MiB and 2MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | W+ |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Display (if Nvidia GPU)** | U |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | P+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Libreboot 20231021 and releases newer than this have ROMs available for
|
||||||
|
Dell Latitude E6420.**
|
||||||
|
|
||||||
|
ROM images for Dell Latitude E6420 are available for flashing in the Libreboot
|
||||||
|
releases *after* 20230625, or you can compile a ROM image for installation via
|
||||||
|
lbmk, see: [build instructions](../build/)
|
||||||
|
|
||||||
|
Only the Intel GPU variants are supported, currently. All models with Intel GPU
|
||||||
|
are assumed to work.
|
||||||
|
|
||||||
|
Unlike the E6400, this one does require a neutered Intel ME image to run. This
|
||||||
|
means running it through `me_cleaner` before flashing; the Libreboot build
|
||||||
|
system does this automatically, during build, or you can insert a neutered
|
||||||
|
ROM image using the vendor scripts, see guide:
|
||||||
|
|
||||||
|
[Insert vendor files](../install/ivy_has_common.md)
|
||||||
|
|
||||||
|
As with the E6400, this one is flashable in software, from Dell UEFI firmware
|
||||||
|
to Libreboot. Please refer to the installation instructions.
|
||||||
|
|
||||||
|
**To install Libreboot, see: [E6420 installation
|
||||||
|
instructions](../install/e6430.md)**
|
|
@ -3,6 +3,12 @@ title: Dell Latitude E6430
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but the machine will otherwise be mostly stable.
|
||||||
|
|
||||||
<div class="specs">
|
<div class="specs">
|
||||||
<center>
|
<center>
|
||||||
Dell Latitude E6430
|
Dell Latitude E6430
|
||||||
|
@ -15,14 +21,14 @@ Dell Latitude E6430
|
||||||
| **Variants** | E6430 with Intel GPU supported |
|
| **Variants** | E6430 with Intel GPU supported |
|
||||||
| **Released** | 2012 |
|
| **Released** | 2012 |
|
||||||
| **Chipset** | Intel Ivy Bridge |
|
| **Chipset** | Intel Ivy Bridge |
|
||||||
| **CPU** | Intel Core i3, i5 or i7 . |
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
| **Graphics** | Intel HD 4000 and unsupported NVidia NVS 5200M |
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
| **Display** | 1366x768/1600x900 TFT |
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
| **Architecture** | x86_64 |
|
| **Architecture** | x86_64 |
|
||||||
| **EC** | SMSC MEC5055 with proprietary firmware |
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
| **Original boot firmware** | Dell UEFI |
|
| **Original boot firmware** | Dell UEFI |
|
||||||
| **Intel ME/AMD PSP** | Present. Can be completely disabled. |
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
| **Flash chip** | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
|
| **Flash chip** | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
@ -47,7 +53,7 @@ P*: Partially works with blobs
|
||||||
|
|
||||||
| ***Payloads supported*** | |
|
| ***Payloads supported*** | |
|
||||||
|---------------------------|-----------|
|
|---------------------------|-----------|
|
||||||
| **GRUB** | FAIL |
|
| **GRUB** | Works |
|
||||||
| **SeaBIOS** | Works |
|
| **SeaBIOS** | Works |
|
||||||
| **SeaBIOS with GRUB** | Works |
|
| **SeaBIOS with GRUB** | Works |
|
||||||
</div>
|
</div>
|
||||||
|
|
|
@ -0,0 +1,84 @@
|
||||||
|
---
|
||||||
|
title: Dell Latitude E6520
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but the machine will otherwise be mostly stable.
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
Dell Latitude E6520
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | Dell |
|
||||||
|
| **Name** | Latitude E6520 |
|
||||||
|
| **Variants** | E6520 with Intel GPU supported |
|
||||||
|
| **Released** | 2012 |
|
||||||
|
| **Chipset** | Intel Sandy Bridge |
|
||||||
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
|
| **Original boot firmware** | Dell UEFI |
|
||||||
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
|
| **Flash chip** | 2xSOIC-8, 6MiB (4MiB and 2MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | W+ |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Display (if Nvidia GPU)** | U |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | P+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Libreboot 20231021 and releases newer than this have ROMs available for
|
||||||
|
Dell Latitude E6520.**
|
||||||
|
|
||||||
|
ROM images for Dell Latitude E6520 are available for flashing in the Libreboot
|
||||||
|
releases *after* 20230625, or you can compile a ROM image for installation via
|
||||||
|
lbmk, see: [build instructions](../build/)
|
||||||
|
|
||||||
|
Only the Intel GPU variants are supported, currently. All models with Intel GPU
|
||||||
|
are assumed to work.
|
||||||
|
|
||||||
|
Unlike the E6400, this one does require a neutered Intel ME image to run. This
|
||||||
|
means running it through `me_cleaner` before flashing; the Libreboot build
|
||||||
|
system does this automatically, during build, or you can insert a neutered
|
||||||
|
ROM image using the vendor scripts, see guide:
|
||||||
|
|
||||||
|
[Insert vendor files](../install/ivy_has_common.md)
|
||||||
|
|
||||||
|
As with the E6400, this one is flashable in software, from Dell UEFI firmware
|
||||||
|
to Libreboot. Please refer to the installation instructions.
|
||||||
|
|
||||||
|
**To install Libreboot, see: [E6520 installation
|
||||||
|
instructions](../install/e6430.md)**
|
|
@ -0,0 +1,84 @@
|
||||||
|
---
|
||||||
|
title: Dell Latitude E6530
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**Thermal safety**: this machine shuts down very quickly, when the machine
|
||||||
|
exceeds 80c CPU temperature, which is far more conservative than on most
|
||||||
|
laptops (non-Dell ones), so you should make sure that your thermals are
|
||||||
|
excellent. More info available [here](dell_thermal.md). This is a known bug,
|
||||||
|
but the machine will otherwise be mostly stable.
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
Dell Latitude E6530
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | Dell |
|
||||||
|
| **Name** | Latitude E6530 |
|
||||||
|
| **Variants** | E6530 with Intel GPU supported |
|
||||||
|
| **Released** | 2012 |
|
||||||
|
| **Chipset** | Intel Ivy Bridge |
|
||||||
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
|
| **Original boot firmware** | Dell UEFI |
|
||||||
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
|
| **Flash chip** | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | W+ |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Display (if Nvidia GPU)** | U |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | P+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Libreboot 20231021 and releases newer than this have ROMs available for
|
||||||
|
Dell Latitude E6530.**
|
||||||
|
|
||||||
|
ROM images for Dell Latitude E6530 are available for flashing in the Libreboot
|
||||||
|
releases *after* 20230625, or you can compile a ROM image for installation via
|
||||||
|
lbmk, see: [build instructions](../build/)
|
||||||
|
|
||||||
|
Only the Intel GPU variants are supported, currently. All models with Intel GPU
|
||||||
|
are assumed to work.
|
||||||
|
|
||||||
|
Unlike the E6400, this one does require a neutered Intel ME image to run. This
|
||||||
|
means running it through `me_cleaner` before flashing; the Libreboot build
|
||||||
|
system does this automatically, during build, or you can insert a neutered
|
||||||
|
ROM image using the vendor scripts, see guide:
|
||||||
|
|
||||||
|
[Insert vendor files](../install/ivy_has_common.md)
|
||||||
|
|
||||||
|
As with the E6400, this one is flashable in software, from Dell UEFI firmware
|
||||||
|
to Libreboot. Please refer to the installation instructions.
|
||||||
|
|
||||||
|
**To install Libreboot, see: [E6530 installation
|
||||||
|
instructions](../install/e6430.md)**
|
|
@ -4,7 +4,7 @@ title: Gigabyte GA-G41M-ES2L desktop board
|
||||||
|
|
||||||
<div class="specs">
|
<div class="specs">
|
||||||
<center>
|
<center>
|
||||||
![GA-G41M-ES2L]()
|
GA-G41M-ES2L
|
||||||
</center>
|
</center>
|
||||||
|
|
||||||
| ***Specifications*** | |
|
| ***Specifications*** | |
|
||||||
|
@ -17,7 +17,7 @@ title: Gigabyte GA-G41M-ES2L desktop board
|
||||||
Pentium Extreme/D/4 Extreme/4/Celeron |
|
Pentium Extreme/D/4 Extreme/4/Celeron |
|
||||||
| **Graphics** | Integrated |
|
| **Graphics** | Integrated |
|
||||||
| **Display** | None. |
|
| **Display** | None. |
|
||||||
| **Memory** | Up to 16GB |
|
| **Memory** | Up to 8GB (2x4GB DDR2-800) |
|
||||||
| **Architecture** | x86_64 |
|
| **Architecture** | x86_64 |
|
||||||
| **Original boot firmware** | AWARD BIOS |
|
| **Original boot firmware** | AWARD BIOS |
|
||||||
| **Intel ME/AMD PSP** | Present. Can be disabled |
|
| **Intel ME/AMD PSP** | Present. Can be disabled |
|
||||||
|
|
|
@ -35,6 +35,14 @@ OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
BROKEN WIFI
|
||||||
|
===========
|
||||||
|
|
||||||
|
Wifi is broken in current revisions. This is because hardware `rfkill` is set,
|
||||||
|
and pressing the button combo to enable wifi doesn't work; we believe that the
|
||||||
|
EC is sending rfkill. We do not yet know how to enable it, at least as of
|
||||||
|
Libreboot 202405xx.
|
||||||
|
|
||||||
Introduction
|
Introduction
|
||||||
============
|
============
|
||||||
|
|
||||||
|
|
|
@ -7,6 +7,10 @@ x-toc-enable: true
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
<div class="specs">
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
HP EliteBook 2570p
|
||||||
|
</center>
|
||||||
|
|
||||||
| ***Specifications*** | |
|
| ***Specifications*** | |
|
||||||
|---------------------------|-----------------------------------|
|
|---------------------------|-----------------------------------|
|
||||||
| **Manufacturer** | HP |
|
| **Manufacturer** | HP |
|
||||||
|
|
|
@ -138,13 +138,16 @@ between the pins until you can see the normal BIOS boot screen.
|
||||||
|
|
||||||
![](https://av.libreboot.org/hp8200sff/fdo\_screwdriver.jpg)
|
![](https://av.libreboot.org/hp8200sff/fdo\_screwdriver.jpg)
|
||||||
|
|
||||||
Boot into an OS supported by flashrom. On Linux, make sure you add the
|
Boot into an OS supported by flashprog. On Linux, make sure you add the
|
||||||
kernel parameter **iomem=relaxed** which disables memory protections that
|
kernel parameter **iomem=relaxed** which disables memory protections that
|
||||||
prevent BIOS flashing.
|
prevent BIOS flashing.
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Now, run this command:
|
Now, run this command:
|
||||||
|
|
||||||
flashrom -p internal -c MX25L6406E/MX25L6408E
|
flashprog -p internal -c MX25L6406E/MX25L6408E
|
||||||
|
|
||||||
The output should contain the text "The Flash Descriptor Override
|
The output should contain the text "The Flash Descriptor Override
|
||||||
Pin-Strap is set". If it doesn't, start again from the beginning.
|
Pin-Strap is set". If it doesn't, start again from the beginning.
|
||||||
|
@ -170,18 +173,21 @@ We'll refer to it as `libreboot4.rom`. We need to pad it to 8 MiB:
|
||||||
Flash the Libreboot image with a tweaked layout:
|
Flash the Libreboot image with a tweaked layout:
|
||||||
|
|
||||||
ifdtool libreboot4.rom -f layout
|
ifdtool libreboot4.rom -f layout
|
||||||
flashrom -p internal -c MX25L6406E/MX25L6408E -w libreboot4.rom -l layout -i fd -i gbe -i bios -i me
|
flashprog -p internal -c MX25L6406E/MX25L6408E -w libreboot4.rom -l layout -i fd -i gbe -i bios -i me
|
||||||
|
|
||||||
Power off the computer. Make sure to power off, rebooting is not enough!
|
Power off the computer. Make sure to power off, rebooting is not enough!
|
||||||
|
|
||||||
Power on the computer.
|
Power on the computer.
|
||||||
Now we can flash the full 8 MiB image. Boot to an OS with flashrom
|
Now we can flash the full 8 MiB image. Boot to an OS with flashprog
|
||||||
again. On linux, remember the **iomem=relaxed** kernel parameter.
|
again. On linux, remember the **iomem=relaxed** kernel parameter.
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Pick a Libreboot image of your choice from `bin/hp8200sff_8mb`
|
Pick a Libreboot image of your choice from `bin/hp8200sff_8mb`
|
||||||
or from a release archive. We'll refer to it as `libreboot8.rom`.
|
or from a release archive. We'll refer to it as `libreboot8.rom`.
|
||||||
|
|
||||||
flashrom -p internal -c MX25L6406E/MX25L6408E -w libreboot8.rom
|
flashprog -p internal -c MX25L6406E/MX25L6408E -w libreboot8.rom
|
||||||
|
|
||||||
Power cycle the computer again.
|
Power cycle the computer again.
|
||||||
|
|
||||||
|
|
|
@ -0,0 +1,330 @@
|
||||||
|
---
|
||||||
|
title: HP EliteBook 820 G2
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2.jpg" /></span>
|
||||||
|
<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_lid.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_lid.jpg" /></span>
|
||||||
|
<br/>
|
||||||
|
<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_ports1.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_ports1.jpg" /></span>
|
||||||
|
<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_ports2.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_ports2.jpg" /></span>
|
||||||
|
<br/>
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | HP |
|
||||||
|
| **Name** | EliteBook 820 G2 |
|
||||||
|
| **Variants** | EliteBook 820 G2 |
|
||||||
|
| **Released** | 2014 |
|
||||||
|
| **Chipset** | 5th gen (Broadwell, SoC) |
|
||||||
|
| **CPU** | Intel i5-5200U, i5-5300U, i7-5500U, i7-5600U |
|
||||||
|
| **Graphics** | Intel HD 5500 graphics (libre initialisation) |
|
||||||
|
| **Display** | 14" 1366x768 or 1920x1080 TFT |
|
||||||
|
| **Memory** | Two slots, max 16GB/slot (32GB), DDR3/SODIMM |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC MEC1324 in main boot flash |
|
||||||
|
| **Original boot firmware** | HP UEFI firmware |
|
||||||
|
| **Intel ME/AMD PSP** | Present. Can be disabled with me_cleaner. |
|
||||||
|
| **Flash chip** | SOIC-8 16MiB 128Mbit, 12MiB usable by coreboot |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | N |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | W+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
|
||||||
|
Full hardware specifications can be found on HP's own website:
|
||||||
|
|
||||||
|
<https://support.hp.com/gb-en/document/c04543492>
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Unavailable in Libreboot 20231106 or earlier. You must [compile from
|
||||||
|
source](../build/), or use a release newer than 20231106.**
|
||||||
|
|
||||||
|
This is a beastly 12.5" Broadwell machine from HP, the main benefit of which is
|
||||||
|
greater power efficiency (compared to Ivybridge and Haswell platforms), while
|
||||||
|
offering similar CPU performance but much higher graphics performance.
|
||||||
|
|
||||||
|
Variants exist with either Intel Core i5-5200U, i5-5300U, i7-5500U or
|
||||||
|
i7-5600U and it comes with a plethora of ports; 3x USB 3.0, DisplayPort (which
|
||||||
|
can do 4K 60Hz), a VGA port, can be expanded to 32GB RAM, has *3* slots which
|
||||||
|
can take SSDs (PCIe, M2 and regular SATA), also has a side dock connector (for
|
||||||
|
a docking station). The screen is eDP type and can be upgraded to 1920x1080.
|
||||||
|
|
||||||
|
This is a nice portable machine, with very reasonable performance. Most people
|
||||||
|
should be very satisfied with it, in daily use. It is widely available in
|
||||||
|
online market places. This page will tell you how to flash it!
|
||||||
|
|
||||||
|
All variants of this mainboard will come with Intel HD 5500 graphics, which has
|
||||||
|
completely free software initialisation in coreboot, provided by *libgfxinit*.
|
||||||
|
|
||||||
|
Build ROM image from source
|
||||||
|
---------------------------
|
||||||
|
|
||||||
|
First, install the build dependencies and initialise git, using the
|
||||||
|
instructions in [building from source](../build/). Unless you're using a
|
||||||
|
release after Libreboot 20231106, you *must* use the latest `lbmk.git`.
|
||||||
|
|
||||||
|
The build target, when building from source, is thus:
|
||||||
|
|
||||||
|
./build roms hp820g2_12mb
|
||||||
|
|
||||||
|
NOTE: The actual flash is 16MB, but you must flash only the first 12MB of it.
|
||||||
|
The ROM images provided by Libreboot are 12MB.
|
||||||
|
|
||||||
|
There is a separate 2MB *system* flash that you must *erase*, prior to
|
||||||
|
installing Libreboot. This, along with Libreboot's modified IFD, bypasses
|
||||||
|
the security (HP Sure Start) that the vendor put there, allowing you to
|
||||||
|
use coreboot-based firmware such as Libreboot.
|
||||||
|
|
||||||
|
Installation
|
||||||
|
============
|
||||||
|
|
||||||
|
Insert binary files
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
If you're using a release ROM, please ensure that you've inserted extra firmware
|
||||||
|
required refer to the [guide](../install/ivy_has_common.md) for that. (**failure
|
||||||
|
to adhere to this advice will result in a bricked machine**)
|
||||||
|
|
||||||
|
If you're *building* from source (using lbmk), the steps takes above are done
|
||||||
|
for you automatically, inserting all of the required files. The above link is
|
||||||
|
only relevant for *release* images, which lack some of these files.
|
||||||
|
|
||||||
|
Set MAC address
|
||||||
|
---------------
|
||||||
|
|
||||||
|
This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
|
||||||
|
region. As such, release/build ROMs will contain the same MAC address. To
|
||||||
|
change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
|
||||||
|
|
||||||
|
Update an existing Libreboot installation
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
<img class="l" tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_backlit.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_backlit.jpg" /></span>
|
||||||
|
|
||||||
|
NOTE: This section only applies if you haven't enabled write protection. You
|
||||||
|
can otherwise use the external flashing instructions (see below) for both the
|
||||||
|
initial installation and updates, but for updates you don't need to re-erase
|
||||||
|
the private flash, if it was already erased.
|
||||||
|
|
||||||
|
If you're already running Libreboot, and you don't have flash protection
|
||||||
|
turned on, [internal flashing](../install/) is possible, but please note:
|
||||||
|
|
||||||
|
You must *only* flash the first 12MB, and nothing in the final 4MB of the flash.
|
||||||
|
This is because the EC firmware is in flash, and we don't touch that during
|
||||||
|
initial installation or during updates.
|
||||||
|
|
||||||
|
Update it like so:
|
||||||
|
|
||||||
|
Create a dummy 16MB ROM like so:
|
||||||
|
|
||||||
|
```
|
||||||
|
dd if=/dev/zero of=new.bin bs=16M count=1
|
||||||
|
```
|
||||||
|
|
||||||
|
Then insert your 12MB Libreboot ROM image into the dummy file:
|
||||||
|
|
||||||
|
```
|
||||||
|
dd if=libreboot.rom of=new.bin bs=12M count=1 conv=notrunc
|
||||||
|
```
|
||||||
|
|
||||||
|
The `libreboot.rom` file is the 12MB image from Libreboot. The `new.bin`
|
||||||
|
file is the Libreboot ROM, padded to 16MB. You will not flash the entire 16MB
|
||||||
|
file, but flashprog detects a 16MB flash IC. This just makes flashrom not
|
||||||
|
complain about mismatching ROM/chip size.
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
|
You should flash each region individually:
|
||||||
|
|
||||||
|
```
|
||||||
|
flashprog -p internal --ifd -i gbe -w new.bin --noverify-all
|
||||||
|
flashprog -p internal --ifd -i bios -w new.bin --noverify-all
|
||||||
|
flashprog -p internal --ifd -i me -w new.bin --noverify-all
|
||||||
|
flashprog -p internal --ifd -i ifd -w new.bin --noverify-all
|
||||||
|
```
|
||||||
|
|
||||||
|
NOTE: The `--ifd` option uses the regions defined in the *flashed* IFD, so
|
||||||
|
they must match the ROM. You can otherwise dump a layout file and use that,
|
||||||
|
using the instructions below (using `-l layout.txt` instead of `--ifd`).
|
||||||
|
|
||||||
|
NOTE: If you already did an installation before, and you don't want to
|
||||||
|
[change the MAC address](../install/nvmutil.html) stored in the gbe region,
|
||||||
|
you can skip the gbe/ifd/me regions as above, and flash just the BIOS region.
|
||||||
|
|
||||||
|
NOTE: Use of `--ifd` requires flashrom 1.2 or higher. If you have an older
|
||||||
|
version, or you don't have `--ifd`, you could instead do:
|
||||||
|
|
||||||
|
```
|
||||||
|
ifdtool -f layout.txt libreboot.rom
|
||||||
|
```
|
||||||
|
|
||||||
|
Then, instead of `--ifd` you would use `-l layout.txt`.
|
||||||
|
|
||||||
|
ALSO: The `--ifd` option makes flashrom flash regions based on what's in
|
||||||
|
the *current* flashed IFD.
|
||||||
|
|
||||||
|
Flashing Libreboot first time (hardware)
|
||||||
|
========================================
|
||||||
|
|
||||||
|
**PLEASE ENSURE that you dump a copy of both flash ICs (system flash and
|
||||||
|
private flash). Take two dumps of each, and make sure each has two good hashes.
|
||||||
|
This is because there are certain files that, while you may not need for a
|
||||||
|
regular Libreboot installation, may be useful for recovery purposes. You have
|
||||||
|
been warned!**
|
||||||
|
|
||||||
|
This section is relevant to you if you're still running the original HP
|
||||||
|
firmware. You must [flash externally](../install/spi.md).
|
||||||
|
|
||||||
|
Take stock of these further notes, because there are extra steps that you
|
||||||
|
must take.
|
||||||
|
|
||||||
|
HP Sure Start
|
||||||
|
-------------
|
||||||
|
|
||||||
|
There is a 16MB flash and a 2MB flash. Read this page for info:
|
||||||
|
<https://doc.coreboot.org/mainboard/hp/hp_sure_start.html>
|
||||||
|
|
||||||
|
The page makes it seem more complicated than necessary, from a user's point
|
||||||
|
of view. What you really need to do is just erase the 2MB flash IC, and flash
|
||||||
|
only the first 12MB of the 16MB flash IC. A photo is shown below. Consult
|
||||||
|
the [SPI flashing guide](../install/spi.md) and act as if you were flashing,
|
||||||
|
but leave out `-w libreboot.rom` (don't write an image), and instead
|
||||||
|
use the `--erase` option, with your clip connected to the private flash (2MB
|
||||||
|
flash IC).
|
||||||
|
|
||||||
|
You might want to dump the private flash first, just in case (use `-r priv.rom`
|
||||||
|
or whatever filename you want to dump to, and take two dumps, ensuring that
|
||||||
|
the hashes match). The private (2MB) flash is inaccessible from your OS. The
|
||||||
|
system stores hashes of the IFD, GbE and a copy of IFD/GbE in private flash,
|
||||||
|
restoring them if they were modified, but erasing the private flash disables
|
||||||
|
this security mechanism.
|
||||||
|
|
||||||
|
Here is a photo of the board, with the flashes:
|
||||||
|
|
||||||
|
![HP 820 G2 flash](https://av.libreboot.org/hp820g2/hp820g2_flash.jpg)
|
||||||
|
|
||||||
|
HP bootblock
|
||||||
|
------------
|
||||||
|
|
||||||
|
See: <https://doc.coreboot.org/mainboard/hp/elitebook_820_g2.html?highlight=elitebook>
|
||||||
|
|
||||||
|
In this page it talks about HP's own bootblock and EC firmware. These are in
|
||||||
|
the final 4MB of the flash. You must *not* modify these, because you will brick
|
||||||
|
your machine unless the IFD is modified;
|
||||||
|
|
||||||
|
This is why Libreboot provides 12MB images. The IFD in Libreboot is modified, as
|
||||||
|
per this coreboot documentation, to make the BIOS region *end* at the last byte
|
||||||
|
of the first 12MB in flash, bypassing HP's security entirely. In other words,
|
||||||
|
you can run whatever you want (such as Libreboot) in the first 12MB of flash,
|
||||||
|
so long as the upper 4MB is untouched and the private 2MB flash has been erased.
|
||||||
|
|
||||||
|
With Libreboot's modified IFD, HP's own bootblock is never executed, but the
|
||||||
|
EC firmware *is*, and must be left alone. You do not to insert it in your
|
||||||
|
Libreboot ROM because it's already in flash, within that last 4MB.
|
||||||
|
|
||||||
|
Flash a ROM image (hardware)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
**REMOVE all power sources like battery, charger and so on, before doing this.
|
||||||
|
This is to prevent short circuiting and power surges while flashing.**
|
||||||
|
|
||||||
|
For general information, please refer to [25xx NOR flash
|
||||||
|
instructions](../install/spi.md).
|
||||||
|
|
||||||
|
Remove the bottom cover via the latch, and the flashes are accessible.
|
||||||
|
First, dump both flashes for backup, using the `-r` option (instead of `-w`)
|
||||||
|
in flashrom. Two dumps of each flash, make sure both dumps match for each chip.
|
||||||
|
|
||||||
|
We will assume that your system flash (16MB) dump is named `dump.bin`. This is
|
||||||
|
the dump of your 16MB flash, containing HP's firmware, including the final
|
||||||
|
bootblock and EC firmware.
|
||||||
|
|
||||||
|
This gives you everything, including the final 4MB. Now insert your new ROM
|
||||||
|
into a copy of `dump.bin`:
|
||||||
|
|
||||||
|
```
|
||||||
|
cp -R dump.bin new.bin
|
||||||
|
dd if=libreboot.rom of=new.bin bs=12M count=1 conv=notrunc
|
||||||
|
```
|
||||||
|
|
||||||
|
Flash `new.bin` to system flash (16MB IC) using the `-w` option in flashrom,
|
||||||
|
and erase the private (2MB) flash IC,
|
||||||
|
using the `--erase` option (instead of `-w filename.rom`) in flashrom.
|
||||||
|
|
||||||
|
In the above example, you replaced the first 12MB of the HP dump with that of
|
||||||
|
your Libreboot image, but leaving the final 4MB intact which contains the EC
|
||||||
|
firmware. Libreboot's custom IFD sets everything so that all regions, from
|
||||||
|
IFD to GbE, ME and then BIOS region, exist within the first 12MB of flash.
|
||||||
|
This makes the machine boot from the end of the 12MB section, containing the
|
||||||
|
coreboot bootblock, instead of the HP bootblock (which is never executed but
|
||||||
|
must remain intact).
|
||||||
|
|
||||||
|
It's very important that you *erase* the 2MB flash. Be careful *not* to
|
||||||
|
erase the system (16MB flash). This is yet another reason why you should keep
|
||||||
|
a backup of both flash ICs, just in case (dumped using `-r` in flashrom).
|
||||||
|
|
||||||
|
![](https://av.libreboot.org/hp820g2/hp820g2.jpg)
|
||||||
|
|
||||||
|
![](https://av.libreboot.org/hp820g2/hp820g2_inside.jpg)
|
||||||
|
|
||||||
|
And that's all. Refer to other documents on Libreboot's website for how
|
||||||
|
to handle Linux/BSD systems and generally use your machine.
|
||||||
|
|
||||||
|
TPM 2.0 potentially supported
|
||||||
|
==============================
|
||||||
|
|
||||||
|
The onboard TPM is an SLB 9660, which supports TPM 1.2 but it is known to be
|
||||||
|
compatible with TPM 2.0 via firmware upgrade. Although not yet tested, we have
|
||||||
|
some notes about that here:
|
||||||
|
|
||||||
|
[../../tasks/#hp-820-g2-tpm](../../tasks/#hp-820-g2-tpm)
|
||||||
|
|
||||||
|
Not yet used meaningfully by Libreboot itself, but the TPM can be used to
|
||||||
|
implement things like measured boot.
|
||||||
|
|
||||||
|
References
|
||||||
|
==========
|
||||||
|
|
||||||
|
See: <https://doc.coreboot.org/soc/intel/broadwell/blobs.html>
|
||||||
|
|
||||||
|
Libreboot's build system automatically pulls down the MRC/refcode files, and
|
||||||
|
modifies the refcode to enable the onboard Intel Gigabit Ethernet (GbE). You
|
||||||
|
don't need to mess with this at all, when you build Libreboot yourself.
|
||||||
|
|
||||||
|
You can see how this works, by looking at the patch which added 820 G2 support:
|
||||||
|
<https://browse.libreboot.org/lbmk.git/commit/?id=401c0882aaec059eab62b5ce467d3efbc1472d1f>
|
||||||
|
|
||||||
|
If you're using release builds, the MRC, refcode and (neutered) ME images are
|
||||||
|
missing from flash, and must be re-inserted, using the instructions
|
||||||
|
on [this page](../install/ivy_has_common.md).
|
|
@ -71,15 +71,18 @@ crystal (small metal cylinder) and the power cable for the optical drive.
|
||||||
|
|
||||||
![](https://av.libreboot.org/hp8300usdt/jumper_to_fdo.jpg)
|
![](https://av.libreboot.org/hp8300usdt/jumper_to_fdo.jpg)
|
||||||
|
|
||||||
Boot into an OS of your choice (that has flashrom support). When using Linux,
|
Boot into an OS of your choice (that has flashprog support). When using Linux,
|
||||||
you need to supply the kernel parameter `iomem=relaxed`.
|
you need to supply the kernel parameter `iomem=relaxed`.
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
The BIOS should no longer impose any write-protections.
|
The BIOS should no longer impose any write-protections.
|
||||||
You can now use `flashrom -p internal` freely.
|
You can now use `flashprog -p internal` freely.
|
||||||
|
|
||||||
Take a backup of the original BIOS:
|
Take a backup of the original BIOS:
|
||||||
|
|
||||||
flashrom -p internal -r oem_bios
|
flashprog -p internal -r oem_bios
|
||||||
|
|
||||||
This is an Ivy Bridge board which means that a neutered ME image
|
This is an Ivy Bridge board which means that a neutered ME image
|
||||||
is required if you wish to flash the ME region. Libreboot's
|
is required if you wish to flash the ME region. Libreboot's
|
||||||
|
@ -95,7 +98,7 @@ platforms](../install/ivy_has_common.md)
|
||||||
|
|
||||||
You can now flash libreboot:
|
You can now flash libreboot:
|
||||||
|
|
||||||
flashrom -p internal -w libreboot.rom
|
flashprog -p internal -w libreboot.rom
|
||||||
|
|
||||||
You can now move the jumper back to its original place.
|
You can now move the jumper back to its original place.
|
||||||
By default, Libreboot applies no write-protection, so
|
By default, Libreboot applies no write-protection, so
|
||||||
|
|
|
@ -0,0 +1,114 @@
|
||||||
|
---
|
||||||
|
title: HP EliteBook 8460p
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
<img tabindex=1 alt="HP EliteBook 8460p" class="p" src="https://av.libreboot.org/hp8460p/hp8460p.webp" /><span class="f"><img src="https://av.libreboot.org/hp8460p/hp8460p.webp" /></span>
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | HP |
|
||||||
|
| **Name** | EliteBook 8460p |
|
||||||
|
| **Variants** | EliteBook 8460p |
|
||||||
|
| **Released** | 2011 |
|
||||||
|
| **Chipset** | Intel QM67 |
|
||||||
|
| **CPU** | Intel Sandy Bridge (socketed) |
|
||||||
|
| **Graphics** | Intel HD Graphics (supported in Libreboot) or
|
||||||
|
AMD Radeon HD 6470M (unsupported in Libreboot) |
|
||||||
|
| **Display** | 14" 1366x768 or 1600x900 TFT |
|
||||||
|
| **Memory** | Two slots, max 8GB/slot (16GB), DDR3/SODIMM |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC KBC1126, proprietary (in main boot flash) |
|
||||||
|
| **Original boot firmware** | HP UEFI firmware |
|
||||||
|
| **Intel ME/AMD PSP** | Present. Can be disabled with me_cleaner. |
|
||||||
|
| **Flash chip** | SOIC-8 8MiB (64Mbit) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | N |
|
||||||
|
| **Display (if Intel GPU)** | W+ |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | W+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Unavailable in Libreboot 20231106 or earlier. You must [compile from
|
||||||
|
source](../build/), or use a release newer than 20231106.**
|
||||||
|
|
||||||
|
This is a beastly 14" Sandy Bridge platform from HP.
|
||||||
|
**NOTE: Until otherwise stated, only the Intel GPU variant is supported in
|
||||||
|
Libreboot.**
|
||||||
|
|
||||||
|
Build ROM image from source
|
||||||
|
---------------------------
|
||||||
|
|
||||||
|
The build target, when building from source, is thus:
|
||||||
|
|
||||||
|
./build roms hp8460pintel_8mb
|
||||||
|
|
||||||
|
Installation
|
||||||
|
============
|
||||||
|
|
||||||
|
Insert binary files
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
If you're using a release ROM, please ensure that you've inserted extra firmware
|
||||||
|
required refer to the [guide](../install/ivy_has_common.md) for that. (failure
|
||||||
|
to adhere to this advice will result in a bricked machine)
|
||||||
|
|
||||||
|
Set MAC address
|
||||||
|
---------------
|
||||||
|
|
||||||
|
This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
|
||||||
|
region. As such, release/build ROMs will contain the same MAC address. To
|
||||||
|
change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
|
||||||
|
|
||||||
|
Flash a ROM image (software)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
If you're already running Libreboot, and you don't have flash protection
|
||||||
|
turned on, [internal flashing](../install/) is possible.
|
||||||
|
|
||||||
|
Flash a ROM image (hardware)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
**REMOVE all power sources like battery, charger and so on, before doing this.
|
||||||
|
This is to prevent short circuiting and power surges while flashing.**
|
||||||
|
|
||||||
|
For general information, please refer to [25xx NOR flash
|
||||||
|
instructions](../install/spi.md).
|
||||||
|
|
||||||
|
At this present time, disassembly instructions are unavailable from the
|
||||||
|
Libreboot project, but you can search for HP's own hardware maintenance manual
|
||||||
|
or look at videos online showing disassembly.
|
||||||
|
|
||||||
|
The flash chip is visible by removing the "bottom door" panel. But the
|
||||||
|
frame makes it hard to put a clip on it, so it's recommended to follow the
|
||||||
|
HP [service manual](https://h10032.www1.hp.com/ctg/Manual/c03015458.pdf)
|
||||||
|
to remove the **bottom cover**, as it's called.
|
||||||
|
|
|
@ -0,0 +1,135 @@
|
||||||
|
---
|
||||||
|
title: HP EliteBook 8560w
|
||||||
|
x-toc-enable: true
|
||||||
|
...
|
||||||
|
|
||||||
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
<div class="specs">
|
||||||
|
<center>
|
||||||
|
<img tabindex=1 alt="HP EliteBook 8560w" class="p" src="https://av.libreboot.org/hp8560w/hp8560w.webp" /><span class="f"><img src="https://av.libreboot.org/hp8560w/hp8560w.webp" /></span>
|
||||||
|
</center>
|
||||||
|
|
||||||
|
| ***Specifications*** | |
|
||||||
|
|----------------------------|------------------------------------------------|
|
||||||
|
| **Manufacturer** | HP |
|
||||||
|
| **Name** | EliteBook 8560w |
|
||||||
|
| **Variants** | EliteBook 8560w |
|
||||||
|
| **Released** | 2011 |
|
||||||
|
| **Chipset** | Intel QM67 |
|
||||||
|
| **CPU** | Intel Sandy Bridge (socketed) |
|
||||||
|
| **Graphics** | MXM-A (3.0), socketed |
|
||||||
|
| **Display** | 15.6" 1600x900 or 1920x1080 LCD |
|
||||||
|
| **Memory** | Two or four slots, max 8GB/slot
|
||||||
|
(16GB or 32GB), DDR3/SODIMM |
|
||||||
|
| **Architecture** | x86_64 |
|
||||||
|
| **EC** | SMSC KBC1126, proprietary (in main boot flash) |
|
||||||
|
| **Original boot firmware** | HP UEFI firmware |
|
||||||
|
| **Intel ME/AMD PSP** | Present. Can be disabled with me_cleaner. |
|
||||||
|
| **Flash chip** | SOIC-8 8MiB (64Mbit) |
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
W+: Works without blobs;
|
||||||
|
N: Doesn't work;
|
||||||
|
W*: Works with blobs;
|
||||||
|
U: Untested;
|
||||||
|
P+: Partially works;
|
||||||
|
P*: Partially works with blobs
|
||||||
|
```
|
||||||
|
|
||||||
|
| ***Features*** | |
|
||||||
|
|---------------------------------------------------|----|
|
||||||
|
| **Internal flashing with original boot firmware** | N |
|
||||||
|
| **Display** | W* |
|
||||||
|
| **Audio** | W+ |
|
||||||
|
| **RAM Init** | W+ |
|
||||||
|
| **External output** | W+ |
|
||||||
|
| **Display brightness** | W+ |
|
||||||
|
|
||||||
|
| ***Payloads supported*** | |
|
||||||
|
|---------------------------|-----------|
|
||||||
|
| **GRUB** | Works |
|
||||||
|
| **SeaBIOS** | Works |
|
||||||
|
| **SeaBIOS with GRUB** | Works |
|
||||||
|
</div>
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**Unavailable in Libreboot 20240126 or earlier. You must [compile from
|
||||||
|
source](../build/), or use a release newer than 20240126.**
|
||||||
|
|
||||||
|
This is a beastly 15" Sandy Bridge mobile workstation from HP.
|
||||||
|
|
||||||
|
**Wi-Fi does not work. It shows correctly in lspci, but stays hard blocked.**
|
||||||
|
|
||||||
|
GPU
|
||||||
|
---
|
||||||
|
|
||||||
|
This laptop has upgradeable GPU: it has a socketed MXM-A 3.0 card. So far,
|
||||||
|
only Quadro 1000M and 2000M (which shipped with the laptop originally) have
|
||||||
|
been tested with Libreboot.
|
||||||
|
|
||||||
|
These laptops shipped with eDP and LVDS panels. If you choose to upgrade the
|
||||||
|
graphics card, make sure it is compatible with the panel you have. Use the
|
||||||
|
following command to check:
|
||||||
|
|
||||||
|
xrandr
|
||||||
|
|
||||||
|
Or if using Wayland:
|
||||||
|
|
||||||
|
wlr-randr
|
||||||
|
|
||||||
|
If you have "LVDS-1 connected", your GPU upgrade needs to support LVDS.
|
||||||
|
According to [this forum thread](https://forums.macrumors.com/threads/2011-imac-graphics-card-upgrade.1596614/),
|
||||||
|
AMD's 1st gen GCN cards are the newest and most powerful to support LVDS.
|
||||||
|
If you have an eDP panel, you should be able to use newer cards than that.
|
||||||
|
|
||||||
|
As long as the card has an onboard VBIOS, Libreboot will execute it and
|
||||||
|
everything *should* work. **However, this is currently untested.**
|
||||||
|
|
||||||
|
Build ROM image from source
|
||||||
|
---------------------------
|
||||||
|
|
||||||
|
The build target, when building from source, is thus:
|
||||||
|
|
||||||
|
./build roms hp8560w_8mb
|
||||||
|
|
||||||
|
Installation
|
||||||
|
============
|
||||||
|
|
||||||
|
Insert binary files
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
If you're using a release ROM, please ensure that you've inserted extra firmware
|
||||||
|
required refer to the [guide](../install/ivy_has_common.md) for that. (failure
|
||||||
|
to adhere to this advice will result in a bricked machine)
|
||||||
|
|
||||||
|
Set MAC address
|
||||||
|
---------------
|
||||||
|
|
||||||
|
This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
|
||||||
|
region. As such, release/build ROMs will contain the same MAC address. To
|
||||||
|
change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
|
||||||
|
|
||||||
|
Flash a ROM image (software)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
If you're already running Libreboot, and you don't have flash protection
|
||||||
|
turned on, [internal flashing](../install/) is possible.
|
||||||
|
|
||||||
|
Flash a ROM image (hardware)
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
**REMOVE all power sources like battery, charger and so on, before doing this.
|
||||||
|
This is to prevent short circuiting and power surges while flashing.**
|
||||||
|
|
||||||
|
Remove the bottom cover. The SOIC-8 flash chip is next to the memory slot 2.
|
||||||
|
You need to cut away a small piece of the clear plastic protection material
|
||||||
|
to get to the chip.
|
||||||
|
|
||||||
|
![](https://av.libreboot.org/hp8560w/hp8560w_chip.webp)
|
||||||
|
|
||||||
|
For information about programming the chip, please refer to [25xx NOR flash
|
||||||
|
instructions](../install/spi.md).
|
|
@ -89,5 +89,8 @@ to program Libreboot on it.
|
||||||
|
|
||||||
Some part of the board might turn on when programming. If programming fails,
|
Some part of the board might turn on when programming. If programming fails,
|
||||||
you might have to attach the laptop to a charger. Make sure the laptop
|
you might have to attach the laptop to a charger. Make sure the laptop
|
||||||
powers off before running flashrom. No LEDs should be lit.
|
powers off before running flashprog. No LEDs should be lit.
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
|
|
|
@ -4,7 +4,7 @@ title: Apple iMac 5,2
|
||||||
|
|
||||||
<div class="specs">
|
<div class="specs">
|
||||||
<center>
|
<center>
|
||||||
![iMac5,2]()
|
iMac5,2
|
||||||
</center>
|
</center>
|
||||||
|
|
||||||
| ***Specifications*** | |
|
| ***Specifications*** | |
|
||||||
|
|
|
@ -3,38 +3,29 @@ title: Hardware compatibility list
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
Need help?
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
|
LIBREBOOT](../../news/safety.md).**
|
||||||
|
|
||||||
This sections relates to known hardware compatibility in libreboot.
|
This sections relates to known hardware compatibility in libreboot.
|
||||||
|
|
||||||
For installation instructions, refer to [../install/](../install/).
|
For installation instructions, refer to [../install/](../install/).
|
||||||
|
|
||||||
NOTE: For T60/R60 thinkpads, make sure that it has an Intel GPU, not an ATI GPU
|
|
||||||
because coreboot lacks native video initialization for the ATI GPUs on these
|
|
||||||
machines.
|
|
||||||
|
|
||||||
(for later machines like T500, T400, ATI GPU doesn't matter, because it also
|
|
||||||
has an Intel GPU, and libreboot uses the Intel one)
|
|
||||||
|
|
||||||
READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
|
|
||||||
====================================================================
|
|
||||||
|
|
||||||
**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
|
|
||||||
ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
|
|
||||||
the release ROMs of Libreboot are MISSING certain files, that you must insert
|
|
||||||
yourself. FAILURE to adhere to this warning may result in you bricking your
|
|
||||||
machine (rendering it unbootable), if you were to flash the release ROMs without
|
|
||||||
modifying them in any way. For more information, please read:**
|
|
||||||
|
|
||||||
**[Insert vendor files on Sandybridge/Ivybridge/Haswell](../install/ivy_has_common.md)**
|
|
||||||
|
|
||||||
NOTE: This warning does not apply to ROMs that you compiled yourself, using
|
|
||||||
lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
|
|
||||||
in release ROMs. The link above says how to re-add them. When building ROM images
|
|
||||||
yourself, from source, Libreboot's build system automatically handles it. See:
|
|
||||||
[Libreboot build instructions](../build/)
|
|
||||||
|
|
||||||
Supported hardware
|
Supported hardware
|
||||||
==================
|
==================
|
||||||
|
|
||||||
|
@ -47,27 +38,44 @@ libreboot currently supports the following systems in this release:
|
||||||
|
|
||||||
### Desktops (AMD, Intel, x86)
|
### Desktops (AMD, Intel, x86)
|
||||||
|
|
||||||
|
- **[Dell OptiPlex 7020/9020 MT and SFF](dell9020.md) - Also [available to buy
|
||||||
|
with Libreboot preinstalled](https://minifree.org/product/libreboot-9020/)** - Dell OptiPlex XE2 MT/SFF also known to work
|
||||||
- [Acer G43T-AM3](acer_g43t-am3.md)
|
- [Acer G43T-AM3](acer_g43t-am3.md)
|
||||||
- [Apple iMac 5,2](imac52.md)
|
- [Apple iMac 5,2](imac52.md)
|
||||||
- [ASUS KCMA-D8 motherboard](kcma-d8.md)
|
- [ASUS KCMA-D8 motherboard](kcma-d8.md)
|
||||||
- [Dell Precision T1650](t1650.md) (**easy to flash without disassembly**)
|
- Dell OptiPlex 7010 **MT** (known to work, using the T1650 ROM, but more
|
||||||
|
research is needed)
|
||||||
|
- [Dell Precision T1650](t1650.md)
|
||||||
- [Gigabyte GA-G41M-ES2L motherboard](ga-g41m-es2l.md)
|
- [Gigabyte GA-G41M-ES2L motherboard](ga-g41m-es2l.md)
|
||||||
- [HP Elite 8200 SFF/MT](hp8200sff.md) (HP 6200 Pro Business probably works too)
|
- [HP Elite 8200 SFF/MT](hp8200sff.md) (HP 6200 Pro Business probably works too)
|
||||||
(**easy to flash without disassembly**)
|
- [HP Elite 8300 USDT](hp8300usdt.md)
|
||||||
- [HP Elite 8300 USDT](hp8300usdt.md) (**easy to flash without disassembly**)
|
|
||||||
- [Intel D510MO and D410PT motherboards](d510mo.md)
|
- [Intel D510MO and D410PT motherboards](d510mo.md)
|
||||||
|
- [Intel D945GCLF](d945gclf.md)
|
||||||
|
|
||||||
### Laptops (Intel, x86)
|
### Laptops (Intel, x86)
|
||||||
|
|
||||||
- [Apple MacBook1,1 and MacBook2,1](macbook21.md) (2,1 flashable without disassembly)
|
- **[Lenovo ThinkPad T440p](../install/t440p_external.md) - Also [available
|
||||||
|
to buy with Libreboot preinstalled](https://minifree.org/product/libreboot-t440p/)**
|
||||||
|
- **[Lenovo ThinkPad W541](../install/ivy_has_common.md) - Also [available to
|
||||||
|
buy with Libreboot preinstalled](https://minifree.org/product/libreboot-w541/)** - NOTE: W540 also compatible (same mainboard, so flash the same ROM)
|
||||||
|
- Lenovo ThinkPad X230 - *Also* available on Minifree: <https://minifree.org/product/libreboot-x230/>
|
||||||
|
- [Apple MacBook1,1 and MacBook2,1](macbook21.md)
|
||||||
- [Dell Latitude E6400, E6400 XFR and E6400 ATG, all with Nvidia or Intel
|
- [Dell Latitude E6400, E6400 XFR and E6400 ATG, all with Nvidia or Intel
|
||||||
GPU](e6400.md) **(easy to flash, no disassembly, similar
|
GPU](e6400.md)
|
||||||
hardware to X200/T400)**
|
- [Dell Latitude E6420 (Intel GPU](e6420.md)
|
||||||
- [Dell Latitude E6430 (Intel GPU](e6430.md) **(easy to flash, no disassembly)**
|
- [Dell Latitude E6430 (Intel GPU](e6430.md)
|
||||||
- [HP EliteBook 2170p](hp2170p.md) (**socketed flash IC**)
|
- [Dell Latitude E5520 (Intel GPU](e5520.md)
|
||||||
|
- [Dell Latitude E5530 (Intel GPU](e5530.md)
|
||||||
|
- [Dell Latitude E6520 (Intel GPU](e6520.md)
|
||||||
|
- [Dell Latitude E6530 (Intel GPU](e6530.md)
|
||||||
|
- Dell Latitude E5420.
|
||||||
|
- [HP EliteBook 2170p](hp2170p.md)
|
||||||
- [HP EliteBook 2560p](hp2560p.md)
|
- [HP EliteBook 2560p](hp2560p.md)
|
||||||
- [HP EliteBook 2570p](hp2570p.md)
|
- [HP EliteBook 2570p](hp2570p.md)
|
||||||
|
- [HP EliteBook 820 G2](hp820g2.md)
|
||||||
|
- [HP EliteBook 8460p](hp8460p.md)
|
||||||
- [HP EliteBook 8470p](hp8470p.md)
|
- [HP EliteBook 8470p](hp8470p.md)
|
||||||
|
- [HP EliteBook 8560w](hp8560w.md)
|
||||||
- [HP EliteBook Folio 9470m](hp9470m.md)
|
- [HP EliteBook Folio 9470m](hp9470m.md)
|
||||||
- [Lenovo ThinkPad R400](r400.md)
|
- [Lenovo ThinkPad R400](r400.md)
|
||||||
- [Lenovo ThinkPad R500](r500.md)
|
- [Lenovo ThinkPad R500](r500.md)
|
||||||
|
@ -75,20 +83,18 @@ libreboot currently supports the following systems in this release:
|
||||||
- [Lenovo Thinkpad T420](../install/ivy_has_common.md) (no install docs yet)
|
- [Lenovo Thinkpad T420](../install/ivy_has_common.md) (no install docs yet)
|
||||||
- [Lenovo ThinkPad T420S](../install/ivy_has_common.md) (no install docs yet)
|
- [Lenovo ThinkPad T420S](../install/ivy_has_common.md) (no install docs yet)
|
||||||
- [Lenovo ThinkPad T430](../install/ivy_has_common.md) (no install docs yet)
|
- [Lenovo ThinkPad T430](../install/ivy_has_common.md) (no install docs yet)
|
||||||
- [Lenovo ThinkPad T440p](../install/t440p_external.md)
|
|
||||||
- [Lenovo ThinkPad T500](t500.md)
|
- [Lenovo ThinkPad T500](t500.md)
|
||||||
|
- [Lenovo ThinkPad T520 / W520](../install/ivy_has_common.md) (no install guide yet)
|
||||||
- [Lenovo ThinkPad T530 / W530](../install/ivy_has_common.md) (no install
|
- [Lenovo ThinkPad T530 / W530](../install/ivy_has_common.md) (no install
|
||||||
- Lenovo ThinkPad T60 (with Intel GPU) (**easy to flash without disassembly**)
|
- Lenovo ThinkPad T60 (with Intel GPU)
|
||||||
- [Lenovo ThinkPad W500](t500.md)
|
- [Lenovo ThinkPad W500](t500.md)
|
||||||
- [Lenovo ThinkPad W541](../install/ivy_has_common.md) (no install docs yet)
|
|
||||||
- [Lenovo ThinkPad X200 / X200S / X200 Tablet](x200.md)
|
- [Lenovo ThinkPad X200 / X200S / X200 Tablet](x200.md)
|
||||||
- [Lenovo Thinkpad X220](../install/ivy_has_common.md)
|
- [Lenovo Thinkpad X220](../install/ivy_has_common.md)
|
||||||
- [Lenovo Thinkpad X220t](../install/ivy_has_common.md)
|
- [Lenovo Thinkpad X220t](../install/ivy_has_common.md)
|
||||||
- Lenovo ThinkPad X230
|
|
||||||
- [Lenovo Thinkpad X230](../install/x230_external.md)
|
- [Lenovo Thinkpad X230](../install/x230_external.md)
|
||||||
- [Lenovo Thinkpad X230t](../install/x230_external.md)
|
- [Lenovo Thinkpad X230t](../install/x230_external.md)
|
||||||
- Lenovo ThinkPad X301
|
- Lenovo ThinkPad X301
|
||||||
- Lenovo ThinkPad X60 / X60S / X60 Tablet (**easy to flash without disassembly**)
|
- Lenovo ThinkPad X60 / X60S / X60 Tablet
|
||||||
|
|
||||||
### Laptops (ARM, with U-Boot payload)
|
### Laptops (ARM, with U-Boot payload)
|
||||||
|
|
||||||
|
@ -107,7 +113,6 @@ re-adding them at a later date. They were removed due to issues. List:
|
||||||
- [Hisense Chromebook C11 and more (veyron-jerry)](../install/chromebooks.md)
|
- [Hisense Chromebook C11 and more (veyron-jerry)](../install/chromebooks.md)
|
||||||
- [HP Chromebook 11 G1 (daisy-spring)](../install/chromebooks.md)
|
- [HP Chromebook 11 G1 (daisy-spring)](../install/chromebooks.md)
|
||||||
- [HP Chromebook 14 G3 (nyan-blaze)](../install/chromebooks.md)
|
- [HP Chromebook 14 G3 (nyan-blaze)](../install/chromebooks.md)
|
||||||
- [Intel D945GCLF](d945gclf.md) (removed from lbmk, TODO: re-add support)
|
|
||||||
- [Samsung Chromebook 2 11" (peach-pit)](../install/chromebooks.md)
|
- [Samsung Chromebook 2 11" (peach-pit)](../install/chromebooks.md)
|
||||||
- [Samsung Chromebook 2 13" (peach-pi)](../install/chromebooks.md)
|
- [Samsung Chromebook 2 13" (peach-pi)](../install/chromebooks.md)
|
||||||
- [Samsung Chromebook XE303 (daisy-snow)](../install/chromebooks.md)
|
- [Samsung Chromebook XE303 (daisy-snow)](../install/chromebooks.md)
|
||||||
|
@ -161,9 +166,12 @@ libreboot, so we don't actually provide that, but if you still have
|
||||||
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
||||||
will update both the BIOS and EC version. See:
|
will update both the BIOS and EC version. See:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
||||||
update the EC firmware while running libreboot is unknown. libreboot
|
update the EC firmware while running libreboot is unknown. libreboot
|
||||||
only replaces the BIOS firmware, not EC.
|
only replaces the BIOS firmware, not EC.
|
||||||
|
|
|
@ -3,6 +3,22 @@ title: 兼容硬件列表
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
**[安装之前请先阅读这些指示](../../news/safety.md),否则你的机器可能会变砖:[安全措施](../../news/safety.md)**
|
**[安装之前请先阅读这些指示](../../news/safety.md),否则你的机器可能会变砖:[安全措施](../../news/safety.md)**
|
||||||
|
|
||||||
这一部分说明了 libreboot 已知兼容的硬件。
|
这一部分说明了 libreboot 已知兼容的硬件。
|
||||||
|
@ -34,24 +50,40 @@ x-toc-enable: true
|
||||||
|
|
||||||
### Desktops (AMD, Intel, x86)
|
### Desktops (AMD, Intel, x86)
|
||||||
|
|
||||||
|
- **Dell OptiPlex 7020/9020 MT and SFF (no guides yet) - [Available to buy
|
||||||
|
with Libreboot preinstalled](https://minifree.org/product/libreboot-9020/)**
|
||||||
- [Acer G43T-AM3](acer_g43t-am3.md)
|
- [Acer G43T-AM3](acer_g43t-am3.md)
|
||||||
- [Apple iMac 5,2](imac52.md)
|
- [Apple iMac 5,2](imac52.md)
|
||||||
- [ASUS KCMA-D8 主板](kcma-d8.md)
|
- [ASUS KCMA-D8 主板](kcma-d8.md)
|
||||||
|
- Dell OptiPlex 7010 **MT** (known to work, using the T1650 ROM, but more
|
||||||
|
research is needed)
|
||||||
- [Dell Precision T1650](t1650.md)
|
- [Dell Precision T1650](t1650.md)
|
||||||
- [Gigabyte GA-G41M-ES2L 主板](ga-g41m-es2l.md)
|
- [Gigabyte GA-G41M-ES2L 主板](ga-g41m-es2l.md)
|
||||||
- [HP Elite 8200 SFF/MT](hp8200sff.md)(HP 6200 Pro Business 多半也能用)
|
- [HP Elite 8200 SFF/MT](hp8200sff.md)(HP 6200 Pro Business 多半也能用)
|
||||||
- [HP Elite 8300 USDT](hp8300usdt.md)
|
- [HP Elite 8300 USDT](hp8300usdt.md)
|
||||||
- [Intel D510MO 及 D410PT 主板](d510mo.md)
|
- [Intel D510MO 及 D410PT 主板](d510mo.md)
|
||||||
|
- [Intel D945GCLF](d945gclf.md)(移出 lbmk,计划:重新加入支持)
|
||||||
|
|
||||||
### 笔记本(Intel,x86)
|
### 笔记本(Intel,x86)
|
||||||
|
|
||||||
|
- **[Lenovo ThinkPad T440p](../install/t440p_external.md) - Also [available
|
||||||
|
to buy with Libreboot preinstalled](https://minifree.org/product/libreboot-t440p/)**
|
||||||
|
- **[Lenovo ThinkPad W541](../install/ivy_has_common.md) - Also [available to
|
||||||
|
buy with Libreboot preinstalled](https://minifree.org/product/libreboot-w541/)**
|
||||||
|
- Lenovo ThinkPad X230 - *Also* available on Minifree: <https://minifree.org/product/libreboot-x230/>
|
||||||
- [Apple MacBook1,1 及 MacBook2,1](macbook21.md)
|
- [Apple MacBook1,1 及 MacBook2,1](macbook21.md)
|
||||||
- [Dell Latitude E6400, E6400 XFR 及 E6400 ATG,皆支持 Nvidia 或 Intel GPU](e6400.md) **(刷入简单,无需拆解,硬件类似 X200/T400)**
|
- [Dell Latitude E6400, E6400 XFR 及 E6400 ATG,皆支持 Nvidia 或 Intel GPU](e6400.md)
|
||||||
- [Dell Latitude E6430, Intel GPU](e6430.md) **(刷入简单,无需拆解)**
|
- Dell Latitude E6420 (Intel GPU) - no guide yet.
|
||||||
|
- [Dell Latitude E6430, Intel GPU](e6430.md)
|
||||||
|
- Dell Latitude E5530 (Intel GPU) - no guide yet.
|
||||||
|
- Dell Latitude E6520 (Intel GPU) - no guide yet.
|
||||||
- [HP EliteBook 2170p](hp2170p.md)
|
- [HP EliteBook 2170p](hp2170p.md)
|
||||||
- [HP EliteBook 2560p](hp2560p.md)
|
- [HP EliteBook 2560p](hp2560p.md)
|
||||||
- [HP EliteBook 2570p](hp2570p.md)
|
- [HP EliteBook 2570p](hp2570p.md)
|
||||||
|
- [HP EliteBook 820 G2](hp820g2.md)
|
||||||
|
- [HP EliteBook 8460p](hp8460p.md)
|
||||||
- [HP EliteBook 8470p](hp8470p.md)
|
- [HP EliteBook 8470p](hp8470p.md)
|
||||||
|
- [HP EliteBook 8560w](hp8560w.md)
|
||||||
- [HP EliteBook Folio 9470m](hp9470m.md)
|
- [HP EliteBook Folio 9470m](hp9470m.md)
|
||||||
- [Lenovo ThinkPad R400](r400.md)
|
- [Lenovo ThinkPad R400](r400.md)
|
||||||
- [Lenovo ThinkPad R500](r500.md)
|
- [Lenovo ThinkPad R500](r500.md)
|
||||||
|
@ -59,16 +91,13 @@ x-toc-enable: true
|
||||||
- [Lenovo Thinkpad T420](../install/ivy_has_common.md)(暂无安装文档)
|
- [Lenovo Thinkpad T420](../install/ivy_has_common.md)(暂无安装文档)
|
||||||
- [Lenovo ThinkPad T420S](../install/ivy_has_common.md)(暂无安装文档)
|
- [Lenovo ThinkPad T420S](../install/ivy_has_common.md)(暂无安装文档)
|
||||||
- [Lenovo ThinkPad T430](../install/ivy_has_common.md)(暂无安装文档)
|
- [Lenovo ThinkPad T430](../install/ivy_has_common.md)(暂无安装文档)
|
||||||
- [Lenovo ThinkPad T440p](../install/t440p_external.md)
|
|
||||||
- [Lenovo ThinkPad T500](t500.md)
|
- [Lenovo ThinkPad T500](t500.md)
|
||||||
- [Lenovo ThinkPad T530 / W530](../install/ivy_has_common.md)(暂无安装文档)
|
- [Lenovo ThinkPad T530 / W530](../install/ivy_has_common.md)(暂无安装文档)
|
||||||
- Lenovo ThinkPad T60(Intel GPU 款)
|
- Lenovo ThinkPad T60(Intel GPU 款)
|
||||||
- [Lenovo ThinkPad W500](t500.md)
|
- [Lenovo ThinkPad W500](t500.md)
|
||||||
- [Lenovo ThinkPad W541](../install/ivy_has_common.md)(暂无安装文档)
|
|
||||||
- [Lenovo ThinkPad X200 / X200S / X200 Tablet](x200.md)
|
- [Lenovo ThinkPad X200 / X200S / X200 Tablet](x200.md)
|
||||||
- [Lenovo Thinkpad X220](../install/ivy_has_common.md)
|
- [Lenovo Thinkpad X220](../install/ivy_has_common.md)
|
||||||
- [Lenovo Thinkpad X220t](../install/ivy_has_common.md)
|
- [Lenovo Thinkpad X220t](../install/ivy_has_common.md)
|
||||||
- Lenovo ThinkPad X230
|
|
||||||
- [Lenovo Thinkpad X230](../install/x230_external.md)
|
- [Lenovo Thinkpad X230](../install/x230_external.md)
|
||||||
- [Lenovo Thinkpad X230t](../install/x230_external.md)
|
- [Lenovo Thinkpad X230t](../install/x230_external.md)
|
||||||
- Lenovo ThinkPad X301
|
- Lenovo ThinkPad X301
|
||||||
|
@ -93,7 +122,6 @@ x-toc-enable: true
|
||||||
- [ASUS Chromebit CS10 (veyron-mickey)](../install/chromebooks.md)
|
- [ASUS Chromebit CS10 (veyron-mickey)](../install/chromebooks.md)
|
||||||
- [ASUS Chromebook Flip C100PA (veyron-minnie)](../install/chromebooks.md)
|
- [ASUS Chromebook Flip C100PA (veyron-minnie)](../install/chromebooks.md)
|
||||||
- [ASUS Chromebook C201PA (veyron-speedy)](../install/c201.md)
|
- [ASUS Chromebook C201PA (veyron-speedy)](../install/c201.md)
|
||||||
- [Intel D945GCLF](d945gclf.md)(移出 lbmk,计划:重新加入支持)
|
|
||||||
|
|
||||||
### 关于已移除的主板
|
### 关于已移除的主板
|
||||||
|
|
||||||
|
@ -122,9 +150,12 @@ d945gclf:据上次报告,根本无法启动。D510MO 仍在 lbmk 中,但
|
||||||
|
|
||||||
建议更新到最新 EC 固件版本。[EC 固件](../../faq.md#ec-embedded-controller-firmware) 与 libreboot 是独立的,所以我们实际上并不会提供这些固件,但如果你仍还有 Lenovo BIOS,那你可以直接运行 Lenovo BIOS 更新工具,它会同时更新 BIOS 和 EC 版本。见:
|
建议更新到最新 EC 固件版本。[EC 固件](../../faq.md#ec-embedded-controller-firmware) 与 libreboot 是独立的,所以我们实际上并不会提供这些固件,但如果你仍还有 Lenovo BIOS,那你可以直接运行 Lenovo BIOS 更新工具,它会同时更新 BIOS 和 EC 版本。见:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
注意:只有在运行 Lenovo BIOS 的时候,你才能这样做。如何在运行 libreboot 的时候更新 EC 固件尚不清楚。libreboot 只会替换 BIOS 固件,而不会替换 EC。
|
注意:只有在运行 Lenovo BIOS 的时候,你才能这样做。如何在运行 libreboot 的时候更新 EC 固件尚不清楚。libreboot 只会替换 BIOS 固件,而不会替换 EC。
|
||||||
|
|
||||||
更新的 EC 固件有一些好处,例如电池管理更加好。
|
更新的 EC 固件有一些好处,例如电池管理更加好。
|
||||||
|
|
|
@ -3,6 +3,8 @@ title: ASUS KCMA-D8 desktop/workstation board
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
TODO: this page is OLD. check that the info is still valid.
|
||||||
|
|
||||||
Introduction
|
Introduction
|
||||||
============
|
============
|
||||||
|
|
||||||
|
@ -149,7 +151,7 @@ Current issues {#issues}
|
||||||
|
|
||||||
- Opteron 4100 series CPUs are currently incompatible
|
- Opteron 4100 series CPUs are currently incompatible
|
||||||
- LRDIMM memory modules are currently incompatible
|
- LRDIMM memory modules are currently incompatible
|
||||||
(use UDIMMs please)
|
(use UDIMMs please) - NOTE: might actually work nowadays.
|
||||||
- Memory initialization is still problematic for some modules. We
|
- Memory initialization is still problematic for some modules. We
|
||||||
recommend avoiding Kingston and Super Talent modules for this reason.
|
recommend avoiding Kingston and Super Talent modules for this reason.
|
||||||
|
|
||||||
|
@ -157,11 +159,6 @@ The coreboot wiki has some information about RAM compatibility. The wiki is
|
||||||
deprecated but the info on it is still correct for this board. Some other
|
deprecated but the info on it is still correct for this board. Some other
|
||||||
considerations:
|
considerations:
|
||||||
|
|
||||||
- Booting from USB mass storage devices is currently broken under GRUB.
|
|
||||||
Consequently, the textmode ROM with SeaBIOS is recommended otherwise
|
|
||||||
in order to install an operating system you will need a hard disk with
|
|
||||||
a pre-installed OS or will have to plug in another HDD or CD/DVD
|
|
||||||
reader in order to boot OS installation media.
|
|
||||||
- SeaBIOS lacked serial console support out-of-the-box in release 20160907
|
- SeaBIOS lacked serial console support out-of-the-box in release 20160907
|
||||||
and as such a workaround using SGABIOS is necessary. You can find
|
and as such a workaround using SGABIOS is necessary. You can find
|
||||||
instructions on how to do this on the
|
instructions on how to do this on the
|
||||||
|
|
|
@ -52,7 +52,10 @@ This is a server board using AMD hardware (Fam10h). It can also be used
|
||||||
for building a high-powered workstation. Powered by libreboot.
|
for building a high-powered workstation. Powered by libreboot.
|
||||||
|
|
||||||
Flashing instructions can be found at
|
Flashing instructions can be found at
|
||||||
[../install/\#flashrom](../install/)
|
[../install/\#flashprog](../install/)
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Form factor {#formfactor}
|
Form factor {#formfactor}
|
||||||
===========
|
===========
|
||||||
|
|
|
@ -3,6 +3,8 @@ title: ASUS KGPE-D16 server/workstation board
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
TODO: OLD page. TODO: check that all the info is still valid.
|
||||||
|
|
||||||
Introduction
|
Introduction
|
||||||
============
|
============
|
||||||
|
|
||||||
|
@ -17,7 +19,7 @@ recommend avoiding Kingston modules.*
|
||||||
*For working configurations see <https://www.coreboot.org/Board:asus/kgpe-d16>.*
|
*For working configurations see <https://www.coreboot.org/Board:asus/kgpe-d16>.*
|
||||||
|
|
||||||
Flashing instructions can be found at
|
Flashing instructions can be found at
|
||||||
[../install/\#flashrom](../install/#flashrom) - note that external
|
[../install/\#flashprog](../install/#flashprog) - note that external
|
||||||
flashing is required, if the proprietary (ASUS) firmware is
|
flashing is required, if the proprietary (ASUS) firmware is
|
||||||
currently installed. If you already have libreboot, by default it is
|
currently installed. If you already have libreboot, by default it is
|
||||||
possible to re-flash using software running in Linux on the
|
possible to re-flash using software running in Linux on the
|
||||||
|
@ -79,6 +81,7 @@ Current issues {#issues}
|
||||||
==============
|
==============
|
||||||
|
|
||||||
- LRDIMM memory modules are currently incompatible
|
- LRDIMM memory modules are currently incompatible
|
||||||
|
(IT MAY WORK NOWADAYS, TODO TEST)
|
||||||
- SAS (via PIKE 2008 module) requires a vendor option ROM (and
|
- SAS (via PIKE 2008 module) requires a vendor option ROM (and
|
||||||
SeaBIOS) to boot from it (theoretically possible to replace, but you
|
SeaBIOS) to boot from it (theoretically possible to replace, but you
|
||||||
can put a kernel in CBFS or on SATA and boot from that, which
|
can put a kernel in CBFS or on SATA and boot from that, which
|
||||||
|
|
|
@ -85,7 +85,7 @@ For the MacBook2,1:
|
||||||
working)*
|
working)*
|
||||||
* MA701LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
|
* MA701LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
|
||||||
working)*
|
working)*
|
||||||
* MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 (untested)
|
* MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 *(tested -
|
||||||
* MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
|
* MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
|
||||||
working)*
|
working)*
|
||||||
* MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 *(tested - working)*
|
* MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 *(tested - working)*
|
||||||
|
@ -103,7 +103,10 @@ Internal flashing
|
||||||
|
|
||||||
MacBook2,1 can always be flashed internally, even if running Apple firmware:
|
MacBook2,1 can always be flashed internally, even if running Apple firmware:
|
||||||
|
|
||||||
sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w your.rom
|
sudo flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w your.rom
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
The MacBook1,1 can't be flashed internally if running the Apple EFI firmware.
|
The MacBook1,1 can't be flashed internally if running the Apple EFI firmware.
|
||||||
You must flash externally.
|
You must flash externally.
|
||||||
|
|
|
@ -77,7 +77,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
|
||||||
(contains notes, plus instructions)
|
(contains notes, plus instructions)
|
||||||
|
|
||||||
Flashing instructions can be found at
|
Flashing instructions can be found at
|
||||||
[../install/\#flashrom](../install/#flashrom)
|
[../install/\#flashprog](../install/#flashprog)
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
EC update {#ecupdate}
|
EC update {#ecupdate}
|
||||||
=========
|
=========
|
||||||
|
@ -88,7 +91,7 @@ libreboot, so we don't actually provide that, but if you still have
|
||||||
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
||||||
will update both the BIOS and EC version. See:
|
will update both the BIOS and EC version. See:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
|
|
||||||
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
||||||
|
|
|
@ -17,15 +17,15 @@ OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
| **Name** | Precision T1650 |
|
| **Name** | Precision T1650 |
|
||||||
| **Variants** | Precision T1650 |
|
| **Variants** | Precision T1650 |
|
||||||
| **Released** | 2012 |
|
| **Released** | 2012 |
|
||||||
| **Chipset** | Intel QM77 |
|
| **Chipset** | Intel C216 |
|
||||||
| **CPU** | Intel Ivy Bridge |
|
| **CPU** | Intel Ivy Bridge |
|
||||||
| **Graphics** | Discrete graphics, or Intel HD Graphics model
|
| **Graphics** | Discrete graphics, or Intel HD Graphics model
|
||||||
depending on CPU model |
|
depending on CPU model |
|
||||||
| **Memory** | DDR3 DIMMs (max 32GB, 2x16GB), ECC memory supported |
|
| **Memory** | DDR3 DIMMs (max 32GB, 4x8GB), ECC memory supported |
|
||||||
| **Architecture** | x86_64 |
|
| **Architecture** | x86_64 |
|
||||||
| **Original boot firmware** | Dell UEFI firmware |
|
| **Original boot firmware** | Dell UEFI firmware |
|
||||||
| **Intel ME/AMD PSP** | Present. Can be disabled with me_cleaner. |
|
| **Intel ME/AMD PSP** | Present. Can be disabled with me_cleaner. |
|
||||||
| **Flash chip** | SOIC-16 16MiB (128Mbit) |
|
| **Flash chip** | SOIC-16 and/or SOIC-8 12MiB (96Mbit) |
|
||||||
|
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
|
@ -76,7 +76,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
|
||||||
(contains notes, plus instructions)
|
(contains notes, plus instructions)
|
||||||
|
|
||||||
Flashing instructions can be found at
|
Flashing instructions can be found at
|
||||||
[../install/\#flashrom](../install/#flashrom)
|
[../install/\#flashprog](../install/#flashprog)
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
EC update {#ecupdate}
|
EC update {#ecupdate}
|
||||||
=========
|
=========
|
||||||
|
@ -87,7 +90,7 @@ libreboot, so we don't actually provide that, but if you still have
|
||||||
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
||||||
will update both the BIOS and EC version. See:
|
will update both the BIOS and EC version. See:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
|
|
||||||
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
||||||
|
|
|
@ -78,7 +78,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
|
||||||
(contains notes, plus instructions)
|
(contains notes, plus instructions)
|
||||||
|
|
||||||
Flashing instructions can be found at
|
Flashing instructions can be found at
|
||||||
[../install/\#flashrom](../install/#flashrom)
|
[../install/\#flashprog](../install/#flashprog)
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
EC update {#ecupdate}
|
EC update {#ecupdate}
|
||||||
=========
|
=========
|
||||||
|
@ -89,7 +92,7 @@ libreboot, so we don't actually provide that, but if you still have
|
||||||
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
||||||
will update both the BIOS and EC version. See:
|
will update both the BIOS and EC version. See:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
|
|
||||||
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
NOTE: this can only be done when you are using Lenovo BIOS. How to
|
||||||
|
|
|
@ -76,7 +76,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
|
||||||
(contains notes, plus instructions)
|
(contains notes, plus instructions)
|
||||||
|
|
||||||
Flashing instructions can be found at
|
Flashing instructions can be found at
|
||||||
[../install/\#flashrom](../install/#flashrom)
|
[../install/\#flashprog](../install/#flashprog)
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
EC update {#ecupdate}
|
EC update {#ecupdate}
|
||||||
=========
|
=========
|
||||||
|
@ -87,7 +90,7 @@ libreboot, so we don't actually provide that, but if you still have
|
||||||
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
|
||||||
will update both the BIOS and EC version. See:
|
will update both the BIOS and EC version. See:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
- [X200, X200s, X200si BIOS Update](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x200/downloads/ds015007)
|
- [X200, X200s, X200si BIOS Update](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x200/downloads/ds015007)
|
||||||
- [X200t BIOS Update](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/thinkpad-x200-tablet/downloads/ds018814)
|
- [X200t BIOS Update](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/thinkpad-x200-tablet/downloads/ds018814)
|
||||||
|
|
|
@ -69,7 +69,10 @@ X200S та X201S; знову ж таки, це неперевірено. *Шви
|
||||||
(містить примітки та інструкції)
|
(містить примітки та інструкції)
|
||||||
|
|
||||||
Інструкції з перепрошивки можна знайти за адресою
|
Інструкції з перепрошивки можна знайти за адресою
|
||||||
[../install/\#flashrom](../install/#flashrom)
|
[../install/\#flashprog](../install/#flashprog)
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Оновлення EC {#ecupdate}
|
Оновлення EC {#ecupdate}
|
||||||
=========
|
=========
|
||||||
|
@ -80,7 +83,7 @@ libreboot, тому ми її фактично не надаємо, але як
|
||||||
Lenovo BIOS, ви можете просто запустити утиліту оновлення BIOS Lenovo, яка
|
Lenovo BIOS, ви можете просто запустити утиліту оновлення BIOS Lenovo, яка
|
||||||
оновить як BIOS, так і версію EC. Дивіться:
|
оновить як BIOS, так і версію EC. Дивіться:
|
||||||
|
|
||||||
- [../install/#flashrom](../install/#flashrom)
|
- [../install/#flashprog](../install/#flashprog)
|
||||||
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
|
||||||
- [Оновлення BIOS X200, X200s, X200i](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x200/downloads/ds015007)
|
- [Оновлення BIOS X200, X200s, X200i](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x200/downloads/ds015007)
|
||||||
- [Оновлення BIOS X200t](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/thinkpad-x200-tablet/downloads/ds018814)
|
- [Оновлення BIOS X200t](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/thinkpad-x200-tablet/downloads/ds018814)
|
||||||
|
|
|
@ -8,6 +8,19 @@ the [main news section](../news/).
|
||||||
|
|
||||||
[Answers to Frequently Asked Questions about libreboot](../faq.md).
|
[Answers to Frequently Asked Questions about libreboot](../faq.md).
|
||||||
|
|
||||||
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
Installing libreboot
|
Installing libreboot
|
||||||
====================
|
====================
|
||||||
|
|
||||||
|
|
|
@ -8,6 +8,19 @@ libreboot. Новини, включаючи оголошення про випу
|
||||||
|
|
||||||
[Відповіді на поширені запитання про libreboot](../faq.md).
|
[Відповіді на поширені запитання про libreboot](../faq.md).
|
||||||
|
|
||||||
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
Встановлення libreboot
|
Встановлення libreboot
|
||||||
====================
|
====================
|
||||||
|
|
||||||
|
|
|
@ -6,6 +6,19 @@ libreboot 的最新更新,可以在 [libreboot.org](https://libreboot.org) 上
|
||||||
|
|
||||||
[libreboot 常见问题解答](../faq.md).
|
[libreboot 常见问题解答](../faq.md).
|
||||||
|
|
||||||
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
安装 libreboot
|
安装 libreboot
|
||||||
====================
|
====================
|
||||||
|
|
||||||
|
|
|
@ -22,6 +22,10 @@ A special fork of flashrom, maintained by Google, is required for flashing.
|
||||||
More information about this is present in the generic [chromebook flashing
|
More information about this is present in the generic [chromebook flashing
|
||||||
instructions](chromebooks.md).
|
instructions](chromebooks.md).
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom, but the chromium fork
|
||||||
|
is another fork of flashrom, and you should use that on chromebooks.
|
||||||
|
|
||||||
Depthcharge payload (obsolete)
|
Depthcharge payload (obsolete)
|
||||||
------------------------------
|
------------------------------
|
||||||
|
|
||||||
|
|
|
@ -88,7 +88,7 @@ Chromebooks may have 1.8V as the supply voltage for the SPI NOR chip, be
|
||||||
extra careful about that.
|
extra careful about that.
|
||||||
|
|
||||||
On newer Chromebooks, there is a root-of-trust chip providing a
|
On newer Chromebooks, there is a root-of-trust chip providing a
|
||||||
[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_cr50.md)
|
[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md)
|
||||||
mechanism that lets you flash externally using a special USB debugging
|
mechanism that lets you flash externally using a special USB debugging
|
||||||
cable. However, most boards that Libreboot supports do not have this.
|
cable. However, most boards that Libreboot supports do not have this.
|
||||||
|
|
||||||
|
@ -109,7 +109,7 @@ by the fact that it bridges electrical contacts, but finding and
|
||||||
removing it might require you to disassemble most of the board.
|
removing it might require you to disassemble most of the board.
|
||||||
|
|
||||||
Newer boards have a root-of-trust chip enforcing write-protection. The
|
Newer boards have a root-of-trust chip enforcing write-protection. The
|
||||||
[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_cr50.md)
|
[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md)
|
||||||
mechanism should be used to disable hardware write-protection. Opening
|
mechanism should be used to disable hardware write-protection. Opening
|
||||||
the case and disconnecting the battery might also disable it.
|
the case and disconnecting the battery might also disable it.
|
||||||
|
|
||||||
|
@ -151,7 +151,7 @@ first (like Intel ME firmware). This is not yet documented here.
|
||||||
|
|
||||||
You can flash the ROM image both internally and externally. For the
|
You can flash the ROM image both internally and externally. For the
|
||||||
latter, see the [external flashing guide](spi.md) and the ChromiumOS
|
latter, see the [external flashing guide](spi.md) and the ChromiumOS
|
||||||
[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_cr50.md)
|
[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md)
|
||||||
documentation if your board supports it.
|
documentation if your board supports it.
|
||||||
|
|
||||||
To flash the entire ROM image internally, run within ChromeOS:
|
To flash the entire ROM image internally, run within ChromeOS:
|
||||||
|
|
|
@ -12,7 +12,10 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Flashing instructions {#clip}
|
Flashing instructions {#clip}
|
||||||
=====================
|
=====================
|
||||||
|
|
|
@ -2,10 +2,6 @@
|
||||||
title: Intel D945GCLF flashing tutorial
|
title: Intel D945GCLF flashing tutorial
|
||||||
...
|
...
|
||||||
|
|
||||||
NOTE: On newer Libreboot revisions, boot issues were reported so this board
|
|
||||||
was temporarily removed. It will be re-added at a later date, after testing
|
|
||||||
has been done.
|
|
||||||
|
|
||||||
This guide is for those who want libreboot on their Intel D945GCLF
|
This guide is for those who want libreboot on their Intel D945GCLF
|
||||||
motherboard while they still have the original BIOS present.
|
motherboard while they still have the original BIOS present.
|
||||||
|
|
||||||
|
|
|
@ -68,7 +68,7 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
We believe most/all are 4MB (32Mb) flash sizes, but larger ROM images are
|
We believe most/all are 4MB (32Mb) flash sizes, but larger ROM images are
|
||||||
provided for people who wish to upgrade.
|
provided for people who wish to upgrade.
|
||||||
|
@ -104,6 +104,19 @@ variants with Intel graphics.
|
||||||
For Intel GPU variants, Libreboot 20230423 and up have full support. Simply
|
For Intel GPU variants, Libreboot 20230423 and up have full support. Simply
|
||||||
flash a release ROM, if you wish.
|
flash a release ROM, if you wish.
|
||||||
|
|
||||||
|
Intel GPU errata
|
||||||
|
----------------
|
||||||
|
|
||||||
|
Systems with a 1440 x 900 display panel instead of the more common 1280 x 800
|
||||||
|
panel will have garbled graphics before the OS boots (i.e. in SeaBIOS or GRUB)
|
||||||
|
in Libreboot 20240504 and earlier. This is fixed in releases after 20240504.
|
||||||
|
|
||||||
|
This was caused by libgfxinit calculating PLL divider values for the pixel clock
|
||||||
|
assuming a 96 MHz reference frequency, whereas the E6400 uses a 100 MHz
|
||||||
|
reference frequency. The error is not large enough to affect the lower
|
||||||
|
resolution panels, but is enough to affect the 1440 x 900 panels which use a
|
||||||
|
higher pixel clock.
|
||||||
|
|
||||||
Nvidia GPU: Video BIOS Option ROM required
|
Nvidia GPU: Video BIOS Option ROM required
|
||||||
==========================================
|
==========================================
|
||||||
|
|
||||||
|
@ -119,17 +132,15 @@ build target `e6400_4mb` - either build from source and it gets inserted
|
||||||
automatically, or you can [insert it
|
automatically, or you can [insert it
|
||||||
manually](ivy_has_common.md) on future release ROMs past Libreboot 20230625.
|
manually](ivy_has_common.md) on future release ROMs past Libreboot 20230625.
|
||||||
|
|
||||||
An earlier experimental revision existed in the `e6400nvidia_wip` branch of
|
An earlier experimental revision existed in an experimental branch of
|
||||||
lbmk, as build target `e6400nvidia_4mb`, but it was decided that since SeaBIOS
|
lbmk, as build target `e6400nvidia_4mb`, but it was decided that since SeaBIOS
|
||||||
is the only payload anyway on this board, having just a single build target is
|
is the only payload anyway on this board, having just a single build target is
|
||||||
more efficient if that can (and it does) support both variants.
|
more efficient if that can (and it does) support both variants. It was therefore
|
||||||
|
added to the master branch.
|
||||||
|
|
||||||
Actual installation is the same as with regular E6400 (Intel GPU) variants.
|
Actual installation is the same as with regular E6400 (Intel GPU) variants.
|
||||||
Refer to the [E6400 flashing instructions](../docs/install/e6400.md).
|
Refer to the [E6400 flashing instructions](../docs/install/e6400.md).
|
||||||
|
|
||||||
The `e6400nvidia_wip` branch is obsolete, and it is merely referenced for
|
|
||||||
historical purposes.
|
|
||||||
|
|
||||||
Problems with Linux video drivers on Nvidia
|
Problems with Linux video drivers on Nvidia
|
||||||
-------------------------------------------
|
-------------------------------------------
|
||||||
|
|
||||||
|
@ -160,29 +171,12 @@ codeberg](https://codeberg.org/libreboot/lbmk/issues/14#issuecomment-907758).
|
||||||
How to flash internally (no diassembly)
|
How to flash internally (no diassembly)
|
||||||
=======================================
|
=======================================
|
||||||
|
|
||||||
Warning for BSD users
|
|
||||||
---------------------
|
|
||||||
|
|
||||||
**NOTE (15 October 2023): The util is now called `dell-flash-unlock`, but it
|
|
||||||
was previously called `e6400-flash-unlock`. Links have been updated.**
|
|
||||||
|
|
||||||
BSD *boots* and works properly on these machines, but take note:
|
|
||||||
|
|
||||||
Nicholas's [dell-flash-unlock](https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/dell_flash_unlock.c)
|
|
||||||
utility has been ported to OpenBSD, but *other* BSDs are assumed unsupported for
|
|
||||||
now. The `flashrom` software is available on BSD systems. Libreboot's build
|
|
||||||
system has *itself* not yet been ported to the BSDs, but you can use the
|
|
||||||
flash unlock utility.
|
|
||||||
|
|
||||||
NOTE: BSD is mentioned above, but the only BSD tested for `dell-flash-unlock`
|
|
||||||
is OpenBSD, as of 15 October 2023.
|
|
||||||
|
|
||||||
Flashing from Linux
|
Flashing from Linux
|
||||||
-------------------
|
-------------------
|
||||||
|
|
||||||
MAKE SURE you boot with this Linux kernel parameter: `iomem=relaxed` - this
|
MAKE SURE you boot with this Linux kernel parameter: `iomem=relaxed` - this
|
||||||
disables memory protections, permitting `/dev/mem` access needed by flashrom.
|
disables memory protections, permitting `/dev/mem` access needed by flashprog.
|
||||||
The flash is memory mapped and flashrom accesses it via `/dev/mem`.
|
The flash is memory mapped and flashprog accesses it via `/dev/mem`.
|
||||||
|
|
||||||
You can flash Libreboot directly from the vendor (Dell) BIOS, without taking
|
You can flash Libreboot directly from the vendor (Dell) BIOS, without taking
|
||||||
the machine apart. It can be done entirely from Linux. It will probably also
|
the machine apart. It can be done entirely from Linux. It will probably also
|
||||||
|
@ -218,18 +212,18 @@ Protected Range registers.
|
||||||
|
|
||||||
When you flash it, you can use this command:
|
When you flash it, you can use this command:
|
||||||
|
|
||||||
flashrom -p internal -w libreboot.rom
|
flashprog -p internal -w libreboot.rom
|
||||||
|
|
||||||
Where `libreboot.rom` is your E6400 ROM. *Make sure* it's the right one.
|
Where `libreboot.rom` is your E6400 ROM. *Make sure* it's the right one.
|
||||||
If flashrom complains about multiple flash chips detected, just pick one of
|
If flashprog complains about multiple flash chips detected, just pick one of
|
||||||
them (doesn't matter which one). On *most* Dell machines, the most correct
|
them (doesn't matter which one). On *most* Dell machines, the most correct
|
||||||
would probably be this option in flashrom: `-c MX25L3205D/MX25L3208D`.
|
would probably be this option in flashprog: `-c MX25L3205D/MX25L3208D`.
|
||||||
|
|
||||||
So:
|
So:
|
||||||
|
|
||||||
flashrom -p internal -w libreboot.rom -c MX25L3205D/MX25L3208D
|
flashprog -p internal -w libreboot.rom -c MX25L3205D/MX25L3208D
|
||||||
|
|
||||||
When you see flashrom say `VERIFIED` at the end, that means the flash was
|
When you see flashprog say `VERIFIED` at the end, that means the flash was
|
||||||
successful. If you don't see that, or you're unsure, please [contact the
|
successful. If you don't see that, or you're unsure, please [contact the
|
||||||
Libreboot project via IRC](../../contact.md).
|
Libreboot project via IRC](../../contact.md).
|
||||||
|
|
||||||
|
@ -239,7 +233,7 @@ BACK UP THE FACTORY BIOS
|
||||||
The `-w` option flashes `libreboot.rom`. You may consider *backing up* the
|
The `-w` option flashes `libreboot.rom`. You may consider *backing up* the
|
||||||
original Dell BIOS first, using the -r option:
|
original Dell BIOS first, using the -r option:
|
||||||
|
|
||||||
flashrom -p internal -r backup.rom -c MX25L3205D/MX25L3208D
|
flashprog -p internal -r backup.rom -c MX25L3205D/MX25L3208D
|
||||||
|
|
||||||
Do this while in a flashable state, after the 2nd run of `dell-flash-unlock`.
|
Do this while in a flashable state, after the 2nd run of `dell-flash-unlock`.
|
||||||
|
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: Flashing the Dell Latitude E6430
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
**NOTE:** This installation guide also pertains to E5520, E6420, E6520, E5530
|
||||||
|
and E6530.
|
||||||
|
|
||||||
Introduction
|
Introduction
|
||||||
============
|
============
|
||||||
|
|
||||||
|
@ -21,7 +24,7 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
The internal flash size is 12MiB on this board; physically, an 8MiB and 4MiB
|
The internal flash size is 12MiB on this board; physically, an 8MiB and 4MiB
|
||||||
chip (two chips) but this distinction only matters for external flashing.
|
chip (two chips) but this distinction only matters for external flashing.
|
||||||
|
@ -38,12 +41,12 @@ Refer to [mac\_address.md](../hardware/mac_address.md).
|
||||||
|
|
||||||
It is recommended that you run *nvmutil*. See:
|
It is recommended that you run *nvmutil*. See:
|
||||||
|
|
||||||
[nvmutil usage manual](nvmutil.md)
|
[nvmutil usage manual](nvmutil.md) - E5530 users don't need to run this.
|
||||||
|
|
||||||
The `nvmutil` software is specifically designed for changing MAC addresses,
|
The `nvmutil` software is specifically designed for changing MAC addresses,
|
||||||
and it implements a few more safeguards (e.g. prevents multicast/all-zero
|
and it implements a few more safeguards (e.g. prevents multicast/all-zero
|
||||||
MAC addresses) and features (MAC address randomisation, ability to correct or
|
MAC addresses) and features (MAC address randomisation, ability to correct or
|
||||||
intententionally corrupt(disable) GbE sections if you wish, swap GbE parts,
|
intentionally corrupt(disable) GbE sections if you wish, swap GbE parts,
|
||||||
etc). - **it is also the only software available for this. Please do not
|
etc). - **it is also the only software available for this. Please do not
|
||||||
use ich9gen on this board. This is an ivybridge board, not ICH9M.**
|
use ich9gen on this board. This is an ivybridge board, not ICH9M.**
|
||||||
|
|
||||||
|
@ -79,9 +82,10 @@ BSD *boots* and works properly on these machines, but take note:
|
||||||
|
|
||||||
Nicholas's [dell-flash-unlock](https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/dell_flash_unlock.c)
|
Nicholas's [dell-flash-unlock](https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/dell_flash_unlock.c)
|
||||||
utility has been ported to OpenBSD, but *other* BSDs are assumed unsupported for
|
utility has been ported to OpenBSD, but *other* BSDs are assumed unsupported for
|
||||||
now. The `flashrom` software is available on BSD systems. Libreboot's build
|
now.
|
||||||
system has *itself* not yet been ported to the BSDs, but you can use the
|
|
||||||
flash unlock utility.
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
NOTE: BSD is mentioned above, but the only BSD tested for `dell-flash-unlock`
|
NOTE: BSD is mentioned above, but the only BSD tested for `dell-flash-unlock`
|
||||||
is OpenBSD, as of 15 October 2023.
|
is OpenBSD, as of 15 October 2023.
|
||||||
|
@ -90,8 +94,8 @@ Flashing from Linux
|
||||||
-------------------
|
-------------------
|
||||||
|
|
||||||
MAKE SURE you boot with this Linux kernel parameter: `iomem=relaxed` - this
|
MAKE SURE you boot with this Linux kernel parameter: `iomem=relaxed` - this
|
||||||
disables memory protections, permitting `/dev/mem` access needed by flashrom.
|
disables memory protections, permitting `/dev/mem` access needed by flashprog.
|
||||||
The flash is memory mapped and flashrom accesses it via `/dev/mem`.
|
The flash is memory mapped and flashprog accesses it via `/dev/mem`.
|
||||||
|
|
||||||
You can flash Libreboot directly from the vendor (Dell) BIOS, without taking
|
You can flash Libreboot directly from the vendor (Dell) BIOS, without taking
|
||||||
the machine apart. It can be done entirely from Linux. It will probably also
|
the machine apart. It can be done entirely from Linux. It will probably also
|
||||||
|
@ -114,27 +118,28 @@ is included in that program's directory, or you can read it online here:
|
||||||
|
|
||||||
<https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/README.md>
|
<https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/README.md>
|
||||||
|
|
||||||
Literally just run that program, and do what it says. You run it once, and shut
|
Literally just run that program, and do what it says. You run it once, shut
|
||||||
down, and when you do, the system brings itself back up automatically. Then
|
down, and then power on the machine. Then run it again to confirm that the
|
||||||
you run it and flash it unlocked. Then you run it again. The source code is
|
flash is unlocked. The source code is intuitive enough that you can easily get
|
||||||
intuitive enough that you can easily get the gist of it; it's writing some EC
|
the gist of it; it's writing some EC commands and changing some chipset config
|
||||||
commands and changing some chipset config bits. The EC on this machine is
|
bits. The EC on this machine is hooked up to the `HDA_SDO` signal, also known
|
||||||
hooked up to the `GPIO33` signal, sometimes called `HDA_DOCK_EN`, which sets
|
as the Flash Descriptor Override (FDO), which disables any flash protection by
|
||||||
the flash descriptor override thus disabling any flash protection by the IFD.
|
the IFD. When booted with the FDO set, the original Dell firmware disables all
|
||||||
It also bypasses the SMM BIOS lock protection by disabling SMIs, and Dell's
|
other BIOS write protections such as SMM BIOS lock bits.
|
||||||
BIOS doesn't set any other type of protection either such as writing to
|
|
||||||
Protected Range registers.
|
*Make sure* to make a backup of the original firmware before proceeding to
|
||||||
|
flash; see the instructions below.
|
||||||
|
|
||||||
When you flash it, you can use this command:
|
When you flash it, you can use this command:
|
||||||
|
|
||||||
flashrom -p internal -w libreboot.rom
|
flashprog -p internal -w libreboot.rom
|
||||||
|
|
||||||
Where `libreboot.rom` is your E6430 ROM. *Make sure* it's the right one.
|
Where `libreboot.rom` is your E6430 ROM. *Make sure* it's the right one.
|
||||||
If flashrom complains about multiple flash chips detected, just pick one of
|
If flashprog complains about multiple flash chips detected, just pick one of
|
||||||
them (doesn't matter which one), with the `-C` flag as directed; just pick one,
|
them (doesn't matter which one), with the `-C` flag as directed; just pick one,
|
||||||
and if it doesn't work, try the next.
|
and if it doesn't work, try the next.
|
||||||
|
|
||||||
When you see flashrom say `VERIFIED` at the end, that means the flash was
|
When you see flashprog say `VERIFIED` at the end, that means the flash was
|
||||||
successful. If you don't see that, or you're unsure, please [contact the
|
successful. If you don't see that, or you're unsure, please [contact the
|
||||||
Libreboot project via IRC](../../contact.md).
|
Libreboot project via IRC](../../contact.md).
|
||||||
|
|
||||||
|
@ -144,10 +149,10 @@ BACK UP THE FACTORY BIOS
|
||||||
The `-w` option flashes `libreboot.rom`. You may consider *backing up* the
|
The `-w` option flashes `libreboot.rom`. You may consider *backing up* the
|
||||||
original Dell BIOS first, using the -r option:
|
original Dell BIOS first, using the -r option:
|
||||||
|
|
||||||
flashrom -p internal -r backup.rom
|
flashprog -p internal -r backup.rom
|
||||||
|
|
||||||
AGAIN: make sure to use `-C` accordingly, if you need to pick a chip (where
|
AGAIN: make sure to use `-C` accordingly, if you need to pick a chip (where
|
||||||
flashrom has detected multiple chip definitions). Just pick one, any of them
|
flashprog has detected multiple chip definitions). Just pick one, any of them
|
||||||
will probably work, if not try the next.
|
will probably work, if not try the next.
|
||||||
|
|
||||||
Do this while in a flashable state, after the 2nd run of `dell-flash-unlock`.
|
Do this while in a flashable state, after the 2nd run of `dell-flash-unlock`.
|
||||||
|
@ -163,11 +168,11 @@ How to flash externally
|
||||||
|
|
||||||
Refer to [spi.md](spi.md) as a guide for external re-flashing.
|
Refer to [spi.md](spi.md) as a guide for external re-flashing.
|
||||||
|
|
||||||
The SPI flash chip shares a voltage rail with the ICH9 southbridge, which is
|
The SPI flash chip shares a voltage rail with the chipset, which is not
|
||||||
not isolated using a diode. As a result, powering the flash chip externally
|
isolated using a diode. As a result, powering the flash chip externally may
|
||||||
causes the ICH9 to partially power up and attempt to drive the SPI clock pin
|
cause the QM77 chipset to partially power up and drive the SPI pins, which can
|
||||||
low, which can interfere with programmers such as the Raspberry Pi. See
|
interfere with programmers such as the Raspberry Pi. See [RPi Drive
|
||||||
[RPi Drive Strength](spi.md#rpi-drive-strength) for a workaround.
|
Strength](spi.md#rpi-drive-strength) for a workaround.
|
||||||
|
|
||||||
Have a look online for videos showing how to disassemble, if you wish to
|
Have a look online for videos showing how to disassemble, if you wish to
|
||||||
externally re-flash.
|
externally re-flash.
|
||||||
|
|
|
@ -22,7 +22,7 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
Flashing instructions {#clip}
|
Flashing instructions {#clip}
|
||||||
=====================
|
=====================
|
||||||
|
@ -52,11 +52,11 @@ Linux. There are 2 flash chips (one is backup).
|
||||||
|
|
||||||
Flash the first chip:
|
Flash the first chip:
|
||||||
|
|
||||||
./flashrom -p internal:dualbiosindex=0 -w libreboot.rom
|
./flashprog -p internal:dualbiosindex=0 -w libreboot.rom
|
||||||
|
|
||||||
Flash the second chip:
|
Flash the second chip:
|
||||||
|
|
||||||
./flashrom -p internal:dualbiosindex=1 -w libreboot.rom
|
./flashprog -p internal:dualbiosindex=1 -w libreboot.rom
|
||||||
|
|
||||||
NOTE: you can still boot the system with just the main flash chip
|
NOTE: you can still boot the system with just the main flash chip
|
||||||
connected, after desoldering the backup chip. This has been tested while
|
connected, after desoldering the backup chip. This has been tested while
|
||||||
|
@ -66,5 +66,5 @@ NOTE: If you don't flash both chips, the recovery program from the default
|
||||||
factory BIOS will kick in and your board will be soft bricked. Make sure that
|
factory BIOS will kick in and your board will be soft bricked. Make sure that
|
||||||
you flash both chips!
|
you flash both chips!
|
||||||
|
|
||||||
NOTE: You need the latest flashrom. Just get it on flashrom.org from
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
their SVN or Git repos.
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
|
@ -123,7 +123,7 @@ accomplish the same result of locking or unlocking a descriptor.**
|
||||||
These files contain the descriptor+GbE region and are suitable for systems
|
These files contain the descriptor+GbE region and are suitable for systems
|
||||||
that have an Intel GbE NIC present. The flash regions (as defined by the
|
that have an Intel GbE NIC present. The flash regions (as defined by the
|
||||||
Intel Flash Descriptor) are set *read-write* which means that you can also
|
Intel Flash Descriptor) are set *read-write* which means that you can also
|
||||||
re-flash using `flashrom -p internal` in your operating system running on
|
re-flash using `flashprog -p internal` in your operating system running on
|
||||||
that machine. This is the default setup used when libreboot's build system
|
that machine. This is the default setup used when libreboot's build system
|
||||||
compiles ROM images.
|
compiles ROM images.
|
||||||
|
|
||||||
|
@ -181,7 +181,7 @@ a Broadcom NIC for ethernet. In descriptorless mode, ICH9M works very similarly
|
||||||
to older ICH7 chipsets.
|
to older ICH7 chipsets.
|
||||||
|
|
||||||
Your libreboot.rom image is now ready to be flashed on the system. Refer
|
Your libreboot.rom image is now ready to be flashed on the system. Refer
|
||||||
back to [../install/\#flashrom](../install/#flashrom) for how to flash
|
back to [../install/\#flashprog](../install/#flashprog) for how to flash
|
||||||
it.
|
it.
|
||||||
|
|
||||||
Write-protecting the flash chip
|
Write-protecting the flash chip
|
||||||
|
@ -289,7 +289,7 @@ This takes a `factory.rom` dump and disables the ME/TPM, but leaves the
|
||||||
region intact. It also sets all regions read-write. Simply put, this means
|
region intact. It also sets all regions read-write. Simply put, this means
|
||||||
that you can use the original factory firmware but without the Intel ME enabled.
|
that you can use the original factory firmware but without the Intel ME enabled.
|
||||||
|
|
||||||
The ME interferes with flash read/write in flashrom, and the default
|
The ME interferes with flash read/write in flashprog, and the default
|
||||||
descriptor locks some regions. The idea is that doing this will remove
|
descriptor locks some regions. The idea is that doing this will remove
|
||||||
all of those restrictions.
|
all of those restrictions.
|
||||||
|
|
||||||
|
|
|
@ -3,34 +3,76 @@ title: Installation instructions
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
This section relates to installing libreboot on supported targets.
|
**SAFETY WARNING!**
|
||||||
|
|
||||||
NOTE: if running `flashrom -p internal` for software based flashing, and you
|
|
||||||
get an error related to `/dev/mem` access, you should reboot with
|
|
||||||
`iomem=relaxed` kernel parameter before running flashrom, or use a kernel that
|
|
||||||
has `CONFIG_STRICT_DEVMEM` not enabled.
|
|
||||||
|
|
||||||
READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
|
|
||||||
====================================================================
|
====================================================================
|
||||||
|
|
||||||
**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
|
LIBREBOOT](../../news/safety.md).**
|
||||||
the release ROMs of Libreboot are MISSING certain files, that you must insert
|
|
||||||
yourself. FAILURE to adhere to this warning may result in you bricking your
|
|
||||||
machine (rendering it unbootable), if you were to flash the release ROMs without
|
|
||||||
modifying them in any way. For more information, please read:**
|
|
||||||
|
|
||||||
**[Insert vendor files on Sandybridge/Ivybridge/Haswell](ivy_has_common.md)**
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
NOTE: This warning does not apply to ROMs that you compiled yourself, using
|
Help is available on [Libreboot IRC](../../contact.md) and other channels.
|
||||||
lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
|
|
||||||
in release ROMs. The link above says how to re-add them. When building ROM images
|
|
||||||
yourself, from source, Libreboot's build system automatically handles it. See:
|
|
||||||
[Libreboot build instructions](../build/)
|
|
||||||
|
|
||||||
This isn't required on *all* Libreboot-supported boards, but if in doubt, follow
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
these instructions anyway. If you run the vendor scripts on a board that doesn't
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
need vendor files, nothing will happen.
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
FLASH ERRORS (and workarounds)
|
||||||
|
=======================
|
||||||
|
|
||||||
|
**NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.**
|
||||||
|
|
||||||
|
This section relates to installing libreboot on supported targets.
|
||||||
|
|
||||||
|
Right out of the gate, some users may experience errors with flashprog when
|
||||||
|
using the internal programmer. They are:
|
||||||
|
|
||||||
|
/dev/mem access error
|
||||||
|
---------------------
|
||||||
|
|
||||||
|
NOTE: if running `flashprog -p internal` for software based flashing, and you
|
||||||
|
get an error related to `/dev/mem` access, you should reboot with
|
||||||
|
`iomem=relaxed` kernel parameter before running flashprog, or use a kernel that
|
||||||
|
has `CONFIG_STRICT_DEVMEM` not enabled.
|
||||||
|
|
||||||
|
On NetBSD and OpenBSD systems, the equivalent to `iomem=relaxed` in this case
|
||||||
|
is `kernel.securelevel=-1`; see [NetBSD securelevel
|
||||||
|
manual](https://wiki.netbsd.org/tutorials/kernel_secure_levels/)
|
||||||
|
and [OpenBSD securelevel manual](https://man.openbsd.org/securelevel).
|
||||||
|
|
||||||
|
ERROR: Could not get I/O privileges
|
||||||
|
------------------------------------
|
||||||
|
|
||||||
|
Error message: `ERROR: Could not get I/O privileges (Function not implemented)`
|
||||||
|
|
||||||
|
If you get this while running `flashprog -p internal -w filename.rom` (or any
|
||||||
|
internal flash operation), note: flashprog heavily uses ioperm/iopl functions
|
||||||
|
to operate the internal flasher, at least on x86 machines.
|
||||||
|
|
||||||
|
See: <https://lwn.net/Articles/804143/>
|
||||||
|
|
||||||
|
Yeah, just enable `CONFIG_X86_IOPL_IOPERM` in your Linux kernel. This is
|
||||||
|
a *build-time* option, so you must re-compile your kernel, or find a build that
|
||||||
|
has this option enabled (IOPL emulation). Many default kernel configurations
|
||||||
|
now disable this option.
|
||||||
|
|
||||||
|
Here's a handy-dandy guide for building a kernel from source:
|
||||||
|
<https://www.cyberciti.biz/tips/compiling-linux-kernel-26.html>
|
||||||
|
|
||||||
|
**BSD users:** On OpenBSD and NetBSD if you get similar errors, note that it
|
||||||
|
should work here, but you need to boot with `kern.securelevel=-1`.
|
||||||
|
See: [NetBSD securelevel manual](https://wiki.netbsd.org/tutorials/kernel_secure_levels/)
|
||||||
|
and [OpenBSD securelevel manpage](https://man.openbsd.org/securelevel).
|
||||||
|
|
||||||
|
Otherwise, if you get such errors, it may just be that you're not root. You
|
||||||
|
must run flashprog as root, at least to use the internal flasher (using external
|
||||||
|
USB flashing dongles doesn't normally require root).
|
||||||
|
|
||||||
PRECAUTIONS
|
PRECAUTIONS
|
||||||
===========
|
===========
|
||||||
|
@ -157,48 +199,16 @@ an option in the boot menu.
|
||||||
ROM images that have `seabios_withgrub` in the file name start with SeaBIOS
|
ROM images that have `seabios_withgrub` in the file name start with SeaBIOS
|
||||||
first, but also have GRUB available in the boot menu when you press ESC.
|
first, but also have GRUB available in the boot menu when you press ESC.
|
||||||
|
|
||||||
### seabios\_grubfirst (DEFUNCT)
|
ROM images with this and `grubonly` in the image start SeaBIOS, but only load
|
||||||
|
GRUB from SeaBIOS and the SeaBIOS menu is disabled. Use these images if you
|
||||||
**DEFUNCT**
|
only want GRUB; they are provided on systems that only have VGA ROM-based
|
||||||
|
initialisation, usually discrete graphics cards on desktop machines.
|
||||||
This build option is obsolete, and should not be used. It was deleted
|
|
||||||
in lbmk revision `e1bbdadc9584291cf062660d67128e9f17ab788e`.
|
|
||||||
|
|
||||||
It was believed, in earlier theory, that VGA ROM initialisation could
|
|
||||||
be used in SeaBIOS and then SeaBIOS boots into a GRUB payload (built
|
|
||||||
for coreboot), where the initialisation would continue to be used, but
|
|
||||||
it didn't work that way.
|
|
||||||
|
|
||||||
It's best to use PC GRUB (normal BIOS GRUB), but compile it into a floppy
|
|
||||||
image to insert inside CBFS, to then be executed by SeaBIOS. This is referred
|
|
||||||
to as SeaGRUB by the Libreboot project, and it would be quite useful
|
|
||||||
for desktop users, but it's largely irrelevant on laptops where
|
|
||||||
coreboot's own `libgfxinit` is usually available (or the option ROM is
|
|
||||||
easy to extract from vendor firmware and insert).
|
|
||||||
|
|
||||||
Where direct bare metal GRUB is desired, but you use a desktop system with
|
|
||||||
an add-on graphics card, you must extract the VGA ROM for your card and
|
|
||||||
insert it into the coreboot ROM, for coreboot itself to execute. This will
|
|
||||||
require custom configuration on your part, and it is thus beyond the scope
|
|
||||||
of the Libreboot project, in context of lbmk (automated build system).
|
|
||||||
|
|
||||||
Some older Libreboot releases included ROM images built using this option,
|
|
||||||
and those specific ROM images (`seabios_grubfirst` ones) should not be
|
|
||||||
used; you should only use `seabios_grubfirst` or `seabios`, in most
|
|
||||||
scenarios, if SeaBIOS is required.
|
|
||||||
|
|
||||||
For most desktop users, if running an external graphics card, it's easier
|
|
||||||
to simply boot in text mode with a SeaBIOS payload and use only that. This
|
|
||||||
will Just Work with almost all graphics cards, allowing you to use an
|
|
||||||
operating system with a full display and (drivers permitting) full 2D/3D
|
|
||||||
acceleration.
|
|
||||||
|
|
||||||
Which systems are supported?
|
Which systems are supported?
|
||||||
============================
|
============================
|
||||||
|
|
||||||
[Refer to the hardware compatibility page](../hardware/)
|
[Refer to the hardware compatibility page](../hardware/)
|
||||||
|
|
||||||
Sandy/Ivybridge/Haswell MAC address (e.g. X230, X220, T440p, W541, hp8200sff)
|
|
||||||
Intel GbE MAC address (IFD-based systems)
|
Intel GbE MAC address (IFD-based systems)
|
||||||
=====================================================================
|
=====================================================================
|
||||||
|
|
||||||
|
@ -228,6 +238,18 @@ which means that the MAC address is irrelevant (either there will be an Intel
|
||||||
PHY module that is now unusable, and you use an add-on card, or it doesn't use
|
PHY module that is now unusable, and you use an add-on card, or it doesn't use
|
||||||
an Intel PHY module and the onboard NIC is usable).
|
an Intel PHY module and the onboard NIC is usable).
|
||||||
|
|
||||||
|
HP EliteBook 820 G2
|
||||||
|
===================
|
||||||
|
|
||||||
|
Please refer to the [820 G2 page](../hardware/hp820g2.md) for specific
|
||||||
|
flashing instructions, both internal and external.
|
||||||
|
|
||||||
|
HP EliteBook 8560w
|
||||||
|
===================
|
||||||
|
|
||||||
|
Please refer to the [8560w page](../hardware/hp8560w.md) for specific
|
||||||
|
flashing instructions, both internal and external.
|
||||||
|
|
||||||
Install via host CPU (internal flashing)
|
Install via host CPU (internal flashing)
|
||||||
========================================
|
========================================
|
||||||
|
|
||||||
|
@ -237,7 +259,7 @@ may be configured to restrict write privileges by the host CPU.
|
||||||
|
|
||||||
In some situations, the host CPU can rewrite/erase/dump the boot flash.
|
In some situations, the host CPU can rewrite/erase/dump the boot flash.
|
||||||
This is called *internal flashing*. This means that you will run software,
|
This is called *internal flashing*. This means that you will run software,
|
||||||
namely `flashrom`, to read/erase/write the contents of the boot flash from a
|
namely `flashprog`, to read/erase/write the contents of the boot flash from a
|
||||||
running operating system on the target device.
|
running operating system on the target device.
|
||||||
|
|
||||||
NOTE: please also read the sections further down this page. On some systems,
|
NOTE: please also read the sections further down this page. On some systems,
|
||||||
|
@ -248,11 +270,11 @@ NOTE: in some cases, external flashing is possible but special steps are
|
||||||
required. This depends on your mainboard. Again, please read this page
|
required. This depends on your mainboard. Again, please read this page
|
||||||
carefully.
|
carefully.
|
||||||
|
|
||||||
Run flashrom on host CPU
|
Run flashprog on host CPU
|
||||||
------------------------
|
------------------------
|
||||||
|
|
||||||
You can simply take any ROM image from the libreboot project, and flash it.
|
You can simply take any ROM image from the libreboot project, and flash it.
|
||||||
Boot a Linux distribution on the target device, and install flashrom.
|
Boot a Linux distribution on the target device, and install flashprog.
|
||||||
|
|
||||||
In some cases, this is not possible or there are other considerations. Please
|
In some cases, this is not possible or there are other considerations. Please
|
||||||
read this section *carefully*.
|
read this section *carefully*.
|
||||||
|
@ -261,7 +283,7 @@ read this section *carefully*.
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
In the output will be information pertaining to your boot flash.
|
In the output will be information pertaining to your boot flash.
|
||||||
|
|
||||||
|
@ -269,14 +291,14 @@ In the output will be information pertaining to your boot flash.
|
||||||
|
|
||||||
How to read the current chip contents:
|
How to read the current chip contents:
|
||||||
|
|
||||||
sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -r dump.bin
|
sudo flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -r dump.bin
|
||||||
|
|
||||||
You should still make several dumps, even if you're flashing internally, to
|
You should still make several dumps, even if you're flashing internally, to
|
||||||
ensure that you get the same checksums. Check each dump using `sha1sum`
|
ensure that you get the same checksums. Check each dump using `sha1sum`
|
||||||
|
|
||||||
How to erase and rewrite the chip contents:
|
How to erase and rewrite the chip contents:
|
||||||
|
|
||||||
sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w libreboot.rom
|
sudo flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w libreboot.rom
|
||||||
|
|
||||||
If you are re-flashing a GM45+ICH9M laptop (e.g. ThinkPad X200/X200S/X200T,
|
If you are re-flashing a GM45+ICH9M laptop (e.g. ThinkPad X200/X200S/X200T,
|
||||||
T400, T500, R400, W500 etc - but not R500), you should run the ich9gen utility
|
T400, T500, R400, W500 etc - but not R500), you should run the ich9gen utility
|
||||||
|
@ -285,13 +307,13 @@ Please read the ich9utils documentation:
|
||||||
[/docs/install/ich9utils.html](/docs/install/ich9utils.html)
|
[/docs/install/ich9utils.html](/docs/install/ich9utils.html)
|
||||||
|
|
||||||
NOTE: `force_I_want_a_brick` is not scary. Do not be scared! This merely disables
|
NOTE: `force_I_want_a_brick` is not scary. Do not be scared! This merely disables
|
||||||
the safety checks in flashrom. Flashrom and coreboot change a lot, over the years,
|
the safety checks in flashprog. Flashrom and coreboot change a lot, over the years,
|
||||||
and sometimes it's necessary to use this option. If you're scared, then just
|
and sometimes it's necessary to use this option. If you're scared, then just
|
||||||
follow the above instructions, but remove that option. So, just use `-p internal`.
|
follow the above instructions, but remove that option. So, just use `-p internal`.
|
||||||
If that doesn't work, next try `-p internal:boardmismatch=force`. If that doesn't
|
If that doesn't work, next try `-p internal:boardmismatch=force`. If that doesn't
|
||||||
work, try `-p internal:boardmismatch=force,laptop=force_I_want_a_brick`. So long
|
work, try `-p internal:boardmismatch=force,laptop=force_I_want_a_brick`. So long
|
||||||
as you *ensure* you're using the correct ROM for your machine, it will be safe
|
as you *ensure* you're using the correct ROM for your machine, it will be safe
|
||||||
to run flashrom. These extra options just disable the safetyl checks in flashrom.
|
to run flashprog. These extra options just disable the safetyl checks in flashprog.
|
||||||
There is nothing to worry about.
|
There is nothing to worry about.
|
||||||
|
|
||||||
If successful, it will either say `VERIFIED` or it will say that the chip
|
If successful, it will either say `VERIFIED` or it will say that the chip
|
||||||
|
@ -306,14 +328,34 @@ the sections below:
|
||||||
|
|
||||||
[You must flash it externally](spi.md)
|
[You must flash it externally](spi.md)
|
||||||
|
|
||||||
#### DELL Latitude E6400 laptop (easy to flash, similar to X200/T400)
|
#### DELL Latitude E6400 laptop
|
||||||
|
|
||||||
See: [Dell Latitude E6400 Libreboot Installation Guide](e6400.md)
|
See: [Dell Latitude E6400 Libreboot Installation Guide](e6400.md)
|
||||||
|
|
||||||
#### DELL Latitude E6430 laptop (easy to flash, no disassembly)
|
#### DELL Latitude E6420 laptop
|
||||||
|
|
||||||
|
See: [Dell Latitude E6420 Libreboot Installation Guide](e6430.md)
|
||||||
|
|
||||||
|
#### DELL Latitude E6430 laptop
|
||||||
|
|
||||||
See: [Dell Latitude E6430 Libreboot Installation Guide](e6430.md)
|
See: [Dell Latitude E6430 Libreboot Installation Guide](e6430.md)
|
||||||
|
|
||||||
|
#### DELL Latitude E6520 laptop
|
||||||
|
|
||||||
|
See: [Dell Latitude E6520 Libreboot Installation Guide](e6420.md)
|
||||||
|
|
||||||
|
#### DELL Latitude E6530 laptop
|
||||||
|
|
||||||
|
See: [Dell Latitude E6530 Libreboot Installation Guide](e6430.md)
|
||||||
|
|
||||||
|
#### DELL Latitude E5520 laptop
|
||||||
|
|
||||||
|
See: [Dell Latitude E5520 Libreboot Installation Guide](e5520.md)
|
||||||
|
|
||||||
|
#### DELL Latitude E5530 laptop
|
||||||
|
|
||||||
|
See: [Dell Latitude E5530 Libreboot Installation Guide](e6430.md)
|
||||||
|
|
||||||
#### ThinkPad X200/T400/T500/W500/R400/R500 vendor BIOS
|
#### ThinkPad X200/T400/T500/W500/R400/R500 vendor BIOS
|
||||||
|
|
||||||
If you're running one of these, it cannot be flashed internally if you're still
|
If you're running one of these, it cannot be flashed internally if you're still
|
||||||
|
@ -328,6 +370,13 @@ Please also see notes about the built-in MAC address inside the boot flash, for
|
||||||
the onboard NIC (ethernet one); not relevant on R500, which doesn't use an
|
the onboard NIC (ethernet one); not relevant on R500, which doesn't use an
|
||||||
Intel NIC.
|
Intel NIC.
|
||||||
|
|
||||||
|
TARGET: ThinkPad X201/X201S/X201 Tablet
|
||||||
|
--------------------------------
|
||||||
|
|
||||||
|
**SUPPORT WAS REMOVED, because fan controls fail when the ME is neutered on
|
||||||
|
this platform. This only affects the arrandale machines, and does not affect
|
||||||
|
newer Intel platforms.**
|
||||||
|
|
||||||
#### Intel D510MO and D410PT running original Intel BIOS
|
#### Intel D510MO and D410PT running original Intel BIOS
|
||||||
|
|
||||||
[You must flash it externally](spi.md)
|
[You must flash it externally](spi.md)
|
||||||
|
@ -376,6 +425,26 @@ example of the push pin as a proof of concept:
|
||||||
|
|
||||||
#### ThinkPad X60/X60S/X60T/T60 with Lenovo BIOS {#flashrom_lenovobios}
|
#### ThinkPad X60/X60S/X60T/T60 with Lenovo BIOS {#flashrom_lenovobios}
|
||||||
|
|
||||||
|
**WARNING: Libreboot 20231021 and likely older 2023 releases do not have the
|
||||||
|
bootblock copied in release ROMs, so the bucts trick below will actually cause
|
||||||
|
a brick. This is fixed in lbmk as of 25 October 2023 onward, but you should
|
||||||
|
do this on 20231021 release ROMs before following the instructions below:**
|
||||||
|
|
||||||
|
dd if=libreboot.rom of=bootblock.bin bs=1 skip=$(($(stat -c %s libreboot.rom) - 0x10000)) count=64k
|
||||||
|
|
||||||
|
And then do this:
|
||||||
|
|
||||||
|
dd if=bootblock.bin of=libreboot.rom bs=1 seek=$(($(stat -c %s libreboot.rom) - 0x20000)) count=64k conv=notrunc
|
||||||
|
|
||||||
|
(This was fixed in Libreboot 20231101)
|
||||||
|
|
||||||
|
**NOTE: the section below pertaining to 20160907 static binaries references
|
||||||
|
flashrom. Libreboot recommends flashprog nowadays, but if you're using that
|
||||||
|
utils archive, please note that it is from a time when Libreboot used
|
||||||
|
flashrom. Use flashrom there as that's what included in those binaries.
|
||||||
|
Libreboot does not currently document how to patch flashprog for sst/macronix
|
||||||
|
on X60/T60, when going (in software) from lenovobios to libreboot.**
|
||||||
|
|
||||||
**NOTE: This section partially relates to `utils` release archive in
|
**NOTE: This section partially relates to `utils` release archive in
|
||||||
Libreboot 20160907, which contains static compiled binaries for things like
|
Libreboot 20160907, which contains static compiled binaries for things like
|
||||||
bucts and flashrom. It will *still* work on modern distros, and thus is
|
bucts and flashrom. It will *still* work on modern distros, and thus is
|
||||||
|
@ -408,12 +477,12 @@ Here are a list of targets:
|
||||||
and you will run it at 115200 baud rate. agetty/fgetty in Linux can give
|
and you will run it at 115200 baud rate. agetty/fgetty in Linux can give
|
||||||
you a serial console in your OS)
|
you a serial console in your OS)
|
||||||
|
|
||||||
Download and build flashrom, using the instructions
|
|
||||||
on [the Git page](../../git.md), and download the `bucts` software using the
|
|
||||||
notes on that very same page.
|
|
||||||
|
|
||||||
You can replace Lenovo BIOS with libreboot, using flashrom running on the host
|
You can replace Lenovo BIOS with libreboot, using flashrom running on the host
|
||||||
CPU. However, there are some considerations.
|
CPU. However, there are some considerations. NOTE: needs patching for SST
|
||||||
|
and macronix chips, but libreboot doesn't yet do this for flashprog. You can
|
||||||
|
use the old Libreboot 20160907 sources to get the modified flashrom instead,
|
||||||
|
which contains this patch - and static binaries are provided, for convenience;
|
||||||
|
they will still work, due to libs being statically linked.
|
||||||
|
|
||||||
Firstly, make sure that the yellow CMOS battery is installed, and functioning
|
Firstly, make sure that the yellow CMOS battery is installed, and functioning
|
||||||
correctly. You could check the voltage. The battery is a CR2032
|
correctly. You could check the voltage. The battery is a CR2032
|
||||||
|
@ -438,7 +507,7 @@ program referenced below.
|
||||||
The libreboot ROM images already have the upper 64KiB bootblock copied to the lower
|
The libreboot ROM images already have the upper 64KiB bootblock copied to the lower
|
||||||
one, so you don't have to worry about copying it yourself.
|
one, so you don't have to worry about copying it yourself.
|
||||||
|
|
||||||
If you build flashrom using the libreboot build system, there will be three
|
If you use the Libreboot 20160907 utils archive, there will be three
|
||||||
binaries:
|
binaries:
|
||||||
|
|
||||||
* `flashrom`
|
* `flashrom`
|
||||||
|
@ -458,7 +527,7 @@ Macronix chip. The Macronix chip will have "MX" written on the chip. You will
|
||||||
use `flashrom_i945_sst` for the SST chip, and `flashrom_i945_mx` for the
|
use `flashrom_i945_sst` for the SST chip, and `flashrom_i945_mx` for the
|
||||||
Macronix chip.
|
Macronix chip.
|
||||||
|
|
||||||
Now run flashrom (for SST):
|
Now run flashrom from the Libreboot 20160907 utils archive (for SST):
|
||||||
|
|
||||||
sudo ./flashrom_i945_sst -p internal -w coreboot.rom
|
sudo ./flashrom_i945_sst -p internal -w coreboot.rom
|
||||||
|
|
||||||
|
@ -495,7 +564,8 @@ Your flash chip is in an unknown state.
|
||||||
If you see this, rejoice! It means that the flash was successful. Please do not
|
If you see this, rejoice! It means that the flash was successful. Please do not
|
||||||
panic. Shut down now, and wait a few seconds, then turn back on again.
|
panic. Shut down now, and wait a few seconds, then turn back on again.
|
||||||
|
|
||||||
**WARNING: if flashrom complains about `/dev/mem` access, please
|
**WARNING: if flashrom (from Libreboot 20160907 utils) complains
|
||||||
|
about `/dev/mem` access, please
|
||||||
run `sudo ./bucts 0`. If flashrom is complaining about `/dev/mem`, it means
|
run `sudo ./bucts 0`. If flashrom is complaining about `/dev/mem`, it means
|
||||||
that you have `CONFIG_STRICT_DEVMEM` enabled in your kernel. Reboot with the
|
that you have `CONFIG_STRICT_DEVMEM` enabled in your kernel. Reboot with the
|
||||||
following kernel parameter added in your bootloader: `iomem=relaxed` and try
|
following kernel parameter added in your bootloader: `iomem=relaxed` and try
|
||||||
|
@ -512,17 +582,24 @@ volatile memory, powered by that CR2032 coin-cell battery.
|
||||||
|
|
||||||
Assuming that everything went well:
|
Assuming that everything went well:
|
||||||
|
|
||||||
Flash the ROM for a second time. For this second flashing attempt, the upper
|
Switch to flashprog now! (avoid flashrom)
|
||||||
64KiB bootblock is now read-write. Use the *unpatched* flashrom binary:
|
---------------------------------------
|
||||||
|
|
||||||
sudo ./flashrom -p internal -w libreboot.rom
|
Flash the ROM for a second time. For this second flashing attempt, the upper
|
||||||
|
64KiB bootblock is now read-write. Use the *unpatched* flashprog binary:
|
||||||
|
|
||||||
|
sudo ./flashprog -p internal -w libreboot.rom
|
||||||
|
|
||||||
|
NOTE: At this point, we recommend use of flashprog instead of flashrom, for
|
||||||
|
the reasons mentioned in the [Libreboot 20240225
|
||||||
|
release](../../news/libreboot20240225.md).
|
||||||
|
|
||||||
To reset bucts, do this:
|
To reset bucts, do this:
|
||||||
|
|
||||||
sudo ./bucts 0
|
sudo ./bucts 0
|
||||||
|
|
||||||
ONLY set bucts back to 0 if you're sure that the upper 64KiB bootblock is
|
ONLY set bucts back to 0 if you're sure that the upper 64KiB bootblock is
|
||||||
flashed. It is flashed if flashrom said VERIFIED when running the above
|
flashed. It is flashed if flashprog said VERIFIED when running the above
|
||||||
command.
|
command.
|
||||||
|
|
||||||
If it said VERIFIED, shut down. If it didn't say VERIFIED, make sure bucts is
|
If it said VERIFIED, shut down. If it didn't say VERIFIED, make sure bucts is
|
||||||
|
@ -568,19 +645,24 @@ ASUS KFSN4-DRE
|
||||||
|
|
||||||
The KFSN4-DRE has an LPC chip. Most people have been flashing these
|
The KFSN4-DRE has an LPC chip. Most people have been flashing these
|
||||||
internally, hot-swapping the chip out after boot, preserving the original chip,
|
internally, hot-swapping the chip out after boot, preserving the original chip,
|
||||||
and using flashrom on a new chip as described above.
|
and using flashprog on a new chip as described above.
|
||||||
|
|
||||||
TODO: Document PLCC32 (LPC) flashing.
|
TODO: Document PLCC32 (LPC) flashing.
|
||||||
The [FlexyICE](https://www.coreboot.org/FlexyICE) has been used to flash these
|
The [FlexyICE](https://www.coreboot.org/FlexyICE) has been used to flash these
|
||||||
chips, but it is hard to find now. A custom flasher may be made such as
|
chips, but it is hard to find now. A custom flasher may be made such as
|
||||||
[flashrom serprog stm32](https://github.com/wosk/stm32-vserprog-lpc) or
|
[flashprog serprog stm32](https://github.com/wosk/stm32-vserprog-lpc) or
|
||||||
[teensy flasher](https://www.flashrom.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher)
|
[teensy flasher](https://www.flashprog.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher)
|
||||||
|
|
||||||
TARGET: DELL Precision T1650 desktop
|
TARGET: DELL Precision T1650 desktop
|
||||||
------------------------------------
|
------------------------------------
|
||||||
|
|
||||||
Refer to the [T1650 hardware page](../hardware/t1650.md).
|
Refer to the [T1650 hardware page](../hardware/t1650.md).
|
||||||
|
|
||||||
|
TARGET: DELL OptiPlex 7020/9020 SFF and MT desktops
|
||||||
|
------------------------------------
|
||||||
|
|
||||||
|
Refer to the [7020/9020 hardware page](../hardware/dell9020.md).
|
||||||
|
|
||||||
TARGET: Apple Macbook2,1, Macbook1,1 and iMac5,2 (i945 platform)
|
TARGET: Apple Macbook2,1, Macbook1,1 and iMac5,2 (i945 platform)
|
||||||
----------------------------------------------------------------
|
----------------------------------------------------------------
|
||||||
|
|
||||||
|
@ -604,6 +686,8 @@ Links to specific HP laptop pages:
|
||||||
* [HP EliteBook 2170p](../hardware/hp2170p.md)
|
* [HP EliteBook 2170p](../hardware/hp2170p.md)
|
||||||
* [HP EliteBook 2560p](../hardware/hp2560p.md)
|
* [HP EliteBook 2560p](../hardware/hp2560p.md)
|
||||||
* [HP EliteBook 2570p](../hardware/hp2570p.md)
|
* [HP EliteBook 2570p](../hardware/hp2570p.md)
|
||||||
|
* [HP EliteBook 820 G2](../hardware/hp820g2.md)
|
||||||
|
* [HP EliteBook 8460p](../hardware/hp8460p.md)
|
||||||
* [HP EliteBook 8470p](../hardware/hp8470p.md)
|
* [HP EliteBook 8470p](../hardware/hp8470p.md)
|
||||||
* [HP EliteBook Folio 9470m](../hardware/hp9470m.md)
|
* [HP EliteBook Folio 9470m](../hardware/hp9470m.md)
|
||||||
|
|
||||||
|
@ -727,8 +811,8 @@ below.**
|
||||||
On currently supported HP laptops AND desktops
|
On currently supported HP laptops AND desktops
|
||||||
-------------------------------------
|
-------------------------------------
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
LIBREBOOT](../../news/safety.md).**
|
||||||
|
|
||||||
Refer to links about and the [hardware page](../hardware/) for installation
|
Refer to links about and the [hardware page](../hardware/) for installation
|
||||||
instructions on each HP mainboard.
|
instructions on each HP mainboard.
|
||||||
|
@ -736,8 +820,8 @@ instructions on each HP mainboard.
|
||||||
TARGET: ThinkPad X220/T420/T420s
|
TARGET: ThinkPad X220/T420/T420s
|
||||||
--------------------------------
|
--------------------------------
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
LIBREBOOT](../../news/safety.md).**
|
||||||
|
|
||||||
Similar to X230 but there's only 1 flash. Intel ME image must be inserted
|
Similar to X230 but there's only 1 flash. Intel ME image must be inserted
|
||||||
if using release ROMs. See: [guide](ivy_has_common.md) (says ivy/haswell but
|
if using release ROMs. See: [guide](ivy_has_common.md) (says ivy/haswell but
|
||||||
|
@ -756,8 +840,8 @@ guide.**
|
||||||
TARGET: Thinkpad X230/T430/T530/W530
|
TARGET: Thinkpad X230/T430/T530/W530
|
||||||
---------------------
|
---------------------
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
LIBREBOOT](../../news/safety.md).**
|
||||||
|
|
||||||
NOTE: no install docs for T430/T530/W530 yet, but check coreboot wiki.
|
NOTE: no install docs for T430/T530/W530 yet, but check coreboot wiki.
|
||||||
|
|
||||||
|
@ -774,8 +858,8 @@ Read [board documentation](/docs/install/x230_external.html) for disassembly.
|
||||||
TARGET: Thinkpad X230t
|
TARGET: Thinkpad X230t
|
||||||
---------------------
|
---------------------
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
LIBREBOOT](../../news/safety.md).**
|
||||||
|
|
||||||
Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
|
Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
|
||||||
make the rom image usable for external flashing.
|
make the rom image usable for external flashing.
|
||||||
|
@ -790,8 +874,8 @@ guide.**
|
||||||
TARGET: Thinkpad t440p/w541
|
TARGET: Thinkpad t440p/w541
|
||||||
---------------------
|
---------------------
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
LIBREBOOT](../../news/safety.md).**
|
||||||
|
|
||||||
Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
|
Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
|
||||||
make the rom image usable for external flashing.
|
make the rom image usable for external flashing.
|
||||||
|
|
|
@ -66,8 +66,7 @@ Libreboot build system:
|
||||||
target name.
|
target name.
|
||||||
* SMSC SCH5545 fan control firmware (for Dell T1650): `vendor/t1650/sch5545ec.bin`
|
* SMSC SCH5545 fan control firmware (for Dell T1650): `vendor/t1650/sch5545ec.bin`
|
||||||
* SMSC KBC1126 embedded controller firmware, on HP EliteBooks: `ec/`
|
* SMSC KBC1126 embedded controller firmware, on HP EliteBooks: `ec/`
|
||||||
* Intel MRC firmware, used for ram/peripheral init on Haswell machines such as
|
* Intel MRC firmware, provides raminit on HP EliteBook 820 G2
|
||||||
thinkpad t440p/w541: `mrc/`
|
|
||||||
|
|
||||||
The above list refers to the *non-redistributable files*, and these are not
|
The above list refers to the *non-redistributable files*, and these are not
|
||||||
directly included in releases. These are auto-downloaded during the build.
|
directly included in releases. These are auto-downloaded during the build.
|
||||||
|
@ -82,16 +81,12 @@ generated when running this command:
|
||||||
|
|
||||||
./build roms list
|
./build roms list
|
||||||
|
|
||||||
For example, `t440pmrc_12mb` corresponds to ThinkPad T440p with MRC firmware.
|
|
||||||
Whereas `t440plibremrc_12mb` corresponds to T440p with libre MRC firmware.
|
|
||||||
Another example: `x230_12mb` corresponds to Thinkpad X230.
|
|
||||||
|
|
||||||
In order to inject the necessary files into a rom image, run the script from the root of lbmk and point to the rom image.
|
In order to inject the necessary files into a rom image, run the script from the root of lbmk and point to the rom image.
|
||||||
|
|
||||||
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
|
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
|
||||||
Run the injection script pointing to the release archive you downloaded:
|
Run the injection script pointing to the release archive you downloaded:
|
||||||
|
|
||||||
./vendor inject /path/to/libreboot-20230319-18-g9f76c92_t440pmrc_12mb.tar.xz
|
./vendor inject libreboot-RELEASE_targetname.tar.xz
|
||||||
|
|
||||||
The script can automatically detect the board as long as you do not change the file name.
|
The script can automatically detect the board as long as you do not change the file name.
|
||||||
You can then find flash-ready ROMs in `/bin/release/`
|
You can then find flash-ready ROMs in `/bin/release/`
|
||||||
|
@ -141,14 +136,31 @@ You'll note the small size of the Intel ME, e.g. 84KB on sandybridge platforms.
|
||||||
This is because lbmk *automatically* neuters it, disabling it during
|
This is because lbmk *automatically* neuters it, disabling it during
|
||||||
early boot. This is done using `me_cleaner`, which lbmk imports.
|
early boot. This is done using `me_cleaner`, which lbmk imports.
|
||||||
|
|
||||||
|
NOTE: the MAC changer makes use of `nvmutil`, which you can read more about in
|
||||||
|
the [nvmutil documentation](nvmutil.md).
|
||||||
|
|
||||||
Errata
|
Errata
|
||||||
======
|
======
|
||||||
|
|
||||||
**NOTE: Haswell machines come with `mrc.bin` or without, depending on the
|
NOTE: As of Libreboot releases from May 2024 onward, the Intel MRC is no longer
|
||||||
ROM image configuration. These ROM configs have `mrc.bin`: `t440pmrc_12mb`
|
included for Haswell; MRC is a blob for raminit, but we now provide libre
|
||||||
and `w541mrc_12mb`. These ROM configs have libre MRC: `t440p_12mb`
|
raminit. The following targets no longer exist in the build system:
|
||||||
and `w541_12mb` - it is critical that you choose the right one, when using
|
|
||||||
the `-b` flag in the `./vendor inject` command. For example, if you
|
* `t440pmrc_12mb` (use `t440plibremrc_12mb` instead)
|
||||||
used `-b t440p_12mb` on a ROM image that actually corresponds
|
* `t440pbmrc_12mb` (use `t440plibremrc_12mb` instead)
|
||||||
to `t440pmrc_12mb`, then the required `mrc.bin` file would not be added
|
* `w541mrc_12mb` (use `w541_12mb` instead)
|
||||||
and that ROM would not boot when flashed.**
|
* `w541bmrc_12mb` (use `w541_12mb` instead)
|
||||||
|
* `dell9020sff_12mb` (use `dell9020sff_nri_12mb` instead)
|
||||||
|
* `dell9020sffbmrc` (use `dell9020sff_nri_12mb` instead)
|
||||||
|
* `dell9020mt_12mb` (use `dell9020mt_nri_12mb` instead)
|
||||||
|
* `dell9020mtbmrc` (use `dell9020mt_nri_12mb` instead)
|
||||||
|
|
||||||
|
This is written as errata because some users may still be using older release
|
||||||
|
images but on the newer build system from May 2024 onward; you must use the
|
||||||
|
Libreboot 20240225 release if you want to inject MRC and so on, for these older
|
||||||
|
targets.
|
||||||
|
|
||||||
|
Libreboot's [binary blob reduction policy](../../news/policy.md) is very strict,
|
||||||
|
and states: if a blob can be avoided, it must be avoided. Therefore, the MRC
|
||||||
|
is removed on Haswell and Libreboot will only use the libre raminit (called
|
||||||
|
NRI, short for Native Ram Initialisation).
|
||||||
|
|
|
@ -70,8 +70,7 @@ Libreboot build system:
|
||||||
target name.
|
target name.
|
||||||
* SMSC SCH5545 fan control firmware (for Dell T1650): `vendor/t1650/sch5545ec.bin`
|
* SMSC SCH5545 fan control firmware (for Dell T1650): `vendor/t1650/sch5545ec.bin`
|
||||||
* SMSC KBC1126 embedded controller firmware, on HP EliteBooks: `ec/`
|
* SMSC KBC1126 embedded controller firmware, on HP EliteBooks: `ec/`
|
||||||
* Intel MRC firmware, used for ram/peripheral init on Haswell machines such as
|
* Intel MRC firmware, provides raminit on HP EliteBook 820 G2
|
||||||
thinkpad t440p/w541: `mrc/`
|
|
||||||
|
|
||||||
The above list refers to the *non-redistributable files*, and these are not
|
The above list refers to the *non-redistributable files*, and these are not
|
||||||
directly included in releases. These are auto-downloaded during the build.
|
directly included in releases. These are auto-downloaded during the build.
|
||||||
|
@ -86,10 +85,6 @@ generated when running this command:
|
||||||
|
|
||||||
./build roms list
|
./build roms list
|
||||||
|
|
||||||
For example, `t440pmrc_12mb` corresponds to ThinkPad T440p with MRC firmware.
|
|
||||||
Whereas `t440plibremrc_12mb` corresponds to T440p with libre MRC firmware.
|
|
||||||
Another example: `x230_12mb` corresponds to Thinkpad X230.
|
|
||||||
|
|
||||||
In order to inject the necessary files into a rom image, run the script from the root of lbmk and point to the rom image.
|
In order to inject the necessary files into a rom image, run the script from the root of lbmk and point to the rom image.
|
||||||
|
|
||||||
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
|
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
|
||||||
|
@ -145,17 +140,31 @@ You'll note the small size of the Intel ME, e.g. 84KB on sandybridge platforms.
|
||||||
This is because lbmk *automatically* neuters it, disabling it during
|
This is because lbmk *automatically* neuters it, disabling it during
|
||||||
early boot. This is done using `me_cleaner`, which lbmk imports.
|
early boot. This is done using `me_cleaner`, which lbmk imports.
|
||||||
|
|
||||||
|
NOTE: the MAC changer makes use of `nvmutil`, which you can read more about in
|
||||||
|
the [nvmutil documentation](nvmutil.md).
|
||||||
|
|
||||||
Errata
|
Errata
|
||||||
======
|
======
|
||||||
|
|
||||||
**NOTE: Haswell machines come with `mrc.bin` or without, depending on the
|
NOTE: As of Libreboot releases from May 2024 onward, the Intel MRC is no longer
|
||||||
ROM image configuration. These ROM configs have `mrc.bin`: `t440pmrc_12mb`
|
included for Haswell; MRC is a blob for raminit, but we now provide libre
|
||||||
and `w541mrc_12mb`. These ROM configs have libre MRC: `t440p_12mb`
|
raminit. The following targets no longer exist in the build system:
|
||||||
and `w541_12mb` - it is critical that you choose the right one, when using
|
|
||||||
the `-b` flag in the `./vendor inject` command. For example, if you
|
|
||||||
used `-b t440p_12mb` on a ROM image that actually corresponds
|
|
||||||
to `t440pmrc_12mb`, then the required `mrc.bin` file would not be added
|
|
||||||
and that ROM would not boot when flashed.**
|
|
||||||
|
|
||||||
NOTE: the MAC changer makes use of `nvmutil`, which you can read more about in
|
* `t440pmrc_12mb` (use `t440plibremrc_12mb` instead)
|
||||||
the [nvmutil documentation](nvmutil.md).
|
* `t440pbmrc_12mb` (use `t440plibremrc_12mb` instead)
|
||||||
|
* `w541mrc_12mb` (use `w541_12mb` instead)
|
||||||
|
* `w541bmrc_12mb` (use `w541_12mb` instead)
|
||||||
|
* `dell9020sff_12mb` (use `dell9020sff_nri_12mb` instead)
|
||||||
|
* `dell9020sffbmrc` (use `dell9020sff_nri_12mb` instead)
|
||||||
|
* `dell9020mt_12mb` (use `dell9020mt_nri_12mb` instead)
|
||||||
|
* `dell9020mtbmrc` (use `dell9020mt_nri_12mb` instead)
|
||||||
|
|
||||||
|
This is written as errata because some users may still be using older release
|
||||||
|
images but on the newer build system from May 2024 onward; you must use the
|
||||||
|
Libreboot 20240225 release if you want to inject MRC and so on, for these older
|
||||||
|
targets.
|
||||||
|
|
||||||
|
Libreboot's [binary blob reduction policy](../../news/policy.md) is very strict,
|
||||||
|
and states: if a blob can be avoided, it must be avoided. Therefore, the MRC
|
||||||
|
is removed on Haswell and Libreboot will only use the libre raminit (called
|
||||||
|
NRI, short for Native Ram Initialisation).
|
||||||
|
|
|
@ -111,23 +111,26 @@ containing your NIC's configuration. This is the part that
|
||||||
many people will struggle with, so we will dedicated an
|
many people will struggle with, so we will dedicated an
|
||||||
entire next section to it:
|
entire next section to it:
|
||||||
|
|
||||||
Use flashrom
|
Use flashprog
|
||||||
------------
|
------------
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
If you wish to operate on the GbE section that's already
|
If you wish to operate on the GbE section that's already
|
||||||
flashed, you should *dump* the current full ROM image.
|
flashed, you should *dump* the current full ROM image.
|
||||||
If you already have a ROM image, you do not need to dump
|
If you already have a ROM image, you do not need to dump
|
||||||
it, so you can skip this section.
|
it, so you can skip this section.
|
||||||
|
|
||||||
Download flashrom here:
|
Download flashprog here:
|
||||||
|
|
||||||
* <https://flashrom.org/>
|
* <https://flashprog.org/>
|
||||||
|
|
||||||
Using recent flashrom versions, you can extract this region. If
|
Using recent flashprog versions, you can extract this region. If
|
||||||
your regions are unlocked, you can run flashrom on the target
|
your regions are unlocked, you can run flashprog on the target
|
||||||
system, like so:
|
system, like so:
|
||||||
|
|
||||||
flashrom -p internal -r rom.bin
|
flashprog -p internal -r rom.bin
|
||||||
|
|
||||||
If your system has two flash chips, the GbE region is usually
|
If your system has two flash chips, the GbE region is usually
|
||||||
stored on SPI1 (not SPI2). Otherwise, it may be that you have
|
stored on SPI1 (not SPI2). Otherwise, it may be that you have
|
||||||
|
@ -145,7 +148,7 @@ from and writing to the chip. See:
|
||||||
* <https://libreboot.org/docs/install/spi.html>
|
* <https://libreboot.org/docs/install/spi.html>
|
||||||
|
|
||||||
If you're using an external programmer, the `-p internal`
|
If you're using an external programmer, the `-p internal`
|
||||||
option should be changed accordingly. Read flashrom
|
option should be changed accordingly. Read flashprog
|
||||||
documentation, and make sure you have everything
|
documentation, and make sure you have everything
|
||||||
properly configured.
|
properly configured.
|
||||||
|
|
||||||
|
@ -201,18 +204,18 @@ This will create the file `rom.bin.new`, which contains
|
||||||
your modified GbE section with the NVM images inside; this
|
your modified GbE section with the NVM images inside; this
|
||||||
includes your MAC address.
|
includes your MAC address.
|
||||||
|
|
||||||
Refer to flashrom documentation. You may flash the new ROM
|
Refer to flashprog documentation. You may flash the new ROM
|
||||||
like so, if running on the same system and the regions are
|
like so, if running on the same system and the regions are
|
||||||
read-write:
|
read-write:
|
||||||
|
|
||||||
flashrom -p internal -w rom.bin.new
|
flashprog -p internal -w rom.bin.new
|
||||||
|
|
||||||
Newer versions of flashrom support flashing just the specified
|
Newer versions of flashprog support flashing just the specified
|
||||||
region, like so:
|
region, like so:
|
||||||
|
|
||||||
flashrom -p internal --ifd -i gbe -w rom.bin.new
|
flashprog -p internal --ifd -i gbe -w rom.bin.new
|
||||||
|
|
||||||
If you're running flashrom from host CPU on the target
|
If you're running flashprog from host CPU on the target
|
||||||
system, and it's dual flash, you can just flash the
|
system, and it's dual flash, you can just flash the
|
||||||
concatenated image, which you created earlier by running
|
concatenated image, which you created earlier by running
|
||||||
the `cat` program; dual-IC flash configurations appear to
|
the `cat` program; dual-IC flash configurations appear to
|
||||||
|
|
|
@ -64,7 +64,10 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
MAC address {#macaddress}
|
MAC address {#macaddress}
|
||||||
===========
|
===========
|
||||||
|
|
|
@ -3,6 +3,25 @@ title: Read/write 25XX NOR flash via SPI protocol
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
@ -14,7 +33,7 @@ which uses LPC flash in a PLCC32 socket, which you can simply hot-swap after
|
||||||
booting the vendor firmware, and then flash internally. Simple!
|
booting the vendor firmware, and then flash internally. Simple!
|
||||||
|
|
||||||
We will be using
|
We will be using
|
||||||
the [flashrom](https://flashrom.org/Flashrom) software which is written to
|
the [flashprog](https://flashprog.org/Flashrom) software which is written to
|
||||||
dump, erase and rewrite these flash chips.
|
dump, erase and rewrite these flash chips.
|
||||||
|
|
||||||
libreboot currently documents how to use these SPI programmers:
|
libreboot currently documents how to use these SPI programmers:
|
||||||
|
@ -36,7 +55,7 @@ libreboot is running.
|
||||||
|
|
||||||
*Internal* flashing means that the host CPU on your system can re-program the
|
*Internal* flashing means that the host CPU on your system can re-program the
|
||||||
SPI flash, using an on-board SPI programmer (which all boards have). You do this
|
SPI flash, using an on-board SPI programmer (which all boards have). You do this
|
||||||
from Linux, with flashrom.
|
from Linux, with flashprog.
|
||||||
|
|
||||||
*This* guide that you're reading now is for using an *external* programmer. It
|
*This* guide that you're reading now is for using an *external* programmer. It
|
||||||
is called *external* because it's not the *internal* one on your mainboard.
|
is called *external* because it's not the *internal* one on your mainboard.
|
||||||
|
@ -67,9 +86,13 @@ You can download the serprog firmware here:\
|
||||||
or here:\
|
or here:\
|
||||||
<https://notabug.org/libreboot/pico-serprog>
|
<https://notabug.org/libreboot/pico-serprog>
|
||||||
|
|
||||||
|
You can also find the source code for these, under `src/` in Libreboot release
|
||||||
|
archives (source code tarball), and/or under `src/` in `lbmk.git` if downloading
|
||||||
|
using the build instructions below.
|
||||||
|
|
||||||
Copy the file `rpi-pico-serprog.uf2` into your Pico. To build this firmware, you
|
Copy the file `rpi-pico-serprog.uf2` into your Pico. To build this firmware, you
|
||||||
could build it yourself or you could also clone `lbmk.git` and [install build
|
could build it yourself or you could also clone `lbmk.git` and [install build
|
||||||
dependencies](..//build/#first-install-build-dependencies), then inside lbmk,
|
dependencies](../build/#first-install-build-dependencies), then inside lbmk,
|
||||||
do:
|
do:
|
||||||
|
|
||||||
./build serprog rp2040 pico
|
./build serprog rp2040 pico
|
||||||
|
@ -85,6 +108,9 @@ pre-compiled in the next Libreboot release, after the 20230625 release.
|
||||||
Disconnect the Pico and proceed to wire it to your
|
Disconnect the Pico and proceed to wire it to your
|
||||||
[flash chip](/docs/install/spi.html#identify-which-flash-type-you-have).
|
[flash chip](/docs/install/spi.html#identify-which-flash-type-you-have).
|
||||||
|
|
||||||
|
**NOTE: SCK and CLK mean the same thing. The diagram below says SCK, and other
|
||||||
|
parts of this guide say CLK. It's the same thing!**
|
||||||
|
|
||||||
![Raspberry Pi Pico pinout, when using the firmware linked
|
![Raspberry Pi Pico pinout, when using the firmware linked
|
||||||
above](https://av.libreboot.org/rpi_pico/pinout_serprog.png)
|
above](https://av.libreboot.org/rpi_pico/pinout_serprog.png)
|
||||||
|
|
||||||
|
@ -104,7 +130,7 @@ will appear:
|
||||||
Take note of the ttyACMx. Flashrom is now usable
|
Take note of the ttyACMx. Flashrom is now usable
|
||||||
(substitute ttyACMx with what you observed earlier).
|
(substitute ttyACMx with what you observed earlier).
|
||||||
|
|
||||||
flashrom -p serprog:dev=/dev/ttyACMx,spispeed=16M
|
flashprog -p serprog:dev=/dev/ttyACMx,spispeed=16M
|
||||||
|
|
||||||
spispeed=32M usually works, but since it's not much faster it's probably
|
spispeed=32M usually works, but since it's not much faster it's probably
|
||||||
not worth it. The 12Mbps USB port is limiting the actual speed here.
|
not worth it. The 12Mbps USB port is limiting the actual speed here.
|
||||||
|
@ -205,8 +231,8 @@ SOIC16
|
||||||
|
|
||||||
| Pin | Function |
|
| Pin | Function |
|
||||||
|-----|----------|
|
|-----|----------|
|
||||||
|
| 1 | HOLD |
|
||||||
| 2 | VCC |
|
| 2 | VCC |
|
||||||
| 3 | HOLD |
|
|
||||||
| 7 | CS |
|
| 7 | CS |
|
||||||
| 8 | MISO |
|
| 8 | MISO |
|
||||||
| 9 | WP |
|
| 9 | WP |
|
||||||
|
@ -263,7 +289,7 @@ BeagleBone Black (BBB)
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
SSH into your BeagleBone Black. It is assumed that you are running Debian 9 on
|
SSH into your BeagleBone Black. It is assumed that you are running Debian 9 on
|
||||||
your BBB. You will run `flashrom` from your BBB.
|
your BBB. You will run `flashprog` from your BBB.
|
||||||
|
|
||||||
NOTE: This section is out of date, because it is written for Debian 9 (running
|
NOTE: This section is out of date, because it is written for Debian 9 (running
|
||||||
on the BBB)
|
on the BBB)
|
||||||
|
@ -304,9 +330,9 @@ RemainAfterExit=yes
|
||||||
WantedBy=multi-user.target
|
WantedBy=multi-user.target
|
||||||
```
|
```
|
||||||
|
|
||||||
Now test flashrom:
|
Now test flashprog:
|
||||||
|
|
||||||
./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
||||||
|
|
||||||
It is important to use `spispeed=512` or a lower number such as 256 or 128,
|
It is important to use `spispeed=512` or a lower number such as 256 or 128,
|
||||||
because otherwise the BBB will be quite unstable.
|
because otherwise the BBB will be quite unstable.
|
||||||
|
@ -316,7 +342,7 @@ Example output:
|
||||||
```
|
```
|
||||||
Calibrating delay loop... OK.
|
Calibrating delay loop... OK.
|
||||||
No EEPROM/flash device found.
|
No EEPROM/flash device found.
|
||||||
Note: flashrom can never write if the flash chip isn't found automatically.
|
Note: flashprog can never write if the flash chip isn't found automatically.
|
||||||
```
|
```
|
||||||
|
|
||||||
This means that it's working (the clip isn't connected to any flash
|
This means that it's working (the clip isn't connected to any flash
|
||||||
|
@ -335,7 +361,7 @@ TODO: document other SPI flashers
|
||||||
Rasberry Pi (RPi)
|
Rasberry Pi (RPi)
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
SSH into your Raspberry Pi. You will run `flashrom` from your Raspberry Pi.
|
SSH into your Raspberry Pi. You will run `flashprog` from your Raspberry Pi.
|
||||||
|
|
||||||
You must configure `spidev` on your Raspberry Pi. This is a special driver in
|
You must configure `spidev` on your Raspberry Pi. This is a special driver in
|
||||||
the Linux kernel; technically, the driver name is `spi-bcm2835`.
|
the Linux kernel; technically, the driver name is `spi-bcm2835`.
|
||||||
|
@ -443,7 +469,7 @@ Website:
|
||||||
|
|
||||||
<https://librerpi.github.io/>
|
<https://librerpi.github.io/>
|
||||||
|
|
||||||
Install flashrom
|
Install flashprog
|
||||||
----------------
|
----------------
|
||||||
|
|
||||||
If you're using a BBB or RPi, you will do this while SSH'd into those.
|
If you're using a BBB or RPi, you will do this while SSH'd into those.
|
||||||
|
@ -452,7 +478,7 @@ Flashrom is the software that you will use, for dumping, erasing and rewriting
|
||||||
the contents of your NOR flash.
|
the contents of your NOR flash.
|
||||||
|
|
||||||
In the libreboot build system, from the Git repository, you can download and
|
In the libreboot build system, from the Git repository, you can download and
|
||||||
install flashrom. Do this after downloading the
|
install flashprog. Do this after downloading the
|
||||||
[lbmk Git repository](https://codeberg.org/libreboot/lbmk):
|
[lbmk Git repository](https://codeberg.org/libreboot/lbmk):
|
||||||
|
|
||||||
cd lbmk
|
cd lbmk
|
||||||
|
@ -461,7 +487,7 @@ install flashrom. Do this after downloading the
|
||||||
NOTE: debian, arch or void can be written instead of ubuntu2004. the debian
|
NOTE: debian, arch or void can be written instead of ubuntu2004. the debian
|
||||||
script is also applicable to newer ubuntu versions
|
script is also applicable to newer ubuntu versions
|
||||||
|
|
||||||
./update trees -b flashrom
|
./update trees -b flashprog
|
||||||
|
|
||||||
If the `ubuntu2004` script complains about missing dependencies, just modify
|
If the `ubuntu2004` script complains about missing dependencies, just modify
|
||||||
the dependencies config to remove those dependencies. The script is located
|
the dependencies config to remove those dependencies. The script is located
|
||||||
|
@ -469,29 +495,29 @@ at `config/dependencies/ubuntu2004` and it is written for
|
||||||
Ubuntu 20.04, but it should work fine in other Linux distributions that use
|
Ubuntu 20.04, but it should work fine in other Linux distributions that use
|
||||||
the `apt-get` package manager.
|
the `apt-get` package manager.
|
||||||
|
|
||||||
A `flashrom/` directory will be present, with a `flashrom` executable inside
|
A `flashprog/` directory will be present, with a `flashprog` executable inside
|
||||||
of it. If you got an error about missing package when running the dependencies
|
of it. If you got an error about missing package when running the dependencies
|
||||||
command above, tweak `config/dependencies/ubuntu2004`. That
|
command above, tweak `config/dependencies/ubuntu2004`. That
|
||||||
script downloads and installs build dependencies in apt-get and it is intended
|
script downloads and installs build dependencies in apt-get and it is intended
|
||||||
for use on x86-64 systems running Ubuntu 20.04, but it should work in Raspbian
|
for use on x86-64 systems running Ubuntu 20.04, but it should work in Raspbian
|
||||||
on the Raspberry Pi.
|
on the Raspberry Pi.
|
||||||
|
|
||||||
Alternatively, you may download flashrom directly from upstream
|
Alternatively, you may download flashprog directly from upstream
|
||||||
at <https://flashrom.org/Flashrom>
|
at <https://flashprog.org/Flashrom>
|
||||||
|
|
||||||
If you're flashing a Macronix flashchip on a ThinkPad X200, you will want to
|
If you're flashing a Macronix flashchip on a ThinkPad X200, you will want to
|
||||||
use a special patched version of flashrom, which you can download here:
|
use a special patched version of flashprog, which you can download here:
|
||||||
<https://vimuser.org/hackrom.tar.xz> - patched source code is available, and a
|
<https://vimuser.org/hackrom.tar.xz> - patched source code is available, and a
|
||||||
binary is also available that you can simply run. Pass the `--workaround-mx`
|
binary is also available that you can simply run. Pass the `--workaround-mx`
|
||||||
argument in flashrom. This mitigates stability issues.
|
argument in flashprog. This mitigates stability issues.
|
||||||
|
|
||||||
If you downloaded the flashrom source code directly, you can go into the
|
If you downloaded the flashprog source code directly, you can go into the
|
||||||
directory and simply type `make`. In the libreboot build system, build
|
directory and simply type `make`. In the libreboot build system, build
|
||||||
dependencies are documented in configuration files located
|
dependencies are documented in configuration files located
|
||||||
at `config/dependencies/` which you can install
|
at `config/dependencies/` which you can install
|
||||||
using the `apt-get` software.
|
using the `apt-get` software.
|
||||||
|
|
||||||
How to use flashrom
|
How to use flashprog
|
||||||
===================
|
===================
|
||||||
|
|
||||||
Read past these sections, further down this page, to learn about specific chip
|
Read past these sections, further down this page, to learn about specific chip
|
||||||
|
@ -506,11 +532,11 @@ current chip contents to a file.
|
||||||
Run this command to see if 25xx flash is detected, with your RPi properly
|
Run this command to see if 25xx flash is detected, with your RPi properly
|
||||||
wired.
|
wired.
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
|
||||||
|
|
||||||
For BBB, you must use a lower speed and a different device path:
|
For BBB, you must use a lower speed and a different device path:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
||||||
|
|
||||||
On BBB, never use a speed higher than `spispeed=512`. In some cases, you may
|
On BBB, never use a speed higher than `spispeed=512`. In some cases, you may
|
||||||
even need to go as low as `spispeed=128`. The BBB is highly unstable and
|
even need to go as low as `spispeed=128`. The BBB is highly unstable and
|
||||||
|
@ -528,11 +554,11 @@ or you can try flashing it with a new ROM.
|
||||||
|
|
||||||
Dump it like so (RPi):
|
Dump it like so (RPi):
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
|
||||||
|
|
||||||
For BBB, do this:
|
For BBB, do this:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
|
||||||
|
|
||||||
It is advisable to take a *2nd* dump, e.g. `dump2.bin`, and then check sha1sum:
|
It is advisable to take a *2nd* dump, e.g. `dump2.bin`, and then check sha1sum:
|
||||||
|
|
||||||
|
@ -563,11 +589,11 @@ Writing
|
||||||
|
|
||||||
Next, run this command (RPi):
|
Next, run this command (RPi):
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
|
||||||
|
|
||||||
If using BBB:
|
If using BBB:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
|
||||||
|
|
||||||
If using BBB, you may have to use a lower speed than 512. You may also have to
|
If using BBB, you may have to use a lower speed than 512. You may also have to
|
||||||
re-flash several times before it works fully.
|
re-flash several times before it works fully.
|
||||||
|
@ -940,6 +966,9 @@ Your DIP8 IC has the same pinout as a SOIC8 IC.
|
||||||
Replace WSON8 IC with SOIC8
|
Replace WSON8 IC with SOIC8
|
||||||
---------------------------
|
---------------------------
|
||||||
|
|
||||||
|
**NOTE: You can alternatively purchase WSON8 probes from a site like Aliexpress.
|
||||||
|
They look similar to SOIC8 clips, and they work similarly.**
|
||||||
|
|
||||||
You *can* connect a SOIC8 test clip, but you will struggle to get good
|
You *can* connect a SOIC8 test clip, but you will struggle to get good
|
||||||
connections and it will be extremely unreliable. DO NOT solder to the pads of
|
connections and it will be extremely unreliable. DO NOT solder to the pads of
|
||||||
the WSON8 directly; some people do this, but you shouldn't do it, because you
|
the WSON8 directly; some people do this, but you shouldn't do it, because you
|
||||||
|
|
|
@ -3,11 +3,27 @@ title: 通过 SPI 协议对 25XX NOR flash 进行读/写
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
Need help?
|
||||||
|
==========
|
||||||
|
|
||||||
|
Help is available on [Libreboot IRC](../../contact.md) and other channels.
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
**[安装之前请先阅读这些指示](../../news/safety.md),否则你的机器可能会成砖:[安全措施](../../news/safety.md)**
|
**[安装之前请先阅读这些指示](../../news/safety.md),否则你的机器可能会成砖:[安全措施](../../news/safety.md)**
|
||||||
|
|
||||||
本指南将教你怎样使用各种工具,通过 SPI 协议对 25xx NOR flash 进行外部再编程。这是 coreboot 所支持的计算机中,最常见的 flash IC 类型。目前 libreboot 支持的每个系统,基本都使用这种类型的引导 flash;唯一的例外就是 ASUS KFSN4-DRE,它在 PLCC32 芯片座中使用了 LPC flash,你可以在供应商固件启动后,对其进行热切换,然后再内部刷入。十分简单!
|
本指南将教你怎样使用各种工具,通过 SPI 协议对 25xx NOR flash 进行外部再编程。这是 coreboot 所支持的计算机中,最常见的 flash IC 类型。目前 libreboot 支持的每个系统,基本都使用这种类型的引导 flash;唯一的例外就是 ASUS KFSN4-DRE,它在 PLCC32 芯片座中使用了 LPC flash,你可以在供应商固件启动后,对其进行热切换,然后再内部刷入。十分简单!
|
||||||
|
|
||||||
我们会用到 [flashrom](https://flashrom.org/Flashrom) 软件,这个软件可以读出、擦除及重写这些 flash 芯片。
|
我们会用到 [flashprog](https://flashprog.org/Flashrom) 软件,这个软件可以读出、擦除及重写这些 flash 芯片。
|
||||||
|
|
||||||
libreboot 目前记录了这些 SPI 编程器的使用方法:
|
libreboot 目前记录了这些 SPI 编程器的使用方法:
|
||||||
|
|
||||||
|
@ -20,7 +36,7 @@ libreboot 目前记录了这些 SPI 编程器的使用方法:
|
||||||
|
|
||||||
大部分支持 libreboot 机器,都需要在第一次刷写的时候,借助这里的教程或是类似教程,对其进行外部再刷写。不过,目前支持的所有机器,你都可以在 libreboot 运行时,对其进行内部再刷写。
|
大部分支持 libreboot 机器,都需要在第一次刷写的时候,借助这里的教程或是类似教程,对其进行外部再刷写。不过,目前支持的所有机器,你都可以在 libreboot 运行时,对其进行内部再刷写。
|
||||||
|
|
||||||
*内部*刷写是指,主机上的 CPU 可以使用板载 SPI 编程器(每个主板都有)对 SPI flash 进行再编程。这可以在 Linux 上使用 flashrom 做到。
|
*内部*刷写是指,主机上的 CPU 可以使用板载 SPI 编程器(每个主板都有)对 SPI flash 进行再编程。这可以在 Linux 上使用 flashprog 做到。
|
||||||
|
|
||||||
你在读的*这个*教程,使用的是*外部*编程器。之所以叫*外部*,是因为用的不是主板上的*内部*编程器。
|
你在读的*这个*教程,使用的是*外部*编程器。之所以叫*外部*,是因为用的不是主板上的*内部*编程器。
|
||||||
|
|
||||||
|
@ -52,7 +68,7 @@ or here:\
|
||||||
|
|
||||||
Copy the file `rpi-pico-serprog.uf2` into your Pico. To build this firmware, you
|
Copy the file `rpi-pico-serprog.uf2` into your Pico. To build this firmware, you
|
||||||
could build it yourself or you could also clone `lbmk.git` and [install build
|
could build it yourself or you could also clone `lbmk.git` and [install build
|
||||||
dependencies](..//build/#first-install-build-dependencies), then inside lbmk,
|
dependencies](../build/#first-install-build-dependencies), then inside lbmk,
|
||||||
do:
|
do:
|
||||||
|
|
||||||
./build serprog rp2040 pico
|
./build serprog rp2040 pico
|
||||||
|
@ -85,7 +101,7 @@ will appear:
|
||||||
Take note of the ttyACMx. Flashrom is now usable
|
Take note of the ttyACMx. Flashrom is now usable
|
||||||
(substitute ttyACMx with what you observed earlier).
|
(substitute ttyACMx with what you observed earlier).
|
||||||
|
|
||||||
flashrom -p serprog:dev=/dev/ttyACMx,spispeed=16M
|
flashprog -p serprog:dev=/dev/ttyACMx,spispeed=16M
|
||||||
|
|
||||||
spispeed=32M usually works, but since it's not much faster it's probably
|
spispeed=32M usually works, but since it's not much faster it's probably
|
||||||
not worth it. The 12Mbps USB port is limiting the actual speed here.
|
not worth it. The 12Mbps USB port is limiting the actual speed here.
|
||||||
|
@ -173,7 +189,7 @@ DIP8
|
||||||
BeagleBone Black(BBB)
|
BeagleBone Black(BBB)
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
SSH 连接到你的 BeagleBone Black。假定你在 BBB 上用的是 Debian 9。你将在 BBB 上运行 `flashrom`。
|
SSH 连接到你的 BeagleBone Black。假定你在 BBB 上用的是 Debian 9。你将在 BBB 上运行 `flashprog`。
|
||||||
|
|
||||||
注意:该部分已过时,因为它是写给 BBB 上运行的 Debian 9 的。
|
注意:该部分已过时,因为它是写给 BBB 上运行的 Debian 9 的。
|
||||||
|
|
||||||
|
@ -212,9 +228,9 @@ RemainAfterExit=yes
|
||||||
WantedBy=multi-user.target
|
WantedBy=multi-user.target
|
||||||
```
|
```
|
||||||
|
|
||||||
现在测试 flashrom:
|
现在测试 flashprog:
|
||||||
|
|
||||||
./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
||||||
|
|
||||||
重要的一点是,要使用 `spispeed=512` 或者更低的速度,例如 256 或 128,否则 BBB 会十分不稳定。
|
重要的一点是,要使用 `spispeed=512` 或者更低的速度,例如 256 或 128,否则 BBB 会十分不稳定。
|
||||||
|
|
||||||
|
@ -223,7 +239,7 @@ WantedBy=multi-user.target
|
||||||
```
|
```
|
||||||
Calibrating delay loop... OK.
|
Calibrating delay loop... OK.
|
||||||
No EEPROM/flash device found.
|
No EEPROM/flash device found.
|
||||||
Note: flashrom can never write if the flash chip isn't found automatically.
|
Note: flashprog can never write if the flash chip isn't found automatically.
|
||||||
```
|
```
|
||||||
|
|
||||||
这表示正常工作了(夹子没连接任何 flash 芯片,所以出错是正常的)。
|
这表示正常工作了(夹子没连接任何 flash 芯片,所以出错是正常的)。
|
||||||
|
@ -238,7 +254,7 @@ BBB 注意事项
|
||||||
Rasberry Pi(RPi)
|
Rasberry Pi(RPi)
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
SSH 连接到树莓派。你将在树莓派上运行 `flashrom`。
|
SSH 连接到树莓派。你将在树莓派上运行 `flashprog`。
|
||||||
|
|
||||||
你必须在树莓派上配置 `spidev`。这是 Linux 内核的一个特别驱动;它严谨的名字叫做 `spi-bcm2835`。
|
你必须在树莓派上配置 `spidev`。这是 Linux 内核的一个特别驱动;它严谨的名字叫做 `spi-bcm2835`。
|
||||||
|
|
||||||
|
@ -256,7 +272,7 @@ SSH 连接到树莓派。你将在树莓派上运行 `flashrom`。
|
||||||
RPi 驱动强度(Drive Strength)
|
RPi 驱动强度(Drive Strength)
|
||||||
------------------
|
------------------
|
||||||
|
|
||||||
RPi 的 flashrom 可能无法检测到一些系统的 SPI flash,即使你已经完美地连好了线并夹住了芯片。这可能是因为树莓派 GPIO 的驱动强度,它默认是 8mA。驱动强度本质上就是,在保持高电平最低电压的同时,引脚最高能输出的电流。对树莓派而言,这个电压是 3.0 V。
|
RPi 的 flashprog 可能无法检测到一些系统的 SPI flash,即使你已经完美地连好了线并夹住了芯片。这可能是因为树莓派 GPIO 的驱动强度,它默认是 8mA。驱动强度本质上就是,在保持高电平最低电压的同时,引脚最高能输出的电流。对树莓派而言,这个电压是 3.0 V。
|
||||||
|
|
||||||
类似地,也要满足一个最低电压,SPI flash 芯片才会把它当成高逻辑电平。这个值一般是 SPI flash 的 0.7*VCC,对 3.3V 的芯片而言也就是 2.31V。如果驱动强度太低了,那 flash 芯片的引脚处的电压可能会低于最低电压,导致它被视为发送了低逻辑电平,而不是高逻辑电平。
|
类似地,也要满足一个最低电压,SPI flash 芯片才会把它当成高逻辑电平。这个值一般是 SPI flash 的 0.7*VCC,对 3.3V 的芯片而言也就是 2.31V。如果驱动强度太低了,那 flash 芯片的引脚处的电压可能会低于最低电压,导致它被视为发送了低逻辑电平,而不是高逻辑电平。
|
||||||
|
|
||||||
|
@ -309,33 +325,33 @@ RPi 的自由固件
|
||||||
|
|
||||||
<https://librerpi.github.io/>
|
<https://librerpi.github.io/>
|
||||||
|
|
||||||
安装 flashrom
|
安装 flashprog
|
||||||
----------------
|
----------------
|
||||||
|
|
||||||
如果你在使用 BBB 或者 RPi,你需要在 SSH 进去之后再这么做。
|
如果你在使用 BBB 或者 RPi,你需要在 SSH 进去之后再这么做。
|
||||||
|
|
||||||
Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
|
Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
|
||||||
|
|
||||||
使用 Git 仓库中的 libreboot 构建系统,你可以下载并安装 flashrom。首先下载 [lbmk Git 仓库](https://codeberg.org/libreboot/lbmk),然后执行:
|
使用 Git 仓库中的 libreboot 构建系统,你可以下载并安装 flashprog。首先下载 [lbmk Git 仓库](https://codeberg.org/libreboot/lbmk),然后执行:
|
||||||
|
|
||||||
cd lbmk
|
cd lbmk
|
||||||
sudo ./build dependencies ubuntu2004
|
sudo ./build dependencies ubuntu2004
|
||||||
|
|
||||||
注意:你可以输入 debian、arch 或 void 来替换 ubuntu。debian 脚本也可以用于新版 ubuntu。
|
注意:你可以输入 debian、arch 或 void 来替换 ubuntu。debian 脚本也可以用于新版 ubuntu。
|
||||||
|
|
||||||
./update trees -b flashrom
|
./update trees -b flashprog
|
||||||
|
|
||||||
如果 `ubuntu2004` 报告了依赖缺失,编辑一下这个脚本,把缺失的依赖移除就行了。脚本位于 `config/dependencies/ubuntu2004`,它是写给 Ubuntu 20.04 的,但在其他使用 `apt-get` 包管理器的 Linux 发行版应该也能用。
|
如果 `ubuntu2004` 报告了依赖缺失,编辑一下这个脚本,把缺失的依赖移除就行了。脚本位于 `config/dependencies/ubuntu2004`,它是写给 Ubuntu 20.04 的,但在其他使用 `apt-get` 包管理器的 Linux 发行版应该也能用。
|
||||||
|
|
||||||
接下来,会出现一个 `flashrom/` 目录,其中有一个 `flashrom` 可执行文件。如果你在运行上面的依赖命令的时候,出现了缺失包的错误,则修改 `config/dependencies/ubuntu2004`。那个脚本会在 apt-get 中下载并安装构建依赖,它是为运行 Ubuntu 的 x86-64 系统写的,但在树莓派上的 Raspbian 应该能用。
|
接下来,会出现一个 `flashprog/` 目录,其中有一个 `flashprog` 可执行文件。如果你在运行上面的依赖命令的时候,出现了缺失包的错误,则修改 `config/dependencies/ubuntu2004`。那个脚本会在 apt-get 中下载并安装构建依赖,它是为运行 Ubuntu 的 x86-64 系统写的,但在树莓派上的 Raspbian 应该能用。
|
||||||
|
|
||||||
或者,你可以直接从上游下载 flashrom,位于:<https://flashrom.org/Flashrom>
|
或者,你可以直接从上游下载 flashprog,位于:<https://flashprog.org/Flashrom>
|
||||||
|
|
||||||
如果你是在 ThinkPad X200 上刷写 Macronix flash 芯片,则要使用一个 flashrom 的特别修改版,下载地址在这里:<https://vimuser.org/hackrom.tar.xz> —— 其中有修改版的源代码,也有可以直接运行的二进制文件。将 `--workaround-mx` 参数传给 flashrom。这会缓解稳定性问题。
|
如果你是在 ThinkPad X200 上刷写 Macronix flash 芯片,则要使用一个 flashprog 的特别修改版,下载地址在这里:<https://vimuser.org/hackrom.tar.xz> —— 其中有修改版的源代码,也有可以直接运行的二进制文件。将 `--workaround-mx` 参数传给 flashprog。这会缓解稳定性问题。
|
||||||
|
|
||||||
如果你直接下载了 flashrom 源代码,你可以进入目录并直接运行 `make`。在 libreboot 构建系统中,`config/dependencies/` 处的脚本写明了构建依赖,你可以直接使用 `apt-get` 软件安装。
|
如果你直接下载了 flashprog 源代码,你可以进入目录并直接运行 `make`。在 libreboot 构建系统中,`config/dependencies/` 处的脚本写明了构建依赖,你可以直接使用 `apt-get` 软件安装。
|
||||||
|
|
||||||
如何使用 flashrom
|
如何使用 flashprog
|
||||||
===================
|
===================
|
||||||
|
|
||||||
请先阅读本页更下方的部分,了解特定的芯片类型及其接线方法。
|
请先阅读本页更下方的部分,了解特定的芯片类型及其接线方法。
|
||||||
|
@ -347,11 +363,11 @@ Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
|
||||||
|
|
||||||
树莓派正确接线后,运行这个命令来查看是否检测到 25xx flash:
|
树莓派正确接线后,运行这个命令来查看是否检测到 25xx flash:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
|
||||||
|
|
||||||
对 BBB 而言,必须使用更慢的速度及不同的设备路径:
|
对 BBB 而言,必须使用更慢的速度及不同的设备路径:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
|
||||||
|
|
||||||
在 BBB 上,绝对不要使用高于 `spispeed=512` 的速度。有时候,你可能还要低到 `spispeed=128` 的速度。BBB 对 SPI 刷写而言非常不稳定、不可靠。在读取的时候,要多次读出,并检查它们的 checksum 是否一致,然后再刷。你可能需要多次刷写芯片!
|
在 BBB 上,绝对不要使用高于 `spispeed=512` 的速度。有时候,你可能还要低到 `spispeed=128` 的速度。BBB 对 SPI 刷写而言非常不稳定、不可靠。在读取的时候,要多次读出,并检查它们的 checksum 是否一致,然后再刷。你可能需要多次刷写芯片!
|
||||||
|
|
||||||
|
@ -361,11 +377,11 @@ Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
|
||||||
|
|
||||||
在 RPi 上,这样读出:
|
在 RPi 上,这样读出:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
|
||||||
|
|
||||||
BBB 的话,这样:
|
BBB 的话,这样:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
|
||||||
|
|
||||||
建议读出*两次*,比如弄一个 `dump2.bin`,然后检查 sha1sum:
|
建议读出*两次*,比如弄一个 `dump2.bin`,然后检查 sha1sum:
|
||||||
|
|
||||||
|
@ -386,11 +402,11 @@ BBB 的话,这样:
|
||||||
|
|
||||||
接下来,运行这个命令(RPi):
|
接下来,运行这个命令(RPi):
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
|
||||||
|
|
||||||
如果用的是 BBB:
|
如果用的是 BBB:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
|
||||||
|
|
||||||
用 BBB 的时候,可能得使用低于 512 的速度。你也许还得多次重复刷写,才能完全工作。
|
用 BBB 的时候,可能得使用低于 512 的速度。你也许还得多次重复刷写,才能完全工作。
|
||||||
|
|
||||||
|
@ -627,6 +643,9 @@ DIP8 IC 的引脚分配和 SOIC8 IC 一样。
|
||||||
使用 SOIC8 替换 WSON8 IC
|
使用 SOIC8 替换 WSON8 IC
|
||||||
---------------------------
|
---------------------------
|
||||||
|
|
||||||
|
**NOTE: You can alternatively purchase WSON8 probes from a site like Aliexpress.
|
||||||
|
They look similar to SOIC8 clips, and they work similarly.**
|
||||||
|
|
||||||
你*连是可以连* SOIC8 测试夹,但要连接效果好,需要费点功夫,而且这也十分不可靠。不要直接焊接 WSON8 的焊盘;有些人会这样做,但你不要这样做,因为你这样很容易就会损坏焊盘。
|
你*连是可以连* SOIC8 测试夹,但要连接效果好,需要费点功夫,而且这也十分不可靠。不要直接焊接 WSON8 的焊盘;有些人会这样做,但你不要这样做,因为你这样很容易就会损坏焊盘。
|
||||||
|
|
||||||
WSON8 的引脚分配和 SOIC8 一样,但它是球状 QFN(四边扁平无引脚封装)。它没有合适的夹子,有时候称为 QFN8。
|
WSON8 的引脚分配和 SOIC8 一样,但它是球状 QFN(四边扁平无引脚封装)。它没有合适的夹子,有时候称为 QFN8。
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: Generic SPI Flashing Guide
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
@ -83,24 +86,24 @@ sudo ldto merge spicc spicc-spidev
|
||||||
Using Flashrom
|
Using Flashrom
|
||||||
==============
|
==============
|
||||||
|
|
||||||
Most linux distros will provide flashrom in their default repositories.
|
Most linux distros will provide flashprog in their default repositories.
|
||||||
You can also download flashrom in binary form with [libreboot utils.](https://libreboot.org/download.html#https)
|
You can also download flashprog in binary form with [libreboot utils.](https://libreboot.org/download.html#https)
|
||||||
Here is an example using raspbian:
|
Here is an example using raspbian:
|
||||||
|
|
||||||
```
|
```
|
||||||
sudo apt update
|
sudo apt update
|
||||||
sudo apt install flashrom
|
sudo apt install flashprog
|
||||||
```
|
```
|
||||||
|
|
||||||
Reading/writing from SPI works respectively as such:
|
Reading/writing from SPI works respectively as such:
|
||||||
|
|
||||||
```
|
```
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r /path/to/read.bin
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r /path/to/read.bin
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
|
||||||
```
|
```
|
||||||
|
|
||||||
Note that `spispeed` varies based on the board in question.
|
Note that `spispeed` varies based on the board in question.
|
||||||
A standard lower limit is *512.*
|
A standard lower limit is *512.*
|
||||||
For example, to read on a board with a lower SPI speed, you may try:
|
For example, to read on a board with a lower SPI speed, you may try:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r /path/to/read.bin
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r /path/to/read.bin
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: Flashing the ThinkPad T400 externally
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Dell Latitude E6400
|
Dell Latitude E6400
|
||||||
===================
|
===================
|
||||||
|
|
||||||
|
@ -77,7 +80,7 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
MAC address {#macaddress}
|
MAC address {#macaddress}
|
||||||
===========
|
===========
|
||||||
|
|
|
@ -3,6 +3,18 @@ title: ThinkPad T440p external flashing
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
Buy Libreboot preinstalled
|
||||||
|
==========================
|
||||||
|
|
||||||
|
This laptop is available to buy with Libreboot pre-installed:
|
||||||
|
<https://minifree.org/product/libreboot-t440p/>
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
============
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
@ -28,29 +40,20 @@ In order to inject the necessary files into a rom image, run the script from the
|
||||||
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
|
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
|
||||||
Run the injection script pointing to the release archive you downloaded:
|
Run the injection script pointing to the release archive you downloaded:
|
||||||
|
|
||||||
./vendor inject /path/to/libreboot-20230319-18-g9f76c92_t440_12mb.tar.xz
|
./vendor inject /path/to/libreboot-RELEASE_targetname.tar.xz
|
||||||
|
|
||||||
The script can automatically detect the board as long as you do not change the file name.
|
The script can automatically detect the board as long as you do not change the file name.
|
||||||
You can then find flash-ready ROMs in `/bin/release/`
|
You can then find flash-ready ROMs in `/bin/release/`
|
||||||
|
|
||||||
Alternatively, you may patch only a single rom file.
|
Alternatively, you may patch only a single rom file.
|
||||||
For example (libre replacement of `mrc.bin`):
|
For example:
|
||||||
|
|
||||||
./vendor inject -r t440p_libreboot.rom -b t440p_12mb
|
./vendor inject -r t440p_libreboot.rom -b t440plibremrc_12mb
|
||||||
|
|
||||||
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
|
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
./vendor inject -r t440p_libreboot.rom -b t440p_12mb -m 00:f6:f0:40:71:fd
|
./vendor inject -r t440p_libreboot.rom -b t440plibremrc_12mb -m 00:f6:f0:40:71:fd
|
||||||
|
|
||||||
If you're flashing a ROM that needs vendor file `mrc.bin`, you would do one of these
|
|
||||||
instead, for example:
|
|
||||||
|
|
||||||
./vendor inject -r t440p_libreboot.rom -b t440pmrc_12mb
|
|
||||||
|
|
||||||
or (inserting a different MAC address)
|
|
||||||
|
|
||||||
./vendor inject -r t440p_libreboot.rom -b t440pmrc_12mb -m 00:f6:f0:40:71:fd
|
|
||||||
|
|
||||||
NOTE: this makes use of `nvmutil`, which you can read more about in
|
NOTE: this makes use of `nvmutil`, which you can read more about in
|
||||||
the [nvmutil documentation](nvmutil.md).
|
the [nvmutil documentation](nvmutil.md).
|
||||||
|
@ -65,7 +68,7 @@ external flashing.
|
||||||
dd if=libreboot.rom of=bottom.rom bs=1M count=8
|
dd if=libreboot.rom of=bottom.rom bs=1M count=8
|
||||||
|
|
||||||
Flash the top chip with top.rom, and tho bottom chip with bottom.rom.
|
Flash the top chip with top.rom, and tho bottom chip with bottom.rom.
|
||||||
Don't worry about knowing which chip is which on a standard setup; flashrom will let you know if the
|
Don't worry about knowing which chip is which on a standard setup; flashprog will let you know if the
|
||||||
image size is incorrect for the chip you're flashing.
|
image size is incorrect for the chip you're flashing.
|
||||||
|
|
||||||
|
|
||||||
|
@ -95,3 +98,29 @@ You should now be able to see the two flash chips near the RAM.\
|
||||||
<img tabindex=1 src="https://av.libreboot.org/board/t440p/t440p_chipLocation.jpg" /><span class="f"><img src="https://av.libreboot.org/board/t440p/t440p_chipLocation_orig.jpg" /></span>
|
<img tabindex=1 src="https://av.libreboot.org/board/t440p/t440p_chipLocation.jpg" /><span class="f"><img src="https://av.libreboot.org/board/t440p/t440p_chipLocation_orig.jpg" /></span>
|
||||||
|
|
||||||
You can now proceed to [flashing](/docs/install/spi.html) this machine.
|
You can now proceed to [flashing](/docs/install/spi.html) this machine.
|
||||||
|
|
||||||
|
Errata
|
||||||
|
======
|
||||||
|
|
||||||
|
NOTE: As of Libreboot releases from May 2024 onward, the Intel MRC is no longer
|
||||||
|
included for Haswell; MRC is a blob for raminit, but we now provide libre
|
||||||
|
raminit. The following targets no longer exist in the build system:
|
||||||
|
|
||||||
|
* `t440pmrc_12mb` (use `t440plibremrc_12mb` instead)
|
||||||
|
* `t440pbmrc_12mb` (use `t440plibremrc_12mb` instead)
|
||||||
|
* `w541mrc_12mb` (use `w541_12mb` instead)
|
||||||
|
* `w541bmrc_12mb` (use `w541_12mb` instead)
|
||||||
|
* `dell9020sff_12mb` (use `dell9020sff_nri_12mb` instead)
|
||||||
|
* `dell9020sffbmrc` (use `dell9020sff_nri_12mb` instead)
|
||||||
|
* `dell9020mt_12mb` (use `dell9020mt_nri_12mb` instead)
|
||||||
|
* `dell9020mtbmrc` (use `dell9020mt_nri_12mb` instead)
|
||||||
|
|
||||||
|
This is written as errata because some users may still be using older release
|
||||||
|
images but on the newer build system from May 2024 onward; you must use the
|
||||||
|
Libreboot 20240225 release if you want to inject MRC and so on, for these older
|
||||||
|
targets.
|
||||||
|
|
||||||
|
Libreboot's [binary blob reduction policy](../../news/policy.md) is very strict,
|
||||||
|
and states: if a blob can be avoided, it must be avoided. Therefore, the MRC
|
||||||
|
is removed on Haswell and Libreboot will only use the libre raminit (called
|
||||||
|
NRI, short for Native Ram Initialisation).
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: ThinkPad T500 external flashing
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**If you haven't bought a T500 yet: the [Dell Latitude
|
**If you haven't bought a T500 yet: the [Dell Latitude
|
||||||
E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
|
E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
|
||||||
it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
|
it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
|
||||||
|
@ -73,7 +76,7 @@ Flash chip size {#flashchips}
|
||||||
|
|
||||||
Use this to find out:
|
Use this to find out:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
MAC address {#macaddress}
|
MAC address {#macaddress}
|
||||||
===========
|
===========
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: ThinkPad T60 Recovery guide
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
This section documents how to recover from a bad flash that prevents
|
This section documents how to recover from a bad flash that prevents
|
||||||
your ThinkPad T60 from booting.
|
your ThinkPad T60 from booting.
|
||||||
|
|
||||||
|
@ -160,16 +163,16 @@ which all draw a lot of current, more than your flasher can provide.
|
||||||
|
|
||||||
Example command:
|
Example command:
|
||||||
|
|
||||||
sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w libreboot.rom -V
|
sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w libreboot.rom -V
|
||||||
|
|
||||||
If flashrom complains about multiple flash chips detected, just pass the `-c`
|
If flashprog complains about multiple flash chips detected, just pass the `-c`
|
||||||
option as it suggests, and pick any of the chips it lists. `spispeed=4096` or
|
option as it suggests, and pick any of the chips it lists. `spispeed=4096` or
|
||||||
lower (e.g. `spispeed=512`) is recommended on this board. The flashing becomes
|
lower (e.g. `spispeed=512`) is recommended on this board. The flashing becomes
|
||||||
unstable, on this machine, when you use higher speeds.
|
unstable, on this machine, when you use higher speeds.
|
||||||
|
|
||||||
Reverse the steps to re-assemble your system, after you've flashed the chip.
|
Reverse the steps to re-assemble your system, after you've flashed the chip.
|
||||||
|
|
||||||
It should be `Verifying flash... VERIFIED` at the end. If flashrom
|
It should be `Verifying flash... VERIFIED` at the end. If flashprog
|
||||||
complains about multiple flash chip definitions detected, then choose
|
complains about multiple flash chip definitions detected, then choose
|
||||||
one of them following the instructions in the output.
|
one of them following the instructions in the output.
|
||||||
|
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: First-time ThinkPad X200 flashing
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**If you haven't bought an X200 yet: the [Dell Latitude
|
**If you haven't bought an X200 yet: the [Dell Latitude
|
||||||
E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
|
E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
|
||||||
it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
|
it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
|
||||||
|
@ -25,7 +28,7 @@ Flash chip size
|
||||||
|
|
||||||
Run this command on x200 to find out flash chip model and its size:
|
Run this command on x200 to find out flash chip model and its size:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
MAC address
|
MAC address
|
||||||
===========
|
===========
|
||||||
|
@ -106,7 +109,7 @@ Look just above the 7 in TP37 (that's GPIO33):
|
||||||
|
|
||||||
![](https://av.libreboot.org/x200/gpio33_location.jpg)
|
![](https://av.libreboot.org/x200/gpio33_location.jpg)
|
||||||
|
|
||||||
By default we would see this in lenovobios, when trying flashrom -p
|
By default we would see this in lenovobios, when trying flashprog -p
|
||||||
internal -w rom.rom:
|
internal -w rom.rom:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
@ -147,7 +150,7 @@ that does the flashing; Lenovo BIOS then probably sees that and runs that, inste
|
||||||
of setting PRx and going for normal boot. It is theoretically possible that we
|
of setting PRx and going for normal boot. It is theoretically possible that we
|
||||||
could discover how this works, by debugging the Lenovo BIOS update utility (in
|
could discover how this works, by debugging the Lenovo BIOS update utility (in
|
||||||
Windows), and then replicate what it is doing, with some tool for Linux,
|
Windows), and then replicate what it is doing, with some tool for Linux,
|
||||||
then load a flashrom binary into memory and the ROM to flash (for the BIOS
|
then load a flashprog binary into memory and the ROM to flash (for the BIOS
|
||||||
region). You would do this with GPIO33 grounded, and the payload program would
|
region). You would do this with GPIO33 grounded, and the payload program would
|
||||||
actually flash the entire chip, with just a normal libreboot image.
|
actually flash the entire chip, with just a normal libreboot image.
|
||||||
|
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: Прошивка ThinkPad X200 вперше
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**If you haven't bought an X200 yet: the [Dell Latitude
|
**If you haven't bought an X200 yet: the [Dell Latitude
|
||||||
E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
|
E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
|
||||||
it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
|
it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
|
||||||
|
@ -25,7 +28,7 @@ same hardware generation (GM45), with same CPUs, video processor, etc.**
|
||||||
|
|
||||||
Виконайте цю команду на x200, щоб дізнатися модель флеш-чіпа та його розмір:
|
Виконайте цю команду на x200, щоб дізнатися модель флеш-чіпа та його розмір:
|
||||||
|
|
||||||
flashrom -p internal
|
flashprog -p internal
|
||||||
|
|
||||||
MAC адреса
|
MAC адреса
|
||||||
===========
|
===========
|
||||||
|
@ -106,7 +109,7 @@ sgsit дізнався про контакт під назвою GPIO33, яки
|
||||||
|
|
||||||
![](https://av.libreboot.org/x200/gpio33_location.jpg)
|
![](https://av.libreboot.org/x200/gpio33_location.jpg)
|
||||||
|
|
||||||
Це замовчуванням ми побачимо це в lenovobios, під час спроби flashrom -p
|
Це замовчуванням ми побачимо це в lenovobios, під час спроби flashprog -p
|
||||||
internal -w rom.rom:
|
internal -w rom.rom:
|
||||||
|
|
||||||
FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
|
FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
|
||||||
|
@ -141,7 +144,7 @@ internal -w rom.rom:
|
||||||
встановлення PRx і переходу до нормального завантаження. Теоретично можливо, що ми
|
встановлення PRx і переходу до нормального завантаження. Теоретично можливо, що ми
|
||||||
зможемо дізнатися, як це працює, налагодивши утиліту оновлення BIOS Lenovo (у
|
зможемо дізнатися, як це працює, налагодивши утиліту оновлення BIOS Lenovo (у
|
||||||
Windows), а потім відтворивши її дії за допомогою якогось інструменту для Linux,
|
Windows), а потім відтворивши її дії за допомогою якогось інструменту для Linux,
|
||||||
а потім завантаживши двійковий файл flashrom в пам'ять та ROM для прошивки (для BIOS
|
а потім завантаживши двійковий файл flashprog в пам'ять та ROM для прошивки (для BIOS
|
||||||
регіона). Ви б зробили це з заземленням GPIO33, і програма корисного навантаження
|
регіона). Ви б зробили це з заземленням GPIO33, і програма корисного навантаження
|
||||||
фактично прошиє весь чіп, лише звичайним образом libreboot.
|
фактично прошиє весь чіп, лише звичайним образом libreboot.
|
||||||
|
|
||||||
|
|
|
@ -3,6 +3,12 @@ title: ThinkPad X230/X230T external flashing
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
This machine is available to purchase with Libreboot pre-installed:
|
||||||
|
<https://minifree.org/product/libreboot-x230/>
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
|
||||||
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
|
||||||
|
|
||||||
|
@ -58,7 +64,7 @@ external flashing.
|
||||||
dd if=libreboot.rom of=bottom.rom bs=1M count=8
|
dd if=libreboot.rom of=bottom.rom bs=1M count=8
|
||||||
|
|
||||||
Flash the top chip with top.rom, and tho bottom chip with bottom.rom.
|
Flash the top chip with top.rom, and tho bottom chip with bottom.rom.
|
||||||
Don't worry about knowing which chip is which on a standard setup; flashrom will let you know if the
|
Don't worry about knowing which chip is which on a standard setup; flashprog will let you know if the
|
||||||
image size is incorrect for the chip you're flashing.
|
image size is incorrect for the chip you're flashing.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: Modifying grub.cfg in CBFS
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Before you follow this guide, it is advisable that you have the ability to
|
Before you follow this guide, it is advisable that you have the ability to
|
||||||
flash externally, just in case something goes wrong.
|
flash externally, just in case something goes wrong.
|
||||||
|
|
||||||
|
@ -27,7 +30,7 @@ a *soft brick* where your machine is effectively useless and, in that scenario,
|
||||||
may or may not require external flashing equipment for restoring the machine to
|
may or may not require external flashing equipment for restoring the machine to
|
||||||
a known state.
|
a known state.
|
||||||
|
|
||||||
Compile flashrom and cbfstool
|
Compile flashprog and cbfstool
|
||||||
=============================
|
=============================
|
||||||
|
|
||||||
libreboot does not currently distribute utilities pre-compiled. It only
|
libreboot does not currently distribute utilities pre-compiled. It only
|
||||||
|
@ -75,34 +78,34 @@ The `cbfstool` utility is what you shall use. It is used to manipulate CBFS
|
||||||
(coreboot file system) which is a file system contained within the coreboot
|
(coreboot file system) which is a file system contained within the coreboot
|
||||||
ROM image; as a *coreboot distribution*, libreboot inherits this technology.
|
ROM image; as a *coreboot distribution*, libreboot inherits this technology.
|
||||||
|
|
||||||
You will also want to build `flashrom` which libreboot recommends for reading
|
You will also want to build `flashprog` which libreboot recommends for reading
|
||||||
from and/or writing to the boot flash. In the libreboot build system, you can
|
from and/or writing to the boot flash. In the libreboot build system, you can
|
||||||
build it by running this command:
|
build it by running this command:
|
||||||
|
|
||||||
./update trees -b flashrom
|
./update trees -b flashprog
|
||||||
|
|
||||||
An executable will be available at `src/flashrom/flashrom` after you have done
|
An executable will be available at `src/flashprog/flashprog` after you have done
|
||||||
this.
|
this.
|
||||||
|
|
||||||
Dump the boot flash
|
Dump the boot flash
|
||||||
===================
|
===================
|
||||||
|
|
||||||
If you wish to modify your *existing* libreboot ROM, which was installed on
|
If you wish to modify your *existing* libreboot ROM, which was installed on
|
||||||
your computer, you can use `flashrom` to acquire it.
|
your computer, you can use `flashprog` to acquire it.
|
||||||
|
|
||||||
Simply run the following, after using libreboot's build system to compile
|
Simply run the following, after using libreboot's build system to compile
|
||||||
flashrom:
|
flashprog:
|
||||||
|
|
||||||
sudo ./src/flashrom/flashrom -p internal -r dump.bin
|
sudo ./src/flashprog/flashprog -p internal -r dump.bin
|
||||||
|
|
||||||
If flashrom complains about multiple flash chip definitions, do what it says to
|
If flashprog complains about multiple flash chip definitions, do what it says to
|
||||||
rectify your command and run it again.
|
rectify your command and run it again.
|
||||||
|
|
||||||
You may want to use the following, instead of `-p internal`:
|
You may want to use the following, instead of `-p internal`:
|
||||||
`-p internal:laptop=force_I_want_a_brick,boardmismatch=force`
|
`-p internal:laptop=force_I_want_a_brick,boardmismatch=force`
|
||||||
|
|
||||||
Do not let the word *brick* fools you. This merely disables the safety checks
|
Do not let the word *brick* fools you. This merely disables the safety checks
|
||||||
in flashrom, which is sometimes necessary depending on what ROM was already
|
in flashprog, which is sometimes necessary depending on what ROM was already
|
||||||
flashed, versus the new ROM image.
|
flashed, versus the new ROM image.
|
||||||
|
|
||||||
The `internal` option assumes that internal read/write is possible; this is
|
The `internal` option assumes that internal read/write is possible; this is
|
||||||
|
@ -195,17 +198,17 @@ Flash the modified ROM image
|
||||||
Your modified `dump.bin` or other modified libreboot ROM can then be re-flashed
|
Your modified `dump.bin` or other modified libreboot ROM can then be re-flashed
|
||||||
using:
|
using:
|
||||||
|
|
||||||
sudo ./flashrom -p internal -w dump.bin
|
sudo ./flashprog -p internal -w dump.bin
|
||||||
|
|
||||||
If a `-c` option is required, use it and specify a flash chip name. This is
|
If a `-c` option is required, use it and specify a flash chip name. This is
|
||||||
only useful when `flashrom` complains about multiple flash chips being
|
only useful when `flashprog` complains about multiple flash chips being
|
||||||
detected.
|
detected.
|
||||||
|
|
||||||
If flashrom complains about wrong chip/board, make sure that your ROM is for
|
If flashprog complains about wrong chip/board, make sure that your ROM is for
|
||||||
the correct system. If you're sure, you can disable the safety checks by running
|
the correct system. If you're sure, you can disable the safety checks by running
|
||||||
this instead:
|
this instead:
|
||||||
|
|
||||||
sudo ./flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w dump.bin
|
sudo ./flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w dump.bin
|
||||||
|
|
||||||
If you need to use external flashing equipment, see the link above to the
|
If you need to use external flashing equipment, see the link above to the
|
||||||
Raspberry Pi page.
|
Raspberry Pi page.
|
||||||
|
|
|
@ -221,6 +221,52 @@ of user-friendliness.
|
||||||
|
|
||||||
That just about covers it, where password setup is concerned!
|
That just about covers it, where password setup is concerned!
|
||||||
|
|
||||||
|
SeaBIOS first?
|
||||||
|
==============
|
||||||
|
|
||||||
|
In releases after Libreboot 20240504, SeaBIOS is the primary payload on
|
||||||
|
all images, but GRUB is available in the boot menu. Select a ROM image
|
||||||
|
with `grubfirst` at the end, and do this to the ROM image:
|
||||||
|
|
||||||
|
cbfstool libreboot.rom add-int -i 0 -n etc/show-boot-menu
|
||||||
|
|
||||||
|
This disables the SeaBIOS menu, so that it only loads GRUB. The `grubfirst`
|
||||||
|
image had this done to it by lbmk (Libreboot build system) during build:
|
||||||
|
|
||||||
|
cbfstool libreboot.rom add -f config/grub/bootorder -n bootorder -t raw
|
||||||
|
|
||||||
|
This `bootorder` file has the following contents:
|
||||||
|
|
||||||
|
```
|
||||||
|
/rom@img/grub2
|
||||||
|
```
|
||||||
|
|
||||||
|
You can add it yourself if your image doesn't have it. With this, SeaBIOS
|
||||||
|
only loads GRUB first. You can still put a GRUB config in CBFS to override
|
||||||
|
the default one, as of Libreboot 20240612.
|
||||||
|
|
||||||
|
NOTE: Before disabling the boot menu, make sure GRUB works. Access it using
|
||||||
|
the `bootorder` file and/or press ESC in the SeaBIOS menu. Then disable the
|
||||||
|
SeaBIOS menu.
|
||||||
|
|
||||||
|
Alternative: GRUB as primary
|
||||||
|
----------------------------
|
||||||
|
|
||||||
|
The *SeaBIOS first* policy is now law, in Libreboot releases. The only
|
||||||
|
exception is the x86 QEMU target. You can do this if building from source:
|
||||||
|
|
||||||
|
./build roms -p grub targetname
|
||||||
|
|
||||||
|
Where `targetname` is e.g. `x200_8mb` (use the correct one for your board).
|
||||||
|
|
||||||
|
Again: make sure GRUB works. Also: don't do this if you're using a non-Intel
|
||||||
|
graphics card because only the Intel graphics have native video initialisation
|
||||||
|
in Libreboot, and we rely on SeaBIOS to execute the VGA ROM for others.
|
||||||
|
|
||||||
|
(it is assumed that you know to add the VGA ROM in CBFS if needed, if using
|
||||||
|
a dGPU, or that you're using a graphics card on a desktop so SeaBIOS will use
|
||||||
|
that automatically)
|
||||||
|
|
||||||
GPG keys
|
GPG keys
|
||||||
========
|
========
|
||||||
|
|
||||||
|
|
|
@ -46,14 +46,25 @@ Then still as root, do these commands:
|
||||||
export PATH="$PATH:/sbin"
|
export PATH="$PATH:/sbin"
|
||||||
update-grub
|
update-grub
|
||||||
|
|
||||||
|
NOTE: `update-grub` is very much Debian-centric. Not all distros will have it.
|
||||||
|
On Arch-based distros for instance, you might do:
|
||||||
|
|
||||||
|
grub-mkconfig -o /boot/grub/grub.cfg
|
||||||
|
|
||||||
Now your distro's GRUB menu should work, when your distro's GRUB bootloader is
|
Now your distro's GRUB menu should work, when your distro's GRUB bootloader is
|
||||||
executed from Libreboot's SeaBIOS payload.
|
executed from Libreboot's SeaBIOS payload.
|
||||||
|
|
||||||
Encrypted (LUKS/dm-crypt) installations
|
Encrypted /boot via LUKS2 with argon2
|
||||||
=======================================
|
=======================================
|
||||||
|
|
||||||
Full encryption for basic LUKS2 (with PBKDF or argon2 key derivation) is
|
Full encryption for basic LUKS2 (with PBKDF or argon2 key derivation) is
|
||||||
supported in libreboot. Legacy LUKS1 is also supported.
|
supported in libreboot. Legacy LUKS1 is also supported. On *most* other
|
||||||
|
systems, `/boot` must be unencrypted, but Libreboot supports use of the
|
||||||
|
GRUB bootloader as a coreboot payload, directly in the boot flash.
|
||||||
|
|
||||||
|
GRUB has code in it that can be used to unlock LUKS1 and LUKS2 dm-crypt,
|
||||||
|
using the `cryptomount` command. With this, you can boot with *true* full
|
||||||
|
disk encryption, by encrypting `/boot`.
|
||||||
|
|
||||||
This is a boon for security, because it's harder
|
This is a boon for security, because it's harder
|
||||||
to tamper with, and you could potentially write-protect plus maybe provide
|
to tamper with, and you could potentially write-protect plus maybe provide
|
||||||
|
@ -92,6 +103,15 @@ At the time of the Libreboot 20231021 release, the GRUB upstream (on gnu.org)
|
||||||
did not have these argon2 patches in its source tree, but Libreboot merges and
|
did not have these argon2 patches in its source tree, but Libreboot merges and
|
||||||
maintains them out of tree.
|
maintains them out of tree.
|
||||||
|
|
||||||
|
argon2id
|
||||||
|
--------
|
||||||
|
|
||||||
|
You should *specifically* use argon2id. Please ensure this, because some
|
||||||
|
older LUKS2 setups defaulted to the weaker *argon2i*. This post by Matthew
|
||||||
|
Garret contains information about that:
|
||||||
|
|
||||||
|
<https://mjg59.dreamwidth.org/66429.html>
|
||||||
|
|
||||||
NOTE: You should also read the instructions about about `GRUB_TERMINAL`.
|
NOTE: You should also read the instructions about about `GRUB_TERMINAL`.
|
||||||
|
|
||||||
Rebooting system in case of freeze
|
Rebooting system in case of freeze
|
||||||
|
|
|
@ -3,6 +3,9 @@ title: lbmk maintenance manual
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
In addition to this manual, you should also refer to [porting.md](porting.md)
|
In addition to this manual, you should also refer to [porting.md](porting.md)
|
||||||
and [testing.md](testing.md).
|
and [testing.md](testing.md).
|
||||||
|
|
||||||
|
@ -82,6 +85,31 @@ the [freedom status page](../../freedom-status.md).
|
||||||
Before *configuration* info, you will first be shown a brief overview of every
|
Before *configuration* info, you will first be shown a brief overview of every
|
||||||
project that Libreboot imports, such as coreboot.
|
project that Libreboot imports, such as coreboot.
|
||||||
|
|
||||||
|
Environmental variables
|
||||||
|
=======================
|
||||||
|
|
||||||
|
XBMK\_THREADS
|
||||||
|
-------------
|
||||||
|
|
||||||
|
For example:
|
||||||
|
|
||||||
|
export XBMK_THREADS=2
|
||||||
|
|
||||||
|
This would build on two threads, when running lbmk. It defaults to 1.
|
||||||
|
|
||||||
|
Previous revisions of lbmk used `nproc` by default, but this was set to 1
|
||||||
|
instead, because nproc is not available on every operating system.
|
||||||
|
|
||||||
|
XBMK\_RELEASE
|
||||||
|
-------------
|
||||||
|
|
||||||
|
If set to `y`, it signals to `script/roms` that a release is being built,
|
||||||
|
and it will honour `release="n"` in target.cfg files. You could also set this
|
||||||
|
yourself, when doing regular builds, if you wanted to test how `./build roms`
|
||||||
|
behaves running it in release mode. Do this if you want to:
|
||||||
|
|
||||||
|
export XBMK_RELEASE=y
|
||||||
|
|
||||||
Projects/files downloaded/generated by lbmk
|
Projects/files downloaded/generated by lbmk
|
||||||
===========================================
|
===========================================
|
||||||
|
|
||||||
|
@ -99,8 +127,8 @@ This directory is created when running any of the following commands, with the
|
||||||
right arguments:
|
right arguments:
|
||||||
|
|
||||||
./build roms ARGUMENTS_HERE
|
./build roms ARGUMENTS_HERE
|
||||||
./build serprog stm32
|
./build roms serprog stm32
|
||||||
./build serprog rp2040
|
./build roms serprog rp2040
|
||||||
|
|
||||||
Simply speaking, `bin/` shall contain finished ROM images or firmware, that
|
Simply speaking, `bin/` shall contain finished ROM images or firmware, that
|
||||||
can then be installed (flashed) to the target device.
|
can then be installed (flashed) to the target device.
|
||||||
|
@ -110,12 +138,6 @@ The files under `bin/` are provided in regular Libreboot releases.
|
||||||
**These** are the ROM images that you should flash. Do *not* flash the ROM
|
**These** are the ROM images that you should flash. Do *not* flash the ROM
|
||||||
images contained under `elf/`!
|
images contained under `elf/`!
|
||||||
|
|
||||||
cbutils/
|
|
||||||
---------------
|
|
||||||
|
|
||||||
The build system compiles `cbfstool` and `ifdtool`, from coreboot, and then
|
|
||||||
places the executables here for use on coreboot ROM images.
|
|
||||||
|
|
||||||
ec/
|
ec/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
|
@ -145,18 +167,14 @@ lbmk in your own custom coreboot ROM (that you didn't build with lbmk).
|
||||||
This is only used by the build system, but these images are *not* provided in
|
This is only used by the build system, but these images are *not* provided in
|
||||||
releases (only the images under `bin/` are provided).
|
releases (only the images under `bin/` are provided).
|
||||||
|
|
||||||
|
As of Libreboot 20240612, the `elf/` directory must be used by default for all
|
||||||
|
builds, in an effort to make exclusive use of *out-of-source builds*. As such,
|
||||||
|
the `cbutils` directory is no longer used.
|
||||||
|
|
||||||
mrc/
|
mrc/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
Please also
|
Intel System Agent downloaded at build time for HP EliteBook 820 G2.
|
||||||
visit: <https://doc.coreboot.org/northbridge/intel/haswell/mrc.bin.html> - the
|
|
||||||
handling of this, in Libreboot, is based largely on the information there.
|
|
||||||
|
|
||||||
This contains the Intel MRC firmware, auto-downloaded during build
|
|
||||||
by `script/vendor/download`.
|
|
||||||
|
|
||||||
In some cases, libre MRC firmware is also available, and provided
|
|
||||||
by Libreboot as an alternative choice.
|
|
||||||
|
|
||||||
pciroms/
|
pciroms/
|
||||||
---------------
|
---------------
|
||||||
|
@ -168,7 +186,7 @@ currently only initialises Intel GPUs natively, on Libreboot systems.
|
||||||
release/
|
release/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
The script at `script/update/release` create tarballs in here, which
|
The script at `build` create tarballs in here, which
|
||||||
constitute regular Libreboot releases. It is meticulously maintained, as per
|
constitute regular Libreboot releases. It is meticulously maintained, as per
|
||||||
current lbmk behaviour, and executed so as to provide Libreboot release
|
current lbmk behaviour, and executed so as to provide Libreboot release
|
||||||
archives.
|
archives.
|
||||||
|
@ -178,6 +196,26 @@ containing non-redistributable vendor code are *scrubbed* such that these files
|
||||||
in regular releases, be [re-added manually](../install/ivy_has_common.md) by
|
in regular releases, be [re-added manually](../install/ivy_has_common.md) by
|
||||||
the user.
|
the user.
|
||||||
|
|
||||||
|
You can create release archives by doing:
|
||||||
|
|
||||||
|
./update release
|
||||||
|
|
||||||
|
By default, this creates a release under `release/`, but you can change the
|
||||||
|
directory, for example:
|
||||||
|
|
||||||
|
./update release -d path
|
||||||
|
|
||||||
|
You can also specify that only a *source archive* be created, like so:
|
||||||
|
|
||||||
|
./update release -m src
|
||||||
|
|
||||||
|
Or with a custom directory:
|
||||||
|
|
||||||
|
./update release -d path -m src
|
||||||
|
|
||||||
|
The build system expects there to be a *git tag*, so make sure there is one.
|
||||||
|
This is used to create the version number for a given release.
|
||||||
|
|
||||||
src/
|
src/
|
||||||
----
|
----
|
||||||
|
|
||||||
|
@ -189,8 +227,9 @@ src/bios\_extract/
|
||||||
Used by the vendor file handler scripts. The upstream that we use is here:
|
Used by the vendor file handler scripts. The upstream that we use is here:
|
||||||
<https://review.coreboot.org/bios_extract>
|
<https://review.coreboot.org/bios_extract>
|
||||||
|
|
||||||
Specifically: the pfs extract utility from this is used on Dell vendor updates,
|
The `dell_inspiron_1100_unpacker.py` script is used here, to extract from Dell
|
||||||
to extract SCH5545 EC (Environment Control) firmware.
|
BIOS updates, to get at the VGA ROM for Nvidia GPU on certain models of Dell
|
||||||
|
Latitude E6400.
|
||||||
|
|
||||||
src/biosutilities/
|
src/biosutilities/
|
||||||
---------------
|
---------------
|
||||||
|
@ -198,9 +237,8 @@ src/biosutilities/
|
||||||
Used by the vendor file handler scripts. The upstream that we use is here:
|
Used by the vendor file handler scripts. The upstream that we use is here:
|
||||||
<https://github.com/platomav/BIOSUtilities>
|
<https://github.com/platomav/BIOSUtilities>
|
||||||
|
|
||||||
The `dell_inspiron_1100_unpacker.py` script is used here, to extract from Dell
|
Specifically: the pfs extract utility from this is used on Dell vendor updates,
|
||||||
BIOS updates, to get at the VGA ROM for Nvidia GPU on certain models of Dell
|
to extract SCH5545 EC (Environment Control) firmware.
|
||||||
Latitude E6400.
|
|
||||||
|
|
||||||
src/coreboot/
|
src/coreboot/
|
||||||
---------------
|
---------------
|
||||||
|
@ -222,12 +260,12 @@ This may be less efficient on disk usage, but it simplifies the logic greatly.
|
||||||
Coreboot also uses its own toolchain called *crossgcc*, and crossgcc is in fact
|
Coreboot also uses its own toolchain called *crossgcc*, and crossgcc is in fact
|
||||||
compiled *per tree* in Libreboot.
|
compiled *per tree* in Libreboot.
|
||||||
|
|
||||||
src/flashrom/
|
src/flashprog/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
Please also visit: <https://flashrom.org/>
|
Please also visit: <https://flashprog.org/>
|
||||||
|
|
||||||
Although currently unused by any part of lbmk, we provide flashrom for the
|
Although currently unused by any part of lbmk, we provide flashprog for the
|
||||||
convenience of users, and this is copied to release archives. Flashrom is the
|
convenience of users, and this is copied to release archives. Flashrom is the
|
||||||
program that you will use to read, erase and write the flash, containing
|
program that you will use to read, erase and write the flash, containing
|
||||||
coreboot firmware.
|
coreboot firmware.
|
||||||
|
@ -250,23 +288,6 @@ GRUB image under `elf/grub/`.
|
||||||
NOTE: This is *only* provided for x86 machines, in Libreboot. For ARM, we ship
|
NOTE: This is *only* provided for x86 machines, in Libreboot. For ARM, we ship
|
||||||
U-Boot instead.
|
U-Boot instead.
|
||||||
|
|
||||||
src/me\_cleaner/
|
|
||||||
---------------
|
|
||||||
|
|
||||||
Please also visit: <https://github.com/corna/me_cleaner/>
|
|
||||||
|
|
||||||
This is used by Libreboot, to *neuter* Intel ME images. The intel ME images
|
|
||||||
are auto-downloaded from the vendor during each build process, cached on
|
|
||||||
disk and processed by `me_cleaner`. It removes almost all code from Intel ME,
|
|
||||||
leaving only the basic bringup code (analogous to running coreboot without a
|
|
||||||
payload). More information available at these pages:
|
|
||||||
|
|
||||||
* <https://github.com/corna/me_cleaner/>
|
|
||||||
* Libreboot [freedom status page](../../freedom-status.md)
|
|
||||||
|
|
||||||
The *vendor file* scripts are what handle this, specifically the download script
|
|
||||||
located at `script/vendor/download`.
|
|
||||||
|
|
||||||
src/memtest86plus/
|
src/memtest86plus/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
|
@ -307,7 +328,7 @@ src/uefitool/
|
||||||
Please also visit: <https://github.com/LongSoft/UEFITool>
|
Please also visit: <https://github.com/LongSoft/UEFITool>
|
||||||
|
|
||||||
This is compiled, so as to provide `UEFIExtract`. Currently used by the
|
This is compiled, so as to provide `UEFIExtract`. Currently used by the
|
||||||
vendor download script at `script/vendor/download`, to download SCH5545 EC
|
vendor download logic within `include/vendor.sh`, to download SCH5545 EC
|
||||||
firmware (used for fan control on Dell Precision T1650).
|
firmware (used for fan control on Dell Precision T1650).
|
||||||
|
|
||||||
src/pico-serprog
|
src/pico-serprog
|
||||||
|
@ -348,7 +369,7 @@ may not have much RAM.
|
||||||
Where large files (or a large number of files) are handled by lbmk on a
|
Where large files (or a large number of files) are handled by lbmk on a
|
||||||
temporary basis, this `tmp/` directory is created and then used.
|
temporary basis, this `tmp/` directory is created and then used.
|
||||||
|
|
||||||
vendor/
|
vendorfiles/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
Used by the vendor file handler scripts, referenced in certain coreboot configs.
|
Used by the vendor file handler scripts, referenced in certain coreboot configs.
|
||||||
|
@ -371,9 +392,6 @@ desirable, `lbmk.git` provides a few utilities as part of itself, namely:
|
||||||
util/dell-flash-unlock/
|
util/dell-flash-unlock/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
**NOTE (15 October 2023): The util is now called `dell-flash-unlock`, but it
|
|
||||||
was previously called `e6400-flash-unlock`. Links have been updated.**
|
|
||||||
|
|
||||||
This program, written by Nicholas Chin, unlocks the boot flash on Dell Latitude
|
This program, written by Nicholas Chin, unlocks the boot flash on Dell Latitude
|
||||||
E6400; it permits internal flashing, from factory firmware to Libreboot, so that
|
E6400; it permits internal flashing, from factory firmware to Libreboot, so that
|
||||||
the user need not disassemble and flash externally.
|
the user need not disassemble and flash externally.
|
||||||
|
@ -458,6 +476,25 @@ config/
|
||||||
This directory contains configuration files, used by the Libreboot build
|
This directory contains configuration files, used by the Libreboot build
|
||||||
system. These next sections will cover specific configuration files.
|
system. These next sections will cover specific configuration files.
|
||||||
|
|
||||||
|
config/PROJECT\*/nuke.list
|
||||||
|
--------------------------
|
||||||
|
|
||||||
|
The script `include/git.sh` handles deletion of certain files, for downloaded
|
||||||
|
projects, based on a `nuke.list` file that can (for single-tree projects) be
|
||||||
|
included at `config/PROJECT/nuke.list` or (multi-tree project)
|
||||||
|
at `config/PROJECT/TREE/nuke.list` (entries are relative links from the root
|
||||||
|
directory of the given source tree e.g. `src/coreboot/default/`).
|
||||||
|
|
||||||
|
So, if `src/coreboot/default/` contained foo/bar.txt, you could add to
|
||||||
|
the `nuke.list` file as follows:
|
||||||
|
|
||||||
|
```
|
||||||
|
foo/bar.txt
|
||||||
|
```
|
||||||
|
|
||||||
|
Ditto `src/flashprog/`, if you wanted to delete a file from in there, as one
|
||||||
|
other example. Deletions occur when the source tree is created.
|
||||||
|
|
||||||
config/vendor/
|
config/vendor/
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
|
@ -486,7 +523,7 @@ When a given coreboot tree is compiled, for a given target, this file defines
|
||||||
which files to copy from the coreboot directory, which are then copied to
|
which files to copy from the coreboot directory, which are then copied to
|
||||||
a location under `elf/coreboot`.
|
a location under `elf/coreboot`.
|
||||||
|
|
||||||
The presence of this file affects behaviour in `script/update/release`;
|
The presence of this file affects behaviour in `./update release` commands;
|
||||||
specifically, PROJECT is then downloaded to `src/PROJECT/PROJECT`, and files
|
specifically, PROJECT is then downloaded to `src/PROJECT/PROJECT`, and files
|
||||||
under `config/PROJECT/TARGET/target.cfg` define which tree to use, which then
|
under `config/PROJECT/TARGET/target.cfg` define which tree to use, which then
|
||||||
looks under `config/PROJECT/TREE/target.cfg` to get the git revision; then
|
looks under `config/PROJECT/TREE/target.cfg` to get the git revision; then
|
||||||
|
@ -527,37 +564,34 @@ This file can contain several configuration lines, each being a string, such
|
||||||
as:
|
as:
|
||||||
|
|
||||||
* `tree="default"` (example entry)
|
* `tree="default"` (example entry)
|
||||||
* `romtype="normal"` (example entry)
|
|
||||||
* `rev="ad983eeec76ecdb2aff4fb47baeee95ade012225"` (example entry)
|
* `rev="ad983eeec76ecdb2aff4fb47baeee95ade012225"` (example entry)
|
||||||
* `arch="x86_64"` (example entry)
|
* `xarch="i386-elf"` (example entry)
|
||||||
* `payload_grub="y"` (example entry)
|
* `payload_grub="y"` (example entry)
|
||||||
* `payload_grub_withseabios="y"` (example entry)
|
* `payload_grub_withseabios="y"` (example entry)
|
||||||
* `payload_seabios="y"` (example entry)
|
* `payload_seabios="y"` (example entry)
|
||||||
* `payload_memtest="y"` (example entry)
|
* `payload_memtest="y"` (example entry)
|
||||||
* `payload_uboot="y"` (example entry)
|
* `payload_uboot="y"` (example entry)
|
||||||
* `payload_seabios_withgrub="y"` (example entry)
|
* `payload_seabios_withgrub="y"` (example entry)
|
||||||
|
* `payload_seabios_grubonly="y"` (example entry)
|
||||||
* `grub_scan_disk="ata"`
|
* `grub_scan_disk="ata"`
|
||||||
* `uboot_config=default` (specify which U-Boot tree to use)
|
* `uboot_config=default` (specify which U-Boot tree to use)
|
||||||
* `vendorfiles="n"`
|
* `release="n"` (example entry)
|
||||||
* `microcode_required="y"`
|
* `xtree="default"` (example entry)
|
||||||
|
* `tree_depend="default"` (example entry)
|
||||||
|
* `grubtree="nvme" (example entry)`
|
||||||
|
|
||||||
The `tree` value refers to `config/coreboot/TREE`; in other words, a given
|
The `tree` value refers to `config/coreboot/TREE`; in other words, a given
|
||||||
target could specify a name other than its own as the tree; it would then
|
target could specify a name other than its own as the tree; it would then
|
||||||
re-use code from that tree, rather than providing its own.
|
re-use code from that tree, rather than providing its own.
|
||||||
|
|
||||||
The `romtype` entry is used during the building of ROM images, to define
|
|
||||||
special steps; for example, d8d16sas` would tell lbmk that a fake PIKE2008
|
|
||||||
ROM must be inserted into CBFS (prevents hanging on SeaBIOS).
|
|
||||||
|
|
||||||
The `rev` entry defines which coreboot revision to use, from the
|
The `rev` entry defines which coreboot revision to use, from the
|
||||||
coreboot Git repository. *At present, lbmk only supports use of the official
|
coreboot Git repository. *At present, lbmk only supports use of the official
|
||||||
repository from the upstream coreboot project*.
|
repository from the upstream coreboot project*.
|
||||||
|
|
||||||
The `arch` entry specifies which CPU architecture is to be used: currently
|
The `xarch` entry specifies which CPU architecture is to be used: currently
|
||||||
recognized entries are `x86_32`, `x86_64`, `ARMv7` and `AArch64`. *Setting it
|
recognized entries are `i386-elf`, `arm-eabi` and `aarch64-elf`. This is the
|
||||||
to a non-native arch means that necessary crossgcc-arch will be compiled and be
|
target architecture for building GCC/toolchain from coreboot crossgcc,
|
||||||
available when building roms, but not necessarily built or discovered when
|
hence `xarch`.
|
||||||
individual scripts are called manually.*
|
|
||||||
|
|
||||||
The `payload_grub` entry specifies whether or not GRUB is to be included in
|
The `payload_grub` entry specifies whether or not GRUB is to be included in
|
||||||
ROM images.
|
ROM images.
|
||||||
|
@ -571,6 +605,11 @@ in ROM images. This option is *automatically* enabled
|
||||||
if `payload_grub_withseabios` and/or `payload_seabios_withgrub` are also turned
|
if `payload_grub_withseabios` and/or `payload_seabios_withgrub` are also turned
|
||||||
on.
|
on.
|
||||||
|
|
||||||
|
The `payload_seabios_grubonly` option, if enabled, creates separate ROM
|
||||||
|
images alongside regular `seabios_withgrub` ones, where the `grubonly` ones
|
||||||
|
start SeaBIOS but disable the menu and only ever load GRUB from CBFS, which
|
||||||
|
then provides the boot for your machine.
|
||||||
|
|
||||||
The `payload_memtest` entry specifies whether or not MemTest86+ is to be
|
The `payload_memtest` entry specifies whether or not MemTest86+ is to be
|
||||||
included in ROM images; it will only be included in ROM images for *text mode*
|
included in ROM images; it will only be included in ROM images for *text mode*
|
||||||
startup, on x86 machines.
|
startup, on x86 machines.
|
||||||
|
@ -591,12 +630,20 @@ on a ThinkPad X60 with the optical drive may cause GRUB to hang, so on that
|
||||||
machine it is advisable to set this option to `ahci` (becuse the default HDD
|
machine it is advisable to set this option to `ahci` (becuse the default HDD
|
||||||
slot is AHCI).
|
slot is AHCI).
|
||||||
|
|
||||||
The `vendorfiles` entry doesn't affect anything in code, except that
|
The `release` variable can be set to n, which makes the `./update release`
|
||||||
the `noblobs` string will be appended to ROM image file names, on releases;
|
call skip that target, when creating release images. For example, a given
|
||||||
ditto `nomicrocode` but in that case, the behaviour is: if no microcode to
|
board may not be stable and you don't want images for it to be included in the
|
||||||
begin with, only `nomicrocode` images will be named, otherwise ROM images with
|
release.
|
||||||
and without microcode updates will be provided in releases (CPU microcode
|
|
||||||
updates).
|
The `xtree` option specifies that a given tree with use a specific coreboot
|
||||||
|
tree for compiling crossgcc. This can be used to skip building gcc if OK on
|
||||||
|
a given board; two trees may use the same crossgcc as each other.
|
||||||
|
|
||||||
|
The `tree_depend` option means that a given tree needs another tree, defined
|
||||||
|
by this variable, to also be present.
|
||||||
|
|
||||||
|
The `grubtree` option specifies which GRUB tree to use. If unset, it defers to
|
||||||
|
the `default` GRUB tree.
|
||||||
|
|
||||||
### config/coreboot/BOARDNAME/config/
|
### config/coreboot/BOARDNAME/config/
|
||||||
|
|
||||||
|
@ -704,18 +751,18 @@ of their own; for example, `config/grub/` exists.
|
||||||
Multiple files exist here, and they are *concatenated* in a temporary file by
|
Multiple files exist here, and they are *concatenated* in a temporary file by
|
||||||
lbmk, which is then scanned to find information about projects.
|
lbmk, which is then scanned to find information about projects.
|
||||||
|
|
||||||
config/grub/
|
GRUB config
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
### config/grub/background
|
### config/data/grub/background
|
||||||
|
|
||||||
Splash screen images applied duing startup when using the GRUB payload.
|
Splash screen images applied duing startup when using the GRUB payload.
|
||||||
|
|
||||||
### config/grub/background/background1024x768.png
|
### config/data/grub/background/background1024x768.png
|
||||||
|
|
||||||
Used on ThinkPad X60 and T60.
|
Used on ThinkPad X60 and T60.
|
||||||
|
|
||||||
### config/grub/background/background1280x800.png
|
### config/data/grub/background/background1280x800.png
|
||||||
|
|
||||||
Used on all other machines, besides X60 and T60 thinkpads.
|
Used on all other machines, besides X60 and T60 thinkpads.
|
||||||
|
|
||||||
|
@ -725,11 +772,11 @@ example, `config/coreboot/x60/target.cfg` specifies this:
|
||||||
|
|
||||||
grub_background="background1024x768.png"
|
grub_background="background1024x768.png"
|
||||||
|
|
||||||
### config/grub/background/COPYING
|
### config/data/grub/background/COPYING
|
||||||
|
|
||||||
Licensing info for GRUB bootsplash images.
|
Licensing info for GRUB bootsplash images.
|
||||||
|
|
||||||
### config/grub/config/
|
### config/grub/TREE/config/
|
||||||
|
|
||||||
GRUB configuration files.
|
GRUB configuration files.
|
||||||
|
|
||||||
|
@ -741,7 +788,7 @@ Author info for GRUB configuration files.
|
||||||
|
|
||||||
Licensing info for GRUB configuration files.
|
Licensing info for GRUB configuration files.
|
||||||
|
|
||||||
### config/grub/config/grub.cfg
|
### config/grub/TREE/config/grub.cfg
|
||||||
|
|
||||||
This is a configuration file. It is used to program GRUB's shell.
|
This is a configuration file. It is used to program GRUB's shell.
|
||||||
|
|
||||||
|
@ -755,7 +802,7 @@ A `grubtest.cfg` can be inserted into CBFS, but it will not override the
|
||||||
default `grub.cfg` (either in CBFS or on memdisk); however, the one in memdisk
|
default `grub.cfg` (either in CBFS or on memdisk); however, the one in memdisk
|
||||||
will provide a menuentry for switching to this, if available.
|
will provide a menuentry for switching to this, if available.
|
||||||
|
|
||||||
### config/grub/config/grub\_memdisk.cfg
|
### config/data/grub/config/memdisk.cfg
|
||||||
|
|
||||||
This GRUB configuration checks whether `grub.cfg` exists in CBFS and switches
|
This GRUB configuration checks whether `grub.cfg` exists in CBFS and switches
|
||||||
to that first (not provided by default) or, if one is not available in CBFS,
|
to that first (not provided by default) or, if one is not available in CBFS,
|
||||||
|
@ -765,12 +812,12 @@ The GRUB memdisk is a file system within `grub.elf`, itself stored within the
|
||||||
coreboot file system named *CBFS*, which is part of the coreboot ROM image on
|
coreboot file system named *CBFS*, which is part of the coreboot ROM image on
|
||||||
every coreboot target.
|
every coreboot target.
|
||||||
|
|
||||||
### config/grub/keymap/
|
### config/data/grub/keymap/
|
||||||
|
|
||||||
Keymap files used by GRUB. They can alter the character set corresponding to
|
Keymap files used by GRUB. They can alter the character set corresponding to
|
||||||
inputted scancodes.
|
inputted scancodes.
|
||||||
|
|
||||||
### config/grub/keymap/\*.gkb
|
### config/data/grub/keymap/\*.gkb
|
||||||
|
|
||||||
The keymap files themselves. These are inserted into the GRUB memdisk, and
|
The keymap files themselves. These are inserted into the GRUB memdisk, and
|
||||||
the `grub.cfg` file can specify which one is to be used.
|
the `grub.cfg` file can specify which one is to be used.
|
||||||
|
@ -779,7 +826,7 @@ These files are binary-encoded, defining which characters correspond to which
|
||||||
scancodes. It is handled by `grub-core/commands/keylayouts.c` in the GRUB source
|
scancodes. It is handled by `grub-core/commands/keylayouts.c` in the GRUB source
|
||||||
code.
|
code.
|
||||||
|
|
||||||
### config/grub/modules.list
|
### config/grub/TREE/modules.list
|
||||||
|
|
||||||
This defines which modules are inserted into `grub.elf`. These modules can be
|
This defines which modules are inserted into `grub.elf`. These modules can be
|
||||||
anything from file systems, small applications/utilities, launchers (e.g.
|
anything from file systems, small applications/utilities, launchers (e.g.
|
||||||
|
@ -945,6 +992,56 @@ Another interesting config option is `CONFIG_POSITION_INDEPENDENT` for ARM
|
||||||
boards, which has been so far enabled in the ones `lbmk` supports, just to be
|
boards, which has been so far enabled in the ones `lbmk` supports, just to be
|
||||||
safe.
|
safe.
|
||||||
|
|
||||||
|
config/submodule
|
||||||
|
----------------
|
||||||
|
|
||||||
|
In here you can find submodule configurations for projects. It works for both
|
||||||
|
single- and multi-tree projects. Use the existing examples as reference.
|
||||||
|
|
||||||
|
Files, in each directory:
|
||||||
|
|
||||||
|
* `module.list` lists paths (files and directories) for given modules, which
|
||||||
|
can be files(via URL) or Git repositories, or both.
|
||||||
|
* NAME/module.cfg
|
||||||
|
|
||||||
|
NAME is the file/directory name for the module, with everything up to the
|
||||||
|
final forward slash removed. E.g. foo/bar/thing.zip would be thing.zip as
|
||||||
|
NAME.
|
||||||
|
|
||||||
|
In `module.cfg` there can be either, file:
|
||||||
|
|
||||||
|
```
|
||||||
|
subfile="url"
|
||||||
|
subfile_bkup="url"
|
||||||
|
subhash="sha512sum for file"
|
||||||
|
```
|
||||||
|
|
||||||
|
or, git repository:
|
||||||
|
|
||||||
|
```
|
||||||
|
subrepo="url"
|
||||||
|
subrepo_bkup="url"
|
||||||
|
subhash="sha1 git commit id"
|
||||||
|
```
|
||||||
|
|
||||||
|
You must only use `subfile` or `subrepo`, not both, and there must be a backup
|
||||||
|
URL. The build system intentionally *avoids* using Git's actual submodules
|
||||||
|
feature, instead opting to download such repositories manually, because the
|
||||||
|
official submodules feature doesn't have very good redundancy.
|
||||||
|
|
||||||
|
Additionally, a `patches` directory can be included alongside `module.cfg`,
|
||||||
|
which can be used to patch the submodule (only supported for Git repositories
|
||||||
|
because files are not extracted, only placed at their configured destination).
|
||||||
|
|
||||||
|
The destination path in `module.list` is relative to the location of the main
|
||||||
|
Git repository under which it is placed.
|
||||||
|
|
||||||
|
config/data/PROJECT
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
Random configuration data provided on a per-project basis. Complements
|
||||||
|
the `config/PROJECT` directory.
|
||||||
|
|
||||||
U-Boot build system
|
U-Boot build system
|
||||||
-------------------
|
-------------------
|
||||||
|
|
||||||
|
@ -1000,7 +1097,7 @@ Updated each time lbmk runs, based on either `git describe` or, on release
|
||||||
archives, this file is static and never changes. It says the *time* of
|
archives, this file is static and never changes. It says the *time* of
|
||||||
whichever Libreboot revision is currently in use (time of commit).
|
whichever Libreboot revision is currently in use (time of commit).
|
||||||
|
|
||||||
At least, you will now learn about the *scripts* (exclusively written as
|
At last, you will now learn about the *scripts* (exclusively written as
|
||||||
posix shell scripts) that constitute the entire Libreboot build system, lbmk:
|
posix shell scripts) that constitute the entire Libreboot build system, lbmk:
|
||||||
|
|
||||||
Scripts in root directory of lbmk
|
Scripts in root directory of lbmk
|
||||||
|
@ -1009,34 +1106,37 @@ Scripts in root directory of lbmk
|
||||||
build
|
build
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
This is the main script in lbmk, Libreboot's build system. It is what executes
|
This is the main script. Symlinks `vendor` and `update` also point to it.
|
||||||
all other parts of the Libreboot build system. The rules are as follows:
|
|
||||||
|
|
||||||
* Argument zero, representing the name of the symlink, will be used to
|
Take any given file under `script/` and you can do:
|
||||||
execute `script/LINKNAME/mode/option` - for example: `./build roms all`
|
|
||||||
would execute `script/build/roms all` in `sh`.
|
|
||||||
* `TMPDIR` is exclicitly set, providing a constant location where temporary
|
|
||||||
files and directories can be made. `TMPDIR` is exported by the parent to
|
|
||||||
all children; for example, `./build roms all` would export it
|
|
||||||
to `script/build/roms`, and then anything called by *that* will also
|
|
||||||
inherit it - the main parent process running `lbmk` will then clean up this
|
|
||||||
`TMPDIR` directory upon any exit.
|
|
||||||
* All exits from lbmk are handled by this script. *All* exits, zero or non-zero,
|
|
||||||
are engineered such that *this* script, in the parent process (the very first
|
|
||||||
instance) is what ultimately exits back to the user's shell prompt.
|
|
||||||
* This script is programmed to *exit* with non-zero status, when run as root,
|
|
||||||
unless the `./build dependencies *` commands are used,
|
|
||||||
referencing files under `config/dependencies/`
|
|
||||||
* Under fault conditions, each child process shall output to stderr, and the
|
|
||||||
main parent process running `lbmk` will output the final error message.
|
|
||||||
|
|
||||||
tl;dr break this script and you *break Libreboot*.
|
./build file # (THIS IS NOT A VALID COMMAND)
|
||||||
|
|
||||||
update
|
For example:
|
||||||
---------------
|
|
||||||
|
|
||||||
Symbolic link, pointing to the `build` script. This is executed by the user, or
|
./build roms
|
||||||
by lbmk, referencing scripts under `script/update/*/`.
|
./update trees
|
||||||
|
|
||||||
|
Special commands available (not provided by files under `script/`):
|
||||||
|
|
||||||
|
./update release
|
||||||
|
./vendor download
|
||||||
|
./vendor inject
|
||||||
|
|
||||||
|
The `vendor` commands are handled by the `build` script, calling functions
|
||||||
|
inside `include/vendor.sh`, and the `./update release` logic is handled
|
||||||
|
directly by the `build` script.
|
||||||
|
|
||||||
|
More information about `./vendor` commands can be found
|
||||||
|
here: [inserting vendor files](../install/ivy_has_internal.md)
|
||||||
|
|
||||||
|
Information about `./update release` is written elsewhere on this page.
|
||||||
|
|
||||||
|
You can also know what build system revision you have by running:
|
||||||
|
|
||||||
|
./build version
|
||||||
|
|
||||||
|
This script is the beating heart of Libreboot. Break it and you break Libreboot.
|
||||||
|
|
||||||
include/
|
include/
|
||||||
===============
|
===============
|
||||||
|
@ -1045,27 +1145,6 @@ This directory contains *helper scripts*, to be included
|
||||||
by main scripts using the `.` command (called the `source`
|
by main scripts using the `.` command (called the `source`
|
||||||
command in `bash`, but we rely upon posix `sh` only).
|
command in `bash`, but we rely upon posix `sh` only).
|
||||||
|
|
||||||
include/err.sh
|
|
||||||
---------------
|
|
||||||
|
|
||||||
Generic error handling, used by all lbmk scripts.
|
|
||||||
|
|
||||||
This also contains functions to verify the current libreboot version, and check
|
|
||||||
whether Git is properly initialised on the host system. It also contains
|
|
||||||
the `setvars` function, which provides a shorthand way of initialising many
|
|
||||||
variables (combined with use of `eval`), which lbmk uses heavily.
|
|
||||||
|
|
||||||
This function also contains `x_` and `xx_` which lbmk uses to execute commands
|
|
||||||
and ensure that they cause an exit (with non-zero status) from lbmk, if they
|
|
||||||
return an error state; the `xx_` function calls `fail()` which a script must
|
|
||||||
provide, to perform some action before calling `err` which in turn prints an
|
|
||||||
error message provided as argument. It is used similarly to the C
|
|
||||||
function `err()` in BSD libc. The `x_` function simply calls `err`.
|
|
||||||
|
|
||||||
This entire file is heavily inspired by `err.h` in BSD libc code. This file is
|
|
||||||
heavily used by lbmk (it's used by every script), to provide clean error
|
|
||||||
handling in `sh`.
|
|
||||||
|
|
||||||
include/git.sh
|
include/git.sh
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
@ -1092,37 +1171,31 @@ it is provided as an include to bypass license incompatibility. It has been
|
||||||
heavily modified to use the same style of logic and general control flow used
|
heavily modified to use the same style of logic and general control flow used
|
||||||
in the script at `script/vendor/download`, and it is used from there.
|
in the script at `script/vendor/download`, and it is used from there.
|
||||||
|
|
||||||
include/option.sh
|
include/lib.sh
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
Functions used by scripts under `script/update/vendor/`, for checking defconfig
|
|
||||||
files. These files are checked because the scripts need to know whether a given
|
|
||||||
file is used; if it is, a path is then specified in defconfig, telling the vendor
|
|
||||||
script either where it is, or where it should be downloaded to.
|
|
||||||
|
|
||||||
Several other parts of lbmk also use this file. It is added to as little as
|
Several other parts of lbmk also use this file. It is added to as little as
|
||||||
possible, and contains miscallaneous functions that don't belong anywhere else.
|
possible, and contains miscallaneous functions that don't belong anywhere else.
|
||||||
|
|
||||||
The functions here are mostly those that deal with configuration files; scanning
|
The functions here are mostly those that deal with configuration files; scanning
|
||||||
them to set variables and so on.
|
them to set variables and so on.
|
||||||
|
|
||||||
|
This file also contains generic error handling, used by all lbmk scripts.
|
||||||
|
|
||||||
|
This also contains functions to verify the current libreboot version, and check
|
||||||
|
whether Git is properly initialised on the host system. It also contains
|
||||||
|
the `setvars` function, which provides a shorthand way of initialising many
|
||||||
|
variables (combined with use of `eval`), which lbmk uses heavily.
|
||||||
|
|
||||||
|
This function also contains `x_()` which lbmk uses to execute commands
|
||||||
|
and ensure that they cause an exit (with non-zero status) from lbmk, if they
|
||||||
|
return an error state.
|
||||||
|
|
||||||
script/
|
script/
|
||||||
=======
|
=======
|
||||||
|
|
||||||
*All* scripts under `script/` are executed only by the main `lbmk` script,
|
script/roms
|
||||||
conforming to the standard `buildpath/mode/option` e.g. `build/roms` - so,
|
-----------
|
||||||
running `./build roms` would run `script/build/roms`.
|
|
||||||
|
|
||||||
script/build/
|
|
||||||
---------------
|
|
||||||
|
|
||||||
These are highly specialised build scripts, written for specific tasks, almost
|
|
||||||
entirely in the context of building firmware images themselves, but some utils
|
|
||||||
are also handled.
|
|
||||||
|
|
||||||
The scripts that create release archives are also located under this directory.
|
|
||||||
|
|
||||||
### script/build/roms
|
|
||||||
|
|
||||||
This builds coreboot ROM images.
|
This builds coreboot ROM images.
|
||||||
|
|
||||||
|
@ -1164,28 +1237,6 @@ It creates ROM images with GRUB, SeaBIOS, U-Boot, optionally with Memtest86+
|
||||||
also included, in various separate configurations in many different ROM images
|
also included, in various separate configurations in many different ROM images
|
||||||
for user installation.
|
for user installation.
|
||||||
|
|
||||||
The `romtype` entry in `target.cfg` tells this script what to do with the ROM,
|
|
||||||
after it has been built. Currently, it operates based on these possible values
|
|
||||||
for `romtype`:
|
|
||||||
|
|
||||||
* `d8d16sas` will cause *fake* (empty) files named `pci1000,0072.rom`
|
|
||||||
and `pci1000,3050.rom` to be inserted in CBFS. This prevents SeaBIOS from
|
|
||||||
loading or executing the option ROM stored on PIKE2008 modules, present on
|
|
||||||
certain configurations with the ASUS KCMA-D8 or KGPE-D16 mainboards. Those
|
|
||||||
option ROMs cause the system to hang, so they should never be executed (this
|
|
||||||
means however that booting Linux kernels from SAS devices is impossible on
|
|
||||||
those boards, unless a Linux payload is used; Linux can use those SAS drives,
|
|
||||||
without relying on the PIKE2008 option ROMs). When SeaBIOS runs, it will
|
|
||||||
default to loading the corresponding option ROM from CBFS, if it exists, for
|
|
||||||
a given PCI device, overriding whatever option ROM is present on the device
|
|
||||||
itself, but if the option ROM is invalid/empty, SeaBIOS will not attempt to
|
|
||||||
load another one, until the empty/invalid one (in CBFS) is deleted.
|
|
||||||
* `i945 laptop`: in this configuration, the upper 64KB section of the ROM is
|
|
||||||
copied into the 64KB section below that. This results in there being two
|
|
||||||
bootblocks in the ROM, and you can decide which one is used by setting `bucts`
|
|
||||||
* If no declaration is made, or a declaration is made contrary to the above,
|
|
||||||
no special modifications will be made.
|
|
||||||
|
|
||||||
If no payload is defined in `target.cfg`, the `build/roms` script will exit
|
If no payload is defined in `target.cfg`, the `build/roms` script will exit
|
||||||
with error status.
|
with error status.
|
||||||
|
|
||||||
|
@ -1214,71 +1265,25 @@ When the ROM is finished compiling, it will appear under a directory in `bin/`
|
||||||
This script is the beating heart of Libreboot. Break it, and you break
|
This script is the beating heart of Libreboot. Break it, and you break
|
||||||
Libreboot!
|
Libreboot!
|
||||||
|
|
||||||
### script/build/grub
|
Serprog images:
|
||||||
|
|
||||||
This builds the `grub.elf` file and keymap configuration files, placing these
|
|
||||||
under `elf/grub/` for use by `script/build/roms`.
|
|
||||||
|
|
||||||
Command: `./build grub`
|
|
||||||
|
|
||||||
This builds the `grub-mkstandalone` utility under `src/grub/`, which is used
|
|
||||||
by `script/build/roms` to insert GRUB payloads inside coreboot ROM
|
|
||||||
images.
|
|
||||||
|
|
||||||
### script/build/serprog
|
|
||||||
|
|
||||||
Build firmware images for serprog-based SPI programmers, where they use an
|
Build firmware images for serprog-based SPI programmers, where they use an
|
||||||
STM32 MCU. It also builds for RP2040-based programmers like Raspberry Pi Pico.
|
STM32 MCU. It also builds for RP2040-based programmers like Raspberry Pi Pico.
|
||||||
|
|
||||||
Example command: `./build serprog stm32`
|
Example command: `./build roms serprog stm32`
|
||||||
|
|
||||||
Example command: `./build serprog rp2040`
|
Example command: `./build roms serprog rp2040`
|
||||||
|
|
||||||
The `list` argument is available:
|
The `list` argument is available:
|
||||||
|
|
||||||
./build serprog stm32 list
|
./build roms serprog stm32 list
|
||||||
|
./build roms serprog rp2040 list
|
||||||
|
|
||||||
Without arguments, all targets would be compiled, but you can specify a short
|
Without arguments, all targets would be compiled, but you can specify a short
|
||||||
list of targets instead, based on the output of `list`.
|
list of targets instead, based on the output of `list`.
|
||||||
|
|
||||||
script/update/
|
script/trees
|
||||||
--------------
|
------------
|
||||||
|
|
||||||
This handles most actual building of source trees, called into by scripts
|
|
||||||
under `script/build/fw` - it also contains logic for downloading source trees
|
|
||||||
or vendor files.
|
|
||||||
|
|
||||||
### script/update/release
|
|
||||||
|
|
||||||
This script builds the release archives, which are then provided in a new
|
|
||||||
Libreboot release. Most users do not need to look at this file at all, but it
|
|
||||||
is provided under free license for curious souls.
|
|
||||||
|
|
||||||
Command: `./update release`
|
|
||||||
|
|
||||||
NOTE: if the `-d` option is used, you can specify a directory other
|
|
||||||
than `release`. For example:
|
|
||||||
|
|
||||||
./update release -d /media/stuff/libreboot_release_test
|
|
||||||
|
|
||||||
If `-d` is not passed, they will go under `release/` in your lbmk repository.
|
|
||||||
The script is engineered to re-initialise git if ran from a release archive.
|
|
||||||
Libreboot releases after 20230625 include `.gitignore` in the src archive.
|
|
||||||
|
|
||||||
This builds release archives, containing ROM images for coreboot and/or serprog
|
|
||||||
programmers. It works simply: lbmk clones *itself*, and builds itself in its
|
|
||||||
clone, then cleans itself up and creates tarballs. If you run this script, you
|
|
||||||
should expect it to take at least 4 hours; slower on really old systems. On
|
|
||||||
really fast systems, it might take 2-3 hours.
|
|
||||||
|
|
||||||
NOTE: This script *scrubs* certain vendor firmware from release ROMs, such as
|
|
||||||
Intel ME or MRC firmware. The release ROMs shall then exclude these files
|
|
||||||
within them, requiring manual insertion by the user post-release. See:
|
|
||||||
|
|
||||||
[Insert vendor files
|
|
||||||
on Sandybridge/Ivybridge/Haswell](../install/ivy_has_common.md)
|
|
||||||
|
|
||||||
### script/update/trees
|
|
||||||
|
|
||||||
*This* is the other beating heart of Libreboot. Used heavily by Libreboot, this
|
*This* is the other beating heart of Libreboot. Used heavily by Libreboot, this
|
||||||
script is what handles defconfig files for SeaBIOS, U-Boot *and* coreboot; it
|
script is what handles defconfig files for SeaBIOS, U-Boot *and* coreboot; it
|
||||||
|
@ -1398,37 +1403,3 @@ All of this used to about 20 different scripts, all with much-duplicated logic.
|
||||||
Now it is unified, efficiently, under a single script.
|
Now it is unified, efficiently, under a single script.
|
||||||
|
|
||||||
Remember: code equals bugs, so less code equals fewer bugs.
|
Remember: code equals bugs, so less code equals fewer bugs.
|
||||||
|
|
||||||
script/vendor/
|
|
||||||
--------------
|
|
||||||
|
|
||||||
### script/vendor/download
|
|
||||||
|
|
||||||
This downloads vendor code when needed, on a given coreboot target. It does
|
|
||||||
this by scanning the defconfig files of that board, to know where the files
|
|
||||||
are (or where they should be) within lbmk. Based on this, it then knows which
|
|
||||||
files to download.
|
|
||||||
|
|
||||||
These files are then inserted at build time by the coreboot build system (as
|
|
||||||
defined by defconfigs), or post-release by running the `inject` script.
|
|
||||||
|
|
||||||
It looks inside `config/vendor/` at the files in there, concatenating them and
|
|
||||||
then scanning that to find info about the given board; for example, info like
|
|
||||||
where to download a Lenovo BIOS updater to extract `me.bin` from, to run through
|
|
||||||
the `me_cleaner` program.
|
|
||||||
|
|
||||||
More information is available [here](../install/ivy_has_common.md).
|
|
||||||
|
|
||||||
This script is executed automatically, when you compile ROM images, if the given
|
|
||||||
mainboard requires vendor code to be inserted. In this way, you do not need to
|
|
||||||
manually extract such files from your original vendor image.
|
|
||||||
|
|
||||||
### script/vendor/inject
|
|
||||||
|
|
||||||
This is not used during the build process, but it can be run by the user on
|
|
||||||
release ROMs (which do not contain non-redistributable code handled by these
|
|
||||||
vendor scripts, even if they are required). This script inserts those files
|
|
||||||
into the coreboot ROM image; if you're building from source, using lbmk, you
|
|
||||||
do not need to run the inject script at all.
|
|
||||||
|
|
||||||
More information is available [here](../install/ivy_has_common.md).
|
|
||||||
|
|
|
@ -2,6 +2,9 @@
|
||||||
title: Porting guide for new mainboards
|
title: Porting guide for new mainboards
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
NOTE: This page is largely Intel-centric, at present. It should be revised to
|
NOTE: This page is largely Intel-centric, at present. It should be revised to
|
||||||
cover more vendors. [Patches welcome!](../../git.md)
|
cover more vendors. [Patches welcome!](../../git.md)
|
||||||
|
|
||||||
|
@ -93,7 +96,7 @@ Wrong CBFS and or ROM size
|
||||||
|
|
||||||
Different boards have different flash chip setups.
|
Different boards have different flash chip setups.
|
||||||
Generally, you have one or two flash chips with a combined size of 4-16MB.
|
Generally, you have one or two flash chips with a combined size of 4-16MB.
|
||||||
Thankfully, flashrom will let you know the size of the flash chip you're flashing.
|
Thankfully, flashprog will let you know the size of the flash chip you're flashing.
|
||||||
For example: when flashing an X230, you'll see that one chip is 8192, and the other is 4096.
|
For example: when flashing an X230, you'll see that one chip is 8192, and the other is 4096.
|
||||||
The total rom size should therefore be set as 12MB.
|
The total rom size should therefore be set as 12MB.
|
||||||
|
|
||||||
|
|
|
@ -2,6 +2,9 @@
|
||||||
title: Керівництво перенесення
|
title: Керівництво перенесення
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Це керівнитво передбачається для тих, хто має дуже низький рівень знань про прошивку
|
Це керівнитво передбачається для тих, хто має дуже низький рівень знань про прошивку
|
||||||
загалом та coreboot окремо.
|
загалом та coreboot окремо.
|
||||||
Більшість плат в coreboot може бути доволі легко перенесена в libreboot.
|
Більшість плат в coreboot може бути доволі легко перенесена в libreboot.
|
||||||
|
@ -90,7 +93,7 @@ libreboot як `плата.`
|
||||||
|
|
||||||
Різні плати мають різні налаштування чіпів флеш-пам'яті.
|
Різні плати мають різні налаштування чіпів флеш-пам'яті.
|
||||||
Загалом, ви маєте один або два флеш-пам'яті з сумарним розміром в 4-16Мбайт.
|
Загалом, ви маєте один або два флеш-пам'яті з сумарним розміром в 4-16Мбайт.
|
||||||
На щастя, flashrom дасть вам знати розмір флеш-чіпа, який ви прошиваєте.
|
На щастя, flashprog дасть вам знати розмір флеш-чіпа, який ви прошиваєте.
|
||||||
Наприклад: коли прошиваєте X230, ви побачите, що один чіп 8192, та інший 4096.
|
Наприклад: коли прошиваєте X230, ви побачите, що один чіп 8192, та інший 4096.
|
||||||
Сумарний розмір rom тоді має бути встановлено на 12Мбайт.
|
Сумарний розмір rom тоді має бути встановлено на 12Мбайт.
|
||||||
|
|
||||||
|
|
|
@ -23,22 +23,38 @@ In order to test the resulting roms, you must have qemu installed on the host ma
|
||||||
Test the roms by pointing qemu to the rom in bios mode.
|
Test the roms by pointing qemu to the rom in bios mode.
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
`qemu-system-x86_64 -bios bin/qemu_x86_12mb/grub_qemu_x86_12mb_libgfxinit_corebootfb_usqwerty_noblobs.rom`
|
`qemu-system-x86_64 -bios bin/qemu_x86_12mb/grub_qemu_x86_12mb_libgfxinit_corebootfb_usqwerty.rom`
|
||||||
|
|
||||||
`qemu-system-x86_64 -bios bin/qemu_x86_12mb/uboot_payload_qemu_x86_12mb_libgfxinit_corebootfb_noblobs.rom -serial stdio`
|
`qemu-system-x86_64 -bios bin/qemu_x86_12mb/uboot_payload_qemu_x86_12mb_libgfxinit_corebootfb.rom -serial stdio`
|
||||||
|
|
||||||
There is basic support for an arm64 virtual machine as well, although the payloads are not as developed as the x86 one:
|
There is basic support for an arm64 virtual machine as well, although the payloads are not as developed as the x86 one:
|
||||||
|
|
||||||
./build roms qemu_arm64_12mb
|
./build roms qemu_arm64_12mb
|
||||||
|
|
||||||
```
|
```
|
||||||
qemu-system-aarch64 -bios bin/qemu_arm64_12mb/uboot_payload_qemu_arm64_12mb_libgfxinit_corebootfb_noblobs.rom \
|
qemu-system-aarch64 -bios bin/qemu_arm64_12mb/uboot_payload_qemu_arm64_12mb_libgfxinit_corebootfb.rom \
|
||||||
-M virt,secure=on,virtualization=on,acpi=on -cpu cortex-a53 -m 768M -serial stdio -vga none -display none
|
-M virt,secure=on,virtualization=on,acpi=on -cpu cortex-a53 -m 768M -serial stdio -vga none -display none
|
||||||
```
|
```
|
||||||
|
|
||||||
NOTE: After the 20230625 release, U-Boot support was removed from x86 Qemu; it's
|
That command (above) does a serial console. Alper Nebi Yasak added this patch to Libreboot:
|
||||||
also problematic on ARM-based Qemu. Only x86 qemu, with other payloads, is to
|
<https://browse.libreboot.org/lbmk.git/commit/?id=444f2899e69e9b84fd5428625aa04b00c1341804>
|
||||||
be considered reliable for now.
|
|
||||||
|
This enables a graphical display in qemu, like so (only works in releases
|
||||||
|
after Libreboot 20231021, but not including Libreboot 20231021, so you
|
||||||
|
must [build lbmk from git](../build/)). Command:
|
||||||
|
|
||||||
|
```
|
||||||
|
qemu-system-aarch64 \
|
||||||
|
-machine virt,secure=on,virtualization=on \
|
||||||
|
-cpu cortex-a72 -m 1G \
|
||||||
|
-serial stdio -device VGA \
|
||||||
|
-device qemu-xhci \
|
||||||
|
-device usb-kbd -device usb-mouse \
|
||||||
|
-bios bin/qemu_arm64_12mb/*.rom
|
||||||
|
```
|
||||||
|
|
||||||
|
NOTE: After the 20230625 release, U-Boot support was removed from x86 Qemu.
|
||||||
|
It works fine on the aaarch64 one.
|
||||||
|
|
||||||
Use Cases
|
Use Cases
|
||||||
=========
|
=========
|
||||||
|
|
|
@ -1,294 +0,0 @@
|
||||||
<!DOCTYPE html>
|
|
||||||
<html lang="en" dir="ltr">
|
|
||||||
<head>
|
|
||||||
<meta charset="utf-8">
|
|
||||||
<meta name="generator" content="pandoc">
|
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
|
||||||
|
|
||||||
<!-- anti-social media tags -->
|
|
||||||
<meta property="og:title" content="Libreboot – Downloads">
|
|
||||||
<meta property="og:type" content="article" />
|
|
||||||
<meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
|
|
||||||
<meta property="og:url" content="https://libreboot.org/download.html">
|
|
||||||
<meta name="twitter:card" content="summary_large_image">
|
|
||||||
<meta property="og:description" content="Libreboot – Downloads">
|
|
||||||
<meta property="og:site_name" content="Libreboot – Downloads">
|
|
||||||
<meta name="twitter:image:alt" content="Libreboot – Downloads">
|
|
||||||
|
|
||||||
<title>Libreboot – Downloads</title>
|
|
||||||
<link rel="stylesheet" href="/global.css">
|
|
||||||
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
|
|
||||||
</head>
|
|
||||||
<body>
|
|
||||||
<div class="page">
|
|
||||||
<header>
|
|
||||||
<div class="title">
|
|
||||||
<p class="title-logo">
|
|
||||||
<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
|
|
||||||
</p>
|
|
||||||
<h1 class="title">Downloads</h1>
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li><a href="/">Home</a></li>
|
|
||||||
<li><a href="/faq.html">FAQ</a></li>
|
|
||||||
<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li>
|
|
||||||
<li><strong><a href="/download.html">Download</a></strong></li>
|
|
||||||
<li><a href="/docs/install/">Install</a></li>
|
|
||||||
<li><a href="/docs/">Docs</a></li>
|
|
||||||
<li><a href="/news/">News</a></li>
|
|
||||||
<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
|
|
||||||
<li><a href="/git.html">Send patch</a></li>
|
|
||||||
<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li>
|
|
||||||
<li><a href="/contact.html">Contact</a></li>
|
|
||||||
<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li>
|
|
||||||
</ul>
|
|
||||||
<hr/>
|
|
||||||
</header>
|
|
||||||
<nav id="TOC">
|
|
||||||
<h1>Navigate this page:</h1>
|
|
||||||
<ul>
|
|
||||||
<li><a
|
|
||||||
href="#read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
|
|
||||||
THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</a>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#gpg-signing-key">GPG signing key</a>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#new-key">NEW KEY</a></li>
|
|
||||||
<li><a href="#old-key">OLD KEY:</a></li>
|
|
||||||
</ul></li>
|
|
||||||
<li><a href="#git-repository">Git repository</a></li>
|
|
||||||
<li><a href="#https">HTTPS mirrors</a></li>
|
|
||||||
<li><a href="#rsync">RSYNC mirrors</a></li>
|
|
||||||
<li><a href="#http">HTTP mirrors</a></li>
|
|
||||||
<li><a href="#ftp">FTP mirrors</a></li>
|
|
||||||
<li><a href="#statically-linked">Statically linked</a></li>
|
|
||||||
</ul></li>
|
|
||||||
</ul>
|
|
||||||
</nav>
|
|
||||||
<div class="pagetext">
|
|
||||||
<p><a href="download.html">English</a> | <a
|
|
||||||
href="download.uk.html">українська</a></p>
|
|
||||||
<p><a href="./">Return to index</a></p>
|
|
||||||
<p>New releases are announced in the <a href="news/">main news
|
|
||||||
section</a>.</p>
|
|
||||||
<p>If you’re more interested in libreboot development, go to the <a
|
|
||||||
href="../git.html">libreboot development page</a>, which also includes
|
|
||||||
links to the Git repositories. The page on <a
|
|
||||||
href="docs/maintain/">/docs/maintain/</a> describes how Libreboot is put
|
|
||||||
together, and how to maintain it. If you wish to build Libreboot from
|
|
||||||
source, <a href="docs/build/">read this page</a>.</p>
|
|
||||||
<h1
|
|
||||||
id="read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
|
|
||||||
THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</h1>
|
|
||||||
<p><strong>On newer Intel platforms that require Intel ME and/or MRC
|
|
||||||
firmware, such as ThinkPad X230 or T440p, and/or HP laptops that require
|
|
||||||
KBC1126 EC firmware, the release ROMs of Libreboot are MISSING certain
|
|
||||||
files, that you must insert yourself. FAILURE to adhere to this warning
|
|
||||||
may result in you bricking your machine (rendering it unbootable), if
|
|
||||||
you were to flash the release ROMs without modifying them in any way.
|
|
||||||
For more information, please read:</strong></p>
|
|
||||||
<p><strong><a href="docs/install/ivy_has_common.html">Insert vendor
|
|
||||||
files on Sandybridge/Ivybridge/Haswell</a></strong></p>
|
|
||||||
<p>NOTE: This warning does not apply to ROMs that you compiled yourself,
|
|
||||||
using lbmk. It only applies to release ROMs, because ME/MRC/EC firmware
|
|
||||||
is <em>deleted</em> in release ROMs. The link above says how to re-add
|
|
||||||
them. When building ROM images yourself, from source, Libreboot’s build
|
|
||||||
system automatically handles it. See: <a href="docs/build/">Libreboot
|
|
||||||
build instructions</a></p>
|
|
||||||
<p>This isn’t required on <em>all</em> Libreboot-supported boards, but
|
|
||||||
if in doubt, follow these instructions anyway. If you run the vendor
|
|
||||||
scripts on a board that doesn’t need blobs, nothing will happen.</p>
|
|
||||||
<div class="h"><h2 id="gpg-signing-key">GPG signing key</h2><a aria-hidden="true" href="#gpg-signing-key">[link]</a></div>
|
|
||||||
<p><strong>The latest release is Libreboot 20231021, under the
|
|
||||||
<code>testing</code> directory.</strong></p>
|
|
||||||
<div class="h"><h3 id="new-key">NEW KEY</h3><a aria-hidden="true" href="#new-key">[link]</a></div>
|
|
||||||
<p>Full key fingerprint:
|
|
||||||
<code>98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856</code></p>
|
|
||||||
<p>This key is for Libreboot releases <em>after</em> the 20160907
|
|
||||||
release.</p>
|
|
||||||
<p>Download the key here: <a href="lbkey.asc">lbkey.asc</a></p>
|
|
||||||
<p>Libreboot releases are signed using GPG.</p>
|
|
||||||
<div class="h"><h3 id="old-key">OLD KEY:</h3><a aria-hidden="true" href="#old-key">[link]</a></div>
|
|
||||||
<p>This key is for Libreboot 20160907, and releases older than
|
|
||||||
20160907:</p>
|
|
||||||
<p>Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8
|
|
||||||
C5B2</p>
|
|
||||||
<p>The GPG key can also be downloaded with this exported dump of the
|
|
||||||
pubkey: <a href="lbkeyold.asc">lbkeyold.asc</a>.</p>
|
|
||||||
<pre><code>sha512sum -c sha512sum.txt
|
|
||||||
gpg --verify sha512sum.txt.sig</code></pre>
|
|
||||||
<div class="h"><h2 id="git-repository">Git repository</h2><a aria-hidden="true" href="#git-repository">[link]</a></div>
|
|
||||||
<p>Links to regular release archives are listed on this page.</p>
|
|
||||||
<p>However, for the absolute most bleeding edge up-to-date version of
|
|
||||||
Libreboot, there is a Git repository that you can download from. Go
|
|
||||||
here:</p>
|
|
||||||
<p><a href="git.html">How to download Libreboot from Git</a></p>
|
|
||||||
<div class="h"><h2 id="https">HTTPS mirrors</h2><a aria-hidden="true" href="#https">[link]</a></div>
|
|
||||||
<p><strong>The latest release is Libreboot 20231021, under the
|
|
||||||
<code>testing</code> directory.</strong></p>
|
|
||||||
<p>These mirrors are recommended, since they use TLS (https://)
|
|
||||||
encryption.</p>
|
|
||||||
<p>You can download Libreboot from these mirrors:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="https://www.mirrorservice.org/sites/libreboot.org/release/"
|
|
||||||
class="uri">https://www.mirrorservice.org/sites/libreboot.org/release/</a>
|
|
||||||
(University of Kent, UK)</li>
|
|
||||||
<li><a href="https://mirrors.mit.edu/libreboot/"
|
|
||||||
class="uri">https://mirrors.mit.edu/libreboot/</a> (MIT university,
|
|
||||||
USA)</li>
|
|
||||||
<li><a href="https://mirror.math.princeton.edu/pub/libreboot/"
|
|
||||||
class="uri">https://mirror.math.princeton.edu/pub/libreboot/</a>
|
|
||||||
(Princeton university, USA)</li>
|
|
||||||
<li><a href="https://mirror.shapovalov.tech/libreboot/"
|
|
||||||
class="uri">https://mirror.shapovalov.tech/libreboot/</a>
|
|
||||||
(shapovalov.tech, Ukraine)</li>
|
|
||||||
<li><a href="https://mirror.koddos.net/libreboot/"
|
|
||||||
class="uri">https://mirror.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Netherlands)</li>
|
|
||||||
<li><a href="https://mirror-hk.koddos.net/libreboot/"
|
|
||||||
class="uri">https://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Hong Kong)</li>
|
|
||||||
<li><a href="https://mirror.cyberbits.eu/libreboot/"
|
|
||||||
class="uri">https://mirror.cyberbits.eu/libreboot/</a> (cyberbits.eu,
|
|
||||||
France)</li>
|
|
||||||
<li><a href="https://mirror.mangohost.net/libreboot/"
|
|
||||||
class="uri">https://mirror.mangohost.net/libreboot/</a> (mangohost.net,
|
|
||||||
Moldova)</li>
|
|
||||||
</ul>
|
|
||||||
<div class="h"><h2 id="rsync">RSYNC mirrors</h2><a aria-hidden="true" href="#rsync">[link]</a></div>
|
|
||||||
<p>The following rsync mirrors are available publicly:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="rsync://rsync.mirrorservice.org/libreboot.org/release/"
|
|
||||||
class="uri">rsync://rsync.mirrorservice.org/libreboot.org/release/</a>
|
|
||||||
(University of Kent, UK)</li>
|
|
||||||
<li><a href="rsync://mirror.math.princeton.edu/pub/libreboot/"
|
|
||||||
class="uri">rsync://mirror.math.princeton.edu/pub/libreboot/</a>
|
|
||||||
(Princeton university, USA)</li>
|
|
||||||
<li><a href="rsync://rsync.shapovalov.tech/libreboot/"
|
|
||||||
class="uri">rsync://rsync.shapovalov.tech/libreboot/</a>
|
|
||||||
(shapovalov.tech, Ukraine)</li>
|
|
||||||
<li><a href="rsync://ftp.linux.ro/libreboot/"
|
|
||||||
class="uri">rsync://ftp.linux.ro/libreboot/</a> (linux.ro, Romania)</li>
|
|
||||||
<li><a href="rsync://mirror.koddos.net/libreboot/"
|
|
||||||
class="uri">rsync://mirror.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Netherlands)</li>
|
|
||||||
<li><a href="rsync://mirror-hk.koddos.net/libreboot/"
|
|
||||||
class="uri">rsync://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Hong Kong)</li>
|
|
||||||
<li><a href="rsync://mirror.mangohost.net/libreboot/"
|
|
||||||
class="uri">rsync://mirror.mangohost.net/libreboot/</a> (mangohost.net,
|
|
||||||
Moldova)</li>
|
|
||||||
</ul>
|
|
||||||
<p>Are you running a mirror? Contact the libreboot project, and the link
|
|
||||||
will be added to this page!</p>
|
|
||||||
<p>You can make your rsync mirror available via your web server, and
|
|
||||||
also configure your <em>own</em> mirror to be accessible via rsync.
|
|
||||||
There are many resources online that show you how to set up an rsync
|
|
||||||
server.</p>
|
|
||||||
<p>How to create your own rsync mirror:</p>
|
|
||||||
<p>Useful for mirroring Libreboot’s entire set of release archives. You
|
|
||||||
can put an rsync command into crontab and pull the files into a
|
|
||||||
directory on your web server.</p>
|
|
||||||
<p>If you are going to mirror the entire set, it is recommended that you
|
|
||||||
allocate at least 25GiB. Libreboot’s rsync is currently about 12GiB, so
|
|
||||||
allocating 25GiB will afford you plenty of space for the future. At
|
|
||||||
minimum, you should ensure that at least 15-20GiB of space is available,
|
|
||||||
for your Libreboot mirror.</p>
|
|
||||||
<p><em>It is highly recommended that you use the libreboot.org
|
|
||||||
mirror</em>, if you wish to host an official mirror. Otherwise, if you
|
|
||||||
simply want to create your own local mirror, you should use one of the
|
|
||||||
other mirrors, which sync from libreboot.org.</p>
|
|
||||||
<p>Before you create the mirror, make a directory on your web server.
|
|
||||||
For example:</p>
|
|
||||||
<pre><code>mkdir /var/www/html/libreboot/</code></pre>
|
|
||||||
<p>Now you can run rsync, for instance:</p>
|
|
||||||
<pre><code>rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
|
|
||||||
<p>You might put this in an hourly crontab. For example:</p>
|
|
||||||
<pre><code>crontab -e</code></pre>
|
|
||||||
<p>Then in crontab, add this line and save/exit (hourly crontab):</p>
|
|
||||||
<pre><code>0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
|
|
||||||
<p><strong>It’s extremely important to have the final forward slash (/)
|
|
||||||
at the end of each path, in the above rsync command. Otherwise, rsync
|
|
||||||
will behave very strangely.</strong></p>
|
|
||||||
<p><strong>NOTE: <code>rsync.libreboot.org</code> is not directly
|
|
||||||
accessible by the public, except those whose IPs are whitelisted. For
|
|
||||||
bandwidth reasons, the firewall running on libreboot.org blocks incoming
|
|
||||||
rsync requests, except by specific IPs.</strong></p>
|
|
||||||
<p><strong>If you wish to run an rsync mirror, sync from one of the
|
|
||||||
third party mirrors above and set up your mirror. You can then contact
|
|
||||||
Leah Rowe, to have your IP addresses whitelisted for rsync usage - if
|
|
||||||
the IP addresses match DNS A/AAAA records for your rsync host, this can
|
|
||||||
be used. A script runs in an hourly crontab on libreboot.org, that
|
|
||||||
fetches the A/AAAA records of whitelisted rsync mirrors, automatically
|
|
||||||
adding rules permitting them to get through the firewall.</strong></p>
|
|
||||||
<p>If you wish to regularly keep your rsync mirror updated, you can add
|
|
||||||
it to a crontab. This page tells you how to use crontab: <a
|
|
||||||
href="https://man7.org/linux/man-pages/man5/crontab.5.html"
|
|
||||||
class="uri">https://man7.org/linux/man-pages/man5/crontab.5.html</a></p>
|
|
||||||
<div class="h"><h2 id="http">HTTP mirrors</h2><a aria-hidden="true" href="#http">[link]</a></div>
|
|
||||||
<p><strong>The latest release is Libreboot 20231021, under the
|
|
||||||
<code>testing</code> directory.</strong></p>
|
|
||||||
<p>WARNING: these mirrors are non-HTTPS which means that they are
|
|
||||||
unencrypted. Your traffic could be subject to interference by
|
|
||||||
adversaries. Make especially sure to check the GPG signatures, assuming
|
|
||||||
that you have the right key. Of course, you should do this anyway, even
|
|
||||||
if using HTTPS.</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="http://mirror.linux.ro/libreboot/"
|
|
||||||
class="uri">http://mirror.linux.ro/libreboot/</a> (linux.ro,
|
|
||||||
Romania)</li>
|
|
||||||
<li><a href="http://mirror.helium.in-berlin.de/libreboot/"
|
|
||||||
class="uri">http://mirror.helium.in-berlin.de/libreboot/</a>
|
|
||||||
(in-berlin.de, Germany)</li>
|
|
||||||
</ul>
|
|
||||||
<div class="h"><h2 id="ftp">FTP mirrors</h2><a aria-hidden="true" href="#ftp">[link]</a></div>
|
|
||||||
<p><strong>The latest release is Libreboot 20231021, under the
|
|
||||||
<code>testing</code> directory.</strong></p>
|
|
||||||
<p>WARNING: FTP is also unencrypted, like HTTP. The same risks are
|
|
||||||
present.</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="ftp://ftp.mirrorservice.org/sites/libreboot.org/release/"
|
|
||||||
class="uri">ftp://ftp.mirrorservice.org/sites/libreboot.org/release/</a>
|
|
||||||
(University of Kent, UK)</li>
|
|
||||||
<li><a href="ftp://ftp.linux.ro/libreboot/"
|
|
||||||
class="uri">ftp://ftp.linux.ro/libreboot/</a> (linux.ro, Romania)</li>
|
|
||||||
</ul>
|
|
||||||
<div class="h"><h2 id="statically-linked">Statically linked</h2><a aria-hidden="true" href="#statically-linked">[link]</a></div>
|
|
||||||
<p>Libreboot includes statically linked executables in some releases,
|
|
||||||
built from the available source code. Those executables have certain
|
|
||||||
libraries built into them, so that the executables will work on many
|
|
||||||
Linux distros.</p>
|
|
||||||
<p>To comply with GPL v2, source ISOs are supplied by the Libreboot
|
|
||||||
project. You can find these source ISOs in the <code>ccsource</code>
|
|
||||||
directory on the <code>rsync</code> mirrors.</p>
|
|
||||||
<p>Libreboot releases past version 20160907 do not distribute statically
|
|
||||||
linked binaries. Instead, these releases are source-only, besides
|
|
||||||
pre-compiled ROM images for which the regular Libreboot source code
|
|
||||||
archives suffice. These newer releases instead automate the installation
|
|
||||||
of build dependencies, with instructions in the documentation for
|
|
||||||
building various utilities from source.</p>
|
|
||||||
<p>These executables are utilities such as <code>flashrom</code>.</p>
|
|
||||||
<div id="footer">
|
|
||||||
<hr />
|
|
||||||
<ul>
|
|
||||||
<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li>
|
|
||||||
<li><a href="/git.html">Edit this page</a></li>
|
|
||||||
<li><a href="/who.html">Who develops Libreboot?</a></li>
|
|
||||||
<li><a href="/license.html">License</a></li>
|
|
||||||
<li><a href="/template-license.html">Template</a></li>
|
|
||||||
<li><a href="/logo-license.html">Logo</a></li>
|
|
||||||
<li><a href="/contrib.html">Authors</a></li>
|
|
||||||
</ul>
|
|
||||||
<hr />
|
|
||||||
</div>
|
|
||||||
<p>Markdown file for this page: <a
|
|
||||||
href="https://libreboot.org/download.md"
|
|
||||||
class="uri">https://libreboot.org/download.md</a></p>
|
|
||||||
<p><a href="/sitemap.html">Site map</a></p>
|
|
||||||
<p>This HTML page was generated by the <a
|
|
||||||
href="https://untitled.vimuser.org/">untitled static site
|
|
||||||
generator</a>.</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
|
@ -11,51 +11,61 @@ Git repositories. The page on [/docs/maintain/](docs/maintain/) describes how
|
||||||
Libreboot is put together, and how to maintain it. If you wish to build
|
Libreboot is put together, and how to maintain it. If you wish to build
|
||||||
Libreboot from source, [read this page](docs/build/).
|
Libreboot from source, [read this page](docs/build/).
|
||||||
|
|
||||||
READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
|
Buy Libreboot pre-installed
|
||||||
====================================================================
|
-----------------
|
||||||
|
|
||||||
**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
the release ROMs of Libreboot are MISSING certain files, that you must insert
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
yourself. FAILURE to adhere to this warning may result in you bricking your
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
machine (rendering it unbootable), if you were to flash the release ROMs without
|
|
||||||
modifying them in any way. For more information, please read:**
|
|
||||||
|
|
||||||
**[Insert vendor files on Sandybridge/Ivybridge/Haswell](docs/install/ivy_has_common.md)**
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
NOTE: This warning does not apply to ROMs that you compiled yourself, using
|
Safety warning
|
||||||
lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
|
--------------
|
||||||
in release ROMs. The link above says how to re-add them. When building ROM images
|
|
||||||
yourself, from source, Libreboot's build system automatically handles it. See:
|
|
||||||
[Libreboot build instructions](docs/build/)
|
|
||||||
|
|
||||||
This isn't required on *all* Libreboot-supported boards, but if in doubt, follow
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
these instructions anyway. If you run the vendor scripts on a board that doesn't
|
LIBREBOOT](news/safety.md).**
|
||||||
need blobs, nothing will happen.
|
|
||||||
|
|
||||||
GPG signing key
|
GPG signing key
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
**The latest release is Libreboot 20231021, under the `testing` directory.**
|
**The latest release is Libreboot 20240612, under the `stable` directory.**
|
||||||
|
|
||||||
### NEW KEY
|
### NEW KEY
|
||||||
|
|
||||||
Full key fingerprint: `98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856`
|
Full key fingerprint: `8BB1 F7D2 8CF7 696D BF4F 7192 5C65 4067 D383 B1FF`
|
||||||
|
|
||||||
This key is for Libreboot releases *after* the 20160907 release.
|
This key is for Libreboot releases *after* the 20240126 release. It applies to
|
||||||
|
all Libreboot releases from the year 2024, and it will expire (unless revoked
|
||||||
|
early) on 26 December 2028.
|
||||||
|
|
||||||
Download the key here: [lbkey.asc](lbkey.asc)
|
Download the key here: [lbkey.asc](lbkey.asc)
|
||||||
|
|
||||||
Libreboot releases are signed using GPG.
|
Libreboot releases are signed using GPG.
|
||||||
|
|
||||||
### OLD KEY:
|
### OLD KEY
|
||||||
|
|
||||||
|
Full key fingerprint: `98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856`
|
||||||
|
|
||||||
|
This key is for Libreboot releases *after* the 20160907 release, and up
|
||||||
|
to the Libreboot 20240126 release. This key *expired* during December 2023,
|
||||||
|
so you should use the *newer* key (see above) for the releases after
|
||||||
|
Libreboot 20240126.
|
||||||
|
|
||||||
|
Download the key here: [lbkey.asc](lbkeyold.asc)
|
||||||
|
|
||||||
|
Libreboot releases are signed using GPG.
|
||||||
|
|
||||||
|
### OLD OLD KEY:
|
||||||
|
|
||||||
This key is for Libreboot 20160907, and releases older than 20160907:
|
This key is for Libreboot 20160907, and releases older than 20160907:
|
||||||
|
|
||||||
Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 C5B2
|
Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 C5B2
|
||||||
|
|
||||||
The GPG key can also be downloaded with this exported dump of the
|
The GPG key can also be downloaded with this exported dump of the
|
||||||
pubkey: [lbkeyold.asc](lbkeyold.asc).
|
pubkey: [lbkeyold.asc](lbkeyoldold.asc).
|
||||||
|
|
||||||
sha512sum -c sha512sum.txt
|
sha512sum -c sha512sum.txt
|
||||||
gpg --verify sha512sum.txt.sig
|
gpg --verify sha512sum.txt.sig
|
||||||
|
@ -73,22 +83,21 @@ there is a Git repository that you can download from. Go here:
|
||||||
HTTPS mirrors {#https}
|
HTTPS mirrors {#https}
|
||||||
-------------
|
-------------
|
||||||
|
|
||||||
**The latest release is Libreboot 20231021, under the `testing` directory.**
|
**The latest release is Libreboot 20240612, under the `stable` directory.**
|
||||||
|
|
||||||
These mirrors are recommended, since they use TLS (https://) encryption.
|
These mirrors are recommended, since they use TLS (https://) encryption.
|
||||||
|
|
||||||
You can download Libreboot from these mirrors:
|
You can download Libreboot from these mirrors:
|
||||||
|
|
||||||
|
* <https://mirror.math.princeton.edu/pub/libreboot/> (Princeton
|
||||||
|
university, USA)
|
||||||
|
* <https://mirror.shapovalov.website/libreboot/> (shapovalov.website, Ukraine)
|
||||||
* <https://www.mirrorservice.org/sites/libreboot.org/release/> (University
|
* <https://www.mirrorservice.org/sites/libreboot.org/release/> (University
|
||||||
of Kent, UK)
|
of Kent, UK)
|
||||||
* <https://mirrors.mit.edu/libreboot/> (MIT university, USA)
|
* <https://mirrors.mit.edu/libreboot/> (MIT university, USA)
|
||||||
* <https://mirror.math.princeton.edu/pub/libreboot/> (Princeton
|
|
||||||
university, USA)
|
|
||||||
* <https://mirror.shapovalov.tech/libreboot/> (shapovalov.tech, Ukraine)
|
|
||||||
* <https://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
|
* <https://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
|
||||||
* <https://mirror-hk.koddos.net/libreboot/> (koddos.net, Hong Kong)
|
* <https://mirror-hk.koddos.net/libreboot/> (koddos.net, Hong Kong)
|
||||||
* <https://mirror.cyberbits.eu/libreboot/> (cyberbits.eu, France)
|
* <https://mirror.cyberbits.eu/libreboot/> (cyberbits.eu, France)
|
||||||
* <https://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
|
|
||||||
|
|
||||||
RSYNC mirrors {#rsync}
|
RSYNC mirrors {#rsync}
|
||||||
-------------
|
-------------
|
||||||
|
@ -98,11 +107,10 @@ The following rsync mirrors are available publicly:
|
||||||
* <rsync://rsync.mirrorservice.org/libreboot.org/release/> (University of Kent,
|
* <rsync://rsync.mirrorservice.org/libreboot.org/release/> (University of Kent,
|
||||||
UK)
|
UK)
|
||||||
* <rsync://mirror.math.princeton.edu/pub/libreboot/> (Princeton university, USA)
|
* <rsync://mirror.math.princeton.edu/pub/libreboot/> (Princeton university, USA)
|
||||||
* <rsync://rsync.shapovalov.tech/libreboot/> (shapovalov.tech, Ukraine)
|
* <rsync://rsync.shapovalov.website/libreboot/> (shapovalov.website, Ukraine)
|
||||||
* <rsync://ftp.linux.ro/libreboot/> (linux.ro, Romania)
|
* <rsync://ftp.linux.ro/libreboot/> (linux.ro, Romania)
|
||||||
* <rsync://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
|
* <rsync://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
|
||||||
* <rsync://mirror-hk.koddos.net/libreboot/> (koddos.net, Hong Kong)
|
* <rsync://mirror-hk.koddos.net/libreboot/> (koddos.net, Hong Kong)
|
||||||
* <rsync://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
|
|
||||||
|
|
||||||
Are you running a mirror? Contact the libreboot project, and the link will be
|
Are you running a mirror? Contact the libreboot project, and the link will be
|
||||||
added to this page!
|
added to this page!
|
||||||
|
@ -166,7 +174,7 @@ crontab. This page tells you how to use crontab:
|
||||||
HTTP mirrors {#http}
|
HTTP mirrors {#http}
|
||||||
------------
|
------------
|
||||||
|
|
||||||
**The latest release is Libreboot 20231021, under the `testing` directory.**
|
**The latest release is Libreboot 20240612, under the `stable` directory.**
|
||||||
|
|
||||||
WARNING: these mirrors are non-HTTPS which means that they are
|
WARNING: these mirrors are non-HTTPS which means that they are
|
||||||
unencrypted. Your traffic could be subject to interference by
|
unencrypted. Your traffic could be subject to interference by
|
||||||
|
@ -180,7 +188,7 @@ if using HTTPS.
|
||||||
FTP mirrors {#ftp}
|
FTP mirrors {#ftp}
|
||||||
-----------
|
-----------
|
||||||
|
|
||||||
**The latest release is Libreboot 20231021, under the `testing` directory.**
|
**The latest release is Libreboot 20240612, under the `stable` directory.**
|
||||||
|
|
||||||
WARNING: FTP is also unencrypted, like HTTP. The same risks are present.
|
WARNING: FTP is also unencrypted, like HTTP. The same risks are present.
|
||||||
|
|
||||||
|
@ -205,4 +213,4 @@ images for which the regular Libreboot source code archives suffice. These newer
|
||||||
releases instead automate the installation of build dependencies, with instructions
|
releases instead automate the installation of build dependencies, with instructions
|
||||||
in the documentation for building various utilities from source.
|
in the documentation for building various utilities from source.
|
||||||
|
|
||||||
These executables are utilities such as `flashrom`.
|
These executables are utilities such as `flashprog`.
|
||||||
|
|
|
@ -1 +0,0 @@
|
||||||
1697840199
|
|
|
@ -1,299 +0,0 @@
|
||||||
<!DOCTYPE html>
|
|
||||||
<html lang="uk" dir="ltr">
|
|
||||||
<head>
|
|
||||||
<meta charset="utf-8">
|
|
||||||
<meta name="generator" content="pandoc">
|
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
|
||||||
|
|
||||||
<!-- anti-social media tags -->
|
|
||||||
<meta property="og:title" content="Libreboot – Завантаження">
|
|
||||||
<meta property="og:type" content="article" />
|
|
||||||
<meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
|
|
||||||
<meta property="og:url" content="https://libreboot.org/download.uk.html">
|
|
||||||
<meta name="twitter:card" content="summary_large_image">
|
|
||||||
<meta property="og:description" content="Libreboot – Завантаження">
|
|
||||||
<meta property="og:site_name" content="Libreboot – Завантаження">
|
|
||||||
<meta name="twitter:image:alt" content="Libreboot – Завантаження">
|
|
||||||
|
|
||||||
<title>Libreboot – Завантаження</title>
|
|
||||||
<link rel="stylesheet" href="/global.css">
|
|
||||||
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
|
|
||||||
</head>
|
|
||||||
<body>
|
|
||||||
<div class="page">
|
|
||||||
<header>
|
|
||||||
<div class="title">
|
|
||||||
<p class="title-logo">
|
|
||||||
<img loading="lazy" class="title-logo" alt="Логотип Libreboot" src="/favicon.ico" />
|
|
||||||
</p>
|
|
||||||
<h1 class="title">Завантаження</h1>
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li><a href="/index.uk.html">Домашня</a></li>
|
|
||||||
<li><a href="/faq.html">FAQ</a></li>
|
|
||||||
<li><strong><a href="/freedom-status.html">Статус свободи</a></strong></li>
|
|
||||||
<li><strong><a href="/download.uk.html">Завантаження</a></strong></li>
|
|
||||||
<li><a href="/docs/install/">Встановлення</a></li>
|
|
||||||
<li><a href="/docs/index.uk.html">Документація</a></li>
|
|
||||||
<li><a href="/news/">Новини</a></li>
|
|
||||||
<li><a href="https://codeberg.org/libreboot/lbmk/issues">Помилки</a></li>
|
|
||||||
<li><a href="/git.uk.html">Відправити виправлення</a></li>
|
|
||||||
<li><strong><a href="https://www.patreon.com/libreleah">Пожертвувати</a></strong></li>
|
|
||||||
<li><a href="/contact.uk.html">Зв'язок</a></li>
|
|
||||||
<li><strong><a href="https://minifree.org/">Придбати передвстановленим</a></strong></li>
|
|
||||||
</ul>
|
|
||||||
<hr/>
|
|
||||||
</header>
|
|
||||||
<nav id="TOC">
|
|
||||||
<h1>Навігація цією сторінкою:</h1>
|
|
||||||
<ul>
|
|
||||||
<li><a
|
|
||||||
href="#read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
|
|
||||||
THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</a>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#код-підпису-gpg">Код підпису GPG</a>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#новий-ключ">НОВИЙ КЛЮЧ</a></li>
|
|
||||||
<li><a href="#старий-ключ">СТАРИЙ КЛЮЧ:</a></li>
|
|
||||||
</ul></li>
|
|
||||||
<li><a href="#репозиторій-git">Репозиторій Git</a></li>
|
|
||||||
<li><a href="#https">Дзеркала HTTPS</a></li>
|
|
||||||
<li><a href="#rsync">Дзеркала RSYNC</a></li>
|
|
||||||
<li><a href="#http">Дзеркала HTTP</a></li>
|
|
||||||
<li><a href="#ftp">Дзеркала FTP</a></li>
|
|
||||||
<li><a href="#статично-звязані">Статично зв’язані</a></li>
|
|
||||||
</ul></li>
|
|
||||||
</ul>
|
|
||||||
</nav>
|
|
||||||
<div class="pagetext">
|
|
||||||
<p><a href="download.html">English</a> | <a
|
|
||||||
href="download.uk.html">українська</a></p>
|
|
||||||
<p><a href="./">попередній індекс</a></p>
|
|
||||||
<p>Нові випуски оголошуються в <a href="news/">основній секції
|
|
||||||
новин</a>.</p>
|
|
||||||
<p>Якщо ви більше зацікавлені в розробці libreboot, пройдіть на <a
|
|
||||||
href="../git.html">сторінку розробки libreboot</a>, яка також включає
|
|
||||||
посилання на репозиторії Git. Сторінка на <a
|
|
||||||
href="docs/maintain/">/docs/maintain/</a> описує те, як Libreboot
|
|
||||||
складається разом, і як підтримувати його. Якщо ви бажаєте зібрати
|
|
||||||
Libreboot із джерельного кода, <a href="docs/build/">прочитайте цю
|
|
||||||
сторінку</a>.</p>
|
|
||||||
<h1
|
|
||||||
id="read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
|
|
||||||
THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</h1>
|
|
||||||
<p><strong>On newer Intel platforms that require Intel ME and/or MRC
|
|
||||||
firmware, such as ThinkPad X230 or T440p, and/or HP laptops that require
|
|
||||||
KBC1126 EC firmware, the release ROMs of Libreboot are MISSING certain
|
|
||||||
files, that you must insert yourself. FAILURE to adhere to this warning
|
|
||||||
may result in you bricking your machine (rendering it unbootable), if
|
|
||||||
you were to flash the release ROMs without modifying them in any way.
|
|
||||||
For more information, please read:</strong></p>
|
|
||||||
<p><strong><a href="docs/install/ivy_has_common.html">Insert vendor
|
|
||||||
files on Sandybridge/Ivybridge/Haswell</a></strong></p>
|
|
||||||
<p>NOTE: This warning does not apply to ROMs that you compiled yourself,
|
|
||||||
using lbmk. It only applies to release ROMs, because ME/MRC/EC firmware
|
|
||||||
is <em>deleted</em> in release ROMs. The link above says how to re-add
|
|
||||||
them. When building ROM images yourself, from source, Libreboot’s build
|
|
||||||
system automatically handles it. See: <a href="docs/build/">Libreboot
|
|
||||||
build instructions</a></p>
|
|
||||||
<p>This isn’t required on <em>all</em> Libreboot-supported boards, but
|
|
||||||
if in doubt, follow these instructions anyway. If you run the vendor
|
|
||||||
scripts on a board that doesn’t need vendor files, nothing will
|
|
||||||
happen.</p>
|
|
||||||
<div class="h"><h2 id="код-підпису-gpg">Код підпису GPG</h2><a aria-hidden="true" href="#код-підпису-gpg">[link]</a></div>
|
|
||||||
<p><strong>Останнім випуском є Libreboot 20231021, в директорії
|
|
||||||
<code>testing</code>.</strong></p>
|
|
||||||
<div class="h"><h3 id="новий-ключ">НОВИЙ КЛЮЧ</h3><a aria-hidden="true" href="#новий-ключ">[link]</a></div>
|
|
||||||
<p>Повний відбиток ключа:
|
|
||||||
<code>98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856</code></p>
|
|
||||||
<p>Вищезазначений ключ для Libreboot 20231021, та наступних
|
|
||||||
випусків.</p>
|
|
||||||
<p>Завантажте ключ тут: <a href="lbkey.asc">lbkey.asc</a></p>
|
|
||||||
<p>Випуски Libreboot підписані з використанням GPG.</p>
|
|
||||||
<div class="h"><h3 id="старий-ключ">СТАРИЙ КЛЮЧ:</h3><a aria-hidden="true" href="#старий-ключ">[link]</a></div>
|
|
||||||
<p>Цей ключ для Libreboot 20160907 та всіх старіших випусків:</p>
|
|
||||||
<p>Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8
|
|
||||||
C5B2</p>
|
|
||||||
<p>Ключ GPG також може бути завантажений разом із цим експортованим
|
|
||||||
дампом публічного ключа: <a href="lbkeyold.asc">lbkeyold.asc</a>.</p>
|
|
||||||
<pre><code>sha512sum -c sha512sum.txt
|
|
||||||
gpg --verify sha512sum.txt.sig</code></pre>
|
|
||||||
<div class="h"><h2 id="репозиторій-git">Репозиторій Git</h2><a aria-hidden="true" href="#репозиторій-git">[link]</a></div>
|
|
||||||
<p>Посилання на архіви регулярних випусків зазначені на цій
|
|
||||||
сторінці.</p>
|
|
||||||
<p>Однак, для абсолютно найновішої версії Libreboot, існує репозиторії
|
|
||||||
Git, з якого можна завантажити. Ідіть сюди:</p>
|
|
||||||
<p><a href="git.html">Як завантажити Libreboot через Git</a></p>
|
|
||||||
<div class="h"><h2 id="https">Дзеркала HTTPS</h2><a aria-hidden="true" href="#https">[link]</a></div>
|
|
||||||
<p><strong>Останнім випуском є Libreboot 20231021, в директорії
|
|
||||||
<code>testing</code>.</strong></p>
|
|
||||||
<p>Дані дзеркала є рекомендованими, оскільки використовують TLS
|
|
||||||
(https://) шифрування.</p>
|
|
||||||
<p>Ви можете завантажити Libreboot через дані дзеркала:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="https://www.mirrorservice.org/sites/libreboot.org/release/"
|
|
||||||
class="uri">https://www.mirrorservice.org/sites/libreboot.org/release/</a>
|
|
||||||
(Кентський університет, Великобританія)</li>
|
|
||||||
<li><a href="https://mirrors.mit.edu/libreboot/"
|
|
||||||
class="uri">https://mirrors.mit.edu/libreboot/</a> (Університет МТІ,
|
|
||||||
США)</li>
|
|
||||||
<li><a href="https://mirror.math.princeton.edu/pub/libreboot/"
|
|
||||||
class="uri">https://mirror.math.princeton.edu/pub/libreboot/</a>
|
|
||||||
(Прінстонський університет, США)</li>
|
|
||||||
<li><a href="https://mirror.shapovalov.tech/libreboot/"
|
|
||||||
class="uri">https://mirror.shapovalov.tech/libreboot/</a>
|
|
||||||
(shapovalov.tech, Україна)</li>
|
|
||||||
<li><a href="https://mirror.koddos.net/libreboot/"
|
|
||||||
class="uri">https://mirror.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Нідерланди)</li>
|
|
||||||
<li><a href="https://mirror-hk.koddos.net/libreboot/"
|
|
||||||
class="uri">https://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Гонконг)</li>
|
|
||||||
<li><a href="https://mirror.cyberbits.eu/libreboot/"
|
|
||||||
class="uri">https://mirror.cyberbits.eu/libreboot/</a> (cyberbits.eu,
|
|
||||||
Франція)</li>
|
|
||||||
<li><a href="https://mirror.mangohost.net/libreboot/"
|
|
||||||
class="uri">https://mirror.mangohost.net/libreboot/</a> (mangohost.net,
|
|
||||||
Moldova)</li>
|
|
||||||
</ul>
|
|
||||||
<div class="h"><h2 id="rsync">Дзеркала RSYNC</h2><a aria-hidden="true" href="#rsync">[link]</a></div>
|
|
||||||
<p>Наступні дзеркала rsync доступні публічно:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="rsync://rsync.mirrorservice.org/libreboot.org/release/"
|
|
||||||
class="uri">rsync://rsync.mirrorservice.org/libreboot.org/release/</a>
|
|
||||||
(Кентський університет, Великобританія)</li>
|
|
||||||
<li><a href="rsync://mirror.math.princeton.edu/pub/libreboot/"
|
|
||||||
class="uri">rsync://mirror.math.princeton.edu/pub/libreboot/</a>
|
|
||||||
(Прінстонський університет, США)</li>
|
|
||||||
<li><a href="rsync://rsync.shapovalov.tech/libreboot/"
|
|
||||||
class="uri">rsync://rsync.shapovalov.tech/libreboot/</a>
|
|
||||||
(shapovalov.tech, Україна)</li>
|
|
||||||
<li><a href="rsync://ftp.linux.ro/libreboot/"
|
|
||||||
class="uri">rsync://ftp.linux.ro/libreboot/</a> (linux.ro, Румунія)</li>
|
|
||||||
<li><a href="rsync://mirror.koddos.net/libreboot/"
|
|
||||||
class="uri">rsync://mirror.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Нідерланди)</li>
|
|
||||||
<li><a href="rsync://mirror-hk.koddos.net/libreboot/"
|
|
||||||
class="uri">rsync://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
|
|
||||||
Гонконг)</li>
|
|
||||||
<li><a href="rsync://mirror.mangohost.net/libreboot/"
|
|
||||||
class="uri">rsync://mirror.mangohost.net/libreboot/</a> (mangohost.net,
|
|
||||||
Moldova)</li>
|
|
||||||
</ul>
|
|
||||||
<p>Ви підтримуєте роботу дзеркала? Зв’яжіться з проектом libreboot, і
|
|
||||||
посилання буде додано до цієї сторінки!</p>
|
|
||||||
<p>Ви можете зробити своє дзеркало rsync доступним через свій
|
|
||||||
веб-сервер, а також налаштувати ваше <em>власне</em> дзеркало бути
|
|
||||||
доступним через rsync. Є багато онлайн-ресурсів, які показують вам те,
|
|
||||||
як налаштувати сервер rsync.</p>
|
|
||||||
<p>Як створити ваше власне дзеркало rsync:</p>
|
|
||||||
<p>Корисно для відзеркалювання повного набору архівів випусків
|
|
||||||
Libreboot. Ви можете розмістити команду rsync в crontab та витягувать
|
|
||||||
файли в директорію на вашому веб-сервері.</p>
|
|
||||||
<p>Якщо ви збираєтесь відзеркалювати повний набір, рекомендовано, щоб
|
|
||||||
вами було виділено хоча би 25 ГБ. Rsync Libreboot наразі приблизно 12
|
|
||||||
ГБ, таким чином виділення 25 ГБ забезпечить вам багато місця на
|
|
||||||
майбутнє. Мінімально, ви маєте переконатись, що хоча би 15-20 ГБ
|
|
||||||
простору доступно, для вашого дзеркала Libreboot.</p>
|
|
||||||
<p><em>Настійно рекомендується, щоб ви використовували дзеркало
|
|
||||||
libreboot.org</em>, якщо бажаєте розміщувати офіційне дзеркало. В іншому
|
|
||||||
випадку, якщо ви просто бажаєте створити своє власне локальне дзеркало,
|
|
||||||
вам варто використовувати одне з інших дзеркал, яке синхронізується з
|
|
||||||
libreboot.org.</p>
|
|
||||||
<p>Перед створенням дзеркала, зробіть директорію на вашому веб-сервері.
|
|
||||||
Для прикладу:</p>
|
|
||||||
<pre><code>mkdir /var/www/html/libreboot/</code></pre>
|
|
||||||
<p>Тепер ви можете виконувати rsync, для прикладу:</p>
|
|
||||||
<pre><code>rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
|
|
||||||
<p>Ви могли би розмістить це в щогодинний crontab. Для прикладу:</p>
|
|
||||||
<pre><code>crontab -e</code></pre>
|
|
||||||
<p>Потім в crontab, додайте цей рядок і збережіться/вийдіть (щогодинний
|
|
||||||
crontab):</p>
|
|
||||||
<pre><code>0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
|
|
||||||
<p><strong>Це надзвичайно важливо, щоб мати в кінці косу лінію (/) в
|
|
||||||
кінці кожного шляху, в вищезазначеній команді rsync. В інакшому випадку,
|
|
||||||
rsync буде поводитись дуже дивно.</strong></p>
|
|
||||||
<p><strong>ПОМІТКА: <code>rsync.libreboot.org</code> не є напряму
|
|
||||||
доступним для громадськості, окрім тих, чиї IP у білому списку. Через
|
|
||||||
пропускну здатність, Брандмауер, який працює на libreboot.org, блокує
|
|
||||||
вхідні запити rsync, окрім окремих IP.</strong></p>
|
|
||||||
<p><strong>Якщо ви бажаєте запустити дзеркало rsync, синхронізуйте з
|
|
||||||
одного з дзеркал третіх сторін вище і встановіть своє дзеркало. Ви
|
|
||||||
можете потім зв’язатись з Лією Роу, щоб мати ваші адреси IP внесеним в
|
|
||||||
білий список для використання rsync - якщо адреси IP відповідають DNS
|
|
||||||
A/AAAA записам для вашого хоста rsync, це може бути використано.
|
|
||||||
Сценарій виконується в щогодинному crontab на libreboot.org, який
|
|
||||||
отримує A/AAAA записи внесених в білий список дзеркал rsync, автоматично
|
|
||||||
додаючи правила, які дозволяють їм проходити через
|
|
||||||
брандмауер.</strong></p>
|
|
||||||
<p>Якщо ви бажаєте регулярно тримати свої дзеркала rsync оновленими, ви
|
|
||||||
можете додати це до crontab. Ця сторінка розповідає вам, як
|
|
||||||
використовувати crontab: <a
|
|
||||||
href="https://man7.org/linux/man-pages/man5/crontab.5.html"
|
|
||||||
class="uri">https://man7.org/linux/man-pages/man5/crontab.5.html</a></p>
|
|
||||||
<div class="h"><h2 id="http">Дзеркала HTTP</h2><a aria-hidden="true" href="#http">[link]</a></div>
|
|
||||||
<p><strong>Останнім випуском є Libreboot 20231021, під директорією
|
|
||||||
<code>testing</code>.</strong></p>
|
|
||||||
<p>УВАГА: ці дзеркала є не-HTTPS, що означає, що вони незашифровані. Ваш
|
|
||||||
трафік може бути об’єктом втручання противників. Особливо ретельно
|
|
||||||
переконайтесь, щоб перевірити підписи GPG, передбачаючи, що ви маєте
|
|
||||||
правильний ключ. Звісно, вам варто зробити це в будь-якому випадку,
|
|
||||||
навіть при використанні HTTPS.</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="http://mirror.linux.ro/libreboot/"
|
|
||||||
class="uri">http://mirror.linux.ro/libreboot/</a> (linux.ro,
|
|
||||||
Румунія)</li>
|
|
||||||
<li><a href="http://mirror.helium.in-berlin.de/libreboot/"
|
|
||||||
class="uri">http://mirror.helium.in-berlin.de/libreboot/</a>
|
|
||||||
(in-berlin.de, Німеччина)</li>
|
|
||||||
</ul>
|
|
||||||
<div class="h"><h2 id="ftp">Дзеркала FTP</h2><a aria-hidden="true" href="#ftp">[link]</a></div>
|
|
||||||
<p><strong>Останнім випуском є Libreboot 20231021, під директорією
|
|
||||||
<code>testing</code>.</strong></p>
|
|
||||||
<p>УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики
|
|
||||||
присутні.</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="ftp://ftp.mirrorservice.org/sites/libreboot.org/release/"
|
|
||||||
class="uri">ftp://ftp.mirrorservice.org/sites/libreboot.org/release/</a>
|
|
||||||
(Кентський університет, Великобританія)</li>
|
|
||||||
<li><a href="ftp://ftp.linux.ro/libreboot/"
|
|
||||||
class="uri">ftp://ftp.linux.ro/libreboot/</a> (linux.ro, Румунія)</li>
|
|
||||||
</ul>
|
|
||||||
<div class="h"><h2 id="статично-звязані">Статично зв’язані</h2><a aria-hidden="true" href="#статично-звязані">[link]</a></div>
|
|
||||||
<p>Libreboot включає статично зв’язані виконувані файли в деяких
|
|
||||||
випусках, побудовані з доступного джерельного кода. Ці виконувані файли
|
|
||||||
мають деякі бібліотеки, вбудовані в них, так щоб виконувані файли
|
|
||||||
працювали на багатьох дистрибутивах Linux.</p>
|
|
||||||
<p>Для дотримання GPL v2, джерельні ISO постачаються проектом Libreboot.
|
|
||||||
Ви можете знайти ці джерельні ISO в директорії <code>ccsource</code> на
|
|
||||||
дзеркалах <code>rsync</code>.</p>
|
|
||||||
<p>Попередні випуски Libreboot 20160907 не розповсюджують статично
|
|
||||||
зв’язані двійкові файли. Натомість ці випуски є лише вихідними кодами,
|
|
||||||
окрім попередньо скомпільованих образів ПЗП, для яких достатньо
|
|
||||||
звичайних архівів джерельного коду Libreboot. Ці новіші випуски
|
|
||||||
натомість автоматизують встановлення залежностей побудови, з інструкцієї
|
|
||||||
в документації для побудови різних утиліт з джерельного коду.</p>
|
|
||||||
<p>Ці виконувані файли є утилітами, подібними <code>flashrom</code>.</p>
|
|
||||||
<div id="footer">
|
|
||||||
<hr />
|
|
||||||
<ul>
|
|
||||||
<li><a href="/news/policy.html">Політика бінарних блобів</a></li>
|
|
||||||
<li><a href="/git.html">Редагувати цю сторінку</a></li>
|
|
||||||
<li><a href="/who.uk.html">Хто розробляє Libreboot?</a></li>
|
|
||||||
<li><a href="/license.html">Ліцензія</a></li>
|
|
||||||
<li><a href="/template-license.uk.html">Шаблон</a></li>
|
|
||||||
<li><a href="/logo-license.uk.html">Логотип</a></li>
|
|
||||||
<li><a href="/contrib.uk.html">Автори</a></li>
|
|
||||||
</ul>
|
|
||||||
<hr />
|
|
||||||
</div>
|
|
||||||
<p>Markdown: <a href="https://libreboot.org/download.uk.md"
|
|
||||||
class="uri">https://libreboot.org/download.uk.md</a></p>
|
|
||||||
<p><a href="/sitemap.html">Індекс сайта</a></p>
|
|
||||||
<p>Ця сторінка була створена з <a
|
|
||||||
href="https://untitled.vimuser.org/">untitled static site
|
|
||||||
generator</a>.</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
|
@ -11,51 +11,61 @@ x-toc-enable: true
|
||||||
Libreboot складається разом, і як підтримувати його. Якщо ви бажаєте зібрати
|
Libreboot складається разом, і як підтримувати його. Якщо ви бажаєте зібрати
|
||||||
Libreboot із джерельного кода, [прочитайте цю сторінку](docs/build/).
|
Libreboot із джерельного кода, [прочитайте цю сторінку](docs/build/).
|
||||||
|
|
||||||
READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
|
Buy Libreboot pre-installed
|
||||||
====================================================================
|
--------------
|
||||||
|
|
||||||
**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
the release ROMs of Libreboot are MISSING certain files, that you must insert
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
yourself. FAILURE to adhere to this warning may result in you bricking your
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
machine (rendering it unbootable), if you were to flash the release ROMs without
|
|
||||||
modifying them in any way. For more information, please read:**
|
|
||||||
|
|
||||||
**[Insert vendor files on Sandybridge/Ivybridge/Haswell](docs/install/ivy_has_common.md)**
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
NOTE: This warning does not apply to ROMs that you compiled yourself, using
|
Safety warning
|
||||||
lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
|
--------------
|
||||||
in release ROMs. The link above says how to re-add them. When building ROM images
|
|
||||||
yourself, from source, Libreboot's build system automatically handles it. See:
|
|
||||||
[Libreboot build instructions](docs/build/)
|
|
||||||
|
|
||||||
This isn't required on *all* Libreboot-supported boards, but if in doubt, follow
|
**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
|
||||||
these instructions anyway. If you run the vendor scripts on a board that doesn't
|
LIBREBOOT](news/safety.md).**
|
||||||
need vendor files, nothing will happen.
|
|
||||||
|
|
||||||
Код підпису GPG
|
Код підпису GPG
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
**Останнім випуском є Libreboot 20231021, в директорії `testing`.**
|
**Останнім випуском є Libreboot 20240612, в директорії `stable`.**
|
||||||
|
|
||||||
### НОВИЙ КЛЮЧ
|
### НОВИЙ КЛЮЧ
|
||||||
|
|
||||||
Повний відбиток ключа: `98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856`
|
Повний відбиток ключа: `8BB1 F7D2 8CF7 696D BF4F 7192 5C65 4067 D383 B1FF`
|
||||||
|
|
||||||
Вищезазначений ключ для Libreboot 20231021, та наступних випусків.
|
Вищезазначений ключ для Libreboot 20240126, та наступних випусків. This key
|
||||||
|
is applicable to any release made on or after the date: 28 December 2023. It
|
||||||
|
will expire on 26 December 2028.
|
||||||
|
|
||||||
Завантажте ключ тут: [lbkey.asc](lbkey.asc)
|
Завантажте ключ тут: [lbkey.asc](lbkey.asc)
|
||||||
|
|
||||||
Випуски Libreboot підписані з використанням GPG.
|
Випуски Libreboot підписані з використанням GPG.
|
||||||
|
|
||||||
### СТАРИЙ КЛЮЧ:
|
### СТАРИЙ КЛЮЧ
|
||||||
|
|
||||||
|
Повний відбиток ключа: `98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856`
|
||||||
|
|
||||||
|
This key is for Libreboot releases *after* the 20160907 release, and up
|
||||||
|
to the Libreboot 20240612 release. This key *expired* during December 2023,
|
||||||
|
so you should use the *newer* key (see above) for the releases after
|
||||||
|
Libreboot 20240126.
|
||||||
|
|
||||||
|
Завантажте ключ тут: [lbkey.asc](lbkeyold.asc)
|
||||||
|
|
||||||
|
Випуски Libreboot підписані з використанням GPG.
|
||||||
|
|
||||||
|
### СТАРИЙ СТАРИЙ КЛЮЧ:
|
||||||
|
|
||||||
Цей ключ для Libreboot 20160907 та всіх старіших випусків:
|
Цей ключ для Libreboot 20160907 та всіх старіших випусків:
|
||||||
|
|
||||||
Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 C5B2
|
Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 C5B2
|
||||||
|
|
||||||
Ключ GPG також може бути завантажений разом із цим експортованим дампом
|
Ключ GPG також може бути завантажений разом із цим експортованим дампом
|
||||||
публічного ключа: [lbkeyold.asc](lbkeyold.asc).
|
публічного ключа: [lbkeyold.asc](lbkeyoldold.asc).
|
||||||
|
|
||||||
sha512sum -c sha512sum.txt
|
sha512sum -c sha512sum.txt
|
||||||
gpg --verify sha512sum.txt.sig
|
gpg --verify sha512sum.txt.sig
|
||||||
|
@ -73,22 +83,21 @@ need vendor files, nothing will happen.
|
||||||
Дзеркала HTTPS {#https}
|
Дзеркала HTTPS {#https}
|
||||||
-------------
|
-------------
|
||||||
|
|
||||||
**Останнім випуском є Libreboot 20231021, в директорії `testing`.**
|
**Останнім випуском є Libreboot 20240612, в директорії `stable`.**
|
||||||
|
|
||||||
Дані дзеркала є рекомендованими, оскільки використовують TLS (https://) шифрування.
|
Дані дзеркала є рекомендованими, оскільки використовують TLS (https://) шифрування.
|
||||||
|
|
||||||
Ви можете завантажити Libreboot через дані дзеркала:
|
Ви можете завантажити Libreboot через дані дзеркала:
|
||||||
|
|
||||||
|
* <https://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський
|
||||||
|
університет, США)
|
||||||
|
* <https://mirror.shapovalov.website/libreboot/> (shapovalov.website, Україна)
|
||||||
* <https://www.mirrorservice.org/sites/libreboot.org/release/> (Кентський
|
* <https://www.mirrorservice.org/sites/libreboot.org/release/> (Кентський
|
||||||
університет, Великобританія)
|
університет, Великобританія)
|
||||||
* <https://mirrors.mit.edu/libreboot/> (Університет МТІ, США)
|
* <https://mirrors.mit.edu/libreboot/> (Університет МТІ, США)
|
||||||
* <https://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський
|
|
||||||
університет, США)
|
|
||||||
* <https://mirror.shapovalov.tech/libreboot/> (shapovalov.tech, Україна)
|
|
||||||
* <https://mirror.koddos.net/libreboot/> (koddos.net, Нідерланди)
|
* <https://mirror.koddos.net/libreboot/> (koddos.net, Нідерланди)
|
||||||
* <https://mirror-hk.koddos.net/libreboot/> (koddos.net, Гонконг)
|
* <https://mirror-hk.koddos.net/libreboot/> (koddos.net, Гонконг)
|
||||||
* <https://mirror.cyberbits.eu/libreboot/> (cyberbits.eu, Франція)
|
* <https://mirror.cyberbits.eu/libreboot/> (cyberbits.eu, Франція)
|
||||||
* <https://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
|
|
||||||
|
|
||||||
Дзеркала RSYNC {#rsync}
|
Дзеркала RSYNC {#rsync}
|
||||||
-------------
|
-------------
|
||||||
|
@ -98,11 +107,10 @@ need vendor files, nothing will happen.
|
||||||
* <rsync://rsync.mirrorservice.org/libreboot.org/release/> (Кентський університет,
|
* <rsync://rsync.mirrorservice.org/libreboot.org/release/> (Кентський університет,
|
||||||
Великобританія)
|
Великобританія)
|
||||||
* <rsync://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський університет, США)
|
* <rsync://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський університет, США)
|
||||||
* <rsync://rsync.shapovalov.tech/libreboot/> (shapovalov.tech, Україна)
|
* <rsync://rsync.shapovalov.website/libreboot/> (shapovalov.website, Україна)
|
||||||
* <rsync://ftp.linux.ro/libreboot/> (linux.ro, Румунія)
|
* <rsync://ftp.linux.ro/libreboot/> (linux.ro, Румунія)
|
||||||
* <rsync://mirror.koddos.net/libreboot/> (koddos.net, Нідерланди)
|
* <rsync://mirror.koddos.net/libreboot/> (koddos.net, Нідерланди)
|
||||||
* <rsync://mirror-hk.koddos.net/libreboot/> (koddos.net, Гонконг)
|
* <rsync://mirror-hk.koddos.net/libreboot/> (koddos.net, Гонконг)
|
||||||
* <rsync://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
|
|
||||||
|
|
||||||
Ви підтримуєте роботу дзеркала? Зв'яжіться з проектом libreboot, і посилання буде
|
Ви підтримуєте роботу дзеркала? Зв'яжіться з проектом libreboot, і посилання буде
|
||||||
додано до цієї сторінки!
|
додано до цієї сторінки!
|
||||||
|
@ -166,7 +174,7 @@ crontab. Ця сторінка розповідає вам, як викорис
|
||||||
Дзеркала HTTP {#http}
|
Дзеркала HTTP {#http}
|
||||||
------------
|
------------
|
||||||
|
|
||||||
**Останнім випуском є Libreboot 20231021, під директорією `testing`.**
|
**Останнім випуском є Libreboot 20240612, під директорією `stable`.**
|
||||||
|
|
||||||
УВАГА: ці дзеркала є не-HTTPS, що означає, що вони
|
УВАГА: ці дзеркала є не-HTTPS, що означає, що вони
|
||||||
незашифровані. Ваш трафік може бути об'єктом втручання
|
незашифровані. Ваш трафік може бути об'єктом втручання
|
||||||
|
@ -180,7 +188,7 @@ crontab. Ця сторінка розповідає вам, як викорис
|
||||||
Дзеркала FTP {#ftp}
|
Дзеркала FTP {#ftp}
|
||||||
-----------
|
-----------
|
||||||
|
|
||||||
**Останнім випуском є Libreboot 20231021, під директорією `testing`.**
|
**Останнім випуском є Libreboot 20240612, під директорією `stable`.**
|
||||||
|
|
||||||
УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики присутні.
|
УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики присутні.
|
||||||
|
|
||||||
|
@ -205,4 +213,4 @@ Libreboot включає статично зв'язані виконувані
|
||||||
випуски натомість автоматизують встановлення залежностей побудови, з інструкцієї
|
випуски натомість автоматизують встановлення залежностей побудови, з інструкцієї
|
||||||
в документації для побудови різних утиліт з джерельного коду.
|
в документації для побудови різних утиліт з джерельного коду.
|
||||||
|
|
||||||
Ці виконувані файли є утилітами, подібними `flashrom`.
|
Ці виконувані файли є утилітами, подібними `flashprog`.
|
||||||
|
|
|
@ -1 +0,0 @@
|
||||||
1697840147
|
|
95
site/faq.md
95
site/faq.md
|
@ -3,27 +3,25 @@ title: Frequently Asked Questions
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
AKA Frequently Questioned Answers
|
AKA Frequently Questioned Answers
|
||||||
|
|
||||||
|
Buy Libreboot pre-installed
|
||||||
|
==========
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
Important issues
|
Important issues
|
||||||
================
|
================
|
||||||
|
|
||||||
What is the status of software freedom in Libreboot?
|
|
||||||
----------------------------------------------------
|
|
||||||
|
|
||||||
An article was written for Libreboot, to be maintained over time, that
|
|
||||||
accurately describes the current status Libreboot in terms of software freedom,
|
|
||||||
describing any caveats that exist for specific hardware platforms.
|
|
||||||
|
|
||||||
Please read the article, thus:
|
|
||||||
|
|
||||||
[Software and hardware freedom status for each mainboard supported by
|
|
||||||
Libreboot](freedom-status.md)
|
|
||||||
|
|
||||||
You may also find this other section of the FAQ useful:
|
|
||||||
[What level of software freedom does Libreboot give
|
|
||||||
me?](#what-level-of-software-freedom-does-libreboot-give-me)
|
|
||||||
|
|
||||||
How to compile libreboot from source
|
How to compile libreboot from source
|
||||||
------------------------------------
|
------------------------------------
|
||||||
|
|
||||||
|
@ -60,15 +58,15 @@ if you are interested in testing roms before they are released.
|
||||||
Flashrom complains about DEVMEM access
|
Flashrom complains about DEVMEM access
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
If running `flashrom -p internal` for software based flashing, and
|
If running `flashprog -p internal` for software based flashing, and
|
||||||
you get an error related to /dev/mem access, you should reboot with
|
you get an error related to /dev/mem access, you should reboot with
|
||||||
`iomem=relaxed` kernel parameter before running flashrom, or use a kernel
|
`iomem=relaxed` kernel parameter before running flashprog, or use a kernel
|
||||||
that has `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` not enabled.
|
that has `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` not enabled.
|
||||||
|
|
||||||
Example flashrom output with both `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` enabled:
|
Example flashprog output with both `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` enabled:
|
||||||
```
|
```
|
||||||
flashrom v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
|
flashprog v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
|
||||||
flashrom is free software, get the source code at https://flashrom.org
|
flashprog is free software, get the source code at https://flashprog.org
|
||||||
|
|
||||||
Calibrating delay loop... OK.
|
Calibrating delay loop... OK.
|
||||||
Error accessing high tables, 0x100000 bytes at 0x000000007fb5d000
|
Error accessing high tables, 0x100000 bytes at 0x000000007fb5d000
|
||||||
|
@ -78,8 +76,8 @@ Error accessing DMI Table, 0x1000 bytes at 0x000000007fb27000
|
||||||
/dev/mem mmap failed: Operation not permitted
|
/dev/mem mmap failed: Operation not permitted
|
||||||
```
|
```
|
||||||
|
|
||||||
The backlight is darker on the left side of the screen when lowering the brightness on my ThinkPad X200/X200S/X200T, T400, T500, R400, W500, R500 and other Intel laptops
|
Uneven backlight on GM45 ThinkPads
|
||||||
---------------------------------------------------------------------------------------------------------------
|
----------------------------------
|
||||||
|
|
||||||
We don't know how to detect the correct PWM value to use in
|
We don't know how to detect the correct PWM value to use in
|
||||||
coreboot, so we just use the default one in coreboot which has
|
coreboot, so we just use the default one in coreboot which has
|
||||||
|
@ -88,8 +86,8 @@ this issue on some CCFL panels, but not LED panels.
|
||||||
You can work around this in your distribution, by following the notes at
|
You can work around this in your distribution, by following the notes at
|
||||||
[docs: backlight control](../docs/misc/#finetune-backlight-control-on-intel-gpus).
|
[docs: backlight control](../docs/misc/#finetune-backlight-control-on-intel-gpus).
|
||||||
|
|
||||||
The ethernet doesn't work on my X200/T400/X60/T60 when I plug in it
|
GM45 thinkpad ethernet port doesn't autoconnect
|
||||||
-------------------------------------------------------------------
|
-----------------------------------------------
|
||||||
|
|
||||||
This was observed on some systems using network-manager. This happens
|
This was observed on some systems using network-manager. This happens
|
||||||
both on the original BIOS and in libreboot. It's a quirk in the
|
both on the original BIOS and in libreboot. It's a quirk in the
|
||||||
|
@ -105,8 +103,8 @@ On systemd-based distros, you might try:
|
||||||
(the service name might be different for you, depending on your
|
(the service name might be different for you, depending on your
|
||||||
configuration)
|
configuration)
|
||||||
|
|
||||||
My KCMA-D8 or KGPE-D16 doesn't boot with the PIKE2008 module installed
|
PIKE2008 module hangs KGPE-D16 / KCMA-D8
|
||||||
-----------------------------------------------------------------------
|
-----------------------------------------
|
||||||
|
|
||||||
Loading the option ROM from the PIKE2008 module on either ASUS KCMA-D8
|
Loading the option ROM from the PIKE2008 module on either ASUS KCMA-D8
|
||||||
or KGPE-D16 causes the system to hang at boot. It's possible to use
|
or KGPE-D16 causes the system to hang at boot. It's possible to use
|
||||||
|
@ -351,8 +349,7 @@ Technology* (AMT).
|
||||||
|
|
||||||
Use of the `me_cleaner` utility is believed to minimize any security risk when
|
Use of the `me_cleaner` utility is believed to minimize any security risk when
|
||||||
using these Intel platforms, and coreboot *does* contain fully free code for
|
using these Intel platforms, and coreboot *does* contain fully free code for
|
||||||
sandybridge/ivybridge platforms. Freedom-wise, these are similar to libreboot
|
sandybridge/ivybridge platforms.
|
||||||
compatible ThinkPads, and they are quite nice machines.
|
|
||||||
|
|
||||||
More information about the Management Engine can be found on various Web
|
More information about the Management Engine can be found on various Web
|
||||||
sites, including [me.bios.io](http://me.bios.io/Main_Page),
|
sites, including [me.bios.io](http://me.bios.io/Main_Page),
|
||||||
|
@ -627,7 +624,7 @@ simply use dd(1) to extract only the non-padded portion. Continuing with the
|
||||||
examples above, in order to extract a 2MiB x86 descriptorless ROM from a
|
examples above, in order to extract a 2MiB x86 descriptorless ROM from a
|
||||||
padded 16MiB image do the following:
|
padded 16MiB image do the following:
|
||||||
|
|
||||||
dd if=flashromread.rom of=yourrom.rom ibs=14MiB skip=1
|
dd if=flashprogread.rom of=yourrom.rom ibs=14MiB skip=1
|
||||||
|
|
||||||
With padding removed cbfstool will be able to operate on the image as usual.
|
With padding removed cbfstool will be able to operate on the image as usual.
|
||||||
|
|
||||||
|
@ -960,6 +957,44 @@ OpenBSD. Other systems are untested, but should work just fine.
|
||||||
See:
|
See:
|
||||||
[docs/bsd/](docs/bsd/)
|
[docs/bsd/](docs/bsd/)
|
||||||
|
|
||||||
|
Windows??
|
||||||
|
---------
|
||||||
|
|
||||||
|
Yes, you can use Windows 10 and 11. They are not officially supported and the
|
||||||
|
Libreboot project recommends that you *avoid* this choice, because Windows is
|
||||||
|
proprietary software. What this means is that you do *not* have the freedom
|
||||||
|
to use, study, adapt and share the software in any reasonable way. You are
|
||||||
|
entirely at the mercy of Microsoft, whose motive is profit, as opposed to the
|
||||||
|
general advancement of computer science and the welfare of everyone.
|
||||||
|
|
||||||
|
See: [What is Free Software?](https://writefreesoftware.org/learn)
|
||||||
|
|
||||||
|
In addition to being proprietary software, Windows is known to be full of bugs,
|
||||||
|
including *backdoors*. When you *use* Windows, it will send information about
|
||||||
|
you to third parties, used for a variety of purposes such as advertising, but
|
||||||
|
it's quite possible that three-letter agencies may also receive your data if
|
||||||
|
you use Windows.
|
||||||
|
|
||||||
|
For the sake of your freedom, you should never, ever use Windows. Use Linux or
|
||||||
|
BSD systems, which are well-supported. Anyway:
|
||||||
|
|
||||||
|
[Video of Windows 10 booting up](https://yewtu.be/watch?v=BWq6XnWKQnM)
|
||||||
|
|
||||||
|
[Video of Windows 11 booting up](https://yewtu.be/watch?v=OFHiMfVNNeA)
|
||||||
|
|
||||||
|
Of note: Windows 11 officially requires at least TPM 1.2 to be supported, and
|
||||||
|
it requires use of UEFI SecureBoot. To bypass this requirement, MajorGeeks has
|
||||||
|
a guide, see: <https://www.majorgeeks.com/content/page/bypass_tpm.html>
|
||||||
|
|
||||||
|
The person who tested this also stated that they were unable to perform an
|
||||||
|
in-place upgrade from 10 to 11, so they had to wipe the drive and perform a
|
||||||
|
clean (note: not clean, because Windows is full of NSA spyware) installation.
|
||||||
|
|
||||||
|
In both cases, as shown above, the Windows operating system was booting from
|
||||||
|
SeaBIOS, with the coreboot framebuffer initialised at startup, on an Intel GPU
|
||||||
|
initialised via coreboot's *libgfxinit*, on November 2023 versions of Libreboot.
|
||||||
|
We do not yet support booting with UEFI on x86 machines.
|
||||||
|
|
||||||
Are other operating systems compatible?
|
Are other operating systems compatible?
|
||||||
-------------------------------------------------------------------
|
-------------------------------------------------------------------
|
||||||
|
|
||||||
|
|
|
@ -3,27 +3,25 @@ title: Часті питання
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
|
NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
|
||||||
|
now, as of 27 January 2024, which is a fork of flashrom.
|
||||||
|
|
||||||
Також відомо як Відповіді на часті питання
|
Також відомо як Відповіді на часті питання
|
||||||
|
|
||||||
|
Buy Libreboot pre-installed
|
||||||
|
==========
|
||||||
|
|
||||||
|
If you want professional installation, Minifree Ltd sells [Libreboot
|
||||||
|
pre-installed](https://minifree.org/) on select hardware, and it also provides
|
||||||
|
a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
|
||||||
|
if you want to send your machine in to have Libreboot installed for you.
|
||||||
|
|
||||||
|
Leah Rowe, the founder and lead developer of Libreboot, also owns and
|
||||||
|
operates Minifree Ltd; sales provide funding for the Libreboot project.
|
||||||
|
|
||||||
Важливі питання
|
Важливі питання
|
||||||
================
|
================
|
||||||
|
|
||||||
Який статус свободи програмного забезпечення в Libreboot?
|
|
||||||
----------------------------------------------------
|
|
||||||
|
|
||||||
Стаття була написана для Libreboot, для підтримки протягом часу, яка
|
|
||||||
ретельно описує поточний статус Libreboot з точки зору свободи програмного забезпечення,
|
|
||||||
пояснюючи будь-які підводні камені, які існують для конкретних платформ апаратного забезпечення.
|
|
||||||
|
|
||||||
Будь ласка, прочитайте статтю щодо цього:
|
|
||||||
|
|
||||||
[Статус свободи програмного та апаратного забезпечення для кожної плати, яка підтримується
|
|
||||||
Libreboot](freedom-status.uk.md)
|
|
||||||
|
|
||||||
Ви також можете знайти цю іншу секцію сторінки поширених запитань корисною:
|
|
||||||
[Який рівень свободи програмного забезпечення Libreboot дає
|
|
||||||
мені?](#який-рівень-програмної-свободи-дає-мені-libreboot)
|
|
||||||
|
|
||||||
Як скомпілювати libreboot з джерельного коду
|
Як скомпілювати libreboot з джерельного коду
|
||||||
------------------------------------
|
------------------------------------
|
||||||
|
|
||||||
|
@ -46,15 +44,15 @@ Libreboot](freedom-status.uk.md)
|
||||||
Flashrom скаржиться на доступ DEVMEM
|
Flashrom скаржиться на доступ DEVMEM
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
Якщо запущено `flashrom -p internal` для програмної перепрошивки та
|
Якщо запущено `flashprog -p internal` для програмної перепрошивки та
|
||||||
ви отримуєте помилку, пов'язану з доступом до /dev/mem, вам слід перезавантажити систему з
|
ви отримуєте помилку, пов'язану з доступом до /dev/mem, вам слід перезавантажити систему з
|
||||||
параметром ядра `iomem=relaxed` перед виконанням flashrom, або використовуйте ядро,
|
параметром ядра `iomem=relaxed` перед виконанням flashprog, або використовуйте ядро,
|
||||||
для якого не ввімкнено `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM`.
|
для якого не ввімкнено `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM`.
|
||||||
|
|
||||||
Приклад виводу flashrom з обома `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM` ввімкненими:
|
Приклад виводу flashprog з обома `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM` ввімкненими:
|
||||||
```
|
```
|
||||||
flashrom v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
|
flashprog v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
|
||||||
flashrom is free software, get the source code at https://flashrom.org
|
flashprog is free software, get the source code at https://flashprog.org
|
||||||
|
|
||||||
Calibrating delay loop... OK.
|
Calibrating delay loop... OK.
|
||||||
Error accessing high tables, 0x100000 bytes at 0x000000007fb5d000
|
Error accessing high tables, 0x100000 bytes at 0x000000007fb5d000
|
||||||
|
@ -64,7 +62,7 @@ Error accessing DMI Table, 0x1000 bytes at 0x000000007fb27000
|
||||||
/dev/mem mmap failed: Operation not permitted
|
/dev/mem mmap failed: Operation not permitted
|
||||||
```
|
```
|
||||||
|
|
||||||
Підсвічування в лівій частині екрана стає темнішим, якщо зменшити яскравість мого ноутбука ThinkPad X200/X200S/X200T, T400, T500, R400, W500, R500 та інших ноутбуків Intel
|
Підсвічування в лівій частині екрана стає темнішим
|
||||||
---------------------------------------------------------------------------------------------------------------
|
---------------------------------------------------------------------------------------------------------------
|
||||||
|
|
||||||
Ми не знаємо, як визначити правильне значення ШІМ для використання в
|
Ми не знаємо, як визначити правильне значення ШІМ для використання в
|
||||||
|
@ -648,7 +646,7 @@ ROM та флеш-чіпом. Випадок вище, наприклад:
|
||||||
наведені вище приклади, щоб видобути ROM без дескрипторів 2 МБ x86 із доповненого
|
наведені вище приклади, щоб видобути ROM без дескрипторів 2 МБ x86 із доповненого
|
||||||
образа 16 МБ, виконайте наступне:
|
образа 16 МБ, виконайте наступне:
|
||||||
|
|
||||||
dd if=flashromread.rom of=вашrom.rom ibs=14MiB skip=1
|
dd if=flashprogread.rom of=вашrom.rom ibs=14MiB skip=1
|
||||||
|
|
||||||
Після видалення заповнення cbfstool зможе працювати із образом як зазвичай.
|
Після видалення заповнення cbfstool зможе працювати із образом як зазвичай.
|
||||||
|
|
||||||
|
@ -981,6 +979,44 @@ OpenBSD. Інші системи не перевірені, але мають п
|
||||||
Дивіться:
|
Дивіться:
|
||||||
[docs/bsd/](docs/bsd/index.uk.md)
|
[docs/bsd/](docs/bsd/index.uk.md)
|
||||||
|
|
||||||
|
Windows??
|
||||||
|
---------
|
||||||
|
|
||||||
|
Yes, you can use Windows 10 and 11. They are not officially supported and the
|
||||||
|
Libreboot project recommends that you *avoid* this choice, because Windows is
|
||||||
|
proprietary software. What this means is that you do *not* have the freedom
|
||||||
|
to use, study, adapt and share the software in any reasonable way. You are
|
||||||
|
entirely at the mercy of Microsoft, whose motive is profit, as opposed to the
|
||||||
|
general advancement of computer science and the welfare of everyone.
|
||||||
|
|
||||||
|
See: [What is Free Software?](https://writefreesoftware.org/learn)
|
||||||
|
|
||||||
|
In addition to being proprietary software, Windows is known to be full of bugs,
|
||||||
|
including *backdoors*. When you *use* Windows, it will send information about
|
||||||
|
you to third parties, used for a variety of purposes such as advertising, but
|
||||||
|
it's quite possible that three-letter agencies may also receive your data if
|
||||||
|
you use Windows.
|
||||||
|
|
||||||
|
For the sake of your freedom, you should never, ever use Windows. Use Linux or
|
||||||
|
BSD systems, which are well-supported. Anyway:
|
||||||
|
|
||||||
|
[Video of Windows 10 booting up](https://yewtu.be/watch?v=BWq6XnWKQnM)
|
||||||
|
|
||||||
|
[Video of Windows 11 booting up](https://yewtu.be/watch?v=OFHiMfVNNeA)
|
||||||
|
|
||||||
|
Of note: Windows 11 officially requires at least TPM 1.2 to be supported, and
|
||||||
|
it requires use of UEFI SecureBoot. To bypass this requirement, MajorGeeks has
|
||||||
|
a guide, see: <https://www.majorgeeks.com/content/page/bypass_tpm.html>
|
||||||
|
|
||||||
|
The person who tested this also stated that they were unable to perform an
|
||||||
|
in-place upgrade from 10 to 11, so they had to wipe the drive and perform a
|
||||||
|
clean (note: not clean, because Windows is full of NSA spyware) installation.
|
||||||
|
|
||||||
|
In both cases, as shown above, the Windows operating system was booting from
|
||||||
|
SeaBIOS, with the coreboot framebuffer initialised at startup, on an Intel GPU
|
||||||
|
initialised via coreboot's *libgfxinit*, on November 2023 versions of Libreboot.
|
||||||
|
We do not yet support booting with UEFI on x86 machines.
|
||||||
|
|
||||||
Чи підтримуються інші операційні системи?
|
Чи підтримуються інші операційні системи?
|
||||||
-------------------------------------------------------------------
|
-------------------------------------------------------------------
|
||||||
|
|
||||||
|
|
|
@ -2,6 +2,7 @@
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
|
|
||||||
* [Binäre Blob Richtlinie](/news/policy.md)
|
* [Binäre Blob Richtlinie](/news/policy.md)
|
||||||
|
* [Freiheits Status](/freedom-status.md)
|
||||||
* [Diese Seite bearbeiten](/git.de.md)
|
* [Diese Seite bearbeiten](/git.de.md)
|
||||||
* [Wer entwickelt Libreboot?](/who.de.md)
|
* [Wer entwickelt Libreboot?](/who.de.md)
|
||||||
* [Lizenz](/license.md)
|
* [Lizenz](/license.md)
|
||||||
|
|
|
@ -2,6 +2,7 @@
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
|
|
||||||
* [Binary Blob Reduction Policy](/news/policy.md)
|
* [Binary Blob Reduction Policy](/news/policy.md)
|
||||||
|
* [Freedom status](/freedom-status.md)
|
||||||
* [Edit this page](/git.md)
|
* [Edit this page](/git.md)
|
||||||
* [Who develops Libreboot?](/who.md)
|
* [Who develops Libreboot?](/who.md)
|
||||||
* [License](/license.md)
|
* [License](/license.md)
|
||||||
|
|
|
@ -2,6 +2,7 @@
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
|
|
||||||
* [Politica di riduzione di parti binarie proprietarie (blobs)](/news/policy.md)
|
* [Politica di riduzione di parti binarie proprietarie (blobs)](/news/policy.md)
|
||||||
|
* [Grado di liberta' possibile](/freedom-status.md)
|
||||||
* [Modifica questa pagina](/git.de.md)
|
* [Modifica questa pagina](/git.de.md)
|
||||||
* [Chi sviluppa Libreboot?](/who.de.md)
|
* [Chi sviluppa Libreboot?](/who.de.md)
|
||||||
* [Licenza](/license.md)
|
* [Licenza](/license.md)
|
||||||
|
|
|
@ -2,12 +2,13 @@
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
|
|
||||||
* [Політика бінарних блобів](/news/policy.md)
|
* [Політика бінарних блобів](/news/policy.md)
|
||||||
|
* [Статус свободи](/freedom-status.md)
|
||||||
* [Редагувати цю сторінку](/git.md)
|
* [Редагувати цю сторінку](/git.md)
|
||||||
* [Хто розробляє Libreboot?](/who.uk.md)
|
* [Хто розробляє Libreboot?](/who.uk.md)
|
||||||
* [Ліцензія](/license.md)
|
* [Ліцензія](/license.md)
|
||||||
* [Шаблон](/template-license.uk.md)
|
* [Шаблон](/template-license.uk.md)
|
||||||
* [Логотип](/logo-license.uk.md)
|
* [Логотип](/logo-license.uk.md)
|
||||||
* [Автори](/contrib.uk.md)
|
* [Автори](/contrib.md)
|
||||||
|
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
|
|
@ -2,6 +2,7 @@
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
|
|
||||||
* [二进制 blob 政策](/news/policy.md)
|
* [二进制 blob 政策](/news/policy.md)
|
||||||
|
* [自由度现状](/freedom-status.md)
|
||||||
* [编辑本页面](/git.md)
|
* [编辑本页面](/git.md)
|
||||||
* [谁在开发 Libreboot?](/who.md)
|
* [谁在开发 Libreboot?](/who.md)
|
||||||
* [许可证](/license.md)
|
* [许可证](/license.md)
|
||||||
|
|
|
@ -214,7 +214,7 @@ Mostly free software, except for the requirement on `daisy` and `peach` mainboar
|
||||||
to include BL1 bootloader files from the vendor. These are:
|
to include BL1 bootloader files from the vendor. These are:
|
||||||
|
|
||||||
* HP Chromebook 11 G1 (daisy-spring) **(board removed from Libreboot, due to
|
* HP Chromebook 11 G1 (daisy-spring) **(board removed from Libreboot, due to
|
||||||
issues (will be re-added at a later date)**
|
issues (will be re-added at a later date))**
|
||||||
* Samsung Chromebook XE303 (daisy-snow) **(ditto)**
|
* Samsung Chromebook XE303 (daisy-snow) **(ditto)**
|
||||||
* Samsung Chromebook 2 13” (peach-pi) **(ditto)**
|
* Samsung Chromebook 2 13” (peach-pi) **(ditto)**
|
||||||
* Samsung Chromebook 2 11” (peach-pit) **(ditto)**
|
* Samsung Chromebook 2 11” (peach-pit) **(ditto)**
|
||||||
|
@ -239,11 +239,12 @@ Intel/x86
|
||||||
### Intel ME:
|
### Intel ME:
|
||||||
|
|
||||||
Neutered ME required on these targets: `t420_8mb`, `t420s_8mb`, `t430_12mb`,
|
Neutered ME required on these targets: `t420_8mb`, `t420s_8mb`, `t430_12mb`,
|
||||||
`t440p_12mb`, `t440pmrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
|
`t440plibremrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
|
||||||
`w541_12mb`, `w541mrc_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
|
`w541_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
|
||||||
`x230edp_12mb`, `x230t_12mb`, `x230t_16mb`, `hp8200sff`, `hp2560p_8mb`,
|
`x230edp_12mb`, `x230t_12mb`, `x230t_16mb`, `hp8200sff`, `hp2560p_8mb`,
|
||||||
`hp2570p_16mb`, `hp8300usdt_16mb`, `hp2170p_16mb`, `hp9470m_16mb`
|
`hp2570p_16mb`, `hp8300usdt_16mb`, `hp2170p_16mb`, `hp9470m_16mb`,
|
||||||
and `t1650_12mb`.
|
`hp820g2_12mb`, `t1650_12mb` and the OptiPlex 9020 ports, also
|
||||||
|
Sandybridge/Ivybridge/Haswell Dell Latitude.
|
||||||
|
|
||||||
As stated, Libreboot provides this in a state where the ME is no longer a
|
As stated, Libreboot provides this in a state where the ME is no longer a
|
||||||
threat to security. It initialises itself, but then does nothing, so it's
|
threat to security. It initialises itself, but then does nothing, so it's
|
||||||
|
@ -276,6 +277,11 @@ technically required, but highly recommended. To remove, do:
|
||||||
|
|
||||||
cbfstool filename.rom remove -n cpu_microcode_blob.bin
|
cbfstool filename.rom remove -n cpu_microcode_blob.bin
|
||||||
|
|
||||||
|
On ASUS KFSN4-DRE, KCMA-D8 and KGPE-D16 boards, do this instead:
|
||||||
|
|
||||||
|
cbfstool filename.rom remove -n microcode_amd.bin
|
||||||
|
cbfstool filename.rom remove -n microcode_amd_fam15h.bin
|
||||||
|
|
||||||
[Releases after Libreboot 20230423 will provide separate ROMs with microcode
|
[Releases after Libreboot 20230423 will provide separate ROMs with microcode
|
||||||
excluded, alongside default ones with microcode included.](news/microcode.md)
|
excluded, alongside default ones with microcode included.](news/microcode.md)
|
||||||
|
|
||||||
|
|
|
@ -330,10 +330,11 @@ Intel/x86
|
||||||
### Intel ME:
|
### Intel ME:
|
||||||
|
|
||||||
Нейтралізований ME потрібен на цих цілях: `t420_8mb`, `t420s_8mb`, `t430_12mb`,
|
Нейтралізований ME потрібен на цих цілях: `t420_8mb`, `t420s_8mb`, `t430_12mb`,
|
||||||
`t440p_12mb`, `t440pmrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
|
`t440plibremrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
|
||||||
`w541_12mb`, `w541mrc_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
|
`w541_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
|
||||||
`x230edp_12mb`, `x230t_12mb`, `x230t_16mb`, `hp8200sff_8mb`, `hp2560p_8mb`,
|
`x230edp_12mb`, `x230t_12mb`, `x230t_16mb`, `hp8200sff_8mb`, `hp2560p_8mb`,
|
||||||
`hp2570p_16mb`, `hp2170p_16mb`, `hp9470m_16mb` та `t1650_12mb`.
|
`hp2570p_16mb`, `hp2170p_16mb`, `hp9470m_16mb`, `hp820g2_12mb`, `t1650_12mb` та
|
||||||
|
Dell OptiPlex 9020, Sandybridge/Ivybridge/Haswell Dell Latitude.
|
||||||
|
|
||||||
Як заявлено, Libreboot надає це в стані, де ME більше не є
|
Як заявлено, Libreboot надає це в стані, де ME більше не є
|
||||||
загрозою для безпеки. Він ініціалізує себе, але потім нічого не робить, тому його
|
загрозою для безпеки. Він ініціалізує себе, але потім нічого не робить, тому його
|
||||||
|
|
|
@ -252,6 +252,14 @@ Ein weiterer Weg Patches zu senden ist Leah Rowe direkt eine email zu senden:
|
||||||
Um den Prozess der Quelltext Überprüfung transparent zu gestalten,
|
Um den Prozess der Quelltext Überprüfung transparent zu gestalten,
|
||||||
wird jedoch empfohlen künftig Codeberg zu verwenden.
|
wird jedoch empfohlen künftig Codeberg zu verwenden.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
------------
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
Mirrors für lbmk.git
|
Mirrors für lbmk.git
|
||||||
===================
|
===================
|
||||||
|
|
||||||
|
@ -261,6 +269,7 @@ Libreboot Veröffentlichungen herstellt (inklusive kompilierter ROM Images).
|
||||||
Du kannst `git clone` für alle diese Links ausführen (die Links können auch
|
Du kannst `git clone` für alle diese Links ausführen (die Links können auch
|
||||||
angeklickt werden, um Änderungen in deinem Web Browser anzusehen):
|
angeklickt werden, um Änderungen in deinem Web Browser anzusehen):
|
||||||
|
|
||||||
|
* <https://git.sr.ht/~libreboot/lbmk>
|
||||||
* <https://git.disroot.org/libreboot/lbmk>
|
* <https://git.disroot.org/libreboot/lbmk>
|
||||||
* <https://gitea.treehouse.systems/libreboot/lbmk>
|
* <https://gitea.treehouse.systems/libreboot/lbmk>
|
||||||
* <https://git.fosscommunity.in/libreboot/lbmk>
|
* <https://git.fosscommunity.in/libreboot/lbmk>
|
||||||
|
@ -286,6 +295,7 @@ der Seite die Du gerade liest!
|
||||||
Du kannst `git clone` für diese Links ausführen und/oder die Links
|
Du kannst `git clone` für diese Links ausführen und/oder die Links
|
||||||
anklicken um Änderungen in deinem Web Browser anzusehen). Siehe:
|
anklicken um Änderungen in deinem Web Browser anzusehen). Siehe:
|
||||||
|
|
||||||
|
* <https://git.sr.ht/~libreboot/lbwww>
|
||||||
* <https://git.disroot.org/libreboot/lbwww>
|
* <https://git.disroot.org/libreboot/lbwww>
|
||||||
* <https://gitea.treehouse.systems/libreboot/lbwww>
|
* <https://gitea.treehouse.systems/libreboot/lbwww>
|
||||||
* <https://git.fosscommunity.in/libreboot/lbwww>
|
* <https://git.fosscommunity.in/libreboot/lbwww>
|
||||||
|
|
10
site/git.md
10
site/git.md
|
@ -232,6 +232,14 @@ Another way to submit patches is to email Leah Rowe directly:
|
||||||
However, for transparency of the code review process, it's recommended that you
|
However, for transparency of the code review process, it's recommended that you
|
||||||
use Codeberg, for the time being.
|
use Codeberg, for the time being.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
------------
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
Mirrors of lbmk.git
|
Mirrors of lbmk.git
|
||||||
===================
|
===================
|
||||||
|
|
||||||
|
@ -241,6 +249,7 @@ produces Libreboot releases (including compiled ROM images).
|
||||||
You can run `git clone` on any of these links (the links are also clickable,
|
You can run `git clone` on any of these links (the links are also clickable,
|
||||||
to view changes in your Web browser):
|
to view changes in your Web browser):
|
||||||
|
|
||||||
|
* <https://git.sr.ht/~libreboot/lbmk>
|
||||||
* <https://git.disroot.org/libreboot/lbmk>
|
* <https://git.disroot.org/libreboot/lbmk>
|
||||||
* <https://gitea.treehouse.systems/libreboot/lbmk>
|
* <https://gitea.treehouse.systems/libreboot/lbmk>
|
||||||
* <https://git.fosscommunity.in/libreboot/lbmk>
|
* <https://git.fosscommunity.in/libreboot/lbmk>
|
||||||
|
@ -266,6 +275,7 @@ you are reading right now!
|
||||||
You can run `git clone` on these links, and/or click to view changes in your
|
You can run `git clone` on these links, and/or click to view changes in your
|
||||||
Web browser. See:
|
Web browser. See:
|
||||||
|
|
||||||
|
* <https://git.sr.ht/~libreboot/lbwww>
|
||||||
* <https://git.disroot.org/libreboot/lbwww>
|
* <https://git.disroot.org/libreboot/lbwww>
|
||||||
* <https://gitea.treehouse.systems/libreboot/lbwww>
|
* <https://gitea.treehouse.systems/libreboot/lbwww>
|
||||||
* <https://git.fosscommunity.in/libreboot/lbwww>
|
* <https://git.fosscommunity.in/libreboot/lbwww>
|
||||||
|
|
|
@ -232,6 +232,14 @@ IRC-канал libreboot і повідомити канал, які виправ
|
||||||
Однак, для прозорості процесу перевірки коду, ми рекомендуємо на даний момент
|
Однак, для прозорості процесу перевірки коду, ми рекомендуємо на даний момент
|
||||||
використовувати Codeberg.
|
використовувати Codeberg.
|
||||||
|
|
||||||
|
Mailing list
|
||||||
|
------------
|
||||||
|
|
||||||
|
Libreboot has this mailing list:
|
||||||
|
<https://lists.sr.ht/~libreboot/libreboot>
|
||||||
|
|
||||||
|
The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
|
||||||
|
|
||||||
Дзеркала lbmk.git
|
Дзеркала lbmk.git
|
||||||
===================
|
===================
|
||||||
|
|
||||||
|
@ -241,6 +249,7 @@ IRC-канал libreboot і повідомити канал, які виправ
|
||||||
Ви можете виконати `git clone` на будь-якому з цих посилань (посилання є також доступними для натискання,
|
Ви можете виконати `git clone` на будь-якому з цих посилань (посилання є також доступними для натискання,
|
||||||
для перегляду змін в вашому веб-браузері):
|
для перегляду змін в вашому веб-браузері):
|
||||||
|
|
||||||
|
* <https://git.sr.ht/~libreboot/lbmk>
|
||||||
* <https://git.disroot.org/libreboot/lbmk>
|
* <https://git.disroot.org/libreboot/lbmk>
|
||||||
* <https://gitea.treehouse.systems/libreboot/lbmk>
|
* <https://gitea.treehouse.systems/libreboot/lbmk>
|
||||||
* <https://git.fosscommunity.in/libreboot/lbmk>
|
* <https://git.fosscommunity.in/libreboot/lbmk>
|
||||||
|
@ -266,6 +275,7 @@ IRC-канал libreboot і повідомити канал, які виправ
|
||||||
Ви можете виконати `git clone` на цих посиланнях, та/або натиснути для перегляду змін в вашому
|
Ви можете виконати `git clone` на цих посиланнях, та/або натиснути для перегляду змін в вашому
|
||||||
веб-браузері. Дивіться:
|
веб-браузері. Дивіться:
|
||||||
|
|
||||||
|
* <https://git.sr.ht/~libreboot/lbwww>
|
||||||
* <https://git.disroot.org/libreboot/lbwww>
|
* <https://git.disroot.org/libreboot/lbwww>
|
||||||
* <https://gitea.treehouse.systems/libreboot/lbwww>
|
* <https://gitea.treehouse.systems/libreboot/lbwww>
|
||||||
* <https://git.fosscommunity.in/libreboot/lbwww>
|
* <https://git.fosscommunity.in/libreboot/lbwww>
|
||||||
|
|
|
@ -1,212 +0,0 @@
|
||||||
<!DOCTYPE html>
|
|
||||||
<html lang="de" dir="ltr">
|
|
||||||
<head>
|
|
||||||
<meta charset="utf-8">
|
|
||||||
<meta name="generator" content="pandoc">
|
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
|
||||||
|
|
||||||
<!-- anti-social media tags -->
|
|
||||||
<meta property="og:title" content="Libreboot – Libreboot projekt">
|
|
||||||
<meta property="og:type" content="article" />
|
|
||||||
<meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
|
|
||||||
<meta property="og:url" content="https://libreboot.org/index.de.html">
|
|
||||||
<meta name="twitter:card" content="summary_large_image">
|
|
||||||
<meta property="og:description" content="Libreboot – Libreboot projekt">
|
|
||||||
<meta property="og:site_name" content="Libreboot – Libreboot projekt">
|
|
||||||
<meta name="twitter:image:alt" content="Libreboot – Libreboot projekt">
|
|
||||||
|
|
||||||
<title>Libreboot – Libreboot projekt</title>
|
|
||||||
<link rel="stylesheet" href="/global.css">
|
|
||||||
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
|
|
||||||
</head>
|
|
||||||
<body>
|
|
||||||
<div class="page">
|
|
||||||
<header>
|
|
||||||
<div class="title">
|
|
||||||
<p class="title-logo">
|
|
||||||
<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
|
|
||||||
</p>
|
|
||||||
<h1 class="title">Libreboot projekt</h1>
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li><a href="/index.de.html">Home</a></li>
|
|
||||||
<li><a href="/faq.html">FAQ</a></li>
|
|
||||||
<li><strong><a href="/freedom-status.html">Freiheits Status</a></strong></li>
|
|
||||||
<li><strong><a href="/download.html">Download</a></strong></li>
|
|
||||||
<li><a href="/docs/install/">Installation</a></li>
|
|
||||||
<li><a href="/docs/">Dokumentation</a></li>
|
|
||||||
<li><a href="/news/">Neuigkeiten</a></li>
|
|
||||||
<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
|
|
||||||
<li><a href="/git.de.html">Patch senden</a></li>
|
|
||||||
<li><strong><a href="https://www.patreon.com/libreleah">Spenden</a></strong></li>
|
|
||||||
<li><a href="/contact.de.html">Kontakt</a></li>
|
|
||||||
<li><strong><a href="https://minifree.org/">Vorinstalliertes Gerät kaufen</a></strong></li>
|
|
||||||
</ul>
|
|
||||||
<hr/>
|
|
||||||
</header>
|
|
||||||
<nav id="TOC">
|
|
||||||
<h1>Navigate this page:</h1>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#warum-solltest-du-libreboot-verwenden">Warum solltest Du
|
|
||||||
<em>Libreboot</em> verwenden?</a></li>
|
|
||||||
<li><a href="#libreboot-ist-kein-coreboot-fork">Libreboot ist kein
|
|
||||||
Coreboot Fork</a></li>
|
|
||||||
<li><a href="#wie-kann-ich-helfen">Wie kann ich helfen</a></li>
|
|
||||||
<li><a href="#übersetzungen-für-libreboot.org-benötigt">Übersetzungen
|
|
||||||
für libreboot.org benötigt</a></li>
|
|
||||||
</ul>
|
|
||||||
</nav>
|
|
||||||
<div class="pagetext">
|
|
||||||
<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
|
|
||||||
href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
|
|
||||||
| <a href="index.uk.html">українська</a> | <a
|
|
||||||
href="index.zh-cn.html">简体中文</a></p>
|
|
||||||
<p>Das <em>Libreboot</em> Projekt bietet eine <a
|
|
||||||
href="freedom-status.html">freie</a> <em>Boot Firmware</em> welche auf
|
|
||||||
<a href="docs/hardware/">bestimmten Intel/AMD x86 und ARM Geräten</a>
|
|
||||||
die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie),
|
|
||||||
und dann einen Bootloader für dein Betriebssystem startet. <a
|
|
||||||
href="docs/linux/">Linux</a> sowie <a href="docs/bsd/">BSD</a> werden
|
|
||||||
gut unterstützt. Es ersetzt proprietäre BIOS/UEFI Firmware. Hilfe ist
|
|
||||||
verfügbar via <a
|
|
||||||
href="https://web.libera.chat/#libreboot">#libreboot</a> und <a
|
|
||||||
href="https://libera.chat/">Libera</a> IRC.</p>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
|
|
||||||
<p><strong>NEUESTE VERSION: Die neueste Version von Libreboot ist
|
|
||||||
20231021, veröffentlicht am 21. Oktober 2023. Siehe auch: <a
|
|
||||||
href="news/libreboot20231021.html">Libreboot 20231021 release
|
|
||||||
announcement</a>.</strong></p>
|
|
||||||
<h2 id="warum-solltest-du-libreboot-verwenden">Warum solltest Du
|
|
||||||
<em>Libreboot</em> verwenden?</h2>
|
|
||||||
<p>Libreboot gibt dir <a
|
|
||||||
href="https://writefreesoftware.org/">Freiheit</a> welche Du mit den
|
|
||||||
meisten Boot Firmwares nicht hast, und zusätzlich schnellere Boot
|
|
||||||
Geschwindigkeiten sowie <a href="docs/linux/grub_hardening.html">höhere
|
|
||||||
Sicherheit</a>. Es ist extrem leistungsfähig und für viele Einsatzzwecke
|
|
||||||
<a href="docs/maintain/">konfigurierbar</a>.</p>
|
|
||||||
<p>Du hast Rechte. Das Recht auf Privatsphäre, Gedankenfreiheit,
|
|
||||||
Meinungsäußerungsfreiheit, und Informationsfreiheit. In diesem
|
|
||||||
Zusammenhang, Libreboot gibt dir diese Rechte. Deine Freiheit ist
|
|
||||||
wichtig. <a href="https://yewtu.be/watch?v=Npd_xDuNi9k">Das Recht auf
|
|
||||||
Reparatur</a> ist wichtig. Viele Menschen verwenden proprietäre
|
|
||||||
(non-libre) Boot Firmware, sogar wenn Sie ein <a
|
|
||||||
href="https://www.openbsd.org/">Libre OS</a> verwenden. Proprietäre
|
|
||||||
Firmware <a href="faq.html#intel">enthält</a> häufig <a
|
|
||||||
href="faq.html#amd">Hintertüren</a>, und kann fehlerhaft sein. Das
|
|
||||||
Libreboot Projekt wurde im Dezember 2013 gegründet, mit dem Ziel,
|
|
||||||
Coreboot Firmware auch für technisch unerfahrene Nutzer verfügbar zu
|
|
||||||
machen.</p>
|
|
||||||
<p>Das Libreboot Projekt verwendet <a
|
|
||||||
href="https://www.coreboot.org/">Coreboot</a> für <a
|
|
||||||
href="https://doc.coreboot.org/getting_started/architecture.html">die
|
|
||||||
Initialiserung der Hardware</a>. Die Coreboot Installation ist für
|
|
||||||
unerfahrene Benutzer überaus schwierig; sie übernimmt lediglich die
|
|
||||||
Basis Initialisierung und springt dann zu einem separaten <a
|
|
||||||
href="https://doc.coreboot.org/payloads.html">payload</a> Programm (z.B.
|
|
||||||
<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
|
|
||||||
href="https://www.tianocore.org/">Tianocore</a>), welche zusätzlich
|
|
||||||
konfiguriert werden muss. <em>Libreboot löst dieses Problem</em>; es ist
|
|
||||||
eine <em>Coreboot Distribution</em> mit einem <a
|
|
||||||
href="docs/build/">automatisierten Build System</a> welches vollständige
|
|
||||||
<em>ROM images</em> für eine robustere Installation erstellt.
|
|
||||||
Dokumentation ist verfügbar.</p>
|
|
||||||
<h2 id="libreboot-ist-kein-coreboot-fork">Libreboot ist kein Coreboot
|
|
||||||
Fork</h2>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
|
|
||||||
<p>Tatsächlich versucht Libreboot so nah am regulären Coreboot zu
|
|
||||||
bleiben wie möglich, für jedes Board, aber mit vielen automatisch durch
|
|
||||||
das Libreboot Build System zur Verfügung gestellten verschiedenen
|
|
||||||
Konfigurationstypen.</p>
|
|
||||||
<p>Ebenso wie <em>Alpine Linux</em> eine <em>Linux Distribution</em>
|
|
||||||
ist, ist Libreboot eine <em>Coreboot Distribution</em>. Sofern Du ein
|
|
||||||
ROM Image von Grund auf herstellen möchtest, musst Du zunächst
|
|
||||||
Konfigurationen auf Experten Level durchführen, und zwar für Coreboot,
|
|
||||||
GRUB sowie sämtliche Software die Du sonst noch verwenden möchtest um
|
|
||||||
das ROM Image vorzubereiten. Mithilfe von <em>Libreboot</em> kannst Du
|
|
||||||
sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen,
|
|
||||||
anschliessend <code>make</code> ausführen, und es wird komplette ROM
|
|
||||||
Images herstellen, ohne das Benutzer Eingaben oder Eingreifen von Nöten
|
|
||||||
sind. Die Konfiguration wurde bereits im Vorfeld erledigt.</p>
|
|
||||||
<p>Sofern Du das reguläre Coreboot herstellen wollen würdest, ohne
|
|
||||||
hierfür das automatisierte Libreboot Build System zu verwenden, würde
|
|
||||||
dies deutlich mehr Eingreifen und ein sehr tiefgreifendes technisches
|
|
||||||
Verständnis voraussetzen um eine funktionsfähige Konfiguration
|
|
||||||
herzustellen.</p>
|
|
||||||
<p>Reguläre Binär Veröffentlichungen bieten diese ROM Images
|
|
||||||
vor-kompiliert, und Du kannst dies einfach installieren ohne spezielle
|
|
||||||
technische Kenntnisse oder Fertigkeiten abgesehen von der Fähigkeit
|
|
||||||
einer <a href="docs/install/">vereinfachten Anleitung, geschrieben für
|
|
||||||
technisch unerfahrene Benutzer</a> zu folgen.</p>
|
|
||||||
<div class="h"><h2 id="wie-kann-ich-helfen">Wie kann ich helfen</h2><a aria-hidden="true" href="#wie-kann-ich-helfen">[link]</a></div>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
|
|
||||||
<p>Der beste Weg wie Du helfen kannst, ist das <em>hinzufügen</em> neuer
|
|
||||||
Mainboards in Libreboot, indem Du eine Konfiguration zur Verfügung
|
|
||||||
stellst. Alles was von Coreboot unterstützt wird kann auch in Libreboot
|
|
||||||
integriert werden, mithilfe von ROM Images in den Veröffentlichungen.
|
|
||||||
Siehe auch:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="docs/maintain/testing.html">Bewerbe dich um Boards zu
|
|
||||||
testen oder zu pflegen</a></li>
|
|
||||||
<li><a href="docs/maintain/porting.html">Anleitung um neue Mainboards
|
|
||||||
hinzuzufügen</a></li>
|
|
||||||
<li><a href="docs/maintain/">Libreboot Build System
|
|
||||||
Dokumentation</a></li>
|
|
||||||
</ul>
|
|
||||||
<p>Zudem ist da noch Pflege des Build Systems (siehe oben), sowie
|
|
||||||
<em>Dokumentation</em> welche wir sehr ernst nehmen. Dokumentation ist
|
|
||||||
wichtig, in jedem Projekt.</p>
|
|
||||||
<p><em>Hilfe für Benutzer</em> ist ebenso wichtig. Bleibe im IRC Chat,
|
|
||||||
und falls Du kompetent genug bist jemandem bei seinem Problem zu helfen
|
|
||||||
(oder bereit mit der Person gemeinsam zu lernen), dann ist dies ein
|
|
||||||
wichtiger Beitrag zum Projekt. Viele Leute fragen zudem unter dem
|
|
||||||
Subreddit <code>r/libreboot</code> nach Hilfe.</p>
|
|
||||||
<p>Eine Liste mit Bugs gibt es unter <a
|
|
||||||
href="https://codeberg.org/libreboot/lbmk/issues">Bug Tracker</a>.</p>
|
|
||||||
<p>Sofern Du einen Bug findest oder einen Fix hast, <a
|
|
||||||
href="git.de.html">hier sind Anleitungen um Patches zu schicken</a>,
|
|
||||||
oder Du kannst davon berichten. Diese Website ist zudem in Markdown
|
|
||||||
geschrieben und verfügbar in einem <a
|
|
||||||
href="https://codeberg.org/libreboot/lbwww">separaten Repository</a> für
|
|
||||||
welches Du auch Patches schicken kannst.</p>
|
|
||||||
<p>Sämtliche Diskussionen über Entwicklung sowie Hilfe für Nutzer findet
|
|
||||||
im IRC Kanal statt. Mehr Informationen gibt es unter <a
|
|
||||||
href="contact.de.html">Kontakt</a>.</p>
|
|
||||||
<h2 id="übersetzungen-für-libreboot.org-benötigt">Übersetzungen für
|
|
||||||
libreboot.org benötigt</h2>
|
|
||||||
<p>Libreboot hat derzeit übersetzte Webseiten in ukrainisch und
|
|
||||||
französisch (aber bislang nicht für alle Seiten für keine der
|
|
||||||
Sprachen)</p>
|
|
||||||
<p>Sofern Du mit Übersetzungen helfen möchtest, kannst Du Seiten
|
|
||||||
übersetzen, existierende Übersetzungen überarbeiten oder deine
|
|
||||||
übersetzten Versionen schicken. Für Anleitungen, siehe bitte hier:</p>
|
|
||||||
<p><a href="news/translations.de.html">Wie man Übersetzungen für
|
|
||||||
libreboot.org bereitstellt</a></p>
|
|
||||||
<p>Auch wenn jemand bereits an einer Übersetzung in einer bestimmten
|
|
||||||
Sprache arbeitet, so können wir immer mehrere Leute gebrauchen. Desto
|
|
||||||
mehr desto besser!</p>
|
|
||||||
<div id="footer">
|
|
||||||
<hr />
|
|
||||||
<ul>
|
|
||||||
<li><a href="/news/policy.html">Binäre Blob Richtlinie</a></li>
|
|
||||||
<li><a href="/git.de.html">Diese Seite bearbeiten</a></li>
|
|
||||||
<li><a href="/who.de.html">Wer entwickelt Libreboot?</a></li>
|
|
||||||
<li><a href="/license.html">Lizenz</a></li>
|
|
||||||
<li><a href="/template-license.html">Vorlage</a></li>
|
|
||||||
<li><a href="/logo-license.html">Logo</a></li>
|
|
||||||
<li><a href="/contrib.html">Autoren</a></li>
|
|
||||||
</ul>
|
|
||||||
<hr />
|
|
||||||
</div>
|
|
||||||
<p>Markdown-Datei: <a href="https://libreboot.org/index.de.md"
|
|
||||||
class="uri">https://libreboot.org/index.de.md</a></p>
|
|
||||||
<p><a href="/sitemap.html">Website karte</a></p>
|
|
||||||
<p>Diese HTML-Seite wurde von <a
|
|
||||||
href="https://untitled.vimuser.org/">untitled static site generator</a>
|
|
||||||
erstellt.</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
|
@ -4,7 +4,7 @@ x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
Das *Libreboot* Projekt bietet
|
Das *Libreboot* Projekt bietet
|
||||||
eine [freie](freedom-status.md) *Boot
|
eine [freie](https://writefreesoftware.org/) *Boot
|
||||||
Firmware* welche auf [bestimmten Intel/AMD x86 und ARM Geräten](docs/hardware/)
|
Firmware* welche auf [bestimmten Intel/AMD x86 und ARM Geräten](docs/hardware/)
|
||||||
die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie),
|
die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie),
|
||||||
und dann einen Bootloader für dein Betriebssystem startet. [Linux](docs/linux/)
|
und dann einen Bootloader für dein Betriebssystem startet. [Linux](docs/linux/)
|
||||||
|
@ -15,9 +15,15 @@ und [Libera](https://libera.chat/) IRC.
|
||||||
|
|
||||||
<img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
|
<img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
|
||||||
|
|
||||||
**NEUESTE VERSION: Die neueste Version von Libreboot ist 20231021, veröffentlicht am
|
You can also [buy Libreboot preinstalled](https://minifree.org/) from Minifree Ltd,
|
||||||
21. Oktober 2023.
|
on select hardware, aswell as send your compatible hardware
|
||||||
Siehe auch: [Libreboot 20231021 release announcement](news/libreboot20231021.md).**
|
for [Libreboot preinstallation](https://minifree.org/product/installation-service/).
|
||||||
|
The founder and lead developer of Libreboot, Leah Rowe, also owns and operates
|
||||||
|
Minifree; sales provide funding for Libreboot.
|
||||||
|
|
||||||
|
**NEUESTE VERSION: Die neueste Version von Libreboot ist 20240612, veröffentlicht
|
||||||
|
am 12. June 2024.
|
||||||
|
Siehe auch: [Libreboot 20240612 release announcement](news/libreboot20240612.md).**
|
||||||
|
|
||||||
Warum solltest Du *Libreboot* verwenden?
|
Warum solltest Du *Libreboot* verwenden?
|
||||||
----------------------------
|
----------------------------
|
||||||
|
@ -65,7 +71,7 @@ musst Du zunächst Konfigurationen auf Experten Level durchführen,
|
||||||
und zwar für Coreboot, GRUB sowie sämtliche Software die Du sonst noch verwenden
|
und zwar für Coreboot, GRUB sowie sämtliche Software die Du sonst noch verwenden
|
||||||
möchtest um das ROM Image vorzubereiten. Mithilfe von *Libreboot* kannst Du
|
möchtest um das ROM Image vorzubereiten. Mithilfe von *Libreboot* kannst Du
|
||||||
sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen, anschliessend
|
sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen, anschliessend
|
||||||
`make` ausführen, und es wird komplette ROM Images herstellen, ohne das Benutzer
|
ein script ausführen, und es wird komplette ROM Images herstellen, ohne das Benutzer
|
||||||
Eingaben oder Eingreifen von Nöten sind. Die Konfiguration wurde bereits im
|
Eingaben oder Eingreifen von Nöten sind. Die Konfiguration wurde bereits im
|
||||||
Vorfeld erledigt.
|
Vorfeld erledigt.
|
||||||
|
|
||||||
|
|
|
@ -1 +0,0 @@
|
||||||
1697839978
|
|
|
@ -1,209 +0,0 @@
|
||||||
<!DOCTYPE html>
|
|
||||||
<html lang="fr" dir="ltr">
|
|
||||||
<head>
|
|
||||||
<meta charset="utf-8">
|
|
||||||
<meta name="generator" content="pandoc">
|
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
|
||||||
|
|
||||||
<!-- anti-social media tags -->
|
|
||||||
<meta property="og:title" content="Libreboot – Projet Libreboot">
|
|
||||||
<meta property="og:type" content="article" />
|
|
||||||
<meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
|
|
||||||
<meta property="og:url" content="https://libreboot.org/index.fr.html">
|
|
||||||
<meta name="twitter:card" content="summary_large_image">
|
|
||||||
<meta property="og:description" content="Libreboot – Projet Libreboot">
|
|
||||||
<meta property="og:site_name" content="Libreboot – Projet Libreboot">
|
|
||||||
<meta name="twitter:image:alt" content="Libreboot – Projet Libreboot">
|
|
||||||
|
|
||||||
<title>Libreboot – Projet Libreboot</title>
|
|
||||||
<link rel="stylesheet" href="/global.css">
|
|
||||||
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
|
|
||||||
</head>
|
|
||||||
<body>
|
|
||||||
<div class="page">
|
|
||||||
<header>
|
|
||||||
<div class="title">
|
|
||||||
<p class="title-logo">
|
|
||||||
<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
|
|
||||||
</p>
|
|
||||||
<h1 class="title">Projet Libreboot</h1>
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li><a href="/">Home</a></li>
|
|
||||||
<li><a href="/faq.html">FAQ</a></li>
|
|
||||||
<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li>
|
|
||||||
<li><strong><a href="/download.html">Download</a></strong></li>
|
|
||||||
<li><a href="/docs/install/">Install</a></li>
|
|
||||||
<li><a href="/docs/">Docs</a></li>
|
|
||||||
<li><a href="/news/">News</a></li>
|
|
||||||
<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
|
|
||||||
<li><a href="/git.html">Send patch</a></li>
|
|
||||||
<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li>
|
|
||||||
<li><a href="/contact.html">Contact</a></li>
|
|
||||||
<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li>
|
|
||||||
</ul>
|
|
||||||
<hr/>
|
|
||||||
</header>
|
|
||||||
<nav id="TOC">
|
|
||||||
<h1>Navigate this page:</h1>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#pourquoi-devriez-vous-utiliser-libreboot">Pourquoi
|
|
||||||
devriez-vous utiliser <em>Libreboot</em>?</a></li>
|
|
||||||
<li><a href="#de-quelle-façon-libreboot-diffère-de-coreboot">De quelle
|
|
||||||
façon Libreboot diffère de Coreboot?</a></li>
|
|
||||||
<li><a href="#comment-aider">Comment aider</a></li>
|
|
||||||
<li><a href="#translations-needed-for-libreboot.org">Translations
|
|
||||||
needed, for libreboot.org</a></li>
|
|
||||||
</ul>
|
|
||||||
</nav>
|
|
||||||
<div class="pagetext">
|
|
||||||
<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
|
|
||||||
href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
|
|
||||||
| <a href="index.uk.html">українська</a> | <a
|
|
||||||
href="index.zh-cn.html">简体中文</a></p>
|
|
||||||
<p>Libreboot est un micrologiciel de démarrage <a
|
|
||||||
href="freedom-status.html">libéré</a> qui initialise le matériel (càd le
|
|
||||||
contrôleur mémoire, CPU, périphériques) sur <a href="docs/hardware/">des
|
|
||||||
ordinateurs x86/ARM spécifiques</a> et lance un chargeur d’amorçage pour
|
|
||||||
votre système d’exploitation. <a href="docs/linux/">Linux</a> et <a
|
|
||||||
href="docs/bsd/">BSD</a> sont bien supportés. C’est un remplacement pour
|
|
||||||
le micrologiciel UEFI/BIOS propriétaire. Des canaux d’aide sont
|
|
||||||
disponibles dans le canal <a
|
|
||||||
href="https://web.libera.chat/#libreboot">#libreboot</a> sur le serveur
|
|
||||||
IRC <a href="https://libera.chat/">Libera</a>.</p>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
|
|
||||||
<p><strong>NOUVELLE VERSION: La dernière version est <a
|
|
||||||
href="news/libreboot20231021.html">Libreboot 20231021</a>, sortie le 21
|
|
||||||
octobre 2023.</strong></p>
|
|
||||||
<h2 id="pourquoi-devriez-vous-utiliser-libreboot">Pourquoi devriez-vous
|
|
||||||
utiliser <em>Libreboot</em>?</h2>
|
|
||||||
<p>Libreboot vous donne des <a
|
|
||||||
href="https://writefreesoftware.org/">libertés</a> que nous n’auriez pas
|
|
||||||
autrement avec d’autre micrologiciel de démarrage. Il est extremement <a
|
|
||||||
href="docs/linux/grub_hardening.html">puissant</a> et <a
|
|
||||||
href="docs/maintain">configurable</a> pour plein de cas
|
|
||||||
d’utilisations.</p>
|
|
||||||
<p>Vous avez des droits. Un droit à la vie privée, liberté de pensée,
|
|
||||||
liberté d’espression et le droit de lire. Dans ce contexte là, Libreboot
|
|
||||||
vous permet d’avoir ces droits. Votre liberté compte. Le <a
|
|
||||||
href="https://yewtu.be/watch?v=Npd_xDuNi9k">Droit à la réparation</a>
|
|
||||||
est important. Beaucoup de personnes utilisent un micrologiciel de
|
|
||||||
démarrage propriétare (non libre), même si ils utilisent <a
|
|
||||||
href="https://www.openbsd.org/">un système d’exploitation libre</a>. Les
|
|
||||||
micrologiciels propriétaires <a href="faq.html#intel">contiennent</a>
|
|
||||||
souvent des <a href="faq.html#amd">portes dérobées</a> et peuvent être
|
|
||||||
instable. Libreboot a été fondé en Décembre 2013 avec le but de rendre
|
|
||||||
le libre au niveau du micrologiciel accessible pour les utilisateurs
|
|
||||||
non-techniques.</p>
|
|
||||||
<p>Libreboot utilise <a href="https://www.coreboot.org">coreboot</a>
|
|
||||||
pour <a
|
|
||||||
href="https://doc.coreboot.org/getting_started/architecture.html">l’initialisation
|
|
||||||
matérielle</a> Coreboot est renommé comme être difficilement installable
|
|
||||||
par des utilisateurs non technique; il se charge seulement de
|
|
||||||
l’initialisation basique puis bascule sur un programme de <a
|
|
||||||
href="https://doc.coreboot.org/payloads.html">charge utile</a> (par ex.
|
|
||||||
<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
|
|
||||||
href="https://www.tianocore.org/">Tianocore</a>), qui doit lui aussi
|
|
||||||
être configuré. <em>Libreboot règle ce problème</em>; c’est une
|
|
||||||
<em>distribution de coreboot</em> avec un <a href="docs/builds/">système
|
|
||||||
de compilation automatisé</a>, crééant des <em>images ROM</em> complètes
|
|
||||||
pour une installation plus robuste. De la documentation est
|
|
||||||
disponible.</p>
|
|
||||||
<h2 id="de-quelle-façon-libreboot-diffère-de-coreboot">De quelle façon
|
|
||||||
Libreboot diffère de Coreboot?</h2>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
|
|
||||||
<p>Contrairement à l’opinion populaire, le but principal de Libreboot
|
|
||||||
n’est pas de fournir un Coreboot déblobbé; ceci n’est simplement qu’une
|
|
||||||
des politiques de Libreboot, une importante certes, mais qui n’est qu’un
|
|
||||||
aspect mineur de Libreboot.</p>
|
|
||||||
<p>De la même façon que <em>Alpine Linux</em> est une distribution
|
|
||||||
Linux, Libreboot est une <em>distribution coreboot</em>. Si vous voulez
|
|
||||||
compilé une image ROM en partant des bases, vous devez alors effectuer
|
|
||||||
une configuration experte de Coreboot, GRUB et n’importe quel autre
|
|
||||||
logiciel dont vous avez besoin afin de préparer la ROM. Avec
|
|
||||||
<em>Libreboot</em>, vous pouvez télécharger la source depuis Git ou une
|
|
||||||
archive, exécuter <code>make</code> etça compilera une image ROM
|
|
||||||
entières. Le système de compilation automatisé de Libreboot nommé
|
|
||||||
<code>lbmk</code> (Libreboot MaKe), compile ces images ROM
|
|
||||||
automatiquement, sans besoin d’entrées utilisateur or intervention
|
|
||||||
requise. La configuration est faite à l’avance.</p>
|
|
||||||
<p>Si vous devriez compiler du coreboot classique sans utiliser le
|
|
||||||
système de build automatisé de Libreboot, ça demanderait bien plus
|
|
||||||
d’effort et de connaissances techniques décente pour écrire une
|
|
||||||
configuration qui marche.</p>
|
|
||||||
<p>Les versions de Libreboot fournissent ces images ROM pré-compilés et
|
|
||||||
vous pouvez les installez simplement, sans connaissance ou compétence
|
|
||||||
particulière à savoir, sauf <a href="docs/install/">suivre des
|
|
||||||
instructions simplifiés écrite pour des utilisateurs non
|
|
||||||
techniques</a>.</p>
|
|
||||||
<div class="h"><h2 id="comment-aider">Comment aider</h2><a aria-hidden="true" href="#comment-aider">[link]</a></div>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
|
|
||||||
<p>The <em>single</em> biggest way you can help it to <em>add</em> new
|
|
||||||
mainboards to Libreboot, by submitting a config. Anything coreboot
|
|
||||||
supports can be integrated in Libreboot, with ROM images provided in
|
|
||||||
releases. See:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="docs/maintain/testing.html">Apply to become a board
|
|
||||||
maintainer/tester</a></li>
|
|
||||||
<li><a href="docs/maintain/porting.html">Porting guide for new
|
|
||||||
mainboards</a></li>
|
|
||||||
<li><a href="docs/maintain/">Libreboot build system
|
|
||||||
documentation</a></li>
|
|
||||||
</ul>
|
|
||||||
<p>After that, there is build system maintenance (see above), and
|
|
||||||
<em>documentation</em> which we take seriously. Documentation is
|
|
||||||
critical, in any project.</p>
|
|
||||||
<p><em>User support</em> is also critical. Stick around on IRC, and if
|
|
||||||
you’re competent to help someone with their issue (or wily enough to
|
|
||||||
learn with them), that is a great service to the project. A lot of
|
|
||||||
people also ask for user support on the <code>r/libreboot</code>
|
|
||||||
subreddit.</p>
|
|
||||||
<p>Vous pouvez allez voir les bugs listés sur le <a
|
|
||||||
href="https://codeberg.org/libreboot/lbmk/issues">traqueur de
|
|
||||||
bugs</a>.</p>
|
|
||||||
<p>Si vous trouvez un bug et avez un correctif, <a href="git.html">voici
|
|
||||||
les instructions pour envoyer des patchs</a>, et vous pouvez aussi nous
|
|
||||||
les signaler. Par ailleurs, ce site est écrit en Markdown et hébergé
|
|
||||||
dans un <a href="https://codeberg.org/libreboot/lbwww">dépôt séparé</a>
|
|
||||||
où vous pouvez envoyer vos patchs.</p>
|
|
||||||
<p>La discussion sur le dévéloppement de Libreboot et le support
|
|
||||||
utilisateur se font toutes sur le canal IRC. Plus d’information est
|
|
||||||
disponible sur la <a href="contact.html">page de contact</a>.</p>
|
|
||||||
<h2 id="translations-needed-for-libreboot.org">Translations needed, for
|
|
||||||
libreboot.org</h2>
|
|
||||||
<p>Libreboot currently has translated Web pages in Ukrainian and French
|
|
||||||
(but not for all pages, yet, on either language).</p>
|
|
||||||
<p>If you want to help with translations, you can translate pages,
|
|
||||||
update existing translations and submit your translated versions. For
|
|
||||||
instructions, please read:</p>
|
|
||||||
<p><a href="news/translations.html">How to submit translations for
|
|
||||||
libreboot.org</a></p>
|
|
||||||
<p>Even if someone is already working on translations in a given
|
|
||||||
language, we can always use multiple people. The more the merrier!</p>
|
|
||||||
<div id="footer">
|
|
||||||
<hr />
|
|
||||||
<ul>
|
|
||||||
<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li>
|
|
||||||
<li><a href="/git.html">Edit this page</a></li>
|
|
||||||
<li><a href="/who.html">Who develops Libreboot?</a></li>
|
|
||||||
<li><a href="/license.html">License</a></li>
|
|
||||||
<li><a href="/template-license.html">Template</a></li>
|
|
||||||
<li><a href="/logo-license.html">Logo</a></li>
|
|
||||||
<li><a href="/contrib.html">Authors</a></li>
|
|
||||||
</ul>
|
|
||||||
<hr />
|
|
||||||
</div>
|
|
||||||
<p>Fichier Markdown pour cette page: <a
|
|
||||||
href="https://libreboot.org/index.fr.md"
|
|
||||||
class="uri">https://libreboot.org/index.fr.md</a></p>
|
|
||||||
<p><a href="/sitemap.html">Plan du site</a></p>
|
|
||||||
<p>Cette page HTML a été générée par le <em><a
|
|
||||||
href="https://untitled.vimuser.org/">untitled static site
|
|
||||||
generator</a></em>.</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
|
@ -3,7 +3,7 @@ title: Projet Libreboot
|
||||||
x-toc-enable: true
|
x-toc-enable: true
|
||||||
...
|
...
|
||||||
|
|
||||||
Libreboot est un micrologiciel de démarrage [libéré](freedom-status.md)
|
Libreboot est un micrologiciel de démarrage [libéré](https://writefreesoftware.org/)
|
||||||
qui initialise le matériel (càd le contrôleur mémoire, CPU,
|
qui initialise le matériel (càd le contrôleur mémoire, CPU,
|
||||||
périphériques) sur [des ordinateurs x86/ARM spécifiques](docs/hardware/)
|
périphériques) sur [des ordinateurs x86/ARM spécifiques](docs/hardware/)
|
||||||
et lance un chargeur d'amorçage pour votre système d'exploitation. [Linux](docs/linux/) et [BSD](docs/bsd/) sont bien supportés. C'est un
|
et lance un chargeur d'amorçage pour votre système d'exploitation. [Linux](docs/linux/) et [BSD](docs/bsd/) sont bien supportés. C'est un
|
||||||
|
@ -13,8 +13,14 @@ dans le canal [\#libreboot](https://web.libera.chat/#libreboot) sur le serveur I
|
||||||
|
|
||||||
<img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
|
<img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
|
||||||
|
|
||||||
**NOUVELLE VERSION: La dernière version est [Libreboot 20231021](news/libreboot20231021.md), sortie
|
You can also [buy Libreboot preinstalled](https://minifree.org/) from Minifree Ltd,
|
||||||
le 21 octobre 2023.**
|
on select hardware, aswell as send your compatible hardware
|
||||||
|
for [Libreboot preinstallation](https://minifree.org/product/installation-service/).
|
||||||
|
The founder and lead developer of Libreboot, Leah Rowe, also owns and operates
|
||||||
|
Minifree; sales provide funding for Libreboot.
|
||||||
|
|
||||||
|
**NOUVELLE VERSION: La dernière version est [Libreboot 20240612](news/libreboot20240612.md), sortie
|
||||||
|
le 12 June 2024.**
|
||||||
|
|
||||||
Pourquoi devriez-vous utiliser *Libreboot*?
|
Pourquoi devriez-vous utiliser *Libreboot*?
|
||||||
-----------------------------------
|
-----------------------------------
|
||||||
|
@ -62,7 +68,7 @@ en partant des bases, vous devez alors effectuer une configuration experte
|
||||||
de Coreboot, GRUB et n'importe quel autre logiciel dont vous avez besoin
|
de Coreboot, GRUB et n'importe quel autre logiciel dont vous avez besoin
|
||||||
afin de préparer la ROM. Avec *Libreboot*,
|
afin de préparer la ROM. Avec *Libreboot*,
|
||||||
vous pouvez télécharger la source depuis Git ou une archive, exécuter
|
vous pouvez télécharger la source depuis Git ou une archive, exécuter
|
||||||
`make` etça compilera une image ROM entières. Le système de compilation
|
and a script etça compilera une image ROM entières. Le système de compilation
|
||||||
automatisé de Libreboot nommé `lbmk` (Libreboot MaKe), compile ces images
|
automatisé de Libreboot nommé `lbmk` (Libreboot MaKe), compile ces images
|
||||||
ROM automatiquement, sans besoin d'entrées utilisateur or intervention
|
ROM automatiquement, sans besoin d'entrées utilisateur or intervention
|
||||||
requise. La configuration est faite à l'avance.
|
requise. La configuration est faite à l'avance.
|
||||||
|
|
|
@ -1 +0,0 @@
|
||||||
1697839885
|
|
203
site/index.html
203
site/index.html
|
@ -1,203 +0,0 @@
|
||||||
<!DOCTYPE html>
|
|
||||||
<html lang="en" dir="ltr">
|
|
||||||
<head>
|
|
||||||
<meta charset="utf-8">
|
|
||||||
<meta name="generator" content="pandoc">
|
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
|
||||||
|
|
||||||
<!-- anti-social media tags -->
|
|
||||||
<meta property="og:title" content="Libreboot – Libreboot project">
|
|
||||||
<meta property="og:type" content="article" />
|
|
||||||
<meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
|
|
||||||
<meta property="og:url" content="https://libreboot.org/">
|
|
||||||
<meta name="twitter:card" content="summary_large_image">
|
|
||||||
<meta property="og:description" content="Libreboot – Libreboot project">
|
|
||||||
<meta property="og:site_name" content="Libreboot – Libreboot project">
|
|
||||||
<meta name="twitter:image:alt" content="Libreboot – Libreboot project">
|
|
||||||
|
|
||||||
<title>Libreboot – Libreboot project</title>
|
|
||||||
<link rel="stylesheet" href="/global.css">
|
|
||||||
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
|
|
||||||
</head>
|
|
||||||
<body>
|
|
||||||
<div class="page">
|
|
||||||
<header>
|
|
||||||
<div class="title">
|
|
||||||
<p class="title-logo">
|
|
||||||
<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
|
|
||||||
</p>
|
|
||||||
<h1 class="title">Libreboot project</h1>
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li><a href="/">Home</a></li>
|
|
||||||
<li><a href="/faq.html">FAQ</a></li>
|
|
||||||
<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li>
|
|
||||||
<li><strong><a href="/download.html">Download</a></strong></li>
|
|
||||||
<li><a href="/docs/install/">Install</a></li>
|
|
||||||
<li><a href="/docs/">Docs</a></li>
|
|
||||||
<li><a href="/news/">News</a></li>
|
|
||||||
<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
|
|
||||||
<li><a href="/git.html">Send patch</a></li>
|
|
||||||
<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li>
|
|
||||||
<li><a href="/contact.html">Contact</a></li>
|
|
||||||
<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li>
|
|
||||||
</ul>
|
|
||||||
<hr/>
|
|
||||||
</header>
|
|
||||||
<nav id="TOC">
|
|
||||||
<h1>Navigate this page:</h1>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#why-should-you-use-libreboot">Why should you use
|
|
||||||
<em>Libreboot</em>?</a></li>
|
|
||||||
<li><a href="#libreboot-is-not-a-fork-of-coreboot">Libreboot is not a
|
|
||||||
fork of coreboot</a></li>
|
|
||||||
<li><a href="#how-to-help">How to help</a></li>
|
|
||||||
<li><a href="#translations-needed-for-libreboot.org">Translations
|
|
||||||
needed, for libreboot.org</a></li>
|
|
||||||
</ul>
|
|
||||||
</nav>
|
|
||||||
<div class="pagetext">
|
|
||||||
<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
|
|
||||||
href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
|
|
||||||
| <a href="index.uk.html">українська</a> | <a
|
|
||||||
href="index.zh-cn.html">简体中文</a></p>
|
|
||||||
<p>The <em>Libreboot</em> project provides <a
|
|
||||||
href="freedom-status.html">free, open source</a> (<em>libre</em>) boot
|
|
||||||
firmware based on coreboot, replacing proprietary BIOS/UEFI firmware on
|
|
||||||
<a href="docs/hardware/">specific Intel/AMD x86 and ARM based
|
|
||||||
motherboards</a>, including laptop and desktop computers. It initialises
|
|
||||||
the hardware (e.g. memory controller, CPU, peripherals) and starts a
|
|
||||||
bootloader for your operating system. <a href="docs/linux/">Linux</a>
|
|
||||||
and <a href="docs/bsd/">BSD</a> are well-supported. Help is available
|
|
||||||
via <a href="https://web.libera.chat/#libreboot">#libreboot</a> on <a
|
|
||||||
href="https://libera.chat/">Libera</a> IRC.</p>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
|
|
||||||
<p><strong>NEW RELEASE: The latest release is Libreboot 20231021,
|
|
||||||
released on 21 October 2023. See: <a
|
|
||||||
href="news/libreboot20231021.html">Libreboot 20231021 release
|
|
||||||
announcement</a>.</strong></p>
|
|
||||||
<h2 id="why-should-you-use-libreboot">Why should you use
|
|
||||||
<em>Libreboot</em>?</h2>
|
|
||||||
<p>Libreboot gives you <a
|
|
||||||
href="https://writefreesoftware.org/">freedoms</a> that you otherwise
|
|
||||||
can’t get with most other boot firmware, plus faster boot speeds and <a
|
|
||||||
href="docs/linux/grub_hardening.html">better security</a>. It’s
|
|
||||||
extremely powerful and <a href="docs/maintain/">configurable</a> for
|
|
||||||
many use cases.</p>
|
|
||||||
<p><em>We</em> believe the freedom to <a
|
|
||||||
href="https://writefreesoftware.org/">study, share, modify and use
|
|
||||||
software</a>, without any restriction, is one of the fundamental human
|
|
||||||
rights that everyone must have. In this context, <em>software
|
|
||||||
freedom</em> matters. Your freedom matters. Education matters. <a
|
|
||||||
href="https://yewtu.be/watch?v=Npd_xDuNi9k">Right to repair</a> matters.
|
|
||||||
Many people use proprietary (non-libre) boot firmware, even if they use
|
|
||||||
<a href="https://www.openbsd.org/">a libre OS</a>. Proprietary firmware
|
|
||||||
often <a href="faq.html#intel">contains</a> <a
|
|
||||||
href="faq.html#amd">backdoors</a>, and can be buggy. The Libreboot
|
|
||||||
project was founded in December 2013, with the express purpose of making
|
|
||||||
coreboot firmware accessible for non-technical users.</p>
|
|
||||||
<p>The Libreboot project uses <a
|
|
||||||
href="https://www.coreboot.org/">coreboot</a> for <a
|
|
||||||
href="https://doc.coreboot.org/getting_started/architecture.html">hardware
|
|
||||||
initialisation</a>. Coreboot is notoriously difficult to install for
|
|
||||||
most non-technical users; it handles only basic initialization and jumps
|
|
||||||
to a separate <a
|
|
||||||
href="https://doc.coreboot.org/payloads.html">payload</a> program (e.g.
|
|
||||||
<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
|
|
||||||
href="https://www.tianocore.org/">Tianocore</a>), which must also be
|
|
||||||
configured. <em>Libreboot solves this problem</em>; it is a <em>coreboot
|
|
||||||
distribution</em> with an <a href="docs/build/">automated build
|
|
||||||
system</a> that builds complete <em>ROM images</em>, for more robust
|
|
||||||
installation. Documentation is provided.</p>
|
|
||||||
<h2 id="libreboot-is-not-a-fork-of-coreboot">Libreboot is not a fork of
|
|
||||||
coreboot</h2>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
|
|
||||||
<p>In fact, Libreboot tries to stay as close to <em>stock</em> coreboot
|
|
||||||
as possible, for each board, but with many different types of
|
|
||||||
configuration provided automatically by the Libreboot build system.</p>
|
|
||||||
<p>In the same way that <em>Alpine Linux</em> is a <em>Linux
|
|
||||||
distribution</em>, Libreboot is a <em>coreboot distribution</em>. If you
|
|
||||||
want to build a ROM image from scratch, you otherwise have to perform
|
|
||||||
expert-level configuration of coreboot, GRUB and whatever other software
|
|
||||||
you need, to prepare the ROM image. With <em>Libreboot</em>, you can
|
|
||||||
literally download from Git or a source archive, and run
|
|
||||||
<code>make</code>, and it will build entire ROM images. An automated
|
|
||||||
build system, named <code>lbmk</code> (Libreboot MaKe), builds these ROM
|
|
||||||
images automatically, without any user input or intervention required.
|
|
||||||
Configuration has already been performed in advance.</p>
|
|
||||||
<p>If you were to build regular coreboot, without using Libreboot’s
|
|
||||||
automated build system, it would require a lot more intervention and
|
|
||||||
decent technical knowledge to produce a working configuration.</p>
|
|
||||||
<p>Regular binary releases of Libreboot provide these ROM images
|
|
||||||
pre-compiled, and you can simply install them, with no special knowledge
|
|
||||||
or skill except the ability to follow <a href="docs/install/">simplified
|
|
||||||
instructions, written for non-technical users</a>.</p>
|
|
||||||
<div class="h"><h2 id="how-to-help">How to help</h2><a aria-hidden="true" href="#how-to-help">[link]</a></div>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
|
|
||||||
<p>The <em>single</em> biggest way you can help is to <em>add</em> new
|
|
||||||
mainboards in Libreboot, by submitting a config. Anything coreboot
|
|
||||||
supports can be integrated in Libreboot, with ROM images provided in
|
|
||||||
releases. See:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="docs/maintain/testing.html">Apply to become a board
|
|
||||||
maintainer/tester</a></li>
|
|
||||||
<li><a href="docs/maintain/porting.html">Porting guide for new
|
|
||||||
mainboards</a></li>
|
|
||||||
<li><a href="docs/maintain/">Libreboot build system
|
|
||||||
documentation</a></li>
|
|
||||||
</ul>
|
|
||||||
<p>After that, there is build system maintenance (see above), and
|
|
||||||
<em>documentation</em> which we take seriously. Documentation is
|
|
||||||
critical, in any project.</p>
|
|
||||||
<p><em>User support</em> is also critical. Stick around on IRC, and if
|
|
||||||
you’re competent to help someone with their issue (or wily enough to
|
|
||||||
learn with them), that is a great service to the project. A lot of
|
|
||||||
people also ask for user support on the <code>r/libreboot</code>
|
|
||||||
subreddit.</p>
|
|
||||||
<p>You can check bugs listed on the <a
|
|
||||||
href="https://codeberg.org/libreboot/lbmk/issues">bug tracker</a>.</p>
|
|
||||||
<p>If you spot a bug and have a fix, <a href="git.html">here are
|
|
||||||
instructions for how to send patches</a>, and you can also report it.
|
|
||||||
Also, this entire website is written in Markdown and hosted in a <a
|
|
||||||
href="https://codeberg.org/libreboot/lbwww">separate repository</a>
|
|
||||||
where you can send patches.</p>
|
|
||||||
<p>Any and all development discussion and user support are all done on
|
|
||||||
the IRC channel. More information is on the <a
|
|
||||||
href="contact.html">contact page</a>.</p>
|
|
||||||
<h2 id="translations-needed-for-libreboot.org">Translations needed, for
|
|
||||||
libreboot.org</h2>
|
|
||||||
<p>Libreboot currently has translated Web pages in Ukrainian and French
|
|
||||||
(but not for all pages, yet, on either language).</p>
|
|
||||||
<p>If you want to help with translations, you can translate pages,
|
|
||||||
update existing translations and submit your translated versions. For
|
|
||||||
instructions, please read:</p>
|
|
||||||
<p><a href="news/translations.html">How to submit translations for
|
|
||||||
libreboot.org</a></p>
|
|
||||||
<p>Even if someone is already working on translations in a given
|
|
||||||
language, we can always use multiple people. The more the merrier!</p>
|
|
||||||
<div id="footer">
|
|
||||||
<hr />
|
|
||||||
<ul>
|
|
||||||
<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li>
|
|
||||||
<li><a href="/git.html">Edit this page</a></li>
|
|
||||||
<li><a href="/who.html">Who develops Libreboot?</a></li>
|
|
||||||
<li><a href="/license.html">License</a></li>
|
|
||||||
<li><a href="/template-license.html">Template</a></li>
|
|
||||||
<li><a href="/logo-license.html">Logo</a></li>
|
|
||||||
<li><a href="/contrib.html">Authors</a></li>
|
|
||||||
</ul>
|
|
||||||
<hr />
|
|
||||||
</div>
|
|
||||||
<p>Markdown file for this page: <a href="https://libreboot.org/index.md"
|
|
||||||
class="uri">https://libreboot.org/index.md</a></p>
|
|
||||||
<p><a href="/sitemap.html">Site map</a></p>
|
|
||||||
<p>This HTML page was generated by the <a
|
|
||||||
href="https://untitled.vimuser.org/">untitled static site
|
|
||||||
generator</a>.</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
|
@ -1,213 +0,0 @@
|
||||||
<!DOCTYPE html>
|
|
||||||
<html lang="it" dir="ltr">
|
|
||||||
<head>
|
|
||||||
<meta charset="utf-8">
|
|
||||||
<meta name="generator" content="pandoc">
|
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
|
||||||
|
|
||||||
<!-- anti-social media tags -->
|
|
||||||
<meta property="og:title" content="Libreboot – Progetto Libreboot">
|
|
||||||
<meta property="og:type" content="article" />
|
|
||||||
<meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
|
|
||||||
<meta property="og:url" content="https://libreboot.org/index.it.html">
|
|
||||||
<meta name="twitter:card" content="summary_large_image">
|
|
||||||
<meta property="og:description" content="Libreboot – Progetto Libreboot">
|
|
||||||
<meta property="og:site_name" content="Libreboot – Progetto Libreboot">
|
|
||||||
<meta name="twitter:image:alt" content="Libreboot – Progetto Libreboot">
|
|
||||||
|
|
||||||
<title>Libreboot – Progetto Libreboot</title>
|
|
||||||
<link rel="stylesheet" href="/global.css">
|
|
||||||
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
|
|
||||||
</head>
|
|
||||||
<body>
|
|
||||||
<div class="page">
|
|
||||||
<header>
|
|
||||||
<div class="title">
|
|
||||||
<p class="title-logo">
|
|
||||||
<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
|
|
||||||
</p>
|
|
||||||
<h1 class="title">Progetto Libreboot</h1>
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li><a href="/index.it.html">Home</a></li>
|
|
||||||
<li><a href="/faq.html">FAQ</a></li>
|
|
||||||
<li><strong><a href="/freedom-status.html">Grado di liberta' possibile</a></strong></li>
|
|
||||||
<li><strong><a href="/download.html">Download</a></strong></li>
|
|
||||||
<li><a href="/docs/install/">Installazione</a></li>
|
|
||||||
<li><a href="/docs/">Documentazione</a></li>
|
|
||||||
<li><a href="/news/">Notizie</a></li>
|
|
||||||
<li><a href="https://codeberg.org/libreboot/lbmk/issues">Difetti (bugs)</a></li>
|
|
||||||
<li><a href="/git.html">Spedisci correzioni (patches)</a></li>
|
|
||||||
<li><strong><a href="https://www.patreon.com/libreleah">Donazioni</a></strong></li>
|
|
||||||
<li><a href="/contact.html">Contatti</a></li>
|
|
||||||
<li><strong><a href="https://minifree.org/">Compra un PC con libreboot gia' installato</a></strong></li>
|
|
||||||
</ul>
|
|
||||||
<hr/>
|
|
||||||
</header>
|
|
||||||
<nav id="TOC">
|
|
||||||
<h1>Sfoglia questa pagina:</h1>
|
|
||||||
<ul>
|
|
||||||
<li><a href="#per-quale-ragione-utilizzare-libreboot">Per quale ragione
|
|
||||||
utilizzare <em>Libreboot</em>?</a></li>
|
|
||||||
<li><a href="#libreboot-non-deriva-da-coreboot">Libreboot non deriva da
|
|
||||||
coreboot</a></li>
|
|
||||||
<li><a href="#come-essere-daiuto">Come essere d’aiuto</a></li>
|
|
||||||
<li><a href="#servono-traduzioni-per-libreboot.org">Servono traduzioni
|
|
||||||
per libreboot.org</a></li>
|
|
||||||
</ul>
|
|
||||||
</nav>
|
|
||||||
<div class="pagetext">
|
|
||||||
<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
|
|
||||||
href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
|
|
||||||
| <a href="index.uk.html">українська</a> | <a
|
|
||||||
href="index.zh-cn.html">简体中文</a></p>
|
|
||||||
<p>Il progetto <em>Libreboot</em> fornisce avvio <a
|
|
||||||
href="freedom-status.html">libero e open source</a> grazie al firmware
|
|
||||||
basato su coreboot, sostituendo cosi’, firmware BIOS/UEFI proprietario
|
|
||||||
su <a href="docs/hardware/">alcune schede madri basate su Intel/AMD x86
|
|
||||||
o ARM</a>, in computer fissi e portatili. Inizializza l’hardware
|
|
||||||
(controller di memoria, CPU, periferiche) e avvia un bootloader per il
|
|
||||||
tuo sistema operativo. <a href="docs/linux/">Linux</a> e <a
|
|
||||||
href="docs/bsd/">BSD</a> sono ben supportati. L’aiuto e’ disponibile sul
|
|
||||||
canale IRC <a href="https://web.libera.chat/#libreboot">#libreboot</a>
|
|
||||||
su <a href="https://libera.chat/">Libera</a>.</p>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
|
|
||||||
<p><strong>ULTIMO RILASCIO: L’ultimo rilascio e’ Libreboot 20231021,
|
|
||||||
rilasciato il 21 ottobre 2023. Vedi: <a
|
|
||||||
href="news/libreboot20231021.html">Libreboot 20231021 annuncio di
|
|
||||||
rilascio</a>.</strong></p>
|
|
||||||
<h2 id="per-quale-ragione-utilizzare-libreboot">Per quale ragione
|
|
||||||
utilizzare <em>Libreboot</em>?</h2>
|
|
||||||
<p>Libreboot ti permette <a
|
|
||||||
href="https://writefreesoftware.org/">liberta’</a> che non potresti
|
|
||||||
ottenere con altri firmware di boot, velocita’ di avvio maggiori e <a
|
|
||||||
href="docs/linux/grub_hardening.html">migliore sicurezza</a>. E’
|
|
||||||
estremamente flessibile e <a href="docs/maintain/">configurabile</a> per
|
|
||||||
la maggior parte dei casi.</p>
|
|
||||||
<p><em>Noi</em> crediamo nella liberta’ di <a
|
|
||||||
href="https://writefreesoftware.org/">studiare, condividere, modificare
|
|
||||||
and usare il software</a>, senza restrizione alcuna, in quanto e’ uno
|
|
||||||
dei fondamentali diritti umani che chiunque deve avere. In questo
|
|
||||||
contesto, <em>il software libero</em> conta. La tua liberta’ conta. La
|
|
||||||
formazione personale conta. <a
|
|
||||||
href="https://yewtu.be/watch?v=Npd_xDuNi9k">Il diritto di riparare</a>
|
|
||||||
conta. Molte persone usano firmware di boot proprietario (non-libero),
|
|
||||||
anche se usano <a href="https://www.openbsd.org/">un sistema operativo
|
|
||||||
libero</a>. Firmware proprietari spesso <a
|
|
||||||
href="faq.html#intel">contengono</a> <a
|
|
||||||
href="faq.html#amd">vulnerabilita’</a>, e possono essere difettosi. Il
|
|
||||||
progetto libreboot venne fondato nel Dicembre 2013, con lo scopo
|
|
||||||
prefissato di permettere che il firmware coreboot sia accessibile anche
|
|
||||||
per utenti con scarsa formazione tecnica.</p>
|
|
||||||
<p>Il progetto Libreboot fa uso di <a
|
|
||||||
href="https://www.coreboot.org/">coreboot</a> per <a
|
|
||||||
href="https://doc.coreboot.org/getting_started/architecture.html">l’inizializzazione
|
|
||||||
hardware</a>. Coreboot e’ notoriamente difficile da installare per
|
|
||||||
utenti che hanno una scarsa formazione tecnica; gestisce solo
|
|
||||||
l’inizializzazione di base e successivamente carica un programma come <a
|
|
||||||
href="https://doc.coreboot.org/payloads.html">payload</a> (ad esempio.
|
|
||||||
<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
|
|
||||||
href="https://www.tianocore.org/">Tianocore</a>), i quali possono essere
|
|
||||||
configurati a piacere. <em>Libreboot risolve questo problema</em>; e’
|
|
||||||
una <em>distribuzione di coreboot</em> con un <a
|
|
||||||
href="docs/build/">sistema di compilazione automatizzato</a> che produce
|
|
||||||
<em>immagini ROM</em> complete, per una installazione piu’ robusta.
|
|
||||||
Viene fornito con apposita documentazione.</p>
|
|
||||||
<h2 id="libreboot-non-deriva-da-coreboot">Libreboot non deriva da
|
|
||||||
coreboot</h2>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
|
|
||||||
<p>In effetti, Libreboot tenta di essere il piu’ possibile simile alla
|
|
||||||
versione <em>ufficiale</em> di coreboot, per ogni scheda, ma con diversi
|
|
||||||
tipi di configurazione forniti automaticamente dal sistema di
|
|
||||||
compilazione automatico di Libreboot.</p>
|
|
||||||
<p>Esattamente come <em>Alpine Linux</em> e’ una <em>distribuzione
|
|
||||||
Linux</em>, Libreboot e’ una <em>distribuzione coreboot</em>. Per fare
|
|
||||||
un immagine ROM da zero, hai bisogno di esperienza necessaria nel
|
|
||||||
configurare coreboot, GRUB e qualunque altra cosa ti serve. Con
|
|
||||||
<em>Libreboot</em>, che puoi scaricare da Git o da un archivio di codici
|
|
||||||
sorgenti, puoi far partire <code>make</code>, e questo mettera’ su
|
|
||||||
automaticamente le immagini ROM richieste. Un sistema di compilazione
|
|
||||||
automatico, chiamato <code>lbmk</code> (Libreboot MaKe), mettera’ su
|
|
||||||
quelle immagini ROM automaticamente, senza troppi interventi da parte
|
|
||||||
dell’utente. Le configurazioni di base sono gia’ state previste in
|
|
||||||
precedenza.</p>
|
|
||||||
<p>Se avresti voluto compilare coreboot normalmente senza il sistema di
|
|
||||||
compilazione automatico di Libreboot, ti troveresti ad affrontare molte
|
|
||||||
piu’ difficolta senza adeguate competenze tecniche per produrre una
|
|
||||||
configurazione funzionante.</p>
|
|
||||||
<p>I rilasci binari di Libreboot forniscono immagini ROM precompilate,
|
|
||||||
che puoi semplicemente installare senza troppe conoscenze tecniche o
|
|
||||||
abilita’ particolari ad eccezione del seguire <a
|
|
||||||
href="docs/install/">semplici istruzioni scritte per chiunque</a>.</p>
|
|
||||||
<div class="h"><h2 id="come-essere-daiuto">Come essere d’aiuto</h2><a aria-hidden="true" href="#come-essere-daiuto">[link]</a></div>
|
|
||||||
<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
|
|
||||||
class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
|
|
||||||
<p>Il <em>modo migliore</em> col quale puoi aiutarci e’ quello di
|
|
||||||
<em>aggiungere</em> nuove schede condividendone la configurazione.
|
|
||||||
Qualunque cosa sia supportata da coreboot puo’ essere integrata in
|
|
||||||
Libreboot, con immagini ROM fornite nei rilasci. Vedi anche:</p>
|
|
||||||
<ul>
|
|
||||||
<li><a href="docs/maintain/testing.html">Richiedi di collaudare o
|
|
||||||
mantenere una scheda</a></li>
|
|
||||||
<li><a href="docs/maintain/porting.html">Guida per rendere nuove schede
|
|
||||||
compatibili</a></li>
|
|
||||||
<li><a href="docs/maintain/">Documentazione del sistema di compilazione
|
|
||||||
automatica di Libreboot</a></li>
|
|
||||||
</ul>
|
|
||||||
<p>Dopo di che c’e’ da tenere seriamente in considerazione la
|
|
||||||
manutenzione della compilazione automatica (guarda sopra), e la
|
|
||||||
<em>documentazione</em>. La documentazione e’ critica in ogni
|
|
||||||
progetto.</p>
|
|
||||||
<p><em>Il supporto utente</em> e’ inoltre un fattore critico. Resta
|
|
||||||
collegato su IRC, e se hai sufficiente esperienza puoi aiutare qualcuno
|
|
||||||
in difficolta’ (o anche imparare insieme a loro), in questo modo sarai
|
|
||||||
di grande aiuto al progetto. Un sacco di persone chiedono inoltre aiuto
|
|
||||||
nel subreddit <code>r/libreboot</code>.</p>
|
|
||||||
<p>Puoi controllare l’elenco dei bugs sul <a
|
|
||||||
href="https://codeberg.org/libreboot/lbmk/issues">bug tracker</a>.</p>
|
|
||||||
<p>Se hai notato un difetto (bug) e hai trovato una soluzione, <a
|
|
||||||
href="git.html">qui puoi trovare istruzioni su come inviare delle
|
|
||||||
correzioni (patches)</a> o puoi semplicemente farne rapporto. Inoltre
|
|
||||||
tutto questo sito internet e’ scritto in Markdown e ospitato su un <a
|
|
||||||
href="https://codeberg.org/libreboot/lbwww">repository separato</a>,
|
|
||||||
dove puoi inviare correzioni (patches).</p>
|
|
||||||
<p>Qualunque discorso relativo a sviluppo e supporto utente viene fatto
|
|
||||||
sul canale IRC. Puoi avere piu’ informazioni sulla <a
|
|
||||||
href="contact.html">pagina dei contatti</a>.</p>
|
|
||||||
<h2 id="servono-traduzioni-per-libreboot.org">Servono traduzioni per
|
|
||||||
libreboot.org</h2>
|
|
||||||
<p>Libreboot attualmente ha pagine Web tradotte in Ucraino and Francese
|
|
||||||
(ma non ancora in ogni pagina e per ogni lingua).</p>
|
|
||||||
<p>Se vuoi essere d’aiuto con le traduzioni, puoi tradurre le pagine,
|
|
||||||
aggiornare traduzioni esistenti e condividere le tue versioni tradotte.
|
|
||||||
Per saperne di piu’ puoi leggere: <a href="news/translations.html">come
|
|
||||||
condividere traduzioni per libreboot.org</a></p>
|
|
||||||
<p>Anche se qualcuno sta gia’ lavorando sulle traduzioni in una
|
|
||||||
determinata lingua, possiamo sempre avvalerci di piu’ contributori. Piu’
|
|
||||||
siamo e meglio e’!</p>
|
|
||||||
<div id="footer">
|
|
||||||
<hr />
|
|
||||||
<ul>
|
|
||||||
<li><a href="/news/policy.html">Politica di riduzione di parti binarie
|
|
||||||
proprietarie (blobs)</a></li>
|
|
||||||
<li><a href="/git.de.html">Modifica questa pagina</a></li>
|
|
||||||
<li><a href="/who.de.html">Chi sviluppa Libreboot?</a></li>
|
|
||||||
<li><a href="/license.html">Licenza</a></li>
|
|
||||||
<li><a href="/template-license.html">Modelli di licenze</a></li>
|
|
||||||
<li><a href="/logo-license.html">Logo</a></li>
|
|
||||||
<li><a href="/contrib.html">Autori</a></li>
|
|
||||||
</ul>
|
|
||||||
<hr />
|
|
||||||
</div>
|
|
||||||
<p>Markdown file: <a href="https://libreboot.org/index.it.md"
|
|
||||||
class="uri">https://libreboot.org/index.it.md</a></p>
|
|
||||||
<p><a href="/sitemap.html">Site map</a></p>
|
|
||||||
<p>This HTML page was generated by the <a
|
|
||||||
href="https://untitled.vimuser.org/">untitled static site
|
|
||||||
generator</a>.</p>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue