Quote:
|
NOW we have a clear definition of the problem. Cpufreqd sounds awfully like something that may be at the heart of a cpu frequency problem, so I would try installing Cpufreqd
Have you a heat problem? The cpu won't speed up unless it's adequately cooled. |
I never had this problem with Lenny. As noted in the OP, it all started during the Install of squeeze.
cpufreqd only shows "failed" during the boot sequence. However, cpufreq-utils loads properly (as far as I can tell) and sets the system to ondemand. Immediately following boot (and not loading X) cpufreq-info shows proper configuration. "./etc/init.d/cpufreqd resart" also will load without an error. The error it encounters during boot is unknown since I can't seem to find it in any /var/log files. I'm seriously about to beat my head against the wall. My laptop has been out of service for ~6mo because the screen died. I just spent $60 on a new backlight and invertor and installed them. I hope not for nothing. |
cpufreqd is not part of cpufreq-utils. I have slackware-13.37 here. I do suggest you read instead of freaking. There are several things with a finger on cpu frequency: The cpu being too hot; Battery low; governor saving power; and then all the clever little daemons, utilities and knacky bits. If you have kde, all this could be running in triplicate (kde always seems that slow).
|
Quote:
I've re-flashed the BIOS like 6 times. Not sure what else to try. Is it possible that the MB's hardware monitor is faulty and locking out the OS's? I like Slackware for my Desktop because it's rock-solid, stable and versatile. I put Debian on my laptops because in a mobile environment the Apt repository is priceless. With Slackware i can compile and configure anything to run on it. But in a mobile environment, ease and a speedy install win out. I installed Debian with the multi-arch disc and added KDE after. I think I'm going to use the i386-KDE disc and see how that runs. I also have a USB hard drive running Lenny I can pop in and double-check with. |
I know nothing about the cpu problem but as for grub you need t oput that menu entry you create in /etc/grub/grub.d.40_custom and run, as root;
Code:
update-grub |
Quote:
It would be nice if 'man grub' actually returned a result. |
Yes it would. It should actually be "man grub-pc" but that doesn't get you anything either. The best documentation on grub is now at;
http://ubuntuforums.org/showthread.php?t=1195275 and; https://help.ubuntu.com/community/Gr...20the%20LiveCD The perpetrator of the first is guilty of most of the second. He was one of us in Ubuntu 9.10 testing when grub-pc was dropped on us at A2 time with NO documentation worth a damn that we could find. Spent 2 weeks editing the grub.cfg file before we started to find hints here and there. Drs305 put all our discoveries, along with a vast amount of experimentation on his part, into the thread over there. He keeps it up to date very well. There are a lot of links at the bottom of that first entry that are just great. One thing that is good to run when you make a change in anything to do with grub, after you run update-grub, is "grub-mkconfig". This will, in terminal, print out the grub.cfg file so you can check it and make any corrections right then by editing the right script and then running update-grub again followed by grub-mkconfig again to check it. Custom menu entries are very handy and, I believe, what you are intended to use after the first boot to your installation. Using them you can disable all other scripts in grub.d above 05 except for your ??_custom file. This makes the load time of the grub menu a lot quicker as there is so much less grub.cfg file to read. This is the entry for the OS I am on right now. It will load any Debian based OS that is on this partition. I could install a version of Mint or Ubuntu here tomorrow and use the same entry unedited, as it just calls for the partition and boots the newest kernel there. Code:
echo "Adding Squeezy on sda7" >&2 I actually have this in the instruction string so that bootchart works on boot up, it comes after a space past "splash"; Code:
initcall_debug printk.time=y quiet init=/sbin/bootchartd ... rdinitrd=/sbin/bootchartd |
I booted up Lenny off the USB hard drive and it face a similar issue, but felt different. i.e. The CPU dropped to 600, locked 600/600MHz (min max) with the fan on, but stayed around 11% CPU. It got up to 55% doing a couple tasks, and even 100% for a couple seconds but remained snappy and responsive. On the other hand, with Squeeze, it would drop to 600 lock 600/600 and remain @100% cpu and would be practically unusable. Remember how in the OP I said the istall was running @600MHz? well I'm running the debian-6.0.1a-i386-kde-CD-1.iso install CD right now and it's zipping along at 1.8GHz and yes the fan is running, and the fan has even been changing speeds. 'lsmod |grep cpu' returns zero results but fan, thermal, and therrmal_sys are running. cpufreq is not running.
|
Solved???
Update....
The laptop was running for a while and then I shelved it because it is practically unusable at 600MHz. It inadvertently got unplugged and the batteries died. I just pulled it off the shelf and booted it up to get some files off it and it was still experiencing the same issue. I dove into it with a fresh mind and started reading the /etc/init.d files and a whole slew of others (gotta love Linux and the programmers/developers who put so many comments in their code and files.) I tracked it down to the /etc/init.d/cpufrequtils file. Namely the top where the default lines are Code:
MAX_SPEED="0" Code:
MAX_SPEED="1800000" |
Thanks for posting back your solution. Please mark the thread as solved using the thread tools at the top of the thread.
|
All times are GMT -5. The time now is 08:40 PM. |