> should it fail how can I get the log when my system completely locks
up and dies?
My understanding of the bug is that it occurs when the NVIDIA driver
tries to bring up the DisplayPort link on certain DisplayPort monitors.
You should be able to drive the system in text mode with a failing
Hello, NVIDIA employee here.
Can those who are still experiencing problems please provide the
following information?
* NVIDIA driver version installed
* NVIDIA GPU model
* Exact model of affected monitor
An nvidia-bug-report.log will capture the driver version and GPU model,
along with some
The workaround suggests that there's an interaction between the NVIDIA
driver and another kernel module at play here. Presumably, adding the
NVIDIA kernel modules to the initrd causes them to be loaded before the
other module. Maybe video.ko, which registers its own brightness
handler?
The
Can somebody with an affected system please try with one of the recently
released 460.xx drivers? There were some brightness regressions that
were resolved in the 460 series that may be related.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Sorry, I didn't notice that this bug had expired, or that it was waiting
on log files. I don't have the system that I originally reproduced the
issue on set up any more, but it should be easily reproducible.
I'll set up another system to reproduce and generate the requested log
files, but in the
amd64 counts as x86 for the purposes of supported architectures in
Linux, and x86 does have the C version of recordmcount. Comment #3
includes a list of architectures that lack the C version of
recordmcount. Of those architectures, ppc64le is the only one that is
supported by the NVIDIA driver
** Patch added: "Patch generated from the upstream commit that fixes this issue"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+attachment/5269215/+files/hda.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
When using HDMI or Displayport audio, the EDID-like Data (ELD) fails to
update properly when hotplugging or hot-unplugging displays. This in
turn prevents tools like the GNOME sound settings control panel from
accurately presenting the system's current audio capabilities.
Public bug reported:
The old-style NVIDIA package (used prior to Bionic) installs an X
configuration snippet to:
/usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-
outputclass.conf
The purpose of this configuration snippet is to configure DRM
OutputClass-based driver matching
Yes, that's the one. The kbuild maintainer modified the commit message
to add a maintainer Signed-off-by line.
I would say that any kernel versions that are shipped for actively
maintained versions of Ubuntu that support hardware platforms that don't
use the C version of recordmcount:
for file
Public bug reported:
When LANG is set to a non-English language with the relevant language
pack installed, Kbuild's recordmcount.pl script fails to function
correctly when building out-of-tree kernel modules on architectures that
do not use the C version of recordmcount (e.g. ppc64le). This can
I'm confused about the above message. This bug never affected the kernel
in Bionic AFAIK. Or is this referring to the HWE kernel for Bionic from
Cosmic for 18.04.2? In that case, why isn't this change already included
in the HWE kernel as it was imported from Cosmic, rather than needing to
be
Just to confirm, this is with the 4.18.0-12-generic x86_64 kernel from
cosmic-proposed.
--
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/1798863
Title:
18.10 kernel does not appear to
Yes, I do see the expected behavior now with signed modules, both when
the signing key is enrolled in the MOK (module loads, no verification
error) and when it is not enrolled in the MOK (module fails to load due
to verification error.) However, the behavior is not quite what I expect
when a
Cool, glad you were able to track down the problems. Sorry if my report
that module signature verification was disabled and couldn't be re-
enabled was misleading. That's what I thought was happening; I didn't
think to imagine that the enforcement of the "valid signature required"
policy wasn't
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204915/+files/ProcInterrupts.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 cosmic
** Description changed:
On a system with Ubuntu 18.10, with secure boot enabled, and a key
enrolled in the MOK database, I am observing the following peculiar
behaviors:
* Signature verification appears to be disabled, and
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204911/+files/IwConfig.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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204917/+files/PulseList.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/1798863/+attachment/5204912/+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/1798863
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204914/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204918/+files/RfKill.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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204909/+files/CRDA.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/1798863
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204919/+files/UdevDb.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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204916/+files/ProcModules.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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204910/+files/CurrentDmesg.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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204913/+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/1798863
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204920/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
On a system with Ubuntu 18.10, with secure boot enabled, and a key
enrolled in the MOK database, I am observing the following peculiar
behaviors:
* Signature verification appears to be disabled, and cannot be enabled again.
It appeared to be enabled previously, as loading
The problem described in this bug is due to a confirmed regression in
the NVIDIA driver. If you are seeing a similar symptom on Intel, that
should probably be tracked in a separate bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Not to my knowledge: that changelog entry refers to adding an additional
interface via the NV-CONTROL API to the existing backlight
functionality. The problem is that the existing backlight functionality
is now broken on some laptops, so it doesn't make a difference whether
it's exposed through a
Sorry, at the moment we don't have an ETA for a fix. It's not likely to
be fixed in the immediate future. I've added a note to the bug report on
the NVIDIA bug tracker as a reminder to update this Launchpad thread
when we have a fix in hand.
The only workaround I'm currently aware of is to use an
32 matches
Mail list logo
