Puppy Linux Discussion Forum

radky wrote:

Should the fonts be included in F96, or perhaps available as an optional addon pet package ??

I would go with addon PET or SFS packages. I don't miss the fonts for the dev work so I don't need the overhead. But setting up a different system I might, and then I could easily add them in.

Following a Puppy Linux philosophy: "Freedom of Choice".

@radky wrote:

Display artifacts (or instability) may be an issue for some older intel video chips that do not support the default 'sna' intel acceleration. Changing to 'uxa' acceleration can be helpful for these old intel video chips. In this scenario, the user can manually add the /etc/X11/xorg.conf.d/20-intel.conf with the following contents:

Code: Alles auswählen

Section "Device"
Identifier "Card0"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection

Is working. Thanks for the explanation.

@radky wrote:

fr-ke wrote:

Ghostscript 9.50 lacks the substitution fonts ...

Can't find (or can't open) font file /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-BoldItalic.

Although these substitution fonts are included in Phil's original BionicPup64 8.0, they are absent in Fossapup64 9.5 and Fossapup64 9.6.
Adding them now would increase the current iso size by more than 4 MB.
Should the fonts be included in F96, or perhaps available as an optional addon pet package ??

There are still some applications that depend on ghostscript, also in this distribution.
qpdfview 0.4.18 e.g. B. prints only empty pages of some .pdf if the substitution fonts are missing.

How often in the everyday life of the user .pdf occur in which e.g. MS fonts are used (these have to be substituted) I cannot estimate.

I'm not a developer and can't assess the consequences, functionality vs. size etc.

I personally think that important applications that only partially work should be taken out or replaced with others.
How important the standard PDF viewer and its options are is, of course, a matter of consideration.
I imagine a user who just got his printer up and running.
Was able to put the first .pdf on paper and suddenly got blank pages with the nth .pdf.

For my part, I've almost completed the switch from bionicpup to fossapup64-9.6.
Thanks again to everyone involved!!

CUPS-PDF issue, (not all applications offer "Print to File")

Delete the current CUPS PDF
- add Printer
- Continue
- give a name
- Continue

Choose "Or Provide a PPD File:" Search
offer a PPD (printer-driver-cups-pdf_3.0.1-6_amd64.deb.extracted/usr/share/ppd/cups-pdf/CUPS-PDF_opt.ppd)

- add Printer
- set default options

works for me

Tested with: qpdfview 0.4.18

(For me, the easiest way to extract individual pages from a versatile PDF is to simply print them as a PDF.)

fr-ke wrote: ↑Tue Jan 24, 2023 10:01 am

@radky wrote:

fr-ke wrote:

Ghostscript 9.50 lacks the substitution fonts ...

Can't find (or can't open) font file /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-BoldItalic.

Although these substitution fonts are included in Phil's original BionicPup64 8.0, they are absent in Fossapup64 9.5 and Fossapup64 9.6.
Adding them now would increase the current iso size by more than 4 MB.
Should the fonts be included in F96, or perhaps available as an optional addon pet package ??

There are still some applications that depend on ghostscript, also in this distribution.
qpdfview 0.4.18 e.g. B. prints only empty pages of some .pdf if the substitution fonts are missing.

How often in the everyday life of the user .pdf occur in which e.g. MS fonts are used (these have to be substituted) I cannot estimate.

I'm not a developer and can't assess the consequences, functionality vs. size etc.

I personally think that important applications that only partially work should be taken out or replaced with others.
How important the standard PDF viewer and its options are is, of course, a matter of consideration.
I imagine a user who just got his printer up and running.
Was able to put the first .pdf on paper and suddenly got blank pages with the nth .pdf.

For my part, I've almost completed the switch from bionicpup to fossapup64-9.6.
Thanks again to everyone involved!!

I just randomly ran into the 'substitution fonts' issue. Printing a simple FEDEX shipping label from evince. It would print to my HP4500 in FP64 radky 6, not to my Brother laser printer driven as a generic PCL4/5 device. OK to both in LxPupSc64, S15Pup64,, or Voidpup64. Snitched the fonts from LxPupSc64 and it's OK. It would be disconcerting if I weren't a forumhead so in spite of the size, I vote for in I guess.

I just noticed something using F96_4-radky6-CE that I hadn't noticed with radky4. But maybe I hadn't made a save with it yet.

