aboutsummaryrefslogtreecommitdiffstats
path: root/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2016-08-04 13:06:13 +0200
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>2016-08-04 13:12:56 +0200
commitb789a44fd121c9a2a7d754c2a46a8a18d200c103 (patch)
tree61a999fc780b5bfe6c485511797f7fe506cf6b69 /patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch
parent38af865df6bb03eb350dfa4651616d224d6d1716 (diff)
def kernel-flavor: linux-image-generic-lts-xenial
Ubuntu arm64: While keeping kernel 4.2 for Trusty (linux-image-generic-lts-trusty), set 4.4 backported from Xenial (linux-image-generic-lts-xenial) as default kernel for Armband ISO. Xenial kernel 4.4 for Trusty has been tested with: - AMD Softiron; - APM Mustang; - Cavium ThunderX; While at it, remove obsoleted rtc-efi fixes. Notes: - keep 4.2 kernel inside the ISO; - selecting 4.2 kernel may be done via deploy settings, by overriding kernel flavor when calling `fuel-bootstrap`; Related-bug: ARMBAND-48 Change-Id: Ice1f95939f0d7d9491befd20030740850b1a0e61 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch')
-rw-r--r--patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch35
1 files changed, 0 insertions, 35 deletions
diff --git a/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch b/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch
deleted file mode 100644
index b0c32f4f..00000000
--- a/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
-Date: Mon, 9 May 2016 21:46:51 +0200
-Subject: [PATCH] target Ubuntu: Blacklist rtc-efi if not supported.
-
-Older ThunderX and possibly other UEFI-enabled targets do not support
-rtc-efi properly, so they end up filling dmesg with useless
-complaints about not being able to read system time.
-
-Target OS (Ubuntu) deployment already has a snippet that blacklists
-i2c_piix4 in certain scenarios, so provide a similar test for rtc_efi.
----
- cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 | 10 ++++++++--
- 1 file changed, 8 insertions(+), 2 deletions(-)
-
-diff --git a/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 b/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2
-index 253be2d..9758376 100644
---- a/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2
-+++ b/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2
-@@ -49,8 +49,14 @@ cloud-init-per instance resolv_conf_head_nameserver /bin/sh -c 'echo nameserver
- # configure black module lists
- # virt-what should be installed
- if [ ! -f /etc/modprobe.d/blacklist-i2c_piix4.conf ]; then
-- ( (virt-what | fgrep -q "virtualbox") && echo "blacklist i2c_piix4" >> /etc/modprobe.d/blacklist-i2c_piix4.conf || :) && update-initramfs -u -k all
-- modprobe -r i2c_piix4
-+ ( (virt-what | fgrep -q "virtualbox") && \
-+ ( echo "blacklist i2c_piix4" >> /etc/modprobe.d/blacklist-i2c_piix4.conf && \
-+ update-initramfs -u -k all && modprobe -r i2c_piix4 ) || :)
-+fi
-+if [ ! -f /etc/modprobe.d/blacklist-rtc_efi.conf ]; then
-+ ( /bin/cat /sys/class/rtc/rtc0/time > /dev/null 2>&1 ) || \
-+ ( echo "blacklist rtc_efi" >> /target/etc/modprobe.d/blacklist-rtc_efi.conf && \
-+ update-initramfs -u -k all && modprobe -r rtc_efi )
- fi
-
- cloud-init-per instance conntrack_ipv4 /bin/sh -c 'echo nf_conntrack_ipv4 | tee -a /etc/modules'