TazPuppy 5.0 rc2

Message

mistfire · #1101 Post by **mistfire** » Tue 03 Mar 2020, 13:14

@zagreb

Try to swap kernel and zdrv modules using the kernel and zdrv modules from a later build puppies. Just don't forget to rename the donor zdrv to zdrv_tazpup_5.0.sfs

zagreb999 · #1102 Post by **zagreb999** » Wed 04 Mar 2020, 13:00

on lenovo 32bit-intel
version 47 iso can not
open desktop

login as tux and root

startx and xwin can not
open desktop

mistfire · #1103 Post by **mistfire** » Wed 04 Mar 2020, 14:38

@zagreb whats the specs of that lenovo laptop?

zagreb999 · #1104 Post by **zagreb999** » Wed 04 Mar 2020, 19:12

lenovo ideapad 1gb ram-intel

all versions untill 47 are ok
new drivers added to 47 iso
are cause of bug?

mistfire · #1105 Post by **mistfire** » Thu 05 Mar 2020, 10:49

@zagreeb I need the exact model of your lenovo laptop. Look at the sticker under your laptop or at the right side of your touchpad

zagreb999 · #1106 Post by **zagreb999** » Thu 05 Mar 2020, 20:33

specificaton

https://www.cnet.com/products/lenovo-id ... 10e/specs/

zagreb999 · #1107 Post by **zagreb999** » Sat 07 Mar 2020, 10:24

please, do not increase iso file
with specifc drivers for over
of 20 mb, put it in ppm!

can you fix gprs?
thanks!

GigaWatt · #1108 Post by **GigaWatt** » Fri 20 Mar 2020, 15:10

I've been trying to integrate TazPuppy into a multiboot USB/ISO, but I've been having problems regarding real vs. protected mode mounting and what the kernel sees after it loads drivers. This a common problem with distros that use more than just vmlinuz and initrd to load the whole distro into RAM, as is the case with distros that use sqfs to load the rest of the OS into a ramdrive (i.e. Puppy Linux).

I've tried GRUB4DOS and SYSLINUX as bootloaders with a bunch of different commands to try and "hint" to the kernel that there actually is a ramdisk ISO mounted in some memory location, but since this ISO is mounted (mapped) in real mode (not protected mode), the kernel can't see it, thus, it can't see the sqfs file... and this is where the loading process stops.

The only solution that I'm aware of is to use memdiskfind in the init script, which should point the kernel to where this ISO is mapped/mounted in real mode, but, in order to do this, you have to know where to insert this command.

Code: Select all

modprobe phram phram=memdisk,$(memdiskfind)
modprobe mtdblock

Could this be done with TazPuppy? If so, what tools would I need to extract/decompress the initrd file, edit the init script and compress the initrd file. Where would I have to insert this command and where do I place the memdiskfind file in the ISO (the root

)?

Also, tried the newest beta, 47, in VMware. It doesn't boot to X, just stays at bash.

GigaWatt · #1109 Post by **GigaWatt** » Mon 23 Mar 2020, 22:26

I was tinkering the last few days with the problem I mentioned in my previous post and did a quick and dirty hack

. I noticed this in the init script.

Code: Select all

#first look inside initrd...
echo "Checking puppy files inside initrd..."
[ -f /${PUPXXXSFS} ] && PUPSFS="rootfs,rootfs,/${PUPXXXSFS}"
[ -f /${ZDRVSFS} ] && ZDRV="rootfs,rootfs,/${ZDRVSFS}"
[ -f /${FDRVSFS} ] && FDRV="rootfs,rootfs,/${FDRVSFS}"
[ -f /${ADRVSFS} ] && ADRV="rootfs,rootfs,/${ADRVSFS}"
[ -f /${YDRVSFS} ] && YDRV="rootfs,rootfs,/${YDRVSFS}"

So, basically I just unpacked the initrd, cpio extracted the content, added the sfs files in the same dir and cpio-ed the dir, compressed the file and... well, it worked

. Now, I can chainload the TazPuppy iso

.

I haven't tried this with any other distros that use sfs, but I'll look into other init scripts. If they check into the root of the ramdrive, this might be a good temporary workaround

.

mistfire · #1110 Post by **mistfire** » Wed 25 Mar 2020, 00:54

TazPuppy 5.0 beta 48 released

