-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi @ all,
is there a Coroboot for the Lenovo T410 Laptop?
Greetings
Alex Veek
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iF4EAREIAAYFAlNxKzsACgkQ53cWmi2XuzOOXAD8CNLPoycJNftQzeHnMQbl8ZG9
4y2SPIHwLota1/Gsfm0BAJzhG2M+MKXDBJgazHjt/HM2DyAeHi6S24sGcwd1W2GN
=sFKM
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
After reviewing some of the comments on the ASUS KGPE-D16 being
essentially too large of a system and too expensive for many people, and
the fact that modern, blob-free systems are not really available in the
mid-range arena, Raptor Engineering would like to offer to create a
native initalization blob-free port for the ASUS KCMA-D8, which is
essentially the KGPE-D16's ATX-compatible "little brother".
We would be asking $15,000 for the port, including upstreaming to the
master coreboot tree. We already have extensive experience with these
Family 10h/15h boards, and would be able to create a port of similar
quality to the existing KGPE-D16 source in terms of both code quality
and overall functionality.
If this is something you might be interested in please let me know. We
are able to accept multiple payments from various sources for the same
project (within limits), so if this is something your local Linux groups
or similar might be interested in we should be able to keep the cost on
any one individual or organization to a reasonable level.
Thank you for your consideration,
- --
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
http://www.raptorengineeringinc.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJWQROpAAoJEK+E3vEXDOFbR2cH/3FTqGFH+cU/HVrBUPcoKjii
h9OC7SGeXdyoLZvob/YayG+g47Yppkg2um4pAC7dmGl/OXtkGh13hlsrQ8BNiYcz
g0kQUdNKYh9dmBC3YnlxU6a7psh473TdyuLILrl7/8WgI8DZnRtjy62Oo5k6XAKW
jfYb/bGC8I3tArYrgQDmFxz2dOejuTZit56I+mbWNtvbuQov2BDmrPPMLRuEvG3M
QHCAo/Pjaajzl4rmtrgu0GHcxHsgAnJcnrcPkFYeSDKt7QxSTNOB6NqhcnYdh1SY
RiA5Z/3enuDs+XNhS+6qMeKOcrEuf+Ccs7sGsgq5tWm20JA+bBoByvrXhHqVUxU=
=DKfR
-----END PGP SIGNATURE-----
Hi Iru,
we aren't still sure which boards use Intel Boot Guard and which doesn't use it. But we expect most board use it,
because it's "recommended" by intel - as we dont recommend it.
Also there isn't yet a test script for Intel Boot Guard.
Can you post a link to that forum post?
I would like to look into a x240 flash image. If you have such board it would be nice
if you can send me a copy of the flash image via private mail.
Cheers,
lynxis
--
Alexander Couzens
mail: lynxis(a)fe80.eu
jabber: lynxis(a)jabber.ccc.de
mobile: +4915123277221
Hi,
we obviously want to participate in FOSDEM.
https://fosdem.org/2016/news/2015-09-24-call-for-participation/
ACT NOW!
Some deadlines already expired. Some can still be managed.
Main track talks: Deadline 2015-10-30 (10 days left)
One hour of entertainment, huge audience.
Anyone up for the challenge?
Stands: Deadline 2015-11-13 (24 days left)
I can send in the proposal if I'm not going to be alone there.
How many tables do we want for our stand/booth(s)?
Who is coming?
Lightning talks: Deadline 2015-11-27 (38 days left)
Short and to the point. Your 15-minute elevator pitch.
Can you sell the project?
All deadlines are at 23.59 UTC
Developer room proposal: Deadline EXPIRED
Maybe some developer room will accept talks/demos from us.
Regards,
Carl-Daniel
Hello,
I have just started playing with coreboot and BIOS flashing, so
please forgive the noobness. I recently acquired an HP Pavilion
M6-1035dx to install coreboot as mentioned in the wiki. I made a few
noob mistakes along the way. First, I wiped the hard drive entirely
and installed Linux to try running flashrom from the native OS (hence
any factory recovery partition has been wiped). Second, I built a
coreboot.rom image without using the supplied .config file from the
wiki. I just used a vanilla configuration, which didn't work at all,
not surprisingly.
Once I found the right config settings, I realized that I never backed
up the stock BIOS ROM or extracted any option ROMs. This is where I
gave my forehead a good slap. Now, I'm able to build a semi-working
coreboot ROM that I can flash via ISP and a R-Pi. I can tell that it
almost works because the system seems to boot fine, and I can see the
hostname in the router. I would probably even be able to SSH in if I
had enabled sshd before the goof-up. The only (fatal) problem is that
the screen is completely blank. No VGA support, obviously.
So, I'm convinced that if I had the right VGA BIOS option ROM, I could
probably get it to work as desired. I've tried to restore a stock
vendor bios rom to extract the vga bios from, but since I wiped the
hard drive and since I no longer have DVD support via coreboot, I cannot
seem to restore the stock bios rom from the HP site in any reasonable
way. I've tried flashing it via flashrom, and I've also tried extracting
the contents of the stock rom with no luck.
Does anyone here have any pointers or ideas that I could try? Or
perhaps someone has the right rom file laying around they could
kindly share? I've scoured all over the net, and the best I could
find was a mention in the config file of including
"1035_dxvgabios.bin", which seems to have been extracted locally. I'm
stumped at this point. Any advice would be greatly appreciated.
much thanks,
-kr
Hi all,
unfortunately autoport didn't work well.
This is the output on the 1st run:
Unsupported PCI device 8086:1e56
Unknown PCI device 8086:0085, assuming removable
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x20 pc=0x40a157]
goroutine 1 [running]:
main.LenovoEC(0xc20801edc0, 0x19, 0xc20801eec0, 0x1f, 0xc20804638f,
0x6, 0xc20804640a, 0x12, 0xc20803d9e0, 0x2d, ...)
/home/gergap/work/opensource/coreboot/util/autoport/ec_lenovo.go:
20 +0x1d37
main.ScanRoot(0xc20801edc0, 0x19, 0xc20801eec0, 0x1f, 0xc20804638f,
0x6, 0xc20804640a, 0x12, 0xc20803d9e0, 0x2d, ...)
/home/gergap/work/opensource/coreboot/util/autoport/root.go:33
+0x52a
main.main()
/home/gergap/work/opensource/coreboot/util/autoport/main.go:727
+0x683
On further runs the system freezes.
To fix the tree again I run
sudo -R gergap .
git clean -fdx
git reset --hard
This way I could reproduce the above output.
The created log files can be found here:
https://www.dropbox.com/s/1r2dvbk7rj68fuv/logs.tar.gz?dl=0
The created mainboard folder is not really useful,
but if you are interested here is the patch:
https://www.dropbox.com/s/2ejds3ppae0y5md/0001-Add-lenovo-thinkpad_x1_carbo…
Any help is appreciated.
On Sunday, December 13, 2015 07:52:31 PM you wrote:
> Try util/autoport and it can be easier.
--
mfg,
Gerhard Gappmeier
I noticed that commit 0d618afc modified the CBFS file format. (It
looks like the "checksum" field was replaced with a new file
"attributes" feature.) However, the CBFS documentation in the
repository (Documentation/cbfs.txt) was not updated.
It would be great if the documentation could be kept in sync with the
CBFS implementation. (Or, if that's not feasible, I think it would be
preferable to remove Documentation/cbfs.txt .) Having up to date
specifications helps other projects (eg, SeaBIOS) keep up with
changes.
Also, I didn't see any emails for the above change on the mailing
list. What is the best way to keep up with notable architectural
changes in coreboot?
-Kevin
Dear coreboot folks,
change set #12804 [1] proposes the following addition to the file
`Documentation/gerrit_guidelines.md`.
239 +* When bringing in a patch from another git repo, update the original
240 +git/gerrit tags by prepending the lines with 'Original-'. Marking
241 +the original text this way makes it much easier to tell what changes
242 +happened in which repository. This applies to these lines, not the actual
243 +commit message itself:
244 + Commit-Id:
245 + Change-Id:
246 + Signed-off-by:
247 + Reviewed-on:
248 + Tested-by:
249 + Reviewed-by:
250 +The script 'util/gitconfig/rebase.sh' can be used to help automate this.
251 +Other tags such as 'Commit-Queue' can simply be removed.
Unfortunately, I do not fully understand the reasoning yet. Why is it
important, to (easily) know what tags were added in what repository.
*Commit-Id* is good to know, to easily find the commit in the other
repository, but the *Change-Id* can be used for that too.
Signed-off-by is also not changed in the Linux kernel when it is pulled
in. The new Signed-off-by line is just appended after the tags so it’s
clear what way the commit or change set took.
The same is true for the other tags.
So I would actually propose, to leave the tags unchanged when moving
them over.
What am I missing?
Thanks,
Paul
[1] https://review.coreboot.org/12804
[2] https://review.coreboot.org/#/c/12804/2/Documentation/gerrit_guidelines.md
Hi, I'm deals compling Coreboot. I compile Coreboot with
Linux payload. This run on QEMU. Coreboot works, but kernel panic error I
had. How I solve my problem?
Coreboot version: 4.1
Coreboot image size: 2 MB
GNU/Linux version in Coreboot: 4.1
QEMU version: 2.0.0
QEMU has been emulated processor type: x86 32 bit - Default
QEMU has been emulated RAM amount: 64 MB (If I set 1024 MB of RAM, even so I have this error.)
This error: Kernel panic - not syncing: Out of memory and no killable processes...
Thanks for replying.
