Page 59 of 60

Posted: Mon 01 Jun 2020, 20:16
by Terry H
New manual frugal install tazpuppy beta55 to Sandisk Ultra Fit Flash drive, manually installed palemoon 28.9.3. Created Save folder. All working well.

Thank you mistfire for your continued development work.

Posted: Tue 02 Jun 2020, 12:28
by gabtech

Posted: Sun 07 Jun 2020, 02:57
by mistfire
TazPuppy 5.0 beta 56

Changes:
* On the fly changing save session manager settings for PUPMODE 3/7/13
* Improved package management

Download: https://drive.google.com/file/d/1yUqhJG ... nEnkNUYIzX
MD5 Checksum: 4ec24cd186690a66509953649de67d0d

Build kit: https://drive.google.com/file/d/1SGwxPu ... r5nCR4VRln

Posted: Wed 10 Jun 2020, 03:18
by mistfire
On my latest experiment, I successfully modified tazpkg to make it independent and stand alone. I was able to run tazpkg on puppy without tazpuppy or slitaz. It only requires busybox and awk for command line.

Posted: Sat 13 Jun 2020, 12:34
by mistfire
TazPuppy 5.0 Release Candidate 1 released

Changes:
* Some improvements on package management. Tazpkg is now stand-alone and fully independent
* Fixed issues on xdg components

Download: https://drive.google.com/file/d/1AYPCAU ... sp=sharing
MD5 Checksum: 0854fdae774d8a41482440fdde9934e8

Build kit: https://drive.google.com/file/d/1rCI3Ne ... sp=sharing

Posted: Sun 14 Jun 2020, 15:06
by mistfire
TazPuppy build kit has been uploaded

Download link at the first post of this thread

Posted: Thu 18 Jun 2020, 04:00
by mistfire
On my latest experiment, I succesfully ran slitaz cooker, I able to compile source code and build slitaz packages using tazpuppy.

Posted: Sat 27 Jun 2020, 10:23
by mistfire
TazPuppy 5.0 Release Candidate 2 released

Changes:
* Easy to setup slitaz cooker.
* Slitaz cooker server is now added on menu
* Some bugfixes

Download: https://drive.google.com/file/d/1cMON88 ... VqmcMJdhyd
MD5 Checksum: ea8d96eb2e44f5f1321fa70a15717c47

Build Kit: https://drive.google.com/file/d/1rxQRV0 ... olCAQvwm6x

Posted: Mon 29 Jun 2020, 16:23
by GigaWatt
Doesn't load X on old VIA Chrome9 HC IGP integrated graphics. Haven't tested with any other VIA Chrome integrated graphics chips.

Posted: Wed 01 Jul 2020, 04:33
by mistfire
@Gigawatt

If you boot TazPuppy for the first time then do the following:

1. Login on commandline as root
2. Run the following commands

Code: Select all

cp /var/log/Xorg.0.log /root/
mkdir -p /root/xorg-conf-files
cp /etc/X11/xorg.conf.d/* /root/xorg-conf-files/
3. Put /home/tux/xorg-conf-files in a tarball
4. Shutdown tazpuppy and create a savefile
5. Boot other puppy
6. If savefile was a file then mount it otherwise enter to the save folder
7. Get the Xorg.0.log and the tarball you made at /home/tux/
8. Upload to this thread.

Posted: Sat 04 Jul 2020, 06:39
by didit
nvidia-xconfig

Using X configuration file: "/etc/X11/xorg.conf".

VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf.
At least one Device section is required.

sh: pkg-config: command not found
Backed up file '/etc/X11/xorg.conf' as
'/etc/X11/xorg.conf.nvidia-xconfig-original'
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

Posted: Sat 04 Jul 2020, 21:42
by didit
Thats what i have on TazPuppy and on SCpup (nouveau driver both)

Posted: Sat 04 Jul 2020, 22:37
by mistfire
@Didit
nvidia-xconfig look for entry in /etc/X11/xorg.conf, however TazPuppy does not store Xorg settings at xorg.conf. Instead it uses individual files saved at /etc/X11/xorg.conf.d folder

Did you try to use ScPup kernel and zdrv files on TazPuppy?

Posted: Sat 04 Jul 2020, 23:47
by didit
mistfire wrote:@Didit
Did you try to use ScPup kernel and zdrv files on TazPuppy?
no i did not, scpup kernel 5.4.46 i dont know if it matters too much

Posted: Sat 04 Jul 2020, 23:53
by mistfire
@didit

Try to boot TazPuppy using ScPup kernel. Don't forget to rename ScPup zdrv file as zdrv_tazpup_5.0.sfs

Posted: Sun 05 Jul 2020, 00:16
by Terry H
Have been running Tazpuppy RC2 for 2 days now. Frugal install on Dell laptop Core i5-5200U 8 GB RAM. I used a save folder for previous install. I had previously installed firefox-official (76.0), which successfully updated yesterday to 78.0.1. I have added a LibreOffice SFS. All working withut issue.

Tazpuppy 5.0 RC2 is running very smoothly. Great work. Thanks mistfire.

Posted: Sun 05 Jul 2020, 01:02
by didit
mistfire wrote:@didit

Try to boot TazPuppy using ScPup kernel. Don't forget to rename ScPup zdrv file as zdrv_tazpup_5.0.sfs
yes i just tried this but nothing changed (but maybe i should use fdrv also idk)

Posted: Sun 05 Jul 2020, 02:07
by Terry H
didit wrote:
mistfire wrote:@didit

Try to boot TazPuppy using ScPup kernel. Don't forget to rename ScPup zdrv file as zdrv_tazpup_5.0.sfs
yes i just tried this but nothing changed (but maybe i should use fdrv also idk)
Attached is a screenshot of the nvidia folder in an fdrv. It may contain firmware which will assist you.

If you run run from a termnal:

Code: Select all

dmesg | grep -i firmware
It may identify missing firmware, which may be in the fdrv.

Posted: Sun 05 Jul 2020, 13:42
by GigaWatt
mistfire wrote:@Gigawatt

If you boot TazPuppy for the first time then do the following:

1. Login on commandline as root
2. Run the following commands

Code: Select all

cp /var/log/Xorg.0.log /root/
mkdir -p /root/xorg-conf-files
cp /etc/X11/xorg.conf.d/* /root/xorg-conf-files/
3. Put /home/tux/xorg-conf-files in a tarball
4. Shutdown tazpuppy and create a savefile
5. Boot other puppy
6. If savefile was a file then mount it otherwise enter to the save folder
7. Get the Xorg.0.log and the tarball you made at /home/tux/
8. Upload to this thread.
Sorry, meant to write earlier, but was busy.

I tried with an old beta (58 I believe) and yes, it doesn't load X on that beta. With the latest RC2, it does load X, but the colors are all scrambled and it looks like the graphics timings are of... you get stripes, like on a bad TV channel (back in the analog TV days) and rainbow colors. Maybe a bad driver config :?:.

I'll see if I can take a pic ;).

Posted: Mon 06 Jul 2020, 05:56
by didit
tux@TazPuppy:~$ dmesg | grep -i firmware
pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)