Re: [coreboot] How to give control to bootable USB

[Dhanasekar Jaganathan]

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).

My USB ONIE installers has following files,

*/initrd.xz*

*/vmlinuz*

*/boot/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  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, taii...@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@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] How to give control to bootable USB

[Nico Huber]

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, taii...@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@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] CBFS mounting failure

[Nico Huber]

Hi,

On 14.06.2017 23:23, Gailu Singh wrote:
> Hi Experts,
> 
> We are using grub2 payload.
> 
> When we configure coreboot with CONFIG_CBFS_SIZE and CONFIG_ROM_SIZE to be
> same, grub fails to mount cbfsdisk.

if you work with a modern x86 system that is expected. The flash chip
isn't dedicated to the "BIOS" anymore. In case of an Intel system the
CBFS must not be bigger than the BIOS region of the flash chip, or it
will be overwritten by other firmware parts. Again in case of Intel,
you can use `ifdtool` [1] to decode the flash regions.

Nico

[1] in `util/ifdtool` of the coreboot source tree

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] t420 MCE and crashing with ivy bridge cpu

[Nico Huber]

Hello Marcus,

I guess you are not alone: https://ticket.coreboot.org/issues/121
Looks like the same issue, on a T520 with Ivy Bridge CPU.

According to some reports, the combination was working before. Maybe
it's a regression. The combination is probably not often tested.

Also, as you speak of the flash image as if it were a single entity:
It's not. There are multiple firmwares and configuration blobs that
share the flash chip. You shouldn't flash all of them at once. It
can confuse the Management Engine (ME) and cause random errors. Hard
to trace the issue down then, if you don't know which part of the
flash (or the flashing process itself) causes it. You can check your
coreboot log for ME errors.

Speaking of the ME, it might be possible that you need a version that
supports Ivy Bridge. Just a random guess, I don't have any experience
with the ME firmware shipped with Sandy Bridge.

One last thought, you should make sure that the microcode updates are
applied.

Hope that helps,
Nico


-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] CBFS mounting failure

[Gailu Singh]

Hi Experts,

We are using grub2 payload.

When we configure coreboot with CONFIG_CBFS_SIZE and CONFIG_ROM_SIZE to be
same, grub fails to mount cbfsdisk. We added prints and found that it fails
at following check in grub-core/fs/cbfs.c

  ptr = grub_cpu_to_le32 (ptr);
  header_off = (grub_disk_get_size (disk) << GRUB_DISK_SECTOR_BITS)
+ (grub_int32_t) ptr;

  if (grub_disk_read (disk, 0, header_off,
  sizeof (head), ))
goto fail;

However if we keep margin of min 64KB between CONFIG_ROM_SIZE and
CONFIG_CBFS_SIZE it works perfectly.

Is there any possibility that coreboot mess up cbfs layout when both rom
size and cbfs size are same

Thank you
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] t420 MCE and crashing with ivy bridge cpu

[Marcus Walsh]

Hi,

I'm running a 3630qm in my t420 with coreboot.

When using the original sandybridge cpu, I have no issues.

When using the ivy bridge 3630qm:

On linux, 300 seconds into boot I get 2 machine check exceptions (posted
below). The exceptions indicate an issue with level 2 cache. I ran all the
tests on memtest86 (which also tests cpu caches) and got no errors. I do
not have another board anymore to test the cpu to rule out the possibility
of a hardware issue with the cpu, however the cpu was perfect last time I
used it.

On both Windows 10 and Linux (Debian), after a random amount of time
running, the computer becomes unresponsive and the screen goes black with
some artifacting on the edge of the screen.

This occurs more frequently when running on battery, usually after about 10
minutes. When running on AC, this does not occur for a few hours.

On Windows, I set all the power management to "High performance", disabled
ASPM, and the issue has not occurred since when running on AC, I have yet
to test it properly on battery power.

I ran Linux with pcie_aspm=off, and the issue still occurs.

