TazPuppy 5.0 rc2
@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.
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 96 times
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Launched from terminal.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.
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!
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.
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 "
@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:
(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.
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
Just launch this script from terminal and show me the terminal outputs.
- Attachments
-
- f2fs-usb-installer.zip
- remove .zip extension
- (20.12 KiB) Downloaded 89 times
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Updated syslinux via terminal.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:(Take note: The next TazPuppy release will have a properly installed syslinux package)Code: Select all
tazpkg -gi syslinux --forced
Just launch this script from terminal and show me the terminal outputs.
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:~#
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 scriptperdido 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.
- Attachments
-
- f2fs-usb-installer.zip
- remove .zip extension
- (20.15 KiB) Downloaded 89 times
Last edited by mistfire on Wed 18 Dec 2019, 01:20, edited 1 time in total.
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
I booted from usb stick with fsfs-tools and syslinux forced-update packages added.mistfire wrote: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 scriptperdido 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.
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
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:~#
@perdido
Does it show the bootloader menu?
If yes, then the vmlinuz file might be corrupted. Please check the checksum of your downloaded tazpuppy live cd and compared it against the given checksum (Located and the first post of this thread). If the checksums dont match. The live cd you downloaded might be corrupted. If matched then the your burned cd might have a problem
Does it show the bootloader menu?
If yes, then the vmlinuz file might be corrupted. Please check the checksum of your downloaded tazpuppy live cd and compared it against the given checksum (Located and the first post of this thread). If the checksums dont match. The live cd you downloaded might be corrupted. If matched then the your burned cd might have a problem
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
No bootloader menumistfire wrote:@perdido
Does it show the bootloader menu?
If yes, then the vmlinuz file might be corrupted. Please check the checksum of your downloaded tazpuppy live cd and compared it against the given checksum (Located and the first post of this thread). If the checksums dont match. The live cd you downloaded might be corrupted. If matched then the your burned cd might have a problem
Never gets that far
md5 sum has been confirmed multiple times multiple ways.
md sum of vmlinuz on stick that did not boot
md5= 49922157d2e183dedcae46086e380f13
same as on cd.
cd iso has verified md5 sum --> bf1d0d76ca4d821fdd19f0dc1264bf36
Files in the usb stick that did not boot listed below
ext2 32MB partition
--------------------------
# tree
.
├── extlinux.conf -->md5 c9f992a9a043d38da6b8a48041db9540
├── ldlinux.sys --> md5 daa001e3122913b37073baa66e425149
├── lost+found
└── tazpup_5.0
├── initrd.xz --> md5 efcc678013a712d9aa6ce90dfd093c90
└── vmlinuz --> md5 49922157d2e183dedcae46086e380f13
2 directories, 4 files
fsf2 partition
--------------------
# tree
.
└── tazpup_5.0
1 directory, 0 files
.
- Attachments
-
- error.jpg
- (45.98 KiB) Downloaded 148 times
@perdido
I make a mockup test by modifying the f2fs installer script to detect hard drives instead of usb flashdrive for installing tazpuppy; suprisingly, the script works nicely and boots. Could you test this script to other usb flash drive?
I make a mockup test by modifying the f2fs installer script to detect hard drives instead of usb flashdrive for installing tazpuppy; suprisingly, the script works nicely and boots. Could you test this script to other usb flash drive?
- Attachments
-
- f2fs-usb-installer.zip
- remove .zip extension
- (20.49 KiB) Downloaded 93 times
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
extlinux.confmistfire wrote:@perdido may I see the content of your extlinux.conf file?
Code: Select all
PROMPT 0
TIMEOUT 20
DEFAULT /
MENU TITLE Puppy Linux
LABEL tazpup
MENU LABEL tazpup 5.0
KERNEL /tazpup_5.0/vmlinuz
APPEND initrd=/tazpup_5.0/initrd.xz pmedia=usbflash psavemark=2 psubdir=tazpup_5.0
MENU SEPARATOR
LABEL hd
MENU LABEL Boot from 1st HD
localboot -1
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Still get errors here.mistfire wrote:@perdido
I make a mockup test by modifying the f2fs installer script to detect hard drives instead of usb flashdrive for installing tazpuppy; suprisingly, the script works nicely and boots. Could you test this script to other usb flash drive?
I wrote just the iso image to cd disc and verified the .iso md5
then tried an install to both usb hdd & usb flash stick using .iso as source, got errors trying to boot both. Got same boot error for both.
Errors and logs next.
Error for usb hdd & usb flash stick are as follows.
Same error for both usb-hdd & usb-flash
Code: Select all
boot:
Invalid or currupt kernel image
Code: Select all
root@TazPuppy:~# /usr/bin/f2fs-usb-installer
yes
syslinux is /bin/syslinux
======================
exist_func
======================
e=/dev/sdd2|f2fs|12617728
1 + 0 = 1
/dev/sdd1 /dev/sdd2
======================
func_gui1
======================
e=No f=Yes 1= 2=
/dev/sdd
Unknown HZ value! (80) Assume 100.
======================
libparted : 3.2
======================
mbr drive found
umount: /mnt/f2fs1: target is busy.
======================
mbr_func
======================
1+0 records in
1+0 records out
446 bytes copied, 0.000118381 s, 3.8 MB/s
1+0 records in
1+0 records out
440 bytes copied, 0.0604464 s, 7.3 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 403: 15581 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 611: 18812 Terminated /usr/lib/gtkdialog/box_splash -close never -text "$SYSPLASH $dev1"
EXIT=" Ok "
root@TazPuppy:~#
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! (93) Assume 100.
======================
libparted : 3.2
======================
mbr drive found
======================
mbr_func
======================
1+0 records in
1+0 records out
446 bytes copied, 0.000132908 s, 3.4 MB/s
1+0 records in
1+0 records out
440 bytes copied, 0.0641471 s, 6.9 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 403: 17997 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 611: 21347 Terminated /usr/lib/gtkdialog/box_splash -close never -text "$SYSPLASH $dev1"
EXIT=" Ok "
root@TazPuppy:~#
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
To have all testing procedures for the TazPuppy Beta 41 f3fs-usb-installer in one place.
Consolidation is to confirm that I have done the required system modifications just in case I missed something.
This is what I have done to prepare the TazPuppy Beta 41 for doing this testing. All md5-hash sums verified.
Installed TazPuppy Beta 41 to usb stick, it is booting from usb stick ok
Create save directory
Installed missing package f2fs-tools package
Re-installed syslinux package using this command from the terminal
Verified those packages have been added.
That is all the preperation for the working TazPuppy Beta 41 I am using to run f2fs-usb-installer script.
The script has been downloaded from this thread and renamed dropping the zip extension
Then the script is made executable and copied to the working usb TazPuppy Beta 41 save directory on my boot device.
The script is launched from terminal /usr/bin/f2fs-usb-installer
Partitions on usb media I am installing to are freshly created each install attempt.
First partition is 32MB ext2 partition with boot flag set
Second partition is f2fs that uses the rest of space on usb stick
Install procedure attempted
1. Boot TazPuppy (has all updates listed above)
Login root Password root
2. Open terminal and run script /usr/bin/f2fs-usb-installer (updated to latest test script - copied to working TazPuppy Beta 41 save file /usr/bin/
3. Choose where to install to
4. Create or verify the partitions on the install-to drive/media then close GParted
5. Choose where to copy install files from (I have been using both an .iso file and install cd)
6. After install finishes copy terminal output to file (to put in thread if necessary)
7. Shut down test computer, remove all plugin media devices and try to boot newly created usb stick.
8.Report back here
.
Consolidation is to confirm that I have done the required system modifications just in case I missed something.
This is what I have done to prepare the TazPuppy Beta 41 for doing this testing. All md5-hash sums verified.
Installed TazPuppy Beta 41 to usb stick, it is booting from usb stick ok
Create save directory
Installed missing package f2fs-tools package
Re-installed syslinux package using this command from the terminal
Code: Select all
tazpkg -gi syslinux --forced
That is all the preperation for the working TazPuppy Beta 41 I am using to run f2fs-usb-installer script.
The script has been downloaded from this thread and renamed dropping the zip extension
Then the script is made executable and copied to the working usb TazPuppy Beta 41 save directory on my boot device.
The script is launched from terminal /usr/bin/f2fs-usb-installer
Partitions on usb media I am installing to are freshly created each install attempt.
First partition is 32MB ext2 partition with boot flag set
Second partition is f2fs that uses the rest of space on usb stick
Install procedure attempted
1. Boot TazPuppy (has all updates listed above)
Login root Password root
2. Open terminal and run script /usr/bin/f2fs-usb-installer (updated to latest test script - copied to working TazPuppy Beta 41 save file /usr/bin/
3. Choose where to install to
4. Create or verify the partitions on the install-to drive/media then close GParted
5. Choose where to copy install files from (I have been using both an .iso file and install cd)
6. After install finishes copy terminal output to file (to put in thread if necessary)
7. Shut down test computer, remove all plugin media devices and try to boot newly created usb stick.
8.Report back here
.
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Hi mistfire,mistfire wrote:@perdido
let's test the bootloader first.
1. Replace the tazpuppy kernel file with kernel file of other puppies
2. Get the corresponding zdrv file of the other puppy and rename it as zdrv_tazpup_5.0.sfs and replace with existing tazpuppy zdrv file.
Then try to boot
I will *guess* you are referring to the working install I am using since the finished product of f2fs-usb-installer has never contained a zdrv
ok I will test the bootloader of the working TazPuppy B41 I am using to run the f2fs-usb-installer script. Will use bionicpup 32-bit as donor.
.