Public bug reported:
The linux-signatures-nvidia-6.8.0-22-generic package only contains
nvidia drivers as new as nvidia-driver-450 despite the current
additional drivers in Software & Updates having nvidia-driver-550 as the
tested topmost choice.
** Affects: linux-restricted-signatures (Ubuntu)
The nvidia support is still messed up under 6.2.0-26 for those using
secure boot. In previous iterations of the nvidia drivers and kernels,
one could always count on the linux-signatures-nvidia-6.2.0-26-generic
and linux-modules-nvidia-535-6.2.0-26-generic to use pre-signed kernel
modules rather
After many false starts, the following similar RedHat bug report, gave
me a hint to a workaround that suppresses the CSR_RESET errors in
iwlwifi.
https://bugzilla.redhat.com/show_bug.cgi?id=2138790
Bug 2138790 - No WiFi on T16 Intel Gen 12th Alder Lake Wifi 6E AX 211
[NEEDINFO]
This bug report
Upgrading the BIOS to capture the USB 2.0 fixes significantly reduced
the occurance of this bug but unfortunately doesn't totally eliminate
it. I should note that the Ubuntu 22.04 LTS kernels initially suffered
from this bug to a small degree but that by 22.04.1 LTS, the issue was
extremely rare.
It appears that this is fixable with a BIOS update on the Gigabyte X570
UD v1.1 motherboard. Upgrading from the F32 stable BIOS release to the
F34 stable BIOS release captures the following change from the F33g beta
BIOS release...
3. Fix USB 2.0 devices stability and compatibility
which makes
Unfortunately, this bug has gotten worse under 5.19.0-23.24 despite the
options hack. On a cold boot, about half the time the iwlwifi driver
shows the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Apparently the options workaround doesn't completely eliminate the bug.
It still occurs around five percent of the time when booting kinetic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looking through the various bug reports against iwlwifi in bugzilla
related to iwlwifi driver initialization failures and previous
workarounds, I added...
options iwlwifi power_save=0
options iwlmvm power_scheme=1
options iwlwifi uapsd_disable=1
to /etc/modprobe.d/iwlwifi.conf. Tentatively,
Public bug reported:
A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu
22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of
the time. When this occurs, the kern.log shows...
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0:
** Attachment added: "screenshot of the rendering artifact in cheese under
22.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577395/+files/Screenshot%20from%202022-04-05%2016-53-06.png
--
You received this bug notification because you are a member of Kernel
I also can confirm that the warnings...
(cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late ():
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be
Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src !
xvimagesink' displays the webcam image fine.
--
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/1967843
Title:
cheese display
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577390/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577392/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577393/+files/lspci.txt
--
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/1967843
apport information
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577394/+files/lsusb.txt
--
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/1967843
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577391/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...
(cheese:4175):
Public bug reported:
The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...
(cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being
dropped.:
The changes made to linux-firmware 1.201.1 on impish has destablized use
of a Gigabyte GC-WB867D-I REV Bluetooth 4.0/Wireless AC/B/G/N Band Dual
Frequency 2.4Ghz/5.8Ghz Expansion Card. Under the new linux-firmware
1.201.1, no wifi is available under Gnome in about 80-90% of the boots.
Under the
I've seen the same issue with focal and System76 Stable PPA's
460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text
was corrupted after waking from suspend but it has only occurred once so
far.
--
You received this bug notification because you are a member of Kernel
Packages,
This offending package for bug is proving very difficult to pin down. I
have tried to sequentially regress all the packages that the recovery
kernel boot are likely to use back to their eoan versions on a 20.04
installation. In each case, I reinstalled the kernels afterwards to
insure that the
This issue extends to the daily desktop cd image for focal. When booted
from a usb memory stick and the safe graphics (which uses nomodeset) is
selected from grub, the screen remains black and never completes
booting. This issue doesn't exist with the current 19.10 cd images which
boot without
I have been able to eliminate the focal 5.4.0-26-generic kernel packages
as the origin of this bug. Manually installing those onto an
installation of Ubuntu 19.10, produced a fully functional boot. More
importantly the recovery mode boot from grub worked fine. So the problem
under 20.04 would
This problem doesn't exist for current Ubuntu 19.10 under its
5.3.0-46-generic kernel. The recovery mode boots fine on the same
hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
Oddly, so far I have not found a Ubuntu mainline kernel build that
doesn't show the problem.
5.3.18-050318-generic
5.4.0-050400-generic
5.4.25-050425-generic
5.4.28-050428-generic
5.6.6-050606-generic
all produce the hang at loading the ramdisk when booting the recovery
kernel with the default
Interestingly, installing the mainline Ubuntu 5.4.25 generic kernel
packages on Ubuntu 18.04 produces the same bug of nomodeset preventing
the recovery dialog from appearing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in
If I remove 'nomodeset' from the grub kernel options for the recovery
kernel under 20.04, the hang in booting at loading the ramdisk is
eliminated. The recovery dialog appears as expected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery
mode from grub hangs on loading of the ramdisk with the Recovery Menu
dialog never appearing. This problem doesn't exist for a fresh install
of Ubuntu 18.04 updated to the current package updates. In that
This bug is definitely triggered by the built kernel image loading the
nvidia drivers. The autologin failures and associated hangs on restarts
can be suppressed as follows...
1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT
2) Regenerate /boot/grub/grub.cfg with 'sudo
Couldn't the nvidia packages all be modified to prune 'splash' from
/boot/grub/grub.cfg prior to rebuilding its kernel modules and thus
regenerating the initrd.img files?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf
under 20.04 has no impact on the autologin bug with nvidia-340.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro
3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is
shown instead. While the login works fine at the point, restarting then
causes the system to hang rather than completing the restart.
--
You received
Public bug reported:
The most recent kernel updates resulted in...
ii linux-image-5.4.0-24-generic 5.4.0-24.28
amd64Signed kernel image generic
ii linux-image-generic5.4.0.24.29
amd64
34 matches
Mail list logo
