I had to recompile my kernel for Manrake 10.1 to get the power management features to work on my laptop. Problem is that it won't boot with the new kernel. The first error that I see is:

Loading jbd.ko module
jbd: version magic '2.6.8.1-12mdk 686 gcc-3.4' should be '2.6.8.1-12mdkcustom preempt K7 gcc-3.4'
insmod: error inserting '/lib/jbd.ko': errno=8
Loading ext3.ko module
ext3: version magic '2.6.8.1-12mdk 686 gcc-3.4' should be '2.6.8.1-12mdkcustom preempt K7 gcc-3.4'
insmod: error inserting '/lib/ext3.ko': errno=8
Mountin /proc filesystem
Mouting sysfs
Creating device files

etc...

It ends by being unable to get to the initrd presumably because the ext3 module failed to load and that is the root filesystem.

This has me annoyed as hell because this is the same error that I had the first time I recompiled the kernel. After some advice, I went back and recompiled the kernel this time making ABSOLUTELY sure that the ext3 file system was compiled into the kernel and NOT compiled as a module. Unless there is some hidden option somewhere, I made sure that everything having to do with ext3 was checked in xconfig instead of dotted. No difference. So this is currently where I am. Does anyone have an idea of something to try next? I'm pretty clueless at this point other than maybe just trying other distros and crossing my finger hoping that they have both the BadRam patch and ACPI built in.

Thanks

Could you list the commands you used to build and install the kernel?

If you're using the initrd from the old kernel that'll cause problems, try recreating the initrd image.

Hi,

Thanks for your replies, I was watching shark tale so sorry I didn't get back more quickly.

Basically I followed the digital hermit kernel compile walkthrough. After downloading and extracting the source for my kernel, the commands I ended up using were:

make mrproper
make xconfig
make clean
make bzImage
make modules
su
password:
make modules_install
make /boot/initrd-2.6.8.1-12mdk.img 2.6.8.1-12mdk
cp arch/i386/boot/bzImage /boot/bzImage-2.6.8.1-12mdk
cp System.map /boot/System.map-2.6.8.1-12mdk
ln -s /boot/System.map-2.6.8.1-12mdk /boot/System.map

It would be really great if I just got one of these lines wrong and could go back and fix them easily. The walk through that I followed is located at:

http://www.digitalhermit.com/linux/K...ild-HOWTO.html

and the only things that I changed in the configuration from the defaults were the processor to K7/Athlon (my laptop has a 1 GHz Duron in it), the ext3 filesystem I changed to being compiled in the kernel instead of a module, and I turned on several of the power management features. Changing to the AMD processor allowed me to use PowerNow and there were laptop oriented options I turned on. That's it.

The 'make /boot/initrd-2.6.8.1-12mdk.img 2.6.8.1-12mdk' line should read:and you should edit grub.conf (or grub.lst, or whatever) to load that image, and the new kernel.

Dave

Oops, sorry.
Yeah, the make at the beginning of that line actually was mkinitrd when I put it in. Else, it probably would have had an error or something. I'm going to try it again with the line you suggested. I'll let you know if it works. Thanks for the idea.

Thanks, that made it boot up. Unfortunately, recompiling the kernel still doesn't have ACPI working, but I figured out how to change my CPU frequency manually and APM management seems to be working fairly well.

Thank you, you have no idea how long I've been working on this off and on. (It's been something in the range of months now).

I guess you already know this, but you can control the CPU frequency with either ACPI (when available) or with the "cpufreq" modules in 2.6 kernels. If you already can manually modify the clockrate, then you should try out "powernowd", "cpudynd" or "cpufreqd". At least cpudynd works with ACPI throttling, and all work with the cpufreq modules.

Yup, I've pretty much been using the userspace options to control my cpu frequency. It starts out at maximum frequency during bootup, I then modified rc.local to lower that down to minimum speed for normal operation at the end of the boot up phase (it's not like you really need a very fast CPU normally), and then I added scripts called freq1, freq2, etc. to change the cpu as I need it. It seems to work very well for me.