From: Marcel Holtmann <marcel@holtmann.org>
To: leidenfrost@corscience.de
Cc: martin f krafft <madduck@madduck.net>,
BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth on a MIPS-System
Date: Thu, 07 Oct 2004 15:11:14 +0200 [thread overview]
Message-ID: <1097154674.7325.32.camel@pegasus> (raw)
In-Reply-To: <416536BA.3080901@corscience.de>
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
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-07 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 10:41 [Bluez-users] Bluetooth on a MIPS-System Thomas Leidenfrost
2004-10-07 11:07 ` Marcel Holtmann
2004-10-07 11:36 ` Thomas Leidenfrost
2004-10-07 12:41 ` Marcel Holtmann
2004-10-07 13:10 ` Thomas Leidenfrost
2004-10-07 13:14 ` Marcel Holtmann
2004-10-07 14:06 ` Thomas Leidenfrost
2004-10-07 14:17 ` Marcel Holtmann
2004-10-07 14:55 ` martin f krafft
2004-10-07 16:01 ` Marcel Holtmann
2004-10-07 15:10 ` Thomas Leidenfrost
2004-10-07 15:10 ` Marcel Holtmann
2004-10-07 15:41 ` martin f krafft
2004-10-08 16:12 ` Thomas Leidenfrost
2004-10-07 14:41 ` martin f krafft
2004-10-07 11:42 ` martin f krafft
2004-10-07 12:29 ` Thomas Leidenfrost
2004-10-07 13:11 ` Marcel Holtmann [this message]
2004-10-07 13:20 ` martin f krafft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1097154674.7325.32.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=leidenfrost@corscience.de \
--cc=madduck@madduck.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox