Thank you very much for those pointers.
For me, the CPU scaling works, backlight changing works, it's only the fan..
With some kernels, the "fan" code I pasted above works well, and it can set the fan speed.
With the current kernel ( 18.104.22.168-105.2.23.fc11.x86_64 ) , the fan command gives a segmentation fault, and the /var/log/messages shows
May 20 18:46:38 tklaptop kernel: fan general protection ip:4005f4 sp:7fff83ad6888 error:0 in fan[400000+1000]
The default, if I do not muck with the "setfan.sh" and "fan.c" , is that the fan stays at full speed, loud and wastes battery.
I just wish my setfan.sh worked all the time
---------- Post added at 10:10 AM CDT ---------- Previous post was at 10:04 AM CDT ----------
ACPI dumping gave some errors, and the mentioned file does not exist, that I suppose to give to iasl:
[root@tklaptop ~]# acpidump --output /home/turgut/Desktop/acpi_dump
Wrong checksum for ATKG
Wrong checksum for ATKG!
[root@tklaptop ~]# acpixtract -a /home/turgut/Desktop/acpi_dump
Acpi table [DSDT] - 46656 bytes written to DSDT.dat
Acpi table [FACS] - 64 bytes written to FACS.dat
Acpi table [FACP] - 244 bytes written to FACP1.dat
Acpi table [APIC] - 92 bytes written to APIC.dat
Acpi table [MCFG] - 60 bytes written to MCFG.dat
Acpi table [SLIC] - 374 bytes written to SLIC.dat
Acpi table [ECDT] - 84 bytes written to ECDT.dat
Acpi table [DBGP] - 52 bytes written to DBGP.dat
Acpi table [BOOT] - 40 bytes written to BOOT.dat
Acpi table [OEMB] - 113 bytes written to OEMB.dat
Acpi table [HPET] - 56 bytes written to HPET.dat
Acpi table [DMAR] - 264 bytes written to DMAR.dat
Acpi table [ATKG] - 32804 bytes written to ATKG.dat
Acpi table [SSDT] - 1264 bytes written to SSDT.dat
Acpi table [XSDT] - 132 bytes written to XSDT.dat
Acpi table [FACP] - 132 bytes written to FACP2.dat
Acpi table [RSDT] - 84 bytes written to RSDT.dat
Acpi table [RSDP] - 36 bytes written to RSDP.dat
---------- Post added at 10:16 AM CDT ---------- Previous post was at 10:10 AM CDT ----------
Update: In fact, it's erratic. the fan.c may work at boot time and then fail later on.
Or it may work great after a reboot. Currently it is working.. very odd.. -t