coreboot December 2013

coreboot@coreboot.org

40 participants
108 discussions

Why boot from floppy not working?
by Gelip 04 Dec '13

04 Dec '13

Hi. I try set floppy support in SeaBIOS like this: root@debian:~# cd /coreboot root@debian:/coreboot# ./build/seabios/scripts/encodeint.py floppy0 4 root@debian:/coreboot# ./build/cbfstool build/coreboot.rom add -f floppy0 -n etc/floppy0 -t raw root@debian:/coreboot# ./build/cbfstool build/coreboot.rom print coreboot.rom: 256 kB, bootblocksize 848, romsize 262144, offset 0x0 alignment: 64 bytes ================================================= Name Offset Type Size fallback/romstage 0x0 stage 17988 fallback/coreboot_ram 0x4680 stage 105981 fallback/payload 0x1e4c0 payload 59988 pci10ec,8139.rom 0x2cf80 raw 57344 etc/floppy0 0x3afc0 raw 8 (empty) 0x3b000 null 19544 ============================================================= After PC boot, press F12 and have menu: Press F12 for boot menu. Select boot device: 1. Floppy [drive A] 2. DVD/CD [ata1-0: OEM CD-ROM F563E ATAPI-0 DVD/CD] 3. ata0-0: Maxtor 2F020J0 ATA-7 Hard-Disk (19881 MiBytes) 4. gPXE (PCI 00:11.0) but after press 1 boot from floppy not working (FDD LED not light) and: Boot failed: could not read the boot disk I tray boot from Win95 boot floppy disk. In CMOS is set FDD 3.5' 1.44MB. In WinXP FDD read OK floppy content but after restart not possible copy any files from floppy. Also after restart I press F12 and select 1. Floppy [drive A]. Now FDD LED light but errors: Disk I/O error Replace the disk, and then press any key In terminal over COM: floppy error: 40 04 10 01 00 00 02 Please see winxp_restart.log I tray also boot from other floppy gPXE 5.4.4 and have other errors: ------------------------------------ 2000 AX:020F BX:3C00 CX:0101 DX:0000 2000 AX:020F BX:3C00 CX:0101 DX:0000 2000 AX:020F BX:3C00 CX:0101 DX:0000 2000 AX:020F BX:3C00 CX:0101 DX:0000 etc. ------------------------------------ and terminal also print: ------------------------------------ floppy error: 40 04 10 01 00 00 02 floppy error: 40 04 10 01 00 00 02 floppy error: 40 04 10 01 00 00 02 floppy error: 40 04 10 01 00 00 02 etc. ------------------------------------

2 2

libpayload not building drivers/usb/xhci.c
by Dave Frodin 03 Dec '13

03 Dec '13

I'm seeing a problem building payloads. The problem is actually occuring when libpayload gets built prior to being copied down to the payload. I'm building a different payload, but the problem can be seen when building coreinfo. Here's the sequence I used cd payloads/coreinfo make distclean rm -rf libpayloadbin make These are the errors I see... drivers/usb/xhci.c:146:1: error: conflicting types for ‘xhci_init’ In file included from drivers/usb/xhci.c:36:0: drivers/usb/xhci.h:37:8: note: previous declaration of ‘xhci_init’ was here drivers/usb/xhci.c: In function ‘xhci_pci_init’: drivers/usb/xhci.c:314:13: error: incompatible types when assigning to type ‘hci_t’ from type ‘struct hci_t *’ drivers/usb/xhci.c:315:12: error: invalid type argument of ‘->’ (have ‘hci_t’) drivers/usb/xhci.c:319:2: error: incompatible types when returning type ‘hci_t’ but ‘struct hci_t *’ was expected drivers/usb/xhci.c: In function ‘xhci_shutdown’: drivers/usb/xhci.c:417:38: error: ‘hci_t’ has no member named ‘bus_address’ drivers/usb/xhci.c: In function ‘xhci_pci_init’: drivers/usb/xhci.c:320:1: warning: control reaches end of non-void function [-Wreturn-type] I bisected the problem down to this commit commit 8992e53c23cb088efbdafbf3e2ba77e7d8778d71 Author: Stefan Reinauer <reinauer(a)chromium.org> Date: Thu May 2 16:16:41 2013 -0700 libpayload: Add USB support for non-PCI controllers Thanks, Dave

