Puppy Linux Discussion Forum

NEWS 201126 ABOUT Nvidia
Today I've discovered that Nvidia’s Proprietary Graphics Driver can be installed in PuppEX Build 201121 after all! Not version 450.80.02, but version 455.45.01. Watch this screenshot. Read this Article about the Open-Source NVIDIA/Nouveau vs NVIDIA Proprietary Driver. Install the Driver like this:
1. Download the driver to /root
2. chmod 755 NVIDIA-Linux-x86_64-455.45.01.run
3. Insert this file in the folder /etc/modprobe.d
4. Reboot your computer
5. Logout to Console Mode (leave X)
6. Run the command ./NVIDIA-Linux-x86_64-455.45.01.run

ABOUT PuppEX Focal64 Build 201121
A new PuppEX Focal64 version with kernel 5.9.9 (latest) is ready today. Unfortunately it does not have Nvidia’s Proprietary Graphics driver 450.80.02 installed. I could not find a patch for kernel 5.9. The good news is that the new version has the kernel sources for kernel 5.9.9. This means that VirtualBox Guest Additions can be installed by you. Which also means that you can run PuppEX in full screen in VirtualBox (among other things). Watch this screenshot. When running PuppEX Build 201121 in VirtualBox you shall first save your session. After a reboot you can install the Additions. When doing so you will get an error message saying failed to remove installed version filelist not found. Fix it by running the command rm /usr/sbin/vbox-greeter /usr/sbin/vbox-uninstall-guest-additions. Watch screenshot 1 and screenshot 2.

ABOUT PuppEX Focal Build 201119
My newest Puppy derivative is built from Puppy Linux 9.5 FossaPup64. I have added Firefox (for Netflix), Spotify, PCManFM, LXTerminal and many development tools. I have also compiled a new kernel – 5.7.19-exton. (A newer kernel than that was impossible to use. Aufs is not yet available for kernel 5.8 and 5.9). Furthermore I have installed Nvidia’s Proprietary Graphics driver 450.80.02. The Nvidia driver will be used if your computer/card is “good/modern” enough. If not automatically just open up a terminal and run the command nvidia-xconfig. Then restart X.

PuppEX Focal64 is compatible with Ubuntu 20.04 (Focal Fossa) LTS, which means that Ubuntu packages for Ubuntu 20.04 can be installed and used in PuppEX. The PuppEX Focal64 ISO is of 1320 MB respectively 1020 MB.

Performance
Puppy Fossapup64 original is of only 409 MB. PuppEX Focal64 is despite this still running as fast as the original, which means it runs very, very fast compared to most other Linux systems. (Puppy/PuppEX runs from RAM).

Study ALL installed packages in PuppEX Focal64. The same packages are installed in version 201121.

SCREENSHOTS
Screenshot of PuppEX Focal’s Desktop
Screenshot showing the live boot screen
Screenshot showing a Samba connection
Screenshot showing a WiFi connection
Your first PuppEX Focal64 Desktop after boot (if you have an Nvidia card)
PuppEX Build 201121 running in full screen i VirtualBox

READ MORE…

exton wrote: ↑Fri Nov 20, 2020 12:19 pm

a new kernel – 5.7.19-exton. (A newer kernel than that was impossible to use. aufs is not yet available for kernel 5.8 and 5.9).

Not totally impossible if you're prepared to try unofficial aufs patches....
viewtopic.php?p=7497#p7497

peebee,

Thanks! I didn't know that. Now I simply have to rebuild PuppEX and use kernel 5.9.9.

mirrored here: http://archive.org/details/Puppy_Linux_Puppex-Focal64

Very good. Thanks!

A new version with kernel 5.9.9 will be ready today.

peebee,

A new version with kernel 5.9.9 will be ready today. Unfortunately it will not have Nvidia’s Proprietary Graphics driver 450.80.02 installed. I could not find a patch for kernel 5.9.

The good news is that the new version will have VirtualBox Guest Additions installed. Which means that you can run PuppEX in full screen in VirtualBox. Watch this screenshot.

ABOUT PuppEX Focal64 Build 201121
A new PuppEX Focal64 version with kernel 5.9.9 (latest) is ready today. Unfortunately it does not have Nvidia’s Proprietary Graphics driver 450.80.02 installed. I could not find a patch for kernel 5.9. The good news is that the new version has the kernel sources for kernel 5.9.9. This means that VirtualBox Guest Additions can be installed by you. Which also means that you can run PuppEX in full screen in VirtualBox (among other things). Watch this screenshot. When running PuppEX Build 201121 in VirtualBox you shall first save your session. After a reboot you can install the Additions. When doing so you will get an error message saying failed to remove installed version filelist not found. Fix it by running the command rm /usr/sbin/vbox-greeter /usr/sbin/vbox-uninstall-guest-additions. Watch screenshot 1 and screenshot 2.

