TazPuppy 5.0 rc2

Under development: PCMCIA, wireless, etc.
Message
Author
User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1041 Post by perdido »

mistfire wrote:@perdido

Here is another revision of f2fs-usb-installer. Can you please test it again?
I ran the script both from the installer and from /usr/bin/ with the same result.

After closing GParted I get the "Failed to make bootable" window, then I click "Ok" and window closes.

.

didit
Posts: 25
Joined: Fri 15 Nov 2019, 15:06

#1042 Post by didit »

I have linux.AppImage: cannot execute binary file: Exec format error
So is it possible to run appimage files in TazPuppy ?

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1043 Post by mistfire »

@diditt AppImages supposed to be worked on TazPuppy. Just chmod +x the appimage file. Make sure that the appimage file was compatible on kernel arch. Based on your appimage error message, I think your appimage file was not 32-bit. Just use 64-bit kernel file and 64-bit zdrv sfs file

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1044 Post by mistfire »

perdido wrote:
mistfire wrote:@perdido

Here is another revision of f2fs-usb-installer. Can you please test it again?
I ran the script both from the installer and from /usr/bin/ with the same result.

After closing GParted I get the "Failed to make bootable" window, then I click "Ok" and window closes.

.
Could you please try this another f2fs-usb-installer script. This time launched it from terminal. Also I disabled boot flag detection.
Attachments
f2fs-usb-installer.zip
remove .zip extension
(32.5 KiB) Downloaded 80 times

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#1045 Post by don570 »

I have linux.AppImage: cannot execute binary file: Exec format error
So is it possible to run appimage files in TazPuppy ?
In fatdog64 I am able to run KRITA paint program appimage
with a special command.
(Otherwise wrong version of QT is loaded)

I can launch KRITA paint program this way

Code: Select all

LD_LIBRARY_PATH= ./krita-4.1.7-x86_64.appimage
_________________________

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1046 Post by perdido »

mistfire wrote:
perdido wrote:
mistfire wrote:@perdido

Here is another revision of f2fs-usb-installer. Can you please test it again?
I ran the script both from the installer and from /usr/bin/ with the same result.

After closing GParted I get the "Failed to make bootable" window, then I click "Ok" and window closes.

.
Could you please try this another f2fs-usb-installer script. This time launched it from terminal. Also I disabled boot flag detection.
Launched from Sakura terminal
After closing GParted a window opens "Failed to make bootable"
Click "OK" window closes

Output from terminal

Code: Select all

root@TazPuppy:~# /usr/bin/f2fs-usb-installer
yes
syslinux is /bin/syslinux
======================
exist_func
======================
e=/dev/sdd2|f2fs|15071232
1 + 0 = 1
/dev/sdd1 /dev/sdd2
======================
func_gui1
======================
e=No f=Yes 1= 2=
/dev/sdd
======================
libparted : 3.2
======================
======================
mbr_func
======================
1+0 records in
1+0 records out
446 bytes copied, 0.00182551 s, 244 kB/s
dd: failed to open '/mbr.bin': No such file or directory
EXIT=" Ok "
.

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1047 Post by mistfire »

Thanks @perdido. I found now the root cause of the problem.
based on your terminal output. I will try to send the revised script within 24-48 hrs.

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1048 Post by mistfire »

@perdido could you please test this f2fs-installer script? I fixed the syslinux folder detection. Just launch it from the terminal to see any error messages
Attachments
f2fs-usb-installer.zip
remove .zip extension
(32.62 KiB) Downloaded 59 times

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1049 Post by perdido »

mistfire wrote:@perdido could you please test this f2fs-installer script? I fixed the syslinux folder detection. Just launch it from the terminal to see any error messages
The new script went farther until some different errors.

The output from terminal is at bottom of post
It is easier to post pics than try to explain with words :)

Launched script from terminal. Chose usb device to intstall to.

Image

Opens GParted

Image

Partitions are present with boot flag

Image

Close GParted, Choose Frugal Install

Image

Choose where puppy files are to install from

Image

After click "OK" files install

Image

After files install, choose how installation will run.
I choose "YES"

Image

After a few minutes I get "failed to edit initrd.xz" window

Image

After that I click "OK" and script exits.
The output from the terminal follows

Code: Select all

root@TazPuppy:~# /usr/bin/f2fs-usb-installer
find: warning: you have specified the -maxdepth option after a non-option argument -type,
but options are not positional (-maxdepth affects tests specified before it as well as those 
specified after it). Please specify options before other arguments.

find: warning: you have specified the -maxdepth option after a non-optio 
n argument -type,
but options are not positional (-maxdepth affects tests specified before it as well as those 
specified after it). Please specify options before other arguments.

yes
syslinux is /bin/syslinux
======================
exist_func
======================
e=/dev/sdd2|f2fs|15071232
1 + 0 = 1
/dev/sdd1 /dev/sdd2
======================
func_gui1
======================
e=No f=Yes 1= 2=
/dev/sdd
======================
libparted : 3.2
======================
======================
mbr_func
======================
ext2 f2fs
======================
full_or_frugal
======================
f=Yes 1=/dev/sdd1 2=/dev/sdd2
======================
func_frugal
======================
======================
copy_func
======================
tazpup 5.0
single boot - 
======================
pupmode_func
======================
Yes
yes
/root
EXIT=" Ok "
The files that are on the usb stick after the install

partition ext2 32MB
---------------------------
# tree
.
├── lost+found
└── tazpup_5.0
└── vmlinuz

2 directories, 1 file

partition f2fs REST OF USB STICK
-----------------------------------------------
# tree
.
└── tazpup_5.0

1 directory, 0 files

###################################
It seems there are files missing after the install completed.

The next install attempt will represent the same type of install except I will choose "NO" in f2fs installer - choice window .
Image
Last edited by perdido on Mon 16 Dec 2019, 22:54, edited 8 times in total.

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1050 Post by perdido »

mistfire wrote:@perdido could you please test this f2fs-installer script? I fixed the syslinux folder detection. Just launch it from the terminal to see any error messages
There was a different error when I choose "NO" at the following window.

The next f2fs-usb-installer attempt - all choices remained exactly the same as previous post until the following window where I choose "NO"
(I chose "Yes" in previous post)

Image

After that choice finishes, the f2fs Installer window indicates "Everything looks good", I click "OK" and installer closes.

Image

Next I unmount and shutdown computer for a reboot with the newly made usb

I get the following error when trying to boot this usb stick

Code: Select all

boot:
Could not find kernel image: /vesamenu.c32
The terminal output from this install attempt

Code: Select all

root@TazPuppy:~# /usr/bin/f2fs-usb-installer
find: warning: you have specified the -maxdepth option after a non-option argument -type,
but options are not positional (-maxdepth affects tests specified before it as well as those
specified after it). Please specify options before other arguments.

find: warning: you have specified the -maxdepth option after a non-optio
n argument -type,
but options are not positional (-maxdepth affects tests specified before it as well as those
specified after it). Please specify options before other arguments.

yes
syslinux is /bin/syslinux
======================
exist_func
======================
e=/dev/sdd2|f2fs|15071232
1 + 0 = 1
/dev/sdd1 /dev/sdd2
======================
func_gui1
======================
e=No f=Yes 1= 2=
/dev/sdd
======================
libparted : 3.2
======================
======================
mbr_func
======================
ext2 f2fs
======================
full_or_frugal
======================
f=Yes 1=/dev/sdd1 2=/dev/sdd2
======================
func_frugal
======================
======================
copy_func
======================
tazpup 5.0
single boot - 
======================
pupmode_func
======================
No
no
======================
boot_func
======================
EXIT=" Ok "
The contents of the file systems on ext2 & f2fs partitions

ext2 32 MB partition
----------------------------
# tree
.
├── extlinux.conf
├── ldlinux.sys
├── lost+found
└── tazpup_5.0

2 directories, 2 files

f2fs partition REST OF USB STICK
----------------------------------------------
# tree
.
└── tazpup_5.0

1 directory, 0 files

###################################
It seems there are files missing after the install completed.
.

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1051 Post by mistfire »

@perdido

Thanks. What a great details.

Here is the latest f2fs-install script. Launch it from terminal. I removed the full install mode. Its is pure frugal install.
Attachments
f2fs-usb-installer.zip
remove .zip extension
(19.1 KiB) Downloaded 97 times

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1052 Post by perdido »

mistfire wrote:@perdido

Thanks. What a great details.

Here is the latest f2fs-install script. Launch it from terminal. I removed the full install mode. Its is pure frugal install.
Launched from terminal.
Script completed normally but the usb stick does not boot.
The error during boot is

Code: Select all

boot:
No DEFAULT or UI configuration directive found!
The contents of both partitions.

ext2 32MB partition
-----------------------------

# tree
.
├── extlinux.conf
├── ldlinux.sys
├── lost+found
└── tazpup_5.0
├── initrd.xz
└── vmlinuz

2 directories, 4 files

f2fs partition
------------------------------

# tree
.
└── tazpup_5.0

########################################
Screens captures and terminal output below this section
Screens are in order of appearance. There were no errors indicated in the windows.

Installer start screen, see below for terminal output.

Image

Image

Image

Image

Image

Image

Image

Screen above does not include terminal output that was redirected to a .txt file

Terminal output below as redirected to a .txt file Script exited normally.

Code: Select all

yes
syslinux is /bin/syslinux
======================
exist_func
======================
e=
======================
func_gui1
======================
e=No f=Yes 1= 2=
/dev/sdd
======================
libparted : 3.2
======================
======================
mbr_func
======================
ext2 f2fs
======================
func_frugal
======================
======================
copy_func
======================
tazpup 5.0
single boot - 
======================
boot_func
======================
EXIT=" Ok "

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1053 Post by mistfire »

@perdido

Almost there. The usb was bootable but the generated configuration file had a problem. I will try to fix the script

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1054 Post by mistfire »

@perdido

Here is the revised f2fs-installer script. It was almost a major overhaul to the script.

But before you run this. Reinstall the syslinux package using this command on terminal:

Code: Select all

tazpkg -gi syslinux --forced
(Take note: The next TazPuppy release will have a properly installed syslinux package)

Just launch this script from terminal and show me the terminal outputs.
Attachments
f2fs-usb-installer.zip
remove .zip extension
(20.12 KiB) Downloaded 90 times

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1055 Post by perdido »

mistfire wrote:@perdido

Here is the revised f2fs-installer script. It was almost a major overhaul to the script.

But before you run this. Reinstall the syslinux package using this command on terminal:

Code: Select all

tazpkg -gi syslinux --forced
(Take note: The next TazPuppy release will have a properly installed syslinux package)

Just launch this script from terminal and show me the terminal outputs.
Updated syslinux via terminal.
Verified new syslinux is installed using Package Manager.
Rebooted, logged in as root/root
Opened Package Manager from menu
Package manager will not allow me to login after syslinux update
Reboot & try again, nope will not allow login.
-----------------------------------------------------------------
New script did not run. tried 3 different terminal programs with same result. Also would not run from install program.

Code: Select all

root@TazPuppy:~# /usr/bin/f2fs-usb-installer
/usr/bin/f2fs-usb-installer: line 597: syntax error near unexpected token `}'
/usr/bin/f2fs-usb-installer: line 597: `}'
root@TazPuppy:~# 
.

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1056 Post by perdido »

@mistfire
Should the sources on CD used during f2fs-usb-installer testing need to be updated with the new syslinux package?
So far I have been using only the TazPuppy Beta41 burned to CD as source files for copying to the usb stick.
I can update them if needed.

