[mythtv-users] Actisys 200L unresolved symbol errors

[David Lyons]

Gideon/Shawn/All,

	Thanks for your help, I am pretty sure that was what the problem
was.  The "EXTRAVERSION" flag did have a .atcustom string at the end, I
removed the whole string (not the custom) which did not seam to help.
Once I reinstalled the kernel source and re-compiled the ACTISYS. The
device is responding to my remote (irlearn), however I am still working
on getting it to control my cable box.

Thanks Again 

Dave

PS I also have gmail invites to give away.  Please send me an email
directly to me; and not the thread; if anyone would like one.

Dave





-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Shawn Asmussen
Sent: Thursday, September 09, 2004 10:25 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] Actisys 200L unresolved symbol errors

> All,
>
> 	I just purchased a ACTISYS 200L IR blaster, in order to control
> my digital cable box.
>
> 	I followed Roberts guide at the following location
>
>              http://members.cox.net/rwraithr/IRBlaster_Howto.txt
>
> 	Everything seamed to go all right with the make/make install
> however when I tried to load /sbin/modprobe remote_sir I get the
> following error
>
> /sbin/modprobe remote_sir
>
> /lib/modules/2.4.22-1.2197.nptl_51.rhfc1.at/misc/remote_dev.o:
> unresolved symbol __wake_up
...
<snip>
...
> /lib/modules/2.4.22-1.2197.nptl_51.rhfc1.at/misc/remote_dev.o: insmod
> /lib/modules/2.4.22-1.2197.nptl_51.rhfc1.at/misc/remote_dev.o failed
> /lib/modules/2.4.22-1.2197.nptl_51.rhfc1.at/misc/remote_dev.o: insmod
> remote_sir failed
>
>
> 	Can someone tell me how to fix the unresolved symbol errors? Or
> better yet what I did wrong (if anything)
>
> Thanks
>
> Dave
>
>

I'm not 100% sure, but I'd say that it is likely that your kernel source
directory was not properly configured for the kernel that you are
running.
Try this from the /lib/modules/<YOUR KERNEL HERE>/ directory:


# nm misc/remote_dev.o | grep __wake_up
         U __wake_up_Rsmp_127fda83
# nm kernel/drivers/scsi/scsi_mod.o | grep __wake_up
         U __wake_up_Rsmp_127fda83


I don't completely understand the scheme, but most of the symbols in the
kernel are named so that the way the kernel was configured are
represented
in the symbol names. For example, from the smp in the symbol names
above,
you can tell that I'm running an smp kernel. Since the two symbol names
match exactly, you can tell that they were probably built from the same
(Or at least a similar) kernel configuration. If you try those two
commands, and they don't show the same symbol names on your system, then
I
would imagine that is what your problem is. Make sure that the kernel
source package you have installed matches the kernel that you are using,
and make sure that the source directory has been properly setup with the
proper .config file (Which should be available from the configs
directory
underneath the top level of the kernel source directory.), and the 'make
dep' is done.


P.S. I just picked scsi_mod.o at random to do the comparison on. The
__wake_up symbol appears in many of the standard kernel modules. You
could
also compare any of the other symbols to another module that has that
particular symbol. I just picked the first one from the list.
_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users