I don't know why the beta-6 boots and beta-7 not. On VirtualBox you told me it works for your. From the grub on the install media, we didn't changed on how we display it. Only the kernel changed to support the autohide menu as needed.
thanks for your reply. Am I right that I need a installation on hd in order to perform those steps?
I tried to boot both the beta-6 and the beta-7 from a live usb stick, whereas in virtualbox I created a new vm and booted from the beta-7-iso directly. So maybe I can't see the boot menu because the beta-7 is the only os on the live usb stick an it is booting quietly?
Ah, now we get you. We always thought the install media you had copied via dd to the USB-Stick doesn't boot-up to install Manjaro. However, you use the OS from the stick. That is a complete different story.
You've still got the normal "grub" for that. So either replace "grub-quiet" with normal grub, or edit grub conf and change "GRUB_TIMEOUT" to your liking and optionally comment out "GRUB_HIDDEN_TIMEOUT" and "GRUB_HIDDEN_TIMEOUT_QUIET".
No, we added new features to grub-quiet. On this we worked with Fedora together.
On systems with only a single OS installed, the grub menu's only function is to allow booting older kernels, which is only necessary as a rescue option in case of a severe kernel bug and as such not something which is directly useful for normal use.
Manjaro already has a lot of work done to not show too technical boot messages to end users during bootup, e.g. we pass quiet to the kernel and we had plymouth to show a bootsplash instead of a bunch of "Starting service-foo: OK" messages.
The grub menu with its kernel versions is another example of showing too technical info to end-users and on non multi-boot systems it normally is not necessary, so it is better to hide it.
This change will add menu-auto-hide functionality to grub, which when enabled will hide the menu if:
The machine only has a single OS installed; and
The previous boot has set a flag to indicate it successfully booted
To make the menu easier to reach when hidden this change will also extend how the menu can be unhidden. Currently to show the menu when hidden the user needs to press ESC during boot. There are 3 problems with this
It is not easily discoverable
Timing the ESC key press right may be hard
ESC makes the machine enter its firmware/BIOS setup screen on some machines (especially with the #bladebook)
So we added 2 new unhide methods to address these problems:
Press F8 to unhide the menu (F8 has been the key to show the Windows boot menu for many older Windows versions)
Keep SHIFT pressed during boot, this fixes the timing problem and this is what Ubuntu does
This new auto-hide functionality will be automatically enabled on new Manjaro 18.0 installs. This can be disabled by running:
sudo grub-editenv - unset menu_auto_hide
You can also show the menu once for 60 seconds on next boot:
I don't mind verbose boots myself, I'm actually kind of fond of them, but you guys had done a wonderful job with this TBH. Specially for the "mainstream" usergroup. And contributing with Fedora guys to the "bleeding edge" side of Linux is super cool in my mind. Keep up the great work.
Tested the new autohiding method on a new installation. For me, it hides the menu even when there are 2 manjaro installations on the machine. It seems multiple manjaros doesn't count as multi boot? Holding shift does not work, beating F8 does, so it is good that there are multiple options.
If we disable fsck by default, shouldn't we enable the corresponding systemd service to compensate?
As the release is approaching I cannot but share an info about a minor bug affecting Elan Touchpads: a HUGE number of the following messages spamming dmesg output as soon as touchpad is used: [ 362.702654] i2c_hid i2c-ETD2303:00: i2c_hid_get_input: incomplete report (14/65535)
I've searched for a solution here and there, and according to what I've found this is a kernel-related problem. This is not a serious issue but it results in logs consuming much space on a drive.
I have this issue since I installed Manjaro in the end of December, 2017, and I am sure it affects every kernel version from 4.14 to 4.19.
PS: 18.0-beta7 boots just fine on my UEFI laptop.