Puppy Linux Discussion Forum

dimkr wrote: ↑Sat Nov 12, 2022 7:00 am

You can download a prebuilt kernel from https://github.com/puppylinux-woof-CE/w ... el-kit.yml. Click on one of the job runs, then on the number below "Artifacts".

@dimkr Thanks for quick response.

I chose the Kernel link kernel-kit-output-5.15.x-x86_64 and downloaded the file kernel-kit-output-5.15.x-x86_64.zip.
The .zip file was placed in the folder woof-out_x86_64_x86_64_ubuntu_jammy64/huge_kernel/

Running the script ./3builddistro again would not detect the file placed in the huge_kernel folder.

Extracted the .zip file using unzip command.

FP: /mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/huge_kernel # ls -1 kernel-kit-output-*
kernel-kit-output-5.15.x-x86_64.zip
FP: /mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/huge_kernel # unzip kernel-kit-output-5.15.x-x86_64.zip 
Archive:  kernel-kit-output-5.15.x-x86_64.zip
  inflating: huge-5.15.77-kernel-kit.tar.bz2.md5.txt  
  inflating: huge-5.15.77-kernel-kit.tar.bz2.sha256.txt  
  inflating: huge-5.15.77-kernel-kit.tar.bz2  
  inflating: kbuild-5.15.77.sfs.md5.txt  
  inflating: kbuild-5.15.77.sfs.sha256.txt  
  inflating: kbuild-5.15.77.sfs      
  inflating: kernel_sources-5.15.77-kernel-kit.sfs.md5.txt  
  inflating: kernel_sources-5.15.77-kernel-kit.sfs.sha256.txt  
  inflating: kernel_sources-5.15.77-kernel-kit.sfs 

Ran the command ./3builddistro one more time.

script fails with the ERROR message .md5.txt and .sha256.txt not found

...

pinstall.sh finished OK
setting PS1="\w\$ " as the CLI prompt.
Now setting /etc/os-release file

Installing HUGE kernel to build/
Please choose the number of the kernel you wish to use
1 ../huge_kernel/huge-5.15.77-kernel-kit.tar.bz2
2 ../huge_kernel/huge-5.15.77-kernel-kit.tar.bz2.sha256.txt

1

You chose ../huge_kernel/huge-5.15.77-kernel-kit.tar.bz2.
Kernel is 5.15.77-kernel-kit version
tar: huge-5.15.77-kernel-kit.tar.bz2.md5.txt: Not found in archive
tar: huge-5.15.77-kernel-kit.tar.bz2.sha256.txt: Not found in archive
tar: Exiting with failure status due to previous errors

.txt files do exist in the folder.

Do I need to rename the original .zip file as huge_... to work around this error ?

You should extract the .zip file to kernel-kit/output.

Quote from https://github.com/puppylinux-woof-CE/w ... the-kernel:

The output should be available in kernel-kit/output and 3builddistro can use it instead of downloading a prebuilt kernel.

If README.md is not clear enough, please open a pull request with proposed improvements.

