LxPupSc: Woof-CE, Slackware-Current, LXDE build 13-Jun-2020

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#941 Post by Marv »

belham2 wrote:Hi all,

Anyone face any problems applying delta+6 while using the same savefile (for deltas 5 & previous)??

I just now applied delta+6 to the iso, then updated my frugal LxPupSc install, and while everything booted up great with delta+6, things like that latest Palemoon browser, redshift, etc, etc just quit working. All of those things were working in delta+5 & previous versions. Yup, I just confirmed it, I went back and re-did the ISO using delta+5, and everything (Palemoon, redshift, etc) from my savefile runs great with no problems with delta+5. Not so with delta+6.

What the heck changed from delta+5 to delta+6???
The kernel changed from 4.15.10 to 4.15.11, I don't know what else that is relevant. I just updated my frugal install, 256Mb EXT2 savefile on my intel i5 based laptop (i915 graphics). I'm running SlimJet 17.0.3.0 as spot, Sylpheed, Geany, a HP4500 and Brother HL2170W networked printers etc. I don't have redshiftgui on this install. I can't see any changes at all in function from +5 to +6 on my install/hardware after updating the savefile. Try starting one of the offenders from terminal and see if that sheds any light. My savefile is neither particularly old nor young. IIRC I started fresh when LxPupSc turned 18.03. Usually when updating a savefile, particularly if I know a kernel change is involved I go into the non-mounted savefile and run a scrubber script that deletes /etc/modules, /lib/modules, /etc/X11/xorg.conf, /etc/udev/rules.d/70-persistent-net.rules (in slackos), and /var/local/xorg_udev . Think that's it. Keeps the cruft down and prevents wlanx number climbing. I've been running +6 since the delta came out. Nothing fancy but web use, pushing updates to several of my other machines... I'll do an update & test on one of the slightly older core 2 duos now.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
8Geee
Posts: 2181
Joined: Mon 12 May 2008, 11:29
Location: N.E. USA

#942 Post by 8Geee »

I was just doing the same, after seeing the Atom D330/ ION GPU set up. I did see some 'amdgpu' stuff in that 4.15.11 revision.
Several more drm/i915 and ath10 stuff.

GL
8Geee
Linux user #498913 "Some people need to reimagine their thinking."
"Zuckerberg: a large city inhabited by mentally challenged people."

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#943 Post by Marv »

Here's what happened on the core 2 duo. First tried a pfix=ram boot of +6T. Clean boot and setup through SNS connection. Seemed all fine.

Then tried an update of an unscrubbed +5T savefile described above. e2fsck clean. Would not boot. Hung after the Booting the kernel line. Then scrubbed as described above and rechecked the savefile. Still hung at that line. A hard reset was required to get out in both cases. Seemed grim.

Then, don't know exactly why, I deleted /etc/DISTRO_SPECS in that savefile. e2fsck run on it again. BOOTED NORMALLY then and running slimmie etc. now. Posting from it. Dmesg has only the customary acpid resource conflict warnings... I see that often. glxgears runs well. Haven't looked at much else yet. All in all seems fine if maybe a bit CPU hungry in Slimmie.

I dunno but that's exactly what I did :? On the i5 i definitely didn't mess with DISTRO_SPECS.

Edit: Rebooted after posting. Hung again at the same place (Booting the kernel). Hard power off, rebooted into another pup, deleted /etc/DISTRO_SPECS in that savefile, e2fsck on it (clean) and it again booted totally normally into +6. Now :? :?
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

ozsouth
Posts: 858
Joined: Fri 01 Jan 2010, 22:08
Location: S.E Australia

#944 Post by ozsouth »

@Marv - Copying the DISTRO_SPECS from initrd.gz (mount via Rox-Filer) to /etc might help.

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#945 Post by Marv »

ozsouth wrote:@Marv - Copying the DISTRO_SPECS from initrd.gz (mount via Rox-Filer) to /etc might help.
I'll try that on the core 2 duo and see. Thanks.

