1 |
Well, it is a good linux lesson, I'll may try, just for the sake of improved boot speed. Does it goes well with the binary nvidia driver? |
2 |
|
3 |
However, I solved my problem by adding the line powernow-k8 to /etc/modules.autoload.d/kernel-2.6 |
4 |
|
5 |
I wonder why the module stopped loading automatically. |
6 |
|
7 |
Nadav. |
8 |
|
9 |
-----Original Message----- |
10 |
From: news on behalf of Duncan |
11 |
Sent: Thu 17-Dec-09 01:35 |
12 |
To: gentoo-amd64@l.g.o |
13 |
Subject: [gentoo-amd64] Re: cpu frequncy scaling module fail to load |
14 |
|
15 |
Nadav Horesh posted on Wed, 16 Dec 2009 20:34:22 +0200 as excerpted: |
16 |
|
17 |
> I recently upgraded from 2.6.23 to 2.6.31-r6 following the udev upgrade |
18 |
> (the latest version - 146-r1 needs kernel version >= 2.6.25). Since the |
19 |
> upgrade the frequency scaling modules fails to load at startup, but I |
20 |
> can load it manually later |
21 |
|
22 |
I don't have that hardware, but have you tried compiling the required |
23 |
drivers /into/ the kernel instead of as modules? |
24 |
|
25 |
FWIW, while I realize this won't fit everyone's situation, I recently |
26 |
decided it was less hassle here to simply compile everything into the |
27 |
kernel, and turn off module loading entirely. What triggered that |
28 |
decision here, was that I have separate /boot and / partitions, with a |
29 |
separate backup / partition as well. As I updated my kernel, the new |
30 |
kernels would show up in /boot and the new modules in the usual place on |
31 |
my working / at /lib/modules/<kern_ver>/, but they'd not get added to the |
32 |
backup / partition, which after all remains unmounted most of the time. |
33 |
|
34 |
When I need to boot from the backup for whatever reason, a simple change |
35 |
to grub's kernel line, adding or changing the root= to point to the |
36 |
backup instead of the usual working /, boots the backup. The problem is |
37 |
that then, I had to remember which kernels I had bothered to copy the |
38 |
modules dirs over to the backup, and which I hadn't. |
39 |
|
40 |
Since I already had the main system all builtin, thus avoiding the hassle |
41 |
of an initramfs/initrd, and it was only "extra" modules like loopback and |
42 |
floppy that were actually built as modules, for some time, I just ignored |
43 |
the problem (while making sure I copied at least the modules from the |
44 |
first release kernel in a series over, the 2.6.x kernel modules), since I |
45 |
wasn't normally after extras when booting to backup anyway. But I got |
46 |
tired of doing even the one set manually, and rather than create a script |
47 |
to automate the process, I decided it was simpler to just build the few |
48 |
remaining modules in. Yes, it takes a few more KB of "locked" kernel |
49 |
memory that can't swap, but the floppy module, for instance, was being |
50 |
loaded automatically anyway, and I never unloaded it, and with multiple |
51 |
gigs of RAM, I decided the few KB extra wasn't going to kill me, |
52 |
especially since that meant everything I needed was now in just ONE file, |
53 |
the kernel itself! |
54 |
|
55 |
Now, some people load the modules so they can feed in special module |
56 |
parameters when the do so. However, for at least some kernel modules, |
57 |
it's possible to feed those in on grub's kernel command line as well -- |
58 |
or, if they don't change, from 2.6.30 or 2.6.31 (IDR which), it's now |
59 |
possible to build-in a portion of the kernel command line at compile |
60 |
time, as well, thus significantly shortening the grub commandline to only |
61 |
the kernel filename and any dynamic parameters, such as the root= |
62 |
parameter I use to point to my backup when mounting it (and even those |
63 |
can have defaults built-in, so you only need to add it to the kernel |
64 |
command line if you're changing from the default for some reason). |
65 |
|
66 |
For instance, the radeon module has the modeset= option (in kernels with |
67 |
radeon kms enabled, 2.6.31 for radeons r500 and earlier, 2.6.32 thru the |
68 |
r700 series). When it's builtin, you can feed that option to the kernel |
69 |
as radeon.modeset= , either from grub, or built-in. (Of course, since |
70 |
that's a binary 0/1 option with a definite default and a kernel option to |
71 |
change that default already, there'd be little reason to build that |
72 |
particular one into the kernel at compile time, but it's possible. More |
73 |
practical would be to always have it in grub.conf, and just edit the |
74 |
kernel command line from grub at boot and change the single digit, from a |
75 |
0 to a 1 or 1 to 0, as appropriate.) |
76 |
|
77 |
Just something I'm throwing out there in case someone finds it useful. |
78 |
YMMV, etc... |
79 |
|
80 |
-- |
81 |
Duncan - List replies preferred. No HTML msgs. |
82 |
"Every nonfree program has a lord, a master -- |
83 |
and if you use the program, he is your master." Richard Stallman |