[CLOSED] ScPup64 SlackwareCurrent Woof-CE build 06-Aug-2022

[gyrog]

I have uploaded 'efibootmgr-20191011_e8ce9fe-x86_64-4.txz' and 'efivarfs-1.pet' files to https://www.mediafire.com/folder/00irfyzi4ghio/mokutil.

You can use ScPup64_21.04 to run the uefi utilities 'efibootmgr' and 'mokutil' by doing the following:

Download 'efivarfs-1.pet'
Click on the downloaded file to install 'efivarfs'.

Download 'efibootmgr-20191011_e8ce9fe-x86_64-4.txz'
Click on the downloaded file to install 'efibootmgr'.
It can be used to manage the uefi/BIOS "Boot Menu".
Handy if you intend to install grub2 to the Windows fat32 boot partition using FrugalPup v27, or newer.

Install 'mokutil' using the "Package manager".
(It can easily be found by entering 'mokutil' in the search field.)
It helps to manage the MOKs (Machine Owner Key) enrolled on a uefi machine.

Of course these utilities only work if you have booted ScPup64 via uefi.

[Clarity]

Understanding that this PUP has couple missing components, has anyone tried to install Chrome from the Menu's Wizard on a pristine version? If so, did it start after install?

Also, I await the next ISO build as I think it will resolve the couple issues.

AND, THANKS for the @gyrog upgrades which has certainly improved booting the ISO and save-session management!

[ozsouth]

@Clarity - I did get peebee's chrome64 to run via Internet menu 'get browser' option. Needed to load it & then run from Internet menu. Had to unload it to reboot a live version of this pup.

[peebee]

withdrawn

[Clarity]

Hi @peebee

Couple questions:

• Is that delta, mentioned in above post, to be applied to this distro? (seems to target LxScPup)

• And which ISO should I apply it to? (I do see it mentions the base ISO 21.0 vs 21.0+4)

Thanks

[peebee]

Hi @peebee

Couple questions:

• Is that delta, mentioned in above post, to be applied to this distro? (seems to target LxScPup)

• And which ISO should I apply it to? (I do see it mentions the base ISO 21.0 vs 21.0+4)

Thanks

Oops sorry - yes - haven't done +3 for ScPup64 yet.............

[watchdog]

ScPup64 21.04: abiword aborted with it locale. I'm using en_US locale.

Code: Select all

#!/bin/sh
export LANG=en_US.UTF-8
abiword-exec "$@"

[mistfire]

@peebee
Did you try to connect mtp device in ScPup64 using pupmtp? I noticed that simple-mtpfs on ScPup64 unable to mount MTP devices, it always threw "LIBMTP PANIC" error. You can try that by launching pupmtp from terminal and watch the error messages appear on the terminal

[peebee]

@peebee
Did you try to connect mtp device in ScPup64 using pupmtp? I noticed that simple-mtpfs on ScPup64 unable to mount MTP devices, it always threw "LIBMTP PANIC" error. You can try that by launching pupmtp from terminal and watch the error messages appear on the terminal

No ................ but @Marv has reported:
viewtopic.php?p=26239#p26239

Does Slack64-8.n behave better?

[Marv]

@peebee
Did you try to connect mtp device in ScPup64 using pupmtp? I noticed that simple-mtpfs on ScPup64 unable to mount MTP devices, it always threw "LIBMTP PANIC" error. You can try that by launching pupmtp from terminal and watch the error messages appear on the terminal

No ................ but @Marv has reported:
viewtopic.php?p=26239#p26239

Does Slack64-8.n behave better?

It does for me. I just downloaded it from github, pristine frugal booted on my i5 based laptop, and it detects and connects correctly to my Open Source Android LG L125DL flip. Thanks for the pointer @peebee

[peebee]

@peebee
Did you try to connect mtp device in ScPup64 using pupmtp? I noticed that simple-mtpfs on ScPup64 unable to mount MTP devices, it always threw "LIBMTP PANIC" error. You can try that by launching pupmtp from terminal and watch the error messages appear on the terminal

@mistfire and @Marv

pupmtp seems to work fine with my Android phone on both ScPup64-21.04+3 and LxPupSc64-21.04+3 ...............

.

Screenshot1.png (141.62 KiB) Viewed 6378 times

.

Screenshot2.png (123.76 KiB) Viewed 6378 times

[Marv]

@peebee, Tested here in a frugal pristine boot of LxPupSc64 21.04 +3 on the i5 based Fujitsu S761 laptop. Generated the +3 iso from the delta, checksum correct. The Android based flip connects perfectly. Posting from ungoogled-chromium 90.1 in that install now. Reversion to the 2.68.2 glib2 observed. That the key?

Update: Also tested in an update of my savefile based LxPupSc64 21.04 +2 install, so far with the 5.12.4 kernel, on the hardware above. Fine there also.

Thanks

[peebee]

Reversion to the 2.68.2 glib2 observed. That the key?

Jolly good!

Don't think there has been a "reversion"......
Nothing showing in http://ftp.slackware.com/pub/slackware/ ... ngeLog.txt

The build history shows:
glib2|glib2-2.66.2-x86_64-1.txz
glib2|glib2-2.66.3-x86_64-1.txz
glib2|glib2-2.66.4-x86_64-1.txz
glib2|glib2-2.66.4-x86_64-2.txz
glib2|glib2-2.66.7-x86_64-2.txz
glib2|glib2-2.66.8-x86_64-2.txz
glib2|glib2-2.68.0-x86_64-1.txz
glib2|glib2-2.68.1-x86_64-1.txz
glib2|glib2-2.68.2-x86_64-1.txz

Bit of a mystery! Hopefully solved!

[Marv]

Don't think there has been a "reversion"......
Nothing showing in http://ftp.slackware.com/pub/slackware/ ... ngeLog.txt

The build history shows:
glib2|glib2-2.66.2-x86_64-1.txz
glib2|glib2-2.66.3-x86_64-1.txz
glib2|glib2-2.66.4-x86_64-1.txz
glib2|glib2-2.66.4-x86_64-2.txz
glib2|glib2-2.66.7-x86_64-2.txz
glib2|glib2-2.66.8-x86_64-2.txz
glib2|glib2-2.68.0-x86_64-1.txz
glib2|glib2-2.68.1-x86_64-1.txz
glib2|glib2-2.68.2-x86_64-1.txz

Bit of a mystery! Hopefully solved!

I misspoke re 'reversion', actually the glib2 version went from 2.66.2 in LxPupSc64 20.06 +2 (connection worked) to 2.68.0 in LxPupSc64 21.04 and 21.04 +2 (connection failed) to 2.68.2 in +3 where connection worked again. My guess is that's it. I'm just glad to have the MTP connection working again. I actually use it fairly often for the new-to-me Android flip, which also tethers admirably

Cheers,

[Clarity]

@Marv, I see you've connected your Flip to a PC via USB.

• Is the PC a desktop or laptop?

• If a desktop, does the PC have Wifi ability?

Your post raises some ideas.

[Marv]

@Clarity The PCs I run are 2nd gen i5 based laptops, all intel. They have wifi but to transfer images I connect the LG L125DL (A fliphone running Open Source Android) by usb. I haven't tried bluetooth though both the laptops and phone support it in principle. Though it's a humble flip, the phone also supports tethering (being a wifi hotspot) and I have used that to support my laptop when a tree severed our DSL line. Just set the phone tethering up WPA2 with the same house password as my wireless router. Works slick and quite adequate speed for emergency use. Some of my pups use SNS for connection, most use PeasyWiFi 4.6. All connect flawlessly when tethering is turned on on the phone.

[Clarity]

@Marv, Thanks. my reply could be viewed as a diversion on this thread, so I am PM'ing you to share how I use my cell-phone in my network that you might find of interest.

Again, thanks for sharing that scenario.

[darry19662018]

I have a CQ61 using this Puppy I had to swap for fossapup's kernel to get SCPup to have sound and shutdown properly with a savefile.

Using 5.11 kernel that comes with it causes this problem.....
viewtopic.php?f=6&t=3036&p=26320#p26320
can't reboot and use save-file adding .... modprobe.blacklist=snd_hda_codec_idt to end of kernel line enables me to reboot with savefile but when I boot to a desktop there is no desktop - so had to use a kernel I know works not a 5.11----------------- series kernel.

Basically any current Puppy is going to give me this trouble.

[peebee]

a4021f77d6d325b0a1096b31e2b24ffb ScPup64-22.02+0-T.iso

see post #1

[one]

Hi @peebee,

ScPup64 22.02 build of 02162022 (k5.15.23) doesn't boot on my 10 years old ACER 5745G (ext. SSD/grub4dos).
I switched to kernel 5.16.5-lxpup64 and it boots fine.

ScPup64 21.04 +4 with kernel 5.11.11 runs ok.

The 5.15.x kernel line does not seem to like this laptop ...

peace

[peebee]

ScPup64 22.02 build of 02162022 doesn't boot

Any clues as to why it doesn't boot?

5.15 is a Woof-CE kernel-kit build and any problems need to be reported on GitHub (@dimkr)

[one]

hI @peebee,

Probing EDD (edd=off to disable) --> ok

Waiting for partition [........-,,,,-....-...............] on sdb2/ext4
--> partition not found!
--> puppy_scpup64_22.02.sfs not found!

Dumping last line ...

...............................................................................
grub4dos/menu.lst (on sdb1/FAT32)

title TEST-ScPup64 22.02 +0 (sdb2/scpup64-22)
find --set-root uuid () aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
kernel /scpup64-x/vmlinuz pdrv=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee psubdir=/scpup64-x pmedia=usbflash pfix=fsck
initrd /scpup64-x/initrd.gz
...............................................................................

I tried "edd=off" on the kernel line, but no difference.

peace

PS: sorry, but debugsave doesn't save "zz_initrd_tmp" on sdb1, so I cannot provide that ...

[OscarTalks]

Now testing 22.02+0 manual frugal to hdd
It boots successfully on my test machine
The notification about probing edd is there but does not cause a problem, I think you can just ignore it
It appears with some of the other WoofCE Pups now (eg VanillaDpup)
Adding edd=off to kernel line removes the notification if desired.

One thing I have noticed with ScPup64 (but not with ScPup32) is that PSIP does not start
psip: symbol lookup error: psip: undefined symbol: EVP_CIPHER_CTX_init
So maybe openssl library mismatch? Not sure why and why only with 64bit?

Ah, is the kernel headers package no longer needed?

[watchdog]

One thing I have noticed with ScPup64 (but not with ScPup32) is that PSIP does not start
psip: symbol lookup error: psip: undefined symbol: EVP_CIPHER_CTX_init
So maybe openssl library mismatch? Not sure why and why only with 64bit?

Yes, I confirm. I have a psip-1.42-x86_64.pet package which works.

Screenshot.png (73.68 KiB) Viewed 5937 times

[norgo]

@OscarTalks
Oh yes I remember when tried to build psip for SLC64.
I had massively problems to build psip because pjproject, osxcart and as you wrote openssl doesn't match anymore.
Thats why I used older versions of the needed components and built a statically version of psip from source.
There is a good chance, that the static version is working in ScPup64 too.

@watchdog
the 64bit version of psip is working for you?

[watchdog]

@watchdog
the 64bit version of psip is working for you?

psip-1.42-x86_64.pet:

https://drive.google.com/file/d/1Y6BS6Y ... sp=sharing

This one from 2018 is working for me. I do not remember where I found it. It probably was by @jamesbond in fatdog64.

[thinkpadfreak]

Hello.

ScPup64 22.02 does not boot from the ntfs partition of my machine (ThinkPad L440), but it boots from the ext2 partition of the same machine.

I also used ScPup64 21.04, and it booted from the ntfs partition of the same machine.

[peebee]

Booting problems: kernel: I have switched over to using the Woof-CE kernel-kit automatic builds...... these are however based on different configs from Debian and as a result may not be as good a match to Puppy's boot sequences - if you have problems I suggest to use a different kernel - but also ask for problems to be reported back to GitHub Woof-CE so that the configs can be "improved".

Devx: yes this does now contain the Slackware Current kernel headers..... for various reasons: 1. the kernel-kit builds do not produce kernel headers; 2. Woof-CE petbuilds require the kernel-headers in the devx.

pSip are both same era so should behave the same:
32-bit: :psip:|pet|Packages-puppy-slacko14.2-official|psip-1.41-i686_s700|psip|1.41-i686_s700||internet|3604||psip-1.41-i686_s700.pet|+osxcart|Psip is a sip phone application especially developed for Puppy Linux|slackware|14.2||

64-bit: :psip:|pet|Packages-puppy-slacko6414.2-official|psip-1.41-x86_64_s700|psip|1.41-x86_64_s700||internet|3500||psip-1.41-x86_64_s700.pet|+osxcart|Psip is a sip phone application especially developed for Puppy Linux|slackware64|14.2||

Can somebody test:
psip-1.42a-x86_64_s80.pet 2021-Feb-27 16:14:58 753.6K

[watchdog]

Can somebody test:
psip-1.42a-x86_64_s80.pet 2021-Feb-27 16:14:58 753.6K

It starts but does not login in diamondcard.us (ex ekiga call out). I'm under NAT so I do not know if the package can work in other context. My above package is tested ok. I have found the origin: http://smokey01.com/software/internet/p ... x86_64.pet

[OscarTalks]

PSIP is built using a pjproject which is a few years old and this pjproject does not like the much newer openssl-1.1.1 which is in most of the newer Puppies these days including ScPup.
When compiling pjproject the ./configure script output includes:-
checking for SSL_library_init in -lssl... no
** OpenSSL libraries not found, disabling SSL support **
Even though the (too new) openssl libraries are installed
So the autodetect just disables ssl in the build and proceeds
I have not been able to find a way to force openssl-1.1.1 to link to pjproject 1.16
All the things I do with PSIP still work
I am not sure in what situations openssl support is needed.
If you build pjproject and PSIP in an earlier Puppy, the older openssl is enabled, but then trying to run that in a newer Puppy might be what causes mismatches