Page: Previous  1, 2, 3

Status: Interested
Joined: 20 Aug 2011
Posts: 21
Reply Quote
I set it there just for completeness, that is all. :)
Plus, I guess I didn't want to depend on a 3rd-party script to do it for me.
Back to top
Status: Interested
Joined: 23 Jan 2012
Posts: 43
Reply Quote
I switched over to my Debian sid setup, and I found the answer to why cpufreq-related modules were not loading in Ubuntu.

From /etc/init.d/loadcpufreq:
:: Code ::
# Provides:          loadcpufreq
# Required-Start:    $remote_fs $syslog
# Required-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:
# Short-Description: Load kernel modules needed to enable cpufreq scaling
# Description:       Make it possible to save power by reducing
#                    the CPU speed when there is little to do.
# License: GNU General Public License.
# Based on scripts found in the powernowd package version
# 0.97-1ubuntu6 on Ubuntu.
# This script is an interim solution until the default Debian packages
# will load the proper kernel modules at boot time.  Track #396117,
# #342014 and #367307 to see status on this.
# <URL:>
# claim the later kernels support autoloading of these modules, so I
# guess In the future this script can be dropped. [pere 2007-05-12]

Now that recent Liquorix kernel releases statically link cpufreq-related modules for various procies, it makes the above script redundant and even perhaps useless in Debian.

Given that there is a design difference between how Ubuntu handles cpufreq support, and Debian's implementation, and taking into consideration that the target audience of Liquorix kernels are Debian-based distros (even though Ubuntu historically is Debian-based, it has since taken its own path and rendered its repos incompatible with other Debian-based distros), would Liquorix continue to favor and abide by Debian's implementation, or be made compatible with Ubuntu-based distros?
Back to top
Display posts from previous:   
Page: Previous  1, 2, 3
All times are GMT - 8 Hours