| Age | Commit message (Collapse) | Author |
|---|
|
In order to enable secure boot without having to use custom certificates,
we use a shim binary signed by Microsoft. Thus, we must obtain the
shim file before builidng the live image.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Update ACPI enabled leg-kernel commandline arguments.
Signed-off-by: Graeme Gregory <graeme.gregory@linaro.org>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Skip some packages for aarch64. The following packages built
only for x86 architecture
- chipsec
- kexec
- vmcore-dmesg
- bits
Signed-off-by: Naresh Bhat <naresh.bhat@linaro.org>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
As we move to Yocto Project v1.7, changes in the license require
to update the checksum for it.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
|
|
Commit 1034518fa73b742e81f ("image.bbclass: default USE_DEVFS to '1'") sets
USE_DEVFS to "1" so that makedevs is not used to populate the /dev directory.
This because it will be populated by the kernel. However, this is only true
for a final rootfs, not for an initramfs. LUV only uses an initramfs but
still needs to have /dev populated. Thus, set USE_DEVFS as "0".
See further info in the kernel's Documentation/early-userspace/README file.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
|
|
The CHIPSEC test suite was disabled in the commit #af66ed38bad4
because of hang/freeze issues when running on ASUS P8H67-M LE
hardware as described in issue #7.
Chipsec is know to work well on various platform based on
Broadwell and Haswell. It also ran correctly on HP Elite Book
8470p.
But users are starting to ask for this test suite to be included
in the LUV. There's no sense in disabling it entirely if it hangs
on a specific platform as described in issue #7. So let's enable
CHIPSEC for users test out!
Cc: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
|
|
If no file system type is specified when creating partitions using
parted (as is currently the case in the luv-live-image recipe) a default
value is used, which happens to be 83 (Linux).
Brian reports that this is causing the luv-results partition to not be
mounted and displayed correctly on his Windows 7 machine, and that some
of the Windows disk management tools are getting kinda confused.
Specify "fat32" when creating partitions, so that the partition label
matches reality.
Reported-by: Brian Richardson <brian.richardson@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Windows will not mount and display more than one partition on a
removable disk.
Make the results partiion the first partition on the image so that users
are able to easily find the test results. Having this one partition
restriction isn't a problem otherwise, since there's little value in
auto-mounting the other partition (the EFI System Partition) anyway.
Of course, we're assuming firmware is smart enough to find the EFI
System Partition based on the partition table.
Fixes issue #23.
Reported-by: William Leara <williamleara@gmail.com>
Debugged-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Tested-by: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Providing verbose kernel output on the serial console during boot is a
useful way to debug issues. It also provides a much more informative
message of what is currently happening.
Enable both the standard ttyS0 device and ttyPCH0 which is the device
used on the Intel Minnowboard.
Tested-by: Gayatri Kammela <gayatri.kammela@intel.com>
Tested-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Provide a luv splash screen for grub's use, which informs the user that
we're currently running boot tests.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
bits comes with its own version of the grub bootloader, with custom
modules installed as part of the grub image, for example a python module
to interpret the python tests.
We must install this boot loader alongside our default one, along with
the necessary parsers and test runners to extract the results of the
bits tests from userland.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Make sure kernel-efi-warnings is included in the ramfs filesystem.
kerne-efi-warnings is a simple script that analyzes the kernel
messages to search for warnings that the kernel might issue if/when
it finds potential bugs in the UEFI firmware.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
|
|
Change
commit 0c91196fcbb953393b3e2f5623b1edc5b40aa445
Author: Andrea Adami <andrea.adami@gmail.com>
Date: Mon Jan 9 23:46:13 2012 +0100
explicitly splits the packages for kexec and kdump. Thus, rather
than generically install kexec-tools. State explicitly which
tools need to be installed.
kexec is needed to reboot a Linux kernel from Linux. vmcore-dmesg
is needed to extract the dmesg buffer from the /proc/vmcore dump
file.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
This reverts commit fcdb6a8c43159704ba16fe1c56a045fa53053180.
The chipsec tests cause one of my test machines to lockup. It's highly
likely that other people will experience similar issues.
The fact that the tests cause lockup isn't the biggest problem, it's
that there's absolutely zero diagnostic information provided to the
user, so they've no data to report other than "my machine freezes".
Disable the tests for now until we can provide useful ways of diagnosing
lockups.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Add the crashkernel parameter to indicate the kernel to reserve memory
for the kernel and initrd images that will be used in the event of a
crash.
Currently our vmlinux binary created from piggy.o is ~80MB and the
initrd image is ~30MB. This could be accomodated on 128MB. Space is
doubled to allow for future growth.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
|
|
In order to uniquely identify the partition at runtime, specify
a known volume-id.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
|
|
Include the chipsec test suite in this image.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Create a second partition to export the results of the LuvOS test
manager.
The idea behind using a different partition for the results is to avoid
any corruption on the boot partition.
The size of the partition is determined according to the following
assupmtions:
- 500 test cases
- 100 lines of raw results per test case
- 20 lines of persed results per test case
- 80 characters per line
Under such assumptions, 4.5MB of data space are required. As most USB
sticks have much greater capacity, the partition size is doubled to 8MB
to err on the safe side.
TODO: An arbitrary UUID is used for the results partitions. This UUID
must match with the UUID used by the test manager init script to mount
the partition. Thus, it is necessary to obtain the UUID by either
parsing such init script or modifying the UUID in the script
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
We don't need to wait for the default 10 seconds before booting the luv
kernel since the most common use case is people wanting to run the luv
tests, rather than interrupting the grub boot to inject some debugging
options.
Also add the "quiet" kernel parameter to reduce the noise of kernel
messages on the console.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Add psplash to the list of packages we want to install and disable
CONFIG_VT_CONSOLE so that we get a much quieter boot.
The splash screen can be disabled at runtime by adding "psplash=false"
to the kernel parameters.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Having a hard drive image to boot with qemu is fine and dandy but we
really need a bootable image that we can write to removable media and
run on real hardware, not least because that's the thing people will
expect to find on the project website.
bootimg.bbclass provides much of the functionality we need and already
contains code to build a FAT file system image from our rootfs.
The customization occurs in do_create_img() where we construct a
partition table and append the rootfs FAT file system. While scripts
already exist to build this type of image (scripts/contrib/mkefidisk.sh)
they explicitly disallow booting with an initramfs as the only file
system. The initramfs is integral to our boot procedure.
Tested on real UEFI hardware.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Signed-off-by: Rakesh Seethamsetty <rakesh.seethamsetty@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
Ditch busybox in favour of more robust utilities.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
It is not expected to have an excessively large filesystem for the
EFI test suite. Thus, it makes sense to utilize an initramfs that
contains all the tests. Also, this reduce the complexity of the
hardware requirements needed to run the suite on a given system: we
will need only a chunk of RAM.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
|
|
|
Put the core pieces in place for generating a file system image for use
on UEFI platforms.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
Ricardo Neri
Naresh Bhat
Gayatri Kammela
Matt Fleming
Rakesh Seethamsetty
Saurabh Tangri