Bionicpup64 8.0 CE

Message

bigpup · #616 Post by **bigpup** » Fri 22 Feb 2019, 22:07

ITSMERSH wrote:
oui wrote:Hi Rainer

ITSMERSH wrote: Where to download?
look at the signature of 666philb
7.9.8?

There is no Xenialpup 7.9.8.
I made a mistake and typed Xenialpup when a meant to type Bionicpup.

ITSMERSH · #617 Post by **ITSMERSH** » Fri 22 Feb 2019, 23:56

Fresh install booted into ram only (pfix=ram).

Grub4DOS Boot Menu Entry wrote:title Puppy Testing (RAM) \n Originalversion
find --set-root --ignore-floppies /PupTest/initrd.gz
kernel /PupTest/vmlinuz plang=de_DE.UTF-8 pkeys=de psubdir=PupTest pmedia=atahd pfix=ram
initrd /PupTest/initrd.gz

666philb · #618 Post by **666philb** » Sat 23 Feb 2019, 01:29

ITSMERSH wrote:Fresh install booted into ram only (pfix=ram).

Grub4DOS Boot Menu Entry wrote:title Puppy Testing (RAM) \n Originalversion
find --set-root --ignore-floppies /PupTest/initrd.gz
kernel /PupTest/vmlinuz plang=de_DE.UTF-8 pkeys=de psubdir=PupTest pmedia=atahd pfix=ram
initrd /PupTest/initrd.gz

hi ITSMERSH ,

do you still get the problem if you boot without the German settings?

Code: Select all

kernel /PupTest/vmlinuz psubdir=PupTest pmedia=atahd pfix=ram

ITSMERSH · #619 Post by **ITSMERSH** » Sat 23 Feb 2019, 07:26

do you still get the problem if you boot without the German settings?

No.
Everything's fine then.

But would be cool if it would work with those German settings, as I need them in the kernel line booting into RAM only in general.

666philb · #620 Post by **666philb** » Sat 23 Feb 2019, 09:59

ITSMERSH wrote:
do you still get the problem if you boot without the German settings?
No.
Everything's fine then.

But would be cool if it would work with those German settings, as I need them in the kernel line booting into RAM only in general.

before i raise an issue on woofce, does it affect any other applications or just pmount?

RedQuine · #621 Post by **RedQuine** » Sat 23 Feb 2019, 10:34

Two issues with the upgrade, although one of them is minor:

1. On first boot, I was unable to configure my trackpad with flSynclient. A dialog box popped up, but it only had an exclamation mark in it (no text), and when I clicked OK, flSynclient closed. Once I'd created a fresh pupsave and rebooted, it worked perfectly - so this one's definitely just a minor issue.

2. I decided to be sensible and boot into RAM as suggested. I then created a new pupsave and rebooted.

At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

Should I have copied everything off it before I rebooted with the new pupsave? I've never had to do that before; unless I upgraded it, the old one was left untouched. Not a disaster as I had a recent backup, but worth mentioning nonetheless.

Other than that, everything's looking great so far. Many thanks!

666philb · #622 Post by **666philb** » Sat 23 Feb 2019, 10:49

RedQuine wrote:Two issues with the upgrade, although one of them is minor:

1. On first boot, I was unable to configure my trackpad with flSynclient. A dialog box popped up, but it only had an exclamation mark in it (no text), and when I clicked OK, flSynclient closed. Once I'd created a fresh pupsave and rebooted, it worked perfectly - so this one's definitely just a minor issue.

2. I decided to be sensible and boot into RAM as suggested. I then created a new pupsave and rebooted.

At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

Should I have copied everything off it before I rebooted with the new pupsave? I've never had to do that before; unless I upgraded it, the old one was left untouched. Not a disaster as I had a recent backup, but worth mentioning nonetheless.

Other than that, everything's looking great so far. Many thanks!

there's been a lot of changes in woofce during bionicpupos development and using old savefiles from the betas isn't recommended and is known to cause problems

artsown · #623 Post by **artsown** » Sat 23 Feb 2019, 12:12

