2.6 recompile, need to adjust things in ACPI
 

OK..Let me get you up to date:

Hardware:
Gateway Solo 1450LS 1.3G Intel Celeron Laptop
256MB RAM
i830m graphics
20GB HDD
i830 chipset
wireless D-Link DWL-650P1 PCMCIA

OS:
Slackware 10.2 Kernel 2.6.13

Problem:
Originally installed Slackware 10.2 w/the default 2.4 kernel. Loved it. Then I decided to go to the 2.6 kernel (mostly for the wireless)
Compiled the kernel, (MANY times, lol) ,and finally got it so I like it.
An unfortunate event happened (My 11 yo son figured out my root password) ,and POOF! All gone.
So reinstalled using the test26s kernel, recompiled that to about where I like it. (Sound, everything almost works)
The problem I'm having, tho, is that this is a laptop that I do carry around with me., and I can't adjust the CPU throttling.
And when I go to klaptop, all my options are greyed out, except battery control.
Any idea what I missed in the recompile? I seem to recall something about button software.
I did enable almost everything else to do with ACPI.
Tried to install gtk-cpuspeed (what a joke, can't even get it to run at all) and a few others say that I'm missing the throttling ability.
I know I could throttle w/2.4
Anybody have any ideas? A recompile won't bother me at all (Learned my lesson, and have entire 2.6 source/old compile/makes/everthing on a separate HDD)
Love this 2.6, BTW...Faster, better support for my hardware, fun to play with(even messing it up...Didn't someone once say::)

did you compile those options into the kernel or as modules?
the default test26 kernel has the acpi functions as modules so you would have to
modprobe battery
modprobe ac
etc

look in:
/usr/src/linux/drivers/acpi
for the rest of the modules you may want to load

Figured it out...Didn't enable /proc/acpi/sleep.... feel like an idiot...Well, recompiling attempt 'e'...lol

Got it now. Only problem was that in the middle of the recompile, I lost total power...On a laptop, that's kinda hard to do.
Luckily, I had another identical laptop that the power reg on the motherboard was fried. Dissassembled both, unsoldered the power connectors and swapped them. While I was in there, I cleaned out the laptop (Amazing how much crap gets caught in those cooling fins!).
Put it back together, turned it on....and NO VIDEO
Swapped LCD's,no good (Also found out that the spare had a cracked screen...oh,well, could've made some money from it.).
As I hit the desk hard in fustration, I noticed two memory sticks that bounced.
Dang. Yep. Shared memory. Put it in, fired it up, and HDD was not gonna boot linux.
So, after making sure the battery was charged, reloaded Slackware 10.2, used my vast recall of what worked and what didn't, and recompiled.
I still called it 'e' because that one didn't finish. But it works like a charm.

Hi,

I would suggest that you get in the habit of writing an active system (related to said laptop). That way you can trail yourself on what has been done. Therefor allowing you to go back as many step as you desire.

I keep active logs for all my equipment. I have logs for my network, both wired and wireless. Each of my many systems have a spiral notebook log. I used to use binders but that got rather cumbersome. The spiral seem to take daily usage without to much of a problem.

HTH!

Actually, i do kinda do that....mostly notes
But i also copied entire /usr/src/linux directory to cd and to two of my networked PC's...That way, if kablooey again, just copy them back, make modules_install, copy bzImage/config/system.map, link them, run lilo, and bob's your uncle.