I have radky6 installed on an ext4 USB stick with a bunch of other pups, using a plain old grub4dos menu 1st that boots everything just fine, including radky6. But when I made a F96 savefolder it's default location was sda1, the laptop hard drive, and once I noticed, I shutdown and moved the save to the radky6 installation folder on the usb drive. I thought the save would load next time, but no go.

I also had installed vanilladpup9.2.34 in this time frame, and experienced the exact same behavior. The save would not load from the install directory on sdb1.

Is this something new in the woof builds? Maybe to prevent users from running system saves off usb?

Is the solution simply putting a psave paramater in the boot stanzas?

Is the solution simply putting a psave paramater in the boot stanzas?

Yes I think that will work. I have not experinced this yet so I'll try to replicate it. It's supposed to find the savefile I thought........

rockedge wrote: ↑Thu Jan 26, 2023 2:18 am

I have not experinced this yet so I'll try to replicate it. It's supposed to find the savefile I thought........

Well I would chalk it up to the computer/usb combination, but all the other pups and KLV are working with persistance folders in the usb installation directories.

@geo_c

Hi geo, just setup a ext4 grub4dos USB flash with F96_4radky6. Created a save folder and rebooted. It finds the save and everything working.

Thanks
wizard

@geo_c

Are you manually editing the menu.lst to have entry for booting F96?
If yes.
Run the Grub4dos Config program, let it reinstall the boot loader, and make all the changes to the menu.lst

bigpup wrote: ↑Thu Jan 26, 2023 2:33 pm

@geo_c

Are you manually editing the menu.lst to have entry for booting F96?
If yes.
Run the Grub4dos Config program, let it reinstall the boot loader, and make all the changes to the menu.lst

Well, the short answer is yes, I manually edited menu.1st. The reason being is I have F96, fossapup64, fatdog, vanilladpup, jackalpup, S15-Pup, and two installs of KLV-airedale, all running off this 500GB USB stick. Every time I run grub4dos and re-install the bootloader, I end up having to do a couple manual edits for KLV. So instead of manually editing, I if I decide to copy a new iso into an existing install directory, I usually just leave the directory name the same and have no problems booting the new system files and loading the existing save. For F96 however, the system sfs with version name was present in the menu1st entry so I changed the name to match which booted successfully, but there were no psave parameters in the menu1st to begin with, so I'm not sure what the savefile issues were. It was quite late in the night, or early in the morning, depending on how you want to look at it. Actually, I woke up in the middle of the night and decided to update this stick's systems on a whim.

@wizard
I'll go ahead and run grub4dos on the stick again and see what happens.

puppy_*sfs not found
Thinkpad x250
houston we got a problem

@AntonioPt This looks like a boot stanza problem. How are you booting? What does the boot stanza look like (menu.lst if using Grub4Dos)?

rockedge wrote: ↑Thu Jan 26, 2023 10:15 pm

@AntonioPt This looks like a boot stanza problem. How are you booting? What does the boot stanza look like (menu.lst if using Grub4Dos)?

I just use Ventoy and copy iso to usb and boot it fossa9.5 works ok but 9.6 didn't

@AntonioPt we should get @Clarity in on this. He is the resident expert on Ventoy and has a lot of experience using it.
I believe he has successfully run F96 in Ventoy. Perhaps he can help out.

F96_4-CE_radky6.iso boots correctly with ISObooter in both BIOS and UEFI modes.

@rockedge im gonna try it with Rufus no wories and thankyou
I just think it's strange because with fossa9.5 in my ventoy usb works and 9.6 dosen't thats all

I'm standing in the airport and wont return for dsys.

@AntonioPt U see the 'debugsave' offered when it didn't boot. Did you run it to capture? If so, post that file as any developer, here, will know the solution for future release.

You do NOT have a USB problem as your USB is booting fine.

IN the meantime, simplest solution while you wait for the next F96 version, do this:

1. Make a folder on Ventoy partition #1 named "BOOTISOS"and MOVE ALL ISO files into it.

2. Add the SuperGrub2Disk ISO file to the folder too.

3. Boot Ventoy USB, select SG2D ISO file, hit the enter key on its menu

4. When SG2D completes, all your ISO files are at the bottom of its screen.