I just now did a complete bonehead (no cleaning, scrubbing or checking of the +5 savefile) update from +5 to +6 on another i5 laptop (also a fujitsu S761) with no hitches or glitches at all. My puzzle is why is it different on the core 2 duo.

Edit: @ozsouth - Indeed, replacing the /etc/DISTRO_SPECS file with the one from initrd.gz does give consistent updates and reboots on the core 2 duo. It has to be done in the main SFS though, not in the savefile because the main SFS one overwrites the savefile one on boot :?: (checked that several ways). I unsquashed the main SFS, made that one change, and resquashed. Now both updates and reboots just work on the core 2 duo as well as on the i5s. The only difference is that the file from initrd.gz lacks the last 2 lines

Code: Select all

#multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
DISTRO_ARCHDIR=''
Cheers,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#946 Post by peebee »

All the above sounds very weird.... :(

There were no woof-ce changes in delta 6
The Slackware Current changes shouldn't have affected Puppy booting!!
The initrd.gz should not have changed

Delta 6 works fine on both my test machines - desktop and laptop

Palemoon running under root worked fine when tested

Hmmmm - baffling!

@belham2 - are you using a savefile (format, encrypted?) or a savefolder?
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#947 Post by belham2 »

peebee wrote:All the above sounds very weird.... :(

@belham2 - are you using a savefile (format, encrypted?) or a savefolder?
Hi Peebee,

Sorry I wrote the wrong word: meant savefolder. It's ok, I just dropped back & am again using Delta+5 & everything's good. I tried everything I could think of (using Marv's hints too) and nothing worked. It occurred on an Intel Core i3, 8gb ram laptop. Just to satisfy my curiosity, I went to one of my AMD desktop machines, and it sure enough it was like nothing was wrong-----Delta+6 and the savefolder all booted normal with everything working. Truly weird stuff... :? Every other frgual pup & DDog run with no problems on the very same Intel laptop, so I don't know what is going on.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#948 Post by peebee »

Please share the output from inxi -Fxx so we can see if that gives any clues.

My laptop:

Code: Select all

System:    Host: puppypc1807 Kernel: 4.15.11-lxpup64 x86_64 (64 bit gcc: 7.3.0)
           Desktop: LXDE (Openbox 3.6.1) dm: N/A Distro: LxPup-Sc 18.03
Machine:   Device: laptop System: ASUSTeK product: X551MA v: 1.0 serial: F1N0CX160100029
           Mobo: ASUSTeK model: X551MA v: 1.0 serial: BSN12345678901234567
           UEFI [Legacy]: American Megatrends v: X551MA.513 date: 09/09/2014
Battery    BAT0: charge: 8.7 Wh 28.4% condition: 30.6/32.6 Wh (94%)
           volts: 14.8/14.8
           model: ASUSTeK X551-26 serial: N/A status: Discharging
CPU:       Dual core Intel Celeron N2840 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8666
           clock speeds: min/max: 499/2582 MHz 1: 562 MHz 2: 722 MHz
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
           bus-ID: 00:02.0 chip-ID: 8086:0f31
           Display Server: X.org 1.19.6 drivers: intel (unloaded: vesa) FAILED: modesetting
           tty size: 80x24 Advanced Data: N/A for root
My desktop:

Code: Select all

System:    Host: puppypc2135 Kernel: 4.15.11-lxpup64 x86_64 (64 bit gcc: 7.3.0)
           Desktop: LXDE (Openbox 3.6.1) dm: N/A Distro: LxPup-Sc 18.03
Machine:   Device: desktop System: Dell product: Precision WorkStation T5400 serial: BKP3C4J
           Mobo: Dell model: 0RW203 serial: ..CN1374092O008A.
           BIOS: Dell v: A11 date: 04/30/2012
           Chassis: type: 7 serial: BKP3C4J
CPU(s):    2 Quad core Intel Xeon E5450s (-HT-MCP-SMP-) cache: 12288 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 47899
           clock speeds: max: 2825 MHz 1: 1995 MHz 2: 2546 MHz 3: 1995 MHz
           4: 2810 MHz 5: 1995 MHz 6: 2825 MHz 7: 1994 MHz 8: 2034 MHz
Graphics:  Card: NVIDIA GT218 [NVS 300] bus-ID: 02:00.0 chip-ID: 10de:10d8
           Display Server: X.org 1.19.6 drivers: nouveau (unloaded: modesetting,nv,vesa)
           tty size: 80x24 Advanced Data: N/A for root
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#949 Post by Marv »

Here are some inxi outputs.

i5 laptop with no +5 to +6 boot issues (LxPupSc64):

Code: Select all

# inxi -Fxx
System:    Host: puppypc395 Kernel: 4.15.7-lxpup64 x86_64 (64 bit gcc: 7.3.0)
           Desktop: LXDE (Openbox 3.6.1) dm: N/A Distro: LxPupSc64 18.03
Machine:   Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
           Mobo: FUJITSU model: FJNB225 UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
           Chassis: AOD47CE51CBA7001 type: 10
Battery    CMB1: charge: 56.0 Wh 100.0% condition: 56.0/56.0 Wh (100%) volts: 12.8/11.1
           model: Fujitsu CP293600-01 serial: 01A-X110812201059X status: Full
CPU:       Dual core Intel Core i5-2520M (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9970
           clock speeds: min/max: 800/2501 MHz 1: 2912 MHz 2: 833 MHz 3: 841 MHz 4: 826 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           bus-ID: 00:02.0 chip-ID: 8086:0126
           Display Server: X.org 1.19.6 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           tty size: 134x32 Advanced Data: N/A for root
Audio:     Card Intel 6 Series/C200 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20
           Sound: Advanced Linux Sound Architecture v: k4.15.7-lxpup64
Network:   Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
           driver: ath9k bus-ID: 02:00.0 chip-ID: 168c:002e
           IF: wlan0 state: up mac: 24:ec:99:24:3b:d1
Drives:    HDD Total Size: 64.0GB (39.0% used)
           ID-1: /dev/sda model: SAMSUNG_SSD_830 size: 64.0GB serial: N/A
RAID:      System: supported: linear raid0 raid1 raid10 raid6 raid5 raid4
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 146 Uptime: 0 min Memory: 188.7/4790.0MB Init: SysVinit v: N/A runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191 running in lxterminal) inxi: 2.3.8 
i5 laptop with no +5 to +6 boot issues (LxPupSc +6):

Code: Select all

# inxi -Fxx
System:    Host: puppypc21956 Kernel: 4.15.11-lxpup64 x86_64 (64 bit gcc: 7.3.0)
           Desktop: LXDE (Openbox 3.6.1) dm: N/A Distro: LxPup-Sc 18.03
Machine:   Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
           Mobo: FUJITSU model: FJNB225 UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
           Chassis: AOD47CE51CBA7001 type: 10
Battery    CMB1: charge: 56.0 Wh 100.0% condition: 56.0/56.0 Wh (100%) volts: 12.8/11.1
           model: Fujitsu CP293600-01 serial: 01A-X110812201059X status: Full
CPU:       Dual core Intel Core i5-2520M (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9970
           clock speeds: min/max: 800/2501 MHz 1: 2893 MHz 2: 1937 MHz 3: 1248 MHz 4: 1757 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           bus-ID: 00:02.0 chip-ID: 8086:0126
           Display Server: X.org 1.19.6 drivers: intel (unloaded: modesetting,vesa)
           tty size: 134x32 Advanced Data: N/A for root
Audio:     Card Intel 6 Series/C200 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20
           Sound: Advanced Linux Sound Architecture v: k4.15.11-lxpup64
Network:   Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
           driver: ath9k bus-ID: 02:00.0 chip-ID: 168c:002e
           IF: wlan0 state: up mac: 24:ec:99:24:3b:d1
Drives:    HDD Total Size: 64.0GB (39.1% used)
           ID-1: /dev/sda model: SAMSUNG_SSD_830 size: 64.0GB serial: N/A
RAID:      System: supported: linear raid0 raid1 raid10 raid6 raid5 raid4
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 150 Uptime: 0 min Memory: 191.7/4790.0MB Init: SysVinit v: N/A runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.191 running in lxterminal) inxi: 2.3.8 
core 2 duo laptop with weird +5 to +6 update boot issues (LxPupSc 18.03 +6):

Code: Select all

# inxi -Fxx
System:    Host: puppypc21956 Kernel: 4.15.11-lxpup64 x86_64 (64 bit gcc: 7.3.0)
           Desktop: LXDE (Openbox 3.6.1) dm: N/A Distro: LxPup-Sc 18.03
Machine:   Device: laptop System: FUJITSU product: LifeBook S6520 serial: R0106363
           Mobo: FUJITSU model: FJNB1E6 BIOS: FUJITSU // Phoenix v: Version 1.31 date: 09/09/2009
           Chassis: A7H2H1G9088C1011 type: 10
Battery    CMB1: charge: 58.0 Wh 100.0% condition: 58.0/58.0 Wh (100%) volts: 12.5/10.8
           model: Fujitsu CP345705-01 serial: 02A-Z080416000015Z status: Full
CPU:       Dual core Intel Core2 Duo P8600 (-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9581
           clock speeds: min/max: 800/2401 MHz 1: 1412 MHz 2: 1546 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:2a42
           Display Server: X.org 1.19.6 drivers: intel (unloaded: modesetting,vesa)
           tty size: 126x33 Advanced Data: N/A for root
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:293e
           Sound: Advanced Linux Sound Architecture v: k4.15.11-lxpup64
Network:   Card-1: Marvell 88E8055 PCI-E Gigabit Ethernet Controller
           driver: sky2 v: 1.30 port: 2000 bus-ID: 08:00.0 chip-ID: 11ab:4363
           IF: eth0 state: down mac: 00:23:26:bc:e3:fd
           Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi bus-ID: 20:00.0 chip-ID: 8086:4236
           IF: wlan0 state: up mac: 00:21:6a:85:4f:d4
Drives:    HDD Total Size: 81.1GB (33.5% used)
           ID-1: /dev/sda model: INTEL_SSDSA2M080 size: 80.0GB serial: N/A
           ID-2: USB /dev/sdb model: TS1GJF110 size: 1.0GB serial: 00000000-0:0
RAID:      System: supported: linear raid0 raid1 raid10 raid6 raid5 raid4
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 131 Uptime: 1 min Memory: 156.8/2960.4MB Init: SysVinit v: N/A runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.191 running in lxterminal) inxi: 2.3.8 
Another normal LxPupSc 18.03 +6 boot this AM on the core 2 duo with the truncated /etc/DISTRO_SPECS in the main SFS. My guess is that I did at least 5 or 6 non-boots on it before mucking with that file. Timing?

Cheers,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#950 Post by peebee »

I have re-uploaded delta +6.....

Probably nothing to do with the above problems but:
fontconfig-2.12.6-i586-1.txz: Reverted to previous version. There are problem reports with the latest version,
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#951 Post by Marv »

I know not why but.... My weirdness at any rate is gone. On the same core 2 duo machine that hung consistently on updates yesterday I applied the new +6 delta, checked the md5sum as always, replaced all the files in the LxPupSc boot dir. with those from the new iso, put an untouched +5 savefile in there (doublechecked kernel version, /etc/DISTRO_SPECS etc. to be sure it was straight up+5, no cleaning or scrubbing), and rebooted to update. No hang at boot! Normal update, everything working when done. Rebooted once just to check, still ok.

I'll take it :)

Thanks,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#952 Post by peebee »

Interim delta +7
.iso md5 = 4b10dd3c9f0e743230dfb80fb08ea79a LxPupSc-18.03+7T-k64.iso

- kernel 4.15.12 (64-bit GCC-7.3.0 build)

- Slackware Current to Fri Mar 23 22:28:20 UTC 2018
Last edited by peebee on Sun 25 Mar 2018, 10:56, edited 2 times in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#953 Post by Marv »

+6 to +7 updates on both the i5 laptop and the briefly problematic core 2 duo laptop went normally. Quick check of all functions seems fine. Posting from the core 2 duo now.
Thanks,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#954 Post by peebee »

aplay problem with devx; fixed by woof-ce pull request:
https://github.com/puppylinux-woof-CE/woof-CE/pull/1159
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#955 Post by peebee »

Interim delta +8
.iso md5 = 51a393b3bfe8bea7c9c39c1f4fb8d657 LxPupSc-18.03+8T-k64.iso

- kernel 4.15.13 (64-bit GCC-7.3.0 build)

- Slackware Current to Mon Mar 26 22:06:38 UTC 2018
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#956 Post by peebee »

Interim delta +9
.iso md5 = 11dbf25a2db4326ebf27447e84427193 LxPupSc-18.03+9T-k64.iso

- kernel 4.15.14 (64-bit GCC-7.3.0 build)

- Slackware Current to Thu Mar 29 20:48:28 UTC 2018

with openssl-1.0.2o
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

LxPupSc-18.04T-k64

#957 Post by peebee »

LxPupSc-18.04T-k64 is a 32-bit woof-ce 'testing' branch build with a 64-bit kernel (therefore only compatible with 64-bit capable processors)

LxPupSc-18.04T-k64.iso {devx} - (devx does not include kernel sources or headers) {kernel 4.15.15-lxpup64 sources}

iso md5 = e8edb38abf81e13d1b526392e9d8ac88

Delta from 18.03T is available

- kernel 4.15.15 64-bit built with GCC-7.3.0
(alternative 32-bit kernels 3.16.x 4.4.x & 4.9.x also available - all need firmware in the fdrv)
- Made from Slackware-Current as of Sun Apr 1 02:53:26 UTC 2018
- BUILD_FROM_WOOF='testing;63e7068d;2018-03-30 13:06:14 +0300'
- new "common32" repo used (see: /root/.packages/woof-installed-packages for details)
- web browser in adrv is light-48.0
- firmware is in fdrv
- 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 the LxPupSc kernel and 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 01-apr-2018 with their md5sums are:
chromium_65.0.3325.181+pepper_29.0.0.113 RUN-AS-SPOT :8e95b861dadcce24ea9d485f262a0e17 **NEW VERSION for LxPupSc-18.04**
firefox-52.7.3esr :6e0286a39274e6a161445bedfaf2e642
palemoon-27.8.3 :e7614b0d75698f5f3b363389f270c312
seamonkey-2.49.2 :20db44d39fe0baef6d8ad4a222f31bc7
firefox-59, iron, slimjet, vivaldi and min are also available
Attachments
Screenshot.png
(121.29 KiB) Downloaded 760 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#958 Post by peebee »

WARNING:

The icu update in LxPupSc-18.04 means that a tweaked version of chromium.sfs needs to be downloaded to replace the previous version.

All the other browsers seem to work OK.
Last edited by peebee on Mon 02 Apr 2018, 15:09, edited 1 time in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#959 Post by Marv »

+9T savefile based frugal grub4dos install on Fujitsu S661 i5 based laptop updated to 18.04 using the delta. md5sum correct, sound, video, SNS connection, overall operation seems fine. Sylpheed 2.0 ok, as is (so far as I can see) your slimjet_lxsc_spot_17.0.3.0.sfs. How would the chromium failure manifest itself?

Cheers,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#960 Post by peebee »

All the other web browsers (firefoxESR, firefox59, palemoon, seamonkey, iron, min, netsurf, slimjet, vivaldi) work as expected - only chromium needs an updated chromium.sfs

kernel 4.16.0 is available to try:
https://sourceforge.net/projects/lxpup/ ... /interims/
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Post Reply