LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 03-22-2016, 05:02 PM   #1
FloppyMcDisk
LQ Newbie
 
Registered: Feb 2015
Distribution: Manjaro XFCE, Debian PPC, Android x86
Posts: 14

Rep: Reputation: Disabled
Question Dual-boot Manjaro & Android X86, GRUB not cooperating


I installed Android X86 4.4-r5 alongside Manjaro 15.12 but I can't seem to get the grub menu to link to Android x86. I tried simply entering "sudo update-grub" in the terminal but that did absolutely nothing. Then I followed some instructions from here

https://forum.manjaro.org/index.php?topic=30541.0

and I ended up with several duplicates of "Android" and "Android x86" on my grub menu but none of them work. It either tells me that the partition and or the kernel cannot be found. I tried using an ext2 and ext3 file system but had the same results with both. Does anyone have any suggestions they would like to share?

OS: Manjaro 15.12 XFCE

Kernel: 4.4.5-1

Hardware: Acer Aspire 5517
 
Old 03-22-2016, 05:46 PM   #2
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,317

Rep: Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057
Quote:
It either tells me that the partition and or the kernel cannot be found.
Post the menuentry(s) for Android from the Manjaro grub.cfg file. Which partition do you have Android on? Try the command below instead of update-grub, run as root:

Quote:
grub-mkconfig -o /boot/grub/grub.cfg
 
Old 03-22-2016, 09:37 PM   #3
FloppyMcDisk
LQ Newbie
 
Registered: Feb 2015
Distribution: Manjaro XFCE, Debian PPC, Android x86
Posts: 14

Original Poster
Rep: Reputation: Disabled
Here's the grub.cfg contents

#
# 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="${saved_entry}"
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
}

set menu_color_normal=light-gray/black
set menu_color_highlight=green/black

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
insmod png
background_image -m stretch /usr/share/grub/background.png
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-996cfe51-bdf3-47c0-91cb-2be3f0fb4606' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
echo 'Loading Linux 4.4.5-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.4-x86_64 root=UUID=996cfe51-bdf3-47c0-91cb-2be3f0fb4606 rw
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64.img
}
submenu 'Advanced options for Manjaro Linux' $menuentry_id_option 'gnulinux-advanced-996cfe51-bdf3-47c0-91cb-2be3f0fb4606' {
menuentry 'Manjaro Linux (Kernel: 4.4.5-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.5-1-MANJARO x64-advanced-996cfe51-bdf3-47c0-91cb-2be3f0fb4606' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
echo 'Loading Linux 4.4.5-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.4-x86_64 root=UUID=996cfe51-bdf3-47c0-91cb-2be3f0fb4606 rw
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64.img
}
menuentry 'Manjaro Linux (Kernel: 4.4.5-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.5-1-MANJARO x64-fallback-996cfe51-bdf3-47c0-91cb-2be3f0fb4606' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
echo 'Loading Linux 4.4.5-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.4-x86_64 root=UUID=996cfe51-bdf3-47c0-91cb-2be3f0fb4606 rw
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64-fallback.img
}
menuentry 'Manjaro Linux (Kernel: 4.1.19-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.1.19-1-MANJARO x64-advanced-996cfe51-bdf3-47c0-91cb-2be3f0fb4606' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
echo 'Loading Linux 4.1.19-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.1-x86_64 root=UUID=996cfe51-bdf3-47c0-91cb-2be3f0fb4606 rw
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.1-x86_64.img
}
menuentry 'Manjaro Linux (Kernel: 4.1.19-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.1.19-1-MANJARO x64-fallback-996cfe51-bdf3-47c0-91cb-2be3f0fb4606' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
else
search --no-floppy --fs-uuid --set=root 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
fi
echo 'Loading Linux 4.1.19-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.1-x86_64 root=UUID=996cfe51-bdf3-47c0-91cb-2be3f0fb4606 rw
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.1-x86_64-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 ###
### 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/40_custom.save ###
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry ‘Android KitKat 4.4′ {
set root=’hd0,msdos1’
linux /android-4.4-r5/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/android-4.4-r5
initrd /android-4.4-r5/initrd.img }
### END /etc/grub.d/40_custom.save ###

