[Xenomai-help] Module loading problems

[Xenomai-help] Module loading problems

[Hans-J. Ude]

I've installed Xenomai 2.0.1 but can't load a module stack for the vxWorks
skin. Kernel is 2.6.13 with the included ipipe patch and I'm getting the
following results.

# insmod xeno_hal.ko
# insmod xeno_nucleus.ko
# insmod xeno_vxworks.ko
# insmod xeno_uvm.ko
insmod: error inserting 'xeno_uvm.ko': -1 Function not implemented

# insmod xeno_hal.ko
# insmod xeno_nucleus.ko
# insmod xeno_uvm.ko
# insmod xeno_vxworks.ko
insmod: error inserting 'xeno_vxworks.ko': -1 Device or resource busy

I've put some printk's into the nucleus modules and found that in the first
case there are two pointers which are compared when a subsequent modules is
loaded. Those pointers are expected to be equal but are unequal and the
module is rejected. Can someone tell what I can do here? Maybe there is
something wrong with the modules, with the distro (Suse 9.3) or maybe I'm
doing something wrong. I think i'm gonna try the original gnu modutils next
and get rid of that Suse stuff.

regards,
Hans

Re: [Xenomai-help] Module loading problems

[Philippe Gerum]

Hans-J. Ude wrote:
> I've installed Xenomai 2.0.1 but can't load a module stack for the vxWorks
> skin. Kernel is 2.6.13 with the included ipipe patch and I'm getting the
> following results.
> 
> # insmod xeno_hal.ko
> # insmod xeno_nucleus.ko
> # insmod xeno_vxworks.ko
> # insmod xeno_uvm.ko
> insmod: error inserting 'xeno_uvm.ko': -1 Function not implemented
> 
> # insmod xeno_hal.ko
> # insmod xeno_nucleus.ko
> # insmod xeno_uvm.ko
> # insmod xeno_vxworks.ko
> insmod: error inserting 'xeno_vxworks.ko': -1 Device or resource busy
> 

Vxworks and UVM modules are mutually exclusive. The VxWorks emulation in 
user-space on top of the UVM does not need the former, and even conflicts with 
it when attempting to set up the real-time timer. IOW, just push xeno_hal.ko, 
xeno_nucleus.ko and xeno_uvm.ko.

> I've put some printk's into the nucleus modules and found that in the first
> case there are two pointers which are compared when a subsequent modules is
> loaded. Those pointers are expected to be equal but are unequal and the
> module is rejected. Can someone tell what I can do here? Maybe there is
> something wrong with the modules, with the distro (Suse 9.3) or maybe I'm
> doing something wrong. I think i'm gonna try the original gnu modutils next
> and get rid of that Suse stuff.
> 
> regards,
> Hans
> 
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 

Philippe.