Problem updating grub-solved-

[rburkartjo]

okay trying to change the default boot screen time out to 0
in ubuntu i set to -1 to accomplish
i made the follow change in grub.cfg
set timeout=-1
saved and exit and rebooted
no luck
so tried running grub-update in terminal
root# update-grub
bash: update-grub: command not found
any ideas
tks
is there a different command in puppy to update grub

[bigpup]

How is Fossapup installed?
A live install on a CD or USB drive?
A frugal install on some drive?
If frugal, how did you do the frugal install?
How did you install the Grub boot loader?

Need to know what actual Grub.cfg you have.

Post the contents of your grub.cfg.
That will tell us.

Puppy does not have the complete Grub2 boot loader package.
Only what is needed to make a working boot loader.

[Clarity]

Hello @rburkartjo
This 'may' offer you a solution. Try the various of 0/1/5. Not sure how GRUB2 handles a negative time for timeout in current GRUB2.

Currently, PUPs & DOGs do not ship with the complete compliment of GRUB2. Hopefully that may get resolved in future WoofCE builds going forward as more members need those GRUB2 utils for various benefits.

Hope that helps

[mikewalsh]

@rburkartjo :-

There IS no "update" command for Grub4DOS. It doesn't NEED one. Unlike GRUB2, which insists on re-probing, and re-cataloguing every time you do this, just set timeout to "0", save & re-boot.

I'm not surprised nothing happened when you tried "-1". Where on earth did you dredge that driblet of information up from? Grub4DOS doesn't recognize negative-value numbers, so it would have reset itself back to the previously-saved configuration.

I've said it before, and I'll say it again; for Chrissakes stop trying to treat Puppy as a mainstream distro. She doesn't like it; that's why she keeps nipping at your ankles!

Mike.

[bigpup]

changed to:
set timeout=0
in my grub.cfg

That eliminated any boot delay for me.

But I am not sure, what your grub boot menu, has for optional selections.
You may find a time, when having that delay, will allow you to use one of these maybe needed options.

[rburkartjo]

first tks
if i need a solution to a problem i first use what i have learned in the past that worked if that doesnt work i ask fo help.and i realise that puppy isnt ubuntu.
i still want to increase the standard 10 second boot screen time out. my mobility issues sometimes prevent my fingers from working in a timely manor. and with ubuntu i was able to make the boot screen persistent. install is on a usb stick. and since you can save sessions there is a way to do this.i just have not found

[mikewalsh]

first tks
if i need a solution to a problem i first use what i have learned in the past that worked if that doesnt work i ask fo help.and i realise that puppy isnt ubuntu.
i still want to increase the standard 10 second boot screen time out. my mobility issues sometimes prevent my fingers from working in a timely manor. and with ubuntu i was able to make the boot screen persistent. install is on a usb stick. and since you can save sessions there is a way to do this.i just have not found

Nah, that's fair comment. I myself have the timeout set to 20 seconds, along with a 'Puppy' background Nic007 (amethyst) provided back on the old Murga Forum:-

Code: Select all

# menu.lst produced by grub4dosconfig-v1.9.3
color white/blue black/cyan white/black cyan/black
splashimage=/splash.xpm
timeout 20
default 0

Sweet, ain't she..? (I always think of Puppy as a 'she', I don't know why...)

AKAIK, you can set the timeout to anything you want. I mean, fair comment; I agree with you.....you're not the first to come unstuck with certain aspects of Puppy, after having got used to the way mainstream distros do it. And I'm absolutely certain you won't be the last..!!

But that's what we like doing; helping folk to get the best out of our wee canine... It's like so many things in Puppy; most of 'em can usually be 'fixed' by simple editing of a script, somewhere.

Mike.

[rburkartjo]

mike what am i doing wrong
i have a fat 32 installation on a stick
when i change the time out on the menu first to 20 seconds doesnt work/tks

[bigpup]

Now that we know you want the boot screen persistent and not time out.

We still do not know for sure what boot loader is being used or what boot menu config file.
Boot menu config file.
is it grub.cfg or menu.lst.

The time entry is different in each one.

Post the contents of your boot loader menu config file.
That will tell us.

[mikewalsh]

Now that we know you want the boot screen persistent and not time out.

We still do not know for sure what boot loader is being used or what boot menu config file.
Boot menu config file.
is it grub.cfg or menu.lst.

The time entry is different in each one.

Post the contents of your boot loader menu config file.
That will tell us.

I agree with bigpup. Just let us see what you're using for a bootloader - menu.lst OR grub.cfg - and we can hopefully see what's happening. I don't know about you, but I'm not much of one for "guessing games".

