LinuxQuestions.org - memtest86 at boot (LILO)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - memtest86 at boot (LILO) (https://www.linuxquestions.org/questions/slackware-14/memtest86-at-boot-lilo-4175575657/)

Bindestreck

03-23-2016 03:21 AM

memtest86 at boot (LILO)

Hi,

In the past this code in lilo worked:

Code:

image = /boot/memtest

label = memtest

memtest is a *.bin-file. However, trying that results in a black screen and after some seconds the computer is rebooting. Does Lilo nowadays require some extra configs to make this work?

Cheers!

phi11ip

03-23-2016 05:25 AM

Works fine for me. The only difference is my memtest bin file is in a different directory.

solarfields

03-23-2016 07:37 AM

Bindestreck,

have you tried https://slackbuilds.org/repository/1...em/memtest86+/

Bindestreck

03-23-2016 07:50 AM

Quote:

Originally Posted by solarfields (Post 5520170)

Bindestreck,

have you tried https://slackbuilds.org/repository/1...em/memtest86+/

Yes I have. Hmm, this is very strange.

*EDIT:

I also tried with this:

image = /boot/memtest86+.bin
root = /dev/sda2
label = memtest86+
read-only

I am clueless. I may give grub a try.

chicken76

03-23-2016 08:41 AM

I also have this problem.
http://www.linuxquestions.org/questi...nu-4175562569/

In the end, I gave up and put memtest on a usb stick. :banghead: More manual work required but less grey hair generated.

elyk	03-23-2016 08:21 PM

Building memtest86+ generates a few similarly-named files. The one with the .bin suffix should be the right one, but you might double-check...

Code:

$ file memtest*

memtest:            ELF 32-bit LSB  executable, Intel 80386, version 1 (SYSV), statically linked, stripped

memtest.bin:        x86 boot sector

memtest.bin.lds:    ASCII text, with CRLF line terminators

memtest.lds:        ASCII text, with CRLF line terminators

memtest_shared:    ELF 32-bit LSB  shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped

memtest_shared.bin: data

memtest_shared.lds: assembler source text

I've had bad luck with newer versions. On my machines it'll start up, then I think I can make out the word "unsupported" or "unknown" (or something like that, can't remember) before it reboots.

You might also try the original "memtest86" (without the "+") from SBo and see if that works any better.

chicken76

03-24-2016 04:12 AM

I don't think it's a matter of memtest86 vs. memtest86+ or latest version vs. older versions.
They all work fine if booted from a cd or usb stick. Only when trying to boot from hdd via lilo something goes wrong.

number22

03-25-2016 07:19 AM

change AHCI to Native IDE in bios

Gordie

10-03-2018 12:00 PM

FIRST - I am not in the habit of resurrecting old threads but this one came up in a search and I have information that applies.

This is what works on my legacy boot computers as we speak:

# Linux memtest86 config begins
image = /boot/memtest86.bin
label = memtest86
password = whatever_password_you_decide_upon
read-only
# Linux memtest86 config ends
#
# Linux memtest86+ config begins
image = /boot/memtest86+.bin
label = memtest86+
password = whatever_password_you_decide_upon
read-only
# Linux memtest86+ config ends

SCerovec

10-06-2018 11:32 AM

I had it working only once i downloaded the EFI memetest from their home page

All times are GMT -5. The time now is 02:58 PM.