(old)Puppy Linux Discussion Forum

peebee wrote:+ now a uefi bootable iso (? not tested)

Hi peebee

I love that you took the effort to make your iso this way!!
It would be nice if this behaviour were standard for Puppy builds (woof CE builds).
Imo it makes Puppy more easily portable and more usable for new users.
(Regulars probably do a frugal install with grub4dos manually and switch the machine to legacy boot in the bios.
Or they put it on the HD directly and use one of many ways to boot it from there, legacy or uefi.)

So I've tested it.
I put the iso on a pendrive with the dd command and tried to boot it on my uefi laptop.
The pendrive was recognised as uefi bootable in the bios as well as legacy bootable. (The laptop supports legacy boot as well.)
Booting succeeded for both! YES!

I went one step further and created pupsave.
First I used the fix-usb.sh to make a third partition on the pendrive, ext3.
I had to disable the exit after the sanity check for 3rd partition empty. I do not know why it says there is something on the 3rd partition.
Then I saved a pupsavefolder to this partition. But on reboot it was not found.
I put another pupsavefolder on the root of an ext3 partition on the ssd/HD. There the pupsave was found and loaded.
If one could put the pupsave on the same stick as the Puppy and have it used, one would have a even more portable Puppy.
So I tried to add puppy boot param.
That should be possible with F2 when the boot screen comes up in legacy boot, but on that moment there is an error in red displaying "DESKTOP FAIL: Black-screen/hangs... " and it is not possible to add anything.
Instead I tried by editing (e) the kernel line, both in eufi (grub2?) and legacy (syslinux?). There I added psave=sdb3 and booted. And that worked!
Would there be a way to avoid this workaround and to have Puppy looking for fitting pupsaves everywhere?

foxpup wrote:...
First I used the fix-usb.sh to make a third partition on the pendrive, ext3.
I had to disable the exit after the sanity check for 3rd partition empty. I do not know why it says there is something on the 3rd partition...

Might have been a "Lost & Found" folder. I think gparted sometimes (always?) creates one when you resize/create a new partition.

mikeslr wrote:Might have been a "Lost & Found" folder.

Could be, though I did not use gparted. Gparted does not handle these pendrives well after dd; gparted is completely clueless; ROX handles it better.

Reminds me that I left some small thing out of my little howto:
After using fix-usb.sh one has to make the filesystem (mkfs ...) as fix-usb says. If not, you still do not 'see' the third partition.

Mike, you have an idea how to accomplish this:

to have Puppy looking for fitting pupsaves everywhere?

It has to happen in the init, doesn't it?

Hi foxpup,

Sorry. I know little about init, and even less about USB-OSes created by dd.

mikesLr

mikeslr wrote:Hi foxpup,

Sorry. I know little about init, and even less about USB-OSes created by dd.

mikesLr

Me neither, just investigating ... and guessing

Installed 18.06+9-uefi to the hard drive of HP desktop:

System: Host: puppypc9263 Kernel: 4.17.0-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.06
Machine: Device: desktop System: Hewlett-Packard product: p7-1246s serial: MXX232077R
Mobo: Foxconn model: 2ADA v: 1.00 BIOS: AMI v: 7.12 date: 06/07/2012
CPU: Quad core Intel Core i5-3550 (-MCP-) speed/max: 1602/3301 MHz
Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
Display Server: X.org 1.20.1 driver: intel tty size: 180x31 Advanced Data: N/A for root
Network: Card-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 2000.4GB (1.0% used)
Weather: Conditions: 72 F (22 C) - Mostly Cloudy Time: October 11, 5:05 PM EDT
Info: Processes: 146 Uptime: 1:22 Memory: 372.2/11901.7MB Client: Shell (bash) inxi: 2.3.8

Added Kpat and Smplayer/Smtube,no luck with Kodi.
Added Chromium64_69.0.3497.100+pepper_31.0.0.122_lx_spot.sfs

Thanks.

I have had trouble playing some videos via seamonkey 2.49.4 - works fine in Slacko64-6.9.9.9, Xenialpup64 7.5, Bionicpup64 7.9.5. Video advances to (at best) advert and stops, sometimes locking up. Main site I've noticed is afl.com.au (any video in middle of page). Have tried adding extra gtk3 packages, changing about:config, turning off acceleration - no avail. Versions of Palemoon before 28.0 & supplied Light browser work. Any ideas?

EDIT: this is a GTK3 problem. Seamonkey64-2.48 (gtk2) works fine. If only it was secure.

EDIT2: apulse libs are in /usr/lib64 - apulse executable points to /usr/lib/64/apulse folder. When moved there, videos work!
.

Interim delta to 18.06+11-uefi

iso md5 = 29fe9aa0fe97a5db3840f1ff2079be1e lxpupsc64-18.06+11-uefi.iso

Just Slackware64 Current updates to Sat Oct 27 18:22:46 UTC 2018 + reversion to pup-volume-monitor-0.1.15

Later 64-bit kernels (4.19.x) are available

Mounted volumes disappear from desktop and pcmanfm panel when attach external drive (pcmanfm bookmarks remain and function though).

Since about k 4.18.10 (through subsequent kernel updates posted and OS updates). Various obvious gui setting changes had no positive effect (pcmanfm/event manager). Tested when new OS 18.06 updates posted (without save folder) and same result. Thought it might be particular to this system but recent load (no save folder) to laptop produced same result.

Checkums matched prior to install. No idea if kernel or OS upgrade specific but sometimes pmount automatically popped up and sometimes not. (Pmount always worked as expected though.)

Reinitializing pup-volume-monitor-starter consistently works for me. (Plug in external drive, wait for volume icons to disappear, reinitialize pup-volume-monitor-starter and all volumes show up and fully functional again in pcmanfm and desktop.)

