ScPup & ScPup64 - Slackware Current based Woof-CE pups

Message

peebee · #1 Post by **peebee** » Wed 26 Dec 2018, 07:37

13-Jun-2020

32-bit
487e9b2bb5ff36cfedcc6c4acb74a8af ScPup32-20.06+0-T.iso

{delta update} - must be applied to the base 487e9b2bb5ff36cfedcc6c4acb74a8af ScPup32-20.06+0-T.iso

Updates are cumulative - only the most recent needs to be applied.

Kernel 5.4.46 32-bit pae
BUILD_FROM_WOOF='testing;b4e0501e2;2020-06-13 10:55:44 +1000'
Built from same Slackware Current components as LxPupSc but no LXDE
Similar look and feel to upupbb / upupdd
Minimal Light webbrowser in adrv - full size browsers from: https://sourceforge.net/projects/lxpup/ ... /browsers/

See next post for 64-bit

peebee · #2 Post by **peebee** » Wed 26 Dec 2018, 07:37

13-Jun-2020

64 bit
8dd31b7255a1320620f245d338467e51 ScPup64-20.06+0-T.iso

{delta update} - must be applied to the base 8dd31b7255a1320620f245d338467e51 ScPup64-20.06+0-T.iso

Updates are cumulative - only the most recent needs to be applied.

Kernel 5.7.2 64-bit
otherwise same as 32-bit version

Full size browsers from:
https://sourceforge.net/projects/lxpup/ ... /browsers/

peebee · #3 Post by **peebee** » Wed 26 Dec 2018, 07:37

32 bit development files

64 bit development files

32-bit compatibility sfs for 64-bit

https://sourceforge.net/projects/lxpup/ ... LXQt-ydrv/

ydrv's to change ScPup 32 & 64 to the LXQt desktop

https://sourceforge.net/projects/lxpup/ ... LXDE-ydrv/

ydrv's to change ScPup 32 & 64 to the LXDE desktop - i.e. equivalent to LXPupSc and LxPupSc64

ally · #4 Post by **ally** » Wed 26 Dec 2018, 11:08

mirrored here: http://archive.org/details/Puppy_Linux_Slacko here: http://archive.org/details/Puppy_Linux_Spup and here: http://archive.org/details/Puppy_Linux_Slacko64

recobayu · #5 Post by **recobayu** » Thu 27 Dec 2018, 12:20

Where is the devx?

Thank you..

peebee · #6 Post by **peebee** » Thu 27 Dec 2018, 16:45

recobayu wrote:Where is the devx?
Thank you..

see post #3

musher0 · #7 Post by **musher0** » Thu 27 Dec 2018, 17:33

peebee requested of me by PM that I bring this post in this thread.
Sorry for any previous confusion.

To be clear, I should mention that I did the pupsave import test after the
installation of the ScPup, after the creation of ScPup's own pupsave. The
ScPup has its own problems. They were there, I did not import them,
i simply uncovered them.

~~~~~~~~~~~

peebee wrote:ScPup - Slackware Current based Puppy

Hi peebee.

I did have a look and it pretty much has the quirks of its "dad". Plus a
couple of its own...

Good news first: it did convert the pupsave from slacko-6999 without
problems though. That saved me some time.

Now the bad news: Bash keeps telling me that variable LC_TIME=
fr_CA.utf8 in /etc/profile.local is an error. I have been using this file to
define my LANG parameters in all my Puppies, and I have never ever
had that error before.

Also, is it possible that you slackers are now using a modified or updated
ROX? 01micko's didn't allow me to copy within the same directory, but
yours won't even allow me to link within the same directory.

The timesync.sh script is useless in your slacko, forgive me for being so
frank. When one wants to update the time, it compares nothing with
nothing. Literally: the before and after time comparison boxes are empty.

And would you believe that Dougal's Connection Wizard has become iffy?
Of course if the connection wizard is not doing a proper job, the timesync
can't sync the time from the Internet.

