Page 40 of 68

Firefox 55.0.3 for LxPupSc

Posted: Fri 11 Aug 2017, 09:27
by peebee
I have added firefox-55.0.3-lxsc.sfs to the LxPupSc browsers.....

Have got sound working - needed a sandbox setting (in about:config) added to allow access to alsa -

Code: Select all

defaultPref("security.sandbox.content.write_path_whitelist", "/dev/snd/");
Includes specific to firefox libraries for gtk+3-3.22.19 and apulse-0.1.10

Tested on LxPupSc-17.08.22T - BBC iPlayer and YouTube video playing and file downloads all OK.

Ends up a smaller .sfs than firefox-52.3.0esr - 47MB as against 53MB.

Posted: Sat 12 Aug 2017, 08:29
by peebee
UPDATED 13-aug-2017

Interim delta to LxPupSc-17.08.23T-k64 - kernel 4.12.7-lxpup64

Posted: Sat 12 Aug 2017, 15:57
by Marv
21 updated to 22, then to 23 on the S761 referenced 3 posts up. md5sums all correct, savefile cleaned prior to each update. No hitches or glitches. All the tests run then were repeated and are fine. One of my users has been using 21 for a few days now on a Fujitsu S761 identical to mine. No complaints (once I got the wifi set up correctly :? ) and the newer CUPS in these pups auto-detects their stinky Canon printer and connects/prints well. I do have a little script that quickly prunes the menu quite a bit for her in lieu of the XFCE Whiskermenu. I haven't yet gotten the older X-slacko or X-tahr to see that Canon yet on wireless laptops cause Canon uses a (to me) squirrely mac address search schema. It prints ok in all from a wired desktop there. Slimjet 15.0.3.0 and 15.0.4.0 from OscarTalks i686 SFS and the inbuilt Sylpheed used throughout.

Thanks,

Updated August 14: The 23 install on the S761 above was updated to the newer 23 with the 4.12.7 kernel. Everything remains solid there. I also moved that install to my NAS box to check it out there, an ethernet connected intel Bay Trail based desktop. In general I have been running X-Slacko 4.2 on my two Bay Trail boxes as it just works. LcPupSc 17.08.23 is also currently running with no problems on that hardware. It is samba sharing a drive partition and an elderly USB connected Epson CX5400 from that box. Peasyscan and iscan on that machine also see both the Epson CX5400 and the networked HP4500 All-In-Ones scanner functions. Runs 24/7 with roughly a 14 watt draw, not too bad for a desktop.

Posted: Fri 25 Aug 2017, 08:12
by peebee
updated 26-aug-2017

Interim delta to LxPupSc-17.08.25T-k64

System: Kernel: 4.12.9-lxpup64 x86_64 (64 bit gcc: 5.3.0)
Desktop: LXDE (Openbox 3.6.1) dm: N/A Distro: LxPup-Sc 17.08.25
Info: Processes: 135 Uptime: 2 min Memory: 162.2/3705.6MB
Client: Shell (bash 4.4.121 running in lxterminal) inxi: 2.3.8

Posted: Fri 25 Aug 2017, 09:13
by Rangan Masti
Hi, good morning!
I just wanted to compile the Kernel 4.12.9!!! Thank you and have a nice day!

Rangan

Posted: Wed 30 Aug 2017, 14:53
by B.K. Johnson
Hello peebee
You wrote:
Have got sound working - needed a sandbox setting (in about:config) added to allow access to alsa -
Code:
defaultPref("security.sandbox.content.write_path_whitelist", "/dev/snd/");
Can you please elaborate on how to do this. I manually installes Firefox-55.0.3 on tahr-6.0.6 32bit. I opened up about:config but did not see a defaultPref setting. Is yours a new setting to be added?

Posted: Wed 30 Aug 2017, 15:26
by peebee
B.K. Johnson wrote:Can you please elaborate on how to do this.
Watchdog has suggested this: http://www.murga-linux.com/puppy/viewto ... 839#965839