Mike.

[rburkartjo]

ootloader - menu.lst OR grub.cfg i have both how to determine which one i am using?

[Clarity]

Hi @rburkartjo I "think" I understand what you are asking. It seems you want to remain on the boot-selection screen, indefinitely until some selection is made.

A timeout does do this.

You ALSO ask a very good question: Your question on which of the "several" boot loader options a single PUP/DOG might be employing at machine start is NOT evident to any casual user. The user ONLY sees the options for boot without any indication of which boot-loader is being used.

I had never considered this before but it does offer great benefit, IMHO, if in some occasions I knew that.

Yes, booting from a PUP's ISO file, a modern PUP will show one of its boot-managers on one machine that boot-manager's way of showing the selection. Then booting that same ISO on a different PC will use the other of its boot-manager and show the selection differently. Yes, I had noticed that too, but never thought much of it. Again, you ask a good question: (rephased) How does a user know at PUP Menu screen which of the different boot-managers is being used?

I will extend your question to an additional one I have: After desktop arrival is that some log that tell which boot-loader was used by PUP to boot the PC? (since it will differ depending on which PC is used to boot (BIOS/UEFI32/UEFI64)

In the WoofCE PUPs the beginning start when giving control to PUP's booter, there is a selection that is being made somewhere as to which of the several boot-loader (aka boot-menu) will be presented on-screen.

This is my guess for modern PUP solution's answer... "hit the 'e' letter key on any menu line". If it exposes the boot commands that will be used, it is 'probably' GRUB2 exposing those boot-command line items.

I stand corrected as there may be other methods that can be used at the Puppy boot menu that will expose which of the varied bootloaders the PUP is using at the time.

[rburkartjo]

clar yes that is exactly what i want to do/tks
and using e shows it grub
so what do i need to do next

[mikewalsh]

@Clarity :-

AFAIK, from my own experience, both GRUB2 AND Grub4DOS display a "title-bar" at the top of the boot Menu window, telling you what's in use. At least, they always do for me......

(*shrug...*)

Mike.

[Clarity]

@rburkartjo, You have the option of adding or changing any Linux line you see.

Or after 'e' (with or without changes), you can hit 'F10' to boot in the case of GRUB2; or for SYSLINUX 'enter' and 'b'.

Hope this helps.

[shinobar]

I will extend your question to an additional one I have: After desktop arrival is that some log that tell which boot-loader was used by PUP to boot the PC? (since it will differ depending on which PC is used to boot (BIOS/UEFI32/UEFI64)

Xenialpup 7.5 and later has a command 'efibootmgr' to see UEFI boot or not.

[Clarity]

Thanks @shinobar. I am not sure how to interpret this result, but will compare in other systems in hope to understand how it shows which boot-manager was used to start the system.

Here's what this slacko64 v8.2.1 PC is showing me.

Code: Select all

~$ efibootmgr
EFI variables are not supported on this system.
~$ uname -a
Linux DellRich 5.10.0 #1 SMP Sun May 30 11:13:02 AEST 2021 x86_64 Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz GenuineIntel GNU/Linux

Any comments-ideas would be helpful knowledge.

[shinobar]

~$ efibootmgr
EFI variables are not supported on this system.

Means BIOS boot, not UEFI. You cannot see what boot loader waked up the Puppy anyway.

[Clarity]

Thanks @shinobar.
Check your PM for an indirectly related concern.

[bigpup]

ootloader - menu.lst OR grub.cfg i have both how to determine which one i am using?

you stated this earlier.

when i change the time out on the menu first to 20 seconds doesn't work/tks

Whatever menu config file you did this change in, must be the wrong file.

So try to make the change in the other config file.

Both boot loader menu config files have a timeout entry.
It is just worded a little differently.

Fossapup64 9.5 has several different setups for a boot loader.
Depending on the computer and bios it uses.
Determines which boot loader is getting used to boot.
This ability to automatically use different boot loaders, hopefully lets a Fossapup live install, boot on any computer, without the user having to get into, what boot loader to use, decision.
That is the hope anyway

[rburkartjo]

tks all
getting no where
i have adjust time out on both grub and 1st menu and no luck
i will keep thread open for awhile

[bigpup]

That gives us no useful info to help you.

You do specifically what?
To specifically what?
You see specifically what?

How do we know you did it correctly, if you do not specifically tell us, specific details.

Adjusting the timeout setting, in the correct boot menu config file, should be working.
It does for me.

[rburkartjo]

okay fixed it while could not figure out how to disable the time out i made these changes to set to 6 minutes
/initrd/mnt/dev_save/menu.lst
and i changed timeout to 360