Support: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 9: | Line 9: | ||
** If your chipset is supported, check out the SuperIO with [[Superiotool]] | ** If your chipset is supported, check out the SuperIO with [[Superiotool]] | ||
** Look for a board that has the same chipset and the same SuperIO and start from there. Make sure you have a backup solution in place to recover if something goes wrong. You can not use your vendor bios' recovery bootblock to do this. | ** Look for a board that has the same chipset and the same SuperIO and start from there. Make sure you have a backup solution in place to recover if something goes wrong. You can not use your vendor bios' recovery bootblock to do this. | ||
** See the [[Developer Manual]] for further information. | |||
= More Resources = | = More Resources = | ||
* [[Laptop]] page with some information on data gathering. | * [[Laptop]] page with some information on data gathering. |
Latest revision as of 00:55, 4 June 2011
Is my mainboard supported?
There are several steps involved in finding out whether your mainboard is supported by coreboot, or if it would be easy to support.
- First, check the Supported Motherboards. If your mainboard is in this list, you are lucky and you will be able to try coreboot.
- If your mainboard is not mentioned here, you will have to know how to code C in order to proceed. If you don't, refrain from trying to get coreboot onto your system.
- Next, you will have to do a lot of data gathering:
- Check out your mainboard's chipset. Use lspci on Linux/*BSD to do this. Look at the host bridge and at the LPC bridge. If you find those in our list of Supported Chipsets and Devices a port might be easy.
- If your chipset is supported, check out the SuperIO with Superiotool
- Look for a board that has the same chipset and the same SuperIO and start from there. Make sure you have a backup solution in place to recover if something goes wrong. You can not use your vendor bios' recovery bootblock to do this.
- See the Developer Manual for further information.
More Resources
- Laptop page with some information on data gathering.