Puppy Linux Discussion Forum

[SOLVED - credit to @bigpup ]

Hi Everyone,

I'm new to Puppy Linux, but eager to using it on my 12 years old laptop, since from what i've heard its very least demanding on H/W specs.
I've tried Zorin, Linux Mint, Lubuntu, Bionicpup, and finally decided this distro, because in live mode my laptop is fully functional (mouse, display, wifi, usb, speaker), and manage to run and join meeting in Zoom smoothly.

However, when i tried to install on HD (linux only, no dual boot), it seems i messed up with gparted, and ended up with no boot partition. Therefore i can not boot from HD. Also, spesifically for Lenovo S-205, i found that the Lenovo IdeaPad S205 has some issues with the Bootloader and Firmware.
https://wiki.archlinux.org/title/Lenovo_IdeaPad_S205

Previously my OS is windows 7.

Is there anyway i can get the tutorial and step by step correct installation, begin with gparted, flags, filesystem, etc.

Thank you.

I'm trying to install Fossapup 9.5 64 bit version

Puppy version
Fossapup 9.5 64 bit

Computer specs
Processor AMD E-300 APU with Radeon(tm) HD Graphics
Memory 3624MB (516MB used)
Machine Type Notebook

Display
Resolution 1366x768 pixels
OpenGL Renderer AMD PALM (DRM 2.50.0 / 5.4.53, LLVM 10.0.0)
X11 Vendor The X.Org Foundation

How is Puppy installed? Full

Installed on: Hard drive

How is drive partitioned: MBR

The partition(s) are formatted what format
\boot
Ext4
Swap

Puppy is installed on which partition
Ext4

using YUMI-2.0.9.0 to create bootable flash disk and running installer from live session

@sebastiansantoso

I have good news and bad news.
The good news: MikeSLR posted detailed instructions on this forum with detailed instruction for installing Puppy Linux to HDD or USB drive. The topic was Manual Frugal Install with some Rox Tips Works every time, if you follow the (detailed) instructions.

The bad news: I found a link (below) to the page/article but it has vanished. (Too far in the past ...)
The Link: https://www.forum.puppylinux.com/viewto ... 4426#p4426

Mike's article is excellent. Perhaps he will re-post it for you.

If it isn't available I will give a short-hand version of Mike's longer article.
I assume you can boot Puppy from a USB drive (or CD).
When I started using Puppy for the first time I made a bootable CD.
Once you have that - you're laughing because you can always recover from any stuff-up.
Let me know.

Cobaka.

How is Puppy installed? Full

Installed on: Hard drive

How is drive partitioned: MBR

The partition(s) are formatted what format
\boot
Ext4
Swap

\boot is not a format

Just redo everything, following this method to do it.

Install Fossapup64 9.5 as a frugal install.
Frugal is just a name used.
It is still the complete OS installed in a special way.
Some features only work in frugal install.
.
.
.
I assume you have Fossapup64 9.5 installed on a CD or USB and can boot the computer with it.

Do all of this from this Fossapup64 booting and running the computer.
Run all programs in This running Fossapup64.

Use the Frugalpup Installer to do the install to hard drive.

Frugalpup installer topic is here:
viewtopic.php?f=105&t=337

Fossapup64 9.5 has Frugalpup Installer already in it.
It is not the newest version, but it will do all you need.

This is how to setup the drive and install Puppy to it.

You do have to manually setup the hard drive with partitions, before using Frugalpup installer.

All data will be deleted from the drive.
So anything you want to keep is going to have to be stored on some other drive.

Use Gparted program to delete all partitions on the internal hard drive.
Make two partitions.
First one a small 300MB, formatted fat32, flagged boot.
2nd partition the rest of the drive, formatted ext 3 or 4.
Note:
If you want to have a swap partition.
Just make the 2nd partition a little smaller leaving some unallocated space to use for making the swap partition.

Note:
If you use a GPT partition table. Only the UEFI boot loader can be installed.
A msdos partition table. Can install UEFI, legacy, or both type boot loaders.

Have the Puppy version iso available at a location it can be accessed.
Store it on the Fossapup USB you are running from, is best location.
Use this Fossapup64 9.5 ISO as source for Frugalpup Installer to use.