This isn't a big deal, just a tip for anyone else who has adopted this as their main and experiencing same perplexing issue and is of similar dubious skill level. (I'd gotten really used to letting pcmanfm handle drive mounts/unmounts.) Bear in mind it could still be something weird I've done causing this...

Thanks for keeping so many things updated PeeBee, greatly appreciate your efforts.

wadmalaw wrote:Mounted volumes disappear from desktop and pcmanfm panel when attach external drive

Thank you for the report which I have verified....

Problem can be traced back to change to 64-bit pup-volume-monitor-0.1.17 on or about 15-sep-2018.

Have reverted back to pup-volume-monitor-0.1.15 in delta 18.06+11

The dmesg crash with 0.1.17 is:I'll report it on github.

Thank you PeeBee, didn't expect you to look into it so quick, thought maybe it'd go in the lower levels of a punch list.

Volumes stay put with 18+11. Nice to have them arranged in the expected order. Pmount automatically popped up when attached external drives, doesn't bother me at all.

Everything else you said was way beyond me.

I am really liking this OS. Thanks again.

ozsouth wrote:I have had trouble playing some videos via seamonkey 2.49.4

I downloaded the UNOFFICIAL 64-bit seamonkey-2.49.4......(only 32-bit seamonkey is official).....
I installed my 64-bit gtk+3 pet that I use in other browsers
I extracted seamonkey to a directory and ran it directly from there...

in my 2 standard tests (youtube and bbc-iplayer) videos and sound played correctly..........no changes to apulse were required.....

@ozsouth

to change settings on spec won't help you along.
find out what your SM version has included and what system components are used.

type about:buildconfig in address line of SM and press enter

look whether SM has been built with pulseaudio support or not
in case of built without pulseaudio you should find the entries ( --disable-pulseaudio --enable-alsa )

is system or internal libvpx used ?
in case of system libvpx usage you should find ( --with-system-libvpx ) and of course a recent version should be installed

whether SM has been built for gtk2 or gtk3 you can detect which toolkit is used
( --enable-default-toolkit=cairo-gtk2 ) or ( --enable-default-toolkit=cairo-gtk3 )

in case of trouble you could also look here
type about:support in address line of SM and look for messages

@norgo - thanks for your help. about:buildconfig makes no mention of pulse or vpx. SM64 2.49.4 uses gtk3. All I noticed is that videos didn't work until I put libs into /usr/lib64/apulse in lxpup64, & I had no video issue with xenialpup64 & bionicpup64, which both have their pulse libs in /usr/lib/apulse. And to confuse things further, slacko64 doesn't have pulse libs & videos play. All with the same Seamonkey setup. Peebee had the same issue with the same videos, but not in Chromium. I don't understand - it's not logical, but I'll have to make do with the workaround for now.

@ozsouth
for clarification, we are talking about 64 bit version of SM, right ?

did a short test in Slacko64 700RC3 and SM 2.49.4 (64bit) from official Website
build configuration shows:

Build platform
target
x86_64-pc-linux-gnu

Configure options
MOZ_AUTOMATION=1 --with-external-source-dir=/builds/slave/rel-c-esr-lnx64-bld/build --enable-application=suite --enable-update-channel=release PKG_CONFIG=/builds/slave/rel-c-esr-lnx64-bld/build/gtk3/usr/local/bin/pkg-config --with-ccache=/usr/bin/ccache CC=/builds/slave/rel-c-esr-lnx64-bld/build/gcc/bin/gcc CXX=/builds/slave/rel-c-esr-lnx64-bld/build/gcc/bin/g++ --enable-rust RUSTC=/builds/slave/rel-c-esr-lnx64-bld/build/rustc/bin/rustc CARGO=/builds/slave/rel-c-esr-lnx64-bld/build/cargo/bin/cargo --enable-js-shell --enable-default-toolkit=cairo-gtk3 --with-google-api-keyfile=/builds/google-api.key MAKE=make --enable-alsa --enable-crashreporter --enable-elf-hack --enable-release --enable-stdcxx-compat

this means:
gtk3 is needed
installation of alsa is sufficient for audio playback
internal libvpx is used

real 64 bit OS doesn't search for libs in /usr/lib they expect libs in /usr/lib64

if you are install apulse and the libs are going to /usr/lib Slacko will not find them
Ubuntu basing distros have a symbolic link from /usr/lib64 to /usr/lib
that's why they are working nevertheless if the needed libs are located in /usr/lib

Interim delta to 18.06+12-uefi

iso md5 = 1f9d9df6fc0718fcd78cdb7176615c6d lxpupsc64-18.06+12-uefi.iso

peebee wrote:Interim delta to 18.06+12-uefi

iso md5 = 1f9d9df6fc0718fcd78cdb7176615c6d lxpupsc64-18.06+12-uefi.iso

Hi Peebee,

Downloaded +12 from the Sourceforge link, and md5 sums are very different. Just wanted to give you a heads up about it. Here's a pic:

belham2 wrote: md5 sums are very different.

You are confusing the iso md5 with the delta md5.....

peebee wrote:

belham2 wrote: md5 sums are very different.

You are confusing the iso md5 with the delta md5.....

So pupmd5sum won't read the delta and only reads the first part of the delta line and not anything after the "__"???

First time I've ever seen this. I opened the delta file specifically, as you can tell in the pic. None of the other deltas, all downloaded to their ISO folder, has ever done this.

Why is it starting now??

No, the ISO md5 in that folder is this:

0de72b2429437268df404838456af51a


3 different md5 numbers, two in the folder I have downloaded, and one in the post I referenced.