-----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 John,
> It sounds to me as though the PCI id's of the graphics card for the
> upgraded CPU may be different (I could be totally wrong about that, so I
> defer to others on the list if I'm barking up the wrong tree) and your
> coreboot image may need to be updated accordingly. Of course, it could
> also be the video BIOS that's the problem as you've suggested.
Thank you for the hint. I inspected that, but the PCI-IDs actually look the same:
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993]
(A4-5300)
and
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8670D] (prog-if 00 [VGA controller])
(A10-6700)
Looks like the VGA BIOS is really different:
# diff vgabios_a4-5300.bin vgabios_a10_6700.bin
Binary files vgabios_a4-5300.bin and vgabios_a10_6700.bin differ
Guess I will have to to "update" the VGA BIOS then.
Cheers, Daniel
>
> Hi Daniel,
>
>
> Kind Regards,
>
> John.
>
>
> On 28/06/16 09:24, Daniel Kulesz via coreboot wrote:
> > Hi folks,
> >
> > I upgraded the CPU in my F2A-85M from a A4-5300 (Trinity) to a A10-6700 (Richland). The board had Coreboot installed before with the VGA BIOS extracted from the A4-5300. However, I did not get any video output when trying to boot after the upgrade, so I replaced the flash chip with a backup with the vendor BIOS that works.
> >
> > Is it likely that the A10-6700 needs a different VGA BIOS or does this this rather look like a different issue? I don't want to experiment too much because the BIOS chips are hardware-wise pretty fragile (even when using the extractor tool).
> >
> > Cheers, Daniel
> >
The Linux 4.7 kernel payload crashes early in the boot process
with CoreBoot 4.4. I traced it to these instructions that are
finding a safe spot to decompress the rest of the kernel and
patched around it with a hard coded location:
diff -u --recursive /home/hudson/build/clean/linux-4.7/arch/x86/boot/compressed/head_64.S ./linux-4.7/arch/x86/boot/compressed/head_64.S
--- /home/hudson/build/clean/linux-4.7/arch/x86/boot/compressed/head_64.S 2016-07-24 15:23:50.000000000 -0400
+++ ./linux-4.7/arch/x86/boot/compressed/head_64.S 2016-08-05 12:07:11.399854225 -0400
@@ -340,9 +357,15 @@
1:
/* Target address to relocate to for decompression */
+#if 0
movl BP_init_size(%rsi), %ebx
subl $_end, %ebx
addq %rbp, %rbx
+#else
+ // coreboot does not populate the init_size boot param?
+ // fake it with a hard coded value
+ movl $0x97b000, %ebx
+#endif
/* Set up the stack */
leaq boot_stack_end(%rbx), %rsp
It seems that the Linux kernel bzImage is supposed to set this value,
rather than coreboot, so my comment is likely incorrect.
Dumping linux-4.7/arch/x86/boot/header.o, it looks like init_siez
is supposed to be 0xcf5000, so I wonder if %rsi is pointing to the
wrong location.
In 4.6.4 the computed address was hardcoded:
movl $LOAD_PHYSICAL_ADDR, %ebx
/* Target address to relocate to for decompression */
addl $z_extract_offset, %ebx
3e: bb 00 00 00 01 mov $0x1000000,%ebx
43: 81 c3 00 00 00 00 add $0x0,%ebx
--
Trammell
Hi,
FOSDEM 2017 deadlines are soon.
Do we want to have a full developer room, a talk or just a stand?
Unfortunately I won't be able to attend, so someone else will have to be
the formal contact for organizing our stand/devroom/talk. I will help
with submitting proposals if this is desired by the person organizing
our stand/devroom/...
Who is willing to take care of our FOSDEM 2017 presence?
https://fosdem.org/2017/news/2016-07-20-call-for-participation/
Deadlines:
Developer Rooms: 9 September
Main Track Talks: 10 October
Stands: 31 October
Lightning talks: 25 November
Regards,
Carl-Daniel
Dear coreboot folks,
At the last coreboot community meeting (CCC) [1][2], some participants
couldn’t here what other participants were saying with the current
conference call solution Discord [3].
As this greatly reduces the productivity, the conclusion was to find a
different solution, as this problem has been present since the
beginning and Discord doesn’t seem to be able to fix this.
So either somebody gets in contact with Discord, and they promise to
work on a solution for the next meeting, or we need to find a different
solution.
The requirements are.
1. Working conference call (audio) functionality
2. No registration necessary
3. Clients for all operating systems (packages at best in distribution
archive), or at least a Web client that runs with Mozilla Firefox (ESR
and last version), and Google Chromium (last version).
Chris(?) offered to set up a Mumble [4] server. Clients for all
operating systems are supposed to be available.
Also Tox was mentioned [5], which doesn’t feature a Web client, as far
as I can see.
So if you know of a solution, please tell us, so that technical
problems won’t spoil the fun of the CCCs.
Thanks,
Paul
[1] https://www.coreboot.org/Coreboot_community_meeting
[2] https://coreboot-meeting.pads.ccc.de/CommunityMeetingTopics?
[3] https://discordapp.com/
[4] https://wiki.mumble.info/wiki/Main_Page
"Mumble is an open source, low-latency, high quality voice chat
software primarily intended for use while gaming."
[5] https://tox.chat/
Dear coreboot folks,
At the last coreboot community meeting (CCC) [1][2] the TALOS Secure
Workstation was brought up, and most people said, they won’t be able to
afford the base system.
Martin said it’d be great to have one system as a coreboot build
system, and suggested that the coreboot community together funds a
workstation.
What do you think?
Thanks,
Paul
PS: Please spread the word of the crowdfunding to your friends, and
coworkers, and support it, so that it’ll be a success.
[1] https://www.raptorengineering.com/TALOS/prerelease.php
[2] https://www.crowdsupply.com/raptor-computing-systems/talos-secure-worksta...
Hi
I have been working on building a Petitboot, a kexec bootloader, [0]
based Linux payload using the Buildroot build system to produce a nice
bzImage that contains both linux and the initrd. It is inspired by the
Raptor Enginering HOWTO [0] and is based on op-build [1], the tool for
building OpenPOWER firmware, which also uses Buildroot and Petitboot.
One of the advantages of Petitboot is that it is fairly simple and
intuitive to use and does not require complex configuration like grub
does, while still providing a large range of hardware support since it
uses linux at its core.
A disadvantage is that a Linux + initrd payload takes up quite a bit of
space. A fairly stripped down kernel + initrd takes up ~6.9M in the
current Buildroot + Linux configuration I have. So a large flash chip or
replacing the flash with a larger one is recommended.
Coreboot can directly use this Linux payload or first load SeaBIOS which
can then chainload the Linux payload.
It is still very much a WIP and is currently aimed at Intel hardware,
but with a kernel configuration tuned to your target it should work
fine.
The repo + initial documentation:
https://github.com/ArthurHeymans/petitboot_for_coreboot
[0] Petitboot: A kexec based bootloader,
https://www.kernel.org/pub/linux/kernel/people/geoff/petitboot/petitboot....
[1] Creating firmware images with petitboot and coreboot
https://secure.raptorengineering.com/content/kb/1.html
[2] OpenPower Firmware Build Environment
https://github.com/open-power/op-build
Kind Regards
--
Arthur Heymans
