Have an issue with NVIDIA graphics card because of which ...

[rajibando]

It feels strange to use Puppy Forums as a beginner.

I have been using Puppy for 6 years, not regularly, but on and off.

As posted on various forums, NVIDIA board for my laptop causes a great deal of issues. But when the drivers are installed downloaded from nvidia website, the laptop works as a dream laptop even now.

Unfortunately, can't have the laptop upgraded to the latest Debian, Ubuntu, Arch(won't proceed forward as installation is largely CLI based) and even Puppy now.

It is really strange that Debian GUI installation could be used for a new HDD, but after installation, no GUI can't be invoked in the FB mode, so that drivers could be searched from NVidia and installed from the GUI.

Please note that my HCL laptop doesn't require a Lightweight system like Lubuntu. It is quite robust to handle heavyweight operations still. Just that the motherboard audio and video chips are its Achilles heels.

I have a question:
Why do Linux people assume that Doze people shall migrate from Doze and be happy with the numerous choices that Linux distros offer?

Even Puppy people do, which is why it has created an installation which makes it impossible to install on my said system with puppy iso flashed on to one of my flash drives. When my first installation id Debian 10.8.

When loaded, it shows a strange GRUB menu with no possibility of installing the OS on a brand new HDD! Linux people still stick to Doze. Doze people won't migrate, and that is for a different reason altogether. Won't go into that terrain presently.

Could a puppy iso be found that could be straightaway copied to the new HDD and booted via loopback loop code using grub on my Nvidia system please?

Or on a flashdrive where the ISO is copied with native linux dd?

Any distro that uses fb as default and runs from there? I am a dedicated Debian, Knoppix and once ubuntu, and occasionally puppy -linux user. Now I don't use ubuntu that often.

Any inputs please?

[bigpup]

Maybe this is what you want:
viewtopic.php?f=156&t=387

[foxpup]

I have a question:
Why do Linux people assume that Doze people shall migrate from Doze and be happy with the numerous choices that Linux distros offer?

These are 2 questions!
We do not assume that windows' people will migrate from windows. They do not.
Some people do not like the freedom and the hence choices to make, but we do.

Could a puppy iso be found that could be straightaway copied to the new HDD and booted via loopback loop code using grub on my Nvidia system please?

2 questions again!
For the loopback @bigpup gave you an answer. Not all Puppy isos can be loopbacked.
But the proprietary Nvidia driver will not come with the iso. It has to be installed, or even compiled.
Another driver (modesetting?) will do the job as good as it can at first though.

You do realise that a loopback iso is not a proper install? You are very limited like that.
The proper install for Puppy is a 'frugal' install.

Wellcome to the kennels @rajibando !

[rajibando]

Maybe this is what you want:
viewtopic.php?f=156&t=387

Too good to be true!
Noted:

Steps for USB sticks
Download a SuperGRUB2 ISO
Burn the ISO to USB
Boot the PC, selecting the USB as the boot device
Hit the Enter key when SuperGRUB2 opens
Wait...wait...for the screen output’s menu with your ISOs listed
Scroll to the bottom of the screen output’s menu
Select an ISO
Your selection will boot

Thank you for your support.

[rajibando]

... We do not assume that windows' people will migrate from windows. They do not.
Some people do not like the freedom and the hence choices to make, but we do ...

Would rather ignore the others.

...
For the loopback @bigpup gave you an answer. Not all Puppy isos can be loopbacked.
But the proprietary Nvidia driver will not come with the iso. It has to be installed, or even compiled.
Another driver (modesetting?) will do the job as good as it can at first though ...

No, puppy didn't require an nvidia driver, as it ran in fb mode. Debian is continually complicating things. I think I shall also try RMS's GNUL.

...
You do realise that a loopback iso is not a proper install? You are very limited like that ...

Yes, of course. But I am starving for some time and am ematiated. Need food at first. Then could dream about gourmet meals.

...
The proper install for Puppy is a 'frugal' install ...

My grub-line on puppy was:

