coreboot June 2017

coreboot@coreboot.org

57 participants
159 discussions

Spi device pci disabled on braswell
by sebastien basset 22 Jun '17

22 Jun '17

Hello, i used same config cyan motherboard for intel braswell.i want use sio spi, gpio multiplexing is configured for SPI, device tree is activated for pci device SPI. I don't see this pci device in coreboot & kernel, can you help me ? -- My configuration: Gpio Multiplexing: 179 V14 SPI1_CLK 1 SPI1_CLK V1P8A 0 (20k PU) 0 180 Y13 SPI1_CS0_N 1 SPI1_CS0_N V1P8A 1 (20k PU) 1 181 Y12 SPI1_CS1_N 1 SPI1_CS1_N V1P8A 1 (20k PU) 1 182 V13 SPI1_MISO 1 SPI1_MISO V1P8A Input (20k PU) Input (20k PD) 183 V12 SPI1_MOSI 1 SPI1_MOSI V1P8A 0 (20k PU) 0 I used mode 1. In device tree of coreboot: register "lpss_acpi_mode" = "0" device pci 1e.5 on end # 8086 228e - SPI 1 device pci 1e.6 on end # 8086 2290 - SPI 2 device pci 1e.7 on end # 8086 22ac - SPI 3 -- In coreboot trace: src/soc/intel/braswell/chip.c/enable_dev ( Intel Braswell SoC ), type: 2 vendor: 0xffff. device: 0xffff class: 0xff Unassigned class subclass: 0xff ??? prog: 0xff revision: 0xff src/soc/intel/braswell/southcluster.c/southcluster_enable_dev ( Intel Braswell SoC ) PCI: Static device PCI: 00:1e.5 not found, disabling it. -- In kernel: # lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 35) 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) 00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:22dc] (rev 35) 00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 35) 00:18.0 DMA controller [0801]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 DMA Controller [8086:22c0] (rev 35) 00:18.1 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #1 [8086:22c1] (rev 35) 00:18.2 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #2 [8086:22c2] (rev 35) 00:18.3 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #3 [8086:22c3] (rev 35) 00:18.4 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #4 [8086:22c4] (rev 35) 00:18.5 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #5 [8086:22c5] (rev 35) 00:18.6 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #6 [8086:22c6] (rev 35) 00:18.7 Serial bus controller [0c80]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO2 I2C Controller #7 [8086:22c7] (rev 35) 00:1b.0 Audio device [0403]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) 00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 35) 00:1c.1 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #2 [8086:22ca] (rev 35) 00:1e.0 DMA controller [0801]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO1 DMA Controller [8086:2286] (rev 35) 00:1e.3 Communication controller [0780]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO1 HSUART Controller #1 [8086:228a] (rev 35) 00:1e.4 Communication controller [0780]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series LPIO1 HSUART Controller #2 [8086:228c] (rev 35) 00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 35) 00:1f.3 SMBus [0c05]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller [8086:2292] (rev 35) 01:00.0 Non-VGA unclassified device [0000]: Altera Corporation Device [1172:e003] (rev 01) 02:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03) In coreboot spi device not found and in kernel, It is the same. -- Sébastien Basset

1 0

Has anyone installed ONIE using coreboot?.
by Dhanasekar Jaganathan 21 Jun '17

21 Jun '17

Hi all, Has anyone installed ONIE using coreboot (on any platform)?. If so, Please share me the steps. I am trying to install ONIE on Accton board which has Cavium switch and Intel Rangeley Atom CPU.. Below, I have mentioned steps which I tried, 1.I have downloaded source ONIE source from ONIE site and built it. 2. Extracted ISO image into USB pendrive. eg. dd if=onie-recovery-x86_64-accton_as5712_54x-r0.iso of=/dev/sdb bs=1M 3. In grub command prompt, >insmod ehci >set root='usb0' >configfile (usb0)/boot/grub/grub.cfg >selected "ONIE Embedded" Observation: ONIE is installing on "dev/sda".( I am thinking it should install on hd0. ). After restart, I am not seeing ONIE in grub menu. Please correct me, If I am wrong. Thanks, Dhanasekar

1 0

New Defects reported by Coverity Scan for coreboot
by scan-admin＠coverity.com 20 Jun '17

20 Jun '17

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 2 new defect(s) introduced to coreboot found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 2 of 2 defect(s) ** CID 1376385: Memory - illegal accesses (RETURN_LOCAL) /src/arch/x86/smbios.c: 122 in smbios_processor_name() ________________________________________________________________________________________________________ *** CID 1376385: Memory - illegal accesses (RETURN_LOCAL) /src/arch/x86/smbios.c: 122 in smbios_processor_name() 116 tmp[j++] = res.edx; 117 } 118 tmp[12] = 0; 119 str = (const char *)tmp; 120 } 121 } >>> CID 1376385: Memory - illegal accesses (RETURN_LOCAL) >>> Using "str", which points to an out-of-scope variable "tmp". 122 return smbios_add_string(start, str); 123 } 124 125 /* this function will fill the corresponding manufacturer */ 126 void smbios_fill_dimm_manufacturer_from_id(uint16_t mod_id, 127 struct smbios_type17 *t) ** CID 1376384: Null pointer dereferences (NULL_RETURNS) /src/northbridge/intel/haswell/raminit.c: 190 in setup_sdram_meminfo() ________________________________________________________________________________________________________ *** CID 1376384: Null pointer dereferences (NULL_RETURNS) /src/northbridge/intel/haswell/raminit.c: 190 in setup_sdram_meminfo() 184 int ddr_frequency; 185 int dimm_size; 186 int ch, d_num; 187 int dimm_cnt = 0; 188 189 mem_info = cbmem_add(CBMEM_ID_MEMINFO, sizeof(struct memory_info)); >>> CID 1376384: Null pointer dereferences (NULL_RETURNS) >>> Dereferencing a pointer that might be null "mem_info" when calling "memset". [Note: The source code implementation of the function has been overridden by a builtin model.] 190 memset(mem_info, 0, sizeof(struct memory_info)); 191 192 addr_decoder_common = MCHBAR32(0x5000); 193 addr_decode_ch[0] = MCHBAR32(0x5004); 194 addr_decode_ch[1] = MCHBAR32(0x5008); 195 ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0… To manage Coverity Scan email notifications for "coreboot(a)coreboot.org", click https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

