Arch Linux

I noticed that, too.
It's clearly not necessary,
I mean, how often is the architecture of your cpu changing?!?
On top of that, I couldn't see any difference in those entries.

Workaround, removing all pkg-linux* kernel entries:

chmod a-x /etc/grub.d/10_archlinux

There is still a x86_64-xen entry I cannot get rid of (even after `chmod a-x 20_linux_xen`) though, but at least I do not have over 40 entries (not kidding, there are three custom kernels here for testing purposes plus the stock kernel).

I also found that removing 10_archlinux can reduce the number of entries to two (x86 and x86_64-xen), while I am with an Arch 64
When I look into grub-mkconfig, "x86_64" is not in the iteration.

Though I do notice that when in actual boot, only one entry would be shown. The "testing mechanism" did work.

P.S. Is Arch not going to adopt the submenu thing? Sounds good if the fallback mode can be made an "advance option", if it can be done so.

This has nothing to do with the code in 10_archlinux . It is due to some upstream grub-mkconfig changes. See http://lists.gnu.org/archive/html/grub-devel/2013-12/msg00346.html for the related discussion. This change may be reverted by upstream before 2.02 stable release.

EDIT 1: You guys can try modified 10_archlinux I uploaded to grub-git AUR pkg maintained by me.

EDIT 2: Personally I suggest everyone to manually maintain their grub.cfg file. It is simply a scaled down shell script. See https://wiki.archlinux.org/index.php/UEFI#Using_GRUB and my grub.cfg (attached) for examples. Most of the perceived complexity of GRUB comes from the grub-mkconfig generated grub.cfg . Arch does not auto overwrite /boot/grub/grub.cfg file unlike other distros, so it is safe to manually maintain grub.cfg . Syslinux does not come with any built-in config generator (neither upstream nor any Arch specific script/tool) and that works perfectly well for users. I don't think that should not work for GRUB.

EDIT 3: Although I submitted the 10_archlinux script and checked the generated grub.cfg (separate /boot, so didn't catch the ${subdir} vs ${SUBDIR} issue discussed at https://bugs.archlinux.org/task/38223), I use my manually written grub.cfg since GRUB 2.00-beta1 release and it works perfectly well for me.

It is already fixed by upstream and included in 2.02-beta2. See: http://git.savannah.gnu.org/cgit/grub.git/commit/?id=faf4a65e1e1ce1d822d251c1e4b53d96ec7faec5

Updated 10_archlinux to work with grub 2.02-beta2 attached.

Should be fixed in 2.02-beta2, please confirm.

Fix confirmed for 1:2.02.beta2-1.

Still happening on grub 1:2.02.beta2-1 today on a fresh Arch install.

Please try 2.02.beta2-2 package from testing repository.

Still happening with 2.02.beta2-2

I get two normal entries from 10_archlinux (normal boot and fallback) and another two from 10_linux: "Arch Linux" and a submenu "Advanced options for Arch Linux" with "Arch Linux, with Linux linux".

do either
# chmod -x /etc/grub.d/10_linux
or
# chmod -x /etc/grub.d/10_archlinux

Please try latest grub from testing.