Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 09 Dec 2019, 23:47
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
ScPup & ScPup64 - Slackware Current based Woof-CE pups
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 8 of 12 [172 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10, 11, 12 Next
Author Message
peebee


Joined: 21 Sep 2008
Posts: 4092
Location: Worcestershire, UK

PostPosted: Mon 08 Apr 2019, 09:47    Post subject:  

19.04 versions of ScPup and ScPup64 are available - see post #1 & #2

Kernels remain the same.

32-bit 19.04+0 with md5 3a5da8e81f24a8f51ae06b0769db8626
and
64-bit 19.04+0 with md5 dc7575e9512bd79576932aa60e0e392d
become the new bases for delta updates.

Deltas from 19.01+0 to 19.04+0:
https://sourceforge.net/projects/spup/files/ScPup/updates/ScPup-19.01%2B0-uefi-T.iso___ScPup-19.04%2B0-uefi-T.iso.delta/download
to create
3a5da8e81f24a8f51ae06b0769db8626 ScPup-19.04+0-uefi-T.iso

https://sourceforge.net/projects/spup/files/ScPup64/updates/ScPup64-19.01%2B0-uefi-T.iso___ScPup64-19.04%2B0-uefi-T.iso.delta/download
to create
dc7575e9512bd79576932aa60e0e392d ScPup64-19.04+0-uefi-T.iso

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Last edited by peebee on Mon 08 Apr 2019, 18:15; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
Terry H

Joined: 29 Mar 2009
Posts: 674
Location: The Heart of Muskoka, ON Canada

PostPosted: Mon 08 Apr 2019, 15:19    Post subject:  

Upgraded scpup64 19.01+0 iso to 19.04+0 using delta file. I then manually replaced the 19.01 +6 installation on Data Traveller USB 3 Flash drive, and chose to upgrade the existing Save Folder (which I have backed up).

All good. Thanks peebee

Code:

# inxi -Fxz
System:    Host: puppypc1956 Kernel: 4.19.13-lxpup64 x86_64 (64 bit gcc: 8.2.0)
           Desktop: JWM 2.3.6 Distro: ScPup64 19.04
Machine:   Device: laptop System: Dell product: Latitude 3350
           Mobo: Dell model: 0TMD22 v: X02
           UEFI [Legacy]: Dell v: A09 date: 11/24/2016
Battery    BAT0: charge: 45.3 Wh 100.0% condition: 45.3/59.0 Wh (77%)
           model: Samsung SDI DELL 6C0FN58 status: Full
CPU:       Dual core Intel Core i5-5200U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8783
           clock speeds: max: 2700 MHz 1: 1786 MHz 2: 1764 MHz 3: 1227 MHz
           4: 1924 MHz
Graphics:  Card: Intel HD Graphics 5500 bus-ID: 00:02.0
           Display Server: X.org 1.20.4 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           tty size: 80x24 Advanced Data: N/A for root
Audio:     Card-1 Intel Wildcat Point-LP High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Broadwell-U Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.19.13-lxpup64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 port: e000 bus-ID: 03:00.0
           IF: eth0 state: down mac: <filter>
           Card-2: Intel Wireless 7265 driver: iwlwifi bus-ID: 04:00.0
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 264.1GB (6.1% used)
           ID-1: /dev/sda model: Crucial_CT256MX1 size: 256.1GB
           ID-2: /dev/sdb model: DataTraveler_3.0 size: 8.0GB
           ID-1: swap-1 size: 10.49GB used: 0.00GB (0%) fs: swap dev: /dev/sda4
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 135 Uptime: 46 min Memory: 484.2/7609.2MB
           Init: SysVinit runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 5.0.31) inxi: 2.3.8
#
Back to top
View user's profile Send private message 
Wiz57


Joined: 03 Feb 2019
Posts: 59
Location: Chickasha, OK

PostPosted: Mon 08 Apr 2019, 21:33    Post subject:  

Downloaded, extracted the new ScPup 19.04+0 32 bit ISO, upgraded the save file upon bootup, and here I am. No problems noted as of yet, noticed the new desktop icon for mounted drives...nice touch, much easier to distinguish between mounted and unmounted drives now!
Thank you peebee! Very Happy
Back to top
View user's profile Send private message 
OscarTalks


Joined: 05 Feb 2012
Posts: 2038
Location: London, England

PostPosted: Tue 09 Apr 2019, 04:04    Post subject:  

Now testing both 32bit and 64bit ScPup 19.04+0
Here is the 64bit version of Viewnior 1.7
Compiled using python 3.7.3 with meson and ninja
viewnior-1.7-x86_64-scpup.pet
Description  Viewnior 1.7 built from source in ScPup64
pet

 Download 
