(old)Puppy Linux Discussion Forum

Updating 2 computers savefile(uefi/ntfs/lick) and savefolder(legacy) from .7 to 7.9.8 made it impossible to see(rox) mounted drives from desktop,did not investigate more.
New savefile/folder made it alright.
Lets try to break something now.
Farewell Tahrpup64...bravo 666philb & all.

oops,tumbled on error in pet:
qjackctl-0.5.5-x64_qt5.9.pet
sorry,fixed ,added menu entry and reuploaded.
Btw it need from ppm;jackd5+python-dbus+jack2_1.2.6-1,(same for muse3 sfs)

Updating 2 computers savefile(uefi/ntfs/lick) and savefolder(legacy) from .7 to 7.9.8 made it impossible to see(rox) mounted drives from desktop,did not investigate more.

I had the same problem with the desktop drive icons using an old save from Bionicpup64 7.9.7.
Click on icon and no mount indication and no Rox window showing contents.
I just figured all the messing around I did with that save, was the problem.
A fresh install of Bionicpup64 7.9.8 and a new save fixed everything with the desktop drive icons and Rox.

The problem with the drive icons not mounting drives is because the file /usr/local/bin/drive_all is missing after the upgrade. Replacing it with the one from the previous version fixes it.

Also, when compiling some applications you get errors about too many levels of symlinks. That can be fixed by copying the files inside /usr/include/sys from the devx to /usr/include/sys.

Really like this OS!

l0wt3ch wrote:The problem with the drive icons not mounting drives is because the file /usr/local/bin/drive_all is missing after the upgrade.

Woof-CE change:

https://github.com/puppylinux-woof-CE/w ... a198892cab

maybe make a symlink pro-tem

Bionicpup64 7.9.8 CE RC

Hi Phil,

Whilst looking at the System Log I noticed that scOttman´s pkg script called by the
/root/Startup/PPMUpdatedatabase script was triggering a tad too early and was taking
precedence over more vital items in the boot process such as the detection of wireless peripherals.

My first simple solution was to add a sleep 60 at the start of the script thus:
Upon reflection I did not really see a need to run it more than once per day so have now implemented
an anacron solution to do that with a 1 minute delay at boot time plus a confirmatory tone & pop-up message once it has run.

In contrast to cron, which can be disabled (default) or enabled, anacron is not a daemon. It´s task is to run one or more
jobs once only, generally on a daily, weekly or monthly basis.

For anyone using a dial-up modem or who runs 24/7, jobs can be run instantly on an ad hoc basis by issuing the
following command in a terminal:
(The -f forces the job to be run regardless of any flags/stamps and the -n ignores any specified job start delay in the anacrontab file.)

If anyone sees any merit in this approach I will post some instructions together with a pet containing the 2 files needed.
Anacron itself, [anacron_2.3-24|cron-like program that doesn´t go by time] is available via PPM.

I'm experiencing hangups during boot with 7.9.8 CE RC...
Frugal install on a Dell Latitude E6400.
This started with 7.9.8 Alpha or Beta

First hangup for 2 minutes during "Loading Kernel Modules..."

Second hangup for another 2 minutes at login, just before sarting X.

X eventually starts, with CPU at ~80%.
Task manager reveals 2 udevd processes. Once those are killed, everything runs smoothly.

I've tried swapping kernels, hangups persist.

