On Thu, 4 May 2023, 22:35 Mantas Kriaučiūnas, <1967...@bugs.launchpad.net>
wrote:
> @juergh maybe it would be better simply reuse debian packaging practice
> for linux-firmware? Please also look at LP bug #1958518 - this issue is
> solved in Debian a long time ago:
>
> metapackage
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
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/1685291
Title:
RFC: virtio and virtio-scsi should be built in
** Description changed:
Combine azure & azure-fde packages
We can generate signed vmlinuz and kernel.efi from the same build.
Thus use the same build for both.
== Plan of action ==
* Extend linux-signed & linux-generate to produce CVM specific package builds.
* Apply that
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Description changed:
Combine azure & azure-fde packages
We can generate signed vmlinuz and kernel.efi from the same build.
Thus use the same build for both.
+
+ == Plan of action ==
+ * Extend linux-signed &
I'm not too sure if updates from sed1991s above are correct
--
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/1991975
Title:
dev file system is mounted without nosuid or noexec
Status in
** Description changed:
In Ubuntu 22.04 generic kernel like 5.15.0-23, efivars file system is
mounted and is visible in the output of mount command, however in Ubuntu
22.04 real-time kernel like 5.15.0-1005-realtime or
5.15.0-1007-realtime, efivars file system is missing. Intel SGX
Public bug reported:
FDE v5.19 edge variant meta packages are incorrectly named
they should just be named `linux-azure-fde-edge`, not `linux-azure-
fde-5.19-edge`.
** Affects: linux-meta-azure-fde-5.19 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Hi Sven & doko,
Nice to hear from you Sven again, you always pop-up on x32 kernel
mailing lists threads, great to hear you use Ubuntu.
Debian also has ports that provide x32 binaries, whereas Ubuntu doesn't.
We did do preliminary work to enable x32 over sixteen years ago in
gutsy, but since then
Public bug reported:
Combine azure & azure-fde packages
We can generate signed vmlinuz and kernel.efi from the same build.
Thus use the same build for both.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are
Note despite the hwe-5.15 obviously picking up all the code changes in
the kernel, this feature will not work in hwe-5.15 in focal, due to lack
of toolchain support. Thus this is a no-op in focal.
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added:
vmlinuz-6.2.0-18-generic is good, so regression introduced in 6.2.0-19
abi, suspecting new apparmor stack
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012136
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
alexsander-souza - if you can make this on per-distro basis that would
be great. Indeed empty (thus apparmor=1) should work on jammy and up,
but yes we can never know. And having it for lunar onwards would be
super nice, because yes overlayfs apparmor things got fixed a while back
and are expected
Lunar kernel will need SRU to be fixed up.
And separately, we could check if we can get rid of apparmor=0 for all
supported releases or not, in next mass release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Now about those bugs, it is true that apparmor and overlayfs used to not
play along.
Depending on support matrix we can attempt to turn apparmor back on.
Equally it is buggy that Ubuntu kernel does not work with apparmor
turned off.
It would be nice to investigate if we can at least enable
** Description changed:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which I
don't believe was part of the 20230319 serial. I don't have access to
the maas server, so I can't directly check any log
horay i managed to reproduce it locally.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/2016908
Title:
Public bug reported:
Split firmware into separate package
* Currently gsp.bin is shipped by nvidia-kernel-common that pulls in
userspace dependencies and is required to match a particular driver
* This prevents co-installing LRM of different nvidia upstream releases
from different kernels,
Note livepatches can only start with the next abi specifically
https://bugs.launchpad.net/kernel-sru-workflow/+bug/2016820 jammy/linux:
5.15.0-71.78 it started building already, and will undergo testing soon.
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Tags added: regression-release
--
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/1988806
Title:
Add
Yes, it is expected for you / Nvidia to update this patch if there is no
other solution.
Please provide patch for v6.2 for lunar & vanilla kernel latest RC.
Ideally also submit it upstream, such that a solution acceptable
upstream is eventually found.
This patch will need to go through acks,
@Tarun Gupta
Is
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=e605d68b8accf43430144999e8206dd8511d135f
still needed in v6.2 kernel. It no longer applies, and there has been a lot of
work by @nvidia.com people on the driver in question
** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe-5.19 (Ubuntu Lunar)
** No longer affects: linux-meta-hwe-5.19 (Ubuntu Kinetic)
** No longer affects: linux-meta-hwe-5.19 (Ubuntu Jammy)
** No longer affects:
it's incorrect to file bugs againt `linux-meta` bugs like these should
be filed against `linux` itself.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
are you sure the dkms module is still needed with the v6.2 kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2013236
Title:
Failed to install bcmwl wireless driver during
Public bug reported:
build_dkms fails
1) if updated dkms is used that changes return code for skip from 9 to 77
2) if MAKEFLAGS are exported that remove implicit variables, which dkms module
submake invocations may require
fix those things for lunar release.
** Affects: linux (Ubuntu)
** Tags removed: block-proposed-lunar
** Changed in: v4l2loopback (Ubuntu)
Status: New => Fix Committed
--
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/2015279
Title:
ftbfs
** Description changed:
ftbfs during kernel build due to dkms changes in lunar
need to revert explicit use of CC= variable, which is now no longer
guaranteed to be exported once again.
causes src:linux to FTBFS
+
+
+ --
+
+ dkms in jammy and lunar are incompatible with each
ah, but that will not fix -a output either, so i guess sort of moot.
--
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/2008084
Title:
Linux image 5.19 cuts off the build date
Status in
imho i find it weird that PREEMPT_DYNAMIC got added and printed by
default in that place on all kernels.
imho PREEMPT_DYNAMIC shouldn't be in the -v output.
is this something we can raise upstream?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi,
8852be/1.0.5 is not a dkms module that Ubuntu ships in the Ubuntu
archive.
Note that Lunar ships v6.2 kernel that contains the following module:
# modinfo
/lib/modules/6.2.0-19-generic/kernel/drivers/net/wireless/realtek/rtw89/rtw89_8852be.ko
filename:
@ahasenack in lunar wireguard dropped depends on neither. Because it is
expected to be built in, and the wireguard-dkms module is out of date,
like a lot.
Please discuss this further with the SRU team on
https://bugs.launchpad.net/ubuntu/kinetic/+source/wireguard/+bug/2008086
as kernel's team
In an ideal world, this would be actually done by upstream Linux
makefiles, i.e. they would have conditional hook to install that file,
and add it as a dep on an appropriate install target (i.e. install-
headers or whatnot).
As all distributions so far manually create snippets like we did as
Marking CONFIG_SCSI_VIRTIO=y enables initrd-less boot on generic kernel,
enabling any Ubuntu installation to be lifted from any hardware and
converted into a VM which will, even with corrupted initrd and missing
modules, be able to boot by default. This is an extremly useful property
to have on
@Steve
These packages only exist in focal.
components-missmatches report is for devel only.
in devel, there is a binary package pattern to automatically seed all kernels,
as in practice we don't have almost any non-main kernels.
I can add these package to focal seeds, but it will not actually
Editing 0.8.3-1ubuntu12.14 changelog seems inappropriate. Whoever is
sponsoring this debdiff, should drop that hung, as long as it doesn't
have any other mistakes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I understand that having it in the root filesystem is too late.
However, I would have thought it would be good enough to have it early
in the initrd, or do you also require output prior to initrd starting?
having it built-in trades wasting RAM for all billions of Ubuntu
instances, and the module
With secureboot, the live session install of that module should trigger
installer questions w.r.t. MOK key enrollment.
Post installer reboot, should trigger MOK interface to complete the mok
key enrollment prior to OS loading.
Once OS is loaded, the driver should work.
--
You received this bug
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-bionic verification-done-focal
verification-done-jammy verification-done-kinetic
** Tags added: kernel-stable-tracking-bug
--
You
Status needs to be set to triaged, and ~ubuntu-archive team needs to be
subscribed. These two things will get this bug into a queue for them to
process.
Also related packages need to be marked as affected too. I.e. meta
** Changed in: linux-xilinx-zynqmp (Ubuntu)
Status: New => Triaged
Public bug reported:
Make kexec work by default on secureboot systems
Lots of people are confused by kexec failing on secureboot systems,
without realising that on Ubuntu one needs to use the option to use a
modern syscall that works on secureboot systems since like forever.
Let's make the mode
Specifically version 390.157-0ubuntu2 needs to be removed on i386 and
armhf
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2008434
Title:
NBS cleanup required in
Public bug reported:
NBS cleanup in lunar-proposed on i386 and armhf
old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384,
nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390,
nvidia-headless-390, nvidia-headless-no-dkms-390,
** Tags added: lunar regression-release
** Changed in: dkms (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2008269
Title:
dkms prevents
Public bug reported:
[ Impact ]
* In kinetic, installing kernel which vendors a dkms module from the
archive allows to still install the same dkms module from the archive,
in an inactive package:
$ sudo apt install linux-virtual zfs-dkms
...
zstd.ko:
Running module version sanity check.
Error!
Public bug reported:
Check abi compatiblity between Lunar and Jammy
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Chan
One should use ubuntu-drivers CLI or Additional Drivers GUI to install
or switch nvidia graphics stacks from one major series to another. It
ensures that correct matching pre-signed kernel drivers are installed
together with the right userspace (with and without gui stacks, as
needed).
--
You
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Description changed:
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#linux-meta
- 1) dm-writeboost broken and abandoned, scheduled for removal in debian.
- Ubuntu RM bug
+ DONE 1)
Kai, open opening this bug report the devel series task at the time
(kinetic) it was marked as fix-released => meaning it's not needed on
v5.19+ kernels.
But it seems, now, we do need this fix (or equivalent) on v5.19+ kernels
right?
Opening kinetic & lunar tasks to investigate.
** Also
Public bug reported:
RM linux-bluefield from jammy-proposed, shipped in PPA instead
Please RM linux-bluefield kernel from jammy-proposed
shipped in the ppa instead for now.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects:
1) changed -1ubuntu1~22.04.0 to -1~ubuntu22.04.0 because
-1ubuntu1~22.04.0 is higher version that is in lunar:
$ dpkg --compare-versions 2.13.8-1ubuntu1~22.04.0 lt 2.13.8-1 && echo "sru
version is lower than devel" || echo "sru version is HIGHER than devel"
sru version is HIGHER than devel
$
the liveapatch service builders are ephemeral and private - as unique
one is setup for every kernel abi build, with matching build-
dependencies, and potentially contains embargoed security updates code.
livepatches are consumed via livepatch clients, with an optional onprem
server. More
The next issue that is still to resolve is around UBSAN -
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003374 it appears that
kpatch is currently incompatible with our kernel configuration that
enables UBSAN.
--
You received this bug notification because you are a member of Kernel
Packages,
kpatch was updated in lunar, and canonical-livepatch-service has a
backport of that in their PPAs to build livepatches on jammy.
** Changed in: kpatch (Ubuntu Jammy)
Status: Confirmed => Invalid
** Changed in: kpatch (Ubuntu Kinetic)
Status: Confirmed => Invalid
--
You received
@roxana for the new upstream version backports, the debdiff is normally
provided against the version that is being backported e.g. relative
2.13.8-1
Also when doing backport / any ubuntu change, the version string must
include ubuntu in it, so something like ~ubuntu22.10.0 is best.
--
You
$ dput ubuntu lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes: Valid signature
from 9B8EC849D5EF70ED
Checking signature on .dsc
gpg:
** Changed in: lttng-modules (Ubuntu)
Status: Invalid => Fix Committed
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Incomplete
** Also affects: lttng-modules (Ubuntu Lunar)
Importance: Undecided
Status: Fix Committed
--
You received this bug
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1980484
Title:
temporarily disable CONFIG_X86_KERNEL_IBT
Status in
v4l2loopback tested 0.12.7-2ubuntu2~22.04.1 to build on ga & hwe kernels
in jammy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991664
Title:
backport dkms fixes to build modules
tl; dr
this has proven to be a bit futile, and instead we went ahead with
changing the default kernel makefiles to default to the correct
toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy
for now.
So the things described here are not strictly even needed in jammy for
now.
** Description changed:
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#linux-meta
1) dm-writeboost broken and abandoned, scheduled for removal in debian.
Ubuntu RM bug
https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605
2) evdi
Public bug reported:
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#linux-meta
1) dm-writeboost broken and abandoned, scheduled for removal in debian.
Ubuntu RM bug
https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605
2) evdi fixed in
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
Use !hypervisor_is_type(X86_HYPER_NATIVE) checks
ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration
-> probably redundant on kvmclock systems
3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age
-> livecd-rootfs should do this in the
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Description changed:
Use !hypervisor_is_type(X86_HYPER_NATIVE) checks
ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration
- -> do this by default on paravirt machines, or potentially kvm only machines
+ ->
Public bug reported:
Use !hypervisor_is_type(X86_HYPER_NATIVE) checks
ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration
-> do this by default on paravirt machines, or potentially kvm only machines
3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age
-> do this by default on
** Changed in: linux-kvm (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1982776
Title:
linux-modules for -kvm does not include dm-crypt
hm, i wonder if this is a u-boot only issue, or lack of running update-
grub.
the preinstalled images / installer media may boot with rootfs
referenced by label; but then they should update to be bootable by-UUID
upon kernel or grub updates; or call to update-grub.
Not sure if we do something
We have a specification for this - https://wiki.ubuntu.com/FSTAB but I
don't know if it needs updating or has regressed somewhere.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.19 in Ubuntu.
$ dput ubuntu firmware-sof_2.0-1ubuntu4.1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1.dsc: Valid signature from
$ dput ubuntu firmware-sof_2.0-1ubuntu4.1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1.dsc: Valid signature from
Which driver is used by untainted generic kernels for the device in
question? Can you attach sosreport, dmesg, etc?
--
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/2004262
Title:
Intel
*** This bug is a security vulnerability ***
Public security bug reported:
[Impact]
New upstream release. This is a database of wireless regulations, and
should updated in all releases to ensure users have the most up-to-date
regulatory information.
[Test Case]
Following reboot after
** Also affects: wireless-regdb (Ubuntu)
Importance: Undecided
Status: New
** Changed in: crda (Ubuntu)
Status: New => Fix Released
** Changed in: crda (Ubuntu Jammy)
Status: New => Fix Released
** Description changed:
Debian has just removed the crda package from the
Public bug reported:
[ Impact ]
* On UEFI platforms, sbverify is used by linux-signed packaging to
check correctness of signing (to ensure that kernel was not signed with
a revoked key by accident).
* Some signed packages are missing such build dependency on arm64
platforms.
[ Test Plan ]
** Summary changed:
- broadcom-sta & bcmwl are duplicates
+ Promote to restricted: broadcom-sta & bcmwl are duplicates
** Changed in: broadcom-sta (Ubuntu)
Status: New => Triaged
** Description changed:
+ Ubuntu archive please promote broadcom-sta from multiverse to
+ restricted.
+
+
@sil2100 marked out test case in the bug report more clearly.
** Description changed:
This is *probably* the wrong package, but it's the best I can figure for
this, so here goes.
Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5,
UEFI, no secure boot. Testing
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=ubiquity
** Also affects: ubiquity (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Jammy)
Importance:
zfs-linux SRUs, should follow the regular SRU testing process which
covers all bases.
In the past we have used these:
[Test Plan]
* autopkgtest pass
* kernel regression zfs testsuite pass
* zsys integration test pass
The first two cover unit, functional, and integration tests. Whilst the
We should SRU these changes to Kinetic too, as they do fixup an issue
which can be hit on kinetic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2002636
Title:
broadcom-sta-dkms
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-jammy
verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-jammy
verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-jammy
verification-done-kinetic
** Tags added: kernel-stable-tracking-bug
--
You received this bug notification because you are a member of
Uploaded to unapproved queue of jammy and kinetic, proposed of lunar.
** Also affects: bcmwl (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: bcmwl (Ubuntu Lunar)
Status: New => Fix Committed
** Changed in: bcmwl (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993318
Title:
ZFS + Encryption installations of Ubuntu Desktop do
Public bug reported:
[ Impact ]
* Revoke & rotate to new signing key
* Update revocations, which match the next Ubuntu shim 15.7
revocations. Specifically - revoke certs that were previously protected
with by-hash revocations, revoke lost/unused certificates.
* Start using advantage2021v1
Public bug reported:
RM obsolete unsupported and no longer used v5.17 kernels
** Affects: linux-allwinner-5.17 (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-meta-oem-5.17 (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-oem-5.17
Public bug reported:
[ Impact ]
* Currently Ubuntu Linux kernel header packages use stock Makefile as
shipped by upstream kernel. During linux kernel package build however
HOSTCC and CC are typically overridden to use explicit complier version
$(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms
Public bug reported:
At the moment fallback pnvm firmware files exists, but are undeclared.
Ensure that if ucode for such devices is copied, that pnvm files are
copied too.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1998841
Title:
firmwar
Our kernel driver supports loading UCODE API versions 39 to 66
inclusive.
Our linux-firmware package, for this SKU variant ships:
./lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode
./lib/firmware/iwlwifi-so-a0-gf-a0-67.ucode
./lib/firmware/iwlwifi-so-a0-gf-a0-68.ucode
I don't quite know why 65 & 66
Currently libunwind-dev is not used on s390x by the kernel build, thus
the runtime dep for libunwind-dev can probably be dropped, will test.
Also not sure why it is at all specified.
** Description changed:
[ Impact ]
- * kpatch upstream has gained support for more architectures which we
** Description changed:
- Kernel live-patch is afaik fully upstream and available for 'all' platforms
(incl. s390x).
- But the kpatch-build tool does only support amd64 as of today.
+ [ Impact ]
+
+ * kpatch upstream has gained support for more architectures which we
+ would like to enable on
Public bug reported:
intel/sof firmware is undeclared by the modules that load it
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Undeclared btusb firmware
btusb.ko can request snprintf(fwname, sizeof(fwname),
"qca/rampatch_usb_%08x.bin", ver_rom); but doesn't declare it as
MODULES_FIRMWARE.
btqca can request lots of qca/ things
** Affects: linux (Ubuntu)
Importance: Undecided
Status:
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
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/1996730
Title:
Missing firmware in kernel snap
Status in linux
Public bug reported:
[ Impact ]
* Previously
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991664 has fixed up
some dkms modules that use makefiles without setting a CC= variable
inside them. However, there is a class of dkms modules that set a CC=
variable inside the makefile, and then
# Setup
apt install software-properties-common ubuntu-dev-tools
add-apt-repository ppa:canonical-kernel-team/ubuntu/ppa
apt install linux-generic linux-generic-wip dkms=2.8.7-2ubuntu2
pull-lp-debs v4l2loopback kinetic
This installs v5.15 and preliminary v5.19 kernels in a jammy chroot, together
Public bug reported:
[ Impact ]
* Recent kernels expose built-in trusted and revoked certificates. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892
* When kernels expose such information, it is prudent to check if the
freshly signed EFI binaries are actually revoked. And fail
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete =>
** Description changed:
[ Impact ]
- * Kernels have a set of builtin trusted and revoked certificates as a bundle
- * It is not very easy to access them, one needs to either download linux
kernel package source code; or boot the kernel look up builtin hashes; and then
find certificates
301 - 400 of 1812 matches
Mail list logo
