Same issue here, also with Ryzen5 3600 and Radeon RX 5600 XT on
Displayport.
As with others on this thread, able to boot fine into 5.15.0-52-generic.
As a 'user' rather than an 'enthusiast', I would have to look up how to
manually install one of your alternative kernels, and I have other
This bug was fixed in the package linux-firmware -
20221114.git60310c2d-0ubuntu1
---
linux-firmware (20221114.git60310c2d-0ubuntu1) lunar; urgency=medium
* Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support
This bug was fixed in the package linux-firmware -
20221114.git60310c2d-0ubuntu1
---
linux-firmware (20221114.git60310c2d-0ubuntu1) lunar; urgency=medium
* Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support
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 1997279
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: ubuntu => linux (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/1997279
Title:
Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
Status in
You have been subscribed to a public bug:
I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop
PC.
When using the new kernel 5.15.0-53-generic, I receive a black monitor right
after booting the system (=ubuntu just won't start).
(Kernel 5.15.0-52-generic used to work
uas.ko hangs, fails, spams dmesg on all 5 HP AMD A10 systems tested, on
all AMD USB3 ports if writing to any device that has UAS.
If booting a livecd on a UAS capable device, UAS cannot be unloaded.
UAS will stall any writes to the temp log partition ubuntu creates on the boot
device.
--
You
Confirmed that reducing the size of the initrd.img slightly allowed my
machine to boot. I just enabled `COMPRESSLEVEL=19` with `COMPRESS=zstd`
(default on debian) in initramfs.conf. That reduced my initrd.img size
from 72MB to 62MB, which allowed my machine to boot.
Ultimately, I set
You saved my day.
I also install cuda stuff from nvidia driver repository (using ubuntu 20.04 and
needed cuda 11)
/etc/systemd/system/systemd-suspend.service.requires contained symbolic links
which point to /lib/systemd/system/nvidia-resume.service
removing these symbolic links made suspend
Verification on kinetic is incomplete. Things do work on a cloud
instance with a single gpgpu. In these cases, both the DKMS and LRM
version of the driver works with the cuda samples test.
Problems are encountered when running on either the DGX2 or A100
systems. For the A100, I have not been able
It seems that commit bcf91619e32fe584ecfafa49a3db3d1db4ff70b2 included
in 5.4.0-132.148 breaks Node Exporter and cadvisor, cf.
https://github.com/prometheus/node_exporter/issues/2500. A minimal
reproducer in Go is available at
Dame problem after reboot for install flatpak ando snap software in
Ubuntu 22.10 x86_64 kernel 5.19.0-23-generic.
The error in boot is
/dev/sda3: clean, 348901/3973120 files, 4784925/15869184 blocks
[ 4.721599] Dev loop0: unable to read RDB block 8
[ 7.184964] Dev loop15: unable to read RDB
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/1997178
Title:
Black screen after wake from
Created attachment 303237
experimental patch
That patch (d341838d776a ("x86/PCI: Disable E820 reserved region
clipping via quirks")) relies on quirks that match DMI Vendor, Product
Version, Product Name, and Board Name. This isn't an ideal solution
because there are likely other systems we don't
>From the dmesg log in
https://bugzilla.kernel.org/attachment.cgi?id=287483,
BIOS-e820: [mem 0x4bc5-0xcfff] reserved
pci_bus :00: root bus resource [mem 0x6540-0xbfff window]
pci :00:07.1: PCI bridge to [bus 2b-54]
pci :00:07.1: bridge window
Tested and confirmed that wake from sleep results in a black screen 100%
of the time on 5.15.0-53-generic, but only ~10% of the time on
5.15.0-52-generic. Thus on the surface it seems 5.15.0-53-generic caused
a regression.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this
You have been subscribed to a public bug:
When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia
driver 515, screen is black, and never changes after 10 minutes of
waiting.
However journalctl shows activity after wake (see attached log excerpt,
where wake occurs around Nov 20
Thanks .. It's solutions done for me, i hope done for other persons.
Setting kernel parameter kernel parameter "psmouse.synaptics_intertouch=1"
solved the problem, as suggested in comment #4 above and here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907991/comments/29
Cheers!
--
I just ran apt update && apt upgrade, noticed the dkms upgrade, rebooted
into 5.15.0-53-generic and still got a no-signal black monitor. See my
previous comment for hardware. Is the fix not out yet or was the
upgraded dkms package supposed to be the fix?
--
You received this bug notification
Public bug reported:
Won't update
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2
Uname: Linux 5.10.13-051013-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
Ping!
--
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/1851887
Title:
[ASUS N550JK] After a system reboot, the audio seems muted until one
raises the level above 50%
Status in linux
** Description changed:
Ubuntu can't wake up while being detached from docking station after
being suspended with docking station and external monitor.
Kernel 5.15.0-53-generic.
I think I didn't have this problem before. Last upgrade (two days ago)
seems to be the issue. Laptop
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Public bug reported:
asd
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1
Uname: Linux 6.0.9-x64v1-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Nov 21 10:55:45 2022
ErrorMessage: o
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997113
Title:
Jammy update: v5.15.76 upstream stable
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
Is this not going to happen?
> kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
--
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/1971712
Title:
Add support for Intel
After a lot of searching around, it seems that it is necessary to change
the "iommu=soft" command on GRUB to "amd_iommu=off" on kernel 5.19 or
higher. With that command, all kernels will boot fine afterwards.
--
You received this bug notification because you are a member of Kernel
Packages,
well not exactly, oem-6.0 will not get DG2 support..
--
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/1971712
Title:
Add support for Intel DG2
Status in linux-firmware package
** Description changed:
--
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/1997151
Title:
The channels for the microphones does not have enough volume.
Status in linux package in Ubuntu:
Note that usually, after 10 minutes or so, I'm able to fix this with
`sudo modprobe -r iwlwifi && sudo modprobe -i iwlwifi`. Might be a
hardware problem? Overheating?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
Same error here.
Wireless-AC 9560 on MSI Stealth GS65 9SE, Ubuntu 22.04 with kernel
5.15.0-53-generic.
--
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/1993052
Title:
iwlwifi
Yes the mutter fix got lost/regressed and so we are dependent on having
just the kernel fix now. This is being tracked in bug 1985869.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug confirmed with a Logitech BRIO on 22.04 and 22.10. Though the bug
does not occur with my laptops' built-in mics.
** Summary changed:
- [jammy] Microphone not working after suspend
+ Logitech BRIO microphone not working after suspend
** No longer affects: pulseaudio (Ubuntu)
** Changed in:
'nvidia-wayland' means a bug only happens on Wayland, which this does
not.
We use the 'wayland' tag to indicate that a bug can occur on Wayland,
which was already done in comment #9.
** Tags removed: nvidia-wayland
--
You received this bug notification because you are a member of Kernel
The verification of the Stable Release Update for dkms 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 encounter a
This bug was fixed in the package dkms - 2.8.7-2ubuntu2.1
---
dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium
* Cherry-pick patches from kinetic/stable to address building dkms
modules correctly for HWE kernels (LP: #1991664):
+ Fix dkms-autopkgtest when a given dkms package
This bug was fixed in the package firmware-sof - 2.0-1ubuntu4
---
firmware-sof (2.0-1ubuntu4) jammy; urgency=medium
* Add RPL firmware to v2.0.x
- Intel relased v2.2.2 firmware to support both adl and rpl, and the rpl
firmware are just symbolic links to adl firmware. The
I know this is a bit of a special package, but please always include
more information about the verification. Since I had some verification
details for kinetic, but for jammy it was just a comment switching the
tags - please always give some context on which versions have been used
for
The verification of the Stable Release Update for firmware-sof 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
This bug was fixed in the package firmware-sof - 2.1.1-1ubuntu1.1
---
firmware-sof (2.1.1-1ubuntu1.1) kinetic; urgency=medium
* Add RPL firmware to v2.1.x
- Intel relased v2.2.2 firmware to support both adl and rpl, and the rpl
firmware are just symbolic links to adl
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 1997213
and then change the status of the bug to 'Confirmed'.
If, due to the
We'll update two actions listed as following
1. Update to latest kernel and have a try.
2. upload file that generated by command "sosreport"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Description:
After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA
disk to the Onboard AHCI controller in our system by plugging a SATA disk into
the SATA slot, However, the OS can not recognize the added disks, both running
command "lsblk"
45 matches
Mail list logo