menuentry "Puppy Linux - The Power of Linux!!!" {
linux (hd0,1)/puppy/vmlinuz
echo 3
initrd (hd0,1)/puppy/initrd.gz
}

Ran quite well that way. No fuss. Clean.

But yes, please guide me on this. I tried with the flashed USB but have already informed the forum on the effect. Please look at the pic here.

The tragedy of grub line

puppy.jpeg (82.18 KiB) Viewed 1133 times

[/size][/url]

...
Wellcome to the kennels @rajibando ! ...

Thank you, The pleasure should be mine alone.

Problem with installation of fossapup64-9.5

Now, I checked info regarding Frugal Intall here. and on the page index. Also other pages like FAQ. Presently searching for a HowTo page on Frugal Install. I have found an install page, but not HowTo. Also, since I don't use Doze, I don't have the facility for a Doze dd program.

But on the Install page at the area,

... Here is a simple tutorial on using dd to make a bootable USB drive. Be very careful with your target drive name!....

there is a link that leads to a tutorial on dd. I had done exactly like that, but I had a USB pen-drive with a Grub, a snapshot of which is posted above. Totally useless, it appears. So, this is a Catch22 situation. I had downloaded the fossapup64-9.5.iso.

[foxpup]

I have a ton of questions.

The snapshot shows it tries to boot with grub4dos (not grub). That is a legacy BIOS boot, not UEFI.
Do you indeed use legacy boot?

I understand you have debian installed on the HDD.
If so, you could install Puppy next to debian and add Puppy to the boot system from debian.
Like this (read it untill the end):
How to add Puppy to grub2 with Windows 10 and Manjaro?
It also includes howto frugal install.
It is not necessary to do it from a running Puppy, you can do it from debian as well.

The menuentry you posted is for grub (not grub4dos) and it looks like an entry for a frugal install (!) of Puppy.
How do you have this working?

And what is the matter with the nvidia and upgrading debian?
Is your nvidia card to old for newer kernels maybe?

By the way.
Most linux users use the CLI/terminal a lot.
It is not difficult, on the contrary, just have to get used to it.
Debian does have gui's for apt though, synaptic and gdebi iirc.

[rajibando]

I have a ton of questions.

It is good for me that you have. ... Now we are really talking.

I shall take a part of your Post to have you solve my issue. I shall post answers to your rest queries later, when I reach there.

The snapshot shows it tries to boot with grub4dos (not grub). That is a legacy BIOS boot, not UEFI.
Do you indeed use legacy boot?

I shall tell you what I did.

I downloaded the fossa puppy iso and dd -ed to an USB pendrive. When I used the pendrive to boot the system, this was the Grub I was led to.

That is because I use the legacy option in BIOS. ... But using the same BIOS I used Knoppix and the latest Debian Live Installation ISO USB Pen drives to install those systems.

The laptop in question is old. NO VEFI. Only PXE Boot available. I wrote to PhoenixBios. They have a doze BIOS flash exe file. But I don't have Doze in my system.

I shall address your other questions later.

Presently, we are to overcome BIOS restrictions, and then boot puppy from there.

[bigpup]

That dd command you used is probably not correct for Fossapup install.

Try doing the install to USB using one of these installers:
viewtopic.php?f=156&t=157

Read the info on maybe having to edit the boot loader config file.
the pmedia= command in the menu entry.

[foxpup]

That is because I use the legacy option in BIOS. ... But using the same BIOS I used Knoppix and the latest Debian Live Installation ISO USB Pen drives to install those systems.

The laptop in question is old. NO VEFI. Only PXE Boot available. I wrote to PhoenixBios. They have a doze BIOS flash exe file. But I don't have Doze in my system.

I shall address your other questions later.

Presently, we are to overcome BIOS restrictions, and then boot puppy from there.

Do not flash your BIOS. It is a sensitive thing to do and there is no need to.
Old legacy BIOS is good as is if it boots Debian Live.
You do not use PXE Boot, do you?

That dd command you used is probably not correct for Fossapup install.

I have tried dd and I boot fine from both a legacy and an EFI machine.

Something I have had trouble with in the past, is multiple usb devices connected on boot.
There even can be mess up between bootloaders on HDD and usb.