User avatar
tom22251
Posts: 15
Joined: Tue 08 Oct 2019, 07:54

#1057 Post by tom22251 »

@perdido

Try "#!/bin/sh" NOT "#!/bin/bash"

if i remember well, taz doesn't like bash,
only ash.

Tom

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1058 Post by mistfire »

perdido wrote:@mistfire
Should the sources on CD used during f2fs-usb-installer testing need to be updated with the new syslinux package?
So far I have been using only the TazPuppy Beta41 burned to CD as source files for copying to the usb stick.
I can update them if needed.
When you are booting tazpuppy beta 41 in pristine state. You have to update the syslinux package first. Please try this script again. Launch on the terminal. I fixed the syntax error on the script. Were getting closer to a working script
Attachments
f2fs-usb-installer.zip
remove .zip extension
(20.15 KiB) Downloaded 91 times
Last edited by mistfire on Wed 18 Dec 2019, 01:20, edited 1 time in total.

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#1059 Post by mistfire »

tom22251 wrote:@perdido

Try "#!/bin/sh" NOT "#!/bin/bash"

if i remember well, taz doesn't like bash,
only ash.

Tom
TazPuppy has a builtin bash unlike slitaz

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#1060 Post by perdido »

mistfire wrote:
perdido wrote:@mistfire
Should the sources on CD used during f2fs-usb-installer testing need to be updated with the new syslinux package?
So far I have been using only the TazPuppy Beta41 burned to CD as source files for copying to the usb stick.
I can update them if needed.
When you are booting tazpuppy beta 41 in pristine state. You have to update the syslinux package first. Please try this script again. Launch on the terminal. I fixed the syntax error on the script. Were getting closer to a working script
I booted from usb stick with fsfs-tools and syslinux forced-update packages added.
This boot is from a usb stick, same as all my other f2fs-usb-installer reports.

The install files "where to install from" I chose CD, it is the TazPuppy Beta 41 iso burned to CD, there are no updates applied.

After the f2fs-usb-installer finishes with no errors I shut down and try booting with the newly created usb install.
The stick does not boot. The message on the screen

Code: Select all

boot:
Invalid or corrupt kernel image
Terminal output from f2fs-usb-installer

Code: Select all

root@TazPuppy:~# /usr/bin/f2fs-usb-installer
yes
syslinux is /bin/syslinux
======================
exist_func
======================
e=/dev/sdd2|f2fs|15071232
1 + 0 = 1
/dev/sdd1 /dev/sdd2
======================
func_gui1
======================
e=No f=Yes 1= 2=
/dev/sdd
Unknown HZ value! (89) Assume 100.
======================
libparted : 3.2
======================
======================
mbr_func
======================
1+0 records in
1+0 records out
446 bytes copied, 0.00178556 s, 250 kB/s
1+0 records in
1+0 records out
440 bytes copied, 0.00535354 s, 82.2 kB/s
ext2 f2fs
======================
func_frugal
======================
======================
copy_func
======================
tazpup 5.0
single boot - 
Copying sfs files...
Contents of /mnt/f2fs2/tazpup_5.0/ (f2fs)
fdrv_tazpup_5.0.sfs
puppy_tazpup_5.0.sfs
zdrv_tazpup_5.0.sfs

/usr/bin/f2fs-usb-installer: line 393: 15430 Killed                  /usr/lib/gtkdialog/box_splash -close never -text "$CPMSG1 $dev2 $CPMSG2"
Contents of /mnt/f2fs1/tazpup_5.0/ (ext2)
initrd.xz
vmlinuz

======================
boot_func
======================
/mnt/f2fs1 is device /dev/sdd1
/usr/bin/f2fs-usb-installer: line 601: 30217 Terminated              /usr/lib/gtkdialog/box_splash -close never -text "$SYSPLASH $dev1"
EXIT=" Ok "
root@TazPuppy:~# 

Post Reply