| Author |
Message |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Sun 31 Oct 2010, 13:51 Post subject:
|
|
| Iguleder wrote: | | tazoc, do you want me to upload the kernel PET I made so you can replace the Lighthouse kernel (someone wrote a guide for that), to make development easier? | That's very kind of you! In fact I was just browsing http://brainwavedesigncentral.net/dima/2.6.35.7-tickless_smp_ht-dpup/
From Barry's Blog or somewhere I read that OpenOffice won't work on 2.6.35, have you tried OO on it?
Thanks,
TazOC
[Edit:]Make that LibreOffice
_________________ lhpup.org Lighthouse 64 6.01
Last edited by tazoc on Sun 31 Oct 2010, 14:42; edited 1 time in total
|
|
Back to top
|
|
 |
Iguleder

Joined: 11 Aug 2009 Posts: 1611 Location: Israel, somewhere in the beautiful desert
|
Posted: Sun 31 Oct 2010, 14:07 Post subject:
|
|
2.6.35.x and 2.6.36 proved to be total crap, we're staying with the good 2.6.32.x. I patch it to appear as 2.6.32 so I can replace it with later 2.6.32.x version to enjoy bug fixes (after all, what's the point in using a LTS kernel if you don't upgrade it?) without breaking third-party drivers. Hardware support is very good and there's nothing vital in 2.6.33.x or 2.6.34.x. 35 has just multiple GPUs support but user-land stuff still suck in this area, so why bother?
It's this one, but in my first build I forgot to compile Aufs as a module, maybe it's this one - I just don't remember if I uploaded the fixed sources. If you want to roll your own just compile this kernel (the sources are patched, cleaned and configured), just make sure Aufs is a module. I think I uploaded the new sources, but don't trust me
And no, haven't tried OO on any kernel, the last time I used it was maybe a year ago.
EDIT: dang, it seems I uploaded the fixed sources but had a typo in the file name, so now I don't know which one is the right sources SFS. You can take the sources from the sources directory, patch with the stuff in the patches directory and copy in the .config file.
_________________ Shahor, my Puppy concept
|
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2353 Location: Texas, USA
|
Posted: Tue 23 Nov 2010, 12:03 Post subject:
Subject description: CPU tool does not retain settings |
|
Tried on luci-238, frugal and full installations.
I activated the CPU Frequency Scaling Tool with these settings, powersave, Min-1600000, Max-1867000. Applied the settings, then later recheck and find that it has gone back to the default start condition running at max speed of 2673000. This was repeated several times on both installations.
| Description |
|
| Filesize |
40.88 KB |
| Viewed |
1568 Time(s) |

|
|
|
Back to top
|
|
 |
Iguleder

