Is that really needed?
Sounds like clutter of the boot menu :\
Utilities like that are best run from floppy/USB/CD IMHO.

CC: (none) => zen25000

Yes, I think it's definitely needed. Of course, if I we want to run from removable media, we can (though note that many machines have no floppy nor CD, and that people don't necessarily have a spare USB key that they can remove the filesystem from). But if I actually went to the trouble of installing memtest86+ on my system, then it's probably a good inference that I want it to be able to run from disk :-)

Anyway, every other distro does this, Mageia/Mandriva always did (in grub-legacy), and the memtest86+ package does install the memtest binary into /boot/memtest.bin. So I think that the least-surprise principle should create the boot option.

(I can see the advantage of an enhancement in say /etc/default/grub of adding
an option GRUB_DISABLE_MEMTEST, similar to GRUB_DISABLE_OS_PROBER).

OK please test grub2-2.00-43.mga3 in updates testing.

You should have memtest86+ in the menu if it is installed, if memtest86+ is uninstalled it should not appear.

Status: NEW => ASSIGNED
Assignee: bugsquad => zen25000
Source RPM: memtest86+-4.20-3.mga3 => grub2

Thank you very much. I have just tested this and it works great :-)

Here are the tests I did:

* Install the new grub2 package. It triggered update-grub, and found memtest86+

* Uninstall and reinstall memtest86+. Each time, update-grub is correctly called, and the menu entry is added to / removed from grub.cfg.

* Actually boot grub2 and select the Memtest option; memtest86+ does start.

So, I think we can mark this one fixed :-)

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

I would mark it fixed when it actually lands in core/release as updates_testing will be wiped during release.

Status: RESOLVED => REOPENED
CC: (none) => sander.lepik
Resolution: FIXED => (none)

(In reply to Sander Lepik from comment #5)
> I would mark it fixed when it actually lands in core/release as
> updates_testing will be wiped during release.

Exactly.

@ Richard: Good - thanks for testing - I need to check a few more things, after which I will ask for it to be included in Mga3.

Well we will not. We are 10 days from the final release. This is not a time to add new features.

CC: (none) => ennael1

(In reply to Anne Nicolas from comment #7)
> Well we will not. We are 10 days from the final release. This is not a time
> to add new features.

OK

I just tried to change target release for this and the option to select Mga4 is missing. :\

Might I suggest that this fix is targeted at release 3.1, i.e. to go out in the updates for the Mga3 release?

@ Anne: Could I ask why the Mga team asks its end-users to test the betas if the bugs that we identify and report aren't going to be fixed in that release?  

As to whether this is a "bug" or a "feature", my view is that it is a canonical bug (broken functionality in Mageia that has worked in many other distros, including Mandriva, for years past), and it's a showstopper for me (because my desktop machine has just had trouble with a bad DIMM).

This is a bug indeed and must get fixed. If not for the release then after release as an update.

I made a minor change which places memtest (when installed) always at the end of the menu.

This is in grub2-2.00-44.mga3 which is in updates/testing and svn.

FWIW I am on the fence regarding whether this gets pushed or not. I don't think it's release critical, but others do.

It is ready to go so if the decision is made to push then it's fine by me.

This is now fixed in Cauldron in grub2-2.00-46.mga4 - I will await more testing and other possible updates before pushing to updates/testing for Mga3.
There is a bug in bootloader-config which when fixed (hopefully soon) will also require an update to grub2.

Moving bug from Cauldron to Mga3.

Version: Cauldron => 3

Update Advisory
---------------

grub2-2.00-46.2.mga3.src.rpm has been submitted to /3/core/updates_testing

This update fixes this bug by adding the option to run memtest86+ to the end of the boot menu IF memtest86+ is installed.

Affected rpms:
grub2-2.00-46.2.mga3
grub2-efi-2.00-46.2.mga3
grub2-mageia-theme-2.00-46.2.mga3
grub2-debuginfo-2.00-46.2.mga3

This may be tested by updating grub2 and installing and removing the memtest86+ package. The memtest option will either be available or not.
Selecting memtest should run it.

Assignee: zen25000 => qa-bugs

Could reproduce the bug on mga3 i586, and the update candidate fixes it.

Procedure used:
1) Installed grub2 and grub2-mageia-theme from core/release
2) Installed memtest86+ from core/release
3) Rebooted, no entry for Memtest
4) Installed grub2 and grub2-mageia-theme from core/updates_testing
The automatic configuration of grub2 was triggered and found /boot/memtest.bin
5) Rebooted, Memtest has an entry and works
6) Uninstalled memtest86+, which triggers the update of grub.cfg, removing the entry for Memtest.

So it's okay for me on i586.

--

As a side note, there's a small issue (which was already there before and might not be related only to grub2): When rebooting from KDE4, using the reboot entry from the menu, one can choose which entry to boot on. The choice has no influence on the behaviour of grub2 (actually I suspect that it refers only to grub). Should I file a bug for that, and if yes, against which components? Is it linked to grub2, to KDE or to Mageia?

CC: (none) => remi
Hardware: x86_64 => All
Whiteboard: (none) => MGA3-32-OK

(In reply to Rémi Verschelde from comment #14)

> --
> 
> As a side note, there's a small issue (which was already there before and
> might not be related only to grub2): When rebooting from KDE4, using the
> reboot entry from the menu, one can choose which entry to boot on. The
> choice has no influence on the behaviour of grub2 (actually I suspect that
> it refers only to grub). Should I file a bug for that, and if yes, against
> which components? Is it linked to grub2, to KDE or to Mageia?

Remi,

Please read https://bugs.mageia.org/show_bug.cgi?id=10246#c19 and see if the KDE settings that I mention in there fix it.
It took a while to figure out how that works ;)

Thanks,
Barry

Thanks - works for me now :-)

Testing complete mga3 64, Ok for me works fine :

--------------------------------------------------------------------
With grub2 on core_updates_testing :

# LC_ALL=C urpmi memtest86+


    $MIRRORLIST: media/core/release/memtest86+-4.20-3.mga3.x86_64.rpm
installing memtest86+-4.20-3.mga3.x86_64.rpm from /var/cache/urpmi/rpms        
Preparing...                     #############################################
      1/1: memtest86+            #############################################
Generating grub.cfg ...
Found theme: /boot/grub2/themes/maggy/theme.txt
Found linux image: /boot/vmlinuz-desktop
Found initrd image: /boot/initrd-desktop.img
Found linux image: /boot/vmlinuz-3.8.13-desktop-1.mga3
Found initrd image: /boot/initrd-3.8.13-desktop-1.mga3.img
Found memtest image: /boot/memtest.bin
done
------------------------------------------------------------------
# LC_ALL=C urpme memtest86+
removing memtest86+-4.20-3.mga3.x86_64
removing package memtest86+-4.20-3.mga3.x86_64
      1/1: removing memtest86+-4.20-3.mga3.x86_64
                                 #############################################
Generating grub.cfg ...
Found theme: /boot/grub2/themes/maggy/theme.txt
Found linux image: /boot/vmlinuz-desktop
Found initrd image: /boot/initrd-desktop.img
Found linux image: /boot/vmlinuz-3.8.13-desktop-1.mga3
Found initrd image: /boot/initrd-3.8.13-desktop-1.mga3.img
done

CC: (none) => geiger.david68210
Whiteboard: MGA3-32-OK => MGA3-32-OK MGA3-64-OK

Validating. Advisory uploaded.

Could sysadmin please push from 3 core/updates_testing to core/updates

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Update pushed:
http://advisories.mageia.org/MGAA-2013-0055.html

Status: REOPENED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED