Re: [coreboot] Execute Linux on AMD DB-FT3b-LC through GRUB2
execute in BIOS GRUB the >>>> following (?!): >>>> grub> set root=(hd0,gpt2) >>>> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >>>> grub> initrd /boot/initrd.img-3.13.0-29-generic >>>> grub> boot >>>> >>>> Can you do this with the kernel 4.4??? Exact the same (above) commands? >>>> And from where you do have 3.13? Also as entry in grub.cfg? How/from where? >>>> Or, maybe... You use different HDD/SSD for Coreboot purposes?! >>>> >>>> And if you use the same HDD/SSD, how do you have two different kernels >>>> you are (after all) executing: >>>> [A] Using GRUB2 as Coreboot payload as GRUB 2.02 beta3, executing >>>> kernel 3.13??? >>>> [B] Using GRUB2 (hidden behind MBR on the HDD/SSD) executing kernel >>>> 4.4??? >>>> >>>> I did not get out of these emails the complete picture, I admit... :-( >>>> >>>> From your view where would the overflow / boot problems come from ? >>>>> >>>> >>>> Still not able to answer this question, since I do not have clear >>>> understanding what you actually do? I am trying... >>>> >>>> Thank you, >>>> Zoran >>>> >>>> >>>>> Thank you, >>>>> Grigore >>>>> >>>>> On Mon, Nov 28, 2016 at 6:31 PM, Zoran Stojsavljevic < >>>>> zoran.stojsavlje...@gmail.com> wrote: >>>>> >>>>>> Hello Grigore, >>>>>> >>>>>> I have here some dummy questions (forgive me for my ignorance), but I >>>>>> need to ask them just for the sake of curiosity (maybe, after all, we can >>>>>> get somewhere if I articulate questions in the right direction/right >>>>>> format >>>>>> for this problem): >>>>>> >>>>>> > If I put a proprietary AMI BIOS, GRUB2 works without issue >>>>>> in gfxterm mode and boots Linux without issue. >>>>>> >>>>>> [1] What Linux architecture are you using (32 or 64)? >>>>>> [2] Which Linux distro? >>>>>> [3] Which kernel version? >>>>>> >>>>>> If you put AMI BIOS, the following questions I would like to know: >>>>>> >>>>>> [4] Are you using 32 or 64 BIOS? >>>>>> [5] Which mode are you using for booting (legacy/CSM ON or UEFI/CSM >>>>>> OFF)? >>>>>> [6] In the accordance with [5], what video component you have set >>>>>> with CMOS: vBIOS or GOP driver? >>>>>> >>>>>> Not sure, but it seems to me that you are using too old/outdated >>>>>> GRUB2 version (or maybe I am also mistaken)? >>>>>> [7] Could you tell us, which GRUB2 version you are using? >>>>>> >>>>>> Thank you, >>>>>> Zoran >>>>>> >>>>>> On Mon, Nov 28, 2016 at 7:13 PM, Grigore Lupescu via coreboot < >>>>>> coreboot@coreboot.org> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I am trying to run Linux through the GRUB2 payload. I am not tied to >>>>>>> GRUB2 but it's the only payload that gives me HDMI output (board has no >>>>>>> serial port) using Coreboot and AMD FT3B-LC. >>>>>>> >>>>>>> I have the latest Coreboot sources, have set config accordingly >>>>>>> (e.g. CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), >>>>>>> getting an image on HDMI and the GRUB2 payload is executing. >>>>>>> In GRUB2 payload I seem to have an overflow issue possibly related >>>>>>> to the *vga_text* mode. If I put a proprietary AMI BIOS, GRUB2 >>>>>>> works without issue in gfxterm mode and boots Linux without issue. >>>>>>> >>>>>>> Using Coreboot every time the screen gets full of text, GRUB2 >>>>>>> re-executes. If I though set the terminal_output to cbmemc then commands >>>>>>> would execute but Linux still fails to execute - at the end GRUB2 would >>>>>>> restart. >>>>>>> >>>>>>> Also the GRUB2 payload on Coreboot does see the drive/files and >>>>>>> attempts to execute - I looks like a GRUB2/Coreboot config/code problem. >>>>>>> >>>>>>> I execute the below in GRUB2 (which work on AMI BIOS + GRUB2). >>>>>>> grub> set root=(hd0,gpt2) >>>>>>> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >>>>>>> grub> initrd /boot/initrd.img-3.13.0-29-generic >>>>>>> grub> boot >>>>>>> >>>>>>> 1. Would anyone have any recommendation about the overflow in GRUB2 >>>>>>> payload ? - related to Coreboot. >>>>>>> 2. Any suggestions on booting Linux given this board's limitations >>>>>>> on output (HDMI only) ? >>>>>>> >>>>>>> Thank you, >>>>>>> Grigore >>>>>>> >>>>>>> -- >>>>>>> coreboot mailing list: coreboot@coreboot.org >>>>>>> https://www.coreboot.org/mailman/listinfo/coreboot >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Execute Linux on AMD DB-FT3b-LC through GRUB2
our view where would the overflow / boot problems come from ? >>>> >>> >>> Still not able to answer this question, since I do not have clear >>> understanding what you actually do? I am trying... >>> >>> Thank you, >>> Zoran >>> >>> >>>> Thank you, >>>> Grigore >>>> >>>> On Mon, Nov 28, 2016 at 6:31 PM, Zoran Stojsavljevic < >>>> zoran.stojsavlje...@gmail.com> wrote: >>>> >>>>> Hello Grigore, >>>>> >>>>> I have here some dummy questions (forgive me for my ignorance), but I >>>>> need to ask them just for the sake of curiosity (maybe, after all, we can >>>>> get somewhere if I articulate questions in the right direction/right >>>>> format >>>>> for this problem): >>>>> >>>>> > If I put a proprietary AMI BIOS, GRUB2 works without issue >>>>> in gfxterm mode and boots Linux without issue. >>>>> >>>>> [1] What Linux architecture are you using (32 or 64)? >>>>> [2] Which Linux distro? >>>>> [3] Which kernel version? >>>>> >>>>> If you put AMI BIOS, the following questions I would like to know: >>>>> >>>>> [4] Are you using 32 or 64 BIOS? >>>>> [5] Which mode are you using for booting (legacy/CSM ON or UEFI/CSM >>>>> OFF)? >>>>> [6] In the accordance with [5], what video component you have set with >>>>> CMOS: vBIOS or GOP driver? >>>>> >>>>> Not sure, but it seems to me that you are using too old/outdated GRUB2 >>>>> version (or maybe I am also mistaken)? >>>>> [7] Could you tell us, which GRUB2 version you are using? >>>>> >>>>> Thank you, >>>>> Zoran >>>>> >>>>> On Mon, Nov 28, 2016 at 7:13 PM, Grigore Lupescu via coreboot < >>>>> coreboot@coreboot.org> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I am trying to run Linux through the GRUB2 payload. I am not tied to >>>>>> GRUB2 but it's the only payload that gives me HDMI output (board has no >>>>>> serial port) using Coreboot and AMD FT3B-LC. >>>>>> >>>>>> I have the latest Coreboot sources, have set config accordingly (e.g. >>>>>> CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), getting an >>>>>> image on HDMI and the GRUB2 payload is executing. >>>>>> In GRUB2 payload I seem to have an overflow issue possibly related to >>>>>> the *vga_text* mode. If I put a proprietary AMI BIOS, GRUB2 works >>>>>> without issue in gfxterm mode and boots Linux without issue. >>>>>> >>>>>> Using Coreboot every time the screen gets full of text, GRUB2 >>>>>> re-executes. If I though set the terminal_output to cbmemc then commands >>>>>> would execute but Linux still fails to execute - at the end GRUB2 would >>>>>> restart. >>>>>> >>>>>> Also the GRUB2 payload on Coreboot does see the drive/files and >>>>>> attempts to execute - I looks like a GRUB2/Coreboot config/code problem. >>>>>> >>>>>> I execute the below in GRUB2 (which work on AMI BIOS + GRUB2). >>>>>> grub> set root=(hd0,gpt2) >>>>>> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >>>>>> grub> initrd /boot/initrd.img-3.13.0-29-generic >>>>>> grub> boot >>>>>> >>>>>> 1. Would anyone have any recommendation about the overflow in GRUB2 >>>>>> payload ? - related to Coreboot. >>>>>> 2. Any suggestions on booting Linux given this board's limitations on >>>>>> output (HDMI only) ? >>>>>> >>>>>> Thank you, >>>>>> Grigore >>>>>> >>>>>> -- >>>>>> coreboot mailing list: coreboot@coreboot.org >>>>>> https://www.coreboot.org/mailman/listinfo/coreboot >>>>>> >>>>> >>>>> >>>> >>> >> > -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Execute Linux on AMD DB-FT3b-LC through GRUB2
e a mistake. Forgot to mention - outdated Coreboot > GRUB2 payload. Here is a naive exercise to be done: > Please, program back BIOS into flash and boot your system (Ubuntu 16.04). > Please, stop in GRUB2, after BIOS, and inspect the Ubuntu 16.04 LTS GRUB2 > data. What is the GRUB2 version? > > And, as you have said: you are able (also) to execute in BIOS GRUB the > following (?!): > grub> set root=(hd0,gpt2) > grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 > grub> initrd /boot/initrd.img-3.13.0-29-generic > grub> boot > > Can you do this with the kernel 4.4??? Exact the same (above) commands? > And from where you do have 3.13? Also as entry in grub.cfg? How/from where? > Or, maybe... You use different HDD/SSD for Coreboot purposes?! > > And if you use the same HDD/SSD, how do you have two different kernels you > are (after all) executing: > [A] Using GRUB2 as Coreboot payload as GRUB 2.02 beta3, executing kernel > 3.13??? > [B] Using GRUB2 (hidden behind MBR on the HDD/SSD) executing kernel 4.4??? > > I did not get out of these emails the complete picture, I admit... :-( > > From your view where would the overflow / boot problems come from ? >> > > Still not able to answer this question, since I do not have clear > understanding what you actually do? I am trying... > > Thank you, > Zoran > > >> Thank you, >> Grigore >> >> On Mon, Nov 28, 2016 at 6:31 PM, Zoran Stojsavljevic < >> zoran.stojsavlje...@gmail.com> wrote: >> >>> Hello Grigore, >>> >>> I have here some dummy questions (forgive me for my ignorance), but I >>> need to ask them just for the sake of curiosity (maybe, after all, we can >>> get somewhere if I articulate questions in the right direction/right format >>> for this problem): >>> >>> > If I put a proprietary AMI BIOS, GRUB2 works without issue in gfxterm >>> mode and boots Linux without issue. >>> >>> [1] What Linux architecture are you using (32 or 64)? >>> [2] Which Linux distro? >>> [3] Which kernel version? >>> >>> If you put AMI BIOS, the following questions I would like to know: >>> >>> [4] Are you using 32 or 64 BIOS? >>> [5] Which mode are you using for booting (legacy/CSM ON or UEFI/CSM OFF)? >>> [6] In the accordance with [5], what video component you have set with >>> CMOS: vBIOS or GOP driver? >>> >>> Not sure, but it seems to me that you are using too old/outdated GRUB2 >>> version (or maybe I am also mistaken)? >>> [7] Could you tell us, which GRUB2 version you are using? >>> >>> Thank you, >>> Zoran >>> >>> On Mon, Nov 28, 2016 at 7:13 PM, Grigore Lupescu via coreboot < >>> coreboot@coreboot.org> wrote: >>> >>>> Hello, >>>> >>>> I am trying to run Linux through the GRUB2 payload. I am not tied to >>>> GRUB2 but it's the only payload that gives me HDMI output (board has no >>>> serial port) using Coreboot and AMD FT3B-LC. >>>> >>>> I have the latest Coreboot sources, have set config accordingly (e.g. >>>> CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), getting an >>>> image on HDMI and the GRUB2 payload is executing. >>>> In GRUB2 payload I seem to have an overflow issue possibly related to >>>> the *vga_text* mode. If I put a proprietary AMI BIOS, GRUB2 works >>>> without issue in gfxterm mode and boots Linux without issue. >>>> >>>> Using Coreboot every time the screen gets full of text, GRUB2 >>>> re-executes. If I though set the terminal_output to cbmemc then commands >>>> would execute but Linux still fails to execute - at the end GRUB2 would >>>> restart. >>>> >>>> Also the GRUB2 payload on Coreboot does see the drive/files and >>>> attempts to execute - I looks like a GRUB2/Coreboot config/code problem. >>>> >>>> I execute the below in GRUB2 (which work on AMI BIOS + GRUB2). >>>> grub> set root=(hd0,gpt2) >>>> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >>>> grub> initrd /boot/initrd.img-3.13.0-29-generic >>>> grub> boot >>>> >>>> 1. Would anyone have any recommendation about the overflow in GRUB2 >>>> payload ? - related to Coreboot. >>>> 2. Any suggestions on booting Linux given this board's limitations on >>>> output (HDMI only) ? >>>> >>>> Thank you, >>>> Grigore >>>> >>>> -- >>>> coreboot mailing list: coreboot@coreboot.org >>>> https://www.coreboot.org/mailman/listinfo/coreboot >>>> >>> >>> >> > -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Execute Linux on AMD DB-FT3b-LC through GRUB2
Hello Zoran, [1-3] I am using the latest Ubuntu 16.04 LTS x64 desktop, 4.4 kernel. [4] I don't know exactly if it's x64 or x86. I have no control over AMI BIOS since it's just a binary I flash into the SPI ROM, which supports the board. [5] I boot Linux using legacy mode (in AMI, the Linux was installed for legacy boot on the HDD/SSD which connects via USB - USBtoSATA) [6] I'm not sure. So I have the following checked: - Run VGA Option ROMs, Native Mode - Add a VGA BIOS image -> 3rdparty/blobs.../VBIOS.bin - Set framebuffer resolution (any, without this + above, I have no HDMI output) [7] It's the same one referenced from Coreboot in the external payloads - GRUB 2.02 beta3. >From your view where would the overflow / boot problems come from ? Thank you, Grigore On Mon, Nov 28, 2016 at 6:31 PM, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > Hello Grigore, > > I have here some dummy questions (forgive me for my ignorance), but I need > to ask them just for the sake of curiosity (maybe, after all, we can get > somewhere if I articulate questions in the right direction/right format for > this problem): > > > If I put a proprietary AMI BIOS, GRUB2 works without issue in gfxterm > mode and boots Linux without issue. > > [1] What Linux architecture are you using (32 or 64)? > [2] Which Linux distro? > [3] Which kernel version? > > If you put AMI BIOS, the following questions I would like to know: > > [4] Are you using 32 or 64 BIOS? > [5] Which mode are you using for booting (legacy/CSM ON or UEFI/CSM OFF)? > [6] In the accordance with [5], what video component you have set with > CMOS: vBIOS or GOP driver? > > Not sure, but it seems to me that you are using too old/outdated GRUB2 > version (or maybe I am also mistaken)? > [7] Could you tell us, which GRUB2 version you are using? > > Thank you, > Zoran > > On Mon, Nov 28, 2016 at 7:13 PM, Grigore Lupescu via coreboot < > coreboot@coreboot.org> wrote: > >> Hello, >> >> I am trying to run Linux through the GRUB2 payload. I am not tied to >> GRUB2 but it's the only payload that gives me HDMI output (board has no >> serial port) using Coreboot and AMD FT3B-LC. >> >> I have the latest Coreboot sources, have set config accordingly (e.g. >> CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), getting an image >> on HDMI and the GRUB2 payload is executing. >> In GRUB2 payload I seem to have an overflow issue possibly related to the >> *vga_text* mode. If I put a proprietary AMI BIOS, GRUB2 works without >> issue in gfxterm mode and boots Linux without issue. >> >> Using Coreboot every time the screen gets full of text, GRUB2 >> re-executes. If I though set the terminal_output to cbmemc then commands >> would execute but Linux still fails to execute - at the end GRUB2 would >> restart. >> >> Also the GRUB2 payload on Coreboot does see the drive/files and attempts >> to execute - I looks like a GRUB2/Coreboot config/code problem. >> >> I execute the below in GRUB2 (which work on AMI BIOS + GRUB2). >> grub> set root=(hd0,gpt2) >> grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 >> grub> initrd /boot/initrd.img-3.13.0-29-generic >> grub> boot >> >> 1. Would anyone have any recommendation about the overflow in GRUB2 >> payload ? - related to Coreboot. >> 2. Any suggestions on booting Linux given this board's limitations on >> output (HDMI only) ? >> >> Thank you, >> Grigore >> >> -- >> coreboot mailing list: coreboot@coreboot.org >> https://www.coreboot.org/mailman/listinfo/coreboot >> > > -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] Execute Linux on AMD DB-FT3b-LC through GRUB2
Hello, I am trying to run Linux through the GRUB2 payload. I am not tied to GRUB2 but it's the only payload that gives me HDMI output (board has no serial port) using Coreboot and AMD FT3B-LC. I have the latest Coreboot sources, have set config accordingly (e.g. CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...), getting an image on HDMI and the GRUB2 payload is executing. In GRUB2 payload I seem to have an overflow issue possibly related to the *vga_text* mode. If I put a proprietary AMI BIOS, GRUB2 works without issue in gfxterm mode and boots Linux without issue. Using Coreboot every time the screen gets full of text, GRUB2 re-executes. If I though set the terminal_output to cbmemc then commands would execute but Linux still fails to execute - at the end GRUB2 would restart. Also the GRUB2 payload on Coreboot does see the drive/files and attempts to execute - I looks like a GRUB2/Coreboot config/code problem. I execute the below in GRUB2 (which work on AMI BIOS + GRUB2). grub> set root=(hd0,gpt2) grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda2 grub> initrd /boot/initrd.img-3.13.0-29-generic grub> boot 1. Would anyone have any recommendation about the overflow in GRUB2 payload ? - related to Coreboot. 2. Any suggestions on booting Linux given this board's limitations on output (HDMI only) ? Thank you, Grigore -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Nothing hdmi displayed on FT3B-LC
I can suppress GRUB output with terminal_output. By default terminal_output is set to "vga_text" and could be set to any of: gfxterm, spkmodem, serial, mda_text, cbmemc, audio, vga_text - only cbmemc and vga_text work. If I set the terminal_output to cbmemc I can execute any command and return to default grub output (by blindly setting terminal_output back to "vga_text"). At this point I can't boot Linux - GRUB restarts (execute blindly boot after I set root, linux and initrd) ++ and there appears to be an overflow problem in GRUB command line when having set vga_text output. Any suggestions would be welcomed. Thank you, Grigore -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] Nothing hdmi displayed on FT3B-LC
Hello, I am working on the board AMD FT3B-LC [1] which has support in Coreboot (CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="DB-FT3b-LC"...) - git cloned the latest coreboot repo (last commit master eeaf9e4). I have generated the coreboot.rom either plain or with VGA BIOS activated and nothing gets displayed. (1) Is this to be expected ? (2) According to [2] I also have very limited debug possibilities. Would anyone have any suggestions ? Thank you, Grigore [1] http://cdn-docs.av-iq.com/dataSheet/DB-FT3b-LC_Datasheet.pdf [2] https://www.coreboot.org/pipermail/coreboot/2015-June/080007.html -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