I considered for a couple of minutes compiling an ntp utility for these
slackos (there's a short, user, version). The one that I had compiled for
the upups is missing a libdns library on the slacko.

Plus, the idea of recompiling a decent WM (the new jwm is still the pits),
plus hunting down a decent replacement for this byzantine new ptheme
stew... Plus, since it comes with no themes worthy of the name (IMO),
that means more hunting.

So... no offense intended, and again sorry for being so frank, but the
idea of reinventing the wheel came to mind, and my motivation went flat.
Until you or 01micko or someone else finishes debugging those animals,
I'll stick with my trusty old xenial-706_32-bit.

BFN.

peebee · #8 Post by **peebee** » Thu 27 Dec 2018, 19:39

Hi Musher0

language and timesynch - I suspect your "patches" are incompatible with recent Woof-CE changes - please try to use the utilities provided in the menu instead and confirm whether they work. I was able to set locale to fr-CA no problem and to Psync also with no problem.

rox is a new version with some ui changes - http://blog.puppylinux.com/puppy-specif ... ing-branch

rox link in the same directory works fine.

netwiz also works fine for me.

JWM and pTheme - whether you like them or not is personal preference not a bug - if you don't like them then you probably should be using something else. JWMDesk manager is however provided in ScPup as an alternative to pTheme.

Cheers!
peebee

musher0 · #9 Post by **musher0** » Thu 27 Dec 2018, 20:39

Thanks for your reply, peebee.

As to my LC_TIME problem, it vanished during this second session. Perhaps
it was a glitch the first time around in my /etc/profile.local file.

The PSync utility timesync.sh however was not in ~/Startup, and nowhere
to be found, it seems. I had to provide my own script based on htpdate.
(Pls see here.)

I think your statement "if you don't like utility X in Puppy Z, don't use
Puppy Z" is a bit of an over-reach? IMO, If utility X is badly designed,.
either programmatically or for the user's perception/usage, it is badly
designed, no matter the Pup. The Pup it's used in has nothing to do with it.

As to the copy and link from ROX within a directory, I still get no response
with the usual mouse controls. I have to highlight the file AND the
command in the ROX sub-menu, and then hit the Enter key on the
keyboard. I'd double-check my mouse, except my mouse left-click button
is not being so fussy in other Pups.

Your PDrive version has a label error: the optical and usbdrive labels
should be switched. (Pls see attached.)

Also included is a scrot of this 2nd session. Much nicer experience this
time around, I must say.

BFN.

bigpup · #10 Post by **bigpup** » Thu 27 Dec 2018, 22:45

ScPup64
Frugal + save folder

Thanks for offering this to Puppy Linux!!

You really need to get the naming of all main files to be scPup.

This is usually no problem in other Puppies.

Using WIFI connecting to my network.

This is not wanting to connect with my WIFI network adapter.

Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev c3)
It uses the Kernel Driver: iwlwifi

Using the Network Wizard
It says no device found.
I try loading the iwlwifi module, but it still says no device found.

I see that the needed stuff is in the zdrv.sfs.
The boot process says the zdrv.sfs is being loaded.

peebee · #11 Post by **peebee** » Thu 27 Dec 2018, 23:11

[quote="bigpup"][/quote]
Naming will be sorted later....

wifi - Probably missing firmware - what clues in dmesg?

peebee · #12 Post by **peebee** » Thu 27 Dec 2018, 23:13

musher0 wrote:The PSync utility timesync.sh however was not in ~/Startup, and nowhere to be found, it seems.

No longer that mechanism....
now /etc/init.d/psync
see enable_psync() {
in
/usr/sbin/psync

Terry H · #13 Post by **Terry H** » Fri 28 Dec 2018, 00:26

bigpup wrote: Using WIFI connecting to my network.

This is not wanting to connect with my WIFI network adapter.

Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev c3)
It uses the Kernel Driver: iwlwifi

I'm not on my PC with 7260 wifii at present, however looking at the fdrv included with ScPup it does not have valid firmware to cover the intel-7260 card, the included firmware is too old for the 4.9.x kernels. With the 4.9.x kernel, I use iwlwifi-7260-17.ucode. The fdrv only includes upto iwlwifi-7260-10.ucode, which isn't being found.

