coreboot October 2014

coreboot@coreboot.org

43 participants
111 discussions

by A. Veek

1 year, 10 months

Re: [coreboot] No VGA output on e350m1 after flashing. what to do?

by Reiner Luett

Hi! On 30.06.2013 19:28, Christian Weinz wrote: > Maybe I didn't include the VGA option in the make menuconfig process. > How can I solve this problem? You need to add the VGA Option ROM (VGA BIOS -> Add VGA BIOS image). I've extracted it from the UEFI, but you also could use these: http://www.coreboot.org/index.php?title=ASRock_E350M1&oldid=11114 at the end of the page or you also may be able to use the default AMD fam14 (Persimmon) vbios. You will need to agree to the click through: http://wwwd.amd.com/support/vbioslic.nsf/userverify?openform http://www.coreboot.org/AMD_DB-FT1_PERSIMMON It's a pity, that bios_extract didn't work for now. You could use the AMI Aptio EFI MMTool with wine: http://win-lite.de/benutzer/fernando/BIOS-Tools/AMI_Aptio_EFI_MMTool_v4.50.… You need to extract OntarioEFIVbios with PCI ID 1002,9802 as Option ROM. Regards, Reiner --

3 years, 1 month

#95: Run coreboot in VirtualBox

by coreboot

#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/>

5 years, 10 months

Re: [coreboot] IBM x60t test - DSDT is in fact incomplete

by Vladimir 'φ-coder/phcoder' Serbinenko

On 25.08.2014 04:39, Charles Devereaux wrote: > Hello > > Previously > (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 details? usecase? > - 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.

5 years, 10 months

Re: [coreboot] coreboot Prague meeting - details

by Werner Zeh

Hi Rudolf. 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 car there or if I should go to the university first. Thanks Werner 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 > exchange, > 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 > office > where is acceptable ratio and no fees. > > Thanks > Rudolf >

5 years, 11 months

Re: [coreboot] ASUS F2A85-M questions

by Patrick 'P. J.' McDermott

On 2014-10-31 10:56, Gregg Levine wrote: > Hello! > 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 as needed. > 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 http://www.pehjota.net/ Lead Developer, ProteanOS http://www.proteanos.com/

5 years, 11 months

ASUS F2A85-M questions

by Patrick 'P. J.' McDermott

Hi, I'm interested in running coreboot on the ASUS F2A85-M, and I have a few questions. 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 http://www.pehjota.net/ Lead Developer, ProteanOS http://www.proteanos.com/

5 years, 11 months

Re: [coreboot] sourcing 128MB flash chips for an X60 with coreboot

by Carl-Daniel Hailfinger

Hi, 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> > wrote: > >> 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 any way? Regards, Carl-Daniel

5 years, 11 months

Re: [coreboot] sourcing 128MB flash chips for an X60 with coreboot

by ron minnich

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. https://docs.google.com/presentation/d/1ji5hprsNFXmMBaYwLw0hphTItdSQs2chTq7… ron

5 years, 11 months

Re: [coreboot] More Fn+key on X60T

by Garreau, Alexandre

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 layout description. > 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 > https://www.kernel.org/doc/Documentation/laptops/thinkpad-acpi.txt > > After that, check: > http://linux-thinkpad.10952.n7.nabble.com/How-to-get-volume-hotkeys-working… > > To do like this guy using python, try: >>>> hex(0x38C7FFF + pow(2,0x14) + pow(2,0x15)) > '0x3bc7fff' 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 least?

5 years, 11 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot October 2014