public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] Booting memtest86 from grub2
@ 2013-05-11 23:12 walt
  2013-05-12 10:07 ` Neil Bothwick
  0 siblings, 1 reply; 7+ messages in thread
From: walt @ 2013-05-11 23:12 UTC (permalink / raw
  To: gentoo-user

Dale, you didn't describe the symptoms you're seeing, but maybe
just seeing how I did it will help:

menuentry "memtest86" {
 search -l gentoo64unstable -s root
 linux ($root)/boot/memtest86/memtest
 boot 
}

Note that gentoo64unstable is the label I gave my root partition.
I do that in case I hot-plug a disk that changes the /dev/name of
the partition.  That's the reason I switched to grub2 originally.
(You can search instead for the UUID if you prefer to use that.)



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-user] Booting memtest86 from grub2
  2013-05-11 23:12 [gentoo-user] Booting memtest86 from grub2 walt
@ 2013-05-12 10:07 ` Neil Bothwick
  2013-05-12 12:40   ` Dale
  0 siblings, 1 reply; 7+ messages in thread
From: Neil Bothwick @ 2013-05-12 10:07 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 746 bytes --]

On Sat, 11 May 2013 16:12:52 -0700, walt wrote:

> Dale, you didn't describe the symptoms you're seeing, but maybe
> just seeing how I did it will help:
> 
> menuentry "memtest86" {
>  search -l gentoo64unstable -s root
>  linux ($root)/boot/memtest86/memtest
>  boot 
> }

I don't know about memtest86, but memtest86+ installs a menu file
in /etc/grub.d, which means grub-mkconfig handles it.

% cat /etc/grub.d/39_memtest86+
#!/bin/sh
exec tail -n +3 $0

menuentry "memtest86+ 4.20" {
        linux16 /boot/memtest86plus/memtest
}

menuentry "memtest86+ 4.20 (netbsd)" {
        insmod bsd
        knetbsd /boot/memtest86plus/memtest.netbsd
}


-- 
Neil Bothwick

Maybe... How much are you bribing me this time?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-user] Booting memtest86 from grub2
  2013-05-12 10:07 ` Neil Bothwick
@ 2013-05-12 12:40   ` Dale
  2013-05-12 12:50     ` Neil Bothwick
  0 siblings, 1 reply; 7+ messages in thread
From: Dale @ 2013-05-12 12:40 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

Neil Bothwick wrote:
> On Sat, 11 May 2013 16:12:52 -0700, walt wrote:
>
>> Dale, you didn't describe the symptoms you're seeing, but maybe
>> just seeing how I did it will help:
>>
>> menuentry "memtest86" {
>>  search -l gentoo64unstable -s root
>>  linux ($root)/boot/memtest86/memtest
>>  boot
>> }
>
> I don't know about memtest86, but memtest86+ installs a menu file
> in /etc/grub.d, which means grub-mkconfig handles it.
>
> % cat /etc/grub.d/39_memtest86+
> #!/bin/sh
> exec tail -n +3 $0
>
> menuentry "memtest86+ 4.20" {
>         linux16 /boot/memtest86plus/memtest
> }
>
> menuentry "memtest86+ 4.20 (netbsd)" {
>         insmod bsd
>         knetbsd /boot/memtest86plus/memtest.netbsd
> }
>
>


That is what I did last.  I just emerged the thing and it put the file
there.  You know I don't reboot often here but this is what it says when
I update grub:

root@fireball / # /root/grub-update
Generating grub.cfg ...
Found linux image: /boot/kernel-3.8.7-1
Found linux image: /boot/kernel-3.6.6-1
Found linux image: /boot/kernel-3.5.3-3
done
root@fireball / #

Shouldn't there be a line for the memtest entry or does it not show
that?  Maybe it is working and I don't know it yet.  lol

Oh, I have a script that has the longer command in it with all the nifty
options.  That's why the command is different.

root@fireball / # cat /root/grub-update
 
grub2-mkconfig -o /boot/grub2/grub.cfg
root@fireball / #

