coreboot May 2015

coreboot@coreboot.org

46 participants
117 discussions

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Test Stand 05 May '15

05 May '15

The ASUS KFSN4-DRE fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: BOOT_FAILURE Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region into ramstage, too 634899c resource: Adjust memory resources high earlier e6a9290 resource: Enhance resource reporting 134b616 resource: Report correct secondary resource window ade2c5e winent/mb6047: symbolic arguments for acpi_create_madt_lapic_nmis() <8 commits skipped> 2436bda cpu: get rid of socket source code 99cc1aa Mediawiki editing warning e9b7e25 util/xcompile/xcompile: Allow to override `HOSTCC` variable 939dc84 crossgcc: Re-download the archive if it is incomplete 6548ae9 cbfstool/Makefile*: Use `LDFLAGS` instead of `LINKFLAGS` See attached boot log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

2 1

Re: [coreboot] cmos.layout: power_on_after_fail
by Marc Jones 05 May '15

05 May '15

Iru, It is powering on if it thinks that the normal shutdown failed. You can change the default for your build and/or check if there is a logic bug. Also check that the option is correctly cleared on S5. Finally, details of your board and chipset would be good to mention. Marc On Mon, May 4, 2015 at 10:37 AM ron minnich <rminnich(a)gmail.com> wrote: > The original use of power_on_after_fail was for HPC server nodes that we > wanted to power on after an external power failure without having to go to > 1024 nodes and touch a button (this was a real issue at Los Alamos and IIRC > the fix came from Linux NetworX). This is LONG before laptops were a gleam > in our eye. > > I'm not surprised that it doesn't fit the laptop use case that well. > > ron > > On Sat, May 2, 2015 at 4:44 AM Iru Cai <mytbk920423(a)gmail.com> wrote: > >> Hi, >> >> After I set CONFIG_USE_OPTION_TABLE, my laptop will power on when I plug >> in the AC adapter. Then I find disabling `power_on_after_fail' will prevent >> my laptop from booting when AC is plugged in. So I wonder why this setting >> is called `power_on_after_fail' instead of `power on AC attach' as with the >> vendor BIOS? >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> http://www.coreboot.org/mailman/listinfo/coreboot > > -- > coreboot mailing list: coreboot(a)coreboot.org > http://www.coreboot.org/mailman/listinfo/coreboot

1 0

QEMU x86_64 Q35 Automated Test Failure
by Raptor Engineering Automated Test Stand 05 May '15

05 May '15

The QEMU x86_64 Q35 fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: BOOT_FAILURE Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region into ramstage, too 634899c resource: Adjust memory resources high earlier e6a9290 resource: Enhance resource reporting 134b616 resource: Report correct secondary resource window ade2c5e winent/mb6047: symbolic arguments for acpi_create_madt_lapic_nmis() <8 commits skipped> 2436bda cpu: get rid of socket source code 99cc1aa Mediawiki editing warning e9b7e25 util/xcompile/xcompile: Allow to override `HOSTCC` variable 939dc84 crossgcc: Re-download the archive if it is incomplete 6548ae9 cbfstool/Makefile*: Use `LDFLAGS` instead of `LINKFLAGS` See attached boot log for details This message was automatically generated from Raptor Engineering's QEMU x86_64 Q35 test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

2 1

Re: [coreboot] cmos.layout: power_on_after_fail
by ron minnich 04 May '15

04 May '15

The original use of power_on_after_fail was for HPC server nodes that we wanted to power on after an external power failure without having to go to 1024 nodes and touch a button (this was a real issue at Los Alamos and IIRC the fix came from Linux NetworX). This is LONG before laptops were a gleam in our eye. I'm not surprised that it doesn't fit the laptop use case that well. ron On Sat, May 2, 2015 at 4:44 AM Iru Cai <mytbk920423(a)gmail.com> wrote: > Hi, > > After I set CONFIG_USE_OPTION_TABLE, my laptop will power on when I plug > in the AC adapter. Then I find disabling `power_on_after_fail' will prevent > my laptop from booting when AC is plugged in. So I wonder why this setting > is called `power_on_after_fail' instead of `power on AC attach' as with the > vendor BIOS? > > -- > coreboot mailing list: coreboot(a)coreboot.org > http://www.coreboot.org/mailman/listinfo/coreboot

1 0

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Test Stand 04 May '15

04 May '15

The ASUS KFSN4-DRE fails verification as of commit 58649b058baecf24a07a2bc85fff68b339d67503 The following tests failed: CBMEM_OBJECT_TABLE_TRUNCATED Commits since last successful test: See attached boot log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

QEMU x86_64 Q35 Automated Test Failure
by Raptor Engineering Automated Test Stand 04 May '15

04 May '15

The QEMU x86_64 Q35 fails verification as of commit 58649b058baecf24a07a2bc85fff68b339d67503 The following tests failed: CBMEM_TIMESTAMP_ACCESS_FAILURE CBMEM_OBJECT_TABLE_TRUNCATED Commits since last successful test: See attached boot log for details This message was automatically generated from Raptor Engineering's QEMU x86_64 Q35 test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

mytbk920423@gmail.com has indicated you're a friend. Accept?
by mytbk920423＠gmail.com 03 May '15

03 May '15

Hi, mytbk920423(a)gmail.com wants to follow you. ****** Is mytbk920423(a)gmail.com you friend? ****** If Yes please follow the link below: http://invites.flipmailer.com/signup_e.html?fullname=&email=coreboot@co… If No please follow the link below: http://invites.flipmailer.com/signup_e.html?fullname=&email=coreboot@co… Follow the link below to remove yourself from all such emails http://invites.flipmailer.com/uns_inviter.jsp?email=coreboot@coreboot.org&a…