Nice

Hi @Exton

Curious:

• Are these builds via WoofCE? AND, are they including the work of @gyrog (from Puppy WoofCE GIT work with portions described here)?

• Have you tested nVidia via HDMI to a TV as a monitor? If so, is sound carried automatically to TV or requiring manual setup (MSCW)? ... and does it provide volume control via the PuppEX or is volume only controlled by the TV's remote?

Thanks for your efforts

Clarity,

No, I've just used the remaster script.

I've not tested with a TV as monitor, but I see no reason why it shouldn't work.

G'day Exton,

Thanks for another comprehensive new PuppEx.

I have only started to explore this one but have found two major (for me) problems:

1. CUPS won't log-in to its localhost (screenshot): I've tried varying the firewall setting to no avail; browsing is fine (posting from Focal64 now). My Epson-WF2510 printer/scanner is on my home network connecting via wifi; all other Pups have connected and print without problem.

2. Xsane won't find/connect after displaying the wifi option which I click. I could not find a sane.d directory in /etc which in other Pups I usually edit (dllconf) to remove unwanted scanners leaving just an entry my networked Epson-WF2510

I'll continue to add my usual apps to this Pup in the meantime.

Thanks again,
David S.

As I can see from Conky you are running BionicPup. Not PuppEX Focal64.

NEWS 201126 ABOUT PuppEX Build 201121 and Nvidia
Today I've discovered that Nvidia’s Proprietary Graphics Driver can be installed in PuppEX Build 201121 after all! Not version 450.80.02, but version 455.45.01. Watch this screenshot. Read this Article about the Open-Source NVIDIA/Nouveau vs NVIDIA Proprietary Driver. Install the Driver like this:
1. Download the driver to /root
2. chmod 755 NVIDIA-Linux-x86_64-455.45.01.run
3. Insert this file in the folder /etc/modprobe.d
4. Reboot your computer
5. Logout to Console Mode (leave X)
6. Run the command ./NVIDIA-Linux-x86_64-455.45.01.run

G'day Exton,

Thanks for replying to my post regarding printing and scanning not working for me in PuppEX Focal.

I don't know how the Puppex Bionic showed in Conky - I use a shared profile for most things and was using PuppEX Bionic to try to fix my PuppEX Focal problems as PuppEX Bionic does scan and print for me.

This morning I definitely started PuppEX Focal and again CUPS could not access its localhost (screenshot).

I fixed the scanning problem by copying sane.d from PuppEX Bionic to /etc in PuppEX Focal.

I still have no idea about the printer/CUPS problem.

In the screenshot, at the bottom right are the applications (icons) I cannot run in PuppEX Focal so far - wine (32-bit) and its associated programs Ocad8, Legacy75 and Deadlink, as well as Gimp-2.10 and Seahaven which both report segmentation faults in a terminal. These all run in most other 64-bit Puppies I have - from an sfs of links to my data partition where all the programs are stored in their 'full' form.

Thanks for any help.

David S.

davids45 wrote: ↑Fri Nov 27, 2020 12:29 am

I don't know how the Puppex Bionic showed in Conky -

The bionicpup64 in the conky might be hard coded in the conkyrc, not read as a parameter.

davids45,

You cannot (according to my experience) mix different versions of Puppy Linux on the same computer. Before using PuppEX Focal64 you should delete everything (all folders) with stuff from other Puppy versions. On all partitions on your computer.

exton wrote: ↑Fri Nov 27, 2020 8:16 am

davids45,

You cannot (according to my experience) mix different versions of Puppy Linux on the same computer. Before using PuppEX Focal64 you should delete everything (all folders) with stuff from other Puppy versions. On all partitions on your computer.

That shouldn't be, I have several Puppy installs on one partition and on other partitions (using psubdir=<puppyname>) and they don't "influence" or "conflict" with each other.
As long as you keep separated save file/folder for each Puppy it should be fine.

Fred

exton wrote: ↑Fri Nov 27, 2020 8:16 am

davids45,

You cannot (according to my experience) mix different versions of Puppy Linux on the same computer. Before using PuppEX Focal64 you should delete everything (all folders) with stuff from other Puppy versions. On all partitions on your computer.