The line

Code: Select all

find /menu.lst, /boot/grub/menu.lst, /grub/menu.lst

is a bit of a mystery to me.
I know that this search is done for grub.cfg from within grub2 binaries. But I have never seen it for grub4dos like this.
And it looks like it does not find menu.lst.

Good idea to try another installer.
Another idea, try dd with bionicpup, tahrpup or slacko. They have slightly different boot installations.
Once you have a running Puppy, it will all be much easier to install others.
@PipzDex explains well a few post lower in the link from @bigpup

[rajibando]

Please excuse my leapfrogging.

...
Read the info on maybe having to edit the boot loader config file.
the pmedia= command in the menu entry ...

I thank you for replying to my post once more. You are a very learned senior. Unfortunately, i am only a user by choice. So my first question to your suggestion is: Why?

... That dd command you used is probably not correct for Fossapup install.
Try doing the install to USB using one of these installers:
viewtopic.php?f=156&t=157 ...

Also, once again, why?

Please note that my competence might not be sufficient to comprehend the long post. A summary would have been helpful. Could one of your juniors compile the entire post into a simple one paragraph summary..

I assure you that I shall definitely follow your directive, but I would require time.

[rockedge]

@rajibando for some reason I am suspicious of your motives.

Your posts are confusing as to what your intent is. Loopback? Now that is a "WHY?" in my book.

What are you trying to achieve exactly? Puppy on a USB drive?

[rajibando]

Thank you for posting to help once more.

... You do not use PXE Boot, do you? ...

No, as I didn't need to. I am not a software professional. I am just an inquisitive user. Just wanted to be free from these Proprietary-Proprietary or Secret-Secret zero-sum games. I would have rather had all companies use standard stacked add-on cards rather than a single motherboards. Would have encouraged competitions more. A small box with batteries, with screen through wire/wireless.

But our rationality is just a thin veneer. What we are within is what is projected outside. I fear if these zero-sum games might destroy humanity.

... I have tried dd and I boot fine from both a legacy and an EFI machine. ...

Yes, as I have said, the USB drive installer booted up fine from a VEFI machine and I had a puppy running on RAM.

...The line

Code: Select all

find /menu.lst, /boot/grub/menu.lst, /grub/menu.lst

is a bit of a mystery to me.
I know that this search is done for grub.cfg from within grub2 binaries. But I have never seen it for grub4dos like this.
And it looks like it does not find menu.lst. ...

Yes, to me it looks like an if, elif, else trap.

It is strange! When there is so much freedom for a chain to form from Debian to Ubuntu to Puppy, why not another modified puppy? Or a BIOS to VEFI conversion tool?

... Once you have a running Puppy, it will all be much easier to install others ...

Yes, you appear to be speaking reasonably.

... @PipzDex explains well a few post lower in the link from @bigpup ...

Yes, but I shall take time to process the info.

[rajibando]

@rajibando for some reason I am suspicious of your motives.

You could have PM-ed me. You are the lord of this universe, so none is beyond your reach !
Humour aside, you are free to check my internet footprint, in knoppix as rajibando and in debian and ubuntu as bkpsus..., i.e., gmail username. To know that I have never abused or used slang ever for anyone, but tried to help with ideas. That's a virtue, isn't that?!

Your posts are confusing as to what your intent is. Loopback? Now that is a "WHY?" in my book.

My first intent is to have a running system on a new HDD bought for the purpose, on a laptop with problematic NVIDIA card. The current driver downloaded from nvidia didn't work in latest Debian. Only a Knoppix 8.2 with nvidia on UsB stick that works. So I don't have a running system now on the laptop's new HDD. Nouveau driver doesn't work for this laptop. FB (e.g., vga=843) is deprecated. I need a new system on an old computer that works very well. My experience with old puppy was good, as it apparently used fb and didn't need drivers.

All other ever-growing complex systems have apparently rejected framebuffer, the poor man's graphics.

What are you trying to achieve exactly? Puppy on a USB drive?

