Frugal Fossapup 'Dumping last lines of tmp/bootinit/log' on boot

[mivison]

Hi all, I'm running puppy along side of Antix on a Dell laptop. When I boot into puppy( I'm using the same grub file as Antix) I get this on my boot screen when booting into puppy. It did the same thing when I was booting from a usb thumb and have the puppySave file on this computer on the Windows 10 drive. Can someone help with this? It boots after a 60 second pause, but it would be nice if it boot up faster.

[taersh]

If nothing helps, you could edit the init script in initrd.gz.

Search for:

Code: Select all

L_PAUSING_60_SECONDS

In Function check_status() you'll find code:

Code: Select all

    else
      echo "${L_PAUSING_60_SECONDS}" >/dev/console
      sleep 60
    fi

Change the sleep 60 to (perhaps) sleep 5?

[bigpup]

I'm running puppy along side of Antix on a Dell laptop

What specific Puppy version?

Installed to the internal drive of computer??

What format is the partition it is installed on?

I assume Puppy is a frugal install?

Post the entry you put in the boot loader menu to boot Puppy?

Is windows 10 completely shutdown normal?
Do not shut it down in hibernate!!
That messes up ability of Puppy to properly access the drives.

Try booting not having any USB drives plugged into the computer.

[mivison]

@bigpup
9.5 fossapup
yes, internal install
format ext4
frugal install
Boot menu text
menuentry "Puppy " {
search --no-floppy --file --set /pup/vmlinuz
linux /pup/vmlinuz psubdir=/pup pfix=fsck,fsckp
initrd /pup/initrd.gz
}
no windows installed at this time. I hosed it with Antix. haha
no usb plugged in at this time.

[bigpup]

How exactly did you do the frugal install?
.
.

menuentry "Puppy " {
search --no-floppy --file --set /pup/vmlinuz
linux /pup/vmlinuz psubdir=/pup pfix=fsck,fsckp
initrd /pup/initrd.gz

search --no-floppy --file --set /pup/vmlinuz
Try this:
search --no-floppy --set=root --file /pup/vmlinuz

linux /pup/vmlinuz psubdir=/pup pfix=fsck,fsckp
Try this:
linux /pup/vmlinuz pmedia=atahd psubdir=/pup pfix=fsck,fsckp

[taersh]

...haha
no usb plugged in at this time.

So, booting is fine and quick without usb flash drive plugged in?

[mivison]

@bigpup
Well I tried changing the grub code, but it is still the same. I'm thinkful that it still boots because I am very use to Puppy and how to move around in it. To answer your question on my install. I just copied the needed files to a directory I named pup. Then I copied and pasted some code from another grub menu I had on a different PC. I had already installed Antix Linux as an alternative. So I just added Puppy to the Antix grub menu. How ever it was acting like this before. Like I said when I had Windows on here.

[mivison]

@taersh
I tryed this too. something keeps changing it back to 60 sec.

If nothing helps, you could edit the init script in initrd.gz.

Search for:

Code: Select all

L_PAUSING_60_SECONDS

In Function check_status() you'll find code:

Code: Select all

    else
      echo "${L_PAUSING_60_SECONDS}" >/dev/console
      sleep 60
    fi

Change the sleep 60 to (perhaps) sleep 5?

[foxpup]

something keeps changing it back to 60 sec.

Sure you have repacked initrd.gz the proper way? It is with cpio.

Have you tried other Puppys? Is it the same?

[bigpup]

What model Dell laptop is this computer?

Is the internal drive a hard drive or SSD?

[mivison]

@foxpup
I did not.I just used Geany. I don't know what cpio is. I'm mainly just a user.

[mivison]

What model Dell laptop is this computer?

Is the internal drive a hard drive or SSD?

SSD
Inspiron 13, 5000 Series

[taersh]

@foxpup
I did not.I just used Geany. I don't know what cpio is. I'm mainly just a user.

If you left-click the initrd.gz there will be an option to expand it to /root.
If expanded, a directory opens and you can edit the init script.
Save the init script after being modified/edited and click the initrd.gz file again,
but make sure to click/update the prev. expanded initrd.gz.
You'll be asked for to update the initrd.gz.
Choose yes.

Reboot...

[foxpup]

Just to clarify:

The initrd.gz contains the init script, the minimal initial basic structure for a Puppy and some tools (modules etc).
You can handle the init script in a texteditor (geany).
The initrd.gz has to be handled with cpio.
cpio is a command. I think it stands for 'copy in and out'.
It dates from the early unix times when tapes where common.
And that is what happens when you follow the instructions of @taersh here above.
In Fossapup there is a tool, a script, that does that for you.

[LateAdopter]

Hello mivision
This happens to me if the modules listed in fossapup64initmodules.txt are not in the kernel-modules sfs (zdrv)
In my case it's because I have built them into the kernel and they are no longer separate modules.

You need to look at which modules are listed in fossapup64initmodules.txt to see if they are significant.

If you rename fossapup64initmodules.txt it should stop hanging at that point but you might need to work out why the module(s) have gone missing. Perhaps you have switched to a different kernel.

The fossapup64initmodules.txt is in the same directory as the savefile.

[foxpup]

Perhaps you have switched to a different kernel.

When you switch kernel, you have to switch both vmlinuz, the kernel proper,
and the zdrv.sfs, with the separate kernel modules, that goes with it.

You have to change the name of zdrv to match for the Puppy.
You do not change the initrd.gz, so the init still looks for the original name of the zdrv.sfs.

[bigpup]

your question on my install. I just copied the needed files to a directory I named pup.

Sorry, but this does eliminate one possible cause.
What exact files did you put in the pup directory?

[rcrsn51]

It would be useful to see what was on the screen just before the "Dumping" lines.

[mivison]

by taersh » Sun Feb 21, 2021 12:41 am

mivison wrote: ↑Sat Feb 20, 2021 10:15 pm

@foxpup
I did not.I just used Geany. I don't know what cpio is. I'm mainly just a user.

If you left-click the initrd.gz there will be an option to expand it to /root.
If expanded, a directory opens and you can edit the init script.
Save the init script after being modified/edited and click the initrd.gz file again,
but make sure to click/update the prev. expanded initrd.gz.
You'll be asked for to update the initrd.gz.
Choose yes.

Reboot...

Yep that spead up the boot time. I changed 60 to 4 seconds.
Thanks!