Joined: 11 Aug 2009 Posts: 1611 Location: Israel, somewhere in the beautiful desert
|
Posted: Wed 24 Nov 2010, 02:05 Post subject:
|
|
tazoc, do you need any help with this? Testing maybe? I just compiled a new kernel and I want to try it out on various machines so maybe I can contribute more to this
Oh, and by the way ... do you intend to upload this to the Lucid repo?
(And regarding the kernel, it's my new linux_kernel-2.6.32.26-pentium2-bfs for the upcoming Insidious Puppy)
_________________ Shahor, my Puppy concept
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Wed 24 Nov 2010, 19:55 Post subject:
Subject description: CPU tool does not retain settings |
|
| Jim1911 wrote: | | Tried on luci-238, frugal and full installations. | Thanks for the bug report Jim. I haven't tried Luci-238 yet. I wonder if it has a new kernel. Your screen shot shows that wcpufreq removed the previous driver, something I added into wcpufreq 0.4 but never thought would work. So we're breaking new ground here.
I will d/l 238 and do some testing tomorrow.
Hi Iguleder, wcpufreq is already in Luci-237/8, I haven't uploaded anything myself to the lucid repo--maybe you're joshin me?
Feel free to test and hack as needed. If my hunch is right, something new about Luci-238 or Jim's hardware is allowing the driver to be removed when wcpufreq starts, which is good because that allows changing the driver without having to reboot. What I need to figure out is whether the driver got removed earlier than it should have. May need a new panel that detects the possibility of removal without rebooting and offers to remove before it actually does.
Thanks,
TazOC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
taca0
Joined: 06 May 2009 Posts: 119
|
Posted: Thu 07 Apr 2011, 23:32 Post subject:
|
|
Problems :
I have Via C3 and I select longhaul mod and its accepted I finish the selection but when I boot the computer again the cpufreq scaling not activate again.
What its the problem??
Thanks!
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Fri 08 Apr 2011, 00:04 Post subject:
|
|
Hi taca0,
The script at /root/Startup/cpu-frequency-scaling.sh should activate scaling when X starts. If not, please let us know which Puppy/puplet and version you have. I don't have a Via C3 to test with but I can at least see if wcpufreq works with the Pup you are using.
Opening the above script with a text editor should look similar to this, but specific to your hardware: | Code: | #!/bin/busybox ash
## To activate at bootup copy rest of code ##
## below this comment to /etc/rc.d/rc.local ##
modprobe powernow-k8
modprobe cpufreq-ondemand
cd /sys/devices/system/cpu
for i in `ls -d1 cpu[0-9]*`; do
echo ondemand > $i/cpufreq/scaling_governor
echo 1350000 > $i/cpufreq/scaling_min_freq
echo 2700000 > $i/cpufreq/scaling_max_freq
done | Copy and paste the lines after the ## comments (from your cpu-frequency-scaling.sh) into a terminal and if there appear to be errors, please post the o/p.
Thanks,
TazOC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
taca0
Joined: 06 May 2009 Posts: 119
|
Posted: Sun 10 Apr 2011, 01:17 Post subject:
|
|
tazoc:
I have test in wary 511 and lupu525 and both write on the root/Startup/cpu-frequency-scaling.sh this >
#!/bin/busybox ash
echo 50 > cpufreq/ondemand/up_threshold
So its activate in the first time but when reboot , nothing...
Maybe I should do it manual like you shows.
I just inform , maybe its a problem with my hardware or the kernel (I use the 3.6.33.git7 from Barry)
Thanks!
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Sun 10 Apr 2011, 22:11 Post subject:
Bug confirmed, will work on it |
|
taca0,
Thanks for the info. My last post was missing the line you have;
| Code: | | echo 50 > cpufreq/ondemand/up_threshold | but you'll need the modprobes for your hardware as well. I'm not familiar with the kernel you are using, but you might try | Code: | modprobe acpi-cpufreq
modprobe cpufreq-ondemand
cd /sys/devices/system/cpu
for i in `ls -d1 cpu[0-9]*`; do
echo ondemand > $i/cpufreq/scaling_governor
done
echo 50 > cpufreq/ondemand/up_threshold | I've been testing wcpufreq in Fatdog64 and have a similar problem where it works the first time, but later running wcpufreq reports scaling driver 'mperf' instead of my selection, powernow-k8. So for now I'm manually editing /root/cpu-frequency-scaling.sh.
I will work on wcpufreq soon and post an update if I can squash these bugs.
-TazOC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Fri 06 May 2011, 17:11 Post subject:
Wcpufreq-0.6 released Subject description: Current scaling module detection improved |
|
wcpufreq-0.6 110424
Bugfix: Jim1911 and taca0 reported that prior scaling module was removed after reboot or second run of wcpufreq. Removed mperf module from driver selection dialog and improved detection of current driver by scanning /proc/modules.
-TazOC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Sun 08 May 2011, 20:46 Post subject:
wcpufreq-0.7 released |
|
wcpufreq-0.7 updates
Activate at boot up from /etc/init.d/wcpufreq instead of script in ~/Startup.
Removed /home/spot and /etc/skel directories from wcpufreq.
Updated for fido user compatibility in Wary 5.1.1.53
Woof/Wary: earlier versions of wcpufreq sometimes failed to activate on reboot--fixed.
-TazOC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
technosaurus

Joined: 18 May 2008 Posts: 3843
|
Posted: Thu 12 May 2011, 14:36 Post subject:
|
|
Edit, oops too many alt tabs
meant to post these really light tray apps that use xcb
http://sourceforge.net/projects/wmc2d/
http://sourceforge.net/projects/wmcpumon/
some pups may need to upgrade xcb and/or xcb-utils for it to compile though ... maybe for the next pup series though
(he also has an xcb rewrite of jwm that looks extremely promising)
_________________ Puppy Web Desktop Now with pet packages - Pet Packaging 100 & 101
|
|
Back to top
|
|
 |
playdayz

Joined: 25 Apr 2008 Posts: 3704
|
Posted: Sun 17 Jul 2011, 12:26 Post subject:
|
|
tazoc, Any reason I should not use version 0.7 in Lucid 5.2.6? Thanks.
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Mon 18 Jul 2011, 13:25 Post subject:
|
|
HI playdayz,
Not that I know of. Have not received any bug reports on v. 0.7 so it should be fine.
-TazOC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1109 Location: Lower Columbia Basin WA US
|
Posted: Tue 13 Sep 2011, 23:49 Post subject:
wcpufreq-0.8 updated for Fatdog 64-520 |
|
wcpufreq-0.8
Updated for Fatdog 64-520 support; account for scaling drivers built-in to kernel instead of compiled modules.
-TaZoC
_________________ lhpup.org Lighthouse 64 6.01
|
|
Back to top
|
|
 |
|