No, to use the USB drive to have a running GUI OS first on new HDD. Which I don't presently have on the said HCL Me laptop. I assumed puppy would be a good choice, based on my past experience.

I am also presently downloading latest Knoppix 9.1 as Knoppix has been my main OS for all work for long, since 2007. Even before I came to debian.

BTW, because of a working Lenovo laptop, I am still functional on the internet and my other work.

[foxpup]

... I have tried dd and I boot fine from both a legacy and an EFI machine. ...

Yes, as I have said, the USB drive installer booted up fine from a VEFI machine and I had a puppy running on RAM.

It is UEFI or EFI, not VEFI.
That means you have Puppy running on another machine, a EFI machine?
Then you can just use frugalpup from that running Puppy to make another usb.
And that usb should work on your laptop. From this you could use frugalpup again to install to the HDD now.

By the way. A big part of the regular Puppy users do a manual frugal install (from a running Puppy), no install scripts involved and super fast.
The routine of @PipzDex is a good example.
viewtopic.php?p=7067#p7067

[foxpup]

It is strange! When there is so much freedom for a chain to form from Debian to Ubuntu to Puppy, why not another modified puppy? Or a BIOS to VEFI conversion tool?

Not sure I understand you.
Puppy just uses the packages, the compiled programs, from this big distros, to win time.
Typically there are Puppys from Slackware and from Debian/Ubuntu.
But others are possible.
The early Puppys were completely made from Puppy's very own packages, compiled for Puppy by Puppy devs.
Nowadays @BarryK , inventor of Puppy, is about the only one who makes a complete distro from 'home compiled' packages.
He does this for his EasyOS project, that still has a lot in common with Puppy.
Puppy is a Puppyland, not a single distro.

Converting BIOS into EFI is not possible. It is in the hardware of the machine. It is a totally other thing.
But most EFI machines however have the possibility to turn on old legacy boot support (CSM). But that may change in the future
And you can have bootloaders for both systems installed next to each other.
Actually I do not think a distro should have to provide the bootloader(s).

[rajibando]

... That means you have Puppy running on another machine, a EFI machine? ...

Yes, i had mentioned it earlier. But lost in the word jungle.

... Then you can just use frugalpup from that running Puppy to make another usb ...

Frugal install on my Lenovo? I had posted my query on the post here: ... Presently searching for a HowTo page on Frugal Install. I have found an install page, but not HowTo. Also, since I don't use Doze, I don't have the facility for a Doze dd program .... But again, lost in wilderness. Word jungle.

... And that usb should work on your laptop. From this you could use frugalpup again to install to the HDD now. ...

Yes, it appears that we are reaching towards a solution. Thank you for staying with me.
And thanks for

... It is UEFI or EFI, not VEFI. ...

[foxpup]

Could you give the specs of your nvidia card?
I would like to understand what the problem is there.

[rajibando]

Thank you. Again.

... But most EFI machines however have the possibility to turn on old legacy boot support (CSM). But that may change in the future
And you can have bootloaders for both systems installed next to each other.
Actually I do not think a distro should have to provide the bootloader(s). ...

I was thinking in terms of Distros helping BIOS to have a feel of UEFI. But my comment may presently be ignored.

... Could you give the specs of your nvidia card?
I would like to understand what the problem is there. ...

Wny only the nvidia card? Please have everything here:
The details of the laptop is here: http://bit.ly/HCL_Pen2Core
Please note that the last updated version in nvidia website installs in the latest debian, but stalls at init 5. I have three older versions, one of which works for Knoppix luckily. Nouveau fails.

[foxpup]

Wny only the nvidia card, Please have everything here:
The details of the laptop is here: http://bit.ly/HCL_Pen2Core
Please note that the last updated version in nvidia website installs in the latest debian, but stalls at init 5. I have three older versions, one of which works for Knoppix luckily. Nouveau fails.

I am not familiar with init/runlevels.
You do install from debian and not from nvidia?
You need 340 and 340 is legacy for nvidia and needs patches with newer kernels.
Maybe you should not upgrade to newer kernels.
For older machines newer kernels are not that important anymore, I guess.

