coreboot June 2017

coreboot@coreboot.org

57 participants
159 discussions

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

07 Jun '17

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 Zoran Stojsavljevic 07 Jun '17

07 Jun '17

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 Zoran Stojsavljevic 07 Jun '17

07 Jun '17

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 < 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 Dhanasekar Jaganathan 07 Jun '17

07 Jun '17

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 Mariusz Szafrański 07 Jun '17

07 Jun '17

Hi, I`m guessing you are on second serial port (ttyS1) on Fedora. If yes try reconfigure GRUB to use second serial port also. Mariusz W dniu 06.06.2017 o 16:53, Dhanasekar Jaganathan pisze: > 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 > >

2 1

ASUS KFSN4-DRE Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand 06 Jun '17

06 Jun '17

The ASUS KFSN4-DRE fails verification for branch master as of commit 00b9f4c4b1cd95a6cafe2b1e66641ff0f113082e The following tests failed: BOOT_FAILURE Commits since last successful test: 00b9f4c mb/*/*/cmos.layout: Make multibyte options byte aligned b40e5c7 Documentation: Describe libgfxinit hook-up See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineering.com> regarding any issues stemming from this notification

3 2

Re: [coreboot] VT-d support
by Nico Huber 06 Jun '17

06 Jun '17

On 05.06.2017 19:47, Zoran Stojsavljevic wrote: >> If you are lucky, you only need to add 20~30 lines to your chipset's code. > > Could you, please, show us an explicit example (of these 20 to 30 lines of > code)?! `src/northbridge/intel/sandybridge/iommu.c` and acpi_fill_dmar() in `src/northbridge/intel/sandybridge/acpi.c`. Nico

2 1

Re: [coreboot] GRUB boot menu is not showing GRUB2
by Zoran Stojsavljevic 06 Jun '17

06 Jun '17

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

GRUB boot menu is not showing GRUB2
by Dhanasekar Jaganathan 06 Jun '17

06 Jun '17

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

1 0

Re: [coreboot] DediProg EM100Pro with Apollo Lake
by Andrey Petrov 06 Jun '17

06 Jun '17

Hi, On 05/31/2017 01:54 AM, Urs Ritzmann wrote: > What flash type were you emulating? I require a 1.8 Volt device with >= 128Mbit size. W25Q128FW, also 1.8v. What application do you use to drive em100? Official one from Dediprog or the open linux one? Also, what em100 firmware# you have, perhaps yours is old? Andrey

2 1

← Newer
1
...
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