2013/3/17 Ozan Çağlayan <ozancag@xxxxxxxxx>: > This is caused because Debian already defined those > structures/functions/etc in their vendor kernel using 2 patches: > - features/all/ethernet-define-eth_hw_addr_random.patch > - features/all/drm/slab-introduce-kmalloc_array.patch I see, thanks for the explanation, really appreciated. > This kind of problems occur from time to time with other distributions > too. I don't know if in the code level there is a dynamic way to > detect whether those symbols are already defined or not but for now > you can edit compat-3.4.h in the compat-drivers folder and comment out > the lines defining kmalloc_array and eth_hw_addr_random. It works, thanks :-) As I don't want to "make install" I first try to load the module using "insmod": hpc03@stt300:~/Escritorio/compat-drivers-3.9-rc2-2-su$ su -c "insmod /home/hpc03/Escritorio/compat-drivers-3.9-rc2-2-su/drivers/net/ethernet/atheros/alx/alx.ko" Contraseña: Error: could not insert module /home/hpc03/Escritorio/compat-drivers-3.9-rc2-2-su/drivers/net/ethernet/atheros/alx/alx.ko: Unknown symbol in module And dmesg shows: [ 6042.342598] alx: Unknown symbol compat_dependency_symbol (err 0) [ 6042.342883] alx: Unknown symbol mdio_mii_ioctl (err 0) Should I try with a different version of the compat-drivers instead? Or maybe is that I commented out too much from "compat-3.4.h"? Thanks for any hint. -- Camaleón -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