[rajibando]

... I am not familiar with init/runlevels ...

How come? Those are basic linux commands. 1,2,3,4,5 and 6.

... You do install from debian and not from nvidia? ...

Didn't understand. Could you please elaborate?

... You need 340 and 340 is legacy for nvidia and needs patches with newer kernels.
Maybe you should not upgrade to newer kernels.
For older machines newer kernels are not that important anymore, I guess.

Yes, I too am beginning to think along these lines. But I shall try once with the latest Knoppix. And Puppy as it uses framebuffer. Which others have discarded.

[foxpup]

... I am not familiar with init/runlevels ...

How come? Those are basic linux commands. 1,2,3,4,5 and 6.

Puppy has busybox as init and that does not use runlevels. Not so basic after all. Isn't it more a tool for admins and servers also?

... You do install from debian and not from nvidia? ...

Didn't understand. Could you please elaborate?

I mean, you use the packages from the debian repos (with apt, synaptic, gdebi)? You do not download and run the .run file from the invidia site?

[foxpup]

But I shall try once with the latest Knoppix. And Puppy as it uses framebuffer. Which others have discarded.

If you want Puppy next to another linux, you better first install the other linux and add Puppy to its boot loader.
Like in How to add Puppy to grub2 with Windows 10 and Manjaro?

I have used Knoppix a long time ago. It is very nice.
The live install with persistence uses layering and is similar to Puppy in that way.
... and debian live ... and Slackware live ...

I think you better use your nvidia card than the framebuffer if you can.
Puppy does not update/upgrade and in Fossapup nvidia 340 driver is available through Quickpet.

Let us know how you get along.

[bigpup]

Nvidia graphics drivers have to be compiled for the specific Linux kernel, that is in the operating system.
They are kernel specific.
You can not use a driver compiled for some other operating system.
That is why Nvidia only offers their driver packages in a run package.
It is all the stuff needed to compile the driver, for whatever operating system, and Linux kernel in it.

Other problem is support for some older hardware is being dropped from newer Nvidia drivers.
Depending on the hardware and age, will determine what driver, will support it.
Here is info for getting the correct driver installed:
viewtopic.php?f=97&t=123

Some Puppy versions have Nvidia driver pet packages already made for some Nvidia drivers.
So installing that pet package, installs that driver.
But they are usually the drivers, that supports what hardware was around, when the Puppy version was developed.
Not every possible Nvidia hardware.
Have to see what specific hardware the specific driver will support.
Nvidia web site can give you that info for each specific driver.

This is why, Puppy is released with the generic Nouveau driver, that generally supports all Nvidia hardware, with basic features, all hardware has.
As a fall-back, the Vesa driver, that all graphics hardware can use.

Why does the pmedia= command in the boot loader menu entry matter.
It tells the boot processes, what device the install is on, and where to look for the Puppy files.
pmedia=cd (installed on CD)
pmedia=usbflash (installed on a usb flash drive)
pmedia=atahd (installed on a internal hard drive)
etc.....
Puppy iso packages are setup as an iso image to burn to a CD/DVD
The boot loader config files have pmedia=cd
So if you install to a usbflash
change pmedia=cd to pmedia=usbflash.
That says look on the usb drive for the files needed to boot.

When you install using dd commands.
It is just coping the files to the USB drive.
The boot loaders are still setup for booting from a CD.

Installer programs in Puppy Linux, are designed for installing Puppy Linux, and know about making these changes to the boot loader.

[mikewalsh]

That is because I use the legacy option in BIOS. ... But using the same BIOS I used Knoppix and the latest Debian Live Installation ISO USB Pen drives to install those systems.

The laptop in question is old. NO VEFI. Only PXE Boot available. I wrote to PhoenixBios. They have a doze BIOS flash exe file. But I don't have Doze in my system.

I shall address your other questions later.

Presently, we are to overcome BIOS restrictions, and then boot puppy from there.

Do not flash your BIOS. It is a sensitive thing to do and there is no need to.
Old legacy BIOS is good as is if it boots Debian Live.

~~~~~~~~~

