Trouble CPU frequency and battery on macbook

Hello everybody,I got news on this problem, perhaps this will help fixing my problem. I got the speedstep working by adding some lines to the /etc/rc.local script, as described in the debian wiki for the macbook.
But, I still don't have my battery recognized. So I installed an ubuntu feisty as dual boot on my macbook since the ubuntu documentation says that the battery of the macbook is recognized without problem and without having to compile a custom kernel.
But, after installing and updating the ubuntu (I installed from the live CD) it happens to have the same behavior as on debian --> The battery is not recognized (gnome applet says no battery is present).So, I suppose that the kernel parameters are not the cause of this; did I forgot something (a daemon, a program, a module)?
Thanks a lotRegards,Alex2007/7/29, Alexandre Neubert <alexandre.neubert@gmail.com>:
Hello List,I recently got a new Macbook and while tryning to install debian on it I have some trouble getting the cpu frequency scalling and the battery status working.I followed the tutorials on:

http://wiki.debian.org/MacBook#head-7271d26c7c6e311218ca20422f7eb86e76a6d5e3andhttp://gentoo-wiki.com/HARDWARE_Apple_MacBook
Here are the action I did exactly:
- Following these tutorials, I got a 2.6.22 kernel from kernel.org- I pachted them with the mactel sources for this kernel version
- I recompiled the kernel using the configuration file provided by the gentoo wiki and set all cpu frequency scalling options to modules (powersave, ondemand, ...) and the default governor to userspace
- Once recompiled, I installed cpufreqdOn the Gnome desktop, the battery applet tells me that there is no battery present, as if ACPI was not configured correctly and cpu frequency scalling applets tells me that my CPU's are running at 100% (although default governor is userspace).
CPU frequency scalling works with the command line:cpufreq-set -c 0 -d 1GHz, so I tried to make an init script with this, but this does not seem to work. In fact, the script seems never to be executed.To do this, I followed the tutorial on:
http://www.debian-administration.org/articles/28I thought CPU frquency and battery management were governed by the same features.
Does anybody know why I don't get my battery status to work? Did I for forgot a module in the kernel?
How come that I can't get my CPU frequency to run on minimum although userspace is set?Finally, how come that my script is not executed although the symblic links in te different runlevel were created?

Thanks for your help.Regards,Alex P.S In case it helps, here is an output of lsmod:# lsmodModule                  Size  Used byhci_usb                17500  2 rfcomm                 40408  0
l2cap                  24768  5 rfcommbluetooth              55524  7 hci_usb,rfcomm,l2capbutton                  7824  0 ac                      5124  0 battery                 9924  0 cpufreq_powersave       1728  0
cpufreq_performance     1984  0 cpufreq_ondemand        8268  1 cpufreq_conservative     7048  0 acpi_cpufreq            9240  0 sbp2                   23304  0 snd_hda_intel         261080  2

snd_pcm_oss            43488  0 snd_mixer_oss          16704  1 snd_pcm_ossappletouch             10048  0 snd_pcm                79876  2 snd_hda_intel,snd_pcm_osssnd_timer              23428  1 snd_pcm

snd                    55140  9 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timersoundcore               8160  1 sndsnd_page_alloc          9992  2 snd_hda_intel,snd_pcmohci1394               35504  0
ieee1394               95480  2 sbp2,ohci1394thermal                13320  0 processor              30652  2 acpi_cpufreq,thermalfan                     4740  0

ok, I'll try that this evening. That is to say, I already run an unstable debian, so I don't know if your procedure is still necessary (sorry, I forgot to tell that I run a debian sid in my previous mails).
On sid, you don't have to do any of the kernel recompilation.  Things should "just work". 
I already did this. This is a nice little program and I followed all suggestions (most of them forced me to recompile my kernel), but this didn't change anything.
Did Powertop show any frequency scaling going on, or was your system permanently running at its full frequency? You may want to try it with the Debian kernel again - it never asked me to recompile my kernel, and it did manage to find that frequency scaling was turned off.
Is this still to test since I run a debian sid? Can it be that the power management works well on testing and not with sid?
Btw, I tried the 2.6.22 precompiled kernel from sid too, but it did not work better.No, sid should work as well as (if not better than) testing.  I'm wondering if this is just an issue with the very newest MacBooks (I have a first-generation one, and it works fine). You shouldn't have to recompile the kernel in any case with
2.6.22.Where can I go from there?
One thing you could try is adding acpi_cpufreq and cpufreq_ondemand to /etc/modules.  That may enable frequency scaling if its disabled.  Also, make sure all the ACPI-related packages are installed by running "tasksel" and making sure "Laptop" is selected.
Tim 

Hello,
I was able to solve this trouble - not on Mac, but on HP Compaq notebook - only by compiling all the ACPI settings not as modules but as a solid parts - I mean all the "y" possinilities.
Still also depends on kernel - it seems. It works for me on 2.6.25, 2.6.25.9, but not on 2.6.18. Configuration is the same in all the kernels concerning this issue.
Milan