On 22/06/14 22:11, Billie Walsh wrote:
On 06/21/2014 10:34 PM, Felix Miata wrote:
On 2014-06-21 19:43 (GMT-0700) Tony Alfrey composed:
Please recall that I'm trying to boot my Windows disk from grub. SuSE boots fine, but a section in grub2/grub.cfg for Windows that does not boot Windows. Windows boots fine if I change the BIOS drive order. OK, so I look on-line and I see that for /grub/menu.lst the code to /add/ to the Windows section of grub is:
map (hd0,0) (hd1,0) map (hd1,0) (hd0,0) rootnoverify (hd1,0) makeactive chainloader +1
But my question is... might there be a difference for the configuration used for /grub2/grub.cfg ?
Definitely. http://www.gnu.org/software/grub/manual/grub.html#Changes-from-GRUB-Legacy
If you alter config with YaST, it should be right. The first HD partition in Grub Legacy (menu.lst) is ",0", but in Grub2 "grub.cfg" it is ",1".
I remembered reading about this a while back somewhere and took some time to remember what it was. I haven't tried it myself so, caveat emptor.
Grub Customizer
On a command line, as ROOT (ie, 'su -' <password> execute: grub2-mkconfig -o /boot/grub2/grub.cfg assuming that you only have 2 systems installed- Windows and openSUSE 13.1, say (where the openSUSE version is actually using grub2 and not grub legacy). This will create the correct grub menu which will boot either oS or Windows. Go to this article, save it and keep reading it until what it contains becomes second nature - and bookmark this article for others in the future: http://www.linuxidentity.com/us/down/articles/LSK_multi_distro_install_US.pd... NOTE: Make a backup of /boot before doing above just in case. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org