Purely as a matter of interest, it IS perfectly possible to "flash" your BIOS, under Linux. As a matter of record, I reflashed the MBR BIOS of a 10-yr old Compaq desktop, in Puppy itself, around 6 years ago, with the invaluable assistance of one of our members on the old Murga-Linux forum. We used the "flashrom" utility, which in that instance we obtained from the Arch Linux repos.....and the instructions for using said utility from the Arch Linux Wiki, one of THE best sources available for Linux information of just about any sort there is.

BUT:-

Foxpup has hit the nail on the head. BIOS 'upgrading' - especially when running Linux - should never be undertaken lightly. You don't perform such just "for the sake of it"; in my case, it was to support the upgrade of an older single-core Athlon64 CPU to a dual-core Athlon64 X2, and the re-flash was necessary. But you should only do so if you are 110% certain of the procedure.....it's all too easy to "brick" your machine, and THEN you'll not be running anything on it!

You can (if interested) read the entire saga here:-

https://oldforum.puppylinux.com/viewtop ... =3&t=98295

Think carefully about this. Weigh the pros & cons, and whatever you do, DON'T "rush in where angels fear to tread". It's not for the faint-hearted, but the gains can be worthwhile under the right circumstances.....i.e., where it's actually necessary.

Mike.

[rajibando]

Thank you, foxpup, mikewalsh and bigpup, for your posts.

... Puppy has busybox as init and that does not use runlevels. Not so basic after all. Isn't it more a tool for admins and servers also? ...

GNU-Linux is modular packages,... servers... Runlevels aren't commands. Each of them are certain state of the system. init is the command used. Let's ignore.

... I mean, you use the packages from the debian repos (with apt, synaptic, gdebi)? You do not download and run the .run file from the invidia site? ....

Of course I use packages from debian. Only the graphics card require specific drivers from nvidia.

...
If you want Puppy next to another linux, you better first install the other linux and add Puppy to its boot loader. ...

Not necessarily. I would also have liked the other linux to be beside puppy, but puppy isn't allowing that. Just like I use Knoppix as my main system.

... Puppy does not update/upgrade ...

I wasn't talking about installing nvidia 340 in puppy. The vesa in puppy is sufficient for the purpose.

... in Fossapup nvidia 340 driver is available through Quickpet. ...

Is it true? Want to know about this.

...
Let us know how you get along. ...

Yes, of course.

...
That is why Nvidia only offers their driver packages in a run package.
It is all the stuff needed to compile the driver, for whatever operating system, and Linux kernel in it. ...

Yes, this is nothing new. For the last 12 years I have been running the scripts, which requires gcc to compile.

...
As a fall-back, the Vesa driver, that all graphics hardware can use. ...

...
Puppy iso packages are setup as an iso image to burn to a CD/DVD ...

Won't enter into a discussion on this. I have to make a system operational. Puppy itself recommends dd.

...
Do not flash your BIOS. It is a sensitive thing to do and there is no need to. ...

Of course not, until I hear from PhoenixBIOS.

... You can (if interested) read the entire saga here:-

https://oldforum.puppylinux.com/viewtop ... =3&t=98295

Think carefully about this. Weigh the pros & cons, and whatever you do, DON'T "rush in where angels fear to tread". ...

Surely will do, but have to make a system operational first.

Please inform me about a puppy flavour that shall suit my PhoenixBIOS, system bios version H2.06E, KBC bios version R1.04

[bigpup]

Puppy iso packages are setup as an iso image to burn to a CD/DVD ...

Won't enter into a discussion on this. I have to make a system operational. Puppy itself recommends dd.

OK do not believe what I am telling you.

dd command does not setup the boot loader for booting from a USB, it only puts what is in the iso on the USB.

How Puppy searches for files, when it boots, has changed over the years, and that dd command knows nothing about adjusting the boot loader, to make it now work on all possible drives.

updating Puppy Linux documentation is the last thing that ever gets done, if at all.

[foxpup]

Of course I use packages from debian. Only the graphics card require specific drivers from nvidia.
....
Yes, this is nothing new. For the last 12 years I have been running the scripts, which requires gcc to compile.

