Page 54 of 60
Posted: Wed 18 Dec 2019, 07:46
by mistfire
@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
Posted: Wed 18 Dec 2019, 09:53
by perdido
mistfire 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
No bootloader menu
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
.
Posted: Wed 18 Dec 2019, 12:08
by mistfire
@perdido may I see the content of your extlinux.conf file?
Posted: Wed 18 Dec 2019, 15:15
by mistfire
@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?
Posted: Wed 18 Dec 2019, 17:12
by perdido
mistfire wrote:@perdido may I see the content of your extlinux.conf file?
extlinux.conf
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
Posted: Wed 18 Dec 2019, 20:23
by perdido
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?
Still get errors here.
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
Terminal output for install to usb hdd
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:~#
Terminal output for install to usb flash
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:~#
Posted: Wed 18 Dec 2019, 21:12
by perdido
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
.
Posted: Thu 19 Dec 2019, 01:31
by mistfire
@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
Posted: Thu 19 Dec 2019, 02:08
by perdido
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
Hi mistfire,
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.
.
Posted: Thu 19 Dec 2019, 02:13
by perdido
Bionicpup32 kernel and zdrv booted to desktop.
All looks ok
Posted: Thu 19 Dec 2019, 02:24
by perdido
Hi mistfire,
Ok since I did not believe you were talking about my working TazPuppy install
I replaced the vmlinuz and copied the zdrv from bionicpup32 to the non working usb-stick that was created with f2fs-usb-installer script.
(The non-working stick has never had a zdrv, not in any of the tests.That confused me.
)
Anyways, the new kernel and zdrv (which is properly renamed) do not boot.
They give the same exact error
Code: Select all
boot:
Invalid or corrupt kernel image
Posted: Thu 19 Dec 2019, 04:30
by didit
mistfire wrote:@diditt I think your appimage file was not 32-bit. Just use 64-bit kernel file and 64-bit zdrv sfs file
I also tried to run this app from slitaz-rolling-core64.and its not working.
Posted: Thu 19 Dec 2019, 09:22
by mistfire
@perdido
The error on the usb installer it become more weird. Unless it was hardware related. I will try to find another usb flash drive to test this thing.
Posted: Sun 22 Dec 2019, 10:02
by mistfire
TazPuppy Beta 42 released
Changes:
* Broken wifi-box is fixed
* Improved networking
* Improved puppy installer
* Improved root account
* Some bugfixes
Download: https://drive.google.com/open?id=16os51 ... tbu3qG1-Kc
MD5 Checksum: aa6d97cac6e250dd5c8a3fd726ac19f4
Build kit:
https://drive.google.com/open?id=1anm5d ... DEb3Vvgm-w
Posted: Mon 23 Dec 2019, 06:59
by zagreb999
mistfire ,
if you wifi connect with
TAZPANEL, can you autoconnect
after reboot?
Posted: Mon 23 Dec 2019, 11:26
by mistfire
zagreb999 wrote:mistfire ,
if you wifi connect with
TAZPANEL, can you autoconnect
after reboot?
Yes it is
Posted: Mon 23 Dec 2019, 21:32
by zagreb999
mistfire
thank you!
Posted: Sat 28 Dec 2019, 06:39
by mistfire
TazPuppy 5.0 beta 43 released
Changes:
* Bugfixes on tazpanel, networking, and tazpkg
Download: https://drive.google.com/open?id=1tny-B ... rPK3qZ2Nnq
MD5 Checksum: 0303a58223a8ec6c790452f94059d3d8
Build kit:
https://drive.google.com/open?id=1SvpLJ ... 1TgHBSr-gK
Posted: Sat 28 Dec 2019, 18:35
by don570
Notes:
-SSH works however there needs to be a utility to scan for addresses
like mpscan or arp-scan
- my wireless mouse (logitech) acts like its battery is worn out
i.e. sometimes there is no response,
however when I use the same mouse in other distros it's fine.
Does anyone else have a problem with a wireless mouse?
Posted: Wed 01 Jan 2020, 14:28
by zagreb999
hi mistfire
is there any chromium 32 bit
browser ?