run menu->Setup->FrugalPup flexible frugal installer.

This is a program that requires you to make choices, just go slowly and read the provided info.

On main widow select the Puppy button.
This will go thru the install process.
Install Puppy version to the 2nd partition.
It will provide a way to make a directory(folder) to put the frugal install in.
Do that. Best if you name it the name of the Puppy version or similar.
Carefully read that pages information.
Pressing OK does not make the directory.
Pressing enter key does.
Complete install.

Back at main window.
Select boot button.
This will install the boot loader.
Choose to install to the first partition.
You can choose UEFI or legacy or both.
Both will install both types of boot loaders, so both will provide for UEFI and legacy booting.

When complete you should have Puppy version as a frugal install on the 2nd partition.
The Grub2 boot loader on the first partition.

When completed.
Shutdown the computer.
Remove the Fossapup64 USB or CD.
Boot the computer.
Not knowing how you have the boot device selection order in the computers UEFI/bios setup.
May have to change the 1st boot device to the internal hard drive.
When computer boots from the internal drive.
Should see the boot menu, with selection to choose the Fossapup64 you installed.

Note:
On a normally setup UEFI (secure boot enabled) it will require installing the Puppy security key.
When you boot.
The Puppy security key install will run and walk you through installing the security key.

After you get Fossapup64 9.5 running.

It has some updates available.

Do the first shutdown of Fossapup64, making a fossapup save folder.
Reboot, so the save is now being used.

Quickpet program icon on desktop.
Run Quickpet-.Info->Fossapup updates
Reboot the computer, so changes are saved and now being used.

Hi Bigpup,
Thank you for your detailed instruction. I managed to complete the instruction until the end, without any error message.

However, when i select the Fossapup64 9.5 from boot menu, the screen is like this:

When I select the "Fossapup":

I create the msdos partition and choose to install both type of bootloader. The partition table:

My bios system:

Boot device selection order in the computers bios setup:

Make sure you booted with no Fossapup64 9.5 USB drive plugged in?

Something is messed up with the boot loader or the menu entry.

Could try to install the boot loader again.
Maybe something did not get installed correctly the first time.

What boot loader did you install?
UEFI?
Legacy?
Both?

Those Bios images look like you have a legacy bios.
Legacy is probably the boot loader that is needed.

Where did you actually put the Fossapup64 files?
Hopefully you made a directory(folder) to put them in.
What did you name it?

I need to see what is in the boot menu config file.
On the first partition should be the file:
grub.cfg for the UEFI boot loader.
menu.lst for the legacy boot loader.
Both, if you chose to install both boot loaders.
Left click on it to open in a text editor to see the contents.
Copy and paste what it shows in a post.

Also would help if I could see what Fossapup64 files actually got installed on the drive.
If you open a Rox file manager window showing the files that got installed.
Fossapup64 has program Take a Shot that can make an image of it you can attach to post.

Hi sebastiansantoso,

Although I wrote the instructions Cobaka linked to --thanks, Cobaka for the plug-- I now use the recipe bigpup provided using frugalpup installer; but with one (perhaps 2) changes. The one change I always make is this:
After using gparted to create the Linux Ext partition --which will hold the Puppy's system files-- before running frugalpup installer-- I'll create a folder on that partition for those system files:
Left-Click the desktop-drive Icon just above the Task bar. In your case it should be labeled sda2. If you have any doubt just place your mouse-cursor on the icon and a Tooltip will appear showing the size and formatting of that partition. Left-Clicking will mount/open it. Then Right-Click an empty space and from the pop-up menu select New>Directory. Give it a name, e.g. Fossa64.
When you run frugalpup installer it will ask you to select a folder, and if one doesn't exist create it. Either I or the application can make mistakes. But with a folder already created, I just have to select it.
--What follows may only confuse you and is, in any event-- optional--
The only other change I make is that while running gparted I may create more than two partitions (not counting a Swap). Puppy, itself, depending on your interests will only need 2-4 Gbs; with datafiles you create, maybe 10. Fleshed-out to the max with Wine + Windows programs, every AppImage, SFS and portable you can think of, maybe 30 Gbs, not counting datafiles.
I've got a terabyte of hard-drive space. Although Puppy runs as Administrator with access to all drives attached, on boot-up it only mounts the partition on which its system files are located. I'll archive a lot of files which are not always needed [and copies of files which are] on the other (unmounted) partition(s)--mounting them to store or open files.
With those files on an unmounted partition, searching for files currently/recently in use is slightly faster; another road-block exists to deter hackers from accessing sensitive informaton; and if for whatever reason I somehow screw up Puppys' HOME partition, a copy of important files on the 'storage' partition can be accessed via Puppy on a USB-Stick.