### BEGIN /etc/grub.d/40_custom.save.1 ###
# 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.
menuentry "Android-x86" {
set root='(hd0,0)'
linux /android-4.0-RC1/kernel quiet root=/dev/ram0 androidboot.hardware=eeepc acpi_sleep=s3_bios,s3_mode SRC=/android-.0-RC1 SDCARD=/data/sdcard.img
initrd /android-4.0-RC1/initrd.img}
### END /etc/grub.d/40_custom.save.1 ###

### BEGIN /etc/grub.d/40_custom.save.2 ###
# 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.
menuentry "Android-x86" {
set root='(hd0,1)'
linux /android-4.0-RC1/kernel quiet root=/dev/ram0 androidboot.hardware=generic_x86 acpi_sleep=s3_bios,s3_mode SRC=/android-4.0-RC1
initrd /android-4.0-RC1/initrd.img}
### END /etc/grub.d/40_custom.save.2 ###

### BEGIN /etc/grub.d/40_custom.save.3 ###
# 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.
menuentry "Android-x86" {
set root='(hd0,1)'
linux /android-4.0-RC1/kernel quiet root=/dev/ram0 androidboot.hardware=generic_x86 acpi_sleep=s3_bios,s3_mode SRC=/android-4.0-RC1
initrd /android-4.0-RC1/initrd.img}
### END /etc/grub.d/40_custom.save.3 ###

### BEGIN /etc/grub.d/40_custom.save.5 ###
# 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.
menuentry ‘Android KitKat 4.4′ {
set root=’hd0,msdos1’
linux /android-4.4-r5/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/android-4.4-r5
initrd /android-4.4-r5/initrd.img }
### END /etc/grub.d/40_custom.save.5 ###

### 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+ ###
if [ "${grub_platform}" == "pc" ]; then
menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
search --fs-uuid --no-floppy --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 996cfe51-bdf3-47c0-91cb-2be3f0fb4606
linux16 /boot/memtest86+/memtest.bin
}
fi
### END /etc/grub.d/60_memtest86+ ###


In addition, i've tried your suggestion. nothing different. however I've noticed this from trying to boot into android again. I think of instead of it simply not finding the kernel, for some reason it's mistaking it as Android 4.0 and is looking for the wrong kernel as you can see here. https://www.dropbox.com/s/y1w3avz8ey...DR%29.jpg?dl=0
 
Old 03-23-2016, 09:16 AM   #4
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,317

Rep: Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057
I've never used Android so I'm not sure what to expect. Your grub.cfg shows Manjaro installed on sda5 and Android installed on sda1. The grub.cfg entry for Manjaro below shows that the kernel (vmlinuz-4.4-x86_64) is in the /boot directory on sda5.

Quote:
linux /boot/vmlinuz-4.4-x86_64 root=UUID=996cfe51-bdf3-47c0-91cb-2be3f0fb4606 rw
The entry below shows the kernel for android which is apparently named 'kernel' is under a directory on sda1 named android-4.0-RC1. Boot Manjaro and mount sda1 and check that this is the case. You also have other different entries with "android-4.4-r5". Verify that android-4.0-RC1 is in the / (root) of sda1 and that there is a file named kernel in that directory. That is what the message is telling you in the image you posted, that file can't be found.

Quote:
linux /android-4.0-RC1/kernel quiet root=/dev/ram0 androidboot.hardware=eeepc acpi_sleep=s3_bios,s3_mode SRC=/android-.0-RC1 SDCARD=/data
 
Old 03-23-2016, 01:40 PM   #5
FloppyMcDisk
LQ Newbie
 
Registered: Feb 2015
Distribution: Manjaro XFCE, Debian PPC, Android x86
Posts: 14

