thrilleratplay / coreboot-builder-scripts Goto Github PK

The path to the data vbt is incorrect after the x1 variant was added. May wait until v4.10

I simply cloned the repo 2 times and built, ./build.sh X230. The resuting images differ. diffoscope shows they differ quite significantly. 4 times the build-time is in there, but a large binary chunk difffers too. Why?

thanks.

Is it possible to add Thinkpad T420 support?
I have dumped the factory firmware of Thinkpad T420 and flashed coreboot. I am happy to assist with testing.

https://seabios.org/Releases#SeaBIOS_1.13.0

I am not sure if these scripts work in Powershell and Docker for Windows as I do not have a Windows machine to test them with.

Any volunteers?

The X220 should be able to update only the BIOS region with the ifd.

--ifd --image bios -N

I have a W541 currently running coreboot 4.15 and Tianocore. I need to stream line the process for mrc.bin

• Create SeaBIOS build
• Add unit tests

• Will likely have two branches, one for SeaBIOS and one for Tianocore
• Update unit tests to run for both versions

I never seem to remember to do this and am always seem to be too busy when coreboot does a release.

I created this a while ago and uploaded the GIMP file https://github.com/Thrilleratplay/bootsplash-coreboot

I just need to save it in a format and resolution that will work with libgfxinit. It is not a priority of mine at the moment so pull requests are welcome.

When running the script for x230, the build process stop at this step :

--2021-08-20 17:48:17--  https://mirror.fsf.org/trisquel/pool/main/t/tint/tint_0.04+nmu1.tar.gz
Resolving mirror.fsf.org (mirror.fsf.org)... 209.51.188.52, 2001:470:142:4::c
Connecting to mirror.fsf.org (mirror.fsf.org)|209.51.188.52|:443... connected.
HTTP request sent, awaiting response... 404 Not Found             
2021-08-20 17:48:18 ERROR 404: Not Found.
                                                                                                                                    
tar: tint_0.04+nmu1.tar.gz: Cannot open: No such file or directory 
tar: Error is not recoverable: exiting now                                                                                          
rm: cannot remove 'tint_0.04+nmu1.tar.gz': No such file or directory             
mv: cannot stat 'tint-0.04+nmu1': No such file or directory
make[1]: *** [Makefile:26: download] Error 1                                                                                        
make: *** [payloads/external/Makefile.inc:210: payloads/external/tint/tint/tint.elf] Error 2
Uh oh. Things did not go according to plan.   

The required file is apparently missing from the url.

Safeguard to prevent script from modifying original file.

I must be missing something, when I execute ./build.sh -i t430 I get a bunch of errors.

First time I ran build.sh it downloaded everything (i guess), and errored out (same error message).
When I run it now, I get this:

❯ pwd
/home/username/coreboot-builder-scripts

Beginning download of fc5b1b96829785ca28c8b211545b1ae5c73a4b53211021fd2410f2a6798776b0  coreboot-4.4-relnotes.txt...
unxz: (stdin): File format not recognized
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
unxz: (stdin): File format not recognized
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Downloading fc5b1b96829785ca28c8b211545b1ae5c73a4b53211021fd2410f2a6798776b0  coreboot-4.4-relnotes.txt complete
cp: cannot create regular file '/home/coreboot/cb_build/configs/defconfig': No such file or directory
Using default config
make: *** No rule to make target 'defconfig'.  Stop.
make: *** No rule to make target 'nconfig'.  Stop.
make: *** No targets specified and no makefile found.  Stop.
Uh oh. Things did not go according to plan.

Docker is installed and running. I'm on Arch.

Edit:
Apparently --bleeding-edge works. So something is wonky with the latest release.

This will require adding the stock rom

TODO:

• Make stock_bios directory read-only
• Fix black SeaBIOS screen before booting into Linux.
• Update flash.sh for x220

Add Wiki page

skeletons of these standard files:

• compile.sh
• flashrom.sh
• readme.md

This should be the same as the x220 but still need to test

This should be very similar to the x230 but I do not own one or have access to one for testing and maintaining an up to date config.

Intel's graphics driver will not on Windows without the blob and libgfxinit has a very limited resolution limit.

• Need a way to search and extract vga blobs
• Use romheader to test validity