bill__ | Hi - after upgrading from xenial to yakkety(sp) I get a boot error:symbol table not loaded - any idea how to fix ? | 12:54 |
---|---|---|
ikonia | depends what is not loading | 12:54 |
ikonia | I suspect it will be because of a conflict | 12:54 |
bill__ | ikonia, I did some googling and it seems it is related to grub 2 - and is a know issue I believe - how would I troubleshoot that | 12:56 |
ikonia | if it's a known issue, what do they suggest | 12:57 |
bill__ | ikonia, well that is a hotly contested subject - some say grub problem some say ubuntu issue with older packages so no resolution - but happens when you upgrade | 12:59 |
bill__ | just came here on the chance someone might know | 12:59 |
ikonia | what stage does it get to in the boot process | 12:59 |
bill__ | happens just after you select the drive to boot - I have 5 bootable drives including 2 windows - mint - 2 ubuntu | 13:00 |
ikonia | are you %101 the grub you are booting is supplied by ubuntu | 13:01 |
ikonia | rather than one of the other distros | 13:01 |
bill__ | yes - but I am booting the from the upgraded machine which was xenial and is now yakkety so that grub is probably different | 13:02 |
ikonia | how are you %101 sure that grub on that drive is the one from ubuntu as you have many distros with many grub installs | 13:02 |
bill__ | yes my bios boot order is set to boot off the upgraded drive | 13:03 |
ikonia | I'm not asking you what your bios is booting, I'm asking how can you be certain that grub on that drive is the grub installed by 16.10 | 13:03 |
bill__ | that is the issue - when I upgraded I went from 16.04 to 16.10 - if grub was upgraded then it would be the grub from 16.10 | 13:05 |
ikonia | not what I'm asking you | 13:05 |
bill__ | but I am unsure of the grub version - how can I check | 13:05 |
ikonia | you should have been certain of this before the upgrade | 13:05 |
ikonia | as now it won't boot | 13:05 |
ikonia | but right now you don't know what grub version is on it, and from what install | 13:05 |
bill__ | it does boot - just has this error message - anyway - bye | 13:06 |
ikonia | the fist point of call for me would be to use some live media to re-apply grub from 16.10 to the right boot sector | 13:06 |
ThePendulum | 'lo | 13:20 |
ThePendulum | I'm wondering if I should expect much trouble upgrading from the 16.10 beta 2 to the official release | 13:21 |
ThePendulum | don't really have an awful lot to do today and figured I'd reorganize my disks and pop on some fresh installs, but apparently I'm a week too early for 16.10 | 13:21 |
krytarik | !daily | ThePendulum | 13:48 |
ubottu | ThePendulum: Daily builds of the CD images of the current development version of Ubuntu are available at http://cdimage.ubuntu.com/daily-live/current/ | 13:48 |
=== lordieva1er is now known as lordievader | ||
=== pavlushka is now known as Guest77853 | ||
=== Guest77853 is now known as pavlushka | ||
ThePendulum | urf, I was hoping to start using 16.10 after not being able to upgrade to 16.04 because of some input timing issue with my Dell monitors | 18:12 |
ThePendulum | but the issue is still there :( | 18:12 |
dn5 | hello | 18:28 |
dn5 | may I ask why official ubuntu for vagrant doesnt have SocketCAN module integrated? | 18:28 |
dn5 | I can't bring vcan up | 18:28 |
dn5 | only can and can_raw | 18:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!