Disabling udev completely takes care of the double process after reboot (there's a similar situation with the latest FatDog).

Other pups, recent or not, and Bionic 7.9.7 boot fine.

.
I updated the kernel that I'm using:

CPU: Dual core Intel Core2 Duo E8400 (-MCP-) speed/max: 2750/3003 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.Org 1.19.6 driver: nvidia Resolution: 1920x1080@60.00hz
OpenGL: renderer: GeForce GT 430/PCIe/SSE2 version: 4.6.0 NVIDIA 390.87
N

Working well so far.

Billtoo wrote:I updated the kernel that I'm using:

How does this make any report you give for Using Bionicpup64 7.9.8 useful?

If you change the kernel. You are no longer testing Bionicpup64 7.9.8, as it is released.
You are testing your version of Bionicpup64 7.9.8.
Any issues you report could be something you did.

Well, I guess you are confirming the kernel can be changed.

The question is, why are you changing the kernel?
Something wrong with the one in Bionicpup64 7.9.8 as it is released?

bigpup wrote: The question is, why are you changing the kernel?
Something wrong with the one in Bionicpup64 7.9.8 as it is released?

It's two updates behind:

https://www.kernel.org/

I can't get sound in firefox with the one that I'm using, sound works in kodi and vlc okay.

I updated my Slacko64-rc3 to 4-14-92 and sound works in firefox esr.

I'm just experimenting anyway so I won't post in this thread anymore.

Bigpup to Billtoo:
How does this make any report you give for Using Bionicpup64 7.9.8 useful?


Billtoo's reply:
I'm just experimenting anyway so I won't post in this thread anymore.


I mean, WTF! We get "useful" reports in how and what kernels can work, especially with different things, and this is the kind of post we get?

Bigpup, Goddamn, take your Donald-Trump-like behavior and keep it to yourself. Billtoo has single-handedly done more for solving problems, and keeping people abreast of changes that can be made, to solve problems, than anything you (or I) have did for the past 8 years. You might think you or I have posted a lot, but in all honesty we aven't posted crap compared to Bill.

Please think next time before you write some inane comment like that, especially to a valuable resource like Bill. Damn...... Why aren't you paying attention to all the people who show up in the Puppy Project and/or Puppy Derivative sections, and start polluting things with their single posts about an OS that already has a thread. Why am I the only one who patrols this, or tries to?? But, yet, somehow you have time to go after Bill for something totally stupid. Come on, wake up...


Please, Bill, don't stop posting and ignore what Bigpup wrote. He must have got a bad patch of coffee, don't know how else to explain it.

What the heck is happening with this world?? We turn on our own now???

Yes, billtoo, please continue to post.
The information you provide is valuable. Bionicpup64 is not Ubuntu Bionic Beaver. We are not bound to rigidly follow what Ubuntu does. If, as in your case, the kernel Ubuntu uses causes a problem or even if a different kernel just works better, Puppy users and especially the Dev publishing a Puppy should know about it.

One of Puppies strength's is how easy it is that it is almost as easy to change kernels as it is to change web-browsers, or anything else. It is just as important to know, perhaps more important, that kernel X breaks a major web-browser and kernel Y doesn't, than to know that Browser version 2 works while Browser version 1 doesn't.

What the heck is happening with this world??

Some say HAARP?
Some say Chemtrails?
Some say GOD?
Some say Satan?

Probably all of this together?

Back to topic BionicPup!

pain in the heck....

Boot issues resolved, by disabling Bluetooth in the BIOS.
Seems to be a common problem for older Dells with newer kernels.

This is at the RC stage of release.

What Bionicpup64 7.9.8 does, as it is released as a iso, is what is important at this point.
It is not going to be released with a different kernel than the one that is in it now.
So, that kernel needs to be used, tested, worked over, etc....

You can turn about any Puppy version into something different by changing the Linux kernel in it.

I asked a simple question.
Is there something wrong with the kernel that is in Bionicpu64 7.9.8 that you needed to change the kernel?

Answer:
It's two updates behind:

https://www.kernel.org/

I can't get sound in firefox with the one that I'm using, sound works in kodi and vlc okay.

There must be something wrong with the firefox he is using.
Quickpet>Browsers>Firefox
Download and install this Firefox and sound will work.
You should not need to change the kernel to try to fix Firefox sound.
Just need to install Firefox setup for Bionicpu64 7.9.8

belham2 wrote: Bigpup, Goddamn, take your Donald-Trump-like behavior and keep it to yourself.

Thank you for those kind words!

I updated the kernel that I'm using:

CPU: Dual core Intel Core2 Duo E8400 (-MCP-) speed/max: 2750/3003 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.Org 1.19.6 driver: nvidia Resolution: 1920x1080@60.00hz
OpenGL: renderer: GeForce GT 430/PCIe/SSE2 version: 4.6.0 NVIDIA 390.87
N

Working well so far.

Please tell me how this provides any useful information about how Bionicpup64 7.9.8 is working as it is released?

This says it must not be working, because they changed the kernel.
No info on why they changed the kernel.
Did they change it just to change it?
Did something not work?
What?
If you did something as drastic, as having to change the kernel to fix it.
I think 666philb would like some details!

.
@bigpup

Did you read the changelog in the 4.19.14 kernel?
Might be some important security fixes,better hardware support,etc there.
Why does peebee make new kernels available as soon as they are released?
Why does quickpet have the change kernels option?
Running with the latest version of the kernel is advisable don't you think?
Are new kernels released just for the hell of it?

"Which kernel" (from the horse's mouth)
Now, Ubuntu 18.04 LTS used 4.13 and LTS2 is using 4.15, none of which are LTS kernels (long story)
BionicPup decided to go with the latest stable 4.19 (now 5.0) relying on the puppy rather than the ubuntu community for any off-tree drivers. Thus changing to the latest stable is recommended for BionicPup!
However, reporting issues, or the lack thereof for the original, or any difference between the two, also helps.
If there is really no difference between the one in RC and the latest stable, why not go with the latest stable for the release of the final?

Running with the latest version of the kernel is advisable don't you think

I wish it was that simple.
Changing the kernel just because there is a newer one can break stuff.
Some things are compiled for a specific kernel and have to be recompiled if the kernel changes.

Example:
These are Nvidia driver pets of the same driver version. Each one only works with a specific Linux kernel.
nvidia-410.78_K4.19.12_x86_64.pet
nvidia-410.78_K4.19.4_x86_64.pet

Changing to a newer kernel can remove support for older hardware.
Even changing to a different kernel can bring new bugs that were not there before.
Also a Linux kernel is configured to have certain features enabled or disabled. You do that when it is compiled.
Example:
PAE feature could be enabled or disabled.
There are many things that can be disabled or enabled.

I think of it like making a new car.
At some point you have to decide exactly what engine will be in this car. Set up everything to work with that engine.
Completely test everything using that engine.
The kernel is the engine in Puppy Linux.

Why does quickpet have the change kernels option

Because people wanted to be able to change the kernel and wanted an easy way to do it.
Hopefully they understand what they are doing and why.
If you look at the kernels offered in change kernel.
Click on the kernels button.
They are ones already used in a Puppy version and those kernels are already compiled for how Puppy works.

The only time changing the kernel, did anything for me, was when I got a very new wifi router.
The kernel I was using was too old and did not have the driver modules for it.
A newer kernel did have the modules.
But after changing the kernel, my Nvidia driver no longer worked.
I had to compile a new Nvidia driver for that kernel.