Changes:
* Build from recent slitaz release
* With networking feature. (File/Folder sharing and manage shared folders on network)
* Improved xorg auto configuration
* Bugfixes on initrd
* Bugfixes on init script

Download: https://drive.google.com/open?id=1Kjl7u ... PkW_65S6xK
MD5 Checksum: 856fe5033db0d5750a0048559ba5350e

Build kit: https://drive.google.com/open?id=1pdj73 ... TyRc57vK1f

mistfire · #1111 Post by **mistfire** » Sat 11 Apr 2020, 10:46

TazPuppy 5.0 Beta 49 released

Changes:
* Optimized boot process
* Improved package management
* Improved SFS module loading
* Improved system script

Download: https://drive.google.com/open?id=1g-bvK ... _TJzE42AA9
MD5 Checksum: c65fa77ed7a3ea9b4752f9ba8fbc21b6

Build kit: https://drive.google.com/open?id=1QyKVU ... AvdSdIkHic

didit · #1112 Post by **didit** » Fri 17 Apr 2020, 21:41

mistfire wrote:@diditt does your slacko use nvidia proprietary drivers? TazPuppy uses nouveau xorg driver for nvidia video cards

mistfire · #1113 Post by **mistfire** » Mon 20 Apr 2020, 05:16

@diditt

Try to use this nvidia package from official nvidia website

https://www.nvidia.com/en-us/drivers/unix/

mistfire · #1114 Post by **mistfire** » Mon 20 Apr 2020, 05:22

TazPuppy 5.0 Beta 50 released

Changes:
* Glibc now upgraded to version 2.28
* GCC libs now upgraded to 8.2.0
* Critical bugfix and improvements on SFS module loading
* Critical bugfix and improvements on package management
* Improvements on default file associations
* Improvements on rc.update script
* Improved sanderdog
* Added support for major desktop environment.

Download: https://drive.google.com/open?id=1YJun8 ... kSBYqWbQr3
MD5 Checksum: 5dc17364ebb5f93a609668ffc1d56f97

Build kit: https://drive.google.com/open?id=1-LyYt ... uCCuNb-JLY

didit · #1115 Post by **didit** » Mon 20 Apr 2020, 17:38

mistfire wrote:@diditt

Try to use this nvidia package from official nvidia website

https://www.nvidia.com/en-us/drivers/unix/

i tried it also but i just can't make it work
and also i would like to know how to install a newer tazpuppy on top of older without wiping the entire partition

mistfire · #1116 Post by **mistfire** » Mon 20 Apr 2020, 18:26

@didit

Use frugal method to install TazPuppy without wiping a whole partition. Use save to folder if TazPuppy was installed on a Linux partition.

Terry H · #1117 Post by **Terry H** » Tue 21 Apr 2020, 19:15

A new clean frugal install of TazPuppy Beta 50 on SanDisk UltraFit USB Flash drive booting in UEFI mode. I created a new Save Folder. All software so far is working well. Only addition is I have installed Palemoon 28.9.1.

The problem I am having is that it is running in PUPMODE=12, instead of 13. I have pmedia=usbflash in the kernel line. It also boots the same if I remove pmedia statement. I have set Save Manager to +0 to Ask at Shutdown, but as PUPMODE is 12 it has no effect.

Why is it booting in this PUPMODE? How can I get it to boot PUPMODE=13?

Thanks in advance.

didit · #1118 Post by **didit** » Tue 21 Apr 2020, 20:26

mistfire wrote:@didit

Use frugal method to install TazPuppy without wiping a whole partition. Use save to folder if TazPuppy was installed on a Linux partition.

grub4dos doesnt work on the latest tazpuppy

mistfire · #1119 Post by **mistfire** » Tue 21 Apr 2020, 21:21

To achieve PUPMODE 13 it requires large ram, the computer has a battery, and the battery was in good health.

Terry H · #1120 Post by **Terry H** » Tue 21 Apr 2020, 21:36

mistfire wrote:To achieve PUPMODE 13 it requires large ram, the computer has a battery, and the battery was in good health.

It's a Dell Latitude 3350 Laptop with i5-5200U CPU with 8GB RAM also 8GB Swap on internal SSD, the battery is good (capacity is down a bit) . Earlier iterations of TazPuppy woud boot to PUPMODE 13 on this laptop.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

TazPuppy 5.0 rc2

Should be running in PUPMODE=13.