[coreboot] Will coreboot work on my Asus P5G41-M?

2016-01-18 Thread Vicente Herrera Cobo
Hi, the FAQ explicitly asked to send information about currently unsupported motherboard. https://www.coreboot.org/FAQ#Will_coreboot_work_on_my_machine.3F 1. Asus P5G41-M. Intel Core 2 Duo E7600 @ 3.06GHz. Northbridge G41. Southbridge ICH7. 2. lspci -tvnn. See lspci.txt attached. 3. Super I/O

Re: [coreboot] steps before screen mods

2016-01-18 Thread kitestramuort
> Hi guys, > > I just came across thinkpad forum thread where people are discuss  about > hardware mods for getting FHD screen on lenovo x220/x230 laptops. > http://forum.thinkpads.com/viewtopic.php?f=43=106919=90 > > What do you guys think, will this affect coreboot at all? Are there any >

Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP

2016-01-18 Thread Patrick Georgi via coreboot
2016-01-18 21:34 GMT+01:00 Ben Gardner : > Is there a work-around for this? For example, is there an option to > pad the FMAP out to 4 KB? The workaround is indeed to increase the FMAP region's size to 4K. To do this, edit $(top)/Makefile.inc, line 708 (since you're on x86,

Re: [coreboot] cbfstool: CBFS alignment broken due to FMAP

2016-01-18 Thread Ben Gardner
Thank you. That worked. On Mon, Jan 18, 2016 at 2:46 PM, Patrick Georgi wrote: > 2016-01-18 21:34 GMT+01:00 Ben Gardner : >> Is there a work-around for this? For example, is there an option to >> pad the FMAP out to 4 KB? > The workaround is indeed to

[coreboot] cbfstool: CBFS alignment broken due to FMAP

2016-01-18 Thread Ben Gardner
Hi all, With the latest cbfstool in master, the alignment option is broken in cbfstool. Or rather, the alignment is relative to the CBFS start, not the actual ROM address, and the 256-byte FMAP throws off the alignment. In my case, I have a ROM size of 16 MB and the BIOS region starts at