Re: [coreboot] How to give control to bootable USB
by Dhanasekar Jaganathan 16 Jun '17

16 Jun '17

Hi Zoran, Ok.. I will try that. After adding below menuentry in grub.cfg( , *menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie {* * echo "ONIE: Embedding ONIE ..."* * set gfxpayload=keep* * insmod gzio* * insmod part_msdos* * insmod ext2* * #onie_entry_start* * set root='USB0' * * set isofile='USB0'/onie-recovery-x86_64-accton_as7512_32x-r0.iso* * loopback loop $isofile* * linux (loop)/live/vmlinuz $ONIE_CMDLINE_LINUX boot_reason=embed install_url=file:///lib/onie/onie-updater* * initrd (loop)/live/initrd.xz* * #onie_entry_end* *}* I am getting below error, *error: file `/boot/grub/i386-coreboot/loopback.mod' not found* Actually, my ONIE .iso has* i386-PC*, not *i386-coreboot*. But GRUB is looking for* i386-coreboot*. I am trying to solve this issue. Thanks, Dhanasekar On Fri, Jun 16, 2017 at 1:22 PM, Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com> wrote: > To simplify your tests... > > If you have enough space on your /boot on your HDD, you can do the > following: > > [1] Copy your ONIE-live-XYZ.iso (or whatever the true name is) there from > USB stick to /boot partition; > > [2] Simplify the grub.cfg script like this: > > menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { > echo "ONIE: Embedding ONIE ..." > onie_entry_start > set root='hd0,msdos1' ## hd0 is your HDD, 1 is /boot -> /dev/sda1) > set isofile=/ONIE-live-XYZ.iso ## or whatever your ONIE... .iso image is > named > loopback loop $isofile > *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed > install_url=file:///lib/onie/onie-updater > *initrd (loop)/live/initrd.xz* > onie_entry_end > > If this does work, U R Cool. But you need to have at least size of ~ 2GB > for /boot (assuming your .iso is no more than ~1.5 GB in size). > > This is why I ALWAYS assign to /boot (/dev/sda1) NO LESS that 2GB in > space! ;-) > > Zoran > > On Thu, Jun 15, 2017 at 3:37 PM, Dhanasekar Jaganathan < > jdhanasekarmca(a)gmail.com> wrote: > >> Hi Zoran, >> >> Thanks for the info. >> >> With previously attached grub.cfg + Vendor BIOS, I can able to install >> ONIE from USB. >> But with Coreboot + GRUB2 + previously attached grub.cfg, I am unable to >> install ONIE from USB. >> >> I am going to try your changes, I will let you know. >> >> Thanks, >> Dhanasekar >> >> On Thu, Jun 15, 2017 at 6:51 PM, Zoran Stojsavljevic < >> zoran.stojsavljevic(a)gmail.com> wrote: >> >>> Hello Dhanasekar, >>> >>> This, I guess, is not (entirely) correct: >>> >>> menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { >>> echo "ONIE: Embedding ONIE ..." >>> onie_entry_start >>> *linux /vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed >>> install_url=file:///lib/onie/onie-updater >>> * initrd /initrd.xz* >>> onie_entry_end >>> >>> You should have something similar to the following: >>> >>> menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { >>> echo "ONIE: Embedding ONIE ..." >>> onie_entry_start >>> set root='hdX,msdosY' ## hdX is your USB stick, Y partition, U R >>> booting from, U should find going to GRUB2 monitor (with > prompt) >>> set isofile=/<dir path>/ONIE-live-XYZ.iso ## or whatever your ONIE... >>> .iso image is named >>> loopback loop $isofile >>> *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed >>> install_url=file:///lib/onie/onie-updater >>> *initrd (loop)/live/initrd.xz* >>> onie_entry_end >>> >>> Please, investigate a bit more using google.com! And let us know if you >>> did solve the problem (post the final grub2 menyentry which works for you). >>> >>> Hope this helps to the whole community. ;-) >>> >>> Zoran >>> >>> On Thu, Jun 15, 2017 at 2:33 PM, Dhanasekar Jaganathan < >>> jdhanasekarmca(a)gmail.com> wrote: >>> >>>> Hi Nico, >>>> >>>> Sorry, It is typo. I have tried with *configfile >>>> (usb0)/boot/grub/grub.cfg* only.. >>>> >>>> with a new *boot/grub/grub.cfg*, I am getting following error, >>>> >>>> *error: file '/vmlinuz' not found.* >>>> >>>> *error: you need to load the kernel first. * >>>> >>>> >>>> FYR, I have attached /boot/grub/grub.cfg(which is present in USB). >>>> >>>> Thanks, >>>> Dhanasekar >>>> >>>> >>>> >>>> >>>> >>>> On Thu, Jun 15, 2017 at 4:59 PM, Nico Huber <nico.h(a)gmx.de> wrote: >>>> >>>>> On 15.06.2017 07:31, Dhanasekar Jaganathan wrote: >>>>> > Hi Nico/Taiidan, >>>>> > >>>>> > After entering "*syslinux_configfile (*", when I press *TAB, I* I am >>>>> not >>>>> > seeing anything (nothing is coming).. >>>>> > >>>>> > So, I have tried this command *"syslinux_configfile >>>>> > (usb0)/boot/grub/grub.cfg" *and got the error (Kernel without label). >>>>> >>>>> Read what Taiidan wrote carefully: >>>>> >>>>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>>>> >>>>> For a grub.cfg, it's a plain *configfile* (not syslinux_configfile). >>>>> >>>>> Nico >>>>> >>>>> > >>>>> > My USB ONIE installers has following files, >>>>> > >>>>> > */initrd.xz* >>>>> > >>>>> > */vmlinuz* >>>>> > >>>>> > */boot/boot.cat <http://boot.cat>* >>>>> > >>>>> > */boot/eltorito.img* >>>>> > >>>>> > */boot/grub/gurb.cfg* >>>>> > >>>>> > */boot/i386-PC/ *.mod (Lot of .mod files)* >>>>> > >>>>> > >>>>> > Thanks, >>>>> > Dhanasekar >>>>> > >>>>> > >>>>> > >>>>> > On Thu, Jun 15, 2017 at 5:01 AM, Nico Huber <nico.h(a)gmx.de> wrote: >>>>> > >>>>> >> Hi Dhanasekar, >>>>> >> >>>>> >> On 14.06.2017 11:21, Dhanasekar Jaganathan wrote: >>>>> >>> Hi Taiidan, >>>>> >>> >>>>> >>> My USB ONIE installers don't have "isolinux/syslinux.cfg". It has >>>>> >>> "boot/grub/grub.cfg". >>>>> >>> >>>>> >>> When I try to run "syslinux_configfile (usb0)/boot/grub/grub.cfg" >>>>> in GRUB >>>>> >>> command line, I am getting "*kernel without label*" error. >>>>> >>> >>>>> >>> Please provide your commands >>>>> >> >>>>> >> Taiidan already told you the correct command name (33 lines below). >>>>> You >>>>> >> might have missed it ;) >>>>> >> >>>>> >> Nico >>>>> >> >>>>> >>> >>>>> >>> Thanks, >>>>> >>> Dhanasekar >>>>> >>> >>>>> >>> On Wed, Jun 14, 2017 at 3:22 AM, Taiidan(a)gmx.com <Taiidan(a)gmx.com> >>>>> >> wrote: >>>>> >>> >>>>> >>>> On 06/13/2017 10:22 AM, Dhanasekar Jaganathan wrote: >>>>> >>>> >>>>> >>>> Hi All, >>>>> >>>>> >>>>> >>>>> I am trying to install ONIE from USB which has ONIE installer. >>>>> >> Actually, I >>>>> >>>>> am using GRUB2 as a payload. If Coreboot display list of >>>>> bootable >>>>> >>>>> device,I >>>>> >>>>> can select USB which will install a OS in the hard disk. As I >>>>> >> understood >>>>> >>>>> that Coreboot won't display list of available bootable device >>>>> (not like >>>>> >>>>> vendor bios).I don't know how to give control to bootable USB or >>>>> boot a >>>>> >>>>> bootable USB by coreboot. Can you please help me on this?. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Dhanasekar >>>>> >>>>> >>>>> >>>> Assuming you are booting a standard linux distro iso: >>>>> >>>> syslinux_configfile (*TAB* to see what is available >>>>> >>>> >>>>> >>>> then simply for instance syslinux_configfile >>>>> (usb0,msdos1)/isolinux/ >>>>> >> syslinux.cfg >>>>> >>>> (or w/e) >>>>> >>>> >>>>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>>>> >>>> >>>>> >>>> Ideally you would add a grub cfg to the coreboot image that does >>>>> >> something >>>>> >>>> like load a config file from a specified local disk so that it is >>>>> easy >>>>> >> to >>>>> >>>> update (ie: no re-flashing) instructions for that are on the wiki. >>>>> >>>> >>>>> >>>> SeaBIOS would provide the classic AMI style F12 selection menu, >>>>> but I >>>>> >>>> don't like it due to how many times I have accidentally enabled >>>>> option >>>>> >> rom >>>>> >>>> execution by forgetting to include the configuration file. >>>>> >>>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> >> >>>>> >> >>>>> > >>>>> >>>>> >>>> >>>> -- >>>> coreboot mailing list: coreboot(a)coreboot.org >>>> https://mail.coreboot.org/mailman/listinfo/coreboot >>>> >>> >>> >> >

1 0

Re: [coreboot] How to give control to bootable USB
by Zoran Stojsavljevic 16 Jun '17

16 Jun '17

To simplify your tests... If you have enough space on your /boot on your HDD, you can do the following: [1] Copy your ONIE-live-XYZ.iso (or whatever the true name is) there from USB stick to /boot partition; [2] Simplify the grub.cfg script like this: menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { echo "ONIE: Embedding ONIE ..." onie_entry_start set root='hd0,msdos1' ## hd0 is your HDD, 1 is /boot -> /dev/sda1) set isofile=/ONIE-live-XYZ.iso ## or whatever your ONIE... .iso image is named loopback loop $isofile *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed install_url=file:///lib/onie/onie-updater *initrd (loop)/live/initrd.xz* onie_entry_end If this does work, U R Cool. But you need to have at least size of ~ 2GB for /boot (assuming your .iso is no more than ~1.5 GB in size). This is why I ALWAYS assign to /boot (/dev/sda1) NO LESS that 2GB in space! ;-) Zoran On Thu, Jun 15, 2017 at 3:37 PM, Dhanasekar Jaganathan < jdhanasekarmca(a)gmail.com> wrote: > Hi Zoran, > > Thanks for the info. > > With previously attached grub.cfg + Vendor BIOS, I can able to install > ONIE from USB. > But with Coreboot + GRUB2 + previously attached grub.cfg, I am unable to > install ONIE from USB. > > I am going to try your changes, I will let you know. > > Thanks, > Dhanasekar > > On Thu, Jun 15, 2017 at 6:51 PM, Zoran Stojsavljevic < > zoran.stojsavljevic(a)gmail.com> wrote: > >> Hello Dhanasekar, >> >> This, I guess, is not (entirely) correct: >> >> menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { >> echo "ONIE: Embedding ONIE ..." >> onie_entry_start >> *linux /vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed >> install_url=file:///lib/onie/onie-updater >> * initrd /initrd.xz* >> onie_entry_end >> >> You should have something similar to the following: >> >> menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { >> echo "ONIE: Embedding ONIE ..." >> onie_entry_start >> set root='hdX,msdosY' ## hdX is your USB stick, Y partition, U R >> booting from, U should find going to GRUB2 monitor (with > prompt) >> set isofile=/<dir path>/ONIE-live-XYZ.iso ## or whatever your ONIE... >> .iso image is named >> loopback loop $isofile >> *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed >> install_url=file:///lib/onie/onie-updater >> *initrd (loop)/live/initrd.xz* >> onie_entry_end >> >> Please, investigate a bit more using google.com! And let us know if you >> did solve the problem (post the final grub2 menyentry which works for you). >> >> Hope this helps to the whole community. ;-) >> >> Zoran >> >> On Thu, Jun 15, 2017 at 2:33 PM, Dhanasekar Jaganathan < >> jdhanasekarmca(a)gmail.com> wrote: >> >>> Hi Nico, >>> >>> Sorry, It is typo. I have tried with *configfile >>> (usb0)/boot/grub/grub.cfg* only.. >>> >>> with a new *boot/grub/grub.cfg*, I am getting following error, >>> >>> *error: file '/vmlinuz' not found.* >>> >>> *error: you need to load the kernel first. * >>> >>> >>> FYR, I have attached /boot/grub/grub.cfg(which is present in USB). >>> >>> Thanks, >>> Dhanasekar >>> >>> >>> >>> >>> >>> On Thu, Jun 15, 2017 at 4:59 PM, Nico Huber <nico.h(a)gmx.de> wrote: >>> >>>> On 15.06.2017 07:31, Dhanasekar Jaganathan wrote: >>>> > Hi Nico/Taiidan, >>>> > >>>> > After entering "*syslinux_configfile (*", when I press *TAB, I* I am >>>> not >>>> > seeing anything (nothing is coming).. >>>> > >>>> > So, I have tried this command *"syslinux_configfile >>>> > (usb0)/boot/grub/grub.cfg" *and got the error (Kernel without label). >>>> >>>> Read what Taiidan wrote carefully: >>>> >>>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>>> >>>> For a grub.cfg, it's a plain *configfile* (not syslinux_configfile). >>>> >>>> Nico >>>> >>>> > >>>> > My USB ONIE installers has following files, >>>> > >>>> > */initrd.xz* >>>> > >>>> > */vmlinuz* >>>> > >>>> > */boot/boot.cat <http://boot.cat>* >>>> > >>>> > */boot/eltorito.img* >>>> > >>>> > */boot/grub/gurb.cfg* >>>> > >>>> > */boot/i386-PC/ *.mod (Lot of .mod files)* >>>> > >>>> > >>>> > Thanks, >>>> > Dhanasekar >>>> > >>>> > >>>> > >>>> > On Thu, Jun 15, 2017 at 5:01 AM, Nico Huber <nico.h(a)gmx.de> wrote: >>>> > >>>> >> Hi Dhanasekar, >>>> >> >>>> >> On 14.06.2017 11:21, Dhanasekar Jaganathan wrote: >>>> >>> Hi Taiidan, >>>> >>> >>>> >>> My USB ONIE installers don't have "isolinux/syslinux.cfg". It has >>>> >>> "boot/grub/grub.cfg". >>>> >>> >>>> >>> When I try to run "syslinux_configfile (usb0)/boot/grub/grub.cfg" >>>> in GRUB >>>> >>> command line, I am getting "*kernel without label*" error. >>>> >>> >>>> >>> Please provide your commands >>>> >> >>>> >> Taiidan already told you the correct command name (33 lines below). >>>> You >>>> >> might have missed it ;) >>>> >> >>>> >> Nico >>>> >> >>>> >>> >>>> >>> Thanks, >>>> >>> Dhanasekar >>>> >>> >>>> >>> On Wed, Jun 14, 2017 at 3:22 AM, Taiidan(a)gmx.com <Taiidan(a)gmx.com> >>>> >> wrote: >>>> >>> >>>> >>>> On 06/13/2017 10:22 AM, Dhanasekar Jaganathan wrote: >>>> >>>> >>>> >>>> Hi All, >>>> >>>>> >>>> >>>>> I am trying to install ONIE from USB which has ONIE installer. >>>> >> Actually, I >>>> >>>>> am using GRUB2 as a payload. If Coreboot display list of bootable >>>> >>>>> device,I >>>> >>>>> can select USB which will install a OS in the hard disk. As I >>>> >> understood >>>> >>>>> that Coreboot won't display list of available bootable device >>>> (not like >>>> >>>>> vendor bios).I don't know how to give control to bootable USB or >>>> boot a >>>> >>>>> bootable USB by coreboot. Can you please help me on this?. >>>> >>>>> >>>> >>>>> >>>> >>>>> Thanks, >>>> >>>>> Dhanasekar >>>> >>>>> >>>> >>>> Assuming you are booting a standard linux distro iso: >>>> >>>> syslinux_configfile (*TAB* to see what is available >>>> >>>> >>>> >>>> then simply for instance syslinux_configfile >>>> (usb0,msdos1)/isolinux/ >>>> >> syslinux.cfg >>>> >>>> (or w/e) >>>> >>>> >>>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>>> >>>> >>>> >>>> Ideally you would add a grub cfg to the coreboot image that does >>>> >> something >>>> >>>> like load a config file from a specified local disk so that it is >>>> easy >>>> >> to >>>> >>>> update (ie: no re-flashing) instructions for that are on the wiki. >>>> >>>> >>>> >>>> SeaBIOS would provide the classic AMI style F12 selection menu, >>>> but I >>>> >>>> don't like it due to how many times I have accidentally enabled >>>> option >>>> >> rom >>>> >>>> execution by forgetting to include the configuration file. >>>> >>>> >>>> >>> >>>> >>> >>>> >>> >>>> >> >>>> >> >>>> > >>>> >>>> >>> >>> -- >>> coreboot mailing list: coreboot(a)coreboot.org >>> https://mail.coreboot.org/mailman/listinfo/coreboot >>> >> >> >

1 0

Adding test configurations for jenkins builds
by Martin Roth 16 Jun '17

16 Jun '17

We recently added the ability for anyone to submit a configuration for the jenkins test builds. This will help us to build-test currently untested configurations. To add a new test configuration for jenkins, add a miniconfig for the platform into the coreboot/configs directory. The configuration name must accurately reflect the platform being built: 'config.vendor_board_testname' When adding a new config, it's recommended that you look at the existing files to see what the new config should look like. Steps for adding a config: - Create the config to test: This is done with 'make menuconfig', then by running 'make savedefconfig' to generate the miniconfig which gets saved as the file 'defconfig'. - Get the name for the config: The config will be named as a lowercase version of the Kconfig board name. "config.emulation_qemu_x86_i440fx_testname" for example. You can get it from defconfig with this command: echo "config.$( grep _BOARD defconfig | sed 's|.*_BOARD_||' | sed 's|\=y||' | tr 'A-Z' 'a-z')_" - Copy the defconfig into the configs directory as the new name. - Test the configuration and verify that the board configuration is being built, run abuild from the coreboot directory, and you should see that your updated config gets built. % util/abuild/abuild -t emulation/qemu-i440fx Building config EMULATION_QEMU_X86_I440FX ... EMULATION_QEMU_X86_I440FX built successfully. (took 17s) Building config EMULATION_QEMU_X86_I440FX_DEBUG ... EMULATION_QEMU_X86_I440FX_DEBUG built successfully. (took 10s) Building config EMULATION_QEMU_X86_I440FX_NOSERIAL ... EMULATION_QEMU_X86_I440FX_NOSERIAL built successfully. (took 9s) - Submit a patch with the config Jenkins will test the updated config immediately in that patch Additional notes: - If the saved configuration is named with no test name: 'config.vendor_board' it will be used by jenkins as the default build for that platform. This is useful for getting jenkins to build default configuration that is slightly more advanced than the Kconfig default build for that platform. - The configs that are typically tested by jenkins are VERY simple - they would typically include just the board and vendor and nothing else - what you would get if you ran make menuconfig and JUST changed the vendor and boardname, then saved and exited. - Binaries that are in the blobs repository can be included in the build, but including other files will not work. - The files in the configs/builder directory are not for jenkins. These are for the coreboot build system, which has not yet been completed. They are miniconfig files that will generate actual working ROM files for the platform if the correct blobs are in the specified location (site-local).

1 0

Re: [coreboot] How to give control to bootable USB
by Dhanasekar Jaganathan 15 Jun '17

15 Jun '17

Hi Zoran, Thanks for the info. With previously attached grub.cfg + Vendor BIOS, I can able to install ONIE from USB. But with Coreboot + GRUB2 + previously attached grub.cfg, I am unable to install ONIE from USB. I am going to try your changes, I will let you know. Thanks, Dhanasekar On Thu, Jun 15, 2017 at 6:51 PM, Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com> wrote: > Hello Dhanasekar, > > This, I guess, is not (entirely) correct: > > menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { > echo "ONIE: Embedding ONIE ..." > onie_entry_start > *linux /vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed > install_url=file:///lib/onie/onie-updater > * initrd /initrd.xz* > onie_entry_end > > You should have something similar to the following: > > menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { > echo "ONIE: Embedding ONIE ..." > onie_entry_start > set root='hdX,msdosY' ## hdX is your USB stick, Y partition, U R booting > from, U should find going to GRUB2 monitor (with > prompt) > set isofile=/<dir path>/ONIE-live-XYZ.iso ## or whatever your ONIE... > .iso image is named > loopback loop $isofile > *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed > install_url=file:///lib/onie/onie-updater > *initrd (loop)/live/initrd.xz* > onie_entry_end > > Please, investigate a bit more using google.com! And let us know if you > did solve the problem (post the final grub2 menyentry which works for you). > > Hope this helps to the whole community. ;-) > > Zoran > > On Thu, Jun 15, 2017 at 2:33 PM, Dhanasekar Jaganathan < > jdhanasekarmca(a)gmail.com> wrote: > >> Hi Nico, >> >> Sorry, It is typo. I have tried with *configfile >> (usb0)/boot/grub/grub.cfg* only.. >> >> with a new *boot/grub/grub.cfg*, I am getting following error, >> >> *error: file '/vmlinuz' not found.* >> >> *error: you need to load the kernel first. * >> >> >> FYR, I have attached /boot/grub/grub.cfg(which is present in USB). >> >> Thanks, >> Dhanasekar >> >> >> >> >> >> On Thu, Jun 15, 2017 at 4:59 PM, Nico Huber <nico.h(a)gmx.de> wrote: >> >>> On 15.06.2017 07:31, Dhanasekar Jaganathan wrote: >>> > Hi Nico/Taiidan, >>> > >>> > After entering "*syslinux_configfile (*", when I press *TAB, I* I am >>> not >>> > seeing anything (nothing is coming).. >>> > >>> > So, I have tried this command *"syslinux_configfile >>> > (usb0)/boot/grub/grub.cfg" *and got the error (Kernel without label). >>> >>> Read what Taiidan wrote carefully: >>> >>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>> >>> For a grub.cfg, it's a plain *configfile* (not syslinux_configfile). >>> >>> Nico >>> >>> > >>> > My USB ONIE installers has following files, >>> > >>> > */initrd.xz* >>> > >>> > */vmlinuz* >>> > >>> > */boot/boot.cat <http://boot.cat>* >>> > >>> > */boot/eltorito.img* >>> > >>> > */boot/grub/gurb.cfg* >>> > >>> > */boot/i386-PC/ *.mod (Lot of .mod files)* >>> > >>> > >>> > Thanks, >>> > Dhanasekar >>> > >>> > >>> > >>> > On Thu, Jun 15, 2017 at 5:01 AM, Nico Huber <nico.h(a)gmx.de> wrote: >>> > >>> >> Hi Dhanasekar, >>> >> >>> >> On 14.06.2017 11:21, Dhanasekar Jaganathan wrote: >>> >>> Hi Taiidan, >>> >>> >>> >>> My USB ONIE installers don't have "isolinux/syslinux.cfg". It has >>> >>> "boot/grub/grub.cfg". >>> >>> >>> >>> When I try to run "syslinux_configfile (usb0)/boot/grub/grub.cfg" in >>> GRUB >>> >>> command line, I am getting "*kernel without label*" error. >>> >>> >>> >>> Please provide your commands >>> >> >>> >> Taiidan already told you the correct command name (33 lines below). >>> You >>> >> might have missed it ;) >>> >> >>> >> Nico >>> >> >>> >>> >>> >>> Thanks, >>> >>> Dhanasekar >>> >>> >>> >>> On Wed, Jun 14, 2017 at 3:22 AM, Taiidan(a)gmx.com <Taiidan(a)gmx.com> >>> >> wrote: >>> >>> >>> >>>> On 06/13/2017 10:22 AM, Dhanasekar Jaganathan wrote: >>> >>>> >>> >>>> Hi All, >>> >>>>> >>> >>>>> I am trying to install ONIE from USB which has ONIE installer. >>> >> Actually, I >>> >>>>> am using GRUB2 as a payload. If Coreboot display list of bootable >>> >>>>> device,I >>> >>>>> can select USB which will install a OS in the hard disk. As I >>> >> understood >>> >>>>> that Coreboot won't display list of available bootable device (not >>> like >>> >>>>> vendor bios).I don't know how to give control to bootable USB or >>> boot a >>> >>>>> bootable USB by coreboot. Can you please help me on this?. >>> >>>>> >>> >>>>> >>> >>>>> Thanks, >>> >>>>> Dhanasekar >>> >>>>> >>> >>>> Assuming you are booting a standard linux distro iso: >>> >>>> syslinux_configfile (*TAB* to see what is available >>> >>>> >>> >>>> then simply for instance syslinux_configfile (usb0,msdos1)/isolinux/ >>> >> syslinux.cfg >>> >>>> (or w/e) >>> >>>> >>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>> >>>> >>> >>>> Ideally you would add a grub cfg to the coreboot image that does >>> >> something >>> >>>> like load a config file from a specified local disk so that it is >>> easy >>> >> to >>> >>>> update (ie: no re-flashing) instructions for that are on the wiki. >>> >>>> >>> >>>> SeaBIOS would provide the classic AMI style F12 selection menu, but >>> I >>> >>>> don't like it due to how many times I have accidentally enabled >>> option >>> >> rom >>> >>>> execution by forgetting to include the configuration file. >>> >>>> >>> >>> >>> >>> >>> >>> >>> >> >>> >> >>> > >>> >>> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot >> > >

1 0

Re: [coreboot] How to give control to bootable USB
by Zoran Stojsavljevic 15 Jun '17

15 Jun '17

And, YES, you need to have this menuentry in grub.cfg you are loading... >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg Zoran On Thu, Jun 15, 2017 at 3:21 PM, Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com> wrote: > Hello Dhanasekar, > > This, I guess, is not (entirely) correct: > > menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { > echo "ONIE: Embedding ONIE ..." > onie_entry_start > *linux /vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed > install_url=file:///lib/onie/onie-updater > * initrd /initrd.xz* > onie_entry_end > > You should have something similar to the following: > > menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { > echo "ONIE: Embedding ONIE ..." > onie_entry_start > set root='hdX,msdosY' ## hdX is your USB stick, Y partition, U R booting > from, U should find going to GRUB2 monitor (with > prompt) > set isofile=/<dir path>/ONIE-live-XYZ.iso ## or whatever your ONIE... > .iso image is named > loopback loop $isofile > *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed > install_url=file:///lib/onie/onie-updater > *initrd (loop)/live/initrd.xz* > onie_entry_end > > Please, investigate a bit more using google.com! And let us know if you > did solve the problem (post the final grub2 menyentry which works for you). > > Hope this helps to the whole community. ;-) > > Zoran > > On Thu, Jun 15, 2017 at 2:33 PM, Dhanasekar Jaganathan < > jdhanasekarmca(a)gmail.com> wrote: > >> Hi Nico, >> >> Sorry, It is typo. I have tried with *configfile >> (usb0)/boot/grub/grub.cfg* only.. >> >> with a new *boot/grub/grub.cfg*, I am getting following error, >> >> *error: file '/vmlinuz' not found.* >> >> *error: you need to load the kernel first. * >> >> >> FYR, I have attached /boot/grub/grub.cfg(which is present in USB). >> >> Thanks, >> Dhanasekar >> >> >> >> >> >> On Thu, Jun 15, 2017 at 4:59 PM, Nico Huber <nico.h(a)gmx.de> wrote: >> >>> On 15.06.2017 07:31, Dhanasekar Jaganathan wrote: >>> > Hi Nico/Taiidan, >>> > >>> > After entering "*syslinux_configfile (*", when I press *TAB, I* I am >>> not >>> > seeing anything (nothing is coming).. >>> > >>> > So, I have tried this command *"syslinux_configfile >>> > (usb0)/boot/grub/grub.cfg" *and got the error (Kernel without label). >>> >>> Read what Taiidan wrote carefully: >>> >>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>> >>> For a grub.cfg, it's a plain *configfile* (not syslinux_configfile). >>> >>> Nico >>> >>> > >>> > My USB ONIE installers has following files, >>> > >>> > */initrd.xz* >>> > >>> > */vmlinuz* >>> > >>> > */boot/boot.cat <http://boot.cat>* >>> > >>> > */boot/eltorito.img* >>> > >>> > */boot/grub/gurb.cfg* >>> > >>> > */boot/i386-PC/ *.mod (Lot of .mod files)* >>> > >>> > >>> > Thanks, >>> > Dhanasekar >>> > >>> > >>> > >>> > On Thu, Jun 15, 2017 at 5:01 AM, Nico Huber <nico.h(a)gmx.de> wrote: >>> > >>> >> Hi Dhanasekar, >>> >> >>> >> On 14.06.2017 11:21, Dhanasekar Jaganathan wrote: >>> >>> Hi Taiidan, >>> >>> >>> >>> My USB ONIE installers don't have "isolinux/syslinux.cfg". It has >>> >>> "boot/grub/grub.cfg". >>> >>> >>> >>> When I try to run "syslinux_configfile (usb0)/boot/grub/grub.cfg" in >>> GRUB >>> >>> command line, I am getting "*kernel without label*" error. >>> >>> >>> >>> Please provide your commands >>> >> >>> >> Taiidan already told you the correct command name (33 lines below). >>> You >>> >> might have missed it ;) >>> >> >>> >> Nico >>> >> >>> >>> >>> >>> Thanks, >>> >>> Dhanasekar >>> >>> >>> >>> On Wed, Jun 14, 2017 at 3:22 AM, Taiidan(a)gmx.com <Taiidan(a)gmx.com> >>> >> wrote: >>> >>> >>> >>>> On 06/13/2017 10:22 AM, Dhanasekar Jaganathan wrote: >>> >>>> >>> >>>> Hi All, >>> >>>>> >>> >>>>> I am trying to install ONIE from USB which has ONIE installer. >>> >> Actually, I >>> >>>>> am using GRUB2 as a payload. If Coreboot display list of bootable >>> >>>>> device,I >>> >>>>> can select USB which will install a OS in the hard disk. As I >>> >> understood >>> >>>>> that Coreboot won't display list of available bootable device (not >>> like >>> >>>>> vendor bios).I don't know how to give control to bootable USB or >>> boot a >>> >>>>> bootable USB by coreboot. Can you please help me on this?. >>> >>>>> >>> >>>>> >>> >>>>> Thanks, >>> >>>>> Dhanasekar >>> >>>>> >>> >>>> Assuming you are booting a standard linux distro iso: >>> >>>> syslinux_configfile (*TAB* to see what is available >>> >>>> >>> >>>> then simply for instance syslinux_configfile (usb0,msdos1)/isolinux/ >>> >> syslinux.cfg >>> >>>> (or w/e) >>> >>>> >>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>> >>>> >>> >>>> Ideally you would add a grub cfg to the coreboot image that does >>> >> something >>> >>>> like load a config file from a specified local disk so that it is >>> easy >>> >> to >>> >>>> update (ie: no re-flashing) instructions for that are on the wiki. >>> >>>> >>> >>>> SeaBIOS would provide the classic AMI style F12 selection menu, but >>> I >>> >>>> don't like it due to how many times I have accidentally enabled >>> option >>> >> rom >>> >>>> execution by forgetting to include the configuration file. >>> >>>> >>> >>> >>> >>> >>> >>> >>> >> >>> >> >>> > >>> >>> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot >> > >

1 0

Re: [coreboot] How to give control to bootable USB
by Zoran Stojsavljevic 15 Jun '17

15 Jun '17

Hello Dhanasekar, This, I guess, is not (entirely) correct: menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { echo "ONIE: Embedding ONIE ..." onie_entry_start *linux /vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed install_url=file:///lib/onie/onie-updater * initrd /initrd.xz* onie_entry_end You should have something similar to the following: menuentry "ONIE: Embed ONIE" --class gnu-linux --class onie { echo "ONIE: Embedding ONIE ..." onie_entry_start set root='hdX,msdosY' ## hdX is your USB stick, Y partition, U R booting from, U should find going to GRUB2 monitor (with > prompt) set isofile=/<dir path>/ONIE-live-XYZ.iso ## or whatever your ONIE... .iso image is named loopback loop $isofile *linux (loop)/live/vmlinuz* $ONIE_CMDLINE_LINUX boot_reason=embed install_url=file:///lib/onie/onie-updater *initrd (loop)/live/initrd.xz* onie_entry_end Please, investigate a bit more using google.com! And let us know if you did solve the problem (post the final grub2 menyentry which works for you). Hope this helps to the whole community. ;-) Zoran On Thu, Jun 15, 2017 at 2:33 PM, Dhanasekar Jaganathan < jdhanasekarmca(a)gmail.com> wrote: > Hi Nico, > > Sorry, It is typo. I have tried with *configfile > (usb0)/boot/grub/grub.cfg* only.. > > with a new *boot/grub/grub.cfg*, I am getting following error, > > *error: file '/vmlinuz' not found.* > > *error: you need to load the kernel first. * > > > FYR, I have attached /boot/grub/grub.cfg(which is present in USB). > > Thanks, > Dhanasekar > > > > > > On Thu, Jun 15, 2017 at 4:59 PM, Nico Huber <nico.h(a)gmx.de> wrote: > >> On 15.06.2017 07:31, Dhanasekar Jaganathan wrote: >> > Hi Nico/Taiidan, >> > >> > After entering "*syslinux_configfile (*", when I press *TAB, I* I am not >> > seeing anything (nothing is coming).. >> > >> > So, I have tried this command *"syslinux_configfile >> > (usb0)/boot/grub/grub.cfg" *and got the error (Kernel without label). >> >> Read what Taiidan wrote carefully: >> >> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >> >> For a grub.cfg, it's a plain *configfile* (not syslinux_configfile). >> >> Nico >> >> > >> > My USB ONIE installers has following files, >> > >> > */initrd.xz* >> > >> > */vmlinuz* >> > >> > */boot/boot.cat <http://boot.cat>* >> > >> > */boot/eltorito.img* >> > >> > */boot/grub/gurb.cfg* >> > >> > */boot/i386-PC/ *.mod (Lot of .mod files)* >> > >> > >> > Thanks, >> > Dhanasekar >> > >> > >> > >> > On Thu, Jun 15, 2017 at 5:01 AM, Nico Huber <nico.h(a)gmx.de> wrote: >> > >> >> Hi Dhanasekar, >> >> >> >> On 14.06.2017 11:21, Dhanasekar Jaganathan wrote: >> >>> Hi Taiidan, >> >>> >> >>> My USB ONIE installers don't have "isolinux/syslinux.cfg". It has >> >>> "boot/grub/grub.cfg". >> >>> >> >>> When I try to run "syslinux_configfile (usb0)/boot/grub/grub.cfg" in >> GRUB >> >>> command line, I am getting "*kernel without label*" error. >> >>> >> >>> Please provide your commands >> >> >> >> Taiidan already told you the correct command name (33 lines below). You >> >> might have missed it ;) >> >> >> >> Nico >> >> >> >>> >> >>> Thanks, >> >>> Dhanasekar >> >>> >> >>> On Wed, Jun 14, 2017 at 3:22 AM, Taiidan(a)gmx.com <Taiidan(a)gmx.com> >> >> wrote: >> >>> >> >>>> On 06/13/2017 10:22 AM, Dhanasekar Jaganathan wrote: >> >>>> >> >>>> Hi All, >> >>>>> >> >>>>> I am trying to install ONIE from USB which has ONIE installer. >> >> Actually, I >> >>>>> am using GRUB2 as a payload. If Coreboot display list of bootable >> >>>>> device,I >> >>>>> can select USB which will install a OS in the hard disk. As I >> >> understood >> >>>>> that Coreboot won't display list of available bootable device (not >> like >> >>>>> vendor bios).I don't know how to give control to bootable USB or >> boot a >> >>>>> bootable USB by coreboot. Can you please help me on this?. >> >>>>> >> >>>>> >> >>>>> Thanks, >> >>>>> Dhanasekar >> >>>>> >> >>>> Assuming you are booting a standard linux distro iso: >> >>>> syslinux_configfile (*TAB* to see what is available >> >>>> >> >>>> then simply for instance syslinux_configfile (usb0,msdos1)/isolinux/ >> >> syslinux.cfg >> >>>> (or w/e) >> >>>> >> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >> >>>> >> >>>> Ideally you would add a grub cfg to the coreboot image that does >> >> something >> >>>> like load a config file from a specified local disk so that it is >> easy >> >> to >> >>>> update (ie: no re-flashing) instructions for that are on the wiki. >> >>>> >> >>>> SeaBIOS would provide the classic AMI style F12 selection menu, but I >> >>>> don't like it due to how many times I have accidentally enabled >> option >> >> rom >> >>>> execution by forgetting to include the configuration file. >> >>>> >> >>> >> >>> >> >>> >> >> >> >> >> > >> >> > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot >

1 0

Re: [coreboot] How to give control to bootable USB
by Nico Huber 15 Jun '17

15 Jun '17

On 15.06.2017 07:31, Dhanasekar Jaganathan wrote: > Hi Nico/Taiidan, > > After entering "*syslinux_configfile (*", when I press *TAB, I* I am not > seeing anything (nothing is coming).. > > So, I have tried this command *"syslinux_configfile > (usb0)/boot/grub/grub.cfg" *and got the error (Kernel without label). Read what Taiidan wrote carefully: >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg For a grub.cfg, it's a plain *configfile* (not syslinux_configfile). Nico > > My USB ONIE installers has following files, > > */initrd.xz* > > */vmlinuz* > > */boot/boot.cat <http://boot.cat>* > > */boot/eltorito.img* > > */boot/grub/gurb.cfg* > > */boot/i386-PC/ *.mod (Lot of .mod files)* > > > Thanks, > Dhanasekar > > > > On Thu, Jun 15, 2017 at 5:01 AM, Nico Huber <nico.h(a)gmx.de> wrote: > >> Hi Dhanasekar, >> >> On 14.06.2017 11:21, Dhanasekar Jaganathan wrote: >>> Hi Taiidan, >>> >>> My USB ONIE installers don't have "isolinux/syslinux.cfg". It has >>> "boot/grub/grub.cfg". >>> >>> When I try to run "syslinux_configfile (usb0)/boot/grub/grub.cfg" in GRUB >>> command line, I am getting "*kernel without label*" error. >>> >>> Please provide your commands >> >> Taiidan already told you the correct command name (33 lines below). You >> might have missed it ;) >> >> Nico >> >>> >>> Thanks, >>> Dhanasekar >>> >>> On Wed, Jun 14, 2017 at 3:22 AM, Taiidan(a)gmx.com <Taiidan(a)gmx.com> >> wrote: >>> >>>> On 06/13/2017 10:22 AM, Dhanasekar Jaganathan wrote: >>>> >>>> Hi All, >>>>> >>>>> I am trying to install ONIE from USB which has ONIE installer. >> Actually, I >>>>> am using GRUB2 as a payload. If Coreboot display list of bootable >>>>> device,I >>>>> can select USB which will install a OS in the hard disk. As I >> understood >>>>> that Coreboot won't display list of available bootable device (not like >>>>> vendor bios).I don't know how to give control to bootable USB or boot a >>>>> bootable USB by coreboot. Can you please help me on this?. >>>>> >>>>> >>>>> Thanks, >>>>> Dhanasekar >>>>> >>>> Assuming you are booting a standard linux distro iso: >>>> syslinux_configfile (*TAB* to see what is available >>>> >>>> then simply for instance syslinux_configfile (usb0,msdos1)/isolinux/ >> syslinux.cfg >>>> (or w/e) >>>> >>>> also configfile (ahci0,msdos1)/grub2/grub.cfg to load a grub cfg >>>> >>>> Ideally you would add a grub cfg to the coreboot image that does >> something >>>> like load a config file from a specified local disk so that it is easy >> to >>>> update (ie: no re-flashing) instructions for that are on the wiki. >>>> >>>> SeaBIOS would provide the classic AMI style F12 selection menu, but I >>>> don't like it due to how many times I have accidentally enabled option >> rom >>>> execution by forgetting to include the configuration file. >>>> >>> >>> >>> >> >> >

2 1

← Newer
1
2
3
4
5
6
7
...
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