0 Members and 4 Guests are viewing this topic.
You may be getting distracted by cpufrequtils.From what I've read here, it seems the problem relates to dependencies associated with linux-tools-common.cpufrequtils doesn't have any link (as far as I can see) to linux-tools-commonI don't think that cpufrequtils got installed - the uninstall command couldn't find it.QuoteIl pacchetto "cpufrequtils" non č installato e quindi non č stato rimossoTrying to install cpufrequtils may have been the first time you noted apt reporting a problem.The inference I make is that something installed *before* cpufrequtils has caused the dependency issue.If you search the command line history before cpufrequtils, you may find something.Or if you were using the GUI, we may need to look into other logs.Unless we find the root cause, we can't try to fix it.It may be more efficient to re-install.
Il pacchetto "cpufrequtils" non č installato e quindi non č stato rimosso
I was trying to boost my clock speed because my cpu, was running at 1.6ghz, only made things worst
Hi!First question you need to answer:What is the goal you are aiming at with cpufrequtils?In other words: What do you expect to get from it? What real problem you want to solve using this program?Defining very clearly what you want to get, increases the available choices to do it.There are lots of programs that do basically the same thing (serve the same purpose).Choosing the best, bolis down to what do you know to do with it.Making it simple: It is unlikely that you will be able to comb your hair, using your shoes. You need a comb to do that.As a final touch:Knowing what to do with whatever piece of software, means: - How do I install it?- How do I uninstall it?- How can I use it?- What kind of trouble can I get into using it?- How do I fix the system in case it breaks down?Still! Nobody knows everything about everything.It applies to me, to you, to anybody on this Forum, including Jerry.Yet, each one might have an idea.In order to gather info, you need a starting point.This is usually the answer to the initial question:What is the goal I am aiming at with ... [package name, or program]In this case, cpufrequtils.Here is what it does:https://packages.debian.org/sid/cpufrequtilsSo, this is why I asked you in the previous message if you know enough to tinker with the Linux Kernel.If you belive that overclocking your CPU will solve anything, you are on a very dangerous path.It usually leads to frying either the CPU, the RAM or the mainboard. Sometimes, all three.Unless you are an expert in hardware testing beyond the factory specifications boundaries. Are you?Best regards, Șerban!
Quote from: gaas on April 07, 2024, 04:02:25 PM[...]Can you explain in simpler terms please? I'm pretty new to Linux.OK. I got it. I'll see what I can do. Now, I'm pretty tired and it's late here.I need to (re)think it differently, and it takes some time.Best regards!
[...]Can you explain in simpler terms please? I'm pretty new to Linux.
Hi!I've been watching the development of this thread. (Sorry for using English, my primary language is Romānă and my Italian is way below requirements...)Now, there are some facts I'm familiar with:1. The cpufrequtils utility.This is easy to replace, since it does little to help you. It's main goal is to show the CPU load. Forget about overclocking. It's about a lot of things that usually go sideways, and you might even get your CPU/Video fried out if you overclock. You can do CPU monitoring using other programs. I recommend you use the "System Monitor" app (Menu> System> System Monitor.) The App has been tweaked by Jerry and it works fine on lots of machines, has a nice GUI and offers enough information regarding the CPU load, Video, Memory, etc.Alternately, you can install "htop". It's a tiny CLI utility that gives you a bunch of information regarding the system.You can use the following to install it:Code: [Select]sudo apt install htopPost - installation, you can then type in Terminal htop and it displays you a semi-graphic interface (like Midnight Commander, ncurses) with lots of dynamically updated info.You can close it by pressing the F10 key, or clicking on the F10 button on the interface.2. The libcpufreq0 library.I did this and here is what I got:Code: [Select]apt search libcpufreq0Sorting... DoneFull Text Search... Donelibcpufreq0/jammy 008-2build1 amd64 shared library to deal with the cpufreq Linux kernel featureAre you shure you have the full expertise to tinker with the Linux Kernel?I doubt I have it, after more than 12 years of using Linux on a daily basis and more than 29 years of computer practice.But... Wo am I to say what is wrong or what is right?I just say I want a peaceful life with my computer, so I stay away from things that are way above "my paygrade". And so far, I could manage to do so!3. Fixing broken packages.I usually go like that:Lite Tweaks (Menu> Search "Lite tw...", click on the menu item "Lite Tweaks").In the Lite Tweaks window, select the checkbox beside the item "Package System Repair". I had some trouble over the years so I used it a few times and it did a great job, spearing me of a full install job. I've done installations maybe thousands of times, but still... it takes at least 100 minutes from start to end. So, why would I go on this path, instead of a two minutes or less job?I discovered that after issuing the "fix-broken" option, you need to issue the: Code: [Select]sudo apt updateIt seems that sometimes, after cleaning the system with that, some residual files still point to the old packages configuration and I presume that this leads to some new error messages during "apt upgrade".Anyway, applying this workaround, never got me into trouble again.I hope that will help you get things done!Best regards, Șerban.
sudo apt install htop
apt search libcpufreq0Sorting... DoneFull Text Search... Donelibcpufreq0/jammy 008-2build1 amd64 shared library to deal with the cpufreq Linux kernel feature
sudo apt update
If running the install for cpufrequtils was the first installation that gave you the error, then it is likely that something you did before actually caused the problem.So cpufrequtils may not be the problem - I think it only installs one other package called libcpufreq0.If you don't want it and can't find other instructions to remove it, this may work.Code: [Select]sudo apt remove cpufrequtils
sudo apt remove cpufrequtils
QuoteAnd how do i do that?Not sure which bit of the post you are asking about.Quoteo specificare una soluzioneIs a reference to the fact that the command that apt suggested can't resolve the problem.That means we have to work out what is wrong and specify a solution to get apt or dpkg to correct the situation.This is proving difficult.QuoteYou could check your cli history to see what commands were run to install.This assumes you used the command line to install powerctl.If you did, open a terminal by pressing 'Ctrl' Alt' and 'T' togetherIn the window that opens enter the commandCode: [Select]historyfollowed by enter. This will list the most recent commands entered on CLI.Scrolling back through the list may show the command(s) used to install the powerctl software - provided you haven't used too many commands since installing or cleared the history.
And how do i do that?
o specificare una soluzione
You could check your cli history to see what commands were run to install.
history
It looks like the (o specificare una soluzione) is required.The powerctl install is a possible suspect but we need the timeline or more details about powerctl to be sure.You could check your cli history to see what commands were run to install.There is a danger in trying to resolve without knowing the problem will make things worse.Unless someone else has insight then re-installing may be the best choice and the quickest way of getting to a stable systemConsider using 'System Restore Utility' and 'Backups' when building a new system to save time if things go wrong.