View Single Post
Old 05-15-2016, 03:46 PM   #672
Gregg Bell
Gregg Bell
Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.
 
Gregg Bell's Avatar
 
Posts: 2,266
Karma: 3917598
Join Date: Jan 2013
Location: Itasca, Illinois
Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet
Quote:
Originally Posted by DMcCunney View Post
Leaving well enough alone is what I'd do. And I don't think the kernel is your problem. (I also don't think 16.10 will magically cure things.)
Thanks Dennis. Yeah, I'm all for leaving well enough alone, but I am a little nervous about the 16.10 upgrade. Do you have a guess as to what might happen.

And now the computer will only boot via the GRUB loader. Which is fine with me (and it boots really quickly). But again it will only boot to 15.10, not to the two 16.04 kernels on there.

Anyway, for the sake of giving the 16.10 upgrade a better chance of succeeding, do you think I should change that

GRUB_DEFAULT=4

back to

GRUB_DEFAULT=0

?


Quote:
Originally Posted by DMcCunney View Post
As it happens, I did just upgrade to Ubuntu 16.04 LTS here. I upgraded the Windows side to Win10 and ran into problems that had me cursing a blue streak. I booted into Ubuntu to Look Stuff Up, and while I was at it, did the 15.10->16.04 LTS upgrade. It proceeded with no issues and works fine.

On the Win10 side, the fixes were simple once I knew them.

The machine would not shutdown or restart, and required a power cycle. Turning off "hybrid shutdown" (intended for laptops in any case) fixed it.

The machine was also guaranteed to hang at some point no matter what I was doing (and even hung when I wasn't doing anything.) That turned out to be SSD related, and I had to turn off Windows write cache buffer flushing on that drive.

Once I made those fixes, Win10 worked perfectly. I'm up under it now. Took about 30 seconds to make the fixes, once I knew what they were.
______
Dennis
Must be nice to know what you're doing! LOL! Good for you!
Gregg Bell is offline   Reply With Quote