coreboot June 2017

coreboot@coreboot.org

57 participants
159 discussions

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Mariusz Szafrański 08 Jun '17

08 Jun '17

W dniu 08.06.2017 o 00:21, Zoran Stojsavljevic pisze: > Hello Mariusz, > > > Try adding below lines on top of your grub.cfg: > > Are you talking about this file: /etc/default/grub ? No. I`m talking about final */boot/grub2/grub.cfg *This is the file we need to point to from coreboot`s menuconfig. /Lines from ///etc/default/grub (grub config "source" file) GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=1 --word=8 --parity=no --stop=1"/ /GRUB_TERMINAL_INPUT="serial"/ /GRUB_TERMINAL_OUTPUT="serial" are "compiled" using grub2-mkconfig to final grub configuration file /boot/grub2/grub.cfg: // serial --unit=1 --speed=115200 --word=8 --parity=no --stop=1 terminal_input serial terminal_output serial / Mariusz

1 0

Re: [coreboot] GRUB boot menu is not showing GRUB2
by coreboot＠akumat.pl 08 Jun '17

08 Jun '17

Hi Dhanasekar, Try adding below lines on top of your grub.cfg: serial --unit=1 --speed=115200 --word=8 --parity=no --stop=1 terminal_input serial terminal_output serial Then rebuild coreboot and try. Or try with grub.cfg containing only above three lines (you should get working grub shell) Mariusz W dniu 07.06.2017 o 15:38, Dhanasekar Jaganathan pisze: > Hi Nico, > > Following is my complete Payload setting, > > 1.Add a payload -> (GRUB2) > 2.GRUB2 version -> (HEAD) > 3.Include GRUB2 runtime config file into ROM image = Y > 4.Gave the path of grub.cfg (which I copied from Fedora OS when booted > is booted with other BIOS vendor). > > Based on this, please provide your comments. > > Thanks, > Dhanasekar

2 1

Re: [coreboot] AMDPSP discussion
by Taiidan＠gmx.com 07 Jun '17

07 Jun '17

