BionicPup32 (UPupBB) (27 June 2020)

A home for all kinds of Puppy related projects
Message
Author
User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#181 Post by peebee »

stemsee wrote:therefore the problem lies somewhere else within BionicPup!
Please post a code snippet to show the problem....

Slackware current has 4.4.23 - but it still identifies as 4.4.19(1).....

Can you try??:
http://ftp.slackware.com/pub/slackware/ ... i586-1.txz
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

hamoudoudou

I will delete old pupsave after manual transfer to new one

#182 Post by hamoudoudou »

pupsave ubbpup renamed upupbb.
I will delete previous pupsave after manual transfer to new one.. (personal files). I will reinstall pets . that is faster than any remaster.
I Keep a minimal pupsave with my first settings and usual pets (as pupsaveconfig). I just have to increase its size to make it 512mB
Continous writing on HardDrive is stupid.. You loose advantage of RAM Speed .. The Hard drive is around 480mb/seconds.. Puppy has to slow down from more than 1600 mb/s to 480 just to record what is done.. Transfer in pup-ro1 let you the choice to record only at shutdown;. So you keep supersonic speed all the the session. Right or false ?
Just consider your pupsave on harddisk as USBFlash to avoid continuous writing.. (frugale install on hard drive)..
Attachments
save.jpg
Isobooter Puppy & Manjaro
(65.41 KiB) Downloaded 941 times
Last edited by hamoudoudou on Tue 26 Jun 2018, 06:51, edited 1 time in total.

hamoudoudou

Cosmic Cuttlefish will be next flavour... Of Bionic

#183 Post by hamoudoudou »

Cosmic Cuttlefish will be next flavour... Of Bionic
Artful was last flavour of Xenial
Bionic is a new project.. Flavours mean period of times, like centuries for humans.

flies will soon change donkey for Cosmic...

stemsee

#184 Post by stemsee »

peebee wrote: Can you try??:
Indeed I tried it. First I expanded the packaged and copied over the binary, renaming bash to bashold then bash4new to bash ... nothing worked. Then I copied over the other dirs from the packaage, including the headers ... still nothing worked for me, then I changed back around the binaries, and everything works as should, leading me to beleive that the headers or libs were at fault not the binary! Maybe you can find exactly the culprit now.

stemsee

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

#185 Post by peebee »

stemsee wrote:Maybe you can find exactly the culprit now.
stemsee
Not without some test code - I've no real idea what problem you have....please provide test code to demonstrate problem.
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:

#186 Post by peebee »

superceded
Last edited by peebee on Sun 01 Jul 2018, 10:16, edited 1 time in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
davids45
Posts: 1326
Joined: Sun 26 Nov 2006, 23:33
Location: Chatswood, NSW

No problems found with 18.05+6

#187 Post by davids45 »

G'day peebee,

I made a manual frugal of the delta-added bionicpup-18.05 and all was fine.

I had added my usual applications-sfs which is comprised of sym-links back to the 'real' application files on my data partition (you might just pick up the arrows on the app pinboard icons of the screenshots).

I fixed Rox-filer so the columns are ordered to my preference, and sorted /lib/ , cups and sane so my Epson-WF2510 prints and scans.
Finally ran Gimp to make a pinboard wallpaper with the bionic details so I think I know which one I've booted :shock: - although pwidgets does have the detail as well (screenshot) :roll: .

This all went so well :D , I thought I'd try an older kernel and a newer kernel (=64-bit) in your 18.05+6.

Replacing the ydrv and vimlinuz files with those from the huge-kernel tars, I made two new frugals and into each added the savefile from the original 18.05+6 (via a savefile hot backup) before booting each new bionicpup.

Again, everything seemed in place with this re-used savefile - I had nothing to change or fix in the 'other kernel' 18.05+6 bionics (pinboard screenshot of each attached).

Rebooting has gone well with each one, and the only issue I have is to remember to rename the savefile backup to show which kernel-version it's from.

Effect of the kernel?
I have a desktop approaching those difficult teenage years so it seems on this unit, the kernel has little or no effect in terms of drivers etc. if I understand the relevance of the ydrv in Puppy.

It's all to do with the Puppy part how things run.

And this/these bionic(s) is/are running very well for me.

Thanks for all your time and effort.

David S.
Attachments
bionic18056k4996.jpg
bionic18.05+6 as-delivered with apps etc added
(112.42 KiB) Downloaded 970 times
bionic18056T64k4172.jpg
64-bit kernel
(108.45 KiB) Downloaded 949 times
bionic18056k31645.jpg
older kernel
(100.52 KiB) Downloaded 946 times

User avatar
recobayu
Posts: 387
Joined: Wed 15 Sep 2010, 22:48
Location: indonesia

#188 Post by recobayu »

I can not change jwm theme in this +6

User avatar
lost3.1
Posts: 39
Joined: Fri 04 Apr 2014, 02:42
Location: Boston,MA USA

#189 Post by lost3.1 »

recobayu wrote:I can not change jwm theme in this +6
Yep Did a clean install with 32bit 18,05+6, tool-bar would not change when I

try to use puppy theme manager and got error

message.(Something about back-up)

I am holding at 18.05+4 and will wait for +7
Last edited by lost3.1 on Sun 01 Jul 2018, 01:49, edited 2 times in total.
[else Y if-false Y]

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

#190 Post by peebee »