Filename  viewnior-1.7-x86_64-scpup.pet 
Filesize  78.12 KB 
Downloaded  133 Time(s) 

_________________
Oscar in England

Back to top
View user's profile Send private message 
ozsouth

Joined: 01 Jan 2010
Posts: 594
Location: S.E Australia

PostPosted: Thu 11 Apr 2019, 23:39    Post subject:  

Loving my new 19.01+5 remaster.
.

Last edited by ozsouth on Wed 24 Apr 2019, 07:19; edited 4 times in total
Back to top
View user's profile Send private message 
OscarTalks


Joined: 05 Feb 2012
Posts: 2038
Location: London, England

PostPosted: Fri 12 Apr 2019, 07:43    Post subject:  

One observation, I don't have a solution to offer as yet.
When compiling in ScPup32 19.04+0
Running new2dir make install
The shared library symlinks are installed in system as normal, BUT
These symlinks are NOT written into the new directory (which would normally be used to create a .pet or .sfs package).

So for example, libwhatever.so.1.2.3 is in the new directory, but the usual symlinks libwhatever.so.1 (run-time) and libwhatever.so (development) are not present in the new directory. I have to create them manually before creating a .pet package otherwise the .pet is (obviously) no good.

_________________
Oscar in England

Back to top
View user's profile Send private message 
ozsouth

Joined: 01 Jan 2010
Posts: 594
Location: S.E Australia

PostPosted: Wed 24 Apr 2019, 07:15    Post subject:  

Further to long (30 sec) pause in bootup (at ... optical input message) - culprit is /etc/profile LANG setting, when using AU instead of US. Get normal speed if .UTF-8 omitted, but that causes other problems. No issue in Slacko64 or Bionic64, & is fine on subsequent boot after savefolder made.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 4092
Location: Worcestershire, UK

PostPosted: Fri 03 May 2019, 04:55    Post subject:  

32-bit
9985f8a5c3fbb6cdffac9147afbb804f ScPup-19.04+2-uefi-T.iso

{delta update} - must be applied to the base 3a5da8e81f24a8f51ae06b0769db8626 ScPup-19.04+0-uefi-T.iso

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

======================
64 bit
b7b1f81079000d5fcca558326b74c236 ScPup64-19.04+2-uefi-T.iso

{delta update} - must be applied to the base dc7575e9512bd79576932aa60e0e392d ScPup64-19.04+0-uefi-T.iso

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

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
watchdog

Joined: 28 Sep 2012
Posts: 1931
Location: Italy

PostPosted: Fri 03 May 2019, 09:10    Post subject:  

Mplayer was not working for me as for disco dingo, neither pavrecord video preview. I have compiled MPlayer 1.4 for my architecture (kernel headers were needed) and now both are working. Why has one to compile mplayer for different cpu architectures? In the readme file of source mplayer I read:

Quote:
MPlayer has builtin support for the most common audio and video formats. For a
few formats no native decoder exists and external binary codecs are required
to handle them. Examples are newer RealVideo variants and a variety of rare
formats. However, binary codecs are NOT required in this day and age, they are
strictly optional.

Please note that binary codecs only work on the processor architecture they
were compiled for. Choose the correct package for your processor. No other
package is necessary.


Are the codecs compiled with mplayer?
Back to top
View user's profile Send private message 
OscarTalks


Joined: 05 Feb 2012
Posts: 2038
Location: London, England

PostPosted: Sat 04 May 2019, 05:19    Post subject:  

Confirmed in ScPup32 19.04+2
Code:
# mplayer /mnt/sda2/Part-1.mp4
MPlayer 1.4-8.3.0 (C) 2000-2019 MPlayer Team

Playing /mnt/sda2/Part-1.mp4.


MPlayer interrupted by signal 4 in module: demux_open
- MPlayer crashed by an 'Illegal Instruction'.
  It usually happens when you run it on a CPU different than the one it was
  compiled/optimized for.
  Verify this!
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.
#

The binary codecs are not likely to be needed for anything most people would come across these days and leaving them out would certainly not cause MPlayer to fail to run.

At compile time you can define the path to them with --codecsdir=/usr/lib/codecs (which seems to be the location in earlier Puppies). Maybe --codecsdir=/usr/lib/mplayer/codecs would be better for clarity if you still want to include them.

There is also the configure option --enable-runtime-cpudetection which may be on by default but it is perhaps worth including just to be sure.

_________________
Oscar in England

Back to top
View user's profile Send private message 
watchdog

Joined: 28 Sep 2012
Posts: 1931
Location: Italy