On 06/07/2017 11:37 AM, Johnysecured88 via coreboot wrote: > What I don't understand is how this will matter. Releasing the source code won't mean that is the source code they are using for PSP. Think of it like an open source program with a compiled binary available. The only way to ensure the code is the code of the binary is to do your own compiling. But for a CPU that would mean..... something much more difficult. The idea would be that they would release a mechanism that disables the boot signing key or enables us to sign our own binaries and thus we could load our own compiled code. (NOTE: I am referring to the boot signing key not the update signing key, one is ethical the other isn't.) > > The ONLY thing that can prevent this is doing away with PSP all together but if you notice in their replies that AMD glances past that idea as not going to happen because it's "impossible". I wonder, sunk costs fallacy or perhaps someone "convinced" them of its value. It is impressive irregardless that a few thousand people have managed to get the attention of AMD, even if it is just a marketing lackey.

1 0

Re: [coreboot] AMDPSP discussion
by Johnysecured88 07 Jun '17

07 Jun '17

What I don't understand is how this will matter. Releasing the source code won't mean that is the source code they are using for PSP. Think of it like an open source program with a compiled binary available. The only way to ensure the code is the code of the binary is to do your own compiling. But for a CPU that would mean..... something much more difficult. The ONLY thing that can prevent this is doing away with PSP all together but if you notice in their replies that AMD glances past that idea as not going to happen because it's "impossible". Sent with [ProtonMail](https://protonmail.com) Secure Email. -------- Original Message -------- Subject: [coreboot] AMDPSP discussion Local Time: June 2, 2017 11:43 AM UTC Time: June 2, 2017 4:43 PM From: rene.shuster(a)bcsemail.org To: coreboot(a)coreboot.org https://www.reddit.com/r/Amd/comments/6dinzy/why_do_amds_psp_drivers_make_m… Keep increasing the pressure! -- Tech III * AppControl * Endpoint Protection * Server Maintenance Buncombe County Schools Technology Department Network Group [ComicSans Awareness Campaign](http://comicsanscriminal.com)

1 0

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Nico Huber 07 Jun '17

07 Jun '17

On 07.06.2017 16:49, Dhanasekar Jaganathan wrote: > Hi Nico, > > Thanks for the info.. > > Actually, I have given "*make al*l" to rebuild the coreboot source. > > Is it correct way to rebuilt to the source? That should work fine. > > Or I have to run *make crossgcc-i386 CPUS=$(nproc)* and *make* crossgcc is only needed once. Nico > > Thanks, > Dhanaeskar > > On Wed, Jun 7, 2017 at 7:17 PM, Nico Huber <nico.huber(a)secunet.com> wrote: > >> On 07.06.2017 15:38, Dhanasekar Jaganathan wrote: >>> Hi Nico, >>> >>> Following is my complete Payload setting, >>> >>> 1.Add a payload -> (GRUB2) >>> 2.GRUB2 version -> (HEAD) >>> 3.Include GRUB2 runtime config file into ROM image = Y >>> 4.Gave the path of grub.cfg (which I copied from Fedora OS when booted is >>> booted with other BIOS vendor). >>> >>> Based on this, please provide your comments. >> >> I can only repeat myself: With this setup, you have to rebuild your >> coreboot every time you make changes to your grub.cfg. (You probably >> know that already and did so, but didn't tell it?) >> >> Nico >> >

2 1

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Nico Huber 07 Jun '17

07 Jun '17

On 07.06.2017 15:38, Dhanasekar Jaganathan wrote: > Hi Nico, > > Following is my complete Payload setting, > > 1.Add a payload -> (GRUB2) > 2.GRUB2 version -> (HEAD) > 3.Include GRUB2 runtime config file into ROM image = Y > 4.Gave the path of grub.cfg (which I copied from Fedora OS when booted is > booted with other BIOS vendor). > > Based on this, please provide your comments. I can only repeat myself: With this setup, you have to rebuild your coreboot every time you make changes to your grub.cfg. (You probably know that already and did so, but didn't tell it?) Nico

2 1

Coreboot + Seabios Asus F2A85-M LE card
by Gabriel Bosque 07 Jun '17

07 Jun '17

Hello everyone, thank you for accepting me in the group. I am totally newbie, however, I would very much like to have a pc running coreboot + seabios on an Asus F2A85-M LE card, could someone send me a .rom to write to memory? I have tried to compile, but nothing appears on the display ... I think if you confirm that it actually runs, it becomes easier to get the doubts later, through this group Thank you very much

1 0

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Nico Huber 07 Jun '17

07 Jun '17

On 07.06.2017 14:52, Dhanasekar Jaganathan wrote: > Hi Nico, > >> where do you expect to see the menu? a display? a serial console? In the >> former case, I expect you have to add a Video BIOS to your coreboot.rom >> (CONFIG_VGA_BIOS) and configure coreboot to run it (CONFIG_VGA_ROM_RUN). >> If you use a discrete gfx card, you don't need to add the VBIOS, it >> would be read from the card. In the latter case, GRUB has to be confi- >> gured to use the serial port, as Mariusz pointed out. > >> I'm a little confused here, did you add an etc/grub.cfg to the CBFS? You >> didn't say so but I wouldn't expect it to boot otherwise. If you have, >> can you please share this grub.cfg. > > I am using a serial console for *DISPLAY*. > I am not adding *grub.cfg* through *etc/grub.cfg*. > When I booted the board with other vendor BIOS, I have copied* > /boot/grub2/grub.cfg* from fedora OS and using this grub.cfg in coreboot. > I have mentioned the location of grub. cfg in menuconfig *(Payload -> > Include GRUB2 runtime config file into ROM image). * I see, that wasn't visible from your .config because you changed it from GRUB2 to adding a simple elf payload. Just to make sure you understood this correctly: This only points the coreboot build system to the file and the file gets copied into CBFS as etc/grub.cfg during build. So in this configuration, you have to rebuild your coreboot every time you change the grub.cfg. A more convenient solution would be to write a small intermediate grub.cfg that just loads the real grub.cfg from disk. e.g. create a new file called coreboot-grub.cfg with the single line: configfile (ahci0,1)/grub2/grub.cfg and point the coreboot build to that coreboot-grub.cfg. I've guessed the path from your current grub.cfg, I'm not 100% sure if it's correct. > > I have attached the same. > >>> >>> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops >>> the system indefinitely at boot menu in GRUB2). Still system is not >>> stopping at boot menu. > >> AFAIK, this file only works as input to `grub-mkconfig`. You'd still >> have to generate a grub.cfg with it and configure the GRUB payload to >> use it. > > when ever I modify */etc/defualt/grub*, I will run *grub2-mkconfig -o > /boot/grub2/grub.cfg*. > I forget to mention this in my previous mail. > >> You have set CONFIG_ROM_SIZE and CONFIG_CBFS_SIZE to the same value >> (8MiB). This is wrong. coreboot shares the flash chip with other Intel >> firmware components (Firmware Descriptor (IFD), ME firmware etc.). Be- >> side other configuration, the IFD partitions the flash chip in regions. >> coreboot's CBFS lives in the BIOS region and should be at most of this >> region's size. You can decode the descriptor with `ifdtool -d ...` (you >> can find it in util/ifdtool/ in the coreboot source). > > After setting, CONFIG_CBFS_SIZE = 6MB, I can able to build coreboot and I > am not getting below issue, > > *lzma: Decodeing error = 1* > *Payload not loaded.* > > Is it correct to set 6MB size for CONFIG_CBFS_SIZE?. > > Please correct me, If I am wrong and Provide your suggestions. It has to match your firmware descriptor, I can't tell you what it's set to. In other words, don't ask me, ask `ifdtool`. The following should work with the original, vendor ROM: $ make -C util/ifdtool/ $ util/ifdtool/ifdtool -d /path/to/vendor.rom | grep $BIOS$ Nico

2 1

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Dhanasekar Jaganathan 07 Jun '17

07 Jun '17

Hi Zoran, Please Ignore my previous mail. This is the correct one. Hi Nico, >where do you expect to see the menu? a display? a serial console? In the >former case, I expect you have to add a Video BIOS to your coreboot.rom >(CONFIG_VGA_BIOS) and configure coreboot to run it (CONFIG_VGA_ROM_RUN). >If you use a discrete gfx card, you don't need to add the VBIOS, it >would be read from the card. In the latter case, GRUB has to be confi- >gured to use the serial port, as Mariusz pointed out. >I'm a little confused here, did you add an etc/grub.cfg to the CBFS? You >didn't say so but I wouldn't expect it to boot otherwise. If you have, >can you please share this grub.cfg. I am using a serial console for *DISPLAY*. I am not adding *grub.cfg* through *etc/grub.cfg*. When I booted the board with other vendor BIOS, I have copied * /boot/grub2/grub.cfg* from fedora OS and using this grub.cfg in coreboot. I have mentioned the location of grub. cfg in menuconfig *(Payload -> Include GRUB2 runtime config file into ROM image). * I have attached the same. >> >> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops >> the system indefinitely at boot menu in GRUB2). Still system is not >> stopping at boot menu. >AFAIK, this file only works as input to `grub-mkconfig`. You'd still >have to generate a grub.cfg with it and configure the GRUB payload to >use it. when ever I modify */etc/defualt/grub*, I will run *grub2-mkconfig -o /boot/grub2/grub.cfg*. I forget to mention this in my previous mail. >You have set CONFIG_ROM_SIZE and CONFIG_CBFS_SIZE to the same value >(8MiB). This is wrong. coreboot shares the flash chip with other Intel >firmware components (Firmware Descriptor (IFD), ME firmware etc.). Be- >side other configuration, the IFD partitions the flash chip in regions. >coreboot's CBFS lives in the BIOS region and should be at most of this >region's size. You can decode the descriptor with `ifdtool -d ...` (you >can find it in util/ifdtool/ in the coreboot source). Can I set *CONFIG_CBFS_SIZE = 0x10000*?. Please correct me, If I am wrong and Provide your suggestions. Thanks, Dhanasekar On Wed, Jun 7, 2017 at 4:44 PM, Dhanasekar Jaganathan < jdhanasekarmca(a)gmail.com> wrote: > Thanks for the info > Hi Zoran, > > Sorry, I have mentioned */boot/default/grub.cfg* by mistake, instead of* > /etc/default/grub.* > > Hi Mariusz, , > > Yes,.. My system booted to Fedora on second serial port (ttyS1). > > I have modified /etc/default/grub as > > *GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=1 --word=8 --parity=no > --stop=1"* > *GRUB_CMDLINE_LINUX="console=tty1 console=ttyS1,115200 > vconsole.font=latarcyrheb-sun16 $([ -x usr/sbin/rhcrashkernel-param ] && > /usr/sbin/rhcr*" > > Still, I am not getting boot menu. > I am working on it. > > Please provide your suggestions. > > > Thanks, > Dhanasekar > > On Wed, Jun 7, 2017 at 12:13 PM, Zoran Stojsavljevic < > zoran.stojsavljevic(a)gmail.com> wrote: > >> And, just FC20 cot my eye??? >> >> *[root@ACCTON-b1-31 ~]# ls -al /boot >> * >> *total 56751 >> * >> *dr-xr-xr-x. 4 root root 1024 May 20 2016 . >> * >> *drwxr-xr-x. 19 root root 4096 Dec 25 20:00 .. >> * >> *-rw-r--r--. 1 root root 131847 Dec 5 2013 >> config-3.11.10-301.fc20.x86_64 * >> *drwxr-xr-x. 6 root root 1024 Dec 26 2009 grub2 >> * >> *-rw-------. 1 root root 34688326 May 20 2016 >> initramfs-0-rescue-16fa681cc2da4g* >> *-rw-------. 1 root root 10081375 May 20 2016 >> initramfs-3.11.10-301.fc20.x86_6g* >> *-rw-r--r--. 1 root root 211746 May 20 2016 initrd-plymouth.img >> * >> *drwx------. 2 root root 12288 May 20 2016 lost+found >> * >> *-rw-------. 1 root root 2686629 Dec 5 2013 >> System.map-3.11.10-301.fc20.x86_4* >> *-rwxr-xr-x. 1 root root 5139320 May 20 2016 >> vmlinuz-0-rescue-16fa681cc2da40c2* >> *-rwxr-xr-x. 1 root root 5139320 Dec 5 2013 >> vmlinuz-3.11.10-301.fc20.x86_64 * >> *-rw-r--r--. 1 root root 168 Dec 5 2013 >> .vmlinuz-3.11.10-301.fc20.x86_64c* >> >> Jesus Christs, WHY you are using Fedora 20??? Should move to F25, at >> least. Not saying that this is the bug, but still... :-(( >> >> Zoran >> >> On Wed, Jun 7, 2017 at 6:38 AM, Dhanasekar Jaganathan < >> jdhanasekarmca(a)gmail.com> wrote: >> >>> Hi Zoran, >>> >>> Below, I have provided the details, >>> >>> *[1] ls -al /boot* >>> >>> [*root@ACCTON-b1-31 ~]# ls -al /boot >>> * >>> *total 56751 >>> * >>> *dr-xr-xr-x. 4 root root 1024 May 20 2016 . >>> * >>> *drwxr-xr-x. 19 root root 4096 Dec 25 20:00 .. >>> * >>> *-rw-r--r--. 1 root root 131847 Dec 5 2013 >>> config-3.11.10-301.fc20.x86_64 * >>> *drwxr-xr-x. 6 root root 1024 Dec 26 2009 grub2 >>> * >>> *-rw-------. 1 root root 34688326 May 20 2016 >>> initramfs-0-rescue-16fa681cc2da4g* >>> *-rw-------. 1 root root 10081375 May 20 2016 >>> initramfs-3.11.10-301.fc20.x86_6g* >>> *-rw-r--r--. 1 root root 211746 May 20 2016 initrd-plymouth.img >>> * >>> *drwx------. 2 root root 12288 May 20 2016 lost+found >>> * >>> *-rw-------. 1 root root 2686629 Dec 5 2013 >>> System.map-3.11.10-301.fc20.x86_4* >>> *-rwxr-xr-x. 1 root root 5139320 May 20 2016 >>> vmlinuz-0-rescue-16fa681cc2da40c2* >>> *-rwxr-xr-x. 1 root root 5139320 Dec 5 2013 >>> vmlinuz-3.11.10-301.fc20.x86_64 * >>> *-rw-r--r--. 1 root root 168 Dec 5 2013 >>> .vmlinuz-3.11.10-301.fc20.x86_64c* >>> >>> *[2] What value GRUB_TIMEOUT do you see in: /boot/grub2/grub.cfg (maybe >>> you can try to play with this value)?* >>> >>> *GRUB_TIMEOUT = 5 (set timeout = 5).* >>> >>> *First I have tried GRUB_TIMEOUT = -1 and after that, I**[1] ls -al >>> /boot** have changed it to GRUB_TIMEOUT = 5. When ever I modified in >>> /etc/default/boot, it is getting reflected in boot/grub2/grub.cfg. * >>> >>> *I am thinking that there may be problem with GRUB2 which I am using or >>> I may be done mistake in GRUB2 integration with coreboot. Because, GRUB2 is >>> not consider the values in /etc/default/boot and booting to OS directly >>> without displaying bootmenu. * >>> >>> Please correct me, if I am wrong. >>> >>> Thanks, >>> Dhanasekar >>> >>> On Tue, Jun 6, 2017 at 10:16 PM, Zoran Stojsavljevic < >>> zoran.stojsavljevic(a)gmail.com> wrote: >>> >>>> Hello Dhanasekar, >>>> >>>> When you do boot into the Fedora (which one version?), could you, >>>> please, display for me the following: >>>> [1] ls -al /boot >>>> [2] What value *GRUB_TIMEOUT *do you see in: /boot/grub2/grub.cfg >>>> (maybe you can try to play with this value)? >>>> >>>> Thank you, >>>> Zoran >>>> >>>> On Tue, Jun 6, 2017 at 4:53 PM, Dhanasekar Jaganathan < >>>> jdhanasekarmca(a)gmail.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by >>>>> Coreboot. I am using *GRUB2 *as a Payload. >>>>> >>>>> In menuconfig, I have selected, >>>>> >>>>> Add a payload - *GRUB2* >>>>> GRUB2 Version - *HEAD*. >>>>> >>>>> My mSata has two fedora OS. When I boot the system, I am not seeing >>>>> GRUB boot load menu. System straightly booted to one of Fedora OS. >>>>> >>>>> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which >>>>> stops the system indefinitely at boot menu in GRUB2). Still system is not >>>>> stopping at boot menu. >>>>> >>>>> With other vendor BIOS on my board, I am seeing boot menu. I have >>>>> observed they were using GRUB 2.02_Beta version. >>>>> >>>>> So, I have checked out GRUB 2.02_Beta and complied the source which >>>>> produced *grub2.elf*. >>>>> And, I have modified Payload as * Add a Payload* = *An ELF executable >>>>> payload *and given the path of *grub2.elf*. >>>>> >>>>> After flashing this BIOS on my board, I am seeing error message, >>>>> >>>>> *lzma: Decodeing error = 1* >>>>> *Payload not loaded.* >>>>> >>>>> FYR, I have attached my *.config* file, Please view it. >>>>> >>>>> Can you please help me to solve this issue?. >>>>> >>>>> Thanks, >>>>> Dhanasekar >>>>> >>>>> -- >>>>> coreboot mailing list: coreboot(a)coreboot.org >>>>> https://mail.coreboot.org/mailman/listinfo/coreboot >>>>> >>>> >>>> >>> >> >

1 0

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Nico Huber 07 Jun '17

07 Jun '17

Hi Dhanasekar, On 06.06.2017 16:53, Dhanasekar Jaganathan wrote: > Hi All, > > I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by Coreboot. I > am using *GRUB2 *as a Payload. > > In menuconfig, I have selected, > > Add a payload - *GRUB2* > GRUB2 Version - *HEAD*. > > My mSata has two fedora OS. When I boot the system, I am not seeing GRUB > boot load menu. System straightly booted to one of Fedora OS. where do you expect to see the menu? a display? a serial console? In the former case, I expect you have to add a Video BIOS to your coreboot.rom (CONFIG_VGA_BIOS) and configure coreboot to run it (CONFIG_VGA_ROM_RUN). If you use a discrete gfx card, you don't need to add the VBIOS, it would be read from the card. In the latter case, GRUB has to be confi- gured to use the serial port, as Mariusz pointed out. I'm a little confused here, did you add an etc/grub.cfg to the CBFS? You didn't say so but I wouldn't expect it to boot otherwise. If you have, can you please share this grub.cfg. > > In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops > the system indefinitely at boot menu in GRUB2). Still system is not > stopping at boot menu. AFAIK, this file only works as input to `grub-mkconfig`. You'd still have to generate a grub.cfg with it and configure the GRUB payload to use it. > > With other vendor BIOS on my board, I am seeing boot menu. I have observed > they were using GRUB 2.02_Beta version. > > So, I have checked out GRUB 2.02_Beta and complied the source which > produced *grub2.elf*. > And, I have modified Payload as * Add a Payload* = *An ELF executable > payload *and given the path of *grub2.elf*. > > After flashing this BIOS on my board, I am seeing error message, > > *lzma: Decodeing error = 1* > *Payload not loaded.* Could be related to the CBFS_SIZE, see below. Maybe the CBFS got cor- rupted. > > FYR, I have attached my *.config* file, Please view it. You have set CONFIG_ROM_SIZE and CONFIG_CBFS_SIZE to the same value (8MiB). This is wrong. coreboot shares the flash chip with other Intel firmware components (Firmware Descriptor (IFD), ME firmware etc.). Be- side other configuration, the IFD partitions the flash chip in regions. coreboot's CBFS lives in the BIOS region and should be at most of this region's size. You can decode the descriptor with `ifdtool -d ...` (you can find it in util/ifdtool/ in the coreboot source). Hope that helps, Nico

2 1

← Newer
1
...
8
9
10
11
12
13
14
15
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot June 2017