1 0

Re: [coreboot] [RFC] Putting HDA verbs in CBFS
by Felix Held 03 May '15

03 May '15

> would it work to name the verb tables by the vendor,device > standard we use for vga bios and then be able to pick the right one? Those HDA verb tables are not only codec dependent, but also board dependent. In the tables is e.g. the configuration for the different analog ports, which very likely differs on different boards.

1 0

[RFC] Putting HDA verbs in CBFS
by Paul Menzel 03 May '15

03 May '15

Dear coreboot folks, currently there are three change sets up for review adding new Lenovo laptops based on the Intel GM45 chipset [1][2][3]. Most of them are very similar to the Lenovo X200, which is already in our tree. One of the major differences between the Lenovo T* models is the HDA verb table. As these are currently included during compile time, all board files have to be copied [3] as Peter noted: Patch Set 2: Code-Review-2 vendor BIOS provides different HDA verbs: coreboot of course needs to do that too. This should still be replaced with a separate port: yes exactly. please resubmit when that is done. Thanks! It’d be great to have one image to support all these different models. Is it feasible to put the HDA verb tables for the different models into CBFS and load the right one during run time? If such a model run time detection is not possible, then the corresponding HDA verb file could be added during the build process and the devices Lenovo R400 and T500 would just be clones of the Lenovo T400 for example with different HDA verbs. Thanks, Paul [1] http://review.coreboot.org/9181 New mainboard: Lenovo T500 [2] http://review.coreboot.org/9316 mainboards/lenovo: Copy X200 board to T400 for future expansion [3] http://review.coreboot.org/8393 lenovo/r400: Add clone of Lenovo T400

3 2

Solving zilogpnz's backlight problem at Lenovo G505s
by Vladimir 02 May '15

02 May '15

Try using vgabios of your Radeon HD 8650G ( " 1002,990b " graphic device of A10-5750M APU ) during coreboot compilation. According to G505s wiki page, currently AtomBIOS blob is needed for onboard VGA, but maybe its also needed for your working backlight? I retrieved my vgabios via Linux kernel 3.19 using this method - http://www.coreboot.org/VGA_support#Retrieval_via_Linux_kernel .Then I downloaded latest sources of SeaBIOS & Coreboot, and build Coreboot using compiled SeaBIOS payload as well as vgabios file. My configuration is a bit similar to this one - http://www.coreboot.org/Supported_Motherboards#lenovo.2Fg505s - although some options were added and some removed since a time of that build. In my understanding, vgabios needs to be extracted from a running machine. So just in case if your G505s is in bricked state and you can't run it for extraction of vgabios, I am sending it to you in attachments of this letter! However I need to mention one interesting thing: *after *my laptop started running coreboot, what I retrieve via Linux kernel is now slightly different -- if to compare with what I used to retrieve *before *, while my laptop was still running a proprietary BIOS. And I have flashed coreboot rom into BIOS chip with file verification , so that doesn't seem to be a "bad flashing" case. Looks like Coreboot does not load a vgabios ROM inside it AS-IS, and instead modifies it slightly while loading... So here are two bios files for you (could use any of them, maybe "before" one like I did) vgabios_before.bin - SHA1 checksum: e4d320eb278b0118c46e2e470e7154b12c41966d vgabios__after.bin - SHA1 checksum: a9e2ed569bbaaea283b5380a5f6c44fc4efc3da4 And here is a report about 3 bytes difference between them - http://www.diffnow.com/?report=2kwq3 P.S. What if your backlight problem could be related to manufacturer/model of LCD panel? For the reference, my panel is Samsung LTN156AT30L01 ( SDC Model 4652 ) which is working perfectly On 4 April 2015 at 13:08, Vladimir <quickcracktime(a)gmail.com> wrote: > Very sorry to hear that your LCD backlight problem is not resolved yet! > Are you confident that LCD backlight is not faulty, and have you tried > reinstalling coreboot? > > If answer for both questions is "yes", then you could try these two advices: > > 1) Redownload a source code of coreboot from github, compile it and flash > again to your G505s. > Since your last try - at the end of January - there were 5 commits to > "coreboot/src/mainboard/lenovo/g505s" branch, > and also some commits to the common branches, changes that affect all the > mainboards supported by coreboot. > Maybe your issue will be resolved if you would try coreboot again, with > latest sources! > > 2) If 1st advice doesn't work, you could open > "coreboot/src/mainboard/lenovo/g505s/buildOpts.c" file > (which is the only file from G505s branch that has a reference to "LCD") > Go to line 158, try to change the "#define BLDCFG_CFG_LCD_BACK_LIGHT_CONTROL > 200" parameter. > Default value seems to be 200 for most platforms, but you could try setting > it to 0. Then compile & flash again > > === Any advices from experienced coreboot members would be very welcome! === > > On 3 April 2015 at 17:46, 1 1 <zilogpnz(a)gmail.com> wrote: >> >> No. I not solved this problem. >> >> 2015-04-03 17:08 GMT+04:00 Vladimir <quickcracktime(a)gmail.com>: >>> >>> > On Mon Jan 26 13:07:42 CET 2015 zilogpnz wrote: >>> >> I'm trying to run Coreboot on Lenovo G505s and have a problem: >>> >> - backlight of LCD is not turn on. But on the external LCD (by CRT >>> >> connector) is all good. >>> >> >>> >> Could you help me with a solution to this problem? >>> >>> >>> Sorry for such a long reply, but what is a current status of this >>> problem? >>> Have you resolved the LCD backlight problem with your G505s - and, if >>> yes, how? >> >> >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2015