I did it slightly differently with ff4lxpup.cfg in /usr/lib/firefox
and
local-settings.js in /usr/lib/firefox/defaults/pref

You can see the contents of these files if you download my firefox .sfs

LxPupSc-17.09.1T-k64

Posted: Fri 01 Sep 2017, 21:46
by peebee
LxPupSc-17.09.1T-k64 is a 32-bit woof-ce 'testing' branch build with a 64-bit kernel (therefore only compatible with 64-bit capable processors)

LxPupSc-17.09.1T-k64.iso {devx} - (devx does not include kernel sources or headers) {kernel 4.12.10-lxpup64 sources}
iso md5 = 1bd8cb1af14302e74848d2a7eb3c1ae7

Delta from 17.08.1T is available

- kernel 4.12.10 64-bit (alternative 32-bit kernels 3.16.x 4.4.x & 4.9.x also available - all need firmware in the fdrv)
- Made from Slackware-14.2/current as of Wed Aug 30 22:34:34 UTC 2017
- BUILD_FROM_WOOF='testing;528129b;2017-08-30 23:00:49 +0100'
- web browser in adrv is light-48.0
- firmware is in fdrv (updated)
- alternative fall-back xorg is in ydrv (no need to install unless needed)

**N.B. the 64-bit kernel means that any kernel drivers have to be built in a true 64-bit system - slacko64 with it's own devx is suggested but use the kernel sources above

Woof-CE build repository is: http://smokey01.com/peebee/slackocurrent/

Chromium, Firefox, Palemoon and Seamonkey are in the repository and installable via Internet -> Get Web Browser

The versions of the browsers as of 25-aug-2017 with their md5sums are:

chromium-60.0.3112.113+pepper_26.0.0.151 :25fb3ea8e083304ba32cc9ef2fea3db0
firefox-52.3.0esr :aad35e41e181ce09b89c01760b7fdc57
palemoon-27.4.2 :05fb210ebd4d3eef01d615430d516a69
seamonkey-2.48 :05b91afef8b60bda21343a45da0aae49

Posted: Sat 02 Sep 2017, 14:16
by mistfire
@peebee does your lxpupsc kernel supports on hibernation/suspend-on-disk?

Posted: Sat 02 Sep 2017, 15:17
by peebee
mistfire wrote:@peebee does your lxpupsc kernel supports on hibernation/suspend-on-disk?
Don't know - supports laptop suspend on lid closure - that what you mean?
Why not try it and see??

Posted: Sat 02 Sep 2017, 16:05
by mistfire
I mean if the lxpupsc kernel can suspend session to disk. It means all the contents of the ram went to the swap partition. And reload it back to ram if the computer is resume. This feature is applicable if the laptop is running out of battery. The suspend that you talked about was only sleep mode

I try acpitool but hibernate does not work

Posted: Sat 02 Sep 2017, 16:21
by peebee
mistfire wrote:I mean if the lxpupsc kernel can suspend session to disk. It means all the contents of the ram went to the swap partition. And reload it back to ram if the computer is resume. This feature is applicable if the laptop is running out of battery. The suspend that you talked about was only sleep mode

I try acpitool but hibernate does not work
The DOTconfig file says:
# Power management and ACPI options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set

so I guess not....

Posted: Sat 02 Sep 2017, 21:40
by mistfire
@peebee can you provide lxpupsc kernel with hibernation support on your next release?

Posted: Sat 02 Sep 2017, 23:33
by Marv
LxPupSc-17.08.24T-k64 updated to LxPupSc-17.09.1T-k64 on a core 2 duo laptop (Fujitsu S6520) and a 2nd gen i3 laptop (Fujitsu S761). Both are frugal Grub4Dos installs to a fat32 boot partition on SSDs. Used the 17.08.1 to 17.09.1 delta, md5sum of iso generated correct. Ran the usual CD and DVD autoplay tests correctly. glxgears FPS excellent on both, sound, video, wireless connection with SNS and PWF ok, as is yassm 4.1 and redshift. I don't load the adrv as Slimjet 15.1.0.0 from SFS suits me fine at this time. Suspend to RAM is working both from session manager and lid. Haven't done the BayTrail desktop yet.

