** Description changed:
Running fine with nvidia-384 until this kernel update came along. When
booted into the new kernel, got super low resolution and nvidia-settings
was missing most of its functionality - could not change resolution.
Rebooted into 4.4.0-112 kernel and all was well.
** Changed in: libglvnd (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1749912
Title:
MIR: libglvnd
To manage notifications
@glenpike
For Xenial you need gcc-5 5.4.0-6ubuntu1~16.04.9. You can find which version
you have installed via "dpkg -l | grep gcc-5".
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
I had the same problem with my -116 kernel upgrade.
So I am running `gcc version 5.4.1 20160904 (Ubuntu
5.4.1-2ubuntu1~16.04)` but this was already installed it seems - I can't
see in the dpkg.log* files when this was added. I am assuming that this
is a newer version of GCC than is needed, but
John (earthspike), you said your version is
gcc-4.8.real (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
but when I run gcc --version I get just
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
The version number appears to be the same but instead of gcc-4.8.real I
only see gcc. Is that a significant
I also tried to switch to the main ubuntu server for maybe the local
mirror did not yet get the gcc update, but apt does not want to install
anything more from main.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Hi, same here, after kernel update no nvidia-340.
Tried the manual dkms rebuild, but no retpoline in vermagic afterwards
either.
Checked gcc: apt says 4:4.8.2-1ubuntu6, but /usr/bin/gcc says
4.8.5-1ubuntu1~14.04 .
`which gcc` confirms using /usr/bin/gcc
What about that?
--
You received this
I took the *-116 kernel a few days ago on my 16.04.3 desktop, got a
mouse freeze after booting, and went back to *-112.
I see from my dpkg.log that version 5.4.0-6ubuntu1~16.04.9 of gcc
installed over a day before the *-116 kernel. I see also from
@cjmather
If you are sure that you have the latest gcc and you are still seeing kernel
panics with the -116 kernel, please file a new bug and report back here what
that bug # is.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
My 14.04 machine received the gcc update after the -116 update, just as
others have noted.
I resolved this by booting into -112 then:
sudo apt-get purge linux-headers-4.4.0-116 linux-headers-4.4.0-116-generic
sudo apt-get install linux-generic-lts-xenial
And then rebooted into -116 with
My Trusty (14.04) also shows gcc-4.8 version 4.8.4-2ubuntu1~14.04.4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04
For Trusty (14.04) I successfully installed the driver with gcc version
4:4.8.2-1ubuntu6
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks
Tim Habigt wrote in #30:
> Yes, I also got the gcc update after the kernel update. With the new
gcc, I could fix the Nvidia kernel module.
> Here's how:
> # Show the current vermagic string of the kernel module
> modinfo nvidia-384 -k 4.4.0-116-generic
> # It will probably say:
> # vermagic:
After I reinstalled gcc from the main repo, I still get the version
mismatch between apt and gcc.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21
Just to be sure, I just reinstalled the -116 kernel as suggested by
earthspike, and fun fact, DMKS was not run at all. No kernel modules
were built. Also, no errors nor warnings that I can see.
Any ideas?
** Attachment added: "full command line output of -116 kernel reinstall (from
-112)"
Anyone else having this?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
16.04)
To manage notifications
Those for whom it didn't work, see post #7 at
https://ubuntuforums.org/showthread.php?t=2385621=13742673#post13742673
- it sounds like maybe you have to remove four items, not just two, but
I'm not sure. If that works for anyone please let us know.
--
You received this bug notification because
** Changed in: xorg-server (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1661934
Title:
Numerous deleted DRM mmaped objects in Xorg
Or rather, introducing libegl1 is what broke bionic's mesa 17.3.3
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1749912
Title:
MIR: libglvnd
To manage notifications about this bug go to:
Introducing libglvnd has seriously broken bionic. See bug 1751414.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1749912
Title:
MIR: libglvnd
To manage notifications about this bug go to:
Having the exact same issue with nvidia-390 package at my Ubuntu 16.04,
rolled back to nvidia-387 and had the same issue. And later I rolled
back nvidia-384, and still the same issue.
Then I downloaded NVIDIA-Linux-x86_64-384.111.run from Nvidia's website
to see if I am able to get it up and
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1751407
Title:
package libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 failed to
install/upgrade: subprocess
Public bug reported:
I believe my issue is similar to this one.
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1606774
I have no idea how to fix it at this time. I am using this workstation
more often these days as it provides a machine on the first floor for me
to use. Typically,
You have been subscribed to a public bug:
I just updated bionic and suddenly:
* No 'Ubuntu on Wayland' login option.
* The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe
(software rendering)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu3
mesa-demos (8.4.0-1) unstable; urgency=medium
* New upstream release.
* Drop configure.ac-Auto-detect-wayland-support.diff, upstream.
* Drop configure.ac-Fix-default-behavior-of-AC_ARG_WITH-glut.patch,
upstream.
* Update watch url.
* Distribute eglinfo within mesa-utils-extra.
*
Public bug reported:
The new application installation is failed.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
I purged the -116 packages and then re-installed them but it didn't
help. What's worse, is that now Unity doesn't work in -112, but
fortunately my Gnome session still works fine.
Here are the commands I executed to reinstall the -116 kernel:
sudo apt-get purge linux-image-4.4.0-116-generic
sudo
Actually, the offending library seems to have come in as a dependency of
this:
mesa-demos (8.4.0-1) unstable; urgency=medium
* New upstream release.
* Drop configure.ac-Auto-detect-wayland-support.diff, upstream.
* Drop configure.ac-Fix-default-behavior-of-AC_ARG_WITH-glut.patch,
FIXED
sudo apt remove libegl1
** Package changed: gnome-shell (Ubuntu) => libglvnd (Ubuntu)
** Changed in: libglvnd (Ubuntu)
Status: New => Triaged
** Description changed:
I just updated bionic and suddenly:
- * No 'Ubuntu on Wayland' login option.
- * The 'Ubuntu' login option
** Summary changed:
- [regression] Missing Wayland login option and missing GL acceleration
+ [regression] Missing Wayland login option and missing GL acceleration, after
installing mesa-utils-extra 8.4.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is
mesa-demos (8.4.0-1) unstable; urgency=medium
* New upstream release.
* Drop configure.ac-Auto-detect-wayland-support.diff, upstream.
* Drop configure.ac-Fix-default-behavior-of-AC_ARG_WITH-glut.patch,
upstream.
* Update watch url.
* Distribute eglinfo within mesa-utils-extra.
*
Fix released in mesa-demos, but the fix is not testable/usable :(
See bug 1751414
** Changed in: mesa-demos (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa-demos in Ubuntu.
I believe a transition might going on right now, but I would need to
defer to Timo to be sure. There is ana newer libglvnd in bionic-proposed
that might be worth testing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa-demos in Ubuntu.
** Summary changed:
- Blank screen with only mouse pointer after mesa driver update; display does
not switch to tty7 upon lightdm start; Xorg.0.log quickly grows
+ Blank screen with only mouse pointer after 7.10 radeon driver update; display
does not switch to tty7 upon lightdm start;
bumping priority, this will block some migrations
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
The newer Ubuntu kernel has the new retpoline Spectre mitigation. In
order to load, your kernel modules will need to be compiled with a
version of gcc that supports retpoline. You can determine if the module
has it with the command "modinfo " and look for the version
magic.
If you are using
The attachment "fix-for-4.15-timer-change" 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
ok so boot in to old 112 is ok, but not ideal. this also may be
affecting some ethernet/usb connections as well.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel
This issue has a workaround:
Download 7.9 radeon driver Ubuntu package (xserver-xorg-video-radeon-
hwe-16.04_7.9.0-0ubuntu1~16.04.1_amd64.deb) from:
https://launchpad.net/ubuntu/xenial/amd64/xserver-xorg-video-radeon-
hwe-16.04/1:7.9.0-0ubuntu1~16.04.1
Execute the following on the downloaded
Unfortunately I don't currently have a 14.04 installation so I don't
know which versions of gcc are available to you. I am using the package
"gcc-5" from the Xenial (16.04) repositories and it is working. You may
also want to check:
1. "which gcc"
a. Make sure this points to the version of gcc
Yes, I also got the gcc update after the kernel update. With the new
gcc, I could fix the Nvidia kernel module.
Here's how:
# Show the current vermagic string of the kernel module
modinfo nvidia-384 -k 4.4.0-116-generic
# It will probably say:
# vermagic: 4.4.0-116-generic SMP mod_unload
Jay Flory, your information was the key! I removed the -116 kernel and
reinstalled it, and the graphics are fine now. It looks like this was
indeed due to a timing problem between when my system got the gcc update
and the kernel update.
It appears that I'll have to reinstall virtualbox as well.
Jay Flory, that's important information and sounds like it can lead
those of us affected to a solution. However, my version of gcc is the
default one for 14.04, I do not have a custom version, yet I still have
this problem. Do you know what version of gcc I should install?
--
You received this
Looking at apt logs, it appears my system got a gcc update the day AFTER
the kernel was pushed out. I'll try reinstalling the kernel and see if
that makes a difference.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Shouldn't the -116 kernel be blacklisted? On a fresh install I'm still
seeing the -116 update available.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on
As long as you have the updated gcc installed before you install the
kernel, it works fine.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks
I've tried it in ubuntu 18.04 now that they have the 4.15 kernel and the
touchpad stopped working completely.
uname -a
Linux berith 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
dmesg
[ 781.000782] Bluetooth: hci0: last event is not cmd complete
How would the average person know to (or know how to) avoid this
problem, before it happens?
Is there something in the -116 kernel that's so great, and time
sensitive that it's worth putting folks through the huge inconvenience
of tracking down the root cause and booting into a previous kernel?
That was it Jay Flory! I too had a different version of gcc in my 16.04
installation (an upgrade I got from the ubuntu-toolchain-r ppa, which I
used in order to test something with gcc-7).
I use Timeshift, so I was able to go back to before adding the ppa.
Upgrading normally from that point,
The -116 kernel contains protections against the Spectre / Meltdown
exploits. So yeah, it's pretty great.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update
In artful the deleted objects have a different name:
# grep i915 /proc/$(pidof Xorg)/maps
7f37ddb56000-7f37ddbd6000 rw-s 00:18 1268577/i915
(deleted)
7f37de9ce000-7f37dedce000 rw-s 00:18 64439 /i915
(deleted)
7f37e3396000-7f37e3b96000
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
Tried it and lo and behold, I got a crash eventually, although it took
way longer in the regular usage scenario. I am not sure if the TLP
settings are implemented correctly though. On one occasion i7z told
*** This bug is a duplicate of bug 1737750 ***
https://bugs.launchpad.net/bugs/1737750
** This bug has been marked a duplicate of bug 1737750
nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux
4.15.0-1.2
--
You received this bug notification because you are a
It's been suggested that this driver should be removed as it's not
longer maintained (bug 1748000), so I'm not sure what the fate of this
patch will be.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
This does not only affect the NVIDIA modules, but seems to affect all
kernel modules built on the system itself. (Meaning all DKMS-built
modules and for example VMWare Workstation/Player modules)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is more visible. When selecting the window, the problem disappears.
Some refresh issue?
** Attachment added: "sshot-3.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751269/+attachment/5061159/+files/sshot-3.png
--
You received this bug notification because you are a member
Closing per upstream comment.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1661934
Title:
Numerous deleted DRM
Public bug reported:
Hello,
I suspect a endianness problem in this BigEndian Machine (Apple PowerBook G4
with ATI Radeon Mobility 9700). The same architecture (bigEndian) shows no this
specific issue on PowerMac G5 Quad with PCI-Express ATI Radeon HD4670 with VGA
BIOS (not powerpc flashed
** Attachment added: "sshot-2.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751269/+attachment/5061158/+files/sshot-2.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1751269
I'm glad to know that the problem is fixable, but my knowledge level is
not such that I could apply this patch without detailed instructions.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
*** This bug is a duplicate of bug 1737750 ***
https://bugs.launchpad.net/bugs/1737750
I changed to nvidia-340 and it works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
61 matches
Mail list logo
