Running Xubuntu 14.04 and just upgraded to 3.13.0-144 from 3.13.0-143
and needed to re-apply the fix again.
The fix I have used is to edit /usr/src/linux-
headers-3.13.0-144/include/linux/vermagic.h
$ cd /usr/src/linux-headers-3.13.0-144/include/linux
$ diff vermagic.h vermagic.h.WAS
27,28c27
<
Running Ubuntu 16.04 (xenial) in VirtualBox (Windows host). After Ubuntu update
got affected too - vboxdrv dkms won't install. dmesg would give:
[ 260.993242] vboxdrv: version magic '4.4.0-119-generic SMP mod_unload
modversions ' should be '4.4.0-119-generic SMP mod_unload modversions retpoline
Still having missing retpoline issues with vboxdrv 5.2.8 on 4.4.0-119
(14.04). Anyone worked this around?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21
Just a follow-up note for 14.04 users that still want a source for a
newer gcc-5 (with c++14 support) or gcc-6/7/8:
I have purged the ppa:ubuntu-toolchain-r/test and switched to the
ppa:jonathonf/gcc per comment #86 and not had any further nvidia driver
problems.
--
You received this bug notific
14.04 here as well. I didn't try purging the PPA, so I don't know if
that works, but what I did was the following:
1. disable the PPA (and sudo apt update)
2. Synaptic refused to apply the changes, so:
$ sudo apt install gcc-4.9-base=4.9.3-0ubuntu4
lib32gcc1=1:4.9.3-0ubuntu4 gcc-4.9-base:i386=4.
So what's the official approach for 14.04 with 4.4.0-116 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
Followed #57 with success (had an exactly same problem), no need for this:
"Then after removing and reinstalling the 4.4.0-116 kernel"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.
Christopher M. Penalver - sounds good. Thanks! Bill
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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) due to
just found this on the GCC thread:
Launchpad Janitor (janitor) wrote on 2018-03-19:#7
This bug was fixed in the package gcc-4.8 - 4.8.5-4ubuntu8
---
gcc-4.8 (4.8.5-4ubuntu8) bionic; urgency=medium
[ Matthias Klose ]
* Stop build gcj in current distro releases. Addresses:
Bill Miller, given your issue was root caused by you to having an
outdated gcc-4.8 package (now since updated), and when receiving the
update this problem is resolved, I'll mark this Fix Released.
** Changed in: gcc-4.8 (Ubuntu)
Status: New => Fix Released
** No longer affects: linux (Ubun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-4.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.
** Project changed: gcc => gcc-4.8 (Ubuntu)
** No longer affects: nvidia-graphics-drivers-384 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 b
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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) by an insufficient compi
Just a quick note to confirm that removing and installing previous
failing DKMS modules for kernel 4.4.0-116 as explained in comment 30,
worked wonders for our issue with vboxdrv issue and retpoline.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tomorrow, I boot my PC on 3.13.0.142 kernel.
There was lots of updates for several compiler.
Right after I reboot my PC and go to the -143 kernel. dkms remove
nvidia, dkms install nvidia.
then, modinfo nvidia| grep vermagic now shoes "retpoline".
At this point I know everything was fixed.
Rebo
Multiple Ubuntu 14.04 systems with newer compilers, and I don't really
want to remove them...
Can we get updated compilers in the ubuntu-toolchain-r/test ppa
... or optional kernels without 'retpoline'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
to Sebastien (olorinseb) about " infinite login loop problem":
It's another bug, reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891960
https://devtalk.nvidia.com/default/topic/1029683/suspend-swap-group-
failed-resume-swap-group-failed-nvidia-390-25/
According to Debian staff,
How to install the latest gcc compiler without pain
sudo add-apt-repository --remove ppa:ubuntu-toolchain-r/test # the best
remedy whatsoever
sudo add-apt-repository --remove ppa:jonathonf/gcc-7.2# (also
broken
https://askubuntu.com/questions/1009433/dependency-issues-while-ins
I'm running Ubuntu 14.04 kernel 3.13.0-143-generic.
I have the infinite login loop problem.
On older kernel (-142) everything still working correctly
I have gcc 4.8.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Could we please know when this bug is going to be fixed at last?
If is not uncommon, actually quite common I would say, to have a NVIDIA
graphic card and a more recent version of GCC installed than the one in
the Ubuntu distribution, which is quite old. And then the machine is
broke when the new k
Yep, mine reverts to 1024x760 76Hz and has no options whatsoever.
It's a bit of a showstopper.
dmesg:
nvidia: version magic '3.13.0-143-generic SMP mod_unload modversions ' should
be '3.13.0-143-generic SMP mod_unload modversions retpoline '
works:
Linux betlogbrick 3.13.0-142-generic #191-Ubunt
I had the same problem however I don't have a Nvidia driver (Intel HD
Graphics instead)
I got this message before enter a loop:
video: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be
'3.13.0-143-generic SMP mod_unload modversions retpoline '
drm: version magic '3.13.0-14
I had the same problem with zfs too.
Changed :
CONFIG_RETPOLINE=y
to
CONFIG_RETPOLINE=n
in
/boot/config-4.4.0-116-generic
and reinstalled the nvidia/zfs kernel modules.
To me it seems that the config file shipped with the kernel is not
matching the version used for compiling.
--
You received
Hello everyone,
Thanks to your answers and this discussion. I ran into this problem yesterday.
Although I tried the instructions by @cjjefcoat on #57, it didn't give me back
my display as expected. Unity got screwed up and although I could see the
display, the rendering was not proper. The windo
Bryce Schober (bryce-schober): I had a very similar issue, but on 16.04
and wanting gcc-7. Adding the the toolchain ppa made gcc-5 subject to
upgrading, triggering this issue. I managed to deal with it with package
pinning and aptitude (see comment 58).
Here are a few more details if in case you w
On Ubuntu 14.04, I've installed the ubuntu-toolchain-r/test ppa in order
to get a gcc-5 compiler, and the assumedly-conflicting
4.8.5-2ubuntu1~14.04.1 came from that PPA along for the ride.
Is there a better PPA option for installing gcc-5 on Ubuntu 14.04?
--
You received this bug notification b
Solve the problem with the instruction from #57 under Ubuntu 16.04.4
LTS.
At first, I cannot find the driver when I typed nvidia-smi. So I try to
reinstall the nvidia driver. In this process, I met the absolutely same
problem as
https://devtalk.nvidia.com/default/topic/1030325/nvidia-driver-
inst
I manage 300+ machines that run openafs that has a dkms built kernel
module like the nvidia module that needs to be built. I also manage
dozens of nvidia gpu servers where users have sudo access and can
install anything they want. Here is a snippet of what I found. Note this
is for 16.04 systems bu
probably related to bug #1749261
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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) by an insufficient compiler
switching to "beta" version of gcc (Ubuntu 7.3.0-5ubuntu1~14.04.york0) 7.3.0
and rebuilding the kernel modules in question for 4.4.0-116 seemingly did the
job.
is this really what you wanted from a good amount of the end users by
publishing those kernel?
** Summary changed:
- 4.4.0-116 Kernel u
are you thinking of something like this?
https://launchpad.net/~jonathonf/+archive/ubuntu/gcc-7.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks
are you sure it has arrived with _some_ gcc version already.
publications indicate its very experimental still and i can not see any
of the typical switches beeing honored by the gcc versions on my
machine. (and i was able to switch them forth and back using "update-
alternatives") needless to say
Same here error with edvi's DisplayLinkManager process to get a
displaylink screen from a USB 3.0 hub/docking station like
https://www.anker.com/store/USB-3.0-Docking-Station/68ANDOCKS-BA
went back to 4.4.0-112 to work.
Will wait future 4.4.0-(>116) kernel to retry.
--
You received this bug noti
@cjjefcoat
Thanks for your advice,I have meet the same issue in virtualbox after the
ubuntu 14.04 kernel update to 116.
After downgrade the gcc to 4.8.4, and reinstall the 116 kernel and
virtualbox 5.2,it work!
** Attachment added: "Virtualbox errror info"
https://bugs.launchpad.net/ubuntu/+
As mentioned in #47, same problem on trusty + xenial HWE stack
(14.04.5).
Additionally, had a gcc version mismatch, don't know where that came
from.
Meta package gcc was 4:4.8.2-1ubuntu6, but /usr/bin/gcc (and corresponding
package gcc-4.8) was 4.8.5-1ubuntu1~14.04 .
I also had installed just gc
Silvano (spaccabyte), if you never added that PPA (and the majority of
Ubuntu users will not have) then there is nothing to remove. In that
case, you probably have the "standard" gcc and could just follow the
instructions at
https://ubuntuforums.org/showthread.php?t=2385621&s=f41dc2da85d14b7d58541
trying the comment 57
sudo ppa-purge ppa: ubuntu- toolchain- r / test
Updating packages lists
PPA to be removed: ppa: ppa:
Warning: Could not find package list for PPA: ppa: ppa:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I resolved the problem with #57 instructions.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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 ma
It seems like the kernel and the nvidia driver weren't built using the
same compiler.
Please, either ssh into your machine, or press CTRL+ALT+F2 and do the
following:
1) Make sure security updates are enabled, and update your system ("apt-
cache policy gcc-5" should report 5.4.0-6ubuntu1~16.04.9
Had the same issue on 14.04 with HWE kernel.
Last Friday morning I got offered the -116 kernel - which broke the
nvidia driver module, forcing me to revert back to the -112 kernel.
Only today (not checked during the weekend) I got offered the compiler
update, from 4.8.4-2ubuntu1~14.04.3 to 4.8.4-
The instructions provided by @cjjefcoat also fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
Following instructions provided by @cjjefcoat, I managed to get kernel -116
running.
It turns out that just removing the "ppa:ubuntu-toolchain-r/test" ppa and
reinstalling the gcc-4.8 wasn't sufficient to get it downgraded to "gcc (Ubuntu
4.8.4-2ubuntu1~14.04.4) 4.8.4". Anyway, *purging* the ppa
Hello, just had the same experience :( not so funny, Thanks to you all,
I just downloaded linux-image-
extra-4.4.0-116-generic_4.4.0-116.140_amd64.deb via internet on my
mobile , then copy paste to pc, and installed manualy (sudo dpkg -i
linux-image-extra-4.4.0-116-generic_4.4.0-116.140_amd64.deb)
Hello, just had the same experience :( not so funny, Thanks to you all,
I just donloaded 116 and installed manualy, after reboot all good, back
in business baby :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Thanks to the instructions posted by @cjjefcoat I was able to get 116 up
and running on my machine. The only difference was that after purging
the toolchain ppa I had to run update-alternatives to get gcc to point
to gcc-5.
--
You received this bug notification because you are a member of Ubuntu
The version in the toolchain ppa currently does not match the "retpoline"
changes in the new kernel ( see discussion above), so should not be used to
compile modules. Which is a pain if you still want to use a newer gcc
alongside for other purposes, because adding the ppa upgrades the default
gcc.
@matpen,
I had similar problems with gcc 5.4.1 on Ubuntu 16.04. I don't think
that version has been updated. My gcc 5.4.1 version was from the
ubuntu-toolchain-r/test ppa. I removed that repository and "downgraded"
to the official Ubuntu 16.04 gcc-5 (5.4.0-6ubuntu1~16.04.9). (See
https://askubu
I can use my Ubuntu 14.04.05 with kernel 4.4.0-112-generic normally, but
when it comes to booting with 4.4.0-116-generic Nvidia drivers don't
work. My gcc-4.8 version is "gcc (Ubuntu 4.8.5-2ubuntu1~14.04.1) 4.8.5"
and gcc-5 version is "gcc-5 (Ubuntu 5.4.1-2ubuntu1~14.04) 5.4.1
20160904".
I tried r
I am facing both the Nvidia problem (cannot login into gnome) and the
VirtualBox problem (cannot start VMs). I just tried all instructions
found here (reinstalling the kernel, even reinstalling VirtualBox and
DKMS modules manually) with both the official gcc and the new gcc-7 from
PPA, but no luck.
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 runni
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 a
Those for whom it didn't work, see post #7 at
https://ubuntuforums.org/showthread.php?t=2385621&p=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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks
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)"
ht
Anyone else having this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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 about this
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 b
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** 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.
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 differenc
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 everythi
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: 4.4
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia dr
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.
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 ho
@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
Bugs, which is subscribed to Ubuntu.
https:
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
https://ubuntu.pkgs.org/16.04/ubuntu-updates-main
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21
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, while
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?
-
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21
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 t
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.
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 mo
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
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
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
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 DKMS
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update
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
Bugs, which is subscribed to
Kaan Akşit: You are going down the same rabbit hole that I did and it
won't work, and will just mess up your system. The problem is not the
nVidia driver, it's the kernel upgrade. Go to the thread at
https://ubuntuforums.org/showthread.php?t=2385621&p=13742281#post13742281
and you will see what
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 runni
FWIW some NVIDIA-related changes were apparently made in 114:
2018-02-09 - Khalid Elmously
linux (4.4.0-114.137) xenial; urgency=medium
* linux: 4.4.0-114.137 -proposed tracker (LP: #1748484)
* ALSA backport missing NVIDIA GPU codec IDs to patch table to
Ubuntu 16.04 LTS Kernel (LP: #1744117)
- A
Not only same video issue as others on Trusty with Nvidia 340.102 driver
for GEForce 8400GS, but am also unable to log in.Entering PW just keeps
flipping me back to "Enter PW box". Old 112 kernel works just fine so I
will stick with that until a fix is available.
--
You received this bug notifica
Add me to the List of People with this problem, nvidia 384.111 worked
great until this kernel now same problem as original poster. Had to go
back to 112 to get it to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
This also seems to affect ZFS on Linux modules:
zavl: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Bill Miller, I can ssh into the system and install packages - apt-get
still works, etc. Right now the only thing I can't do is get into the
desktop; it shows a login screen but won't accept my password (even
though my password works fine in ssh). I think it is because when I
tried to install the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Mythological, you have to fix the system to the point that you can
install packages. I am not sure you are that point yet from your
description. Once you are there, you can install an old kernel by
following the procedure outlined here
https://askubuntu.com/questions/928146/install-an-older-kernel
Bo9b Miller, how do I install "-112"? I am afraid I have already dug
myself into so deep a hole I don't want to make any more mistakes, and I
have no idea what you mean by "-112". Please explain, or point me to a
page that does.
--
You received this bug notification because you are a member of
Bob Miller, how do I install "-112"? I am afraid I have already dug
myself into so deep a hole I don't want to make any more mistakes, and I
have no idea what you mean by "-112". Please explain, or point me to a
page that does.
--
You received this bug notification because you are a member of Ubu
Same thing here on 16.04, with nvidia driver 384.111.
Kernel 4.4.0-112: no problems
kernel 4.4.0-116: Low res and can't login on graphical mode.
I have tried to uninstall and reinstall nvidia drivers to no effect.
I did a diff for dmesg output on both cases. The relevant bits are:
> Spectre V2
** Summary changed:
- 14.04 Kernel update on 2/21 breaks Nvidia drivers
+ 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17509
93 matches
Mail list logo