Same issue for me.
- Kernel: 5.15.0.50-generic
- Driver: 515.65.01
- Card: GTX 1660
Workarounds
1. Kernel 5.15.0.48-generic
2. GRUB "nomodeset"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://github.com/frankcrawford/it87
The chances of mainlining aren't exactly stellar though.
https://lore.kernel.org/all/0134609e-0b03-d9d2-62ba-75d8d8211...@roeck-us.net/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Same issue with me.
- Kernel: 5.15.0-50-generic (48 also fails)
- Driver: 515.76-0ubuntu0.22.04.1 amd64
- Card: RTX3060 LHR (GA106).
Currently using the following workaround:
- Kernel: 5.15.0-48-generic
- Driver: 510.85.02-0ubuntu0.22.04.1 amd64
--
You received this bug notification because you
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 1993040
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
System: Ubuntu 22.04.1 LTS (x86-64)
Kernel: 5.15.0-50-generic
NVIDIA card: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1)
Problem summary:
Just updated "nvidia-driver-515" package from "515.65.01-0ubuntu0.22.04.1" to
newest "515.76-0ubuntu0.22.04.1". It
** Project changed: launchpad => 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/1993040
Title:
After resuming from suspend, NIC has WOL disabled
Status in linux package
You have been subscribed to a public bug:
I have my NIC configured with WOL in magic packet mode:
```
$ sudo ethtool enp5s0
Settings for enp5s0:
...
Supports Wake-on: pumbg
Wake-on: g
```
However, every time I resume the system from suspend once, WOL becomes
disabled:
```
$
Same problem, Ubuntu freezes at startup before user login.
- Kernel version: 5.15.0-50-generic
- Nvidia driver version: 515.76
- Nvidia card: RTX3060
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello. I'm sorry, but, is link above correct for this issue?
I don't understand how to install the working setup, may be there is a more
detailed guide?
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in
I have found out that loading rtw88_pci with disable_aspm=1 and
disable_msi=1 fixes the issue.
--
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/1992517
Title:
rtw88_8822ce: unable to ping
Confirm this.
And why the change log of the kernel package all goes like 'Bump ABI
xxx'?
--
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/1992679
Title:
Can not login after new kernel
Could you try booting with a daily live image, available at
https://cdimage.ubuntu.com/ubuntu/daily-live/current/, and see if the
issue exists with it? Thanks in advance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
also affects new 520 driver
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1799679
Title:
Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
Exactly the same issue.
5.15.0-50 did not boot at all.
Went back to 5.15.0-48, Ubuntu software manager claimed some updates had
to be done and I did them.
Now 5.15.0-48 no longer boots, my machine is unusable... Not ideal at
all...
--
You received this bug notification because you are a
The attachment "dkms.diff" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for
** Changed in: linux-oem-6.0 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1992976
Title:
Jammy update: v6.0.1 upstream stable
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
For the record, someone has just joinned the Ubuntu-fr chat group and
asked what driver to choose since he fear to apply one of the driver in
the list without any impact
** Summary changed:
- 12th gen intel PC can't boot with nvidia installed
+ end user has no hint on choosing the working driver
If you don't want to update the dkms package version, you can apply this
patch to fix the problem
** Patch added: "dkms.diff"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+attachment/5624265/+files/dkms.diff
--
You received this bug notification because you are a member of
You have been subscribed to a public bug by atactic (atactic):
When starting the PC, the splash screen freezes with the motherboard logo
displayed.
As my disk is encrypted the decryption field does not appear below the logo.
By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again
** Summary changed:
- Boot issue with Ubuntu 22.10 Kinetic Kudu Kernel 1 5.19.0.15.15
+ Boot issue with Ubuntu 22.10 Kinetic Kudu Kernel 1 5.19.0.15.15, now hanging
with blinking cursor after update to Kernel 5.19.0.21.21
** Summary changed:
- Boot issue with Ubuntu 22.10 Kinetic Kudu Kernel 1
Kernel has been updated to version 5.19.0.21.21 and now during boot the
system hangs with a white blinking cursor after hitting the [OK] button
following the resume Resume normal boot option (see above explanations
about boot sequence).
I had to hard reboot the system and select instead from the
22 matches
Mail list logo