Thanks for the help.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 2620 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-user] Booting memtest86 from grub2
  2013-05-12 12:40   ` Dale
@ 2013-05-12 12:50     ` Neil Bothwick
  2013-05-12 14:00       ` Dale
  0 siblings, 1 reply; 7+ messages in thread
From: Neil Bothwick @ 2013-05-12 12:50 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

On Sun, 12 May 2013 07:40:15 -0500, Dale wrote:

> > I don't know about memtest86, but memtest86+ installs a menu file
> > in /etc/grub.d, which means grub-mkconfig handles it.
> >
> > % cat /etc/grub.d/39_memtest86+
> > #!/bin/sh
> > exec tail -n +3 $0
> >
> > menuentry "memtest86+ 4.20" {
> >         linux16 /boot/memtest86plus/memtest
> > }
> >
> > menuentry "memtest86+ 4.20 (netbsd)" {
> >         insmod bsd
> >         knetbsd /boot/memtest86plus/memtest.netbsd
> > }
> 
> That is what I did last.  I just emerged the thing and it put the file
> there.  You know I don't reboot often here but this is what it says
> when I update grub:
> 
> root@fireball / # /root/grub-update
> Generating grub.cfg ...
> Found linux image: /boot/kernel-3.8.7-1
> Found linux image: /boot/kernel-3.6.6-1
> Found linux image: /boot/kernel-3.5.3-3
> done
> root@fireball / #
> 
> Shouldn't there be a line for the memtest entry or does it not show
> that?  Maybe it is working and I don't know it yet.  lol

There are no echo commands in the file, so it doesn't show anything when
adding. grub-mkconfig doesn't output anything by default, only the helper
scripts generate non-error output

Check the contents of grub.cfg.

> Oh, I have a script that has the longer command in it with all the nifty
> options.  That's why the command is different.
> 
> root@fireball / # cat /root/grub-update
>  
> grub2-mkconfig -o /boot/grub2/grub.cfg

I do a similar thing, except the script is in /usr/local/bin, where it
should be :P, and it checks if /boot is mounted ro and remounts it rw if
necessary.


-- 
Neil Bothwick

WinErr 019: User error - Not our fault. Is Not! Is Not!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-user] Booting memtest86 from grub2
  2013-05-12 12:50     ` Neil Bothwick
@ 2013-05-12 14:00       ` Dale
  2013-05-12 14:31         ` Neil Bothwick
  0 siblings, 1 reply; 7+ messages in thread
From: Dale @ 2013-05-12 14:00 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]

Neil Bothwick wrote:
> On Sun, 12 May 2013 07:40:15 -0500, Dale wrote:
>
>>> I don't know about memtest86, but memtest86+ installs a menu file
>>> in /etc/grub.d, which means grub-mkconfig handles it.
>>>
>>> % cat /etc/grub.d/39_memtest86+
>>> #!/bin/sh
>>> exec tail -n +3 $0
>>>
>>> menuentry "memtest86+ 4.20" {
>>>         linux16 /boot/memtest86plus/memtest
>>> }
>>>
>>> menuentry "memtest86+ 4.20 (netbsd)" {
>>>         insmod bsd
>>>         knetbsd /boot/memtest86plus/memtest.netbsd
>>> }
>>
>> That is what I did last.  I just emerged the thing and it put the file
>> there.  You know I don't reboot often here but this is what it says
>> when I update grub:
>>
>> root@fireball / # /root/grub-update
>> Generating grub.cfg ...
>> Found linux image: /boot/kernel-3.8.7-1
>> Found linux image: /boot/kernel-3.6.6-1
>> Found linux image: /boot/kernel-3.5.3-3
>> done
>> root@fireball / #
>>
>> Shouldn't there be a line for the memtest entry or does it not show
>> that?  Maybe it is working and I don't know it yet.  lol
>
> There are no echo commands in the file, so it doesn't show anything when
> adding. grub-mkconfig doesn't output anything by default, only the helper
> scripts generate non-error output
>
> Check the contents of grub.cfg.

