Looks like I have serious issues with abbreviations. CURA != CUDA NUC != NIC
On Sun, May 7, 2017 at 5:07 PM, Howard White <[email protected]> wrote: > I did mention that this opportunity presented itself immediately after a > regular Ubuntu software update. The second or third thing I did was > connect up a USB DVD drive and boot from a known good (as in OLD) 16.04 > install disk. When that worked, I then went about trying to boot the NUC > from the prior kernel which also worked. I did not try to remove any other > package updates besides booting from the prior kernel. Conclusive? Prolly > not but at least I can boot. I only use the NUC as a media player to my TV. > > As for going to 16.10 from 16.04, no thanks. I definitely stick to the > LTS versions. Granted, the above stated purpose of this NUC would allow > for some distro version experimentation. > > Howard > > On 05/07/2017 03:23 PM, Csaba Toth wrote: > >> That's shocking. Intel NIC's driver source is great in terms of >> openness. What I'd wonder is what's your linux-firmware package version. >> That's a big lump of firmware collection, and in my mind it is more >> important than the kernel. Did that change recently (a.k.a. newer >> version)? If you have this problem I'm sure others have it too. Try a >> 16.10 fresh live CD, and if that's working well I'd consider a dist >> upgrade to Yakkety Yak. >> >> On Sun, May 7, 2017 at 6:39 AM, Howard White <[email protected] >> <mailto:[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. > -- -- 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.
