File site/news/libreboot20241206.md changed (mode: 100644) (index 647f1e7..49ff590) |
... |
... |
for reading, and have a wonderful day! |
353 |
353 |
Revisions |
Revisions |
354 |
354 |
========= |
========= |
355 |
355 |
|
|
|
356 |
|
Occasionally, stable releases such as this one may contain minor (or critical) |
|
357 |
|
issues that went unnoticed during testing. When this occurs, critical or |
|
358 |
|
otherwise desirable fixes are implemented, while not fundamentally altering |
|
359 |
|
the substance of the original release. |
|
360 |
|
|
|
361 |
|
When this occurs, the ROM image and source code archives are entirely re-built, |
|
362 |
|
and re-uploaded, replacing the old one. Patch files are provided alongside the |
|
363 |
|
updated source archive, so that you can revert (from it) back to the older |
|
364 |
|
revisions if you wish; by doing this, you can therefore also re-create the |
|
365 |
|
original release archive, for reference. |
|
366 |
|
|
356 |
367 |
Revision 1 |
Revision 1 |
357 |
368 |
---------- |
---------- |
358 |
369 |
|
|
|
... |
... |
which manifested during S3 resume, but that bug never made it into the release |
412 |
423 |
because it was fixed *before* the initial release of Libreboot 20241206. |
because it was fixed *before* the initial release of Libreboot 20241206. |
413 |
424 |
|
|
414 |
425 |
The ROM images were all re-uploaded, compiled from the rev3 tarball, because it was discovered that the rev2 tarballs had a GRUB built showing the old Libreboot 20241008 version number; the actual code in GRUB matched the code for 20241206, but it was a cached GRUB build from just before updating the version number for release. This is because the rev2 ROM image tarballs were done manually, to avoid a full re-build of every target in lbmk. To avoid all doubt, all ROM images have been re-compiled with the version number corrected, from the rev3 tag. |
The ROM images were all re-uploaded, compiled from the rev3 tarball, because it was discovered that the rev2 tarballs had a GRUB built showing the old Libreboot 20241008 version number; the actual code in GRUB matched the code for 20241206, but it was a cached GRUB build from just before updating the version number for release. This is because the rev2 ROM image tarballs were done manually, to avoid a full re-build of every target in lbmk. To avoid all doubt, all ROM images have been re-compiled with the version number corrected, from the rev3 tag. |
|
426 |
|
|
|
427 |
|
Revision 4 |
|
428 |
|
---------- |
|
429 |
|
|
|
430 |
|
All current ROM/src archives in this release match changes up to rev4. |
|
431 |
|
|
|
432 |
|
Rev4 fixed a bug: GRUB was not allowing the background image to be changed, |
|
433 |
|
despite rules in `grub.cfg` that made one in CBFS load before memdisk. This fix |
|
434 |
|
was implemented by no longer inserting background images into GRUB's memdisk, |
|
435 |
|
instead inserting them into CBFS. |
|
436 |
|
|
|
437 |
|
This way, you can remove what's in CBFS and replace it with your own, if that's |
|
438 |
|
what you want to do. |
|
439 |
|
|
|
440 |
|
To celebrate this fix, the default background logo was also changed. The old |
|
441 |
|
one was a white silhouette of the Libreboot logo, whereas the new one is of |
|
442 |
|
the same shape but shoes a rainbow-coloured gradient instead of all-white. This |
|
443 |
|
rainbow logo was also used in U-Boot on the very initial Libreboot 20241206 |
|
444 |
|
release, and it's also used for the main website logo at the time of this |
|
445 |
|
revision. |
|
446 |
|
|
|
447 |
|
Basically, this fix was done as an excuse just to do another revision update, |
|
448 |
|
to change the logo! The actual bug was actually quite minor and irrelevant. |