Hello-

     I have an interesting issue (at least I think it's interesting).



     I'm running redhat 7.2 with the 2.4.9-21 kernel, I pulled down the OCO
modules for the qeth and qdio drivers from developerworks (for my kernel
version), and attempted to load them into the kernel (after the appropriate
/etc/modules.conf and /proc/chandev changes/additions were done).  I got
this little monster:


[root@somemachine root]# insmod qdio
Using /lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
remove_wait_queue_Rsmp_166d6b0b
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_event_common_Rsmp_49943507
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_unregister_Rsmp_0e92db0d
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_set_level_Rsmp_25d0b381
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_register_view_Rsmp_266ed7c2
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_hex_ascii_view_Rsmp_ebb4a885
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
add_wait_queue_Rsmp_e4d306c7
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_register_Rsmp_f35379f3
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: unresolved symbol
debug_exception_common_Rsmp_b8fd00fe
/lib/modules/2.4.9-21/kernel/drivers/s390/qdio.o: Note: modules without a
GPL compatible license cannot use GPLONLY_ symbols


     Has anyone else seen this?  I looked around and this seems to have
effected Intel as well, are there any remedies for this?  I do need to use
those drivers and from what I can see, the current tools are not allowing
me to access teh kernel symbols that have been GPL'd, simply because my
module is not GPL'd and is not declared as such.



               Any and all help is greatly appreciated, you may respond on
list or to my address as well,



                         Thank you,


                         M Butler

Reply via email to