OK, all Good. Just checking impossible: that you did not have somehow (?) efi/ directory in there (this is NOT anyhow possible, but one only knows).
You should check Mariusz's and mine reply to his @ (actually to you) as well. And try some stuff out there. Please, let us know, Zoran On Wed, Jun 7, 2017 at 6:38 AM, Dhanasekar Jaganathan < [email protected]> 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 < > [email protected]> 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 < >> [email protected]> 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: [email protected] >>> https://mail.coreboot.org/mailman/listinfo/coreboot >>> >> >> >
-- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