These issues occur on every coreboot rom I have tried. Including the rom on
the t420 coreboot wiki page.

I'm also using the original t420 battery, and not the extended one, if that
matters.

Questions:

1) What else can I do to figure out if this is indeed a hardware issue or
not?
2) Are there any specific kernel versions or parameters I should try?
3) Are there any coreboot config options I should try?

Any help at all would be really appreciated. I really want to make sure
this is a hardware problem before I shell out for another cpu. The whole
point of installing coreboot was so that I could reuse this cpu.

Here are the MCE's, it is always the same two, CACHE Level-2 Generic Error
on bank 7 and bank 8, and it always occurs 300 seconds after boot.


Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 7
MISC 104086 ADDR fe40
TIME 1496380314 Fri Jun  2 06:11:54 2017
MCG status:
MCi status:
Error overflow
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ee23110a MCGSTATUS 0
MCGCAP c09 APICID 0 SOCKETID 0
CPUID Vendor Intel Family 6 Model 58

Hardware event. This is not a software error.
MCE 1
CPU 0 BANK 8
MISC 104086 ADDR fe00
TIME 1496380314 Fri Jun  2 06:11:54 2017
MCG status:
MCi status:
Error overflow
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ee23110a MCGSTATUS 0
MCGCAP c09 APICID 0 SOCKETID 0
CPUID Vendor Intel Family 6 Model 58
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] t420 MCE and crashing with ivy bridge cpu

[Marcus Walsh]

Hi,

I'm running a 3630qm in my t420 with coreboot.

When using the original sandybridge cpu, I have no issues.

When using the ivy bridge 3630qm:

On linux, 300 seconds into boot I get 2 machine check exceptions (posted
below). The exceptions indicate an issue with level 2 cache. I ran all the
tests on memtest86 (which also tests cpu caches) and got no errors. I do
not have another board anymore to test the cpu to rule out the possibility
of a hardware issue with the cpu, however the cpu was perfect last time I
used it.

On both Windows 10 and Linux (Debian), after a random amount of time
running, the computer becomes unresponsive and the screen goes black with
some artifacting on the edge of the screen.

This occurs more frequently when running on battery, usually after about 10
minutes. When running on AC, this does not occur for a few hours.

On Windows, I set all the power management to "High performance", disabled
ASPM, and the issue has not occurred since when running on AC, I have yet
to test it properly on battery power.

I ran Linux with pcie_aspm=off, and the issue still occurs.

These issues occur on every coreboot rom I have tried. Including the rom on
the t420 coreboot wiki page.

I'm also using the original t420 battery, and not the extended one, if that
matters.

Questions:

1) What else can I do to figure out if this is indeed a hardware issue or
not?
2) Are there any specific kernel versions or parameters I should try?
3) Are there any coreboot config options I should try?

Any help at all would be really appreciated. I really want to make sure
this is a hardware problem before I shell out for another cpu. The whole
point of installing coreboot was so that I could reuse this cpu.

Here are the MCE's, it is always the same two, CACHE Level-2 Generic Error
on bank 7 and bank 8, and it always occurs 300 seconds after boot.


Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 7
MISC 104086 ADDR fe40
TIME 1496380314 Fri Jun  2 06:11:54 2017
MCG status:
MCi status:
Error overflow
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ee23110a MCGSTATUS 0
MCGCAP c09 APICID 0 SOCKETID 0
CPUID Vendor Intel Family 6 Model 58

Hardware event. This is not a software error.
MCE 1
CPU 0 BANK 8
MISC 104086 ADDR fe00
TIME 1496380314 Fri Jun  2 06:11:54 2017
MCG status:
MCi status:
Error overflow
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ee23110a MCGSTATUS 0
MCGCAP c09 APICID 0 SOCKETID 0
CPUID Vendor Intel Family 6 Model 58
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] How to give control to bootable USB

[Dhanasekar Jaganathan]

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

Thanks,
Dhanasekar

On Wed, Jun 14, 2017 at 3:22 AM, taii...@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@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot