-----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-----
#95: Run coreboot in VirtualBox
---------------------------------+------------------------------------------
Reporter: uwe | Owner: somebody
Type: defect | Status: new
Priority: minor | Milestone:
Component: misc | Version:
Keywords: | Dependencies:
Patchstatus: there is no patch |
---------------------------------+------------------------------------------
It would be nice if we could test coreboot images in VirtualBox, see
http://virtualbox.org/.
VirtualBox does not (yet) provide a simple mechanism to use a different
BIOS in their emulated machines (something like "-L" in qemu). Instead the
BIOS image (a custom bochs BIOS + LGPL'g VGABIOS) is converted to C code
(an array of bytes, or the like) and merged into the VirtualBox
executable.
The relevant files are
{{{
src/VBox/Devices/PC/DevPcBios.cpp
bldprogs/bin2c.c
}}}
if someone want to hack VirtualBox to easily support using coreboot images
instead of their usual BIOS.
--
Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/95>
coreboot <http://www.coreboot.org/>
Hello all,
I am currently working on helping the Chromium team get their coreboot
patches upstreamed so I thought I should introduce myself to the community.
My name is Isaac Christensen and I've been working for Sage Electronic
Engineering since October. These will be my first pushes up to coreboot.org
so if you have any comments on process or workflow feel free to let me know
as I'm still learning.
Thank you,
Isaac
Hi all,
First of all sorry that it took so long to get back to this.
I have in plan to organize a coreboot meeting in the Prague on 19,20,21 of
September. I created the doodle here:
http://doodle.com/h6yar2mtxarvhv3x
I put there also Thursday if we want to meet earlier. The programme is to hack a
coreboot and enjoy Prague together. This time we will have a room at the Czech
Technical university near the the Masarykova dormitory (that one which was used
last time).
Please let me know if anyone has questions / ideas what to do / talk about /
Does the date fit well?
We have some co-working center in Prague so it could be possible to stay longer
in Prague and do office stuff from there (besides that google has office in
Prague too).
Thanks
Rudolf
Hello, i make it short and simple. I want use coreboot but i dont know if my system is supportet:
Mainboard infos:
I have an Acer Predator G3620 and my mainboard have the same nameand i have I7-3770
More Infos:
I have try to get my Super I/O under linux but i get always the outpput "No Super I/O found:
Bios device is " Found Winbond flash chip "W25Q64.V" (8192 kB, SPI)."
And here is my "lspci" output:http://pastebin.com/CvccKqsH
I hope someone can help me
On 07/29/2014 09:20 PM, David Hendricks wrote:
> On Tue, Jul 29, 2014 at 9:55 AM, Isaac <isaac.christensen(a)se-eng.com> wrote:
>
>> Hello all,
>>
>> I am currently working on helping the Chromium team get their coreboot
>> patches upstreamed so I thought I should introduce myself to the community.
>> My name is Isaac Christensen and I've been working for Sage Electronic
>> Engineering since October. These will be my first pushes up to
>> coreboot.org
>> so if you have any comments on process or workflow feel free to let me know
>> as I'm still learning.
>>
>
> Great! We'll look forward to working with you on this.
>
> It might be beneficial to drop by #coreboot on irc.freenode.net to answer
> questions / feedback about patches in real-time.
>
>
>
Excellent. A couple questions though:
Do you plan to upstream all Chromebook coreboot and libpayload branches
from Chromium git, or just the individual patches Sage finds useful and
necessary for the boards You currently work on?
Do we expect the original authors to review the rebased, possibly
modified work, or is the plan these patches just get rubberstamped as +2
by a 3rd party once they build cleanly?
I see some of you first patches had a couple commits from Chromium tree
squashed into one. Why was the approach changed from how eg. Aaron and
Stefan handled the process? This has the unpleasant effect that commit
ownership (and eg. git blame) will no longer reflect the actual author
of change and also git log --oneline no longer serves as a datapoint in
attempt to compare which changes from Chromium branches have been
upstreamed or not.
Did you develop some nice method to keep track of which branches from
Chromium we can consider as completely upstreamed?
Do you have the facilities to do regular board-status script runs for
recent Chromebooks?
Kyösti
Hello
The modem is listed as "untested" on the X60 page, so I tried to explore
that a bit further.
On Windows, its hardware info is
"HDAUDIO\FUNC02&VEN_14F1&DEV_2BFA&SUBSYS_&REV_0900"
Some googling confirmed it was a Conexant, device ID 0x14f1,0x2bfa that was
connected as the 2nd device of the HDA bus and should show as the 2nd codec
of the audio card.
However it was never detected! (which may or may not be related to ACPI
tables - I don't know if they contain HDA bus info)
After reading the HDA-Intel kernel documentation, I could successfully
detect it with the kernel options : snd_hda_intel.model=thinkpad
snd-hda-intel.probe_mask=0x103
Basically, the current hardware tables do not expose it to the OS, so you
have to boot with manual probe instead of autodetection.
The modem is then detected as:
$ cat /proc/asound/Intel/codec#1
Codec: Conexant ID 2bfa
Address: 1
MFG Function Id: 0x2 (unsol 1)
Vendor Id: 0x14f12bfa
Subsystem Id: 0x14f10000
Revision Id: 0x90000
Modem Function Group: 0x2
Then, problem is that very codec is not supported with slmodem :
https://bugzilla.novell.com/show_bug.cgi?id=244436
"Some HD-modem codecs (e.g. Conexant ones) don't work with slmodemd."
So I tried to fix hsfmodem to have it compile under a recent kernel 3.x (cf
http://ubuntuforums.org/archive/index.php/t-1903439.html) but gave up.
At the moment the best option for those who need a working modem seems to
get a MDC card that works, like the Si3054, to replace the Conexant MDC.
Cf:
http://www.silabs.com/Support%20Documents/TechnicalDocs/si3054-18.pdfhttp://www.futurel.bg/datasheets/2/3054_PB.pdf
Even them, it will be far from perfect, cf
https://freemor.wordpress.com/2008/05/16/si3054-and-hardy-heron-the-saga-co…
Anyway, if you want to get one, search for "Modem 3054" on ebay : you will
find many ML3054. As per the specsheets, it needs revE or later to be
compatible with the HDA-Intel "Azalia" interface. Basically, make sure the
original computer it was pulled from used snd-intel-hda instead of
snd-intel8x0m (ex: lenovo y510 is ok) and you should be good.
I'm waiting for such a card, I will let you know if the modem works, but
everything indicates it should. The modem could then be indicated as
"working", but it will require a blob (for slmodem compilation) so
personally I don't think I'll use the modem functions, but someone might be
interested.
Charles
Hi,
Does anyone know how to enable S3 support for "Bayley Bay CRB-I" ?
I have been able to boot to linux using SeaBios as well as Grub2 payload
on the "Bayley Bay CRB-I"
but it does no appear to support S3 resume.
What needs to be done to enable support for S3 Sleep ?
Regards,
Mohan