(And make sure you also read and understand https://github.com/puppylinux-woof-CE/w ... kernel-kit)

Finally - light at the end of the tunnel...

ISO file was built in the following directory woof-out_x86_64_x86_64_ubuntu_jammy64 / woof-output-upup-22.04/

woof-out_x86_64_x86_64_ubuntu_jammy64 # ls -1 woof-output-upup-22.04/
upup-22.04.iso
upup-22.04.iso.md5.txt
upup-22.04.iso.sha256.txt

Contents of upup-22.04.iso

drwxr-xr-x 4 root root     2048 Nov 12 04:25 boot
-rw-r--r-- 1 root root 78712832 Nov  7 09:43 fdrv_upup_22.04.sfs
-rw-r--r-- 1 root root     2020 Nov 12 04:25 grub.cfg
-rw-r--r-- 1 root root  2365699 Nov 12 04:23 initrd.gz
-rw-r--r-- 1 root root    38912 Aug 10  2021 isolinux.bin
-rw-r--r-- 1 root root    14259 Nov 12 04:23 README.txt
-rw-r--r-- 1 root root  6564352 Nov 12 04:24 ucode.cpio
-rw-r--r-- 1 root root 11087552 Nov  7 09:35 vmlinuz
drwxr-xr-x 2 root root     2048 Nov 11 21:25 Windows_Installer
-rw-r--r-- 1 root root 49094656 Nov  7 09:45 zdrv_upup_22.04.sfs

Thanks to @dimkr and everyone else who helped in reaching this goal.

Boot failed with the message :
fatal error puppy_upup_22.04.sfs not found

Here's the listing of every .sfs file under the Build directory /mnt/home/PL and is missing puppy_upup_22.04.sfs.

FP: /mnt/home # find /mnt/home/PL  -name *.sfs
/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/sandbox3/build/zdrv_upup_22.04.sfs
/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/sandbox3/build/fdrv_upup_22.04.sfs
/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/kernel-kit/output/kernel_sources-5.15.77-kernel-kit.sfs
/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/kernel-kit/output/kbuild-5.15.77.sfs

Grub Entry to run "Ubuntu - Jammy64"

menuentry '2. Ubuntu.Jammy64 - Puppy Linux - [SDA6] ' {
  set root=(hd0,gpt6)

  echo '..... Loading Ubuntu.Jammy64 : VMLINUZ .....'
  linux /Ubuntu.Jammy64/vmlinuz psubdir=/Ubuntu.Jammy64 pmedia=ataflash psave=sda6:/Ubuntu.Jammy64/RY.SAVE/
  
  echo '..... Loading Ubuntu.Jammy64 :  INITRD .....'
  initrd /Ubuntu.Jammy64/initrd.gz
}

Directory Listing :SDA6:/Ubuntu.Jammy64/

FP: /mnt/home # ls -l Ubuntu.Jammy64/
total 137972
-rw-r--r-- 1 root root 78712832 Nov 12 05:15 fdrv_upup_22.04.sfs
-rw-r--r-- 1 root root  2365699 Nov 12 05:15 initrd.gz
-rw-r--r-- 1 root root    14259 Nov 12 05:15 README.txt
drwxr-xr-x 2 root root     4096 Nov 12 05:38 RY.SAVE
-rw-r--r-- 1 root root 11087552 Nov 12 05:15 vmlinuz
-rw-r--r-- 1 root root 49094656 Nov 12 05:15 zdrv_upup_22.04.sfs

Question:
missing puppy...sfs --> Is there a particular log file, I can check to see what happened ?

Start with looking at the output of 3builddistro, the ISO is definitely faulty.

dimkr wrote: ↑Sat Nov 12, 2022 12:22 pm

Start with looking at the output of 3builddistro, the ISO is definitely faulty.

I copied & modified the script 3builddistro. Added "set -x" at the very top

#!/bin/bash
# new for fatdog style kernel

set -x
...

Ran the command $> ./3builddistro 1>3BuildDistro.log 2>&1

Sample output of the included log file

chroot . /usr/sbin/setup-spot weechat=true
mv -f root/.spot-status root/.spot-status.orig
chroot . /usr/sbin/setup-spot powerapplet_tray=true
mv -f root/.spot-status.orig root/.spot-status
./usr/sbin/pup-advert-blocker start ./etc/hosts
mv root/Downloads home/spot/
chroot . chown -R spot:spot /home/spot/Downloads
ln -s ../home/spot/Downloads root/
rm -f usr/share/applications/pupX-X-settings.desktop usr/share/applications/Mouse-keyboard-Wizard.desktop usr/share/applications/Xorg-Video-Wizard.desktop usr/share/applications/BootManager-configure-bootup.desktop usr/share/applications/wallpaper.desktop usr/share/applications/FontManager.desktop usr/share/applications/Set-date-and-time.desktop usr/share/applications/Set-timezone.desktop usr/share/applications/ptheme.desktop usr/share/applications/Psync.desktop
for i in usr/share/themes/*; do case "$i" in usr/share/themes/Default|usr/share/themes/Emacs|usr/share/themes/Flat-grey-rounded|usr/share/themes/Polished-Blue|usr/share/themes/Gradient-grey|usr/share/themes/buntoo-ambience|usr/share/themes/stark-blueish) ;; *) rm -vrf "$i" ;; esac; done
for i in usr/share/ptheme/globals/*; do case "$i" in usr/share/ptheme/globals/Flat-grey|usr/share/ptheme/globals/431|usr/share/ptheme/globals/412|usr/share/ptheme/globals/Buntoo|usr/share/ptheme/globals/Tahrpup) ;; *) rm -vf "$i" ;; esac; done
rm -vf usr/share/backgrounds/*.jpg
rm -f etc/fonts/conf.d/10-hinting-slight.conf etc/fonts/conf.d/10-autohint.conf
ln -s ../conf.avail/10-hinting-none.conf etc/fonts/conf.d/
...

+ mksquashfs rootfs-complete build/puppy_upup_22.04.sfs -comp zstd -Xcompression-level 19 -b 256K -no-exports -no-xat
trs
mksquashfs: Compressor "zstd" is not supported!
mksquashfs: Compressors available:
gzip
lzma
lzo
xz (default)

Either change to -comp xz (or any other option) in _00build.conf or run woof-CE on a newer distro, where squashfs-tools supports zstd compression.

Modified _00build.conf & ran ./3builddistro script

#SFSCOMP='-comp zstd -Xcompression-level 19 -b 256K -no-exports -no-xattrs'   #--- Fails (#RY)
SFSCOMP='-comp xz -Xbcj x86 -b 256K -no-exports -no-xattrs'

Build completed successfully with puppy_upup_22.04.sfs now showing up in upup-22.04.iso.

Issues
1) Ubuntu-Jammy64 displayed Error Message "zswap failed to load" during the boot process.
2) System booted into Graphical desktop. Keyboard and Mouse would not work.

I am happy with the progress made but still a long way to go to get a fully functional Distro.

Question:
1) Other scripts may also have exhibited partial failures but completed. I guess it is better to switch to the latest Puppy Distro for local build. Could someone provide the name and url for Puppy ISO which has been working for them now to do the builds ?
2) Building on GitHub :: woof-CE --> Actions --> release, is it possible to modify 4 scripts 0,1,2,3 , add "set -x" and capture the output into log file ?
Comparing DEBUG-LOGs between GitHub and Local Script-Runs will surely help us resolve most of the issues quickly.

You probably used an incompatible kernel. Use kernel-kit-output-usrmerge-5.15.x-x86_64, not kernel-kit-output-5.15.x-x86_64,

Quote from https://github.com/puppylinux-woof-CE/w ... kernel-kit:

Some kernel versions have a -usrmerge variant: one where /lib/modules is moved to /usr/lib/modules, /sbin is moved to /usr/sbin, and so on. They will work with a Puppy built with USR_SYMLINKS=yes, where /lib and /sbin are symlinks to their counterparts under /usr.

dimkr wrote: ↑Sat Nov 12, 2022 6:35 pm

You probably used an incompatible kernel. Use kernel-kit-output-usrmerge-5.15.x-x86_64, not kernel-kit-output-5.15.x-x86_64,

Quote from https://github.com/puppylinux-woof-CE/w ... kernel-kit:

Some kernel versions have a -usrmerge variant: one where /lib/modules is moved to /usr/lib/modules, /sbin is moved to /usr/sbin, and so on. They will work with a Puppy built with USR_SYMLINKS=yes, where /lib and /sbin are symlinks to their counterparts under /usr.

I will work on rebuilding with the right kernel : kernel-kit-output-usrmerge-5.15.x-x86_64

Question:
I had tried to upgrade FossaPup9.5 to Ubuntu.22.04 by running apt . I could not update dpkg to install apt and go from there.
How to update FossaPup9.5 to use the latest packages ?

Build was successful.
Boot was successful.
Keyboard, Mouse and Internet connection worked with ZERO issues.

Could I test your ISO file? I've had problems similar to some of what you've solved. If I test your ISO and it solves my test PC's problem, if provides a guide to look toward.

Clarity wrote: ↑Tue Nov 15, 2022 5:14 am

Could I test your ISO file? I've had problems similar to some of what you've solved. If I test your ISO and it solves my test PC's problem, if provides a guide to look toward.

Where should I post the .iso and devx..sfs files ?
Does PuppyLinux website itself allow hosting user files ?

$> du -sh devx* *.iso
115M	devx_upup_22.04.sfs
387M	upup-22.04.iso

Build : Ubuntu.22.04-Jammy64-x86_64 huge-5.15.77-kernel-kit
ISO & DEVX files are now available here ...

https://github.com/RYRNRY/FileShare

List of Files & their Size

# du -sh *
115M	devx_upup_22.04.sfs
4.0K	devx_upup_22.04.sfs.md5.txt
388M	upup-22.04.iso
4.0K	upup-22.04.iso.md5.txt
4.0K	upup-22.04.iso.sha256.txt

This is the first time I am trying out GitHub's Large File Repository feature. Please let me know, if you run into file download / corruption issues.