One more trick: If you'd like to avoid that particular version from getting you into trouble in the future, through an inadvertent apt-get upgrade, here's a trick I learned from dealing with a broken nVidia driver update:
$ ls -l /etc/apt/preferences.d/pin-nvidia ; cat /etc/apt/preferences.d/pin-nvidia -rw-r--r-- 1 root root 76 Dec 6 12:11 /etc/apt/preferences.d/pin-nvidia Package: nvidia-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -1 Throw the package name on the first line, the full package version on the second, and the -1 Pin tells apt NEVER to install that version. You can still upgrade beyond it, but this signals to apt that this particular version is blacklisted. The filename doesn't matter, but you could call it something like "pin-4.4.0-77-kernel-is-stupidly-broken" and it will work fine. On Mon, May 8, 2017 at 2:03 PM, Tilghman Lesher <[email protected]> wrote: > It would appear that you are not the only one having trouble with > 4.4.0-77. Reverting to a previous kernel does appear to be the > suggested fix: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687623 > > 4.4.0-75 does appear to work. Try installing that version, followed > by removing 4.4.0-77 and see if that works for you after rebooting. > > On Mon, May 8, 2017 at 1:56 PM, Tilghman Lesher <[email protected]> wrote: >> You ought to be able to alter the grub configuration files to tell it >> that the previous kernel version should be the default, thus ensuring >> that even if you aren't booted to that particular kernel, that it will >> boot to your preferred kernel upon the next reboot. >> >> I'd also suggest posting a bug report back to Ubuntu's bug reporting >> system. I would suspect that it's already been reported, and you can >> simply add your "Me too" vote to having it prioritized for a fix. >> Persons on the bug report might even have a fix for you, in terms of >> adding a particular PPT to get the kernel driver fixes. >> >> On Sun, May 7, 2017 at 8:39 AM, Howard White <[email protected]> wrote: >>> Just curious; might only be me... Yes, there are hundreds of different NUC >>> combinations. >>> >>> The most recent kernel update, 4.4.0-77, left my NUC in a confused state. >>> Post upgrade the network interface quit and my wireless keyboard and >>> pointing device (connected to a USB thing) lost contact, though a USB >>> keyboard and mouse worked. After a few minutes of head scratching, I >>> decided to try the previous kernel and all is square, plumb and level. >>> >>> Just interrupting GRUB at the correct time to get the option to boot a prior >>> kernel is challenging enough :/ >>> >>> Howard >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "NLUG" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/nlug-talk?hl=en >>> >>> --- You received this message because you are subscribed to the Google >>> Groups "NLUG" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Tilghman > > > > -- > Tilghman -- Tilghman -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