recobayu wrote:I can not change jwm theme in this +6
Confirmed - woof-ce issue #1222 raised
Attachments
Screenshot.png
(20.87 KiB) Downloaded 691 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
recobayu
Posts: 387
Joined: Wed 15 Sep 2010, 22:48
Location: indonesia

#191 Post by recobayu »

I fix my problem by edit file: /usr/share/applications/sys-update.desktop.
I change the line:

Code: Select all

Exec=sh -c "xmessage -title Updates_Warning -bg firebrick1 -fg white 'Updates can only be applied to\nthe original upupbb-18.05.iso\nwith md5=55e20c3e53339cf6ddbc5bc3c0c0bad1\n\nReverse_updates are available to generate\nthe original .iso from one of the updates' & defaultbrowser https://sourceforge.net/projects/zestypup/files/Upup-Bionic/updates/"
to be just:

Code: Select all

Exec=defaultbrowser https://sourceforge.net/projects/zestypup/files/Upup-Bionic/updates/"
:)

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#192 Post by rerwin »

I suspect the bug is the single ampersand. It should be '&&'.
  • # xmessage -title Updates_Warning -bg firebrick1 -fg white 'Updates can only be applied to\nthe original upupbb-18.05.iso\nwith md5=55e20c3e53339cf6ddbc5bc3c0c0bad1\n\nReverse_updates are available to generate\nthe original .iso from one of the updates' & defaultbrowser https://sourceforge.net/projects/zestyp ... c/updates/
    [1] 27981
    #
    [1]+ Done xmessage -title Updates_Warning -bg firebrick1 -fg white 'Updates can only be applied to\nthe original upupbb-18.05.iso\nwith md5=55e20c3e53339cf6ddbc5bc3c0c0bad1\n\nReverse_updates are available to generate\nthe original .iso from one of the updates'
    #
    #
    #
    # xmessage -title Updates_Warning -bg firebrick1 -fg white 'Updates can only be applied to\nthe original upupbb-18.05.iso\nwith md5=55e20c3e53339cf6ddbc5bc3c0c0bad1\n\nReverse_updates are available to generate\nthe original .iso from one of the updates' && defaultbrowser https://sourceforge.net/projects/zestyp ... c/updates/
    #

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

#193 Post by peebee »

18.05+7

fixes above menu / theme change snafu

+ ubuntu updates inc. openssl
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
festus
Posts: 235
Joined: Wed 14 Jan 2015, 19:10

#194 Post by festus »

peebee wrote:....
+ ubuntu updates inc. openssl
Thanks for the updates peebee

What was updated regarding openssl?

With the +6 update

Code: Select all

# openssl version
OpenSSL 1.1.0g  2 Nov 2017
After the +7 update:

Code: Select all

# openssl version
OpenSSL 1.1.0g  2 Nov 2017
Maybe it is something I'm not seeing.

Thank you, again peebee

bliss,
festus

User avatar
jplt_bis
Posts: 69
Joined: Mon 20 Feb 2017, 19:06
Location: Planete Terre

#195 Post by jplt_bis »

Hi all,

i want to make my wifi work on a puppy , how must i do to make my realtek RTL8723BS wifi shipset work ?

This shipset work on BionicDog

Thanks for your help.

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

#196 Post by peebee »

festus wrote:What was updated regarding openssl?
openssl|libssl-dev_1.1.0g-2ubuntu4.1_i386.deb
openssl|libssl1.1_1.1.0g-2ubuntu4.1_i386.deb
openssl|openssl_1.1.0g-2ubuntu4.1_i386.deb

Don't forget that in the strange ubuntu world things get updated but their version number stays the same - all very confusing....
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:

#197 Post by peebee »

jplt_bis wrote:how must i do to make my realtek RTL8723BS wifi shipset work ?
Does dmesg provide any clues?

Probably missing firmware - replace the fdrv with
http://www.fishprogs.software/puppy/fir ... 180526.sfs
suitably renamed.

or download the firmware from github and put it into:
/lib/firmware/rtlwifi
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
sszindian
Posts: 807
Joined: Sun 25 Apr 2010, 02:14
Location: Pennsylvania U.S.

Not Printing

#198 Post by sszindian »

I posted the below over in the graphics section in the mtpaint tread but after trying mtpaint (I believe the same or near version) in xenial64-7.5 and it worked just fine, I figured I'd better post here to see if it's a UPupBB thingy and not mtpaint?

---------------------------------------
Running UpupBB 18.05+6 (32 bit Bionic Beaver)

Can't get mtpaint 3.49.12 to print any graphics. My setup for mtpaint is the same as for other pup's that do print.

It won't draw the graphic-file-path into the dialog box... Manually putting the path into th‎e dialog box, still no print?

Not sure but it looks like it may be missing a gtk something or other?

Any ideas appreciated!
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]

hamoudoudou

iwlwifi deleted excepted iwlwifi-3945-2u code

#199 Post by hamoudoudou »

wireless , files iwlwifi deleted excepted iwlwifi-3945-2u code
signal strength 70/70 perfect
Outdoor with laptop and dongle 8192Cu driver : signal strength 60/70 good
Just a feedback for people needing to move..

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

Re: Not Printing

#200 Post by peebee »

sszindian wrote:Can't get mtpaint 3.49.12 to print any graphics.
GtkLP is in build and mtpaint is configured to use it.....

File -> Actions -> Print Image

brings up GtkLP dialogue...

so should be OK
Attachments
Screenshot.png
(72.41 KiB) Downloaded 495 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Post Reply