Hi @mikeslr
Thank you and will follow through yours, after i'm done with bigpup instruction. It needs concentration and focus, since i'm a beginner.

@bigpup

Make sure you booted with no Fossapup64 9.5 USB drive plugged in? Yes, no usb plugged in.

What boot loader did you install? both.
Where did you actually put the Fossapup64 files? sda2
Hopefully you made a directory(folder) to put them in. What did you name it? Fossapup 9.5

I need to see what is in the boot menu config file.

grub.cfg for the UEFI boot loader.
#
set default=0
set timeout=5

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

if [ $grub_platform = 'efi' ]; then
loadfont /boot/grub/fonts/DejaVuSansMono18.pf2
set gfxmode=auto
terminal_output gfxterm
fi

menuentry "Puppy Fossapup" {
insmod squashfs
search --no-floppy --fs-uuid --set C449-8570
echo "Loading vmlinuz"
linux /mnt/sda2/vmlinuz pmedia=usbhd pdrv=MULTIBOOT psubdir=/mnt/sda2 pfix=fsck,fsckp TZ=WIB-7
echo "Loading initrd.gz"
initrd /mnt/sda2/initrd.gz
}
menuentry "Puppy fossapup64 9.5" {
insmod squashfs
search --no-floppy --fs-uuid --set C449-8570
echo "Loading vmlinuz"
linux /vmlinuz pmedia=usbhd pdrv=MULTIBOOT pfix=fsck,fsckp TZ=WIB-7
echo "Loading initrd.gz"
initrd /initrd.gz
}
if [ $grub_platform = 'efi' ]; then
menuentry 'System BIOS setup' {
fwsetup
}
fi
menuentry "Shutdown computer" {
halt
}
menuentry "Reboot computer" {
reboot
}

menu.lst for the legacy boot loader

timeout 0
default 0

title grub2
kernel /boot/grub/i386-pc/core.img

Also would help if I could see what Fossapup64 files actually got installed on the drive.

You seem to have Fossapup64 installed correctly.

Something did not work correctly when you installed the boot loader.
Those grub.cfg entries are not correct.

This is the main issue. The uuid is a specific identification of the drive.

search --no-floppy --fs-uuid --set C449-8570

That uuid should be much different.
Something like this:
search --no-floppy --fs-uuid --set 3bf3fb39-e2cc-410b-80dc-1379eba590fa
This uuid identifies my specific drive.
Yours will be different uuid.

I assume you tried using both of the menu entries?

I have done many installs using Frugalpup Installer and had no boot problems.

The version of Frugalpup Installer (V20) in Fossapup64, is the first version, and a lot of improvements and tweaking have been done to it.
It is now V35.
viewtopic.php?f=105&t=337
So try using the newest version of Frugalpup Installer.

Boot using Fossapup64 9.5 USB.
Download and install the latest Frugalpup Installer pet package.
https://www.mediafire.com/file/d87f4o6d ... 5.pet/file
(to install a pet package. Download to location you can find it. Navigate to that location. Left click on it to install.)

Now with the newer version of Frugalpup Installer.
Run Frugalpup Installer.
Make sure it shows as v35.
Do the install again of the boot loader install.
When asked. Make sure you are identifying the correct partition, on internal drive, as location of Fossapup64 and where to place boot loader.
Shutdown computer.
Remove the Fossapup64 USB and all USB drives, so no USB drives are plugged in.
Startup and boot now using the internal drive.

What now happens?

I assume you tried using both of the menu entries?
What is this menu entry?

I've installed the frugalpup v35, and reinstall the boot loader. This is the screenshot:

location of Fossapup64

where to place boot loader

