TazPuppy 5.0 rc2

Message

mistfire · #1126 Post by **mistfire** » Thu 30 Apr 2020, 03:54

@Terry H

Please place this file attached on /usr/sbin to fix the issue. Dont forget to set the permission by typing this command

Code: Select all

chmod +x /usr/sbin/snapmergepuppy

Terry H · #1127 Post by **Terry H** » Fri 01 May 2020, 01:22

Saves now working as expected with updated snapmergepuppy. All working well now.

Thank you.

mistfire · #1128 Post by **mistfire** » Sun 03 May 2020, 13:39

TazPuppy 5.0 beta 52

Changes:
* Smaller initrd. (1.4Mb compressed, 3.3Mb expanded)
* Improved write caching (PUPMODE 3, 7, and 13)
* Improved boot and shutdown process
* Some bugfixes

Download: https://drive.google.com/open?id=11EW9g ... Vjbs698XEH
MD5 Checksum: eee29935e68cf8f1a3c731f73fd74648

Build kit: https://drive.google.com/open?id=1GshmJ ... a1dGMbrG7s

Terry H · #1129 Post by **Terry H** » Sun 03 May 2020, 17:39

Tested beta 52.

Initial test was to test upgrading existing save folder. This was done after deleting the previously provided snapmergepuppy from the save folder. Saves and reboots working OK.

I then did a clean install (pfix=ram). Save and reboot working OK. All other software is OK

There is on observation, which may be intentional. On initial save when creating save folder, there is no option provided to add a chosen suffix to the save folder name. The save folder creation does however create unique names adding -n to the name.

Thanks mistfire, looking really good now.

mistfire · #1130 Post by **mistfire** » Mon 04 May 2020, 10:14

I found something weird. the shutdownconfig script works fine without problems on previous releases of TazPuppy then recently the dialog inputbox suddenly don't work on commandline upon shutdown process while the menubox works fine. However when it launched from commandline shell the dialog and gui version of shutdownconfig works.

mistfire · #1131 Post by **mistfire** » Tue 05 May 2020, 21:51

On my latest experiment the GUI version of shutdownconfig is now working on first shutdown if Xorg was running. Also GUI version of Save Session messagebox upon shutdown for PUPMODE 3/7/13 is added.

The only problem we need to solve was the commandline version where the dialog was buggy. But shutdownconfig works nicely if it was launched from logged in shell.

mistfire · #1132 Post by **mistfire** » Sat 09 May 2020, 13:49

TazPuppy 5.0 Beta 53 released

Changes:
* Build from recent Slitaz release
* First shutdown dialog now runs on both GUI mode and commandline mode
* Dialog asking to save session for PUPMODE 3/7/13 now runs on both GUI and commandline mode
* Fixed bugs on shutdown script
* More bugfixes

Download:https://drive.google.com/open?id=18pg3d ... GVeUqczl1b
MD5 Checksum: 382026ee90fb17206741d475f0630750

Build kit: https://drive.google.com/open?id=1aMGyB ... tho9Vl9nlx

Terry H · #1133 Post by **Terry H** » Tue 12 May 2020, 01:11

New frugal install of Beta 53 on Sandisk USB Flash drive., on Dell Latitude 3350 Laptop with Core i5-5200U 8GB Ram Intel 7265 AC wifi card.

I first tested first shutdown to check save file/folder creation, including adding suffix to name. All OK, with all changes made contained in save folder created. I then booted with pfix=ram and checked first save against reboot. Save folder creation OK. with all changes being saved.

Terry H · #1134 Post by **Terry H** » Tue 12 May 2020, 01:33

In this lot of testing I have encountered an issue with the fdrv. I normally don't use the fdrv. I generally just manually load my own firmware and do a modprobe to load it and have it included in the save folder. for this testing I just used the fdrv provided, which encountered strange behaviour.

I found thet the iwlwifi-7265D*.ucode wasn't loaded, when checking the /lib/firmware there was only 1 directory inside NXP-linux-firmware-67b7579. Checking this directory showed that all the linux firmware was contained in this directory.

I viewed the content of the fdrv, which does not contain such a directory name. I did notice another issue with the supplied fdrv with in the tazpuppy.iso. With in the /lib/firmware directory there is another nested directory firmware which contains all the firmware. This is different to the fdrv contained in other versions of puppy.

mistfire · #1135 Post by **mistfire** » Fri 15 May 2020, 03:30

On my latest experiment, I successfully upgraded xorg and mesa on TazPuppy the problem was mesa requires llvm libs which makes tazpup sfs larger by 6Mb+

didit · #1136 Post by **didit** » Thu 21 May 2020, 06:39

is there any chance to make hardware acceleration work in browser?
cpu load 90% while on windows7 30% on the same web sites/apps

Problems Detected
GPU process was unable to boot: GPU process launch failed.
Disabled Features: all

mistfire · #1137 Post by **mistfire** » Thu 21 May 2020, 23:32

TazPuppy 5.0 beta 54 released

Changes:
* Xorg version 1.20.3 (with glamor acceleration)
* Mesa 17.3.4 (for supporting newer graphics card)
* Improved save session manager for PUPMODE 3/7/13
* Improved xorg auto configuration

Download: https://drive.google.com/open?id=1WyCnI ... n3cYnRz9vA
MD5 Checksum: 62799e075f563f5e7f802518c4138bd9

Build kit: https://drive.google.com/open?id=192ujW ... 0vLqQfF7_Q

NOTICE: On this version, don't update xorg drivers when upgrading packages.

Terry H · #1138 Post by **Terry H** » Sat 23 May 2020, 01:05

Frugal install to USB flash drive. As a clean install saved with new save folder. All seems OK.

For information only :
This version won't boot to X desktop using any previously created save folders, tried with 3 different save folders. Only boots to CLI. I assume it is due to xorg changes.

TiredPup · #1139 Post by **TiredPup** » Sat 23 May 2020, 18:14

is there any chance to make hardware acceleration work in browser?
cpu load 90% while on windows7 30% on the same web sites/apps

Problems Detected
GPU process was unable to boot: GPU process launch failed.
Disabled Features: all

Hardware acceleration does not work in linux for chromium based browsers.

didit · #1140 Post by **didit** » Sun 24 May 2020, 00:04

TiredPup wrote:
is there any chance to make hardware acceleration work in browser?
cpu load 90% while on windows7 30% on the same web sites/apps

Problems Detected
GPU process was unable to boot: GPU process launch failed.
Disabled Features: all
Hardware acceleration does not work in linux for chromium based browsers.

i had hardware acceleration and webgl on chrome in puppy slacko

gabtech · #1141 Post by **gabtech** » Sun 24 May 2020, 16:48

HI people,

I've just downloaded tazpuppy-5.0-beta-54.iso - frugally installed it on my compaq 6710B laptop where I house a collection of puppies and dogs. It boots fine but does no go to desktop. I have booted with both tux login and root login but still no X, only commandline.

mistfire · #1142 Post by **mistfire** » Sun 24 May 2020, 22:19

@gabtech

What's the specs of your laptop?

Could you please send me the xorg.conf file (located at /etc/X11) of other puppies which works on your laptop?

Also when you boot tazpuppy, did you create savefile upon shutdown? If yes; then boot other puppy, mount the savefile of tazpuppy, get the Xorg.0.log file (located at /var/log) and Device.conf file (located at /etc/X11/xorg.conf.d) then send it here.

gabtech · #1143 Post by **gabtech** » Mon 25 May 2020, 00:06

Hi mistfire,

Find attached requested files. No Xorg.0.log file (found at /var/log).

System: Host: dellbot Kernel: 3.14.56 i686 (32 bit, gcc: 4.8.4) Desktop: JWM git-976 Distro: tahrpup 6.0.5
Machine: System: Hewlett-Packard (portable) product: N/A version: F.0B
Mobo: Hewlett-Packard model: 30C0 version: KBC Version 71.2A
Bios: Hewlett-Packard version: 68DDU Ver. F.0B date: 08/02/2007
CPU: Dual core Intel Core2 Duo CPU T7500 (-MCP-) cache: 4096 KB flags: (lm nx pae sse sse2 sse3 ssse3 vmx) bmips: 8777.3
Clock Speeds: 1: 800.00 MHz 2: 2201.00 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) bus-ID: 00:02.0
X.org: 1.15.1 drivers: intel (unloaded: vesa) tty size: 80x24 Advanced Data: N/A for root
Audio: Card: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture ver: k3.14.56
Network: Card-1: Broadcom NetLink BCM5787M Gigabit Ethernet PCI Express driver: tg3 ver: 3.136 bus-ID: 18:00.0
IF: eth0 state: down mac: <filter>
Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
driver: iwl4965 ver: in-tree: bus-ID: 10:00.0
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 320.1GB (40.1% used) 1: id: /dev/sda model: Hitachi_HTS54503 size: 320.1GB
Partition:
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 139 Uptime: 50 min Memory: 356.2/998.3MB Runlevel: 5 Gcc sys: 4.8.4 Client: Shell (sh) inxi: 1.9.17

mistfire · #1144 Post by **mistfire** » Mon 25 May 2020, 01:11

@gabtech

Thanks for the files that you sent to me

May I see the Xorg.0.log (located at /var/log) and xerrs.log (located at /tmp) of your tahrpup

Also run "busybox lspci" on terminal of your tahrpup and post the terminal output here

If Xorg.0.log file was missing on TazPuppy kindly do the following:
1. Boot TazPuppy with Savefile loaded.
2. If you reached terminal login then logged in as root.
3. Type this on command line

Code: Select all

cp -f /var/log/Xorg.0.log /root/Xorg.0.log

4. Now restart the computer and boot other puppy
5. Mount the tazpuppy savefile and get the Xorg.0.log at /root folder from the save file
6. Upload the Xorg.0.log on this thread

gabtech · #1145 Post by **gabtech** » Mon 25 May 2020, 04:28

Hello mistfire,

Files attached.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

TazPuppy 5.0 rc2

Tazpuppy54--beta(only booting to commandline)

Tazpuppy Beta 54(booting to commandline

Tazpuppy Beta 54(booting to commandline)