-----BEGIN PGP SIGNED MESSAGE-----
Hi @ all,
is there a Coroboot for the Lenovo T410 Laptop?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----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
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
The relevant files are
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>
On 25.08.2014 04:39, Charles Devereaux wrote:
> (http://www.coreboot.org/pipermail/coreboot/2014-July/078320.html) I
> mentioned that 3 bugs seemed to be related to the DSDT:
> - missing ACPI events when the stylus is inserted/removed
How is the OS supposed to react to them?
> - errors when trying to make the leds blink with tpacpi
> - errors during TPM initialization
Some people here would call it a feature.
> Ideally, the DSDT should be fixed within coreboot, but this goes beyond
> my present abilities.
Not true. Just do the same changes to the corresponding *.asl files in
coreboot repo and send the patch to gerrit. Other than a layer of
preprocessing, it's exactly the same code as you got from disassembly.
Do you know from which time the hotel is accessible on Thursday?
I just need to know if I can arrive at the hotel directly and leave my
or if I should go to the university first.
Am 14.10.2014 um 13:31 schrieb Rudolf Marek:
> Hi all,
> Sorry for the noise I managed to exchange euros already. I did a
> favor to a colleague who needed urgently cash in CZK. If you need to
> I would try either ATMs or as I have written on wiki page the
> exchange8.cz (todays rate is 1 EUR =27.68 CZK) or any other exchange
> where is acceptable ratio and no fees.
On 2014-10-31 10:56, Gregg Levine wrote:
> The rest of the group will chime in soon, but is the board currently
> running a known working distribution of Linux? Some released ones do
> not provide good toolchains for us.
I don't have the board, as I haven't yet decided to buy it. But I'd run
Debian wheezy on it. By toolchains, do you mean GCC and Binutils or
superiotool and flashrom?
> The other problem here is that we'll need to have you run such tools
> as are shown on the wiki. Please note that they need to be run at the
> prompt. One of them is the superio tool, and the other is the flashrom
> tool. The other one concerns itself with the tool to reading the
> contents of the PCI management registers. (It also tells us what
> components were used to glue the entire system together.)
Sure, I can run superiotool and flashrom, either from Debian or from Git
> For example some examples shown are untested because the boards are
> wearing proprietary parts who were specially built for them. Intel is
> famous for doing that...
> Oh and regarding the ROM chip containing your system's commercial BIOS
> I suggest tracking down spares as you might need them. The other
> problem is how the part is fastened down on the board.
> I believe that covers it.
Yes, I have some W25Q80BVDAIG chips I planned to use with another board.
I know the board comes with a socketed W25Q64FVAIG, although I'm having
some trouble finding a distributor who carries that chip or equivalent
chips. I assume the 80BV ones I have won't work, because they use a
slightly different supply voltage range?
Patrick "P. J." McDermott
Lead Developer, ProteanOS
I'm interested in running coreboot on the ASUS F2A85-M, and I have a few
The wiki page for the board says that hardware virtualization is
untested. Has anyone tested this since the page was created in 2012?
Or could someone with this board please test this?
How reliable is the hack for supporting Richland CPUs?
Are other variants of the F2A85-M (e.g. F2A85-M2) supported?
Patrick "P. J." McDermott
Lead Developer, ProteanOS
On 29.10.2014 05:17, Charles Devereaux via coreboot wrote:
> On Tue, Oct 28, 2014 at 8:56 PM, Kyösti Mälkki <kyosti.malkki(a)gmail.com>
>> For the i82801gx part in x60, I am not sure if it will support 16MB SPI
>> parts as datasheet specifies decode registers for the top 8MB only.
>> Or was there already a proof-of-concept it works?
>> FWH_DEC_EN1Firmware Hub Decode Enable Register.
> Oops. you may be right. I just picked up 16 MB since it was the largest
> size SPI would support. For the moment, I guess I will have to restrict the
> images to 8MB
What does FWH_DEC_EN1 have to to with SPI flash? AFAICS it's for FWH
flash, a totally different beast.
Or put another way, why would that register restrict SPI flash size in
FYI, at the coreboot workshop, thanks to the efforts of several people
including peter, stefanct, and another person named "Ron's memory
sucks", we got the u-root stuff working!
This is a kernel and and an initramfs containing a full go toolchain
and source to all programs that you run. They are compiled on demand.
Le 29/10/2014 à 05h26, Charles Devereaux a écrit :
> This is interesting because just today I did remap Fn+space to switch
> between desktops, so I'm positive it works. I only remember of Fn+10 (IIRC
> - might be 11) not working.
How did you do? It doesn’t have any effect on xev, so I don’t know which
keysym/keycode (though I don’t know how to use keycode with xkb) in my
> Maybe you are not getting the full key events?
Yes, at least not trough xev/xkb.
> I suggest you first try with acpi_listen (as some of these Fn keys
> give acpi events)
Done, and actually it works: Fn+1, 11, space, and also 2, 3, 4, 5, 7,
but nothing else.
> then read tpacpi documentation about the keymask
> After that, check:
> To do like this guy using python, try:
>>>> hex(0x38C7FFF + pow(2,0x14) + pow(2,0x15))
Not sure to understand much of this…
> I'm using 0x078DFFFF and I wanted to add : 0x08, 0x09, 0x0c, 0x0d, 0x0e,
> 0x11, 0x12 to get more keyevents (just like you, I love to have more
> possibilities) but I haven't had much time to investigate the details.
Yeah so do you know how to do anything? How did you remapped Fn+Space at