PostPosted: Sat 04 May 2019, 06:59    Post subject:  

I put in /etc/X11/xorg.conf.d the radky's 20-intel.conf forcing "uxa" accel method for palemoon to work. But I do not think this is the culprit after OscarTalks' previous post confirming the mplayer bug.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 4092
Location: Worcestershire, UK

PostPosted: Sat 04 May 2019, 09:04    Post subject:  

I used the petbuild:
https://github.com/puppylinux-woof-CE/petbuilds/blob/slacko_142/MPlayer/MPlayer.petbuild
Code:
# MPlayer
# Builds from https://github.com/puppylinux-woof-CE/petbuilds

. ../func
. ../build.conf

URL=http://www.mplayerhq.hu/MPlayer/releases
PKG=MPlayer
VER=1.4
COMP=tar.xz
DESC="Media player for audio and video"
DEPS=+ffmpeg
CAT=Multimedia
DESKTOP=MPlayer.desktop
BUILD=
CWD=$(pwd)
[ -z "$MWD" ] && MWD=$(dirname $CWD)   
[ -z "$BUILD" ] && BUILD=$DEF_BUILD
[ -f "$DESKTOP" ] || DESKTOP=not
[ -z "$DEPS" ] && DEPS=not   

ARCH=$(uname -m)
case $ARCH in
 *64)    LIBDIR=$LIBCONF64 ;;
 arm*)   LIBDIR=$LIBCONFarm;;
 *)    LIBDIR=$LIBCONF32 ;;
esac

build() {
   cd ${PKG}-${VER}
   ./configure --prefix=/usr \
      --disable-runtime-cpudetection \
      --confdir=/etc \
      --disable-smb \
      --disable-mencoder
   [ "$?" -eq 0 ] || exit
   
   make $MKFLG
   [ "$?" -eq 0 ] || exit
   make DESTDIR=$CWD/${PKG}-install install
   cd -
}
   
# main
retrieve ${PKG}-${VER}.${COMP}
extract ${PKG}-${VER}.${COMP}
build
package_std $PKG $VER $ARCH $DESKTOP "$DESC" $DEPS $CAT   

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
OscarTalks


Joined: 05 Feb 2012
Posts: 2038
Location: London, England

PostPosted: Sat 04 May 2019, 09:29    Post subject:  

I would suggest to try changing --disable-runtime-cpudetection to --enable-runtime-cpudetection

Seems that [disabled] is the default but I always build with this enabled.
This issue cropped up in a Slacko (5.x) a few years back and we decided that we should enable this feature. Not sure why the petbuild has it different.

_________________
Oscar in England

Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 4092
Location: Worcestershire, UK

PostPosted: Sat 04 May 2019, 14:28    Post subject:  

We need to amend the petbuild if your suggestion helps...I'll build some new pets and upload them for testing as I'm not able to....

The MPlayer module in woof-ce resulting from the petbuild has no libs at all - so either the binary contains static libs or the ffmpeg libs are being used.

I can't get the problem on my desktop (Xeon) or my laptop (Celereon) where test mp4s play with no problem on both....as does pavrecord video preview....

What processors do you both have??

Do you get the problem on both ScPup32 and ScPup64??

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Back to top
View user's profile Send private message Visit poster's website 
OscarTalks


Joined: 05 Feb 2012
Posts: 2038
Location: London, England

PostPosted: Sat 04 May 2019, 15:01    Post subject:  

I haven't tested 64bit yet. EDIT - Have now - seems OK
That is on a different machine in another room.
CPU on this machine is Pentium Dual-Core.
I recall discussing this with 01micko and we found that --enable-runtime-cpudetection makes the executable much more portable.
I am no expert, but would suggest amending the petbuild.

Modern day MPlayer links statically against ffmpeg, allowing for builds to always contain latest trunk snapshot (that is the idea anyway). Snapshots of trunk of MPlayer will download and use a trunk snapshot of ffmpeg at build time and use that. The release tarball (eg 1.4) of MPlayer contains a snapshot of ffmpeg master from the time of release, which it is known to be compatible with. If you want MPlayer to use system ffmpeg you can (I believe) configure for that and produce a smaller executable which will of course dynamically link. This might make sense, since ffmpeg libs are very recent, but it is personal choice.

QUICK UPDATE:-
ScPup64 19.04+2
MPlayer seems OK on the 64bit version, different machine though.
CPU is Intel Core i5 - 2500 with 4 cores

_________________
Oscar in England

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 8 of 12 [172 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10, 11, 12 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0797s ][ Queries: 12 (0.0127s) ][ GZIP on ]