On the face of it, I cannot see how this particular commit could in any
way cause that other bug to arise. All it does is to allow the i915
driver to load a particular firmware file, and that too only if it's
explicitly specified on the kernel command line.
I think bug 1777242 needs to be
** Changed in: initramfs-tools
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728238
Title:
update-initramfs not adding i915 GuC firmware for Kaby Lake,
Using the 4.15.0-23-generic kernel from bionic-proposed correctly loads
the GuC firmware as expected:
[1.470927] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin
(v1.1)
[1.483832] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin
(version 2.0)
[1.494403] [drm]
Reverting that commit will address the firmware loading issue for both
kbl and bxt. Although as far as I understand, Intel had cancelled
Broxton, and there are no chips based on it in the market, so it's
basically Kaby Lake users that are affected.
--
You received this bug notification because
** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu)
** Summary changed:
- update-initramfs not adding i915 GuC firmware, firmware fails to load
+ update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails
to load
--
You received this bug notification because you
/lib/firmware/i915/kbl_guc_ver9_14.bin and
/lib/firmware/i915/bxt_guc_ver8_7.bin have been present in linux-
firmware 1.165 onwards.
I believe the patch to remove the MODULE_FIRMWARE entries,
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
6 matches
Mail list logo
