Hi. I go through this tutorial:
https://doc.coreboot.org/tutorial/part1.html
I'm on Step 5 - Configure the build > Check your configuration (optional step):
I entered
$ make savedefconfig $ cat defconfig
I have changed my mind. Now I'd like to install SeaBIOS instead of coreinfo. What do I need to do? How do I change it?
Regards,
Bernd
Hello!
To change the payload to SeaBIOS instead of coreinfo, skip step 4, and in step 5 under "Select the payload" you would select SeaBIOS in the "Add a payload" menu, and then exit and build as usual. Then when you run qemu in step 8, you should see SeaBIOS instead of coreinfo.
Once you are familiar with that you could try building coreboot for your Thinkpad. To do that, first run "make distclean". Then, run "make menuconfig" (like step 5 in the part1 tutorial on doc.coreboot.org) and select Lenovo as the "Mainboard vendor", and the appropriate model in the "Mainboard model" menu. SeaBIOS should be the default payload, but you can check that in the Payloads menu. That will produce an image that should work on your hardware. I won't go into the details about flashing it, as I am not familiar with the exact process for your laptops and there are plenty of flashing tutorials available on the internet.
Also, feel free to join us on IRC (#coreboot on libera.chat). There you can more directly communicate with the coreboot community and likely will get answers sooner. If you aren't familiar with that, the easiest way is probably by going to https://web.libera.chat/, entering a nickname in the "Nick" box and "#coreboot" in the "Channel" box. You don't need to register, but you can if you would like to reserve your nickname.
Cheers, Nicholas
On Sun, Nov 7, 2021 at 11:35 PM bernd1-1@web.de bernd1-1@web.de wrote:
Hi. I go through this tutorial:
https://doc.coreboot.org/tutorial/part1.html
I'm on Step 5 - Configure the build > Check your configuration (optional step):
I entered
$ make savedefconfig $ cat defconfig
I have changed my mind. Now I'd like to install SeaBIOS instead of coreinfo. What do I need to do? How do I change it?
Regards,
Bernd _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
It's fine that there are more than 2 lines. In general, there would only be two lines if you configure coreboot exactly the same as in the tutorial (and even then there probably will be more than 2 lines, as was explained previously on another thread). Anything you do differently from the tutorial could add more lines. So once you configure it for real hardware, there will also be more lines.
Regards, Nicholas
Original Message
From: bernd1-1@web.de Sent: November 8, 2021 2:43 a.m. To: nic.c3.14@gmail.com Cc: coreboot@coreboot.org Subject: AW:AW:[coreboot] Re: Installing coreboot with SeaBIOS
Hi. I'm with "Check your configuration (optional step):".
I did
$ make savedefconfig $ cat defconfig
The instructions say:
"There should only be two lines (or 3 if you’re using the system toolchain):
CONFIG_PAYLOAD_ELF=y CONFIG_PAYLOAD_FILE="payloads/coreinfo/build/coreinfo.elf""
I wasn't using the system toolchain. It's clear I installed SeaBIOS instead of coreinfo.
I got the following response:
CONFIG_CBFS_SIZE=0x00040000 CONFIG_CONSOLE_CBMEM_BUFFER_SIZE=0x20000 CONFIG_UART_PCI_ADDR=0x0 CONFIG_SUBSYSTEM_VENDOR_ID=0x0000 CONFIG_SUBSYSTEM_DEVICE_ID=0x0000 CONFIG_CONSOLE_QEMU_DEBUGCON_PORT=0x402 CONFIG_POST_IO_PORT=0x80 CONFIG_SEABIOS_DEBUG_LEVEL=-1
I've already asked the corresponding question regarding coreinfo but is it the same with SeaBIOS:
Is it a problem that there are 8 lines instead of only two lines? Do I need to fix anything or could I just continue?
Regards,
Bernd
On 08.11.21 19:15, bernd1-1@web.de wrote:
Hi. Is the SeaBIOS payload open source, actually?
Yes.
I have looked for SeaBIOS on Wikipedia but it has no entry of its own.
Please look closer [1].
Nico
Hi,
Are the errors a problem and do I need to do something? Can I proceed?
Yes of course, they're *errors* after all. Look here:
/bin/sh: 1: python: not found make[2]: *** [Makefile:168: out/romlayout16.lds] Error 127 make[1]: *** [Makefile:84: build] Error 2 make: *** [payloads/external/Makefile.inc:65: payloads/external/SeaBIOS/seabios/out/bios.bin.elf] Error 2
In the first line it says it could not found python on your system. So, install python and try building again by running `make clean` followed by `make`.
No offense, but you may be better off with buying some device which has coreboot pre-installed (if that's what you want). For a list of vendors who sell devices with coreboot/SeaBIOS pre-installed, look at the section "Consumer platforms" at the bottom here: https://coreboot.org/users.html
If you want to proceed with doing it yourself, be prepared that it will take some time (several weeks+) and that you will have to learn a lot.
Good luck!
Merlin
bernd1-1@web.de wrote:
/bin/sh: 1: python: not found make[2]: *** [Makefile:168: out/romlayout16.lds] Error 127
It's unfortunate that SeaBIOS requires python to build, but keep it up, you're not far away.
Merlin Büge wrote:
If you want to proceed with doing it yourself, be prepared that it will take some time (several weeks+) and that you will have to learn a lot.
I hope Bernd does proceed and the first success shouldn't be too long now. It's a great feeling to have a machine (virtual or otherwise) boot self-built firmware! :)
Hang in there
//Peter
Hi Peter and Piotr,
thank you for your replies. Maybe I misunderstood what Bernd is trying to achieve. If so, I'm sorry.
Generally, I very much encourage people to play around with FW/HW/SW and to learn how (seemingly) complex stuff works. However, it sounded to me that Bernd was actually wanting/needing a computer system which is "more secure": They asked for "step to step instructions" in their first mail, and said "this entire topic is extremely sensitive, for the moment I'd prefer not to reveal my identity". "More secure" is obviously a relative term and will mean different things for different people or different threat models.
If you want to harden your firmware via coreboot and make it more secure than the stock firmware, you have to learn how things work on a deeper level, which would take *more* than a few days if you are a complete beginner (like Bernd seems to be, at least to me). The alternative would be to buy something with coreboot pre-installed like Chromebooks, which has some tradeoffs I guess (for security, understanding how things work is very valuable and almost a prerequisite I guess) - but it's much faster, it does not take several weeks+.
After reading my last mail again I think it sounds a little unfriendly, that was not my intend. Also let me clarify regarding the previous paragraph: There is obviously not anything wrong with being a beginner! We all were beginners at some point. (Actually, learning more about firmware often makes me feel even more like a beginner :D) It is not meant to sound insulting or offending in any way.
It was just my impression that Bernd is looking for something which I thought just compiling+flashing coreboot could not provide, so I wanted to prevent them from "going down the wrong rabbit hole".
On Tue, 9 Nov 2021 18:22:40 +0000, Peter Stuge wrote:
I hope Bernd does proceed and the first success shouldn't be too long now. It's a great feeling to have a machine (virtual or otherwise) boot self-built firmware! :)
Btw I forgot about the VM. I was just thinking about HW-flashing the X220.
Regards,
Merlin
Hang in there
//Peter _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
On Tue, Nov 09, 2021 at 06:57:10PM +0100, Merlin Büge wrote:
No offense, but you may be better off with buying some device which has coreboot pre-installed (if that's what you want). For a list of vendors who sell devices with coreboot/SeaBIOS pre-installed, look at the section "Consumer platforms" at the bottom here: https://coreboot.org/users.html
If you want to proceed with doing it yourself, be prepared that it will take some time (several weeks+) and that you will have to learn a lot.
Please stop. I've done my first coreboot with some minor issues in few days. Then one thing led to another and I've made small contribution to coreboot git repo. With almost zero knowledge about low level hardware things like this before my first real build.
Building coreboot, diving inside - it was a great trip. :) When I have some spare time I'm going back!
"Just buy the hardware" is just sad advice. It hurts my eyes.
No offence, just my 2 cents. :)
Keep going Bernd!
Best regards, Piotr Szymaniak.
On Wed, Nov 10, 2021 at 2:05 AM bernd1-1@web.de bernd1-1@web.de wrote:
I see something like:
The command 'qemu-system-x86_64' wasn't found, but can be installed with: sudo apt install qemu-system-x86 # version 1:4.2-3ubuntu6.18, or sudo apt install qemu-system-x86-xen # version 1:4.2-3ubuntu6.18
Well, the message says the command wasn't found, and that qemu-system-x86_64 needs to be installed. I would use the first one, "sudo apt install qemu-system-x86". After that qemu should work and hopefully you'll see SeaBIOS once it starts up. You're almost there!
Nicholas
On Sat, Nov 13, 2021 at 2:02 AM bernd1-1@web.de bernd1-1@web.de wrote:
Hi. I did "make distclean" and "make menuconfig". I've set the "Mainboard vendor" to Lenovo and the "Mainboard model" to X220.
"SeaBIOS should be the default payload, but you can check that in the Payloads menu."
I see the following in the Payloads menu:
... Add a payload (SeaBIOS) ---> SeaBIOS version (1.14.0) ---> ...
Is SeaBIOS the default payload?
Do I need to do
$ make
again after making changes?
Yes, that looks correct. SeaBIOS is set to the payload, so you should just be able to exit menuconfig and then run make
Regards, Nicholas
On Sat, Nov 13, 2021 at 12:03 PM bernd1-1@web.de bernd1-1@web.de wrote:
Built lenovo/x220 (ThinkPad X220) ** WARNING ** coreboot has been built without an Intel Firmware Descriptor. Never write a complete coreboot.rom without an IFD to your board's flash chip! You can use flashrom's IFD or layout parameters to flash only to the BIOS region.
Obviously it accepted the Lenovo ThinkPad X220 mainboard settings but what does that warning mean? Is there something to do about it?
This warning just means you shouldn't flash the entire coreboot.rom image to your motherboard. You can safely ignore it, as long as you add the option "--ifd -i bios" when programming the bios flash chip using flashrom and an external programmer.
Regards, Nicholas
On Sat, Nov 13, 2021 at 12:41 PM bernd1-1@web.de bernd1-1@web.de wrote:
Should I test the image with QEMU once again?
coreboot is board specific, a rom built for the X220 will only run on an actual X220, and will not run on QEMU. Only a rom built for QEMU will run on QEMU.
Regards, Nicholas
You should back up your chip before you flash anything new. And have another functional computer while you do this so that you can get online. If something doesn't work, get on the IRC channel.
On Sat, Nov 13, 2021 at 12:03 PM Nicholas nic.c3.14@gmail.com wrote:
On Sat, Nov 13, 2021 at 12:41 PM bernd1-1@web.de bernd1-1@web.de wrote:
Should I test the image with QEMU once again?
coreboot is board specific, a rom built for the X220 will only run on an actual X220, and will not run on QEMU. Only a rom built for QEMU will run on QEMU.
Regards, Nicholas _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
On Sun, Nov 21, 2021 at 7:46 AM bernd1-1@web.de bernd1-1@web.de wrote:
Hi. I'd like to backup the chip of my ThinkPad X220 (notebook) and afterwards flash coreboot with SeaBIOS. I don't want to use a Raspberry Pi. I've got an old laptop. Which items could I use for reading/writing?
Hello again,
First, you need a programming clip to connect to the actual BIOS chip, regardless of the actual programmer you use. You can usually find them under the names "SOIC8 clip" or "Pomona clip" [1][2]. The Pomona ones are blue and are supposedly higher quality, and have pins on the end of the clip to connect jumper wires. Cheaper clips typically have black plastic, and may or may not have wires already connected to them. The ones without wires have pins on the end of them like the Pomona ones, but the spacing is narrower and likely won't fit all the jumper wires.
Next you need a programmer to actually communicate with the BIOS chip to read/write it. The "CJMCU-2232H" [3] has previously been suggested as a good choice, as it does not require as much configuration as other solutions like a Raspberry Pi or STM32. Many of them seem to have unsoldered pin headers, so you either need to have the ability to solder them on yourself, get someone to solder it for you, or find a version with the headers already soldered on.
You will also need some jumper wires to connect the clip to the programmer. These can be found under the name "dupont wire" [4]. Many of these sets come with male to male (pins on both ends), male to female (pin on one end and a socket on the other) and female to female (sockets on both ends). Depending on the actual programmer and clip you buy, the type of wires you actually need might be different, but it will likely be female to female or possibly female to male.
As a brief overview of how everything would be connected, the 2232h board would connect to your old laptop over usb, then the board would connect to the clip using the jumper wires, and the clip would connect to the flash chip on your X220. Then you would use the flashrom program (should be available on any Linux distribution) on your old laptop to backup the flash chip on the X220 and then write the coreboot rom onto it.
If you are unsure of whether a specific product listing would work, feel free to ask on IRC or this mailing list thread with the links.
Regards, Nicholas
Here are some listings for the items mentioned above, but consider these as more of a reference of what they look like and feel free to look at other sites/stores for similar products [1] https://www.amazon.com/XLX-Motherboard-Universal-Connector-Programmer/dp/B08... [2] https://www.amazon.com/Pomona-Electronics-5250-Plated-Spacing/dp/B00JJ4G13I/ [3] https://www.amazon.com/FT2232HL-Module-Channel-RS232-CJMCU-2232HL/dp/B07Q4K3... [4] https://www.amazon.com/Yueton-Multicolored-Female-Breadboard-Jumper/dp/B01DD...
On Sun, Dec 5, 2021 at 12:55 PM bernd1-1@web.de bernd1-1@web.de wrote:
https://www.electronicloop.de/Original-Pomona-SOIC8-SOP8-Chip-IC-Test-Clip-A... https://www.conrad.de/de/p/joy-it-1717242-raspberry-pi-usb-hub-interface-kon...
I took a look at these, and the clip should work. However, I found a datasheet for that programmer [1], and there does not seem to be any pins which can act as a 3.3V supply, which is required. There might be ways around that [2], but I don't know for sure if that method will work on the X220. So that programmer may not be ideal.
It seems the connection of the jumper wire, that's going to be connected with the programmer, needs to be female (socket) because the programmer seems to have a male connection (pins) with the pin header already soldered on. I can't see on the pictures, whether the jumper wire really has got a female connection there. I also can't see, whether the boards shipped with the clip/wire, that fit to the jumper wire, have got female connections. Do you think I need an adapter and generally, is this equipment sufficient or do I need anything else, for example a USB extension cable?
Reading the description of that clip, it looks like it ships with those extra boards as well as the wires. Based on the connections on the clip and the boards, the wires are female to female, but the connectors on the ends of the wires appear to be connected together in 2 blocks of 4. They should be separate in order to connect each wire to the correct pin on the programmer. So if you get that clip, you would still need to get separate female to female jumper wires.
For the programmer that you linked, a USB extension cable would likely be needed, as the way USB ports are typically oriented on laptops means that the pins on the programmer would face the table, making it difficult to connect anything to it. However, that may not be needed for other programmers depending on the way the pins are soldered on.
Regards, Nicholas
[1] http://www.ftdichip.com/Support/Documents/DataSheets/Modules/DS_USB_HI-SPEED... [2] https://doc.coreboot.org/flash_tutorial/no_ext_power.html
Hello Bernd,
On 16.01.22 11:09, bernd1-1@web.de wrote:
... "other solutions like a Raspberry Pi or STM32." ...
Is the STM32 a board like the CJMCU-2232H which has a USB connection and a pin header and that's attached to a second computer via USB and to the programming clip via jumper wires?
STM32 is actually a whole family of microcontrollers. In this context, likely a blue-pill board was meant (e.g. [1]). As mentioned, this requires more effort to set up. You need to solder the pin headers and you need another device to program a flashrom-compatible firmware[2] to it. For the programming, you need a TTL-level (3.3V!) UART. For instance, a USB adapter, or the UART of an RPi.
There are also other STM32 boards that work with this firmware. But the blue-pill is the famous/cheap one.
If a Raspberry Pi is used, is it both the second computer and the programmer all in one or is a second computer or a programmer still needed?
It can act as the second computer, you just need a keyboard and screen I suppose. flashrom works well on the RPi. Usually you can just install it with your package manager.
Nico
[1] https://www.ebay.de/itm/144350056565 [2] https://github.com/dword1511/stm32-vserprog
On 16.01.22 18:16, bernd1-1@web.de wrote:
Hello Nico,
... "It can act as the second computer, you just need a keyboard and screen I suppose. flashrom works well on the RPi. Usually you can just install it with your package manager." ...
Is a Raspberry Pi with keyboard, screen and jumper wires and a programming clip enough hardware to flash the ROM to the chip of my ThinkPad or is anything else necessary?
Depends on your ThinkPad model, usually yes if the clip fits the chip, the wires fit the clip and aren't too long, and you have PSUs to power everything.
Nico
On Sun, Jan 16, 2022 at 06:43:42PM +0100, bernd1-1@web.de wrote:
It's a ThinkPad X220 (notebook version, not tablet version).
The X200 may not be quite the same as the X220, but this guide should at least give you *some* idea of what's involved, on the hardware side.
https://libreboot.org/docs/install/x200_external.html
What are PSUs?
Power Supply Units. In the case of battery-powered devices like phones or laptops, these may also be called "chargers".
PSUs for computers typically take mains voltage (220V AC, for example) and convert it to the relevant DC voltage.
Your X220 probably has something like a 20V DC PSU.
Most Raspberry Pis need 5V PSUs, same as most Android phones.
If you use an external monitor for the Raspberry Pi, instead of SSHing into it, then you might need a PSU for that monitor - although these days, most LCD monitors have internal PSUs and so just need a mains cable.
I must say, if you are unsure what a PSU is, then I would recommend reading some basic electronics textbooks - and familiarising yourself with the dangers of using incorrect voltages or polarities, the dangers of static discharge, and the dangers of electrocution - before you attempt to do anything relatively advanced and delicate like flashing the ROM chip of an X220. Using a PSU improperly could brick your laptop, start a fire, or worse.
So, please take time to understand the principles well first of all. Then, after that, you would stand a better chance of doing a good job of flashing your laptop.
On 18.01.22 10:40, bernd1-1@web.de wrote:
"Depends on your ThinkPad model, usually yes if the clip fits the chip, the wires fit the clip and aren't too long, and you have PSUs to power everything."
It's a ThinkPad X220 (notebook version, not tablet version). Let's provide that the clip fits the chip, the wires fit the clip and I have PSUs to power everything.
You're lucky. The X220 is a rather easy target.
How long may the wires be?
10 to 20cm works well. Sometimes shorter is better, but the X220 shouldn't make you any trouble. So I'd rather choose cables that don't make handling of the clip too inconvenient.
Nico
On Tue, Jan 18, 2022 at 12:21:24PM +0100, Nico Huber wrote:
On 18.01.22 10:40, bernd1-1@web.de wrote:
How long may the wires be?
10 to 20cm works well. Sometimes shorter is better, but the X220 shouldn't make you any trouble. So I'd rather choose cables that don't make handling of the clip too inconvenient.
Nico is right about convenience.
Still, I experienced inconsistent reads almost every time I used 20cm wires. (Yes, I checked the wires and the clip for resistivity or loose connections, etc.)
I experienced almost no inconsistent reads with 10cm wires.
When I shielded the 10cm wires with earthed aluminium foil, I got entirely consistent reads. Unfortunately, this is much less convenient to handle than unshielded 20cm leads.
Your luck may depend on how electrically noisy your environment is.
Hi Bernd,
On 18.01.22 14:41, bernd1-1@web.de wrote:
So, after having made clear the corresponding points do you think that the following hardware will be sufficient to flash the coreboot/SeaBIOS ROM to the chip of my ThinkPad X220 (notebook version, not tablet version):
Raspberry Pi with keyboard and screen Pomona or SOIC8 programming clip 8 jumper wires/dupont wires that fit the clip 10 to 20 cm each PSUs to power everything
tl;dr Go!
If you want to be 100% sure, you should open your ThinkPad and check that your BIOS flash is indeed in a SOIC-8 package, and that there is only a single flash chip. In theory it can be different, but so far people have only encountered a single SOIC-8 chip, AFAICT.
Minor corrections: Pomona is the name of the manufacturer (of the better clips). You only need 6 wires; /HOLD and /WP pins of the flash are already properly connected by the mainboard.
Nico
bernd1-1@web.de wrote:
... "tl;dr Go!" ...
TL;DR is short for "Too Long; Didn't Read", sometimes used to place the most important message at the very top for limited capacity readers.
... "AFAICT" ...
"As Far As I Can Tell"
Should I use this tutorial, that applies to the ThinkPad X200 where I got a ThinkPad X220, for opening the housing and figuring out what screws to open in order to get access to the chip or is there one for the ThinkPad X220, too
The hardware is not identical but will probably be similar-ish. The official X220 Hardware Maintenance Manual by Lenovo is available here:
https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/0a60739_04.pdf
Chapter 8 on Page 67 is where disassembly starts, you eventually want to complete the first step of 1120 "Removal steps of system board" but quite possibly you don't actually need to perform every single step before even though the manual says so, in particular I doubt that you actually have to remove the LCD assembly.
It's also possible that you don't need to remove the system board from the case at all, to access the flash chip. It depends on which side of the system board it is mounted on and I unfortunately don't know. If you're lucky it's on the top side of the board and you only have to go through step 1090 to remove the keyboard bezel.
You may have to experiment to get to know your X220. It might take up to a full day but hang in there, it's a great learning experience.
Keep in mind that the maintenance manual will never mention the BIOS flash because Lenovo does not intend for anyone to do component level work on the system. Their technicians must only ever consider the system board as a whole, quite wasteful btw.
You can of course compare the maintenance manual both to the X200 instructions on the web page and to your actual hardware to figure out how much overlap there is, either beforehand or as you go.
Take all the blahblah about having to be trained and certified and whatnot with a grain of salt. It's your hardware, you can do what you want with it, and taking it apart is highly admirable!
Viel Erfolg and in case you get stuck you can always ask questions.
Kind regards
//Peter
Hi Bernd,
bernd1-1@web.de wrote:
I performed the steps â1010 Battery packâ, â1040 Keyboardâ, â1050 Palm rest or palm rest with a fingerprint readerâ and after that "1090 Keyboard bezel". I see what's on the attached image. That's the upper side where the keyboard was before.
Excellent progress! Well done.
How should I continue to get access to the flash chip?
I didn't know the board so I searched and found someone who has documented exactly the process that you are going through with photos:
https://szclsya.me/posts/coreboot/x220/#headline-4
Great news: No need to disassemble the machine any further! The flash chip is on the top side of the mainboard, under the black plastic film next to the Expresscard slot.
Kind regards
//Peter
Peter Stuge wrote:
How should I continue to get access to the flash chip?
I didn't know the board so I searched and found someone who has documented exactly the process that you are going through with photos:
Turns out www.coreboot.org also has some documentation and photos. :)
https://www.coreboot.org/Board:lenovo/x220 https://www.coreboot.org/File:X220_flash_chip.jpg https://www.coreboot.org/File:X220_clip.jpg
//Peter
[This](https://www.amazon.com/gp/product/B07R5LPTYM/) had everything I needed to read/write the flash on my T430.
On Sun, Nov 21, 2021 at 2:33 PM Sven Semmler Sven@svensemmler.org wrote:
[This](https://www.amazon.com/gp/product/B07R5LPTYM/) had everything I needed to read/write the flash on my T430. _______________________________________________
This is also an option, but there is a chance that such programmers (the CH341A) will output 5V (which may cause damage to the system) instead of 3.3V and will need to be modified to output the correct voltage.
Hi. When installing python I did:
$ apt-get install python or $ sudo apt-get install python
I don't remember.
So if I got it right maybe I've installed the wrong python version.
Anyway, I see the output (probably of coreboot) in the original terminal window and the output (probably of SeaBIOS) in an additional QEMU window. I assume that the boot process is simulated. It seems to try booting from CD/DVD (which isn't built-in) and Floppy (also not built-in) and hard disk. It doesn't seem to work and it doesn't startup. I'm in a loop.
QEMU says:
No bootable devive. Retrying in 60 seconds.
It tries to boot each 60 seconds.
Is that due to the (possibly wrong) python version or what's the reason? What do I need to do?
If you need the precise output either of the terminal or the QEMU window, please let me know.
Regards,
Bernd
On Wed, Nov 10, 2021 at 11:39 AM bernd1-1@web.de bernd1-1@web.de wrote:
So if I got it right maybe I've installed the wrong python version.
Since coreboot did seem to build, I believe you installed the correct version. I don't believe SeaBIOS requires python to actually run, only to compile.
Anyway, I see the output (probably of coreboot) in the original terminal window and the output (probably of SeaBIOS) in an additional QEMU window. I assume that the boot process is simulated. It seems to try booting from CD/DVD (which isn't built-in) and Floppy (also not built-in) and hard disk. It doesn't seem to work and it doesn't startup. I'm in a loop.
QEMU says:
No bootable devive. Retrying in 60 seconds.
It tries to boot each 60 seconds.
Is that due to the (possibly wrong) python version or what's the reason? What do I need to do?
Congratulations, you've built coreboot (for QEMU) with the SeaBIOS payload! That output is expected, as there isn't anything to boot from. QEMU emulates an entire computer, and the command listed in the tutorial does not include a virtual hard drive, floppy disk, disk drive, or anything else, so there isn't anything it could possibly boot from. So you didn't do anything wrong, and python doesn't have anything to do with it.
If you want to see it start something up, one way would be to add a secondary payload to the coreboot image (It's also a good way to experiment and gain experience with the build system). That will add a second payload alongside SeaBIOS. Run "make menuconfig" again, select the "Payloads" menu, select the "Secondary payloads" menu, then select any one of the options in there (tint is probably the most interesting, it's a Tetris like game), and then exit selecting "yes" at the end to save the config.
Then run "make" again to rebuild the image, then run the same QEMU command as in step 8 in the tutorial. When QEMU starts you should see a prompt that says "Press ESC for boot menu", and when you hit escape, you should be presented with a menu to select the boot menu. Type the appropriate number to select the secondary payload that you added, and something should come up.
Another thing you could do is to download an install ISO for some Linux distro (if you don't already have one handy), saving it in the the directory where coreboot is located, and then running a command like this:
$ qemu-system-x86_64 -bios build/coreboot.rom -serial stdio -cdrom linux.iso
replacing "linux.iso" with the actual name of the iso.
Once you feel comfortable with the build system feel free to try and move on and build coreboot for your actual hardware; I believe I outlined some steps to do that in a previous email.
Regards, Nicholas
-
bernd1-1＠web.de -
Merlin Büge -
Nicholas -
Nico Huber -
Peter Stuge -
Piotr Szymaniak -
Prasun Gera -
Sam Kuper -
Sam Kuper -
Sven Semmler