5. ALL forum PUPs-DOGs (except 1) will boot.

Add ALL future ISO files to the BOOTISOS folder and expect that both Ventoy & SG2D will find ISOs in the folder and list them for your selection.

Back next week

P.S. SG2D boots ALL PUP-DOGs while Ventoy, newer, boot only a few. But, noted that recent PUPs, Slacko v7, KLV, KLU, etc are now able to boot directly from Ventoy.

Clarity wrote: ↑Fri Jan 27, 2023 1:03 am

IN the meantime, simplest solution while you wait for the next F96 version, do this:

That's the simplest solution?

@rcrsn51 Yes, add SG2D and boot all forum distros when need.

I do understand YOUR position.

There is a way to add ISObooter GRUB2 support to the Ventoy USB, but I have not published that SET of STEPS

Clarity wrote: ↑Fri Jan 27, 2023 1:03 am

I'm standing in the airport and wont return for dsys.

@AntonioPt U see the 'debugsave' offered when it didn't boot. Did you run it to capture? If so, post that file as any developer, here, will know the solution for future release.

You do NOT have a USB problem as your USB is booting fine.

IN the meantime, simplest solution while you wait for the next F96 version, do this:

1. Make a folder on Ventoy partition #1 named "BOOTISOS"and MOVE ALL ISO files into it.

2. Add the SuperGrub2Disk ISO file to the folder too.

3. Boot Ventoy USB, select SG2D ISO file, hit the enter key on its menu

4. When SG2D completes, all your ISO files are at the bottom of its screen.

5. ALL forum PUPs-DOGs (except 1) will boot.

Add ALL future ISO files to the BOOTISOS folder and expect that both Ventoy & SG2D will find ISOs in the folder and list them for your selection.

Back next week

P.S. SG2D boots ALL PUP-DOGs while Ventoy, newer, boot only a few. But, noted that recent PUPs, Slacko v7, KLV, KLU, etc are now able to boot directly from Ventoy.

hi @Clarity no i didnt run debugsave but i will do it tomorow or so meanwhile i will do the other stuff you said it and good flight,.... and thxx for your quick anser

Clarity wrote: ↑Fri Jan 27, 2023 1:03 am

P.S. SG2D boots ALL PUP-DOGs while Ventoy, newer, boot only a few. But, noted that recent PUPs, Slacko v7, KLV, KLU, etc are now able to boot directly from Ventoy.

I thought you said that SG2D only boots "modern" Puppies and people had reported that Ventoy boots many Puppies.

So much confusion.

rcrsn51 wrote: ↑Fri Jan 27, 2023 1:17 am

...
So much confusion.

Not really.

But I do understand YOUR position.

Have a good weekend everyone.

Clarity wrote: ↑Fri Jan 27, 2023 1:12 am

There is a way to add ISObooter GRUB2 support to the Ventoy USB, but I have not published that SET of STEPS

Why would any sane person do that?

Antonio there are members across this forum who have used and understand SG2D and Ventoy and I am sure while I'm away they will come to your rescue should you need. Yet, I believe you probably will not not.

ASk here or on this thread and expect member help for SG2D. The form thread there is accurate. There is another thread somewhere in that area that address the exact steps given here for Ventoy users.

Member across this forum are aware of both. Oops boarding...

rcrsn51 wrote:

F96_4-CE_radky6.iso boots correctly with ISObooter in both BIOS and UEFI modes.

I also have success with ISObooter, which is one of my favorite tools for this kind of job.

F96_4-radky6 is very young but already starts to show its age. These important fixes went into woof-CE recently:

https://github.com/puppylinux-woof-CE/w ... 0e6c64bc3f
https://github.com/puppylinux-woof-CE/w ... 0a22ce2f13
https://github.com/puppylinux-woof-CE/w ... c62232b9dd
https://github.com/puppylinux-woof-CE/w ... f75f348b08
https://github.com/puppylinux-woof-CE/w ... 29c8234955

F96_4-radky6 is very young but already starts to show its age.

Yes you win. That fact was clear during the entire time we were making it and what F96's role would be. I personally wrote and posted often the idea behind making it.

Is this your way of encouragement or another attempt of telling me how superior your projects are?

But KLV-Airedale and KLA and KLU-jam sure are nice and fresh.......everyday