Thanks Yu Lou - in the end I did a fresh install. That was OK.
David
On 19 Nov 2016 02:00, "Yu Lou" <1633...@bugs.launchpad.net> wrote:
> I have a dual system of Ubuntu and Windows 7 and encountered the same
> problem after in place upgrade from 16.04 to 16.10. I tried boot-repair
> before but
As other replies Joseph. The only thing I didn't try was an upstream
kernel. But in the end I've just done a completely fresh install - so
someone else will need to try the upstream kernel approach.. But I'm
intrigued that two people found their solution via a new grub install,
while I didn't
I have tried 'boot-repair' in normal and advanced mode and have tried
reinstalling grub via sudo grub-install /dev/sda1 (then sda2, and finally
simply sda). All of these approaches have reported 'success' in bash/terminal
etc - but none have actually solved my problem.
Actually I'm wondering
Thanks Alex
I had tried 'boot-repair' to no avail, although success was reported.
But I tried your solution twice by using dev/sda1 (the current efi FAT32
boot partition) and /dev/sda2 ( the main ext4 partition). Neither solved
the problem although there were no error messages only 'successful'
Thanks Michka
I had tried the boot-repair option, to no avail.
But this time I made sure I had the latest version (I do) by completely
removing boot-repair and reinstalling, including repository, and tried
'advanced' option. 'Successful' but didn't solve the problem.
Then I tried default version
5 matches
Mail list logo