Shutdown, Remove the Fossapup64 USB and all USB drives, no USB drives are plugged in

When i startup and boot, previously there was fossapup boot menu, now its gone. There are only 3 options: system bios setup, shutdown, reboot. I click system bios and the screen is like this:

Frugalpup Installer is a good program, but it is easy to not select the correct input information.

I think this is what is not correct.
This screen selecting location of the Fossapup install.
.

.
Where it says initrd/mnt/dev-save/Fossapup9.5

The location should be mnt/sda2
Just identify the partition you do not need to indicate the exact directory.
I think you are actually indicating what is on the USB.
I know, this windows info is a little confusing.
The info is just examples, not what you have to have showing.

Back to beginning of installing the boot loader.

Sorry, I have to use your images, so I have to circle what is wrong and tell you what should be there.

When you get to this selection window.
.

.
Select sda2
.
The next window (Select the directory containing puppy frugal installs) should open with mnt/sda2 here:
That is all that should be in the red circled selection input.
That is all that is needed.
Click OK to proceed.
.

.
This should make the correct boot loader menu on sda1

If you are not getting what I show should be in the selection windows.

I have seen some computers that are booted from a Fossapup USB.
Identify and show the USB as sda.
The internal drive is identified as sdb

So, make sure this is not what is happening to you.

If none of this helps you.

Try using this boot loader to install a boot loader on the internal drive.
viewtopic.php?p=29703#p29703

Hi @bigpup

Thx for taking the extra miles. Using my images and showing what should be there is exactly what i need, actually.

I boot from live usb and use the save session and couldn't select mnt/sda2 as the source of frugalpup installer, instead when i choose sda2 it says: initrd/mnt/dev-save/Fossapup9.5. I sent you personal email, since the attachment won't allow more than 512Kb, to show that process.

However, i managed to boot "fossapup no save" from the live usb boot menu and successfully choose mnt/sda2 as the source of fossapup install, and re-wrote the boot loader in sda1 with frugalpup installer. Still, the boot menu from internal HDD shows the same result.

Next, will try the Grub2config, although i'm not sure since it mention this:
Only one case the Grub2config does not support:
If you clean install Ubuntu Linux on a legacy BIOS PC, the partition sda1 is ext4 formatted, does not support Grub2config nor FrugalPup.
In this case, you can install Puppy manually or using the Universal installer on a live Puppy.
And then make a text file /boot/grub/custom.cfg describes menu entry shown in the next post.
The file /boot/grub/custom.cfg persists as is even the grub updated.

This was what i've done with the laptop, and messed up the boot loader. You can see from one of my attachment picture, Bios showing two 'ubuntu' option to boot in boot priority order.

Now I am confused.

Do you want to only have Fossapup64 on the internal drive?
Do you want to have both Ubuntu and Fossapup64 on the internal drive? A Duel boot setup?

I have been trying to get you setup with only Fossapup64 on the internal drive.

What exactly you are trying to do affects how you do it.

So, what is the answer to what you want on the internal drive?

I boot from live usb and use the save session and couldn't select mnt/sda2 as the source of frugalpup installer, instead when i choose sda2 it says: initrd/mnt/dev-save/Fossapup9.5.

I see in one of the images you posted, the fossapup64save is on sda2 and not on the Fossapup64 USB.
That could be why it is giving this: initrd/mnt/dev-save/Fossapup9.5.
That is why Rox file manager is identifying sda2 as /mnt/home
to a running Fossapup64.
The location of the save it is using is /mnt/home
.

.
.

The fossapup64save, used by the booted Fossapup64 USB, really needs to be on the USB, with the other Fossapup64 files.
Let me guess.
When you made the save, the internal drive was only place offered to put the save.
That is another issue, when you use a non Puppy Linux installer to put Puppy on a USB drive.
The boot menu entries config file, needs to be modified to make the pmedia=cd changed to pmedia=usbflash.

Did you use Gparted program, in the booted running Fossapup64 USB install, to make the partitions, on the internal drive sda?

Did Ubuntu ever make partitions on this drive?

I am still not seeing why the boot loader install procedure, is not making a working boot loader menu.
Something is wrong, but just not seeing what it is, yet!