Not at all! That is one of the strong points of the 'frugal' install system. I regularly have up to 6 different pups in separate uniquely named directories on my boot partition. Grub4Dos allows me not only to choose a pup but to have different kernel parameters for each. Just works -and has for decades-. I just finished remastering fossapup64 while testing several iterations (one with peebees 5.9.10 kernel) in my 'experimental' kennel on the boot partition. As an aside, all boot and run but I haven't yet hit the balance I like between a small core SFS still capable of running my addon SFS and the adrv stuff I've left in.

Marv,

Ok, I didn't know that was possible. (I'm no Puppy Linux "expert").

Hi @exton

I tell you that using your last puppy (puppexfosssa) I noticed that when doing the frugal installation with Grub4dos it does not detect it as frugal only as a complete installation, investigating a little about this I found the reason why ...

puppy.sfs) # frugal installed Puppy with simple file name
DISTRO_IDSTRING = $ (tail -c 16 $ TOPDIR $ KEYFILE)
DVERSION = $ (echo $ DISTRO_IDSTRING | cut -b1-6 | tr -dc 'a-z0-9')
MAJOR = $ (echo $ DVERSION | cut -b1-4)
MINOR = $ (echo $ DVERSION | cut -b5-6 | tr -dc '0-9')
["$ MINOR" = ""] && MINOR = 0
[$ MINOR -eq 0] && DVERSION = $ MAJOR || DVERSION = $ MAJOR- $ MINOR
["$ DVERSION"! = ""] || DVERSION = $ UPLOAD
DNAME = "Puppy_ $ DVERSION"

Here it mentions that to be detected as frugal the main sfs must have a condition and that is marked as "puppy" or in this case, here in this part other versions of puppy are configured that the program will detect without problems

# which puppy is better at the top? # v1.9
debug "MYPUPPY = $ MYPUPPY"
NPUP = $ (echo "$ PUPPIES" | wc -l)
if ["$ MYPUPPY" = ""]; then
[-s / etc / DISTRO_SPECS] && source / etc / DISTRO_SPECS
["$ DNAME" = "Fatdog64"] && MYPUPPY = "Fatdog64"
fi
TOPPUPPY = $ MYPUPPY
if ["$ MYPUPPY"! = "" -a $ NPUP -gt 1]; then
TOPPUPPY = $ (echo "$ PUPPIES" | grep -w "$ MYPUPPY" | head -n 1)
["$ TOPPUPPY" = ""] && TOPPUPPY = $ (echo "$ PUPPIES" | grep -w $ (basename "/ $ MYPUPPY") | head -n 1)
["$ FLOPPY" = ""] && TOREMOVABLE = $ (cat / sys / block / $ TODRIVE / removable) || TOREMOVABLE = "0"
["$ (echo $ MYDRIVE | cut -b2)" = "d"] && MYREMOVABLE = $ (cat / sys / block / $ MYDRIVE / removable) || MYREMOVABLE = "1"
["$ TOPPUPPY" = ""] && TOPPUPPY = $ (echo "$ PUPPIES" | grep -Ew "^ $ TODRIVE. * $ MYSFSBASE" | head -n 1)
if ["$ TOPPUPPY" = "" -a "$ TOREMOVABLE" = "0"]; then
for P in $ (echo "$ PUPPIES" | grep -w "$ MYSFSBASE"); do
D = $ (echo $ P | cut -d '/' -f1 | tr -d '0-9')
["$ (cat / sys / block / $ D / removable)" = "0"] && TOPPUPPY = $ P && break
done
fi
if ["$ TOPPUPPY"! = ""]; then
PUPPIES = $ (echo "$ PUPPIES" | grep -vx "$ TOPPUPPY")
PUPPIES = "$ TOPPUPPY
$ PUPPIES "
fi
if ["$ TOREMOVABLE" = "1" -o "$ MYREMOVABLE" = "1"]; then
MYPUPPY = $ (echo "$ PUPPIES" | grep -Ew "^ $ TODRIVE. * $ MYSFSBASE" | head -n 1)
["$ MYPUPPY" = ""] && MYPUPPY = $ (echo "$ PUPPIES" | grep "^ $ TODRIVE" | head -n 1)
if ["$ MYPUPPY"! = ""]; then
PUPPIES = $ (echo "$ PUPPIES" | grep -vx "$ MYPUPPY")
PUPPIES = "$ MYPUPPY
$ PUPPIE

in my case I use a 32-bit system and I use 32 and 64 systems between my puppy installations without problems, in your system I only have to rename your sfs from puppex to puppy, use Grub4dos and before starting the system correct my previous changes and problem solved

PipzDex,

Very good. Thanks for sharing your findings.