08-06-2014, 02:18 PM
[quote author=gold_finger link=topic=685.msg3622#msg3622 date=1406956488]
The dual-boot problem only occurs when another OS's grub is in charge of booting computer. Easiest way to solve the problem is to make sure LL 2.0 is in charge of booting. You can do that in one of two ways:
1. Install LL 2.0 last and direct grub bootloader installation to the MBR of the drive (which is normally the default on any installation).
2. If LL 2.0 is already on system and you don't want to bother re-installing it again, you can direct a re-installation of grub using a live DVD/USB. To do that, first determine which partition on the drive is your LL root partition, then follow instructions on this page to re-install grub while booted with LL install DVD/USB: https://help.ubuntu.com/community/Grub2/...D_terminal. If other OSs don't show on grub menu upon reboot, just boot into LL and run this in a terminal:
I tried the above, and used the instructions in the link, but sadly I couldn't get this to work. In my dual boot system (LL 2.0 with zorin 9, both are ubuntu 14.04), only zorin showed up on grub screen. So I mounted LL 2.0 using the Terminal within the live DVD of zorin 9 (and a subsequent attempt with LL live DVD), deleted/removed Grub from LL's sda (i.e. using sudo apt-get remove grub; sudo apt-get purge grub; sudo apt-get autoremove), and then reinstalled it according to your instructions. This had the effect of grub now showing both distros listed, but when I choose LL it went to the LL's start up screen but hung indefinitely at this screen. A forced restart by pressing the Ctrl-Alt-Del keys produced the same again. LL 1.0.8 dual boots very smoothly with zorin 9 - no issues whatsoever. By the way I ensured that LL 2 had the bootloader - on my laptop the first distro that is set up carries the flag boot, not the second as you mentioned in point (1) above. If I load LL 2 last, zorin 9 has the boot flag instead. I tried redirecting the bootloader to LL using Gparted when I set up LL 2 last (instead of first), using the Gparted option to do this, but this didn't work either.
Shall I still send you a screenshot from Gparted or an output from the terminal (i.e. from sudo blkid). It would be great to dual boot LL 2.0 with another distro, instead of using LL 1.0.8 with another distro, as the more up to date LL version is significantly better. Anyway, hopefully this one can be cracked... thanks for your continued support on this one.
Kind regards
Mike
The dual-boot problem only occurs when another OS's grub is in charge of booting computer. Easiest way to solve the problem is to make sure LL 2.0 is in charge of booting. You can do that in one of two ways:
1. Install LL 2.0 last and direct grub bootloader installation to the MBR of the drive (which is normally the default on any installation).
2. If LL 2.0 is already on system and you don't want to bother re-installing it again, you can direct a re-installation of grub using a live DVD/USB. To do that, first determine which partition on the drive is your LL root partition, then follow instructions on this page to re-install grub while booted with LL install DVD/USB: https://help.ubuntu.com/community/Grub2/...D_terminal. If other OSs don't show on grub menu upon reboot, just boot into LL and run this in a terminal:
I tried the above, and used the instructions in the link, but sadly I couldn't get this to work. In my dual boot system (LL 2.0 with zorin 9, both are ubuntu 14.04), only zorin showed up on grub screen. So I mounted LL 2.0 using the Terminal within the live DVD of zorin 9 (and a subsequent attempt with LL live DVD), deleted/removed Grub from LL's sda (i.e. using sudo apt-get remove grub; sudo apt-get purge grub; sudo apt-get autoremove), and then reinstalled it according to your instructions. This had the effect of grub now showing both distros listed, but when I choose LL it went to the LL's start up screen but hung indefinitely at this screen. A forced restart by pressing the Ctrl-Alt-Del keys produced the same again. LL 1.0.8 dual boots very smoothly with zorin 9 - no issues whatsoever. By the way I ensured that LL 2 had the bootloader - on my laptop the first distro that is set up carries the flag boot, not the second as you mentioned in point (1) above. If I load LL 2 last, zorin 9 has the boot flag instead. I tried redirecting the bootloader to LL using Gparted when I set up LL 2 last (instead of first), using the Gparted option to do this, but this didn't work either.
Shall I still send you a screenshot from Gparted or an output from the terminal (i.e. from sudo blkid). It would be great to dual boot LL 2.0 with another distro, instead of using LL 1.0.8 with another distro, as the more up to date LL version is significantly better. Anyway, hopefully this one can be cracked... thanks for your continued support on this one.
Kind regards
Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work