Page 2 of 53

Posted: Sat 17 Sep 2011, 21:07
by jim3630
pemasu hope don't mind i posted the firmware pet and linked backed to here.

http://murga-linux.com/puppy/viewtopic. ... 809#564809

Posted: Sat 17 Sep 2011, 21:10
by pemasu
No problem. The firmware compressed package was originally provided by Tempestuous. I only made pet of it. You should add the url link for supported chips, which I posted. People get from that link the understanding for whom those firmwares are needed.

Posted: Sat 17 Sep 2011, 21:14
by DaveS
There is just so much here to like :)

Posted: Sat 17 Sep 2011, 22:19
by radky
The date48.png in /usr/local/lib/X11/themes/Trinity is a 24-pixel image, and looks very small when linked to "Plan" on the JWM desktop. :)

Posted: Sat 17 Sep 2011, 22:24
by pemasu
Radky. Yes I know. I thought I had fixed it but it seems I havent moved the fix to the woof. I will now.
Thank you. I have replacement anyway already picked.

Posted: Sat 17 Sep 2011, 22:38
by pemasu
Radky, and others. What do you think this replacement for JWM-Pinboard.

Edit. Blue Step Humanity still has the problem. Originally I needed the change because e17 needed better icon, the original was only black patch.

Oh well, it needs more investigation. I dont like tempering with icons used with several instances, but these are the mandatory ones for e17.

Maybe I change e17 to the Openbox-Fbpanel and make link to the Dave S great tuning thread.

Posted: Sat 17 Sep 2011, 23:21
by radky
pemasu wrote: Maybe I change e17 to the Openbox-Fbpanel and make link to the Dave S great tuning thread.
Dave's Openbox-Fbpanel Desktop works great in Dpup Exprimo. :)
http://www.smokey01.com/pemasu/pet_pack ... o-1.30.pet
http://www.smokey01.com/pemasu/pet_pack ... mo-1.1.pet

Posted: Sun 18 Sep 2011, 07:20
by tempestuous
jim3630 wrote:The new brcm80211 worked after installing only the firmware pet. the driver is pre-installed in the kernel.
That's good news.

pemasu, I would now make the bold suggestion that you remove the proprietary broadcom_sta driver driver from the first post, so that all users of modern Broadcom wifi devices will then have only one option - the brcm80211 drivers. I have several reasons:

i) for consistency and to avoid confusion - you don't want users reporting Broadcom wifi errors and getting confused about which driver is actually being used. They might not understand the difference, and inadvertently report wrong information.

ii) the proprietary driver will continue to conflict with the underlying ssb driver, and potentially cause problems with other hardware that depends on the ssb driver - such as USB interfaces.

iii) we should be encouraging the use of opensource drivers, whenever possible.

I suggest you add the brcm-firmware to future releases.

Posted: Sun 18 Sep 2011, 09:08
by pemasu
Tempestuous. I will do as you suggested. Straight logic behind your reasoning.

Posted: Mon 19 Sep 2011, 18:58
by jim3630
only error found so far is when connecting a usb storage device then maybe 12 gtkdialog idrive pannels appear repeating some of the drives. upon disconnecting 3 duplicate gtkdialog boxes appear showing idrive pannel with current available drives.

Posted: Mon 19 Sep 2011, 19:07
by pemasu
Hmmm, maybe I should remove gtkdialog binary..... :D

Posted: Mon 19 Sep 2011, 19:13
by jim3630
added a pic but the pic of 12 or more is too large to post.

Posted: Mon 19 Sep 2011, 19:19
by pemasu
Yeah, Idrive panel has been put in so that people can test it with e17. It has showed that it is not overly compliant under e17.

Idrivepanel

Posted: Mon 19 Sep 2011, 20:25
by Béèm
Indeed even in 5X6 I saw already that there are multiple gtk and I drivepanel processes.

Posted: Mon 19 Sep 2011, 20:27
by pemasu
Thats interesting. I wonder what creates those multiple processes.

Posted: Mon 19 Sep 2011, 20:28
by Béèm
Is it on purpose that the SMP and non-SMP ISO have the same name and size?

Posted: Mon 19 Sep 2011, 20:36
by pemasu
The distro name inside the build is different. And I created different threads for them.
And yes, both have almost same kernel specs, only other is optimized for multicores and other for intel atom, they use same woof version, overall apps, and version numbers are the same. I added some usability stuff more to the main version, and some small apps.

But there is overall 993 packages, 99 % is the same.
So....I thought it is much easier for me to remember the stuff inside when people refer to 5.X.7 version. Also, there isnt much need to update to the main version from this SMP multicore version atm.

I could have named this one totally different, but this uses stuff intended to the main 5.X.7 so....

Posted: Mon 19 Sep 2011, 20:41
by Béèm
pemasu wrote:Thats interesting. I wonder what creates those multiple processes.
I just launched Idrive panel.

Code: Select all

# ps |grep Idrivepanel
17329 root       0:00 /bin/sh /usr/sbin/Idrivepanel
17337 root       0:00 /bin/sh /usr/sbin/Idrivepanel
17731 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
20532 root       0:00 grep Idrivepanel
# 
Two Idrivepanel processes. (still in 5X6)

Posted: Mon 19 Sep 2011, 21:09
by pemasu
Beem. If you mount and unmount several times, do you get accumulating count of them

Posted: Tue 20 Sep 2011, 08:19
by Béèm
pemasu wrote:Beem. If you mount and unmount several times, do you get accumulating count of them
Tried in 5X6 still.
No, I didn't get accumulation of processes.
But I booted this morning from 5X6 still and did get now:

Code: Select all

# ps |grep Idrivepanel
 8437 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 8660 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 8728 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 8904 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 8990 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9205 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9283 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9523 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9616 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9820 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9932 root       0:00 /bin/sh /usr/sbin/Idrivepanel
 9956 root       0:00 /bin/sh /usr/sbin/Idrivepanel
10077 root       0:00 /bin/sh /usr/sbin/Idrivepanel
10127 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
10644 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
11018 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
11376 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
11499 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
11525 root       0:00 gtkdialog3 -p Idrivepanel --class Idrive --geometry 850x90+1+1000
11823 root       0:00 grep Idrivepanel
# 
I drivepanel is started in Startup.

But I get now 5 gtkdialog entries in the window list.
They indicate different states of Idrivepanel.
One is really significant. Very weird.