...My main distro is Arch_gnome, and I created an Arch_enlightenment on a separate partition, because enlightenment is my second favorite desktop....
Just curious, why did you do it that way? There is no reason one cannot install several 'desktops' and choose the one you want at run time. You can even log in multiple times and use different environments with each log in.
]]>Google told me Error 13 comes after you choose from grub menu, which means something's wrong with the kernel line in Arch Enlightenments menu.lst.
]]>Hi,
As a workaround, why not boot the Arch Enlightenment kernel directly, just like you do with Arch itself? Why is a chainloader necessary?
These are two separate installs, on to separate partitions, not like one install with two desktop environments.
]]>from grub's web site:
13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).So you have an Arch install on hd0,0 and you created a new partition in order to install Arch with Enlightenment?
That is the case. My main distro is Arch_gnome, and I created an Arch_enlightenment on a separate partition, because enlightenment is my second favorite desktop. Arch_gnome grub installed in MBR end supposed to handle all the other installs. Chainloader +1 never failed me before. And it still boots ubuntu without problem.
]]>13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
So you have an Arch install on hd0,0 and you created a new partition in order to install Arch with Enlightenment?
]]>As a workaround, why not boot the Arch Enlightenment kernel directly, just like you do with Arch itself? Why is a chainloader necessary?
]]>What you might want to do to eliminate most possibilities is to chroot from an Arch live CD and run mkinitcpio:
mkinitcpio -p linux
Be sure your /etc/mkinitcpio.conf has the appropriate hooks for your system, otherwise you might have a working kernel but it won't boot (especially if you're using LVM and forget the LVM hook).
This may not be of much help, but it'll be a start to figure out what went wrong.
]]>I've just finished fixing the partition issue in the morning with much help from this forum community and now I have another one.
I've installed arch-enlightenment desktop on a separate partition and grub can't start the distro. I get
“Error 13, invalid or unsupported executable format” message.
This is all the more surprising because chainloader +1 never failed me before.
I have also Ubuntu installed and arch execute perfectly chainloader +1 with ubuntu – no problem, only arch can't start arch. Interesting.
Here is the menulist to make clearer what I mean.
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz-linux root=/dev/sda1 ro
initrd /boot/initramfs-linux.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /boot/vmlinuz-linux root=/dev/sda1 ro
initrd /boot/initramfs-linux-fallback.img
title Ubuntu
root (hd0,1)
chainloader +1
title Arch Enlightenment
root (hd0,2)
chainloader +1
Lots of people having this problem but my search found no usable solution to this problem. Now I have arch-enlightenment installed by I can't start it.
]]>