Original Poster
Rep: Reputation: Disabled
Yes Android is in sda1. In addition I don't know how I missed it but apparently for some reason the file directory was "android-4.0-RC1/kernel" when it was suppose to be "android-4.4-r5/kernel" so I manually corrected each entry in grub.cfg to the correct directory. After I did this, I did manage to get past the grub menu but then it just hangs as the operating system is trying to boot kernel and I just get endless periods slowly going across the screen as you can see here.

https://www.dropbox.com/s/eop805eiyf...DR%29.jpg?dl=0
 
Old 03-23-2016, 02:45 PM   #6
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,317

Rep: Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057
The kernel in most distributions is named "vmlinuz". That is not necessarily the case as I have seen some kernels referred to as "linux" and possible others. I'd look for those, probably in the boot directory or the root of the filesystem. Do you actually have a file named "kernel" in the android-4.4-r5 directory?
 
Old 03-24-2016, 09:18 AM   #7
FloppyMcDisk
LQ Newbie
 
Registered: Feb 2015
Distribution: Manjaro XFCE, Debian PPC, Android x86
Posts: 14

Original Poster
Rep: Reputation: Disabled
Yes, there's literally a file called "kernel" in the android-4.4-r5 directory alongside the initrd.img, ramdisk.img, and folders entitled "system" and "data". I'm assuming that's the actual kernel because I searched through the entire file system on that partition for anything entitled "vmlinuz" or "linux" and found nothing.
 
Old 03-24-2016, 10:29 AM   #8
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,317

Rep: Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057Reputation: 2057
If your android is on sda1, the entry below should work. Check that it is exact, the name of the directory for android must be exact in grub.cfg. That is no upper case where it shows lower case and vice versa. It doesn't matter on the menuentry line, but the other lines need to be precise.

Quote:
menuentry ‘Android KitKat 4.4′ {
set root=’hd0,msdos1’
linux /android-4.4-r5/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/android-4.4-r5
initrd /android-4.4-r5/initrd.img }
 
Old 03-24-2016, 08:08 PM   #9
FloppyMcDisk
LQ Newbie
 
Registered: Feb 2015
Distribution: Manjaro XFCE, Debian PPC, Android x86
Posts: 14

Original Poster
Rep: Reputation: Disabled
I double on everything on gparted, the grub.cfg file, and file manager. Everything seems to be in order. I have no clue on what the problem could be. I did test a live session of Android from the SD card before I installed it to the hard drive and it booted up flawlessly. I don't understand what could possibly be causing the problem.

https://www.dropbox.com/s/x4fobk0r8l...0info.png?dl=0
 
Old 03-25-2016, 07:15 AM   #10
FloppyMcDisk
LQ Newbie
 
Registered: Feb 2015
Distribution: Manjaro XFCE, Debian PPC, Android x86
Posts: 14

Original Poster
Rep: Reputation: Disabled
Okay I found a "workaround" for this issue. I installed Android straight to an SD card just to see what would happen. Apparently when I boot from the SD card, Android's grub menu takes me directly to sda1 on my hard drive instead of the system on the SD card. It's rather odd but it works. Basically I just need to use my SD card as the boot disk.
 
  


Reply

Tags
android-x86, dual boot, dual-boot, grub, grub boot menu


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Dual-boot with Manjaro - no GUI canadensis Slackware 7 01-29-2016 06:35 PM
BIOS, UEFI & CSM Boot, GRUB and/or LILO and Windows/Linux Dual Boot rm_-rf_windows Linux - General 4 11-10-2014 08:30 AM
both dual boot win vista & linux enterprise 5 stop .see only grub>. grub.conf. is del fasika Linux - Enterprise 2 05-23-2012 08:39 AM
LXer: r 2012 How To Dual-Boot Android-x86 And Ubuntu (With GRUB 2) LXer Syndicated Linux News 0 03-05-2012 05:11 PM
help me to rescue my grub on x86 system with dual boot adityakumar Linux - Software 9 12-28-2006 07:01 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 07:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration