Errors installing Thinkpad drivers for tpctl on Minislack

saxophobe · 03-19-2005, 07:13 AM

Hi all!

As the title specifies, I am getting the following error when trying to install the Thinkpad drivers for tpctl.

Quote:

The directions in the README specify the following:

On distributions that don't set things up for you automatically,
you can install from the source tarball. First make sure that your
kernel source tree is at /lib/modules/`uname -r`/build and make
sure that the file include/linux/modversions.h is in that tree.
(It is generated by the "make dep" command in the kernel build
procedure.) Then do:
tar zxvf thinkpad_<ver.num>.src.tar.gz
cd thinkpad-<ver.num>

If you are running Linux 2.6, do:
ln -s 2.6/drivers drivers
ln -s 2.6/include include
make all

And I believe this is the problem, when I look for the modversions.h file, I find it in /usr/include/linux directory.

Does anyone know how I can specify where this file can be found when executing the make all command? When I unpack the tarball and go to the new dir to run the command, I get the following error:

Code:

make -C 2.6/drivers
make[1]: Entering directory `/usr/src/linux/thinkpad-5.8/2.6/drivers'
make -C /lib/modules/2.6.101/build SUBDIRS=/usr/src/linux/thinkpad-5.8/2.6/drivers modules
make: Entering an unknown directorymake: Leaving an unknown directorymake[1]: Leaving directory `/usr/src/linux/thinkpad-5.8/2.6/drivers'

If anyone has any ideas, please let me know.

Thanks for your time!

sax

short101 · 03-20-2005, 09:00 PM

Which buttons are you trying to get to work. The ibm-acpi module sorts out a lot, and you can use xmodmap for others. I did play with tpctl once, and somehow managed to screw my x-server, so gave up on it.

saxophobe · 03-22-2005, 07:02 PM

Mainly, I was trying to get my alsa settings to stick after I shutdown my laptop. Please tell me where I can find this IBM module you are referring to!

Thanks for the reply!

sax

short101 · 03-22-2005, 09:22 PM

Its on option in 2.6.8? plus kernels or apt-get install ibm-acpi (source) or get the latest from sourceforge. Whats wrong with your alsa, I dont think ibm-acpi will help that.

saxophobe · 03-25-2005, 10:17 AM

Sorry for not getting back sooner...

The problem with Alsa is that my settings aren't sticking; every time I shut down the system, the next time I turn it back on I have to go thru the process of re-initializing, rebooting, re-running alsaconf to get my sound to work at all. And even then, sound doesn't work with Firefox, just XMMS. Anyway, it's really annoying, and a problem every TP 600e user has to go thru if they want sound to work while using Linux.

My latest theory is that maybe the battery on the motherboard is dead, or it may have to do with the fact that the laptop battery is dead and needs replacing, but I'm not sure.

Anyway, if you have any ideas, please let me know.

Thanks for the replies!

sax

interndan · 03-25-2005, 11:47 AM

run alsaconfig select your card, then run alsamixer to set levels, then run alsactl store.

saxophobe · 03-25-2005, 06:51 PM

interndan,

I HAVE to run alsaconf everytime I boot my system. The problem is that the alsa settings are not sticking; I have to go thru the following process EVERY time I boot my system if I want ANY sound to work:

1. Boot system while pressing F1 and go into IBM's stupid excuse for BIOS
2. Select "Configure"
3. Select "Initialize" - What I am initializing is not stated. Why doesn't it do this by default is beyond me.
4. Reboot and login as root
5. Run alsaconf
6. Run alsamix, or aumix
7. Run alsactl store
8. Log out and log back on as a normal user

This is the problem I am looking for an answer to. If you have any ideas, other than the ones stated previously, please let me know.

Thanks!

sax

interndan · 03-28-2005, 01:28 PM

Hmmmmm,

I had Slack 10 running on a 760XL for awhile. Sound was never a problem. I think when you initialize the BIOS you are resetting to factory condition. Try setting your BIOS for the sound card ( I think it is ESS 1688) and saving BIOS settings. Then retry alsaconf. If that doesn't work, you may indeed need a new BIOS battery.