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

Message

peebee · #946 Post by **peebee** » Tue 20 Mar 2018, 06:57

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?

belham2 · #947 Post by **belham2** » Tue 20 Mar 2018, 08:30

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.

peebee · #948 Post by **peebee** » Tue 20 Mar 2018, 11:42

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

Marv · #949 Post by **Marv** » Tue 20 Mar 2018, 14:10

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,

peebee · #950 Post by **peebee** » Wed 21 Mar 2018, 08:27

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,

Marv · #951 Post by **Marv** » Thu 22 Mar 2018, 01:01

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,

peebee · #952 Post by **peebee** » Thu 22 Mar 2018, 17:09

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

Marv · #953 Post by **Marv** » Thu 22 Mar 2018, 18:07

+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,

peebee · #954 Post by **peebee** » Fri 23 Mar 2018, 11:02

aplay problem with devx; fixed by woof-ce pull request:
https://github.com/puppylinux-woof-CE/woof-CE/pull/1159

peebee · #955 Post by **peebee** » Sun 25 Mar 2018, 10:56

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

peebee · #956 Post by **peebee** » Thu 29 Mar 2018, 10:04

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

peebee · #957 Post by **peebee** » Sun 01 Apr 2018, 14:29

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

peebee · #958 Post by **peebee** » Sun 01 Apr 2018, 14:33

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.

Marv · #959 Post by **Marv** » Sun 01 Apr 2018, 15:08

+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,

peebee · #960 Post by **peebee** » Mon 02 Apr 2018, 15:13

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/

peebee · #961 Post by **peebee** » Sun 08 Apr 2018, 08:49

Browser updates: Iron, Slimjet & Min

Marv · #962 Post by **Marv** » Sun 08 Apr 2018, 14:45

slimjet_lxsc_spot_17.0.3.0.sfs updated to slimjet_lxsc_spot_18.0.2.0.sfs, running under latest LxPupSc. Shared Spot directory is on the EXT2 data partition with a symlink to it from each pup on the computer. Unload one SFS, load new one. Didn't skip a beat.

Edit: Ditto for LxArtfulPup, ArtfulPup and uPupBB on both the core 2 duo laptops and the i5 sandy bridge laptops.

Later: Spoke too soon!! Using Slimjet 18.0.2.0 on the i5. Looking at monitor specs/reviews on amazon, cnet, several other sites. LOTS of page failures! Snap or aw shucks

Ebay, weather, several forums, news and economic sites had all been fine all day. Seems confined to the ad ridden commercials and occurs with or without the use of adblock plus. Identical behavior on the core 2 duo and under LxPupSc and uPupBB. Went back to 17.0.3.0 and no failures. When a failure occurs, the pages seemed to load initially and then failed when an ad or slider tried to load. It never crashed Slimjet but those particular pages were not usable. So for now it's still 17.0.3.0 as the workhorse. Alas.

Thanks,

davids45 · #963 Post by **davids45** » Mon 09 Apr 2018, 06:17

G'day peebee,

I made a manual frugal from the iso (LxPupSc-18.04T-k64) on my old HP Smallform desktop. It took me a while to realise this is suitable for 'old-dog' 32-bitters like me

.

I switched to the 'devil-I-know' JWM and added my usual applications in the form of my many pets composed of symlinks to my boot-mounted data partition. I then dragged each .desktop file to the pinboard for quick access (screenshot).

Some apps needed extra libs which I had already made as 'missing-lib' pets from trying my apps in earlier Slacko Pups.

My apps all work in this LxPupSc ... except the inkgui package that says it cannot find my networked printer (screenshot). Most other Pups (maybe not other Slackos - I haven't checked recently) have no problem with this very handy printer ink level app. The printer prints and its scanner scans so I'm puzzled (as usual).

I noticed my (27) drive icons are very, very slow to appear in turn across the bottom of the pinboard (check screenshot). Is there an option to say, only display mounted partitions, if this slowness is now unavoidable? Previous Pups seem not as slow.

Likewise, the 'Places' panel when I go to 'Open File' have all my partitions when all I need are the mounted partitions and /root (screenshot). Again some other Pups are free of this panel clutter. It is really my problem with so many partitions but I don't still know how to get rid of these unnecessary 'Places'.

My usual thanks for all your Puppies - great fun for me as a hooked user/addict.

David S.

peebee · #964 Post by **peebee** » Mon 09 Apr 2018, 15:48

UPDATE
Kernel 4.16.2

Marv · #965 Post by **Marv** » Tue 10 Apr 2018, 18:15

Got slimjet sorted to my satisfaction for now, see 3 posts up. The site failures were due to the libffmpeg.so in the package (11.3MB, source?). I first built an 18.0.1.0 SFS using OscarTalks SFS as a base, adding libs for slackware and modifying the /usr/bin files to run-as-spot with --user-data-dir=/root/spot/. Runs fine, no failures. Then I swapped the libffmpeg.so from a fresh slimjet 18.0.2.0 download into peebees 18.0.2.0 package. No failures. Then I built an SFS from a fresh slimjet 18.0.3.0 download, keeping their libffmpeg.so and adding only libs needed for LxPupSc and the std. /usrbin files for run-as-spot. It is running fine, no failures to date on the sites that were problematic. I'll continue using that one but so far so good. I haven't played with any other libffmpegs. An aside, with all the libs in /opt/slimjet it seems to pick them up ok without the

Code: Select all

export LD_LIBRARY_PATH=/opt/slimjet:$LD_LIBRARY_PATH

line in /usr/bin/slimjet. Runs in LxPupSc and no nags about libs anyway when run from terminal.

Cheers,

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

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

LxPupSc-18.04T-k64

First try with LxPup-Sc-18.04T