Puppy Linux Discussion Forum

[musher0]

Hi!

I did solve a problem -- and maybe discovered a bug in probedisk.

When the disk icons are reduced to one in the bottom left corner, cpu usage jumps to between 50 and 100 %.

When the icons are displayed by default as one icon per drive, cpu usage varies between 10 and 49 % -- which is normal. I'm currently at 43 % -- according to conky -- writing this in opera, which is a bit of a cpu and memory hog.

Puppy system on which this bug was encountered : Puppy Ludid 5.2.5 retro, the one with the 2.6.30.5 kernel.

Compy: Intel 1.8 MgHz
Video card: Nvidia MX 4400

Has anybody noticed the same behaviour when reducing the number of disk icons to one? In other words, is it just me and my workhorse, or is this a widespread Puppy bug?

(You don't need to answer, since I perchance solved the problem. I'm only posting this for reference.)

BFN.

[musher0]

Still, from the point of view of desktop design, it would be nice not to have to display the whole slew of disk icons...

[Karl Godt]

The program that manages the drive icons is /sbin/pup_event_frontend_d .

It includes many internal functions and external scripts .

Rox-Filer displays the icons . I had always all partitions on the desk , and while experimenting with `which eventmanager` i think i had these minimized to one icon and can not remember any problems that time .

/sbin/pup_event_frontend_d has changed at least from puppy version 4.3 to 4.3.1 .

Also checkout if `which mut` is running as daemon in the background .

I am using xosview to display the CPU usage .

And on a one-core CPU it was always visible the polling of /sin/pup_event_frontend_d every 4 seconds witch a peak in the cpu line of xosview .

[musher0]

Nice app, this xosview...

But looking at your image, I can see a disk. Therefore, you are not using the reduced function of pup_event_front_end_d. Thus, your results are for "normal" display/activity.

Do you think you can retry your test with the "front_end" display reduced to the one icon at the bottom left?

The results would then be more conclusive, no?

I should add that my machine has 1.25 Gb of RAM, 192 Mg's of which are used as a ramdrive.

Someone with less ram would have "stangled" his machine, I think, with this problem.

TWYL.

[Karl Godt]

NO problem here ...

I must say that i have made many adjustments to /sbin/pup_event_frontend_d and /usr/sbin/eventmanager mainly to add start|restart|stop parameter AND to check for /tmp/pup_event_icon_change_flag to redraw the icons without need to restart X AND to check for the position of the taskbar ...

I also adjusted /sbin/probepart AND /sbin/probedisk2 to cope with different kernel configurations like the ones mavrothal posted at Barry's blog shortly AND EXTENDED_BLOCK_MAJORS ...

In the beginning many ways lead somewhere AND all adjustments i made are at least slightly different every partition ...

Soooo ...

I am also running 95%+ full installed ...

One idea i could think of is if the USB is loose attached the two files /root/.usb* seems to get updated every 2 or 4 seconds ... perhaps check the hidden files in your /root directory AND if rox shows a scanning in the window frame ... someone some time ago posted that problem in the USERS or BEGINNERS section , maybe search for my name AND probedisk OR probepart ...

[Karl Godt]

NEXT Partition : no PROBLEMS

[musher0]

Hello, Karl.

I discovered there was a way to disable the eventmanager altogether. It is actually a luxury, since Puppy doesn't need it to run properly.

It's in the FULL Puppy Event Manager, first pane ("Activate"). I unticked the "hotplug module/firmware loading" item, and my cpu is running sometimes as low as 6 %. Happy as a deer, now!

TWYL.