On Tue, Nov 21, 2000 at 01:40:30PM +0000, Robert Collier wrote:
>
> I'm still seeing the same lack of response with "irattach irda0 -s"
> for my nsc-ircc FIR driver, and oopsen with modprobe of irlan & irnet.
>
> I have upgraded to the latest modutils (I was one minor revision
> behind), and rebuilt irda-utils-0.9.10 (as found in ebian-unstable)
> against the headers in kernel test11.
>
> - Regards, Robert.
A pretty common cause of troubles for IrDA is a botched module
configuration. I had an example with a user here this morning. I
cleaned up the module mess and everything started to work by magic...
So, I strongly suspect a module problem, which would be
consistent with he error...
Common module problems :
o Compiling the IrDA stack static (i.e. non module)
o Mixing static and module bits in the IrDA stack
o Mixing modules belonging to different versions of the IrDA stack
o Mixing modules belonging to different kernel versions
o Trying to load IrDA modular stack on a kernel with static IrDA stack
o Loading module twice
o Multiple FIR modules loaded
o Multiple instances of irattach (staying in background)
o Wrong version of modules tools
o Failed to do depmod -a (usually automatic at reboot)
Of course, let's not forget the classics :
o irmanager running
o Unclean IrDA source (botched patch)
o using the wrong driver (FIR/irtty/irport)
o Wrong irattach command ("irattach /dev/ttySX" vs "irattach irdaX")
o Wrong modules names (should be ircomm-tty, not ircomm_tty)
o Mixing up /dev/ttySX and /dev/ircommX
No, let's go back to your problem, and let's demonstrate that
it can only be a module problem :
We have the message :
---------------------------------
Assertion failed! irlmp != NULL,irlmp.c,irlmp_register_client,line=1354
---------------------------------
This mean that the global variable irlmp is NULL. Bad.
Now, check irlmp.c @ l-79. This variable is NULL only if we
run out of memory (unlikely) or if the irlmp_init() function is not
called.
irlmp_init() is called in irda_init(), irsyms.c @ l-189. Then,
irda_init() is called in irda_proto_init(), af_irda.c @ l-2406.
And irda_proto_init() is called at module insertion (irda.o),
see af_irda.c @ l-2432.
Even not knowing much of C, it's trivially easy to check.
Of course, irlmp is reset to NULL in irlmp_cleanup, strictly
called from irda_cleanup, strictly called from irda_proto_cleanup,
stricly called at module removal.
Same story for the other error message related to irttp.
In other words, with the code I have under my eyes (test11
final), this error message is strictly impossible. So, something of
your setup is very wrong, or your IrDA stack becamed corrupted beyond
recognition.
To summarize, to me the IrDA stack is perfectly fine is
test11, what's wrong and broken is something else...
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
