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
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 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:
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
** 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
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
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
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
** 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
** Changed in: initramfs-tools (Ubuntu Kinetic)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: initramfs-tools (Ubuntu Jammy)
Assignee: (unassigned) => Dave Jones (waveform)
** Also affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
** No longer
Also affects my Acer Aspire TravelMate Spin B118 on Ubuntu 22.04. The
i2c-i801 workaround from comment 14 above
(https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-5.11/+bug/1931001/comments/14) works nicely.
--
You received this bug notification because you are a member of Kernel
Packages,
Now that jammy's out (which still includes CONFIG_GPIO_SYSFS), let's at
least consider this for kinetic. I would suggest it would sensible to at
least try this in an interim release prior to the next LTS. There will
undoubtedly be things that break, but it's probably better to be aware
of how much
I'm afraid if you're getting undervolt warnings that's almost certainly
the cause of any serious issues like kernel hangs. The lightning bolt
not being visible simply means that the undervolt condition is not
sustained, but nevertheless any such warnings indicate that your power
supply is dropping
I've been unable to replicate this so far; tried with four different
USB-SATA cables attaching boot storage to USB3 on a Pi 4B and a Pi 400;
wifi worked happily in each case. Given this was expired for Eoan (a
couple of years ago) I'll close this as invalid for now; please re-open
if this is still
Argh, I'm an idiot -- had the flashing cable plugged into the micro-USB
while the keyboard was *also* plugged into the USB-A sockets (which I
knew doesn't work and apparently missed when originally debugging this).
Closing as invalid.
** Changed in: linux-raspi (Ubuntu Jammy)
Status: New
Public bug reported:
The official Raspberry Pi touchscreen (the 7" model connected via the
DSI port) does not operate when the KMS overlay is applied (as is the
default on the Ubuntu Desktop for Raspberry Pi images). The display does
operate on RaspiOS Bullseye, also running kernel 5.15, when the
** Changed in: ubuntu-meta (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-image (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
** Changed in: flash-kernel (Ubuntu)
Status: New => Fix Released
--
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/1954757
Title:
Missing overlays/README
Status in
** Also affects: linux-raspi (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: linux-raspi (Ubuntu Jammy)
Closing as we're now using "full" KMS on all supported desktops
** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Public bug reported:
Plugging in a Raspberry Pi Pico board (or several other MCU-based
boards) results in the serial console /dev/ttyACM0 appearing on the
Ubuntu PC desktop, but not on the Ubuntu Pi Desktop as the cdc_acm is
currently in modules-extra.
If there's not too many dependencies
This sounds more like it may be a pi-kernel or pi-gadget issue; I've
added the linux-raspi package (from which the pi-kernel derives), but I
don't think there's a project I can add for the gadget. However, I'll
take a look at this from the gadget perspective.
** Also affects: linux-raspi (Ubuntu)
sktop
seed specifically instead of the raspi-common seed.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: cloud-init (Ubuntu)
Assignee: Dave Jones (waveform) =
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
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/1954757
Title:
Missing overlays/REA
: Undecided
Status: New
** No longer affects: linux-raspi (Ubuntu Focal)
** No longer affects: linux-raspi (Ubuntu Hirsute)
** No longer affects: linux-raspi (Ubuntu Impish)
** Changed in: raspberrypi-userland (Ubuntu Jammy)
Assignee: (unassigned) => Dave Jones (waveform)
--
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-firmware (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Invalid
--
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/1947601
Title:
Cannot start docker container on ubuntu 21.10
Worth noting that this issue only appears to occur when the fkms ("fake"
KMS) overlay is in use on the Ubuntu Desktop for Raspberry Pi images.
Under the kms ("full" KMS) overlay, the audio is fine. While kms is
indeed the default overlay, it is likely (due to LP: #1946368 on impish)
that many may
Public bug reported:
Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
for the Ubuntu Pi pre-installed desktop impish release, the HDMI output
occasionally freezes. A known workaround at this time is to change the
following line in /boot/firmware/config.txt:
@sil2100 sorry - that's my fault for skimming this (and the breaks: bit
too -- that's actually not necessary as the backport re-instates the
postinst installing the binaries to the boot partition; the breaks was
there as later releases ditched the postinst and passed the
responsibility for copying
** Changed in: xwayland (Ubuntu Hirsute)
Status: Confirmed => Invalid
--
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/1909678
Title:
Ubuntu 20.10 Desktop on Pi4B -
This post: https://waldorf.waveform.org.uk/2021/the-pins-they-
are-a-changin.html should explain things rather more completely than I
can here but the TL;DR version is: it would be nice to disable sysfs but
there's *way* too much stuff that would break right now if we did
(mostly Python GPIO
> Thanks for the details. You did address the part about upstreaming the
change to Debian. How important is that notification in practice? If
feels like we should have bluez preinstall on the raspi images if that's
not the case, and if it's pre-install is that really worth the packaging
overhead
Appears to work happily on both hirsute and the latest core 20 beta
image on a 3A+. May have been fixed in a kernel update prior to one of
these.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Also affects: flash-kernel (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: flash-kernel (Ubuntu Hirsute)
Importance: Undecided
Assignee: Dave Jones (waveform
Due to a missing brcmfmac43455-sdio.raspberrypi,4-compute-module.txt
alias in linux-firmware-raspi2. The CM4's we'd encountered so far (and
which had been tested for WiFi compatibility were all requesting
brcmfmac43456-sdio.raspberrypi,4-compute-module.txt (note 43455 vs
43456) but it appears
** Changed in: linux-firmware-raspi2 (Ubuntu Hirsute)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: linux-firmware-raspi2 (Ubuntu Hirsute)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
There's a version of bluez with the patches that I've submitted upstream
built in the following PPA against the hirsute branch (the patch changes
are pretty minimal; basically amounts to removal of the arbitrary
sleep(1) as during December's tests I couldn't find a single platform
that actually
@hujq is there anything unusual about your bluetooth setup? miniuart-bt
overlay or anything like that? I'm unable to replicate the failure here
on a Pi 4 8GB
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it
On Thu, Nov 12, 2020 at 11:11:23AM -, Sebastien Bacher wrote:
>Sorry but I'm reverting that upload for now until the patches are
>properly upstreamed. We have been bitten too often by unforwarded
>changes that create issues or create maintainance burden over the years
>and we currently don't
On Tue, Nov 10, 2020 at 03:12:30PM -, Sebastien Bacher wrote:
>Thanks for the work but it there any work to upstream those changes? I'm
>not happy to carry a sleep(1) hack in our package unless there is a
>strong reason and we are working on a way to replace it by a better
>solution
The
** Description changed:
+ [Impact]
+
+ Without these patches, Bluetooth is inoperable on the recently released
+ Raspberry Pi 400.
+
+ [Test Case]
+
+ * Boot the Ubuntu Desktop for Pi image on a Pi 400.
+ * Start the Settings application and switch to the Bluetooth tab
+ * Verify that
** Summary changed:
- Bluetooth won't activate on the pi 400
+ [SRU] Bluetooth won't activate on the pi 400
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU]
@Daniel could you try out the bluez package from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ?
Should be as simple as doing:
sudo add-apt-repository ppa:waveform/pi-bluetooth
sudo apt update
sudo apt upgrade
The version in that PPA contains
1 - 100 of 174 matches
Mail list logo