Well I be darn.

### BEGIN /etc/grub.d/39_memtest86+ ###

menuentry "memtest86+ 4.20" {
    linux16 /boot/memtest86plus/memtest
}

menuentry "memtest86+ 4.20 (netbsd)" {
    insmod bsd
    knetbsd /boot/memtest86plus/memtest.netbsd
}
### END /etc/grub.d/39_memtest86+ ###

There it be.  I wonder if it worked all the other times I tried?

>
>
>> Oh, I have a script that has the longer command in it with all the nifty
>> options.  That's why the command is different.
>>
>> root@fireball / # cat /root/grub-update
>> 
>> grub2-mkconfig -o /boot/grub2/grub.cfg
>
> I do a similar thing, except the script is in /usr/local/bin, where it
> should be :P, and it checks if /boot is mounted ro and remounts it rw if
> necessary.
>
>


I keep mine mounted anyway.  I'm not a script writer by any means.

Next time I reboot, I'll see if it is really there or not.  Looks like
it is.

Thanks much.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 3899 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-user] Booting memtest86 from grub2
  2013-05-12 14:00       ` Dale
@ 2013-05-12 14:31         ` Neil Bothwick
  2013-05-12 20:24           ` Dale
  0 siblings, 1 reply; 7+ messages in thread
From: Neil Bothwick @ 2013-05-12 14:31 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Sun, 12 May 2013 09:00:04 -0500, Dale wrote:

> ### END /etc/grub.d/39_memtest86+ ###
> 
> There it be.  I wonder if it worked all the other times I tried?

If anyone else had asked that question I'd have said "yes" :)

> > I do a similar thing, except the script is in /usr/local/bin, where it
> > should be :P, and it checks if /boot is mounted ro and remounts it rw
> > if necessary.

> I keep mine mounted anyway.  I'm not a script writer by any means.

As do I, but read-only. It prevents filesystem corruption but, unlike not
mounting it, it also avoids the embarrassment of installing a new kernel
then wondering why it boots with the old one :)


-- 
Neil Bothwick

Bumper Sticker: If you can read this, you are in phaser range.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-user] Booting memtest86 from grub2
  2013-05-12 14:31         ` Neil Bothwick
@ 2013-05-12 20:24           ` Dale
  0 siblings, 0 replies; 7+ messages in thread
From: Dale @ 2013-05-12 20:24 UTC (permalink / raw
  To: gentoo-user

Neil Bothwick wrote:
> On Sun, 12 May 2013 09:00:04 -0500, Dale wrote:
>
>> ### END /etc/grub.d/39_memtest86+ ###
>>
>> There it be.  I wonder if it worked all the other times I tried?
> If anyone else had asked that question I'd have said "yes" :)

Well, it is spring here so I shutdown today and did some serious blowing
out of the dust.  One thing about the Cooler Master HAF-932 case, lots
of air flow, quite a bit of dust too.   Anyway, when I booted up again,
there sat memtest86+ in the menu.  I selected it and you won't guess the
result.  Yep.  Error message.  Can I shoot it now?  :-/  I can't copy
and paste so bear with my fat fingers.

error: too small lower memory 0x9100 > 0x98400

Put to use my pitiful google skills and found out this is quite common. 
That makes me feel better.  It isn't JUST me.  Downgrading memtest
thingy and trying a older version.  After that, I'll try some other
tester thingy.  If that fails, remove the file and use my USB stick
thingy. 

I do a lot of thingys when things ain't going right. 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2013-05-12 20:24 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-11 23:12 [gentoo-user] Booting memtest86 from grub2 walt
2013-05-12 10:07 ` Neil Bothwick
2013-05-12 12:40   ` Dale
2013-05-12 12:50     ` Neil Bothwick
2013-05-12 14:00       ` Dale
2013-05-12 14:31         ` Neil Bothwick
2013-05-12 20:24           ` Dale

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox