** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Noble)
Status: New => Incomplete
** Changed in: linux-firmware (Ubuntu Noble)
Status:
All the fixes are in upstream repository, so there should be no work to
do for Noble once it migrate to upstream HEAD.
--
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/2051636
Title
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
SRU:
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/6 (jammy)
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/8 (mantic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.la
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Is there anything anyone would want to know (or must be told), so we can
anticipate these kinds of issues with Linux/the
Kernel/Mint/ReadyNAS/NetGear/Ubuntu/Debian/Synology/SAMBA/cifs in the
future and prevent another regression ruining all my or any other users'
timestamps next time we run a rsync
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
+ within a few minutes or sometimes even quicker
+
+ [Fix]
+
+ Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and
other prerequisites:
+
Public bug reported:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Please note that
** Description changed:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Pl
** Also affects: systemd (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/1970069
Title:
Annoying boot messages interfering with splash
The userspace part of this bug is coming from our systemd patch:
debian/fsckd-daemon-for-inter-fsckd-communication.patch
In particular where systemd-fsckd.service says:
StandardOutput=journal+console
Is the patch still required at all, or can it be reordered to wait for
Plymouth to splash f
All the fixes are in upstream repository. Should have no work to do for
Noble once it migrates to upstream HEAD.
** Changed in: linux-firmware (Ubuntu Noble)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Public bug reported:
I am not sure that kdump can at all work on ubuntu core.
bootloader integration is very different, and the kernel image types are
very different as follows:
* initramfs/system - lack kexec tooling
* uefi - no kexec support of kernel.efi
* pi - no integration with piboot
* u
Public bug reported:
kdump-gaps: does it work on raspberry-pi with piboot?
I don't see any integration with raspberry-pi using piboot, either
should be automatic, or documentation provided.
** Affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bu
Public bug reported:
kdump-gaps: Does not work on Desktop FDE
similar to azure-cvm & ubuntu core, there is no kexec/kdump support for
kernel.efi
** Affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ke
Public bug reported:
Azure CVM uses kernel.efi which currently lacks kexec capability.
Unless a second vmlinuz image is installed to support kdump only.
** Affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
Public bug reported:
kdump-gaps: does it work with riscv64 u-boot-menu?
I don't see any integration with u-boot-menu on riscv64, and also many
boards have very little RAM not sure it will be ever possible to kdump
the small riscv64 boards
** Affects: kdump-tools (Ubuntu)
Importance: Undecid
You can use the 'fastboot' kernel parameter to bypass the systemd-fsckd
issue. So overall most systems can work around the bug in full using
kernel parameters:
quiet splash loglevel=2 fastboot
After that I've only encountered one weird laptop that refused to stay
silent (even with loglevel=0).
** Also affects: kdump-tools (Ubuntu Noble)
Importance: Medium
Status: Confirmed
** Also affects: kdump-tools (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: kdump-tools (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: kdump-tools
** Tags added: originate-from-2045942
--
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/2048747
Title:
Dell dock station WD22TB4 loses ether dev after reboot/power off
Status in H
Research on StackOverflow suggested to restrict to just the 2.4GHz band
because they noticed the issues might arise from switching bands. I did
that but still seeing the connections drop randomly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.26 in a few hours, and then in
the -proposed repository.
Please help us by testi
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.26 in a few hours, and then in
the -proposed repository.
Please help us by testi
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.26 in a few hours, and then in
the -proposed repository.
Please help us by testi
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.26 in a few hours, and then in
the -proposed repository.
Please help us by testi
Public bug reported:
Hello,
I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is probably
This is a back port of the patch to hwe-6.2-next, conflicts had been in
the section below, as 6.2 does not have FUSE_CREATE_SUPP_GROUP
Initial patch for 6.5
```
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index d66070af145d0..660be31aaabc2 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -
@Mario Limonciello, thank you for help.
I did try the proposed version.
uname -r
6.5.0-17-generic works.
Obviously, this Bug report 2051410 is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867.
--
You received this bug notification because you are a member of Kernel
P
Switching status for Noble to In Progress.
Target release for Noble is 6.8 (which includes fix) but it's not out yet,
status will be changed once 6.8 will be introduced.
** Changed in: linux (Ubuntu Noble)
Status: Invalid => In Progress
--
You received this bug notification because you a
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26
---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: U
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26
---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: U
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26
---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: U
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26
---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: U
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26
---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: U
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Impo
Public bug reported:
I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVers
** Tags removed: need-duplicate-check
--
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/2051705
Title:
package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
bluez package pos
Looks like Michael Larabel has done some analysis for you already :-)
https://www.phoronix.com/news/Ubuntu-Generic-LL-Kernel
--
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/2051342
Title:
AFAIK, the systemd-fsckd patch is still required, but we have vague
plans to get rid of it by making plymouth learn this functionality (i.e.
reading /run/systemd/fsck.progress directly). I have no idea about the
re-ordering, but it would be easy to test with a drop-in config.
** Changed in: system
SRU:
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/9 (jammy)
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/10 (mantic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.l
@colin-king noticed, I just left a thank you message in the article.
I'll still do the tests, but it's nice to see that someone else is
contributing to this!
Another thing that I'd like to measure is to bpftrace the time spent in
the tick handler before and after these changes applied, because we
** Description changed:
+ [SRU Justification]
+
+ BugLink: https://bugs.launchpad.net/bugs/2049220
+
+ [Impact]
+
+ MT7921 - IPv6 no longer working (Not receiving Multicast).
+
+ [Fix]
+
+ Update WiFi/Bluetooth firmware to upstream commits:
+ * WiFI: commit 0a18a7292a66 ("linux-firmware: upda
** Changed in: zfs-linux (Ubuntu Mantic)
Status: New => Fix Released
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.n
** Description changed:
[ Impact ]
- * Multiple data corruption issues have been identified and fixed in
+ * Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs rel
I couldn't find this in the benchmark description on Phoronix, so I'm
assuming the lowlatency kernel was booted with default parameters. Which
means CONFIG_NO_HZ_FULL basically had no effect. This is probably fair
for most users who won't specify `nohz_full` kernel parameter and will
observe the pe
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2051700
Title:
Missing fuse backport: "fuse: add feature flag for expire-only"
Status in linux-hwe-6.2 packag
The request from comment#3 is being handled separately via bug 2051560.
--
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/1613393
Title:
Provide linux-perf package
Status in linux package
This is functionality is going to be important for our customers. RDMA
/ RoCE are used extensively in our clusters, and we're going to run into
more cases where people need to be able to trace the RDMA traffic.
There are other tools in Ubuntu to manage OFED devices and RDMA, so RDMA
support is the
Public bug reported:
```
kernel: Bluetooth: hci0: command 0xfc05 tx timeout
```
This issue started with kernel 6.5. Bluetooth has been broken ever
since. The issue was not present in earlier versions of the kernel.
```
$ uname -a
Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Public bug reported:
Installing some python packages (numpy, matplotlib, pandas) and this
occurred. New Ubuntu install on pretty old laptop (Dell Latitude E6420)
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1
ProcVersionSignatur
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218416.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
@andysem correct, without `nohz_full` specified at boot
CONFIG_NO_HZ_FULL has no effect, except for the little extra overhead
that it's adding to the tick handler (there is still some overhead with
this option enabled, even if it's not used). That's why I'd like to
measure the time spent in some of
https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
the-24-04-noble-numbat-release/41958/2
Once we have a 6.8 kernel available for Noble, test that and then we can
just close this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
the-24-04-noble-numbat-release/41958/2
Once we have a 6.8 kernel available for Noble, test that and then we can
just close this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Excellent!
--
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/2045796
Title:
Update bnxt_en with bug fixes and support for Broadcom 5760X network
adapters
Status in linux package in Ubunt
Reopening for Jammy as the bug is not really fixed but the previous
commits reverted and the bot apparently looks at the bug references in
the changes file.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a
Do we need to revert the commits in Mantic as well?
--
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/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
For the Stress-NG 0.16.04: pts/stress-ng-1.11.0 [Test: Socket Activity]
I get:
6633.31 Bogo Ops/s on a 1000Hz kernel. 0.9% improvement.
6572.92 Bogo Ops/s on a 250 Hz kernel.
I did this in a hurry, and will re-test tonight or tomorrow.
--
You received this bug notification because you are a mem
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Mantic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Public bug reported:
Recently a patch has been accepted on the Linux Kernel regarding the TCP
stack which fix an additional +40ms latency on ARM64 CPU architecture
without impacting other CPU types.
More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi..
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2047853
Title:
Public bug reported:
My system works fine using vmlinuz-5.15.0-92-generic. When I run
software update and the new kernel vmlinuz-6.5.0-15-generic is installed
I no longer have a dual monitor system. This is the second time this has
happened and I have to return to a prior kernel version to get the
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:
I gave this another spin today with 6.5.0-17-generic #17~22.04.1 and the
LRM modules of the 535 driver (6.5.0-17.17~22.04.1+1 of linux-modules-
nvidia-535-server-generic-hwe-22.04) on our Altra system with 2x L4 GPUs
and the same problem exists as with the DKMS modules:
[ 39.437849] watchdog: BU
Public bug reported:
With the lowlatency kernel, if I specify "nohz_full=1-15" boot parameter
then CPU frequency scaling doesn't work for the logical cores 1-15. That
is, only logical core 0 shows varying CPU frequency in its
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all other
co
While testing locally, I have found this problem:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-
hwe-6.5/+bug/2051733
If this is indeed a valid bug and not something weirdly specific to my
system, I'd say `nohz_full` is non-functional.
--
You received this bug notification be
JFYI
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 [1] is
reported to fix issues that were found in 36 in [2].
[1]
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/5217b76bed90ae86d5f3fe9a5f4e2301868cdd02
[2] https://bugzilla.kernel.org/show_bug.cgi?id=217239
** Bug wat
--- Comment From cha...@us.ibm.com 2024-01-30 16:28 EDT---
Is there an update from Canonical please? Can we provide any further
information or trace to help diagnose this issue ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1008.8
---
linux-nvidia-tegra-igx (5.15.0-1008.8) jammy; urgency=medium
* jammy/linux-nvidia-tegra-igx: 5.15.0-1008.8 -proposed tracker (LP:
#2049526)
* apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
-
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1021.21
---
linux-nvidia-tegra (5.15.0-1021.21) jammy; urgency=medium
* jammy/linux-nvidia-tegra: 5.15.0-1021.21 -proposed tracker (LP:
#2049525)
* apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
- NVIDIA:
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1021.21
---
linux-nvidia-tegra (5.15.0-1021.21) jammy; urgency=medium
* jammy/linux-nvidia-tegra: 5.15.0-1021.21 -proposed tracker (LP:
#2049525)
* apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
- NVIDIA:
This Bug report is a duplicate of :
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2051410
Bug solved by proposed version 6.5.0-17-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubunt
Okay Bug Bot, updated.
** Also affects: linux-meta-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051612
Title:
Public bug reported:
The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone has the fix
--
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/2008157
Title:
[SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace
multiple times on Ubuntu 22.04.1 OS during boot
Sta
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051741/+attachment/5743702/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Still no update, it's apparently a very low priority to be looked at.
--
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/1988023
Title:
Could not switch uppercase/lowercase by using keyboard
Hi. I'm sorry for left-out details. This is my first time reporting a bug.
The issue occurs when using a Raspberry Pi mouse plugged into a DELL
Latitude 3510 machine running Ubuntu 23.10.
On Tue, Jan 30, 2024 at 12:55 AM Daniel van Vugt <2051...@bugs.launchpad.net>
wrote:
> Also you don't seem to
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
--
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/2051457
Title:
Jammy 22.04.3 gcc compiler no longer builds module
I am also the author of the Plymouth feature that parses and renders the
fsck progress. What I think isn't being communicated here is that it's
currently useless on startup. Because Plymouth doesn't start rendering
until well after the fsck has already happened. See also bug 1869655.
--
You recei
Oh wait, we've been through something very like this before
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
a judicious application of flock may be the most correct solution
available.
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Changed in: plymouth (Ubuntu)
Status: Invalid => 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/1970069
Title:
Annoying boot messages interfering with splash screen
I now expect the kernel patch would change before it gets proposed to
dri-devel. In particular the primary delay doesn't need to be
configurable (or even finite?), and the secondary delay probably doesn't
need to be more than zero. But the feature would still be gated on the
"splash" kernel paramet
It looks like the installation might have succeeded and just requires a
reboot. The error was:
Failed to start bluetooth.service: Unit bluetooth.service failed to load
properly, please adjust/correct and reload service manager: File exists
** Summary changed:
- package bluez 5.68-0ubuntu1.1 fail
You have been subscribed to a public bug:
n/a
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-session-bin 42.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5C
Please check to see if the kernel is getting the button events by
running:
sudo apt install evtest
sudo evtest
--
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/2051617
Title:
Raspberr
The log in comment #6 seems to show it's a problem in the nouveau kernel
driver preventing graphics from starting up:
ene 30 11:03:31 localhost kernel: nouveau :01:00.0: timeout
...
ene 30 11:03:31 localhost kernel: nouveau :01:00.0:
fifo:c0:0001:0001:[gnome-shell[1853]] vctx 0[gr]: -
Have you already looked at everything Fedora is doing in this area?
They already have simpledrm; but from what you described I would have
thought they should still lose the fbcon race.
Is it just that they don't have systemd-fsckd patch? I would think they
still end up showing ERR/WARN kernel mes
> But the feature would still be gated on the "splash" kernel parameter
which is Plymouth-specific and may cause pushback from kernel
developers.
If the patch is the way you go another idea for you is to use the
"quiet" keyword to key off instead for this behavior which is already
used by the kern
"splash" is more appropriate than "quiet" (unfortunately) because we
would delay framebuffer takeover to the same event (primary DRM startup)
as Plymouth does.
I would also like to know why our Plymouth doesn't render on SimpleDRM
even when it's available (tested in bug 1965303). I don't really kn
On Tue, Jan 30, 2024 at 6:21 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Oh wait, we've been through something very like this before
> https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
> a judicious application of flock may be the most correct solution
> a
I verified on 6.5.0-17 mantic kernel built by myself and it passed. @Max
was trying to verify with the proposed mantic 6.5.0-17 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs
> I don't really know if Fedora does that better or they just failed to
notice the bug.
I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in
Fedora with simpledrm; never see the console. That's why I was thinking
something might be missing and worth looking at.
* Fedora doe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-lowlatency-hwe-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency-hwe-6.5
I have this problem as well. I've made multiple approaches trying to
install the stock package for CUDA:
cuda-repo-ubuntu2204-12-1-local_12.1.1-530.30.02-1_amd64.deb
but had problems with the 530 Nvidia driver. Got suggestions to try to
install the 535 Nvidia driver first so that the 530 driver
on MYBY-PIL-C4_202309-32142, install kernel >= 6.5.0-17-generic.
1. install mantic
2. enable proposed
3. $ sudo apt update
4. $ sudo apt dist-upgrade
5. $ sudo rm /var/lib/alsa/asound.state
6. # echo b > /proc/sysrq-trigger
7. $ amixer -c 1 name='PGA2.0 2 Master Capture Volume'
numid=53,iface=MIXE
1 - 100 of 117 matches
Mail list logo
