This has been fixed in lucid.
memtest86+ (4.00-2ubuntu1) lucid; urgency=low
* Merge from debian testing, remaining changes:
- Makefile: Add -fno-stack-protector to CFLAGS, since this package does
not link against libc.
- debian/grub: check for existance of /usr/lib/grub/grub-mkconfig_lib
- debian/postinst: Only run update-grub2 in postinst if
/boot/grub/grub.cfg exists
memtest86+ (4.00-2) unstable; urgency=low
* Fix wrong integration of grub2 patch (Closes: #549125).
memtest86+ (4.00-1) unstable; urgency=low
* New upstream release (Closes: #548033).
* Dropped obsolete patches for old gcc-4.3 bugs (works fine now), and
for opteron (support for builtin memory controller was redone).
* Update grub2 support file to use "linux16" command and use
grub-mkconfig_lib instead of old update-grub_lib (Avi Rozen,
Closes: #539907, #522345).
* Update grub2 support file for systems where /boot is on a separate
partition (Vasilis Vasaitis, Closes: #540572).
** Changed in: memtest86+ (Ubuntu)
Status: Confirmed => Fix Released
--
cannot start memtest86+ when /boot is a separate partition
https://bugs.launchpad.net/bugs/450351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