1 0

Re: [coreboot] Checking the latest Coreboot git snapshot
by Patrick Georgi 03 Dec '13

03 Dec '13

Am Dienstag, den 03.12.2013, 15:10 +0000 schrieb Stojsavljevic, Zoran: > (3) if (2) has nothing to do with descriptor.bin, what is that (description)?? It's not the FSP binary, it's the Intel Firmware Descriptor, essentially the flash partition table. Patrick

1 0

Checking the latest Coreboot git snapshot
by Stojsavljevic, Zoran 03 Dec '13

03 Dec '13

Hello Marc, Patrick, I was busy with another things over these few weeks, so today I got the newest snapshot from the Coreboot git, assuming that the IVB, HSW and SNB frameworks are already integrated with Sage Electronics, and approved by Coreboot maintainers. Now I am trying to build Coreboot from the real Coreboot, and I am running in to the following problem: CC arch/x86/boot/wakeup.ramstage.o CC generated/coreboot_ram.o CC cbfs/fallback/coreboot_ram.debug OBJCOPY cbfs/fallback/coreboot_ram.elf DD Adding Intel Firmware Descriptor make: *** [bd82x6x_add_me] Error 1 I found that the new added option in Coreboot make menuconfig in option <chipset>: [ ] Build with a fake IFD (3rdparty/mainboard/$(MAINBOARDDIR)/descriptor.bin) Path to intel firmware descriptor I added (according what I know) the following directories to Coreboot config options: [1] Specific microcode for my IVB CPU (0x306A9) I added into src/cpu/intel/model_206ax/ [2] vbios 2170 I added in src/mainboard/intel/emeraldlake2/vbios/snm_2170.dat (vbios.bin) [3] I assume that for FSP there is premeditated location...??? I added it into: src/mainboard/intel/emeraldlake2/fsp/FvFsp.bin Marc (Jones), Patrick (or anyone who followed the development), could you answer me the following questions, please? (1) Where I should place FSP.bin blob (is there place in Coreboot in mainboard/intel/$(BOARDNAME)... Or? (2) If I should define directory for FSP.bin, where I should put this in Coreboot .config? (3) if (2) has nothing to do with descriptor.bin, what is that (description)?? Thank you, Zoran Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Re: [coreboot] Need help to compile an AMD Geode GX2 VSA Binary
by Oliver Schinagl 01 Dec '13

01 Dec '13

On 12/01/13 13:06, Quentin Bouteiller wrote: > Thanks for your quick reply. However, the VSA mentioned in the Geode > Porting Guide is for the Geode LX (and not the GX which is in the Wyse > S30). Are-you sure that it will work? No clue, only one way to find out ;) But it might ... Oliver > > > 2013/12/1 Oliver Schinagl <oliver+list(a)schinagl.nl> > >> On 12/01/13 01:51, Quentin Bouteiller wrote: >> >>> Hi, >>> I am currently trying to compile Coreboot for my Wyse S30 (which is pretty >>> identical to a Wyse S50, for those who have one) by following this >>> tutorial<http://fijam.eu.org/blog/how-to-put-coreboot-on-wyse-S30s50/>but >>> >>> I have a major problem. >>> As you know, to compile a Coreboot ROM , we need two external elements: >>> SeaBIOS (or any other Payload) and a VSA image. For the first, there is no >>> problem: I am able to compile it without any problem. However, for the >>> second, there is a big problem: as it is said in the tutorial, "GX2 VSA >>> needs to be compiled with an antediluvian and esoteric toolchain from >>> sources that are almost nowhere to be found and embedded within the >>> coreboot image". And guess what? I am no able to get all the components >>> needed for the compilation (currently, I only have NMAKE.EXE and the >>> compilation environment if needed (a 16 years old Fujitsu computer running >>> Windows 95))... So, I want to know anyone could help me by sharing all the >>> dependencies (or, if you have it, directly the binary), please? >>> >> I've had the intention to try the same thing and ask the same question. >> Meanwhile I was able to find http://www.coreboot.org/AMD_ >> Geode_Porting_Guide which links to http://review.coreboot.org/ >> gitweb?p=blobs.git;a=tree;f=cpu/amd/geode_lx where there is 'a' blob [0] >> that I haven't been able to try yet. >> >> Do keep us posted of your progress! >> >> Oliver >> >> [0] http://review.coreboot.org/gitweb?p=blobs.git;a=blob;f= >> cpu/amd/geode_lx/gpl_vsa_lx_102.bin >> >>> >>> Quentin Bouteiller >>> >>> >>> >>> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> http://www.coreboot.org/mailman/listinfo/coreboot >> >

1 0

google/butterfly: Erratic touchpad behavior in cold weather
by mrnuke 01 Dec '13

01 Dec '13

Have any of you noticed this with the Pavilion 14 Chromebook? You take it outside from the warm house, open the lid to resume, and the mouse pointer moves heratically. It becomes impossible to co control, and the only way to bring it back to sanity is to completely power off. When the system comes back on, the issue is gone. Alex

2 1

Re: [coreboot] Need help to compile an AMD Geode GX2 VSA Binary
by Oliver Schinagl 01 Dec '13

01 Dec '13

On 12/01/13 01:51, Quentin Bouteiller wrote: > Hi, > I am currently trying to compile Coreboot for my Wyse S30 (which is pretty > identical to a Wyse S50, for those who have one) by following this > tutorial<http://fijam.eu.org/blog/how-to-put-coreboot-on-wyse-S30s50/>but > I have a major problem. > As you know, to compile a Coreboot ROM , we need two external elements: > SeaBIOS (or any other Payload) and a VSA image. For the first, there is no > problem: I am able to compile it without any problem. However, for the > second, there is a big problem: as it is said in the tutorial, "GX2 VSA > needs to be compiled with an antediluvian and esoteric toolchain from > sources that are almost nowhere to be found and embedded within the > coreboot image". And guess what? I am no able to get all the components > needed for the compilation (currently, I only have NMAKE.EXE and the > compilation environment if needed (a 16 years old Fujitsu computer running > Windows 95))... So, I want to know anyone could help me by sharing all the > dependencies (or, if you have it, directly the binary), please? I've had the intention to try the same thing and ask the same question. Meanwhile I was able to find http://www.coreboot.org/AMD_Geode_Porting_Guide which links to http://review.coreboot.org/gitweb?p=blobs.git;a=tree;f=cpu/amd/geode_lx where there is 'a' blob [0] that I haven't been able to try yet. Do keep us posted of your progress! Oliver [0] http://review.coreboot.org/gitweb?p=blobs.git;a=blob;f=cpu/amd/geode_lx/gpl… > > Quentin Bouteiller > > >

2 1

Need help to compile an AMD Geode GX2 VSA Binary
by Quentin Bouteiller 01 Dec '13

01 Dec '13

Hi, I am currently trying to compile Coreboot for my Wyse S30 (which is pretty identical to a Wyse S50, for those who have one) by following this tutorial<http://fijam.eu.org/blog/how-to-put-coreboot-on-wyse-S30s50/>but I have a major problem. As you know, to compile a Coreboot ROM , we need two external elements: SeaBIOS (or any other Payload) and a VSA image. For the first, there is no problem: I am able to compile it without any problem. However, for the second, there is a big problem: as it is said in the tutorial, "GX2 VSA needs to be compiled with an antediluvian and esoteric toolchain from sources that are almost nowhere to be found and embedded within the coreboot image". And guess what? I am no able to get all the components needed for the compilation (currently, I only have NMAKE.EXE and the compilation environment if needed (a 16 years old Fujitsu computer running Windows 95))... So, I want to know anyone could help me by sharing all the dependencies (or, if you have it, directly the binary), please? Quentin Bouteiller

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 December 2013