Re: [Bluez-users] Bluetooth on a MIPS-System

Marcel Holtmann
2004-10-07T13:11:14Z

Hi Thomas,

> > modprobe takes the name of a module, not the filename.
>
> you're right, that was a little mistake by my own. Now it says this:
> (I've absolutely no idea what's going wrong here)
>
> # modprobe l2cap
> Using /lib/modules/2.4.21/l2cap.o
> insmod: unresolved symbol malloc
> insmod: unresolved symbol putchar
> insmod: unresolved symbol free
> insmod: unresolved symbol perror
> insmod: unresolved symbol parser
> insmod: unresolved symbol get_proto
> insmod: unresolved symbol cmtp_dump
> insmod: unresolved symbol sdp_dump
> insmod: unresolved symbol avdtp_dump
> insmod: unresolved symbol stderr
> insmod: unresolved symbol hidp_dump
> insmod: unresolved symbol bnep_dump
> insmod: unresolved symbol hcrp_dump
> insmod: unresolved symbol rfcomm_dump
> insmod: unresolved symbol raw_dump
> insmod: unresolved symbol _gp_disp
> insmod: unresolved symbol printf
> insmod: unresolved symbol fwrite
> modprobe: failed to load module l2cap

do you tried to load the l2cap.o from bluez-hcidump into your kernel?

Regards

Marcel