Code: Select all

dmesg | grep wifi

This will identify the firmware that is being attempted to be loaded.

If you have a working puppy using a 4.9.x kernel, copy the working the iwlwifi-7260-xx,ucode to /lib/firmware[/code]

peebee · #14 Post by **peebee** » Fri 28 Dec 2018, 09:02

Terry H wrote:I use iwlwifi-7260-17.ucode. The fdrv only includes upto iwlwifi-7260-10.ucode,

iwlwifi firmware is a nightmare!

There are currently 78 versions with a total size of 90MB.

The fdrv has a subset 30 versions making 16.6MB out of the total fdrv size of 19.3MB

For 7260 there is currently -7 -9 -10

I therefore propose to replace -9 with -17 in future builds...........unless somebody says they must have -9

bigpup · #15 Post by **bigpup** » Fri 28 Dec 2018, 16:09

I need iwlwifi-7260-17.ucode.

I may be wrong, but that should be the latest version of the 7260 ucode. There should be support for all 7260 devices in that one ucode.

Bionicpup64 7.9.7 only has iwlwifi-7260-17.ucode.
Everything works OK in it.

I would try just having that one.

I think you only need one iwlwifi ucode for each Intel device.
As long as it is the latest version of that ucode, it should work for all devices of that model number.

watchdog · #16 Post by **watchdog** » Fri 28 Dec 2018, 16:19

Trying to install some software (64 bit version). I have symbols errors about libicui18n. Mtools-4.0.18 does not compile and a my previous version compiled in slacko64-14.2 does not work. Wxcam does not work, too. I have wasted time to install my brother laser printer: slackware does not support foomatic. I have solved with alien packages ending to reuse the expired 64bitinstaller by rcrsn51.

Terry H · #17 Post by **Terry H** » Fri 28 Dec 2018, 18:37

bigpup wrote: I think you only need one iwlwifi ucode for each Intel device.
As long as it is the latest version of that ucode, it should work for all devices of that model number.

As peebee said it's a bit of a nightmare. The problem here is in trying to cater for new and old kernels. The kernels will do a search starting at a firmware version then cycle back, depending on the kernel a variable number of times (I had between 3 and 8 attempts) looking for appropriate firmware. Version 17 will work for current kernels being used (4.9.x > 4.19.x), it may be out of range for earlier kernels.

I ran a lot of tests back in April for a ilwifi-7265, so similar issues with firmware versions, to determine firmware versions required by various kernels. At that time I tested kernels between 3.18.x to 4.15.x.
Link to earlier testing.

bigpup · #18 Post by **bigpup** » Sat 29 Dec 2018, 02:30

The problem here is in trying to cater for new and old kernels.

Why try to do that.
Just support the kernel that is going to be in the ScPup release.

Kernel Release: 4.19.12 is what is in this ScPup64 19.01.
If I understand all you are saying.
The firmware needs to be for that kernel
Anyway, I got the iwlwifi-7260-17.ucode from Bionicpu64 7.9.7 and put it in /lib/firmware.

That fixed my Intel 7260 wifi controller.

Posting this from ScPup64 using that wifi controller.

Terry H · #19 Post by **Terry H** » Sat 29 Dec 2018, 03:38

bigpup wrote: Kernel Release: 4.19.12 is what is in this ScPup64 19.01.
If I understand all you are saying.
The firmware needs to be for that kernel

No, regarding iwlwifi firmware specifically, wifi will only work if the kernel finds firmware within a a set range of versions.

watchdog · #20 Post by **watchdog** » Tue 01 Jan 2019, 15:20

watchdog wrote:Trying to install some software (64 bit version). I have symbols errors about libicui18n. <cut>
Wxcam does not work, too.

Reverting to icu4c-56.1-x86_64-2.txz wxcam works.
I also have a working mtools-4.0.23 built from an alien package. It's a mistery that mtools-4.0.18 compiled in slacko64-700-RC3 does not work.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

ScPup & ScPup64 - Slackware Current based Woof-CE pups

ScPup & ScPup64 - Slackware Current based Woof-CE pups