Do you want to only have Fossapup64 on the internal drive?

Yes

Do you want to have both Ubuntu and Fossapup64 on the internal drive? A Duel boot setup?

No. I'm just trying to give you as much info as i can, to explained what has been done in the past to the laptop boot menu. As i mentioned in the first post, i've been trying to install various light linux distros, lubuntu, zorin, etc. That is why i post you this image.

You can see there is record of ubuntu boot priority order, although the installation has been wiped out, when i made the partition table for fossapup installation.
Could it damaged the boot or HDD in some way because of my several fail attempts to install various linux?

I see in one of the images you posted, the fossapup64save is on sda2 and not on the Fossapup64 USB.
That could be why it is giving this: initrd/mnt/dev-save/Fossapup9.5.
That is why Rox file manager is identifying sda2 as /mnt/home to a running Fossapup64. The location of the save it is using is /mnt/home

So, in relation with above post, am i correct to locate the frugalpup folder? initrd/mnt/dev-save/Fossapup9.5

The boot menu entries config file, needs to be modified to make the pmedia=cd changed to pmedia=usbflash.

How to do this? and what is the purpose?

Did you use Gparted program, in the booted running Fossapup64 USB install, to make the partitions, on the internal drive sda?

Yes

Did Ubuntu ever make partitions on this drive?

Yes, with Gparted from live USB install of various light distros i.e. Lubuntu, Zorin, Linux Mint.

So, in relation with above post, am i correct to locate the frugalpup folder? initrd/mnt/dev-save/Fossapup9.5

Yes if that is what Rox file manager is identifying sda2 as.
Better to click on the lower left of desktop, icon for sda2, to make sure that is what you are seeing.

The Fossapup 9.5 directory(folder) on sda2 partition of the internal drive.
That is a frugal install with all the Fossapup64 9.5 files in fossapup 9.5 directory you made.

The boot menu entries config file, needs to be modified to make the pmedia=cd changed to pmedia=usbflash.

How to do this? and what is the purpose?

Forget that right now.
That is just tweaking the USB drive install.

The problem is getting the correct setup of a boot loader, with correct boot menu entries to boot the internal drive install.

I am wondering if something got messed up with the MBR on the drive.

Booted with the Fossapup64 USB.
If you still have the fossapupsave on the internal drive.
You will have to boot not using the save.
The next procedure will delete everything from the internal drive.

Time to start over fresh with everything.

Run Gparted program and setup the internal drive with a fresh new setup.
Make sure you are selecting the internal drive to work on!!!!!
Geparted->Device->Create a Partition Table (msdos)
Now make the two partitions as before.
Now run Frugalpup Installer.
Install Fossapup as before to sda2.
Installing boot loader.
Let's try only one specific boot loader at a time.
Choose to install the UEFI one.

Do a test boot and see how that works.

If not working.
Try just installing the MBR one.

Finally, it works man!

I intend to post the summary in graphics, with the screenshoot i made. Unfortunately, when asked to save, i chose not to save. Alas, i can not post it here. But i remember the steps, which as follows:

1. Make new partition MSDOS
2. Set partition 1 (sda1), 512MB, type fat32, flaged as boot
3. Set partition 2 (sda2), [whatever size your disk have], Type Ext4, for the frugall instalation
4. Make remaining partition, as Swap, equivalent to your RAM size
5. Do Frugal install of fossa, to partition 2 (sda2). Yes, this time there was sda2 with numerics like more than 16 digits.
6. Install the boot loader to sda1, choose only UEFI.
7. Exit, Boot from Internal HDD, You are in fossapup.

Now, i'm testing the hardware functionality. If all goes well, will post it.
My early detection is that the wifi is so slow. Using the same network, what could have been around 3Mbps download speed, now is only a tenth of it.
Going to update the fossapup first.

Good to finally see it is working OK

Sometimes I think computers will just mess with you, until just before the time you want to throw it, out a window.
Then it suddenly just works

I think maybe redoing the partition table, corrected what was wrong with the drive.

If you have any other issues or questions.
Start a new topic for them.

If the problem is solved.
We ask that you edit the subject of the first post and add solved to the end.
The subject of the first post is the subject tittle of the topic.