COMPILING ACERHDF WITH KUKI KERNEL
If you have a look at my previous post regarding acerhdf I've been having a bit of a mare trying to get fan control implemented on my AAO with SSD and BIOS v.3309
The method described on the Wiki (using acerfand) would cause my AAO to poweroff randomly + I couldn't compile the latest acerhdf kernel modules with the kuki kernel referenced on the wiki (see quotes below for the reason). I also tried the latest sickboy kernels which have the acerhdf module built in - for some reason they didn't work with crunchbang on my AAO. I finally figured how to compile acerhdf myself which was nice - and I'm rather chuffed I figured it out as I'm new to the linux world. So just thought I'd share:
fmcc wrote: Hmm. There is a symbolic link /lib/modules/2.6.28sickboy-kuki/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/2.6.28sickboy-kuki/build
Hmm. The package shipped with a symbolic link /lib/modules/2.6.28sickboy-kuki/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.28sickboy-kuki/source
As you can see from the quotes above there are some missing symbolic links. To rectify this I did:
cd /lib/modules/2.6.28sickboy-kuki/
I took a look at the equivalent directory in the generic kernel and realised the link should point to:
/usr/src/linux-headers-2.6.28sickboy-kuki/
so I created the symbolic link myself:
ln -sf /usr/src/linux-headers-2.6.28sickboy-kuki build
I then took a look at the Makefile in the extracted acerhdf_kmod directory.
- first the INST variable has a "/" at the end which needs to be removed otherwise you end up with a "//" in the copy path i.e. it should be ' INST := $(DESTDIR)/lib/modules/$(shell uname -r) '
- second, that install directory mentioned in the line ' cp acerhdf.ko $(INST)/kernel/drivers/misc/' doesn't exist. So...
cd /lib/modules/2.6.28sickboy-kuki/kernel/drivers
then
sudo mkdir /lib/modules/2.6.28sickboy-kuki/kernel/drivers/misc
now when you follow the README.txt instructions for installation everything should work (it did for me!!)
Hope that is of use to someone!
P.S. I couldn't find the equivalent symbolic link for the "source" directory so didn't worry about creating it - it doesn't affect the above process