What I mean is: "Don't run these .run scripts from nvidia."
If you use new kernels the .run packages from nvidia for old (legacy) drivers are not ready.
You have to install the driver through a package manager from your distro (apt/synaptic/gdebi for debian, quickpet for Fossapup) from the repos of your distro.
(Quickpet is in the menu under Setup.)
Distro (Debian/Puppy) devs have patched, forged and compiled the .run package from nvidia into a package that works with the kernel/Xorg from the distro.
Use the nvidia site only to get information on what driver you need, 340 in your case.
Unless you want to patch, forge, compile yourself.

I would also have liked the other linux to be beside puppy, but puppy isn't allowing that. Just like I use Knoppix as my main system.

Why do you say that?
Puppy lives peacefully next to Windows, Knoppix, Debian, any unix/BSD/linux/OS on the desktop.
Just give Puppy its basket, that is a frugal install.

[mikewalsh]

Puppy iso packages are setup as an iso image to burn to a CD/DVD ...

Won't enter into a discussion on this. I have to make a system operational. Puppy itself recommends dd.

OK do not believe what I am telling you.

dd command does not setup the boot loader for booting from a USB, it only puts what is in the iso on the USB.

How Puppy searches for files, when it boots, has changed over the years, and that dd command knows nothing about adjusting the boot loader, to make it now work on all possible drives.

updating Puppy Linux documentation is the last thing that ever gets done, if at all.

@bigpup :-

Some people will argue black is white, just for the sake of it.....even when they know the opposite to be true. I daresay you're aware of this as well as I am, mate.....it's one of the more perverse aspects of human nature!

They DO learn otherwise.....eventually. Though it won't be at my expense....doesn't take many posts to figure out who the "time-wasters" are.

I won't be posting further in this topic.

Mike.

[rajibando]

Thank you once more, foxpup, bigpup and mikewalsh for posting to this thread once more.

... What I mean is: "Don't run these .run scripts from nvidia."
If you use new kernels the .run packages from nvidia for old (legacy) drivers are not ready.
You have to install the driver through a package manager from your distro (apt/synaptic/gdebi for debian, quickpet for Fossapup) from the repos of your distro.
(Quickpet is in the menu under Setup.)
Distro (Debian/Puppy) devs have patched, forged and compiled the .run package from nvidia into a package that works with the kernel/Xorg from the distro.
Use the nvidia site only to get information on what driver you need, 340 in your case. ... Just give Puppy its basket, that is a frugal install. ...

I fully understand what you say, but never has debian's native nvidia pkg ever worked for nvidia.

Please also note that i have not yet been directed to, or taught (it is not in the mentioned page even), how to frugal install. I could refer to the exact line, but the BB code is very limited for referencing a phrase, a sentence or a paragraph.

... I won't be posting further in this topic. ...

I shall respect your decision.

Clearly, Mr. Walsh is offended. He is to appreciate that I can't accept without any declared evidence. Can;t just accept word of mouth as documentation. None is to be offended by this choice. If puppy isn't documenting well, leaders should look into this aspect.
May be, there could be just one linear distro, frozen in every 6 month or so, if contributors are limited.

May please this reference be checked: 0001_Ref_2021-04-16 Puppy Linux Installation and Usage.png

I would avoid posting until the matter has cooled down enough.

... OK do not believe what I am telling you. [...] dd command does not setup the boot loader for booting from a USB, it only puts what is in the iso on the USB [...] updating Puppy Linux documentation is the last thing that ever gets done, if at all.

If:
Puppy pages mention on the first line on dd and then a little later, on frugal install, but isn't found to be explaining how to frugal install,

Then:
Why isn't the board pursued to update puppy pages?

[bigpup]

Then:
Why isn't the board pursued to update puppy pages?

You want to volunteer to do that update to documentation?
That is the problem.
Someone has to volunteer to do it and have access to the locations it is posted.
Very few people like to do documentation and have the time to work on it.
It is what it is!

All of us have other jobs and a life, that is not working on Puppy Linux.