That's a different issue, LP: #2063365, which only started occurring
after the recent wifi firmware bump
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861338
Title:
RPI4 wifi
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be removed from)
Public bug reported:
While attempting to play music as part of the ISO tests for the release,
while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321
player used by the tests (which has never worked *well* on the older
models, but at least worked) failed with:
[0.029s]
Public bug reported:
The protection-domain-mapper package (and qrtr-tools) are both installed
by default on the Ubuntu Desktop for Raspberry Pi images, thanks to
their inclusion in the desktop-minimal seed for arm64. However, there's
no hardware that they target on these platforms, and the result
** Changed in: linux-raspi (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2038924
Title:
No alsa sound cards on Pi 5
Status
I haven't managed to reproduce this on several systems (pi4 booting from
USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can
come up with a firm reproduction case.
** Changed in: pi-bluetooth (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Public bug reported:
The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the
kernel starts booting under noble (I hope this is only on noble; I only
just noticed this during ISO testing and it's quite possible I missed it
on earlier revisions...).
Specifically, on the 2W (which
This was fixed with version 11 of linux-firmware-raspi in noble; I don't
see a great deal of point in expending the effort to backport this to
mantic, however, so I'll set that to invalid.
** Changed in: linux-firmware-raspi (Ubuntu)
Status: Confirmed => Fix Released
** Changed in:
Public bug reported:
When shutting down Ubuntu noble desktop on my Pi 5, I consistently see
the following kernel errors briefly flash by before the machine shuts
down:
kernel: spl: loading out-of-tree module taints kernel.
kernel: zfs: module license 'CDDL' taints kernel.
kernel: Disabling
I believe this is also "fixed" (or rather wasn't an issue) with the
noble kernel; at least testing the current noble desktop beta image from
an SD card shows an NVMe drive attached to a pimoroni base. I'll mark
this as Fix Released; please feel free to re-open if this re-appears on
the noble
Public bug reported:
Came across something bizarre when investigating the audio situation
with server on the Pi 5 (LP: #2038924). Moving the server images to use
the KMS overlay solves the situation, and would be preferable as it
would eliminate another difference between server and desktop
Public bug reported:
First reported on the Raspberry Pi forums
(https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since
confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT,
which is basically the same board) works happily under RaspiOS on the Pi
5, but not Ubuntu
Indeed -- the Pi isn't compatible with our generic arm64 kernel, so
we'll be sticking with the flavour limit for the time being, and this
does actually reduce our delta with Debian. I've got a couple of other
patches to incorporate into f-k this week, so I'm going to sponsor this
as part of a
Any updates here?
--
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/2033348
Title:
Wireless: Update RTL8852BE wifi driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
rpi-imager currently has no facility to encrypt the image it flashes to
the storage on the Pi (and making such a facility generic enough that it
would fit all potentially interested distros is a daunting task to say
the least), so this isn't valid for rpi-imager.
I *did* add some initial steps
Ah, I remember this old one. We discussed this with upstream and found
the issue was that for that specific firmware, the clm-blob was included
in the firmware blob itself, but the code that loaded firmware blobs
still warned that it couldn't find the external file. That code was
eventually
At this point, we've had all the necessary firmware blobs for numerous
releases and I'm reasonably convinced that the remaining AC wifi issues
are largely related to incorrect regulatory domain, because we don't
provide a friendly way of setting this on desktop (see LP: #1951586 for
more on this).
** Changed in: linux-raspi (Ubuntu)
Importance: Undecided => High
** Also affects: linux-raspi (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu Mantic)
Status: New => Confirmed
** Changed in: linux-raspi (Ubuntu Mantic)
Importance:
** Changed in: ubuntu-release-notes
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
** Changed in: linux-raspi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2037059
Title:
array index out of bounds in brcmfmac driver
Public bug reported:
During ISO testing of the final mantic images on the Pi 5, no ALSA cards
are listed under /proc/asound/cards and (predictably) none of the ALSA
utilities are able to output audio. Is this a DT related issue again?
(reminiscent of LP: #1991254)
** Affects: linux-raspi
The following changes since commit
294374341c622e5c2ffd15712cadabe0dd9865f1:
UBUNTU: Ubuntu-5.15.0-83.92 (2023-08-14 11:05:34 +0200)
are available in the Git repository at:
https://github.com/tdavenvidia/ubuntu_kernel_jammy/pull/3
for you to fetch changes up to
Public bug reported:
DAMBUF is backported using the two series of patches:
First, we need the series of 3 patches at:
https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/
- dma-buf: Fix pin callback comment
- RDMA/umem: Allow pinned dmabuf umem usage
- RDMA/efa: Add
The rpiboot package can be skipped for now; according to upstream the
updated package won't be ready at release. The separate bug LP: #2032178
will track updates if/when I can get the uploaded.
** No longer affects: rpiboot (Ubuntu)
--
You received this bug notification because you are a member
Public bug reported:
Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B
with 4GB or 8GB of RAM (the only two I've tested thus far) causes the
following to show up in dmesg:
[ 10.384021]
[
Public bug reported:
I formatted a new Flash Drive and the process hung. So I unplugged the
drive. Disks App crashed when I did.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic
Public bug reported:
Would it be possible to move the "nbd" kernel module from linux-modules-
extra-raspi into linux-modules-extra? This would enable NBD-based
network boot (which has certain advantages over the NFS-based network
boot more traditional in the Pi world, such as permitting services
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/2033348
Title:
Wireless: Update RTL8852BE wifi driver
Status in
@kobako The full thread of the problem can be seen in
https://lore.kernel.org/linux-
wireless/20230421015357.13940-1-pks...@realtek.com/T/#u
This bug report is mainly a preemptive request to get the latest stable
driver on.
A few error logs below.
* Note: these were not gathered in an Ubuntu
Submitted request to update driver/firmware to latest v0.29 in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348
--
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/2002601
Public bug reported:
Firmware 0.27 was added in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there
has been an update submitted by Realtek which resolves crash issues of
the driver related to DMA.
New firmware file is up in kernel:
** Tags removed: rls-ll-incoming
** Tags added: foundations-todo
--
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/2027847
Title:
Bump minimum /boot size in
Thanks. I see the same behavior (i.e. no warning) with the patch.
I will add the patch 'commit f5451547b8310868f5b5acff7cd4aa7c0267edb3' to
linux-nvidia-6.2 then..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in
Can you try the below commit from linus's "linux" tree and see if the
warning goes away?
commit f5451547b8310868f5b5acff7cd4aa7c0267edb3
Author: Thomas Gleixner
Date: Tue Feb 7 15:16:53 2023 +0100
mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early
--
You received this bug
yeah I suspect that.. there are couple of irq patches in the 6.2.0-1004-nvidia
could be the cause..
I will update here shortly!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
** Changed in: linux-nvidia-6.2 (Ubuntu)
Assignee: (unassigned) => Tushar Dave (tdavenvidia)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2026891
Title:
linux-nvi
As stated above, Ubuntu on ZFS failed to boot after an earlier version
upgrade.
The Jonathon F PPA
(https://launchpad.net/~jonathonf/+archive/ubuntu/zfs) resolved this
problem.
If Ubuntu patches zfs to be compatible, why does this PPA exist?
--
You received this bug notification because you
Public bug reported:
In the lunar release of linux-raspi, despite the boot configuration
enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0
and /dev/i2c-1 devices are missing (they are present in jammy and
kinetic). These are the I2C interfaces present on the GPIO header
Was able to purge the non-working 6.2 kernels with --
sudo dpkg --purge
and then list the 6.2 kernels listed
after finding all the 6.2 linux kernels with
sudo dpkg -l | grep "Linux kernel"
Have not yet tried installing anything beyond 5.19 yet.
--
You received this bug notification because
Same issue here though I don't have any displaylink drivers installed.
Seemed that my upgrade install was interrupted perhaps and no amount of
installing a new kernel either by download and with dpkg -i or using
Ubuntu's mainline yield any success. 6.2 Kernel still shows up when I
reboot and is
Under lunar's 6.2 kernel the situation is the same as kinetic's 5.19
kernel: display output works, but rotation is ignored and touchscreen
input doesn't work.
** Also affects: linux-raspi (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification
As a workaround until the fix lands (and is subsequently back-ported to
the jammy HWE kernel), Koba's test-kernel in comment 36 works nicely.
However, please note that the test kernel is not signed and will require
that you disable secure boot to try it (if it's enabled on your
machine), which may
@Koba I can confirm the 5.19.9000-37-generic kernel from comment 36
fixes the issue for me as well, congratulations!
I agree the 60Hz audio issue ought to be a separate report, but until
that appears a quick side note to this one: my refresh rate is 60Hz and
I have no issues with my audio but I
** Description changed:
CLARIFICATION: Just to avoid any confusion for those coming to this bug
report; the "Jammy: invalid" status above does *not* mean that this bug
doesn't affect jammy -- it does, and the kernel team is aware of this.
All it reflects is that the fix has to go into the
@duxeu To fill in a bit of background here, the AMD folks were emailed
in the background and are of the same opinion.
Personally, I'm not sure the bisect *did* identify that as the commit,
but unfortunately bisection isn't an entirely straight-forward process
when dealing with packages that have
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
>From lspci.txt it appears your GPU is a Radeon RX 550, so this is almost
certainly a duplicate of LP: #2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 & -37
@koba I've tried each of the kernels in comment 25 and I'm afraid it
rather refutes the theory that fdcc4c22b is the culprit:
The latest vanilla kernel (#1) is "good"; HDMI audio works happily. That
suggests (although not conclusively) that fdcc4c22b isn't the culprit as
it presumably includes
** Description changed:
+ CLARIFICATION: Just to avoid any confusion for those coming to this bug
+ report; the "Jammy: invalid" status above does *not* mean that this bug
+ doesn't affect jammy -- it does, and the kernel team is aware of this.
+ All it reflects is that the fix has to go into the
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 & -37 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
I'm *reasonably* certain this is a duplicate of LP: #2009136 as that
covers kernel 5.19.0-35. I don't think there *is* a 5.15.0-35, and the
"reversion to 5.15.0-67" (which is the current 5.15 release) also
@Timo ah I see, sorry for the noise!
--
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/2009136
Title:
No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Status in linux package in
@bpl indeed -- I asked Timo if the targeting should be adjusted in
comment 9 as I wasn't sure if the kernel team wanted to track this
separately over in the hwe package, but given this bug was moved from
that package this one I may as well just add jammy to the affected set.
** Also affects:
Errr, let me try that again from root so it's actually got the caps
output!
** Attachment added: "lspci.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653114/+files/lspci.out
--
You received this bug notification because you are a member of Kernel
Packages,
@kobako the 5.15.9003-68-generic kernel in comment 16 is "good"; HDMI
audio detected and working happily. I'm attaching the requested lspci
output.
** Attachment added: "lspci.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653113/+files/lspci.out
--
You
@kobako the 5.19.9002-34-generic kernel in comment 14 is also "bad"
--
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/2009136
Title:
No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9001-34-generic kernel provided in comment 12 is also
"bad" (same symptoms, same dmesg lines as seen in the -35 kernel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
My apologies; I'm going to mark this as a duplicate of LP: #2009136 even
though that bug was reported later as it's very likely the same issue
(AMD-based card with HDMI audio output), and that seems to be
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is
@kobako the 5.19.9000-34-generic kernel provided in comment 10 is "bad"
(no HDMI audio present, same dmesg lines as seen in the -35 kernel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Timo, this also affects jammy -- should I add that to the targeting,
or is that to be handled separately?
--
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/2009136
Title:
No HDMI audio
Looking through the growing list of duplicates, everyone has an AMD GPU
so this is almost certainly an issue in that driver. The list of cards
affected so far:
* RX570 (mine)
* RX6700 XT (from LP: #2009275)
* RX580 (from LP: #2009276)
* RX6600 (from LP: #2009542)
I'm happy to post any additional
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "pactl-list-5.19.0-35"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651269/+files/pactl-list-5.19.0-35
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "pactl-list-5.19.0-32"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651268/+files/pactl-list-5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "dmesg-5.19.0-35"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651267/+files/dmesg-5.19.0-35
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in
** Attachment added: "dmesg-5.19.0-32"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651266/+files/dmesg-5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in
Public bug reported:
After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
the kernel, I found my HDMI audio output device had disappeared.
Reverting to the -32 release caused it to appear again (hence why I'm
filing the bug against the kernel rather than pulseaudio). I'm
.
===
Date: Tue, 24 Mar 2015 10:54:37 -0700
From: Dave Taht
To: Joseph Salisbury
Cc: Kernel Team
command ran
** Package changed: linux (Ubuntu) => spectacle (Ubuntu)
--
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/170
Title:
Plasma notification setting not honoured
Status in
apport information
** Tags added: apport-collected jammy
** Description changed:
My notification pop-up timeout is set for 1second.
Taking a screenshot with spectacle I expect the pop up to be removed after 1
second.
The pop up stays for 5 seconds which is the default for the
Public bug reported:
My notification pop-up timeout is set for 1second.
Taking a screenshot with spectacle I expect the pop up to be removed after 1
second.
The pop up stays for 5 seconds which is the default for the notification.
reboot/restart of KDE/Plasma makes no difference
System
@vorlon, I just found this ticket, and would like to report that my Intel AX211
wifi card no longer connects via 6ghz with the linux-oem-22.04b. It was
working fine with the 5.15 kernel. I suspect regulatory compliance to be the
issue as all of the 6ghz channels show disabled when running
$
Is there actually an issue in gcc-12 here? Looking at the patch Juerg
linked to, it appears to be a kernel issue only?
--
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/1993120
Title:
ce: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu Lunar)
Assignee: (unassigned) => Dave Jones
So where are we on this folks?
--
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 linux package in Ubuntu:
Alright so that means we either need to push a change to remove noexec
from the kernel init code, or we go ahead with noexec, and give people
on option to remount with exec should they want sgx functionality. I do
think the nosuid flag does still provide some benefit even if we decide
not to
In case anyone is curious conversation is on-going on the kernel-team mailing
list
https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@juliank, is this an aws system? If not there's a good chance that you
are using an initramfs to mount the filesystems. That's definited in
either /etc/init.d/udev or directly out of the init that lives in the
initramfs.
--
You received this bug notification because you are a member of Kernel
Here is a workaround for this issue in case anyone finds this in the
future.
Copy remount_dev.service to /etc/systemd/system
sudo chown root:root /etc/systemd/system/remount_dev.service
sudo systemctl daemon-reload
sudo systemctl enable remount_dev.service
Still I think the kernel patch should
** Information type changed from Private Security to Public Security
** Summary changed:
- dev file system is mounted without nosuid
+ dev file system is mounted without nosuid or noexec
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
+ [ SRU TEMPLATE ]
+ [ Impact ]
+
+ * nosuid, and noexec bits are not set on /dev
+ * This has the potential for nefarious actors to use this as an avenue for
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more
discussion around this.
+ *
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like Kees already found this years ago.
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/
Looks like it was accepted as commit 28f0c335dd4a1 in 5.17. So I think
we should apply this patch and the corresponding set
CONFIG_DEVTMPFS_SAFE=y at least for the
I was hoping to work around this in /etc/init.d/udev, but it looks like that
gets redirected to systemctl via
. lib/lsb/init-functions
** Description changed:
This is similar to
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.
I discovered that my ec2 instances
So far I've only tested focal AWS images, but this may likely exist
elsewhere as well.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
** 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/1991975
Title:
dev file system is mounted without nosuid
** Tags added: foundations-todo
--
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/1990621
Title:
PXE Boot contains wrong suggested link to ISO for live file system
Status in casper
** Tags added: foundations-todo
--
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/1990964
Title:
FTBFS on kinetic
Status in linux package in Ubuntu:
In Progress
Status in strace package
Public bug reported:
During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi
armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no
longer appears in /proc/asound/cards; only the Headphones output (from
the AUX socket on the board) appears.
I checked with the
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1826228
Title:
api3a+ hang when reading
Public bug reported:
On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g.
from http://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/) there is no console output over HDMI. The
"rainbow" boot screen appears as usual, but then remains while the
system continues to
Looks like this is one of the ones moved to the modules-extra package
(this split is kernel specific, and wasn't done on the PC kernel which
probably explains why this adapter works on your PC installation of
Ubuntu Server). If you do the following:
$ sudo apt install linux-modules-extra-raspi
** Also affects: ubuntu-seeds
Importance: Undecided
Status: New
** Changed in: ubuntu-seeds
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
ht
I've finished some research with this on one of the larger Pis (a 400)
for performance measurements, and a memory limited Pi (Zero 2W) for an
idea of the impact on memory usage.
First the performance side of things: the good news is it doesn't make
anything worse, the bad news is it doesn't make
I'm hoping to look into the effects of MULTI_PERCPU on the smaller Pi
platforms (in particular the Pi Zero 2 and 3A+ which each have 512MB of
RAM and, with the arm64 arch, typically have ~250MB free at runtime).
Unfortunately building a local version of the linux-raspi package (just
naively with
I'm having a similar issue in Jammy again with an HDMI connected 2k
monitor. The issue here being that the monitor works on boot up, but
experiences this problem after a few hot plugs. Has someone found a
follow-on ticket similar to this?
--
You received this bug notification because you are a
** Tags added: indeed jammy
--
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/1901470
Title:
[i915] HDMI monitor's native resolution (EDID detailed mode) not
available, defaults to 1080p
** Tags added: indeed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker container creation causes kernel oops on linux-aws
5.13.0.1028.31~20.04.22
Status
1 - 100 of 881 matches
Mail list logo