Fresh "from scratch" frugal to hard drive of 8.0 using a core i5 and 4 gig
ram desktop. Installation of all my usual stuff was uneventful. It seems that
8.0 is noticeably faster than the 7.9.8 rc.

I noticed that 8.0 has the same old HTOP version 1.0.3 that xenialpup64
version 7.5 has. Ram useage reports are now much lower than they
are on bio 7.9.8 rc with its version 2.0.2 version HTOP. In fact, the
ram useage reports are comparable to xenialpup64. I wonder why
you chose the old and outdated version of HTOP for the 8.0 release?

Anyway, your bionicpup64 is by far the best pup for my purposes, and
I thank you again for it!

Art

RedQuine · #624 Post by **RedQuine** » Sat 23 Feb 2019, 13:28

666philb wrote:
RedQuine wrote: At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

there's been a lot of changes in woofce during bionicpupos development and using old savefiles from the betas isn't recommended and is known to cause problems

I appreciate the reasons for the change and I'm absolutely fine with them. However, there were icons and application settings in there which shouldn't have caused any problems with woofce, and I appear to have lost them all permanently. As I say, I have a backup so it's not a disaster. I was just wondering why the old pupsave was wiped during the upgrade.

666philb · #625 Post by **666philb** » Sat 23 Feb 2019, 14:18

artsown wrote:Fresh "from scratch" frugal to hard drive of 8.0 using a core i5 and 4 gig
ram desktop. Installation of all my usual stuff was uneventful. It seems that
8.0 is noticeably faster than the 7.9.8 rc.

I noticed that 8.0 has the same old HTOP version 1.0.3 that xenialpup64
version 7.5 has. Ram useage reports are now much lower than they
are on bio 7.9.8 rc with its version 2.0.2 version HTOP. In fact, the
ram useage reports are comparable to xenialpup64. I wonder why
you chose the old and outdated version of HTOP for the 8.0 release?

Anyway, your bionicpup64 is by far the best pup for my purposes, and
I thank you again for it!

Art

believe it or not this wasn't deliberate & i've just spent the last 40mins trying to figure this out. Htop has always been a .pet in bionic and when building with woof it looks for the .pet in allocated repos. in bionicpup it looks in this order.
Packages-puppy-bionic-official
Packages-puppy-noarch-official
Packages-puppy-xenial64-official
Packages-puppy-tahr64-official
Packages-puppy-common64-official
i built htop 2.10 for bionicpup but never added to bionicpups repo as it didn't render properly in urxvt with its default settings.
so woof not finding htop in bionicpup repo should next look in noarch not find it there,and then xenial where it does find it.
in this build this is what it has done and grabbed xenials htop 1.0.3.

unusually in older builds, it skipped the htop in xenials repo and grabbed htop 2.0.2 from tahrpups repo. (no idea why this htop-2.0.2 never got used in tahr or xenial, was possibly added for tahr6.0.6 which never materialised)

anyway i'm currently re-uploading the iso & devx as i missed a printing bug fix, so i also added htop 2.0.2 as i think it shows a more realistic memory usage.

thanks for pointing this out.

666philb · #626 Post by **666philb** » Sat 23 Feb 2019, 14:26

RedQuine wrote:
666philb wrote:
RedQuine wrote: At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

there's been a lot of changes in woofce during bionicpupos development and using old savefiles from the betas isn't recommended and is known to cause problems
I appreciate the reasons for the change and I'm absolutely fine with them. However, there were icons and application settings in there which shouldn't have caused any problems with woofce, and I appear to have lost them all permanently. As I say, I have a backup so it's not a disaster. I was just wondering why the old pupsave was wiped during the upgrade.

hi RedQuine,

i've just tested and seen what you mean. i've taken down the iso and will raise an issue on woofce

thankyou for reporting

ITSMERSH · #627 Post by **ITSMERSH** » Sat 23 Feb 2019, 15:14

before i raise an issue on woofce, does it affect any other applications or just pmount?

I don't know.

Is there any other applications that could be affected?

bigpup · #628 Post by **bigpup** » Sat 23 Feb 2019, 16:00

The first Bionicpup64 8.0
Fresh Frugal, using save folder

Before or while you are rebuilding.

I need to use pmcpucurt64 for my temp readout on the tray.

I see you have a pet for it in the Bionicpup64 repository.

In PPM did a search for pmcpucurt64.
The results are it is already installed.

Did a search for it in Pfind.
It says it could not find it

Not sure what is going on here.

From a earlier post. Not sure if this is corrected yet.

CPU temperature monitor for 64-bit Pups
I see someone has uploaded pmcpucurt64.pet to the ibiblio.org site for bionicpup64 pet packages.
http://distro.ibiblio.org/puppylinux/pe ... -bionic64/
This pet package is missing the /root/.config/autostart/pmcpucurt.desktop

So, when the pet is installed. Nothing is put into the autostart directory to make the program load. Thus it is not running and no temp is displayed in the tray.

Here is the topic for pmcpucurt64
http://murga-linux.com/puppy/viewtopic.php?t=114502

Update:
I went to the pmcpucurt64 topic and downloaded and installed the pmcpucurt64.pet.
I also needed the sensors64x.pet.
Now have a working temp indicator in the tray.

mavrothal · #629 Post by **mavrothal** » Sat 23 Feb 2019, 16:27

No major complains

I was surprised at first with these automatic connections on startup but I realised is because of all these scripts in the Startup folder.

Here is the proprietary "wl" broadcom wifi driver and the Facetime broadcom 1570 PCIe webcam driver for the Bionicpup64 8.0 CE, if anyone needs them.

rockedge · #630 Post by **rockedge** » Sat 23 Feb 2019, 17:08

when will the ISO and devx be avialable for download again?

666philb · #631 Post by **666philb** » Sat 23 Feb 2019, 17:09

bigpup wrote: I see you have a pet for it in the Bionicpup64 repository.

In PPM did a search for pmcpucurt64.
The results are it is already installed.

hi bigpup,
it definitely isn't installed and wasn't meant to be. as far as i can tell it was how the .pet was named in Packages-puppy-bionic64-official

i've renamed the .pet and re-uploaded and it now seems fixed (need to update PPM) BTW sensors is included in the package

BTWx2 careful as i've had to pull the iso until a savefile issue is fixed in woof.
https://github.com/puppylinux-woof-CE/w ... ssues/1335

666philb · #632 Post by **666philb** » Sat 23 Feb 2019, 17:11

mavrothal wrote:No major complains
I was surprised at first with these automatic connections on startup but I realised is because of all these scripts in the Startup folder.

Here is the proprietary "wl" broadcom wifi driver and the Facetime broadcom 1570 PCIe webcam driver for the Bionicpup64 8.0 CE, if anyone needs them.

thanks mavrothal,

i'll add them before re-uploading

BTW careful as i've had to pull the iso until a savefile issue is fixed in woof
https://github.com/puppylinux-woof-CE/w ... ssues/1335

666philb · #633 Post by **666philb** » Sat 23 Feb 2019, 17:15

rockedge wrote:when will the ISO and devx be avialable for download again?

hi rockedge,

i'll re-upload as soon as the savefile issue gets fixed in woof.

https://github.com/puppylinux-woof-CE/w ... ssues/1335

ITSMERSH · #634 Post by **ITSMERSH** » Sat 23 Feb 2019, 21:45

i'll re-upload as soon as the savefile issue gets fixed in woof.

Why do they break stuff, that has worked very well for years?

In my tahr based ArtStudio everything still works fine. Even though I modified the dependent scripts to have also the free space of a drive in the tooltips of drive icons.

The new scripts still don't have such feature, so why to fix anything within these scripts that wasn't broken?

Hopefully it will not take years to fix that broken development.

rockedge · #635 Post by **rockedge** » Sun 24 Feb 2019, 01:11

@666philb,

Thank you for the information. I am looking forward to the fix and using Bionicpup64 8.0 CE very much...... for advancing the Puppy Linux - ZoneMinder platform using object detection and recognition

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Bionicpup64 8.0 CE