Arch & Android-x86 Dual Boot ?

Hi All
Has anyone installed Android-x86 as a Dual Boot with Arch yet ? Its something that i'm considering doing and wondered if anyone had done it yet ?
Cheers

...I don't care
I see no reason why it wouldn't work... I would think a simple google search would tell you the answer, no?

Similar Messages

[SOLVED] Grub refuses to boot Arch on a dual boot

Hi,
After hours of trying things out and searching the web for answers, I finally gave up and joined this helpforum.
I found several similar topics, but none seemed to work.
So here's the deal.
My HDD looks like this
sda1 (/boot)
sda2 (Windows7, bootflag)
sda3 (/swap)
sda5 (/)
sda6 (NTFS ExtraData)
So i'm trying to dual boot windows7 and arch.
my menu.lst looks like this:
# (0) Arch Linux
title Arch Linux
root (hd0,4)
kernel /vmlinuz-linux root=/dev/sda5 ro
initrd /initramfs-linux.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,4)
kernel /vmlinuz-linux root=/dev/sda5 ro
initrd /initramfs-linux-fallback.img
# (2) Windows
title Windows 7
rootnoverify (hd0,1)
makeactive
chainloader +1
Windows boots fine, but when I try to boot Arch I get this
Booting 'Arch Linux'
title Arch Linux
root (hd0,4)
kernel /vmlinuz-linux root=/dev/sda5 ro
error 15: File not found
Thanks,
Chris
Last edited by preute (2011-12-12 18:51:16)

I think that the lines
root (hd0,4)
are wrong. They are for GRUB's root (which is /boot), not /. So I think it should be
root (hd0,0)
instead.

Arch & Windows 8 Dual Boot -- Windows Boot Loader loads grub-rescue

Arch works fine,but as it always happens Windows boot went down. Both OS are EFI.
Note that boot secure and fast boot were disabled for Windows 8.
I used os-prober, but did not fix anything; so, I removed it. I tried to hack things out using boot-repair from Ubuntu, but it requires a repository, grub-efi, from Ubuntu that Arch doesn't have.
I am trying to modify files in grub.d and grub.cfg and hopefully fix something.
Exact description:
- archgrub loads and shows 3 entries. Two for Arch that load the sys succesfully and one for Windows 8 that fails.
- When I try to execute Windows from grub, it brings me to a grub rescue>
and shows error /boot/grub/x86_64-efi/normal.mod not found
As far as I am concerned this .mod is from Linux, so I don't know why it is being called into Windows loading procedures.
lsblk returns:
[jav@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
|-sda1 8:1 0 1000M 0 part
|-sda2 8:2 0 260M 0 part
|-sda3 8:3 0 1000M 0 part
|-sda4 8:4 0 128M 0 part
|-sda5 8:5 0 605.3G 0 part
|-sda6 8:6 0 5.4G 0 part /boot/efi
|-sda7 8:7 0 25G 0 part
|-sda8 8:8 0 20G 0 part
|-sda9 8:9 0 244.1G 0 part /
`-sda10 8:10 0 29.3G 0 part
sr0 11:0 1 1024M 0 rom
Here's the output of fdisk. Another weird thing is that sometimes ubuntu would show on my terminal. See the first line below, "jav@ubuntu"?!
[jav@ubuntu ~]$ sudo fdisk -l
[sudo] password for jav:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: [i deleted this]
Device Start End Size Type
/dev/sda1 2048 2050047 1000M Windows recovery environment
/dev/sda2 2050048 2582527 260M EFI System
/dev/sda3 2582528 4630527 1000M unknown
/dev/sda4 4630528 4892671 128M Microsoft reserved
/dev/sda5 4892672 1274335231 605.3G Microsoft basic data
/dev/sda6 1847777280 1859151871 5.4G EFI System
/dev/sda7 1859151872 1911580671 25G Microsoft basic data
/dev/sda8 1911580672 1953523711 20G Windows recovery environment
/dev/sda9 1335775232 1847777279 244.1G Linux filesystem
/dev/sda10 1274335232 1335775231 29.3G Microsoft basic data
And, bootinfoscript output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda2: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi
sda3: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi /bootmgr /boot/bcd
sda4: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
sda5: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 6.02 ... :..(:,:0:4:8:....D:H:L:[.T:[.\:`:d:[.l:p:t:x:|:.:.:.:.:.:.:.:.....................
Boot sector info: Syslinux looks at sector 99102 of /dev/sda6 for its
second stage. SYSLINUX is installed in the /syslinux
directory. No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /syslinux/syslinux.cfg
/syslinux/ldlinux.sys
sda7: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda8: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda9: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sda10: _________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 2,050,047 2,048,000 Windows Recovery Environment (Windows)
/dev/sda2 2,050,048 2,582,527 532,480 EFI System partition
/dev/sda3 2,582,528 4,630,527 2,048,000 -
/dev/sda4 4,630,528 4,892,671 262,144 Microsoft Reserved Partition (Windows)
/dev/sda5 4,892,672 1,274,335,231 1,269,442,560 Data partition (Windows/Linux)
/dev/sda6 1,847,777,280 1,859,151,871 11,374,592 EFI System partition
/dev/sda7 1,859,151,872 1,911,580,671 52,428,800 Data partition (Windows/Linux)
/dev/sda8 1,911,580,672 1,953,523,711 41,943,040 Windows Recovery Environment (Windows)
/dev/sda9 1,335,775,232 1,847,777,279 512,002,048 Data partition (Linux)
/dev/sda10 1,274,335,232 1,335,775,231 61,440,000 Data partition (Windows/Linux)
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 CE62D9F062D9DCF1 ntfs WINRE_DRV
/dev/sda10 150a8788-6049-45ed-85af-ded92a2c0801 ext4
/dev/sda2 16DC-8816 vfat SYSTEM_DRV
/dev/sda3 7CDD-0403 vfat LRS_ESP
/dev/sda4
/dev/sda5 40E4E0CFE4E0C7EC ntfs Windows8_OS
/dev/sda6 9C3F-2A9E vfat
/dev/sda7 7240E43740E40427 ntfs LENOVO
/dev/sda8 422CE5EA2CE5D945 ntfs PBR_DRV
/dev/sda9 1a765403-f251-43d8-8edf-c191475d3837 ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda6 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda6 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda9 / ext4 (rw,relatime,data=ordered)
============================= sda6/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
## Attempt at fixing grub
# insmod fat
# set root='hd0,gpt6'
### BEGIN /etc/grub.d/30_os-prober ###
#menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
# insmod part_gpt
# insmod fat
# set root='hd0,gpt2'
# if [ x$feature_platform_search_hint = xy ]; then
# search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
# else
# search --no-floppy --fs-uuid --set=root 16DC-8816
# fi
# chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8 UEFI" {
set root='(hd0,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
========================= sda6/syslinux/syslinux.cfg: ==========================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
=================== sda6: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
================= sda6: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
============== sda6: Version of COM32(R) files used by Syslinux: ===============
syslinux/cat.c32 : not a COM32/COM32R module
syslinux/chain.c32 : not a COM32/COM32R module
syslinux/cmd.c32 : not a COM32/COM32R module
syslinux/config.c32 : not a COM32/COM32R module
syslinux/cptime.c32 : not a COM32/COM32R module
syslinux/cpuid.c32 : not a COM32/COM32R module
syslinux/cpuidtest.c32 : not a COM32/COM32R module
syslinux/debug.c32 : not a COM32/COM32R module
syslinux/disk.c32 : not a COM32/COM32R module
syslinux/dmitest.c32 : not a COM32/COM32R module
syslinux/elf.c32 : not a COM32/COM32R module
syslinux/ethersel.c32 : not a COM32/COM32R module
syslinux/gfxboot.c32 : not a COM32/COM32R module
syslinux/gpxecmd.c32 : not a COM32/COM32R module
syslinux/hdt.c32 : not a COM32/COM32R module
syslinux/hexdump.c32 : not a COM32/COM32R module
syslinux/host.c32 : not a COM32/COM32R module
syslinux/ifcpu.c32 : not a COM32/COM32R module
syslinux/ifcpu64.c32 : not a COM32/COM32R module
syslinux/ifmemdsk.c32 : not a COM32/COM32R module
syslinux/ifplop.c32 : not a COM32/COM32R module
syslinux/kbdmap.c32 : not a COM32/COM32R module
syslinux/kontron_wdt.c32 : not a COM32/COM32R module
syslinux/ldlinux.c32 : not a COM32/COM32R module
syslinux/libcom32.c32 : not a COM32/COM32R module
syslinux/libgpl.c32 : not a COM32/COM32R module
syslinux/liblua.c32 : not a COM32/COM32R module
syslinux/libmenu.c32 : not a COM32/COM32R module
syslinux/libutil.c32 : not a COM32/COM32R module
syslinux/linux.c32 : not a COM32/COM32R module
syslinux/ls.c32 : not a COM32/COM32R module
syslinux/lua.c32 : not a COM32/COM32R module
syslinux/mboot.c32 : not a COM32/COM32R module
syslinux/meminfo.c32 : not a COM32/COM32R module
syslinux/menu.c32 : not a COM32/COM32R module
syslinux/pcitest.c32 : not a COM32/COM32R module
syslinux/pmload.c32 : not a COM32/COM32R module
syslinux/poweroff.c32 : not a COM32/COM32R module
syslinux/prdhcp.c32 : not a COM32/COM32R module
syslinux/pwd.c32 : not a COM32/COM32R module
syslinux/pxechn.c32 : not a COM32/COM32R module
syslinux/reboot.c32 : not a COM32/COM32R module
syslinux/rosh.c32 : not a COM32/COM32R module
syslinux/sanboot.c32 : not a COM32/COM32R module
syslinux/sdi.c32 : not a COM32/COM32R module
syslinux/sysdump.c32 : not a COM32/COM32R module
syslinux/vesainfo.c32 : not a COM32/COM32R module
syslinux/vesamenu.c32 : not a COM32/COM32R module
syslinux/vpdtest.c32 : not a COM32/COM32R module
syslinux/whichsys.c32 : not a COM32/COM32R module
syslinux/zzjson.c32 : not a COM32/COM32R module
=============================== sda9/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda9
UUID=1a765403-f251-43d8-8edf-c191475d3837 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
#UUID=9C3F-2A9E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=9C3F-2A9E /boot vfat defaults 0 2
UUID=9C3F-2A9E /boot/efi vfat defaults 0 1
============== sda9: Version of COM32(R) files used by Syslinux: ===============
boot/syslinux/cat.c32 : not a COM32/COM32R module
boot/syslinux/chain.c32 : not a COM32/COM32R module
boot/syslinux/cmd.c32 : not a COM32/COM32R module
boot/syslinux/config.c32 : not a COM32/COM32R module
boot/syslinux/cptime.c32 : not a COM32/COM32R module
boot/syslinux/cpuid.c32 : not a COM32/COM32R module
boot/syslinux/cpuidtest.c32 : not a COM32/COM32R module
boot/syslinux/debug.c32 : not a COM32/COM32R module
boot/syslinux/disk.c32 : not a COM32/COM32R module
boot/syslinux/dmitest.c32 : not a COM32/COM32R module
boot/syslinux/elf.c32 : not a COM32/COM32R module
boot/syslinux/ethersel.c32 : not a COM32/COM32R module
boot/syslinux/gfxboot.c32 : not a COM32/COM32R module
boot/syslinux/gpxecmd.c32 : not a COM32/COM32R module
boot/syslinux/hdt.c32 : not a COM32/COM32R module
boot/syslinux/hexdump.c32 : not a COM32/COM32R module
boot/syslinux/host.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu64.c32 : not a COM32/COM32R module
boot/syslinux/ifmemdsk.c32 : not a COM32/COM32R module
boot/syslinux/ifplop.c32 : not a COM32/COM32R module
boot/syslinux/kbdmap.c32 : not a COM32/COM32R module
boot/syslinux/kontron_wdt.c32 : not a COM32/COM32R module
boot/syslinux/ldlinux.c32 : not a COM32/COM32R module
boot/syslinux/libcom32.c32 : not a COM32/COM32R module
boot/syslinux/libgpl.c32 : not a COM32/COM32R module
boot/syslinux/liblua.c32 : not a COM32/COM32R module
boot/syslinux/libmenu.c32 : not a COM32/COM32R module
boot/syslinux/libutil.c32 : not a COM32/COM32R module
boot/syslinux/linux.c32 : not a COM32/COM32R module
boot/syslinux/ls.c32 : not a COM32/COM32R module
boot/syslinux/lua.c32 : not a COM32/COM32R module
boot/syslinux/mboot.c32 : not a COM32/COM32R module
boot/syslinux/meminfo.c32 : not a COM32/COM32R module
boot/syslinux/menu.c32 : not a COM32/COM32R module
boot/syslinux/pcitest.c32 : not a COM32/COM32R module
boot/syslinux/pmload.c32 : not a COM32/COM32R module
boot/syslinux/poweroff.c32 : not a COM32/COM32R module
boot/syslinux/prdhcp.c32 : not a COM32/COM32R module
boot/syslinux/pwd.c32 : not a COM32/COM32R module
boot/syslinux/pxechn.c32 : not a COM32/COM32R module
boot/syslinux/reboot.c32 : not a COM32/COM32R module
boot/syslinux/rosh.c32 : not a COM32/COM32R module
boot/syslinux/sanboot.c32 : not a COM32/COM32R module
boot/syslinux/sdi.c32 : not a COM32/COM32R module
boot/syslinux/sysdump.c32 : not a COM32/COM32R module
boot/syslinux/vesainfo.c32 : not a COM32/COM32R module
boot/syslinux/vesamenu.c32 : not a COM32/COM32R module
boot/syslinux/vpdtest.c32 : not a COM32/COM32R module
boot/syslinux/whichsys.c32 : not a COM32/COM32R module
boot/syslinux/zzjson.c32 : not a COM32/COM32R module
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown GPT Partiton Type
e7afbfbf4fa38a449a5b6213eb736c22
========= Devices which don't seem to have a corresponding hard drive: =========
sdb
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
/dev/cdrom: open failed: No medium found
/dev/sdb: open failed: No medium found
No volume groups found
mdadm: No arrays found in config file or automatically
Any ideas?
Here's my grub.cfg:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
else
search --no-floppy --fs-uuid --set=root 16DC-8816
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by knowNothing23 (2013-12-30 00:17:02)

Hi,
New to this forum, joined today in anticipation of trying an install of AL...For whatever this may be worth:
I have an HP Pavillion desktop that came with Windows 8 (now 8.1), & has, of course, a UEFI boot system. I tried earlier to install Ubuntu Studio (which I currently run) on the same disk as Windows (/dev/sda), I made (I believe) a huge mistake in trying to install as LVM/ext4... wiped out my Windows install & made the UEFI unavailable... I had to do a complete re-install of Windows (fortunately, I did the recommended system backup, using 4 DVD's!) so then I tried a (non LVM) install on an external usb 3.0, with the Grub 2 on the external disk (great access time, & it worked fine... IMO)...
One other item: as I have been trying to find the right flavor of Linux for my main purposes, I have been trying various distros. & having to try to learn to negotiate the UEFI, secure/legacy procedures (still learning)... As I was unsure of installing rEFind... I did down load the .iso, burn it to a CD...
http://www.rodsbooks.com/refind/getting.html
& in legacy mode, found that simply putting it (rEFind CD into the CD/DVD player, which in the UEFI it is labeled something like HP/UEFI CD/DVD), & then launching it, rEFind worked for some other distros...that is, I was able to boot into my Linux distros, even bypassing Grub), as well as having the option of booting Windows. It may seem trivial that I say this (it maybe is), but I have not seen anywhere (I have scoured the internet rather well) this mentioned as a possibility (though it, of course, would not make such a good permanent solution, especially for computers like mine that have only one CD/DVD player).
HenryP

Windows XP SP2 and Solaris 10 x86- Dual Boot, Single Hard Drive

I recently decided to look into installing the newly available Solaris version capable of running on my personal x86 Intel workstation (Solaris 10). There were quite a few hurdles, however, in getting the system to install, detect devices and associate drivers with compatible hardware. Here�s the process I went through to get my system configured to run both operating systems on a single hard drive:
(Note- This is something of a layman�s guide. I apologize if there are any errors. I didn�t see anything similar on the boards, and felt obligated to contribute. I highly encourage posting corrections.)
Read more: http://ryanhornbeck.com/content/view/85/2/

Here are a few reference websites that helped me along the way:
http://multiboot.solaris-x86.org/v/1.html
http://www.linuxquestions.org/questions/archive/20/2005/04/3/279197
http://www.sun.drydog.com/faq/
http://www.cs.uu.nl/wais/html/na-dir/Solaris2/x86/FAQ.html
http://www.experts-exchange.com/Operating_Systems/Solaris/Q_21244455.html
Hope they help.
Ryan

YOGA 2 - 1051F Windows 8.1 Dual boot Android

Hello,
I have a YOGA 2 Tablet 1051-F under Windows 8.1 and I want to install Android in dual boot mode.
I made an USB stick bootable with Android IMG but the tablet don't want to boot on it. I checked the UEFI and Secure is OFF --> no succes.
I also download on this site the UEFI Tools & Diagnostic, I can see it in the BIOS option but when I want to but on it, nothing append.
Any idea to help me ?
Many thanks

Salut Misterwood .
a tu trouvé quelque chose ?

Arch linux through vmware in dual boot

Hi guys,
I've reinstalled arch again on a fake (intel) raid system with dual boot with Windows 7. Right now arch runs just fine natively on the machine, but I want to set it up so I can run it from vmware in windows as well. I have most things figured out but I have a small problem which I have yet to tackle.
Natively the disks are mapped through dmraid in the following manner (etc/fstab):
/dev/mapper/isw_cidbgaibjd_Systemp3 /boot ext2 defaults 0 1
/dev/mapper/isw_cidbgaibjd_Systemp5 swap swap defaults 0 0
/dev/mapper/isw_cidbgaibjd_Systemp6 / ext4 defaults 0 1
/dev/mapper/isw_cidbgaibjd_Systemp2 /mnt/Win7 ntfs-3g defaults 0 0
/dev/mapper/isw_cidbgaibjd_Datap1 /mnt/Data ntfs-3g defaults 0 0
To access from vmware in Win7 I have set up vmware to map the physical (raid) drive where the arch partitions are for the virtual machine. The difference is that in Win7 the raid drive /dev/mapper/isw_cidbgaibjd_System is seen as /dev/sda (vmware abstracts the raid drive as a regular scsi/sata drive).
I've used mkinitcpio to generate a separate profile "kernel26-vmware" to load different hooks to boot arch linux in a virtual machine and create a separate runlevel (runlevel 7) to load different daemons at boot and added a new entry in grub to load the kernel26-vmware mkinitcpio image and go into runlevel 7. The only problem remaining is to switch out /etc/fstab so that it loads proper device paths to the raid drive partitions e.g.:
/dev/sda3 /boot ext2 defaults 0 1
/dev/sda5 swap swap defaults 0 0
/dev/sda6 / ext4 defaults 0 1
/dev/sda2 /mnt/Win7 ntfs-3g defaults 0 0
/dev/sdb1 /mnt/Data ntfs-3g defaults 0 0
So the question is, is there anyway to tell mkinitcpio to rewrite fstab at boot with what I want depending on if I'm booting arch natively through dual boot, or booting from vmware in Win7? I've seen that mkinitcpio has "FILES" directive which enables it to load additional custom files. Can this be used to load two separate fstabs and a small script that will ovewrite /etc/fstab on boot?
Last edited by digivampire (2009-09-24 17:32:48)

Nevermind, I figured out the solution. Since UUIDs are preserved on the filesystem, setting fstab to use /dev/disk/by-uuid... works when booting both native and from vmware.

[SOLVED] dual booting windows 7 with btrfs on grub-bios -- core.img

I am trying to install arch in a dual boot configuration with an existing windows 7 partition. I have everything from the beginner's guide done but the bootloader. When I run grub-install it tells me that core.img is too big.
Some googling tells me that this is relatively common with btrfs, and it seems the only work around is to switch to gpt mode and use a grub bios partition. But the info I've seen indicates that I need to use MBR mode to dual boot windows.
Is it safe to do this with windows? Is there another workaround? Or will I have to settle for ext4?
Last edited by jorenko (2013-06-09 03:53:24)

Well there's your problem, your first partition starts at sector 63. With recent versions of windows and fdisk (and every other partitioning tool I can think of off the top of my head) things now align themselves correctly. Also because there is now GPT, the first partition typically starts later as the GPT partition table will typically sit between the MBR and the first partition.
On a MBR partitioned system, grub2 will actually use the first 446 bytes like normal, but will then also use the space that is empty where GPT would sit. This is why when you have a GPT partitioned system, it will require you to create a 1-2MB grub boot partition, as it needs somewhere else to put its bloat. GPT actually still uses the MBR section, but simply creates one large partition covering the whole disk. This is so that tools that are not GPT aware will not think that they have a whole free disk to use as they please.
For comparison, here is whe I get from fdisk:
# fdisk -l /dev/sda
sudo fdisk -l /dev/sda
[sudo] password for curtisshima:
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
Disk /dev/sda: 250.1 GB, 250059350016 bytes, 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
# Start End Size Type Name
1 2048 2099199 1G EFI System EFI System
2 2099200 252166798 119.2G Linux filesyste arch-btrfs-1
3 252168192 488397134 112.7G Linux filesyste arch-btrfs-3
Note that I do use GPT. But that is not the point here. What I am trying to show is where my first partition starts. This is also where fdisk will start partitions these days. This is to ensure compatibility with 4k advanced format disks.
If you are not dead set on Grub2, you could try using syslinux. I really like it much better, though if you are booting more than one Linux, you need to either employ chainloading to various partition boot records, or have a shared /boot. Having a windows partition doens't really matter, as you are simply chainloading to that funky reserved partition anyway.
The other option is to use grub-legacy, which can still be found in the AUR. I actually liked the orginal Grub, as it provided a nice feature set, but was still configurable by hand and it actually fit into the MBR.

Dual boot (Win XP - ARCH 0.8) / disk 80 GByte

Hi,
I am trying to setup DUAL Boot Windows-XP Archlinux on a Compaq nc6320
I want to load linux from the Window NT loader I have only a " - " in the left uppercorner when I select --linux--
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
c:\boot.lnx="-- Linux--"
Although the boot.lnx is not a text file I could read .... è*·ëþGRUB ·Geom·Hard Disk·Read· Error·»·´Í¬<·uôÃ···········
I have a disk of 80 byte
Sda1 NTFS Windows XP 40Gb
Sda3 7 Mb Grub Bootmanager installed here (this was a unused space here)
Sda2
Sda5 NTFS, about 26 Gbyte
Sda6 /boot 130 Mb
Sda7 swap 1024 Mb
Sda8 / 9,7 Gb > Arclinux 0.8
I made the file boot.lnx this way
dd if=/dev/sda3 of=boor.lnx bs=512 count=1
Possible I have problems with the Cylindrer 1024 border ?
Due to company base policy I would like to avoid changing MBR and first ntfs partiton.
Any idea what oher solutions there are ? Thanks.
I id not found LBA support in bios setup.
http://www.geocities.com/epark/linux/gr … HOWTO.html
Last edited by go4it (2007-01-29 15:29:33)

Whenever I've put linux on the same disk as windows I've always used lilo to handle the booting by installing the linux bootloader to the "/root" of the linux partition, before that I would flag the partition as bootable with cfdisk while I was doing my partitioning and untoggle the boot flag for windows, this was also reversible so it never harmed my windows bootloader.
I would make an entry like this if I was using lilo:
# Partition 3: Windows XP Home
other = /dev/hda1
label = WinXP
and then run lilo for the change to stick.
In grub I would imagine you would have to add something like this:
title WindowsXP
rootnoverify (hd0,0)
chainloader +1
makeactive
I now just keep linux on its own seperate drive, to give you an idea how that works this is what my grub looked like last week, I repartitioned and only have arch on there now, so far..... , keep in mind my windows is actually on my second drive, hence the need for the "map" entries, reading up a bit on grub would be to your advantage, its hdd naming scheme is a bit confusing at first, but once ya get the hang of it you realise how powerful and usefull it can be, I love the password and fallback features.
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,1)
# kernel /boot/kernel-genkernelreal_root=/dev/sda2
# initrd /boot/initramfs-genkernel
#boot=/dev/sda2
default=0
timeout=120
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
password --md5 XXXXXXXXXXXXXXXXXXXXXXXXXXX
title Sabayon Linux x86 3.25
root (hd0,1)
kernel /boot/kernel-genkernel-x86-2.6.19-gentoo-r4 root=/dev/ram0 ramdisk=8192 real_root=/dev/sda2 quiet init=/linuxrc splash=silent,theme:sabayon CONSOLE=/dev/tty1 pci=nomsi vga=0x31b
initrd /boot/initramfs-genkernel-x86-2.6.19-gentoo-r4
title Windows XP Professional
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
makeactive
title VectorLinux 5.8 Std Gold
root (hd0,2)
kernel /boot/vmlinuz root=/dev/sda3 ro vga=795
title Arch Linux Voodoo
root (hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5 ro vga=795
initrd /boot/kernel26.img
Last edited by RabidWolf (2007-01-31 12:32:39)

Dual-booting with Windows 8, Arch Linux first?

I initially had Windows 7, then Arch. Now, I have a key for Windows 8. I can just upgrade the previous Windows 7 partition, but I only allocated 37 GB originally, so I want to expand it - I would therefore need to delete the partition and make a new one. However, dual-booting guides say that Windows should be first. What is the best way to go about this?

srs5694 wrote:
x33a wrote:Thanks, that's interesting. I always thought that it didn't run without secure boot.
Note that Secure Boot is NOT synonymous with EFI. Secure Boot is one optional feature of EFI. In fact, of five computers I've got that use EFI, only one supports Secure Boot.
I did know that
Microsoft requires manufacturers to ship their computers with Secure Boot enabled in order to get a Windows 8-compatible sticker. Because most manufacturers consider the lack of such a sticker to be the kiss of death for their products, this means that nearly all computers that ship with Windows 8 ship with Secure Boot enabled. Because Secure Boot is an EFI feature, this means that these computers also use EFI.
This does not mean that Windows 8 itself requires either EFI or Secure Boot; the requirement is a marketing requirement for new computers. If you buy a Windows 8 package at the store, it will install on an older BIOS-only computer (assuming it's not too old), on an EFI computer that lacks Secure Boot support, on an EFI computer with Secure Boot support but with that feature disabled, or on an EFI computer with Secure Boot and Microsoft's keys enabled. (It is possible to replace your firmware's Secure Boot keys, which would prevent the installation of Windows unless you re-signed the Windows boot loader yourself.)
Note also that it's possible to switch Secure Boot on and off, at least on x86-64 systems. (Microsoft's Windows 8 sticker requirements specify that users must be able to do this on x86-64 systems; but on ARM computers, Microsoft's sticker requirements say that users must not be able to disable Secure Boot.) Windows 8 should continue to boot when you turn Secure Boot on or off; however, some versions of GRUB have problems chainloading to other EFI boot loaders (including the Windows boot loader) when Secure Boot is enabled.
Thanks, that's very informative.

Dual-Booting Windows and Android on Yoga Tablet 2 13?

So I am a big fan of the lenovo yoga tablet so I started looking into the new versions of the tablet and I came upon something curious. both the yoga tablet 2 pro and the yoga tablet 2 13 (windows) have the same processor (a 64-bit processor) as well as very similar technical specs(the main difference being the windows edition has 4GB of ram instead of 2GB and a larger battery no doubt due to the removal of the integrted pico projector). as well Lenovo has the source code for the android build in the pro available on the website.
So my question is if both are running off the same 64-bit processor is there anything stopping someone from compiling the yoga 2 pro source code and installing the yoga 2 pro android OS onto the Windows version of the tablet (dual-booting both) aside from secure boot needing to be disabled?
after scouring the internet and asking a few lenovo representatives I have found absolutely no information on this (the lenovo reps I spoke to couldn't even confirm the specs of the processors but I found that data from the intel ark database) and it is something I really would like to do if possible (especially with android 5.0 having x86 support integrated in the vanila build)
So anyone have any information on anyone trying this or something similar being attempted?

so, lenovo putted a really bad bios on thoses tablets.
http://forums.lenovo.com/t5/Windows-based-Tablets/Alternatives-OSes-and-CMS-under-Yoga-1051/td-p/190...
To make it short, the uefi bios used on yoga tablets support only x86 so, the x86-64 instruction set can't be used, on windows. Without CSM (compatibility support module) you can't even try to boot some oses. For linux you need to mod it, i'll try later but, i can't build a new bios and lenovo is not present on this board

[SOLVED] Dual Boot Window 7 & Arch on a Uefi system.

From the Wiki
Windows 7 x86_64 versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support IA32 (x86 32-bit) UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk.
I don't understand this. As stated in the title I have a ueif system so that means I have to create a GPT disk ? I already have a gpt disk which I confirmed by running Arch Live USB. Under type it said GPT. I don't understand this at all
However if Arch is installed in BIOS-GPT in one disk and Windows is installed in BIOS-MBR mode in another disk, then the BIOS bootloader used by Arch CAN boot the Windows in the other disk, if the bootloader itself has the ability to chainload from another disk.
Note: If Arch and Windows are dual-booting from same disk, then Arch SHOULD follow the same firmware boot mode and partitioning combination used by the installed Windows in the disk.
In the Note above it says both Arch and Windows follow the same boot mode if they are dual booting from same disk. I DO NOT want to do this. I have already decided to partition my drive with 200 Gb going to Windows and 500 Gb going to Arch. Does this mean that I should install both in different modes i.e. Arch in Bios-GPT and Windows in Bios-MBR.
The recommended way to setup a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create additional partitions for Linux while leaving the existing Windows partitions untouched.
UEFI systems
Both Gummiboot and rEFInd autodetect Windows Boot Manager \EFI\Microsoft\Boot\bootmgfw.efi and show it in their boot menu, so there is no manual config required.
For GRUB(2) follow GRUB#Windows_Installed_in_UEFI-GPT_Mode_menu_entry.
Syslinux (as of version 6.02 and 6.03-pre9) and ELILO do not support chainloading other EFI applications, so they cannot be used to chainload \EFI\Microsoft\Boot\bootmgfw.efi .
Computers that come with newer versions of Windows often have secure boot enabled. You will need to take extra steps to either disable secure boot or to make your installation media compatible with secure boot.
Being a beginner should I go with Gummiboot then. GRUB made a mess last time.
Also my secure boot is NOT enabled so is that good.
I have read the FAQs, Beginner's guide, Installation Guide, Dual Boot wiki entry but I just don't understand the above concepts. But it looks this this is the main thing in dual booting. Almost everything else is doable but this I have to get right on account of what happened the last time I installed Arch without getting the above right.
Last edited by Some Arch Lovin (2014-06-14 08:53:14)

A few issues with the dual boot setup
Hello again, I lost my dual factor authentication grid from lastpass. Opensuse was acutally overwriting new pdf files over my old pdf files so now that grid pdf is actually an Arch cheat cheet with the name last_pass_grid.pdf. And the gmail account I used to register to Arch forums is also in last pass.
This is why I created another account. I am some arch lovin.
The installation went smoothly but I could not dual boot Windows7 with Arch because my Win7 image is not UEFI bootable so had to dual boot win8(not a fan at all) and arch.
Almost everything is working correctly. I have a few issues that aren't affecting how the system is working but they still need sorting out.
I'll do them one at a time but I want to know from the admins if I should start a new thread? Because in a way this thread accomplished it job i.e. win7 and arch dual booting in uefi system.
If the answer is yes I should create a new thread depending upon the issue then I will do that but in case its a no since I have only 2-3 problems I am going to ask help for the first one.
My gummiboot is not working on startup. I have to press f12 and use bios booting menu to boot. The problem with that is if I put Windows at the top of the boot priority the bios does not show F12 and F2 at the time of booting up so I can't access the boot menu. I have to boot into Windows and crash it by holding the power button and then the F12 options shows up and I am able to boot into Arch. If I put Arch at the top then Windows keeps restoring back to an earlier version due to start up options.
NOTE : I can't be sure but one it did work(only once). I checked the images online to compare with what I saw and its very similar. An all black screen with three bootloading options
Windows
Arch
Opensuse(don't know why I created a completely new GPT partition table)
This is what I did while installing Gummiboot
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
# pacman -S gummiboot
# gummiboot install
I tried going through the gummiboot to see if I can do something but it very difficult to comprehend as a beginner. All I get is the characters gummiboot understands but thats all.
Last edited by Archer61 (2014-06-11 13:48:56)

Stream 7, dual boot, windows and android

Given that the HP Stream 7 can be equipped with lots of storage, why not dual boot it with Window and Andoid so I can have the best of both worlds
can this tablet be configured to do that?

Before going to a lot of trouble, I'd get a boot disk on USB with Android X86 on it. Then boot off the USB.
I'd also suggest using 4.22 or 4.4, not 5.0. "Everyone" is still working on 5.0.x.
I've not had much luck on a few devices and Android x86 - hence my suggestion. I have NOT tried it on the Stream 7

Dual boot Windows 7 (64) and Arch Linux (64) problems

Hello:
I am new to Arch Linux and just finished installing the 64bit on my laptop. It had a prebuilt Windows 7 (64) installed which I kept but split the hdd from 160Gb to 80Gb and 80Gb. I installed Arch there and set 4 partitions, all of them as Logical - a 64 MB ext2 /boot partition; a 512 MB swap partition; a 15 GB root partition; and the rest as my /home partition. My partitions look like this:
Disk Drive: /dev/sda
Size: 160041885696 bytes, 160.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 19457
Name Flags Part Type FS Type [Label] Size (MB)
sda1 Primary Unknown (27) 12889.02
sda2 Boot Primary NTFS 106.93
sda3 Primary NTFS [] 73915.11*
sda5 Logical Linux ext2 65.81*
sda6 Logical Linux 509.97*
sda7 Logical Linux ext2 15002.92*
sda8 Logical Linux ext2 57549.55*
The install was succesful(this was running from the core install cd) and I installed GRUB to my /boot but when I restarted it loaded Windows 7. I have used Knoppix USB disc to boot and see my Arch Linux install files and edited the /boot/gur/menu.lst file.
In Windows I installed EasyBCD 1.7.2 and tried to get NeoGrub bootloader working as a dual boot. I tried getting rid of the boot flag for Windows with cfdisk and setting it to my (Logical) sda5. That did not work. So far the only way I have booted into my Arch Linux install has been by going to the Live CD, choosing "Boot from Existing Linux Install" and editing the command files there.
root (hd0,4)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img
My goal is to get a dual boot working for Windows 7 and Arch Linux 64 and continue installing the Xorg and KDE to Arch. I just don't know what the problem is here. I don't mind reinstalling Arch if something went wrong, but I would like to keep my Windows running in order and add Arch on.
Any help would be greatly appreciated.

I ran the LiveCD and chose "Install to MBR hd0". I ended up with this:
setup hd(0,1)
Checking if "/boot/grub/stage1" exists.....yes
Checking if "/boot/grub/iso9660_stage1_5" exists.....yes
Running "embed /boot/grub/iso9660_stage1_5 (hd0,1)".....failed(this is not fatal)
Running "embed /boot/grub/iso9660_stage1_5 (hd16)".....failed(this is not fatal)
Running "install /boot/grub/stage1 d (hd0,1) /boot/grub/stage2 p (hd0,1) boot/grub/menu.lst".....failed
Error 31: File is not sector aligned
My entry for Windows into the menu.lst looks like this:
# (0) Arch Linux x64
title Arch Linux x64
root (hd0,4)
kernel /vmlinuz26 root=/dev/disk/by-uuid/3841273c-d91e-41d6-9dbf-716a15d03a01 ro
initrd /kernel26.img
# (1) Arch Linux x64
title Arch Linux x64 Fallback
root (hd0,4)
kernel /vmlinuz26 root=/dev/disk/by-uuid/3841273c-d91e-41d6-9dbf-716a15d03a01 ro
initrd /kernel26-fallback.img
# (2) Windows 7
title Windows 7
rootnoverify (hd0,0)
makeactive
chainloader +1

[SOLVED] Advice for Arch install with rEFInd dual boot Lenovo laptop?

I am trying to plan an Arch install on a new laptop for dual boot with Windows 8.1, but I know there is a potential to cause huge problems so I have been trying to read and learn about the hard disk partition structure and how I might install the rEFInd boot files so that I am still able to boot Windows once Arch is installed. (Unfortunately for some tasks such as updating the maps on my satnav box Windows is essential). However I am really quite unsure if I am doing the right thing in the way I am thinking about the Arch install so I would appreciate any help from experts on the forum.
The laptop is a Lenovo IdeaPad Y510p which came with Windows 8 pre-installed, with the option to upgrade to Windows 8.1. The upgrade was completed without issue and I then looked into the question of hard drive partitions and boot. I had read posts on the Ubuntu forums about users who had installed Ubuntu on this same laptop and ended up being unable to boot Windows afterwards so I wanted to tread very carefully before executing anything which might cause really major damage. I had also read on the Lenovo forums replies about people who had replaced the hard drive and installed linux only to find that they could not boot to the recovery partitions, with replies from Lenovo moderators saying that if the partition structure had been changed then the laptop would have to be sent back to Lenovo for a factory repair.
On this laptop to get into the bios or boot options you do not just press the power button and hit an F key, but instead there is a special small "OneKey Recovery" button next to the power jack, which opens up with options for BIOS setup and boot options as well as normal boot or recovery. This OneKey Recovery button is therefore needed to boot a usbkey - the power button only allows it to boot to windows presumably until/unless a different bootloader and NVRAM entry is amended.
I have done all the initial ( safe!)changes necessary to move to the point at which I can execute the Arch install. From within Windows (switched off fastboot, and shrunk the "C:" drive to make space for linux partitions). I have also switched off Secure Boot from the BIOS, and made sure that Windows still boots up fine.
The current arch install iso (February 2014) boots under uefi just fine - and of course once booted I have access to the gdisk programme. That certainly showed the pre-existing partitions on the drive (8 partitions with partition number 2 being the EFI partition, and three recovery partitions!) with a GPT partition table, and it should therefore be possible to make the necessary new linux partitions in the now unallocated space on the disk that was freed up with the internal disk management facility within Windows 8.1. So at that point I created three partitions for a root partition (type 8300), a swap partition (type 8200) and another type 8300 partition which will become /opt in the installed Arch system.
In order to try and not make any changes to the partition structure I let the three new linux partitions be number 9, 10 and 11.
I am told that for a GPT disk it is a definite no-no to try to create more than one EFI partition. So I will need to use the existing EFI partition to place the rEFInd files and the kernel once I install Arch.
In this (Y510p) laptop the EFI partition contains the following structure:
BOOT/ - containing only boot.sdi
BOOTSECT.BAK
EFI/ which contains two directories Boot/ and Microsoft/
so EFI/Boot/ contains only Boot64.efi which is likely a fallback copy of the Windows 8.1 bootloader
and EFI/Microsoft/ contains a Boot/ directory - so
EFI/Microsoft/Boot/ contains loads of language specific directories like en-GB/
plus bootmgfw.efi (which I believe is the Windows main efi loader file)
bootmgr.efi
memtest.efi
The scheme that I am planning to use which I have previously used in pure Arch uefi machines, is that /boot is a directory in the root partition, /. That way /boot is an ext4 directory and will contain the kernel and initramfs plus the rEFInd linux config file.
Then I can mount the EFI (vfat) partition as /boot/efi and so I can then make a /boot partition under /. Then the EFI /BOOT/ directory would be seen in Linux as /boot/efi/BOOT/ and the Windows efi stuff would be in /boot/efi/EFI/Boot/Microsoft/Boot/ in which case I would presume that I have to make a new directory in /boot/efi/EFI/refind/ and put the refind stuff including the filesystem drivers there, and let the kernel go into the (ext4) /boot/ directory which would be preferred! However I am not 100% confident that this is what will work and I need to read more before trying to do the install. The thing that concerns me is how the system will handle the uefi boot process, and whether it would auto-detect the Windows efi file as well as the Arch refind efi file once the system has started up?
... and then there is the issue of the NVRAM entries and I am no longer confident that if I use the usual tools to create an entry (efiboomgr or bcfg), that I will get a successful dual boot system!
There is still a chance that I would irrevocably damage being able to boot to the Windows and Recovery partition boot options by messing up the EFI and/or the NVRAM so I have to tread very very carefully with this.
If anyone has gone through this kind of dual boot install with a Windows 8 or 8.1 machine using rEFInd for the bootloader, and can offer advice or help here I would very much appreciate it. I have another pure Arch system which uses rEFInd that works extremely well, but it seems that dual boot with uefi is a rather more complex animal than a pure linux system!
Last edited by mcloaked (2014-02-22 10:06:03)

vipin wrote:I have recently bought the y510p , im planning to install Arch , this is my 4th laptop , i had installed Arch in all the other 3 with no problems, but im a bit worried with the installation as this is the first laptop which has EFI , im a linux user for the past 6 years , i started with fedora , now i like Arch , mike documentation is excellent, i just had one question when i had grub , it automatically finds the new kernel when i update (grub.conf/menu.lst gets updated), does rEFInd also do that.
When there is an update to the rEFInd package you need to copy the files across to your ESP from the files contained in /usr/share/refind/ usually you need to copy the refind_x64.efi binary as well as the icons, fonts, and drivers directories. Since there is flexibility in how you configure the kernel and initrd files in terms of where they are located whether you need to do anything else when a new kernel update arrives depends on how you set your system up. If you have the /boot directory as your ESP partition which will then have the kernel and initrd files updated by default then there no need to do anything else when there is a kernel update. If the ESP is then at /boot/EFI and within that is your refind/ directory then that is where the replacement files go if refind-efi gets a pacman update. So it is actually fairly straight forward. If you configure rEFInd to look for kernels in some other directory than /boot/ then you may need to copy the files there after a kernel update but there is more information in the arch wiki about this.
During a refind-efi package update there are helpful files in the pacman output (and log) reminding you of what you need to do. eg for the latest refind-efi update you get:
[2014-06-18 18:48] [PACMAN] upgraded radvd (1.12-1 -> 1.13-1)
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd UEFI application has been installed at /usr/share/refind/refind_*.efi
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] Other UEFI applications have been installed at /usr/share/refind/tools_*/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] UEFI drivers have been installed at /usr/share/refind/drivers_*/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] Copy the efi application (according to your UEFI ARCH)
[2014-06-18 18:48] [ALPM-SCRIPTLET] and /usr/share/refind/refind.conf-sample to a sub-directory of <EFISYS>/EFI/
[2014-06-18 18:48] [ALPM-SCRIPTLET] as refind.conf and add an entry to firmware boot menu using efibootmgr
[2014-06-18 18:48] [ALPM-SCRIPTLET] or mactel-boot (for Macs)
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd Icons have been installed at /usr/share/refind/icons/
[2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd Fonts have been installed at /usr/share/refind/fonts/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] HTML Documentation is available at /usr/share/refind/docs/html/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] More info: [url]https://wiki.archlinux.org/index.php/UEFI_Bootloaders#Using_rEFInd[/url]
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [PACMAN] upgraded refind-efi (0.8.1-1 -> 0.8.2-1)
I hope that helps.
By the way you can also boot uefi using grub and in fact you can get rEFInd to chainload grub as a backup bootloader as an added safety factor and have both rEFInd as well as grub installed simultaneously. How that can be done is explained in the thread at https://bbs.archlinux.org/viewtopic.php?id=181906
Last edited by mcloaked (2014-06-25 17:41:12)

How to dual boot with Windows 8.1 and Arch?

Hello everyone,
I've been looking into using Linux as my daily driver since having some experience with it on a server. After some digging around, I think Arch Linux is the best distro for me, now onto where I am.
I'm currently running Windows 8.1 (updated from Windows 8, which updated from Windows 7) on a Dell Inspiron 15R SE laptop, I want to dual boot Arch Linux with it. I've looked at the wiki and I'm still not entirely sure what to do.
Can anyone give me a quick list of steps of what to do to dual boot this? I've dual booted Ubuntu in the past and it was really simple because an installer did it all.
Thanks, Expi.

stqn wrote:
Expi1 wrote:Thanks, I'm mostly struggling with how to partition for Arch and then how to do the bootloader. I'm using Win8 64-bit and from what I understand a Legacy BIOS bootloader. I'm not entirely sure what I should be partitioning the C: into, I've done partitions before, just not for Arch and then I'm not sure whether to use GRUB or syslinux, or if I even need those. Or if I need to use GPT or MBR?
Your disk is already partitionned so you don’t have to choose between GPT or MBR, the choice is already made.
You don’t partition “C:”, that is the name of a Windows partition. You partition a drive.
Grub or syslinux, use whatever the beginners guide tells you to. Personally I think syslinux is simpler which is why I’m using it (but I’m not dual-booting, if that matters).
You’re not saying what your problem is with partitionning, so it’s hard to help.
Thanks for getting back to me, I'm not sure if I just create one large partition for Archlinux or if I have to create multiple? Where I'm also confused is with the Creating Filesystems part of the guide. I don't understand how I'd do this in Windows, or what /dev/sda1 is referring to.
As for the bootloader part, the Beginner's Guide gives you a choice between syslinux and grub, what I'm not sure about is which to use considering I'm dualbooting. How it will affect my windows bootloader, do I disregard that and use GRUB now? I'm unclear on how that works.
I'm also aware I need to disable Secure Boot, I just searched my BIOS options and couldn't find anything remotely relating to that, so I'm assuming it's not an issue since this computer was originally on Windows 7 anyway?
Thanks again, Expi.
Last edited by Expi1 (2014-03-06 19:54:30)

Arch & Android-x86 Dual Boot ?

Similar Messages

Maybe you are looking for