Um, no, it's Barrys in the repo. (see screeny).
Lucid Puppy 5.1- A Full-Featured Compact Distro
- abushcrafter
- Posts: 1418
- Joined: Fri 30 Oct 2009, 16:57
- Location: England
- Contact:
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
weird behavior of CPU frequency scaling
Even with 204 I'm still getting strange behavior from the CPU frequency scaling utility. One point I notice is that the window sometimes says 1.3-1 and sometimes 1.3-2. This sounds like a race condition between two versions.
I'm also being told any module I try is incompatible. This machine has been working with the AMD powernow K8 module. After I futz with things for some time, I have been able to get a window which says CPU frequency scaling is already running. This appears to be non-deterministic, and I don't have any guaranteed way to get this started.
Once it starts, I can see the reported temperature go down. After I get it started, it appears to run without problems on later boots.
I'm also being told any module I try is incompatible. This machine has been working with the AMD powernow K8 module. After I futz with things for some time, I have been able to get a window which says CPU frequency scaling is already running. This appears to be non-deterministic, and I don't have any guaranteed way to get this started.
Once it starts, I can see the reported temperature go down. After I get it started, it appears to run without problems on later boots.
Here is an update to luci-204. It corrects the wrong Nvidia pet in Puppy Package Manager, and adds the new Arora pet by James C. It also assigns the defaultaudioplayer to gnome-mplayer. Finally, it adds a config for Qt programs, which we have several of now in the PPM, Arora, SMPlayer, and Scribus, at least.
http://www.diddywahdiddy.net/Puppy500/u ... 100617.pet
Also, updating the repos in Puppy Package Manager will get the correct Nvidia pet and the new Arora. It may be necessary to reboot.
James C, you will see a different color scheme on Arora after applying the update pet. It's not set, but I thought it was better than the scheme the qt programs have by default.
http://www.diddywahdiddy.net/Puppy500/u ... 100617.pet
Also, updating the repos in Puppy Package Manager will get the correct Nvidia pet and the new Arora. It may be necessary to reboot.
James C, you will see a different color scheme on Arora after applying the update pet. It's not set, but I thought it was better than the scheme the qt programs have by default.
Last edited by playdayz on Thu 17 Jun 2010, 21:13, edited 2 times in total.
Me too, prehistoric. It sounds the same--powernow-k8 is the one that should work--in fact, has worked in previous versions on this computer. I am being told that it is not compatible. I just refreshed and it asked me to reboot, so I will try that.strange behavior from the CPU frequency scaling utility. One point I notice is that the window sometimes says 1.3-1 and sometimes 1.3-2. This sounds like a race condition between two versions.
I'm also being told any module I try is incompatible. This machine has been working with the AMD powernow K8 module.
Do you happen to recall when it stopped working correctly? I think it is trio's program and I think he is not doing much with Puppy now. Maybe some one will take it over.
- abushcrafter
- Posts: 1418
- Joined: Fri 30 Oct 2009, 16:57
- Location: England
- Contact:
Re: Doh! moment on customization
This is just about what I have wanted for some time.seaside wrote:Here's a script that I put together to test md5sums.
I use it on a right-click -file - open with -menu. Paste the md5sum in the box and it makes the comparison.
It also could be adapted to run in other ways as well.Code: Select all
#!/bin/sh -a checksum() { echo "$MDSUM $1" >/tmp/mdsumtmp [ "`md5sum -c /tmp/mdsumtmp`" ] && yaf-splash -font "12x24" -outline 0 -bg green -bd green -text "Checksum OK -- click on message when finished" || yaf-splash -font "12x24" -outline 0 -bg orange -bd orange -text "Checksum BAD! -- click on message when finished" } GUI=$(cat <<EOV|sed "s/#.*//" # enable interpolation and comments <window title="Check Md5sum"> <frame> <hbox> <text> <label>Md5sum digits:</label> </text> <entry activates-default="true"> <default>Paste Md5sum here</default> <variable>MDSUM</variable> </entry> <button can-default="true" has-default="true"> <input file>"/usr/local/lib/X11/pixmaps/archive24.png"</input> <label>Check Sum</label> <action>checksum $1</action> </button> <button cancel> <action type="exit">QUIT</action> </button> </hbox> </frame> </window> EOV) CHOICES=`gtkdialog3 -p GUI`
Cheers,
s
However please could you add these features:
- Quits when Esc is pressed.
- When the splash "Checksum BAD!/ok" is shown. I could do with being able to press enter and and the program quits.
Last edited by abushcrafter on Thu 17 Jun 2010, 21:57, edited 1 time in total.
OK, thanks.abushcrafter wrote:Arora uses QTWebKit, so not the same WebKit as Midori.01micko wrote:I just wonder if we should offer Webkit as a separate download, then browsers like Midori and Arora could be smaller pets. Plus there are a ton of other browser projects out there dependant on webkit.
Thoughts?
Puppy Linux Blog - contact me for access
jwm-492-i18n
i built i18n'ed jwm-492 on Lupu-5.0.1, tested both on Lupu-5.0.1 and Lupu-204.
http://www.murga-linux.com/puppy/viewtopic.php?t=51847
http://www.murga-linux.com/puppy/viewtopic.php?t=51847
Happy Fun Time with 204 here. I used 01micko's dir2pet script to make a 145meg pet for Open Office. I did it quick-and-dirty, I want to do it again and pay attention to details this time, will post when done. Also got Filezilla 3.3.1 going, and will pet that up as well.
Edit: Just found that there's a Filezilla 3.3.3 pet already. There I go reinventing the wheel...
Edit: Just found that there's a Filezilla 3.3.3 pet already. There I go reinventing the wheel...
- Attachments
-
- OOon204.jpg
- (67.92 KiB) Downloaded 1068 times
Last edited by tubeguy on Fri 18 Jun 2010, 04:23, edited 1 time in total.
[b]Tahr Pup 6 on desktop, Lucid 3HD on lappie[/b]
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
cpu frequency scaling
It is indeed from trio. I'm looking through older systems to find a change responsible for bugs. At this point, nothing jumps out at me. As I recall, he had difficulty testing on multi-processor machines. It looks like he is launching a copy of his script for each processor.playdayz wrote:...Do you happen to recall when it stopped working correctly? I think it is trio's program and I think he is not doing much with Puppy now. Maybe some one will take it over.
What I'm guessing, at this point, is that it was working correctly on single-processor machines, or on multi-processor machines booted without smp. It may have worked on some multi-processor machines with smp more or less by accident, then stopped working when a new system changed timings. We can probably get it to work on specific machines just by fiddling with delays. This is not a general solution.
I don't see anything in the code I understand which looks like it is designed to deal with real concurrency. It's working on a netbook which says it has two processors, but this is merely hyperthreading with a single core. There is no physical parallelism.
I've got a considerable learning curve if I'm going to make sense out of what he's done. Younger people will probably get there ahead of me.
Added: I may have been lucky. I just found a difference to the way it works under Stardust13 and Luci204. The start_cpu_freq script in Startup is empty in Luci. When I pasted in this code, inserted by his script under Stardust, it worked.
Code: Select all
#!/bin/sh
modprobe powernow-k8
modprobe cpufreq_ondemand
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 2600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 2600000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
More bones to chew on... well they are the same old bones, freshened up a little..
James and tubeguy..and anyone else having a play with the script, I have altered the debs2pkg script to now have a pause so you can go searching through the newly created directory tree to find the icon you want for the menu entry, and if there is not a suitable one there you can add your own. While you are paused you can edit the dot_desktop file to point to the icon, the way Puppy likes it
James... I have fixed the browser-default program to find any browser installed, so now arora will show up in the list. What it does is search the .desktop files looking for browsers, even Netsurf shows up now, and Puppy browser doesn't, unless you install it of course.
Jim.. and I'm a good dog now! It's DuDE compliant! But, if you have made changes to your tray the files will overwrite what's there and your tray will be back to the DuDE default plus the browser icon. I haven't tested how well it plays entirely with DuDE if you change tray stuff in PCC, for example the number of desktops, it may be something to check.
Playdayz.. since this app has been a staple from near the start of Lupu-Luci then I gather that the JWM tray file (/root/.jwmrc-tray) has been changed upstream when building from Woof, is that correct? Reason I ask is that the pet attached has the jwm file stored in /tmp and it is transferred to /root by the pinstall.sh script. This is for DuDE compliance, else it breaks the DuDE menus. If not then just replace the script in browser-default-0,8. Jim has to install the DuDE compliant version after installation of DuDE anyway.
Shinobar... I noticed no change using your JWM, which is as it should be for me using my locale . I did rename the executable back to just "jwm"
Cheers all
EDIT: as a side note shinobar's Realplayer videos play just fine in Seamonkey, not in Chromium
James and tubeguy..and anyone else having a play with the script, I have altered the debs2pkg script to now have a pause so you can go searching through the newly created directory tree to find the icon you want for the menu entry, and if there is not a suitable one there you can add your own. While you are paused you can edit the dot_desktop file to point to the icon, the way Puppy likes it
James... I have fixed the browser-default program to find any browser installed, so now arora will show up in the list. What it does is search the .desktop files looking for browsers, even Netsurf shows up now, and Puppy browser doesn't, unless you install it of course.
Jim.. and I'm a good dog now! It's DuDE compliant! But, if you have made changes to your tray the files will overwrite what's there and your tray will be back to the DuDE default plus the browser icon. I haven't tested how well it plays entirely with DuDE if you change tray stuff in PCC, for example the number of desktops, it may be something to check.
Playdayz.. since this app has been a staple from near the start of Lupu-Luci then I gather that the JWM tray file (/root/.jwmrc-tray) has been changed upstream when building from Woof, is that correct? Reason I ask is that the pet attached has the jwm file stored in /tmp and it is transferred to /root by the pinstall.sh script. This is for DuDE compliance, else it breaks the DuDE menus. If not then just replace the script in browser-default-0,8. Jim has to install the DuDE compliant version after installation of DuDE anyway.
Shinobar... I noticed no change using your JWM, which is as it should be for me using my locale . I did rename the executable back to just "jwm"
Cheers all
EDIT: as a side note shinobar's Realplayer videos play just fine in Seamonkey, not in Chromium
- Attachments
-
- browser-default-0.9.pet
- (2.33 KiB) Downloaded 306 times
-
- debs2pkg-0.3.tar.gz
- (2.06 KiB) Downloaded 294 times
Puppy Linux Blog - contact me for access
Sweet!01micko wrote:James and tubeguy..and anyone else having a play with the script, I have altered the debs2pkg script to now have a pause so you can go searching through the newly created directory tree to find the icon you want for the menu entry, and if there is not a suitable one there you can add your own. While you are paused you can edit the dot_desktop file to point to the icon, the way Puppy likes it
[b]Tahr Pup 6 on desktop, Lucid 3HD on lappie[/b]
If it is already installed it won't show up as a choice, but it should show up in the bottom window as installed. But the way I did that update mgiht have confused something.I did install Mick's great nvidia driver before the ppm update. Nvidia doesn't show up as a choice now that the ppm update has been installed. Is that normal?
Radeonhd is Quickpet is not the one that gives hardware acceleration (it is just an alternate to the radeon driver--that gives 16-bit which is the only difference I have seen) For hardware acceleration the one is now the Xorg_Full in PPM.Installed the HDradeon with quickpet
it is showing up in the package manager but after a x
restart or even full restart it is not coming up in the
Hardinfo settings - which it did previously
Am I forgetting something?
Got Fotoxx btw. It looks nice.
Last edited by playdayz on Fri 18 Jun 2010, 18:42, edited 1 time in total.
Yes, We need to keep a list somewhere. I guess that would be my jobdit: Just found that there's a Filezilla 3.3.3 pet already. There I go reinventing the wheel...
How about in the first message of this thread?
Also tubeguy, They say that there is no advantage in splitting up the components of OpenOffice--but I wonder--even a small savings in size might be helpful.
Please read everyone. It is great to have help making program packages. It is a contribution to a better Lucid Puppy 5.1. Thank you very much.
Please consider this. In making the packages there is a strong preference for using Ubuntu binaries or compiling the program in a version of luci (the testing releases for Lucid Puppy 5.1). The reason for this is that there is a presumption of stability. The Ubuntu binaries are not the same infrastructure as previous or other Puppies. and mix and match would not be a good idea. Only in special cases would we want to use a package that was not made from the Ubuntu binaries or compiled in luci, and that would be only after we tried to build it in those two ways.
I just thought of this additional thing. We should build and test the packages in the latest version of luci. We should be careful *not* to add any libraries, etc., that are already in luci--because when the package would be removed it would take those libraries with it. So if we build and test in luci I think that would take care of itself. Thanks
And also, we should uninstall everything else before building a package, so it is just the base luci-204. If anything else is installed it might provide a dependency that would not always be present.
Please consider this. In making the packages there is a strong preference for using Ubuntu binaries or compiling the program in a version of luci (the testing releases for Lucid Puppy 5.1). The reason for this is that there is a presumption of stability. The Ubuntu binaries are not the same infrastructure as previous or other Puppies. and mix and match would not be a good idea. Only in special cases would we want to use a package that was not made from the Ubuntu binaries or compiled in luci, and that would be only after we tried to build it in those two ways.
I just thought of this additional thing. We should build and test the packages in the latest version of luci. We should be careful *not* to add any libraries, etc., that are already in luci--because when the package would be removed it would take those libraries with it. So if we build and test in luci I think that would take care of itself. Thanks
And also, we should uninstall everything else before building a package, so it is just the base luci-204. If anything else is installed it might provide a dependency that would not always be present.
Used the Ubuntu packages and made a pet for XFE file manager.
This Xfe pet includes Xfwrite text editor, Xfimage image viewer,Xfe file manager,Xfview text viewer and Xfpack package manager.
Download link..............2.83 mb Xfe-1.32.1 pet
http://www.datafilehost.com/download-a8eacc95.html
Pet was made from Ubuntu packages in Luci 204 and tested in 204 and Lucid Puppy 501.
Test it ,mirror it and have fun.
This Xfe pet includes Xfwrite text editor, Xfimage image viewer,Xfe file manager,Xfview text viewer and Xfpack package manager.
Download link..............2.83 mb Xfe-1.32.1 pet
http://www.datafilehost.com/download-a8eacc95.html
Pet was made from Ubuntu packages in Luci 204 and tested in 204 and Lucid Puppy 501.
Test it ,mirror it and have fun.
- Attachments
-
- xfe file manager.png
- (105.43 KiB) Downloaded 1540 times
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
That should be useful - will see if I can delete files from my camerasmade a pet for XFE file manager
SD card which seem ultra protected (a good thing on the whole)
Many thanks. It has no title bar for resizing or dragging?
Tried icewm - reminder that xwin icewm has to be entered
after pressing ctrl+alt + backspace (save open files first)
Can a menu item be entered/included?
Tried Skype
After trying to download from 3 repos - gave up
(yep a typical user response)
Liked Lucid repo being the only available
download by default in the package manager
Giving access to more does not make them usable
for most users