On 09/13/2012 12:26 PM, Gawlas, Julius wrote:
We have the following scenario to deal with:
- we have setup autotest/cobbler ring with several test clients
- in the test pool there are new machines that have hardware requiring firmware
updates, that firmware is not part of the upstream kernel but it is in
git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware
- we get autotest job request with source based kernels (tar.gz2) that are
basically slightly modified upstream kernels (the job submitter git clones from
Linux-stable and makes some modifications to it)
The result is that on the SUT kernel is rebuild and when booting into new
kernel it does not come up bc it is missing necessary firmware.
What is a good way to handle this? Any ideas would be greatly appreciated.
I can tell you about our experience running kvm upstream tests (that
require building kernels based on git). As we run such tests on Fedora,
we prepared a recent kernel-firmware rpm and install it in the box as
part of the test job and that usually solves our problem.
Not sure whether this is a valid solution for you, but I believe it's
worth a try. If not we could consider adding firmware build steps to
autotest kernel build procedure.
Lucas
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