I do run a modified /etc/acpi/actions/suspend.sh file, kind of a work in progress. It's necessary on the i3 laptop in LxPupSc and on X-slacko 4.3 to get correct touchpad and button mappings on resume. The presuspend cleanup just gets the dialogs to display before suspend when using the session suspend tab in the LxPups and the Openbox case on recovery has worked flawlessly on all my hardware for the last 4 or 5 LxPups. I continue to work on the xfce case to try to get the Xfce4 pups to resume without a restartwm on the i3 so far without sucess. Many combinations of the XFCE4 session startups, xfdesktop.. tried. The only thing so far that works on all of the hardware is a restartwm. I don't use jwm but did do a brief check on slacko 6.9.9.9. I like to have the lidsuspend working on my stable of laptops as it's the carrot that gets the laptop shut after use. The laptop is a lot tougher closed than open. Think kids, coffee, dogs, cats and lots else. Alas, but suspend/recovery seems to remain quite hardware dependent.

Posted: Sun 03 Sep 2017, 06:17
by peebee
mistfire wrote:@peebee can you provide lxpupsc kernel with hibernation support on your next release?
The 3.16.x alternative kernel does seem to have hibernation configured if you want to try it....

Posted: Sun 03 Sep 2017, 06:22
by mistfire
@peebee where I can find that kernel alternative (precompiled not source code)?

Posted: Mon 04 Sep 2017, 16:21
by peebee
Interim delta to LxPupSc-17.09.21T-k64 - kernel 4.13.0-lxpup64 with hibernation enabled as requested (hopefully)....

Posted: Wed 06 Sep 2017, 09:44
by mistfire
@peebee you forgot to compile a 32-bit version of that kernel.

Posted: Wed 06 Sep 2017, 13:30
by Marv
:) LxPupSc-17.09.1T-k64 Grub4Dos frugal install on the S761 laptop above updated to LxPupSc-17.09.21T-k64 using the delta. md5sum of the iso generated is correct, video, sound, PWF 4.5 wireless connection, lid and button suspend to RAM, redshift, Slimjet 15.1.2.0 from SFS (I run Ghostery and Click&Clean on it), glxgears FPS (at 10,000) all are good. CD (Mahler :) ) and DVD (The adventures of Milo and Otis :lol: ) mount and play tested and continue to work correctly. CPU at idle is at 1 to 2% and base memory use is roughly 120Mb on this hardware and install. I really haven't noticed any change in that as you have worked through the 4.9 to 4.13 kernel range. I am using Yassm 4.1 to connect to the NAS box currently running 17.08.24T and X-Slacko 4.3 alternately as I chase a large (0.5 Gb +) file transfer quirk, probably disc cache related. The PcManFm tools also connect correctly but I haven't yet gotten it to remember my password so lazyfingers prefers Yassm.

I'm using and updating the 2nd gen i3 based Fujitsu laptop first partly cause I love it and also because it seems to be much more particular hardware wrt timing/boot/suspend/Fn buttons/touchpad than either the core 2 duo laptops or the Bay Trail desktops are.

Cheers,

Posted: Wed 06 Sep 2017, 14:38
by rcrsn51
Marv wrote:I am using Yassm 4.1 to connect to the NAS box currently running 17.08.24T and X-Slacko 4.3 alternately as I chase a large (0.5 Gb +) file transfer quirk, probably disc cache related.
I'm guessing that this is over WiFi? I have had problems with this in the past.

It isn't a YASSM issue - YASSM just uses the mounting tools provided by the host Puppy. After that, it's the job of the Puppy file manager and the target Samba server to maintain a connection.

I found this to be fragile over WiFi with large files, even with ROX as the file manager. Do the built-in PcManFm tools work any better?

[Edit:] However, I notice that some Puppies are still using the mountcifs-1.5.pet package from 2011.