You are not logged in.
I can no longer get into Arch Linux from the windows 7 boot manager after the last two updates of grub2. There was no problem with earlier versions. "GRUB" is displayed and the system stops starting if "Arch Linux" is selected.
There are four primary partitions on the hard disk.
1) First three were formatted into NTFS and win 7 system on the 1st one. The 4th (/dev/sda4) was ext4 for Arch Linux.
2) Win 7 boot manager was installed on MBR and grub2 on /dev/sda4. The first 8 sectors of /dev/sda4 was dumped to a file c:\boot\archlinux.bin and an entry was added to win 7 bcd as below.
Real-mode Boot Sector
---------------------
identifier {f234c0b4-d796-11e0-8585-f04da2c44d3d}
device partition=C:
path \boot\archlinux.bin
description Arch Linux
locale en-US
Could somebody help?
Last edited by lapa (2012-06-27 05:18:21)
Offline
I think you should be using GRUB 2 to boot into Windows 7, not the Windows 7 boot manager to boot into Arch.
No offence but this isn't the Windows tech support forum, you know.
If it were me, I would chroot using a "live" Linux distribution (architecture must match, don't use i686 with an x86_64 install) and follow the wiki entry. But then again, for a few months now I switched to Syslinux and I'm liking it. I find it to be much more "KISS" than GRUB 2 (which I've been using for almost 2 years). You should check it out. The syslinux.cfg Windows entry looks like this:
LABEL windows
MENU LABEL Windows 7
KERNEL chain.c32
APPEND hd0 1I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Thanks, but I prefer win 7 boot manager as the default boot loader. Actually there was an entry for Win 7 in my grub2 configuration when things were right and I could jump between two boot managers.
I think something is not right with the boot record dumped from /dev/sda4. I can get into Arch Linux with an older version of grub2 on a USB key drive.
Offline
The thing is that Windows 7 may have some trouble if its boot partition or its only partition is not set to be the active one. That's a common case when you dual boot a Linux distribution, where the partition containing /boot would have the "boot" flag set. I guess that's why lapa wants to use Windows BCD as the boot loader other than GRUB2.
I suggest you take a look at EasyBCD, a Windows program able to add entries to Windows' BCD for the common loaders for Linux. Try out the latest beta 2.2 build 175 and see if it works.
Offline
Just updated to the latest version of grub2 and the problem is gone. Guess it is an issue with the last release of grub2.
Thanks for all the replies!
Offline