*** This bug is a duplicate of bug 2038745 ***
https://bugs.launchpad.net/bugs/2038745
** This bug has been marked a duplicate of bug 2038745
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver
installed
--
You received this bug notification because you are a mem
*** This bug is a duplicate of bug 2038745 ***
https://bugs.launchpad.net/bugs/2038745
** This bug has been marked a duplicate of bug 2038745
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver
installed
--
You received this bug notification because you are a mem
Public bug reported:
I have made an older version of the kernel immutable to prevent its
deletion, because the newer kernels will not boot. This has the side
effect of preventing hardlinks, which caused an error message. I don't
know if this is related.
ProblemType: Package
DistroRelease: Ubuntu
This is usually a problem with display connection quality. Please try a
different HDMI cable.
Also next time the problem happens please run:
journalctl -b0 > journal.txt
grep . /sys/class/drm/*/status > connections.txt
sudo apt install drm-info
drm_info > drminfo.txt
and attach the resul
You have been subscribed to a public bug:
When using an external HDMI monitor, the screen frequently goes blank
for a few seconds. This only happens with the external monitor and not
the integral screen of the laptop.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
Proc
I'm having the same problem after updating to version 1.7. My desktop
freezes before boot with a RX7900XT
--
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/2038867
Title:
Linux fir
@Juerg:
Internal team looked at it, VP with Navi31 XTX boards, VNP with the others.
So the testing with OEM-6.1/OEM-6.5 on other Navi31 from earlier bug is
accurate.
Confirmed that upgrading SMU binary (just dropped into
/lib/firmware/updates/amdgpu) fixes the issue.
Considering the regression
Public bug reported:
SRU Justification:
[Impact]
After syncing up the gpio-mlxbf3.c driver with the upstreamed version, we
dropped the use of the valid_mask variable because kernels greater or equal to
6.2.0 dont need it.
This is no longer needed in kernel versions >= 6.2.0 because valid_mask
I just reported the same issue
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038867
--
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/2038864
Title:
20230323.gitb
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.
Public bug reported:
I just upgraded my System76 Thelio running 23.04 with a Navi 31 [Radeon
RX 7900 XT/7900 XTX] GPU. It seems this update causes my displays to
freeze very early in the boot process. I see some basic messages and
then some screen corruption and that is where the screen remains.
Public bug reported:
Nvidia crash
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: nvidia-kernel-common-535 535.113.01-0ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubun
Relevant information may be:
c1:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL
Upstream Port of PCI Express Switch [1002:1478] (rev 10) (prog-if 00 [Normal
decode])
Flags: bus master, fast devsel, latency 0, IRQ 38, NUMA node 0
Memory at d8e0 (32-bi
Public bug reported:
[Impact]
20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely
hangs the entire kernel on a RX 7900 XTX. Reverting back to
20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again.
[Fix]
Revert AMD firmware updates.
[Test Case]
Boot a machine
I cannot provide logs using apport. Please let me know if you need to
know how I am using this driver.
** 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.
Public bug reported:
I bought a new Asus Vivobook Notebook X1504ZA-NJ205 and installed ubuntu on it,
but I couldn't use my wifi card: Network controller [0280]: MEDIATEK Corp.
Device [14c3:7902].
After posting on that on the Ubuntu forum someone suggested me to file a bug
report: https://ubuntu
After installing via the legacy iso I saw the same message on login.
Opening a terminal and typing df I saw again the same message in the
terminal followed by the normal df output.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I can confirm that in my case I was experiencing this problem on 22.04 so
indeed both are affected.
On Mon, Oct 9, 2023 at 1:55 AM Juerg Haefliger <2031...@bugs.launchpad.net>
wrote:
> The problem is with kernel 6.2 which is in both 23.04 and 22.04 (hwe) so
> affects both releases.
>
> --
> You r
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2038852
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: 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/2038852
Title:
Isotp driver causes timeout because of race condition dur
You have been subscribed to a public bug:
This are my system details
Description:Ubuntu 20.04.6 LTS
Release:20.04
When using 5.15.133 kernel on Ubuntu 20.04. I am seeing that non blocking
writes cause race condition and locks the socket. This issue is resolved by a
patch from here
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.1
---
linux-firmware (20230919.git3672ccab-0ubuntu2.1) mantic; urgency=medium
* /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 (LP: #2038546)
- [Packaging] config: Don't exclude cypres
I have this issue on an HP Spectre X360-Convertible 14 with Bang &
Olufsen internal speakers, and Ubuntu 22.04.3 LTS.
As others, I can use the audio jack or bluetooth the sound out. It
worked well with Windows 11.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038292
Title:
nvidi
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Confirmed => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubun
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/2038837
Title:
kernel: evict_inodes inode 000
Hi
I've tested the kernel changes to enable Renesas RZ platform serial
installer.
The changes are working ok. I got the Ubuntu serial installer working
for Renesas RZ platform.
Please can you help to change the status to verification-done for
different releases.
Best Regards
John
** Changed
Public bug reported:
This gets spammed after I shutdown, though the inode values are
different for each line. Had to phyically reboot to get it to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => JOHN VINCENT (johnvincent)
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => JOHN VINCENT (johnvincent)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
In Mantic, we try to exclude firmware files that the kernel doesn't
reference. Some bcm/brcmfmac files are symlinks to cypress/cyfmac files
so we need to keep the cypress files on all relevant architectures.
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
** Changed in: ubuntu-release-notes
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037417
Title:
mantic images after 20230917 are failing to deploy with fa
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
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because
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
Did an hour of soak testing with arm64 kernel
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5.6/arm64/linux-image-
unsigned-6.5.6-060506-generic_6.5.6-060506.202310061235_arm64.deb and
cannot reproduce this issue.
--
You received this bug notification because you are a member of Kernel
Packa
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
Glad to help, so is it fixed in the next update? or i need to do it
manually
On Mon, Oct 9, 2023, 5:30 PM Daniel van Vugt <2038...@bugs.launchpad.net>
wrote:
> Thanks. That confirms it's the kernel not detecting the monitor.
>
> ** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu)
>
> ** Changed
This bug is awaiting verification that the linux-
azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-trusty-linux-
azure' to 'verification-done-trusty-linux-
This bug is awaiting verification that the linux-
azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-trusty-linux-
azure' to 'verification-done-trusty-linux-
This bug is awaiting verification that the linux-
azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-trusty-linux-
azure' to 'verification-done-trusty-linux-
Ok, let's see. Thank you.
--
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/2032338
Title:
HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)
Status in linux-fir
Discussing this internally, it was suggested to use:
fbcon=map:X
With X = 0, I see the same behavior (boot process on the BMC, X on
whatever is set)
And other values for X just blank the boot process on both outputs (BMC
and HDMI).
--
You received this bug notification because you are a member
The log messages specifically refer to lightdm,
"2023-10-08T16:35:59.205065+00:00 ubuntu-budgie lightdm[1890]: df:
/sys/firmware/efi/efivars: Invalid argument", and I noticed this patch
in lightdm:
https://git.launchpad.net/ubuntu/+source/lightdm/tree/debian/patches/04_language_handling.patch?h=ap
This bug was fixed in the package linux-azure - 6.5.0-1007.7
---
linux-azure (6.5.0-1007.7) mantic; urgency=medium
* mantic/linux-azure: 6.5.0-1007.7 -proposed tracker (LP: #2038690)
* Azure: net: mana: Configure hwc timeout from hardware (LP: #2036627)
- net: mana: Configure
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.104.12-0ubuntu2
---
nvidia-graphics-drivers-535-server (535.104.12-0ubuntu2) mantic; urgency=medium
* debian/rules:
- Add override_dh_installsystemd.
- Pass in --no-stop-on-upgrade --no-restart-after-
This bug was fixed in the package linux - 6.5.0-9.9
---
linux (6.5.0-9.9) mantic; urgency=medium
* mantic/linux: 6.5.0-9.9 -proposed tracker (LP: #2038687)
* update apparmor and LSM stacking patch set (LP: #2028253)
- re-apply apparmor 4.0.0
* Disable restricting unprivile
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.104.12-0ubuntu2
---
nvidia-graphics-drivers-535-server (535.104.12-0ubuntu2) mantic; urgency=medium
* debian/rules:
- Add override_dh_installsystemd.
- Pass in --no-stop-on-upgrade --no-restart-after-
I did test the kernel from lunar proposed (6.2.0.1015.16) on AWS. The
image boots with sev-snp enabled:
# sudo dmesg | grep -i sev
[5.563677] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP
[6.140250] SEV: Using SNP CPUID table, 64 entries present.
[8.507286] SEV: SNP guest p
Public bug reported:
tried to install nvidia driver on fresh install
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-510 510.60.02-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
So it doesn't seem to be firmware related then? Closing the ticket.
Please open a new one should you run into issues agaain.
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
--
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/2032338
Title:
HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)
Status in linux-firmware package in Ubuntu:
Sounds like a BIOS bug. Does anything happen if you press the airplane
hot key? Also is there a difference in loaded modules before and after
suspend/resume? You could also try to blacklist any hp modules but that
probably won't do much.
** Changed in: linux-firmware (Ubuntu)
Status: New =>
The latest maas images from 20231008 are booting without issue:
ubuntu@akis:~$ lsb_release -sc
No LSB modules are available.
mantic
ubuntu@akis:~$ cat /etc/cloud/build.info
build_name: server
serial: 20231008
ubuntu@akis:~$ uname -a
Linux akis 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep
This bug is awaiting verification that the linux-azure/6.2.0-1016.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
cloud minimized and non minimized images have now been tested with
6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite
which was failing and which is the test suite which prompted this whole
thread. +1
--
You received this bug notification because you are a member of Kernel
Packa
Not sure why you think the driver doesn't load a vendored clm_blob. That
works fine on a Raspberry Pi.
--
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/2013027
Title:
Issues over
This bug was fixed in the package linux-firmware -
20230323.gitbcdcfbcf-0ubuntu1.7
---
linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.7) lunar; urgency=medium
* linux-firmware is outdated (LP: #2033441)
- nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW
*** This bug is a duplicate of bug 2033441 ***
https://bugs.launchpad.net/bugs/2033441
** This bug has been marked a duplicate of bug 2033441
linux-firmware is outdated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware
lunar released because upstream made it clear we need this, verified or
not
--
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/2033441
Title:
linux-firmware is outdated
Status in l
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 -
20230323.gitbcdcfbcf-0ubuntu1.7
---
linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.7) lunar; urgency=medium
* linux-firmware is outdated (LP: #2033441)
- nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.laun
And can reproduce on real H/W on a 24 core "SC2A11" is a multi-core chip
with 24 cores of ARM® Cortex-A53. with Linux 6.5.0-7-generic #7-Ubuntu
SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64
GNU/Linux
[ 201.075720] EXT4-fs (loop13): mounted filesystem
52e32882-8b3a-47c
Reproduced this with mainline arm64 kernel
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5.5/arm64/linux-image-
unsigned-6.5.5-060505-generic_6.5.5-060505.202309230703_arm64.deb
[ 219.219042] Internal error: Oops - BUG: f2000800 [#1] SMP
[ 219.262013] Modules linked in: cfg80211 binf
Can you check if this kernel commandline makes a difference with the
new/broken firmware?
enable_autosuspend=0
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Relevant log entries:
[ 14.405083] Bluetooth: Core ver 2.22
[ 14.405115] NET: Registered PF_BLUETOOTH protocol family
[ 14.405116] Bluetooth: HCI device and connection manager initialized
[ 14.405120] Bluetooth: HCI socket layer initialized
[ 14.405121] Bluetooth: L2CAP socket layer init
Thanks. That confirms it's the kernel not detecting the monitor.
** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: Incomplete => New
** Summary changed:
- System doesnt recognize second monitor
+ [i915] System doesn't recognize second moni
Reproduced this with mainline arm64 kernel
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5/arm64/linux-image-
unsigned-6.5.0-060500-generic_6.5.0-060500.202308271831_arm64.deb
[ 184.853731] pstate: 4045 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 184.862627] pc : d_instantiate_new+0
You have been subscribed to a public bug:
I am using an old monitor which using a DVI connectors but I used a DVI
to HDMI adapter which works fine on Windows operating system... My
monitor is HP W2072a... I hope with the information provided helps...
ProblemType: Bug
DistroRelease: Ubuntu 22.04
P
Can't reproduce this with mainline arm64 kernel
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.5.6/arm64/linux-image-
unsigned-6.5.6-060506-generic_6.5.6-060506.202310061235_arm64.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Proposed a different fix:
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/111
--
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/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'
** Description changed:
+ [Impact]
+
/lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
StarFive VisionFive board which uses the starfive kernel flavor.
The file was available in Jammy and only recently removed from Mantic.
File debian/config/linux-firmware/riscv64/
** Tags added: kern-8207
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2038582
Title:
Turning COMPAT_32BIT_TIME off on arm64
Status in linux package in Ubuntu:
Incomplete
Status
** Tags added: kern-8208
--
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/2038586
Title:
Turning COMPAT_32BIT_TIME off on armhf
Status in linux package in Ubuntu:
Incomplete
Status in l
** Description changed:
+ [ Impact ]
+
+ gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
+ sometimes when the screen locks, sometimes when launching particular
+ apps.
+
[ Workaround ]
Add this to /etc/environment:
- MUTTER_DEBUG_KMS_THREAD_TYPE=user
+ MUTTER_DEBU
99 matches
Mail list logo
