Re: [tlug] Problem with tpctl on Thinkpad 600X

["Stephen J. Turnbull" <stephen@example.com>]

>>>>> "jb" == Jonathan Byrne <jq@example.com> writes:

    jb> tpctl: System error message is: no such device
    jb> tpctl: Can't open device file /dev/thinkpad/thinkpad with flags O_RDONLY.

    jb> The device exists, but I can't seem to get any modules loaded
    jb> for it, and that seems to be the real problem.

Well, given that we're talking Debian, it's quite possible that the
package maintainer has his own system set up correctly but gave the
wrong device node numbers to MAKEDEV.  I don't think that should
prevent the low-level device driver from loading though.  Is the
driver built into the kernel, or a module?

    jb> installed a modules package but it didn't help.  If I try to
    jb> manually insert one of those modules (which were placed in
    jb> /lib/modules/thinkpad) it complains about unresolved symbols
    jb> and does not load.

Either your kernel doesn't have the driver or it's built with the
wrong flavor of symbol versioning.  Can you get source for the modules
and build them with the kernel?  N.B.  Debian has a system by which
kernel-pkg will build external "modules" (eg PCMCIA control stuff)
automatically (of course, device drivers have to be built in-tree most
of the time).  Requires a bit of investment to learn to set it up
(mainly figuring out where to put your external source trees so kpkg
will find them) but after that it's easy.  (I haven't used it in a
couple years so I'm not necessarily going to be much help :-( but I
hope the pointer is useful.)


-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.