Problem with GRUB2

[bw_mzee]

Hali Everibody. On BookwormPup64 10.0.100 with a 'set gfxpayload=keep' grub config setting the gfxpayload screen is not kept. It switches to a character display with kernel messages immediately before the INIT script starts, even if I copy the properly working grub.cfg of Fossapup64, just rewriting the BookwormPup64 kernel and initrd settings. Does anyone know if there is some kernel command line parameter, missing module, or other trick to restore the correct operation?

[williwaw]

some ideas here?

https://superuser.com/questions/919028/ ... -to-the-os

[bigpup]

BookwormPup64 is not the same as Fossapup64, so do not try to mix them.

What grub2 are you using?

Booting a live install of BookwormPup64 which should be using the boot loader provided in the ISO?

A frugal install using a grub2 boot loader you installed?

What exactly do you want to happen when it starts booting?

[williwaw]

BookwormPup64 is not the same as Fossapup64, so do not try to mix them.

I use vanilladpup with grub2 and assumed bookwormpup boots with grub2 as well, or perhaps I am mistaken?

[bigpup]

Any Puppy can boot using Grub2 boot loader, if it has a properly setup grub.cfg file entry.

Not all Puppy versions use exactly the same commands in the entry.

Requirements change as Puppy has developed.

BookwormPup64 now requires a command for loading the ucode.cpio file.

Also uses some different commands for using fsck.

[bw_mzee]

some ideas here?

https://superuser.com/questions/919028/ ... -to-the-os

Thanx, but it boots with the 'linux <filename>' command, not with 'multiboot'.

[bw_mzee]

What grub2 are you using?

Grub2.12.

Booting a live install of BookwormPup64 which should be using the boot loader provided in the ISO?

Yes, but paths and kernel parms rewritten for the hd/frugal install.

A frugal install using a grub2 boot loader you installed?

A more difficult 'mix', just a little Grub4dos chainloads a grub2 core.img with embedded config with a 'normal /BookwormPup64/grub.cfg' command. But once again: the frugal system is booting and working well, and with the same loader chain to a /fossapup/grub.cfg the 'gfxpayload=keep' works too.

What exactly do you want to happen when it starts booting?

To see only the splash graphics without any messages, until the X starts.

[bigpup]

I thought that was what you wanted.

But I can tell you for sure, that seeing the information statements, as Puppy boots, is there for a good reason.

Puppy is doing a lot of things, that have to happen in a set order, as it boots.

If something in the boot process does not correctly work.

That information will be a big clue as to what needs fixed.

My suggestion is just do not look at the screen while it is booting.

[williwaw]

some ideas here?

https://superuser.com/questions/919028/ ... -to-the-os

Thanx, but it boots with the 'linux <filename>' command, not with 'multiboot'.

there was an interesting link to a related topic in the right hand side bar of that page, but as bigpup points out, will having the splash work out if you have more than one save to pick from?

[mikeslr]

It might help if we knew exactly what grub.cfg says. Ordinarily we'd only need the Bookwormpup stanza: the 'paragraph' begining with something like "menuentry 'Bookworm 10.0.10 (sda4/book)' --class puppylinux{". But as your issue is with " 'set gfxpayload=keep'"
I'd suggest you also include the entire initiating stanza; i.e that which begins with (for example):
# grub.cfg produced by grub2config 2.1
set default=0
set timeout=20

[bw_mzee]

My suggestion is just do not look at the screen while it is booting.

Right, but for a stable, well-functioning system, I don't think it's necessary anymore. And when a teacher/boss/policeman or so sees the running lines on the screen, she/he instantly says: “It’s not a Vindoze, huh? You are suspicious, litta bro.”

[bw_mzee]

there was an interesting link to a related topic in the right hand side bar of that page, but as bigpup points out, will having the splash work out if you have more than one save to pick from?

Thanks, I didn't notice it. But then I tried disabling the nouveau, but that didn't help.

[bw_mzee]

It might help if we knew exactly what grub.cfg says. Ordinarily we'd only need the Bookwormpup stanza: the 'paragraph' begining with something like "menuentry 'Bookworm 10.0.10 (sda4/book)' --class puppylinux{". But as your issue is with " 'set gfxpayload=keep'"
I'd suggest you also include the entire initiating stanza; i.e that which begins with (for example):
# grub.cfg produced by grub2config 2.1
set default=0
set timeout=20

The grub.cfg practically the same as in the downloaded iso file, only the 'linux' commands were changed, for example:

Code: Select all

linux /BookwormPup/vmlinuz pfix=fsck,fsckp,nocopy pmedia=usbflash psubdir=/BookwormPup

and the full paths for the loadfont, background_image, ucode.cpio and initrd items, like:

Code: Select all

initrd ${ucode_parm} /BookwormPup/initrd.gz

[williwaw]

Thanks, I didn't notice it. But then I tried disabling the nouveau, but that didn't help.

if one save exists, the boot will progress uninterupted
if more than one save exists, the boot will stop at a previously unseen menu in the console and resume after you make your choice of saves.

you can boot with pfix=ram in the linux line to a "first boot" session, which will allow you to create a second save at shutdown. thereafter you wil be presented with the menu......
0 none (which is the same as pfix=ram)
1 your first save
2 your second save etc....

[bw_mzee]

if one save exists, the boot will progress uninterupted
if more than one save exists, the boot will stop at a previously unseen menu in the console and resume after you make your choice of saves.

you can boot with pfix=ram in the linux line to a "first boot" session, which will allow you to create a second save at shutdown. thereafter you wil be presented with the menu......
0 none (which is the same as pfix=ram)
1 your first save
2 your second save etc....

Yes, but where is the problem? If I have more than one saves, then I do know it. If someone don't, she/he will suck it. On the old Fossapup, where the 'splash=keep' works, I use encrypted savefile. Where the INIT asks for the password, I've put a 'beep' command into the script, just for convenience. If any unforeseen problems arise and the boot stops, you can comment out the 'keep' command from the grub.cfg at any time from an other working system.