From: Mark Watson <mark@marubeca.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Building btsco for Fedora 3
Date: Sun, 15 May 2005 16:04:50 +0100 [thread overview]
Message-ID: <42876512.5040205@marubeca.net> (raw)
In-Reply-To: <4286E60F.1020505@xmission.com>
Brad Midgley wrote:
> Mark
> ...
>
>>> make: *** /lib/modules/2.6.11-1.14_FC3/source: No such file or
>>> directory. Stop.
>>
> source is a softlink to the source dir on my machine. it may be good
> enough to install the kernel-header package for your kern version.
> look for a kernel-source package too.
>
Thanks Brad. Turns out the link was the thing I missed. Made link, made
config in kernel source dir and the driver built. Now (and firstly, I'm
probably continuing to be dense, and probably secondly, in the wrong
list at this stage) after depmod the mod loads OK but when I try:
btsco <device address> 1
.. when in pairing mode on the device (a jabra 250) I get
Can't connect RFCOMM channel: Resource temporarily unavailable
I've set the default pin via bluez-pin, was previously seeing auth
requests in log.
Mark
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-15 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 0:47 [Bluez-devel] Building btsco for Fedora 3 Mark Watson
2005-05-15 1:08 ` Henryk Plötz
2005-05-15 6:02 ` Brad Midgley
2005-05-15 15:04 ` Mark Watson [this message]
2005-05-15 19:14 ` Brad Midgley
2005-05-15 19:58 ` Mark Watson
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=42876512.5040205@marubeca.net \
--to=mark@marubeca.net \
--cc=bluez-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.